Re: [regext] WG LAST CALL: draft-ietf-regext-epp-registry-maintenance-03

2020-11-09 Thread James Galvin
The WGLC for this document is now closed. The Chairs do not believe this document is ready for publication. Unfortunately, a number of items were brought up during the last call that have not received enough discussion to resolve. This document will remain a working group document. The auth

Re: [regext] WG LAST CALL: draft-ietf-regext-epp-registry-maintenance-03

2020-10-29 Thread Gould, James
...@verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com<http://verisigninc.com/> From: Jody Kolker Date: Friday, October 23, 2020 at 5:16 PM To: "regext@ietf.org" , James Gould , "gal...@elistx.com" Subject: RE: [regext] WG LAST CALL: draft-ietf-regex

Re: [regext] WG LAST CALL: draft-ietf-regext-epp-registry-maintenance-03

2020-10-26 Thread James Galvin
The Chairs would like to extend this WG Last Call for an additional two weeks, to close on Friday, 30 October 2020. Although there have been 2 indications of support, James Gould provided some extensive comments, most of which have been addressed in version -04 of the document. However, Jody

Re: [regext] WG LAST CALL: draft-ietf-regext-epp-registry-maintenance-03

2020-10-23 Thread Jody Kolker
CALL: draft-ietf-regext-epp-registry-maintenance-03 Notice: This email is from an external sender. Hi, I did a review of draft-ietf-regext-epp-registry-maintenance and the following is my feedback: 1. Section 1.1 Terminology and Definition * Since the draft has moved to WGLC

Re: [regext] WG LAST CALL: draft-ietf-regext-epp-registry-maintenance-03

2020-10-08 Thread Jody Kolker
Thanks for the feedback Jim! We are reviewing and will get back to you From: regext On Behalf Of Gould, James Sent: Thursday, October 8, 2020 7:55 AM To: gal...@elistx.com; regext@ietf.org Subject: Re: [regext] WG LAST CALL: draft-ietf-regext-epp-registry-maintenance-03 Notice: This email is

Re: [regext] WG LAST CALL: draft-ietf-regext-epp-registry-maintenance-03

2020-10-08 Thread Gould, James
Reston, VA 20190 Verisign.com<http://verisigninc.com/> From: regext on behalf of "Gould, James" Date: Tuesday, October 6, 2020 at 3:27 PM To: "gal...@elistx.com" , "regext@ietf.org" Subject: [EXTERNAL] Re: [regext] WG LAST CALL: draft-ietf-regext-epp-regi

Re: [regext] WG LAST CALL: draft-ietf-regext-epp-registry-maintenance-03

2020-10-06 Thread Gould, James
Hi, I did a review of draft-ietf-regext-epp-registry-maintenance and the following is my feedback: 1. Section 1.1 Terminology and Definition * Since the draft has moved to WGLC, this is somewhat a non-applicable point, but the latest practice for EPP extensions has been to use a p

Re: [regext] WG LAST CALL: draft-ietf-regext-epp-registry-maintenance-03

2020-10-05 Thread Mario Loffredo
Hi all, I have a couple of comments about this document: 1) Don't understand which maintenance notifications should be returned  by an info command including the element. I mean, only those about both ongoing and future events or also about past events? In the latter case,  could it be helpf

Re: [regext] WG LAST CALL: draft-ietf-regext-epp-registry-maintenance-03

2020-10-05 Thread Roger D Carney
+1 From: regext on behalf of Tobias Sattler Sent: Monday, October 5, 2020 6:23 AM To: James Galvin Cc: regext@ietf.org Subject: Re: [regext] WG LAST CALL: draft-ietf-regext-epp-registry-maintenance-03 Notice: This email is from an external sender. +1

Re: [regext] WG LAST CALL: draft-ietf-regext-epp-registry-maintenance-03

2020-10-05 Thread Tobias Sattler
+1 > On 2. Oct 2020, at 22:57, James Galvin wrote: > > The following working group document is believed to be ready for submission > to the IESG for publication as a standards track document: > > https://datatracker.ietf.org/doc/draft-ietf-regext-epp-registry-maintenance/ > > This WG last cal