Re: [regext] CALL FOR ADOPTION: Proposed Milestones for the next year

On Fri, May 17, 2019 at 06:38:12PM +0200, Peter Koch wrote: > could the chairs please clarify my point raised 29 April: now OBE. Thanks, Peter, impatient at times ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext

Re: [regext] CALL FOR ADOPTION: Proposed Milestones for the next year

On 29 Apr 2019, at 9:16, Peter Koch wrote: Jim, Antoin, On Fri, Apr 26, 2019 at 04:25:41PM -0400, James Galvin wrote: Please review the milestones and respond to the list with ???+1??? or ???+1 with any updates or comments??? or just respond with your questions or comments. maybe I miss

Re: [regext] CALL FOR ADOPTION: Proposed Milestones for the next year

On Fri, May 17, 2019 at 11:58:59AM -0400, James Galvin wrote: > The results were: > Support: 4 > Object: 0 > > The chairs consider these milestones adopted by the REGEXT WG. could the chairs please clarify my point raised 29 April: # maybe I missed it, but is an item designated as a milestone t

Re: [regext] CALL FOR ADOPTION: Proposed Milestones for the next year

The call for adoption of Proposed Milestones ended 2 May 2019. (Sorry, this was not indicated in the original call for support message.) The results were: Support: 4 Object: 0 The chairs consider these milestones adopted by the REGEXT WG. The chairs will submit changes to our milestone list t

Re: [regext] CALL FOR ADOPTION: Proposed Milestones for the next year

+1 On 4/26/19, 4:26 PM, "regext on behalf of James Galvin" wrote: As discussed at our last meeting at IETF104 Prague, we need to set milestones for ourself. This is a formal request for adoption of a set of milestones. As previously explained, we have included the tw

Re: [regext] CALL FOR ADOPTION: Proposed Milestones for the next year

+1 on the milestones -Original Message- From: regext On Behalf Of James Galvin Sent: Friday, April 26, 2019 3:26 PM To: Registration Protocols Extensions Subject: [regext] CALL FOR ADOPTION: Proposed Milestones for the next year As discussed at our last meeting at IETF104 Prague, we

Re: [regext] CALL FOR ADOPTION: Proposed Milestones for the next year

Jim, Antoin, On Fri, Apr 26, 2019 at 04:25:41PM -0400, James Galvin wrote: > Please review the milestones and respond to the list with ???+1??? or ???+1 > with any updates or comments??? or just respond with your questions or > comments. maybe I missed it, but is an item designated as a mileston

Re: [regext] CALL FOR ADOPTION: Proposed Milestones for the next year

+1 Best, Maurizio > Il giorno 26 apr 2019, alle ore 22:25, James Galvin ha > scritto: > > As discussed at our last meeting at IETF104 Prague, we need to set milestones > for ourself. > > This is a formal request for adoption of a set of milestones. > > As previously explained, we have incl

Re: [regext] CALL FOR ADOPTION: Proposed Milestones for the next year

+1 mario Il 26/04/2019 22:25, James Galvin ha scritto: As discussed at our last meeting at IETF104 Prague, we need to set milestones for ourself. This is a formal request for adoption of a set of milestones. As previously explained, we have included the two proposed new documents in this se

Re: [regext] CALL FOR ADOPTION: Proposed Milestones for the next year

+1 — JG James Gould Distinguished Engineer jgo...@verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com On 4/26/19, 4:26 PM, "regext on behalf of James Galvin" wrote: As discussed at our last meeting at IETF104 Prague, we need to se

[regext] CALL FOR ADOPTION: Proposed Milestones for the next year

As discussed at our last meeting at IETF104 Prague, we need to set milestones for ourself. This is a formal request for adoption of a set of milestones. As previously explained, we have included the two proposed new documents in this set. If you support the adoption of the documents you can j