[regext] Re: WGLC: draft-ietf-regext-rdap-rir-search-09
There have been no objections to this document. The Chairs would like to note that the notice below incorrectly states “Best Current Practice” for the status of this document. As noted during WG last call the document will be progressed onto the Standards Track. There have only been two indications of support: Scott Hollenbeck and Andy Newton. Along with the two authors and the Document Shepherd the Chairs believe this is sufficient consensus to move this document forward. There was some discussion during working group last call resulting in a request, that was agreed to by all parties, that some text to the effect of the following be included in the Shepherd writeup: The shepherd writeup include a description of the situation with respect to the extension identifiers and non-conformance with Standard 95 as noted below. It would be perfectly acceptable to note that only one person raised the concern. With that action the Chairs pass v11 of this document to the Document Shepherd — Mario Loffredo — to confirm that all comments and questions have been addressed and to prepare the Shepherd Writeup. The Chairs will submit the document to the IESG upon completion of the writeup. Thanks to all for the careful review. Antoin and Jim On 12 Jul 2024, at 17:18, James Galvin wrote: > The document editors have indicated that the following document is ready for > submission to the IESG to be considered for publication as a Best Current > Practice: > > RDAP RIR Search > https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-rir-search/09/ > > This document has been through WGLC previously. However, a number of > questions arose and changes were made that are considered material and thus > we are proceeding with this additional WGLC. > > Please indicate your support or no objection for the publication of this > document by replying to this message on list (a simple “+1” is sufficient). > > If any working group member has questions regarding the publication of this > document please respond on the list with your concerns by close of business > everywhere, Friday, 2 August 2024. This WGLC has been extended to 3 weeks > because of the IETF120 meeting. > > If there are no objections the document will be submitted to the IESG. > > The Document Shepherd for this document is Mario Loffredo. > > Thanks, > > Antoin and Jim > REGEXT WG Co-Chairs ___ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
[regext] Re: WGLC: draft-ietf-regext-rdap-geofeed-05
There have not been any objections to submitting this document for publications. After some non-material discussion there are 4 indications of support: Scott Hollenbeck, Andy Newton, Jim Gould, and Mario Loffredo. The current version of the document is v07. The Chairs ask the Document Shepherd - Gavin Brown — to confirm all questions and comments have been addressed, and to prepare the Shepherd Write-up after which the Chairs will submit the document to the IESG on behalf of the working group. Thanks to all for your careful review. Antoin and Jim On 12 Jul 2024, at 17:12, James Galvin wrote: > The document editors have indicated that the following document is ready for > submission to the IESG to be considered for publication as a Proposed > Standard: > > An RDAP Extension for Geofeed Data > https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-geofeed/ > > Please indicate your support or no objection for the publication of this > document by replying to this message on list (a simple “+1” is sufficient). > > If any working group member has questions regarding the publication of this > document please respond on the list with your concerns by close of business > everywhere, Friday, 2 August 2024. This WGLC has been extended to 3 weeks > because of the IETF120 meeting. > > If there are no objections the document will be submitted to the IESG. > > The Document Shepherd for this document is Gavin Brown. > > Thanks, > > Antoin and Jim > REGEXT WG Co-Chairs ___ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
[regext] Re: [Ext] Secdir last call review of draft-ietf-regext-epp-ttl-15
Hi all, I've taken the liberty of uploading version -17 to add this section. https://www.ietf.org/archive/id/draft-ietf-regext-epp-ttl-17.html#name-changes-to-server-policy Diff to the previous version: https://author-tools.ietf.org/iddiff?url2=draft-ietf-regext-epp-ttl-17 G. > On 11 Oct 2024, at 10:48, Gavin Brown wrote: > > Hi Wes, > >>> Policy changes will almost certainly only happen infrequently, and the >>> omission was intentional on my point. Do you feel it warrants some >>> discussion in the document? >> >> I think inserting a warning note would be helpful to the reader. >> Something along the lines of "Although a client is requesting a >> particular TTL value that is within the current acceptable range, >> registries are not obligated to maintain that value indefinitely and may >> change the value when, for example, they update their acceptable TTL >> value ranges." > > In my working draft[1] I have added a new Section 5.3, which says: > > "Registry operators may change their policies relating to TTL values from > time to time. Previously configured TTL values may consequently fall outside > a newly-applied policy. This document places no obligation on EPP server > operators in respect of these values, and server operators may, as part of a > policy change, change the TTL values specified by clients for domain and host > objects. Section 4 describes how such out-of-band changes should be carried > out." > > Let me know what you think. If it looks good I can upload a new version. > > G. > > [1] > https://github.com/gbxyz/epp-ttl-extension/commit/b8bf5d56779fb5a0123401558fd6cab654348c85#diff-e81d8d738f47db9115098e0fe66a7a9904ca10821206e12ff5229e5e384b648cR577 -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org ___ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
[regext] I-D Action: draft-ietf-regext-epp-ttl-17.txt
Internet-Draft draft-ietf-regext-epp-ttl-17.txt is now available. It is a work item of the Registration Protocols Extensions (REGEXT) WG of the IETF. Title: Extensible Provisioning Protocol (EPP) mapping for DNS Time-To-Live (TTL) values Author: Gavin Brown Name:draft-ietf-regext-epp-ttl-17.txt Pages: 30 Dates: 2024-10-14 Abstract: This document describes an extension to the Extensible Provisioning Protocol (EPP) that allows EPP clients to manage the Time-To-Live (TTL) value for domain name delegation records. About this draft This note is to be removed before publishing as an RFC. The source for this draft, and an issue tracker, may can be found at https://github.com/gbxyz/epp-ttl-extension. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-regext-epp-ttl/ There is also an HTMLized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-regext-epp-ttl-17 A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-regext-epp-ttl-17 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts ___ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
