Thanks to all who responded to this extended call for adoption. The Chairs
note that in addition to the authors, Jim Gould and Pawel Kowalik have
indicated support for adoption.
With that, the authors are requested to submit version -03 of their document to
the datatracker with the following name, which has been pre-approved:
draft-ietf-regext-rfc3915bis
This is a call for a Document Shepherd for the document. Please note on the
mailing list if you are willing to be the Document Shepherd for this document.
Thanks,
Jorge, Antoin, Jim
On 4 May 2026, at 6:55, James Galvin wrote:
> Folks,
>
> IMPORTANT: PLEASE READ AND RESPOND IF APPROPRIATE FOR YOU.
>
>
> Strictly speaking, based on the fact that no one outside of the authors have
> indicated support for adopting this document, the adoption of this document
> should be rejected. However, this working group often makes exceptions, in
> large part because the number of working group members who are active is
> quite small compared to the typical IETF working group. In this case, the
> authors are all active participants, leaving extremely few others to express
> an opinion.
>
> So here’s the exception.
>
> The Chairs would suggest this document be adopted. Although we do not
> ordinarily base our decisions only on document author preferences, this is an
> update to an existing standard that should progress, in our opinion of
> course. If we adopt this document the working group will still have a
> decision point at which it can reject or revise these changes.
>
> Since this is an exception, we have not changed the status of the document
> just yet. While we will consider this document adopted, we are going to
> allow an additional week for any working group member to object this
> decision. If anyone objects, then this document will not be adopted and will
> revert to remaining on the list of “Candidate for Working Group Adoption”.
> The Chairs will work with the authors to consider the best path forward at
> that time.
>
> If no one objects during this week, the document status will change on 11 May
> 2026 and the Chairs will ask the authors to submit a draft named for the
> working group.
>
> The opportunity to object to the adoption of this draft, closes on Monday, 11
> May 2026.
>
> Please reply to the list if you want to object and please indicate why you do
> not believe we should adopt this document.
>
> Thanks,
>
> Jim, Antoin, Jorge
>
>
> On 20 Apr 2026, at 15:33, James Galvin via Datatracker wrote:
>
>> This message starts a regext WG Call for Adoption of:
>> draft-carney-regext-rfc3915bis-02
>>
>> This Working Group Call for Adoption ends on 2026-05-04
>>
>> Abstract:
>> This document describes an Extensible Provisioning Protocol (EPP)
>> [RFC5730] extension mapping for the management of Domain Name System
>> (DNS) domain names subject to "grace period" policies. Grace period
>> policies exist to allow protocol actions to be reversed or otherwise
>> revoked during a short period of time after the protocol action has
>> been performed. This mapping extends the EPP domain name mapping
>> [RFC5731] to provide additional features required for grace period
>> processing.
>>
>> This document replaces the extension mapping for grace periods
>> described in [RFC3915], rendering that document obsolete.
>>
>> Please reply to this message and indicate whether or not you support adoption
>> of this Internet-Draft by the regext WG. Comments to explain your preference
>> are greatly appreciated. Please reply to all recipients of this message and
>> include this message in your response.
>>
>> Authors, and WG participants in general, are reminded of the Intellectual
>> Property Rights (IPR) disclosure obligations described in BCP 79 [2].
>> Appropriate IPR disclosures required for full conformance with the provisions
>> of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
>> Sanctions available for application to violators of IETF IPR Policy can be
>> found at [3].
>>
>> Thank you.
>> [1] https://datatracker.ietf.org/doc/bcp78/
>> [2] https://datatracker.ietf.org/doc/bcp79/
>> [3] https://datatracker.ietf.org/doc/rfc6701/
>>
>> The IETF datatracker status page for this Internet-Draft is:
>> https://datatracker.ietf.org/doc/draft-carney-regext-rfc3915bis/
>>
>> There is also an HTMLized version available at:
>> https://datatracker.ietf.org/doc/html/draft-carney-regext-rfc3915bis-02
>>
>> A diff from the previous version is available at:
>> https://author-tools.ietf.org/iddiff?url2=draft-carney-regext-rfc3915bis-02
_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]
