[regext] I-D Action: draft-ietf-regext-rdap-reverse-search-05.txt

2020-10-26 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Registration Protocols Extensions WG of the IETF. Title : Registration Data Access Protocol (RDAP) Reverse search capabilities Authors : Mario Loff

[regext] Fwd: New Version Notification for draft-ietf-regext-rdap-reverse-search-05.txt

2020-10-26 Thread Mario Loffredo
Hi all, sorry for the delay in publishing this version as a consequence of the WG feedback. I have been very busy with the review of drafts under IESG evaluation and the implementation of jscontact-tools library. Hope this version addresses the points raised by Jansdip, George, Patrick and

Re: [regext] WG LAST CALL: draft-ietf-regext-unhandled-namespaces-03

2020-10-26 Thread Gould, James
Patrick, We'll agree to disagree with the value and risk of draft-ietf-regext-unhandled-namespaces, since I can't think of a theoretical or real risk to existing clients with at least two independent implementations. Your objection can be included in the document shepherd writeup, but as noted

Re: [regext] WG LAST CALL: draft-ietf-regext-secure-authinfo-transfer-03

2020-10-26 Thread James Galvin
Thanks to all who responded to the WG Last Call for this document. There have been 3 clear indications of support with no objections. There was some discussion and support to change the document to Standards Track from BCP. There have not been any issues noted during last call. The WG last

[regext] The REGEXT WG has placed draft-blanchet-regext-rfc7484bis in state "Candidate for WG Adoption"

2020-10-26 Thread IETF Secretariat
The REGEXT WG has placed draft-blanchet-regext-rfc7484bis in state Candidate for WG Adoption (entered by Antoin Verschuren) The document is available at https://datatracker.ietf.org/doc/draft-blanchet-regext-rfc7484bis/ ___ regext mailing list regext

Re: [regext] WG LAST CALL: draft-ietf-regext-unhandled-namespaces-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 3 indications of support, Patrick Mevzek and James Gould have been having an extended discussion on the mailing list about one issue. The chairs believe

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-rfc7482bis

2020-10-26 Thread Antoin Verschuren
Thank you Scott and all others that replied during the extended WGLC.. The chairs agree with the Authors that there was no consensus reached during the extended WGLC to make changes to the document. Therefor this WGLC is now officially closed. We had 3 explicit statements of support for this docum

Re: [regext] WG LAST CALL: draft-ietf-regext-rfc7483bis

2020-10-26 Thread Antoin Verschuren
Thank you Scott and all others that replied during the extended WGLC.. This is to inform you that this WGLC is now officially closed. We had 3 explicit statements of support for this document, and 2 concerns which led to an extended WGLC. 1 of the concerns was addressed by the autor in a new vers

Re: [regext] WG LAST CALL: draft-ietf-regext-rfc7482bis

2020-10-26 Thread Mario Loffredo
Hi Chairs, Il 26/10/2020 16:10, Antoin Verschuren ha scritto: Thank you Scott and all others that replied during the extended WGLC.. The chairs agree with the Authors that there was no consensus reached during the extended WGLC to make changes to the document. Therefor this WGLC is now offici

Re: [regext] WG LAST CALL: draft-ietf-regext-unhandled-namespaces-03

2020-10-26 Thread Thomas Corte
Hello, On 10/26/20 15:01, James Galvin wrote: > Current consensus is to seek publication.  However, we are a relatively > small group and we would like all comments considered by multiple > people.  Would others please indicate their point of view in the active > thread between James and Patrick?