Hi Jim, My co-authors and I do not believe that it is appropriate to introduce new functionality in this document. This document will fix the erratum only. Any additional functionality should be done in a different document (i.e "RGP v2.0").
The reason for this is that there will be EPP servers who will want to stick with RGP "v1.0", and they need the erratum to be fixed. I would be supportive of an effort to improve the RGP extension in the way you suggest, but this document is not the vehicle for that work. Thanks, G. On Wed, 6 May 2026, at 13:29, Gould, James wrote: > Jim, > > I support adoption, but I would like the scope of the work to include > consideration of the recommendation that came from the EPP > Extensibility and Extension Analysis: > > Enhance the RGP Extension (Section 3.1) to use a single step Restore > Command and add an optional “expiry” attribute to the RGP statuses. > With a one step Restore Command there is no need for the RGP Poll > Mapping (Section 3.6). Elements of the .SE EPP Extensions (Section > 3.22) deactivation could be merged into the enhancement to the RGP > Extension, which includes the option for a scheduled deactivation at > expiry. > > I will add one additional scope item, which is if we can't get to a one > step Restore Command, then we should add support for a poll message > (see RGP Poll Mapping at > https://www.verisign.com/assets/epp-sdk/verisign_epp-extension_rgp-poll_v01.html > > ) to notify the registrar that the pendingRestore period is ending. We > could reference the Change Poll message in RFC 8590 if the server > transitions the domain name from pendingRestore back to > redemptionPeriod. > > Thanks, > > -- > > JG > > > > James Gould > Fellow Engineer > [email protected] > <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[email protected]> > > 703-948-3271 > 12061 Bluemont Way > Reston, VA 20190 > > Verisign.com <http://verisigninc.com/> > > > > > On 5/4/26, 6:55 AM, "James Galvin" <[email protected] > <mailto:[email protected]>> wrote: > > > Caution: This email originated from outside the organization. Do not > click links or open attachments unless you recognize the sender and > know the content is safe. > > > 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://secure-web.cisco.com/1TXpgrge9ZkQPICSJFjZlsgFIQ2ylhIQ1Otb9zG_aEjsJlVWqd3puURvVDfwrs3pBBg4-YXj4IYTmUCz-1fVkQTyWMI10eeIduJdhu81ivodZOgnIj1pWexfIXHHxV21FZAf_rh8IQuG-jMagJTZbGRERihyhbYDE97tFlMY2I5OsOWMhDNGsN__PLvSXrP4G0ou3HkG2V8dqLmtPxZisZJbASOt8Hb5tdE2d6loDZMunRK3wbXbYLCE2Q8SxOkQbHVBzF0OM8NzFfkKOe-EvCObgYGQDm8jjVRzJyfDQts0/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fbcp78%2F >> >> <https://secure-web.cisco.com/1TXpgrge9ZkQPICSJFjZlsgFIQ2ylhIQ1Otb9zG_aEjsJlVWqd3puURvVDfwrs3pBBg4-YXj4IYTmUCz-1fVkQTyWMI10eeIduJdhu81ivodZOgnIj1pWexfIXHHxV21FZAf_rh8IQuG-jMagJTZbGRERihyhbYDE97tFlMY2I5OsOWMhDNGsN__PLvSXrP4G0ou3HkG2V8dqLmtPxZisZJbASOt8Hb5tdE2d6loDZMunRK3wbXbYLCE2Q8SxOkQbHVBzF0OM8NzFfkKOe-EvCObgYGQDm8jjVRzJyfDQts0/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fbcp78%2F> >> [2] >> https://secure-web.cisco.com/1uMCH_yupWcZNJWMiCJEQslQSJynvSLpf7Bm4yzQSir1OqqWm8Prt3md_dhShNy-bm8r3UhBwz2xSC6a9JwFE6Q7b97lw4YSCCT1RNUmrsbLBh6VQIZ4qItLJQbwBgCzPr1dfGKtHVRuf8YKZ3ekhxndJONgiNnD0x0HEt21UUIzipVciuia_CNVF_VXm8ezf1tya64vO67ozj_dXS-BuAD32u6jlWmq6P2P_Tyl9Dmw9NCIO3uYL0y2xtAryHp395UiWGvRd1q1rx4L3fhDO0Eoh098sGrbOcFaqhHDGzPI/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fbcp79%2F >> >> <https://secure-web.cisco.com/1uMCH_yupWcZNJWMiCJEQslQSJynvSLpf7Bm4yzQSir1OqqWm8Prt3md_dhShNy-bm8r3UhBwz2xSC6a9JwFE6Q7b97lw4YSCCT1RNUmrsbLBh6VQIZ4qItLJQbwBgCzPr1dfGKtHVRuf8YKZ3ekhxndJONgiNnD0x0HEt21UUIzipVciuia_CNVF_VXm8ezf1tya64vO67ozj_dXS-BuAD32u6jlWmq6P2P_Tyl9Dmw9NCIO3uYL0y2xtAryHp395UiWGvRd1q1rx4L3fhDO0Eoh098sGrbOcFaqhHDGzPI/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fbcp79%2F> >> [3] >> https://secure-web.cisco.com/1bzy25SwjQCIJWWvrWtLcFcoMeQdFHsF_q2H57wkEMqQriDhfXIPs6UkWyUoJkloRgAKnjklrq7Mv3G-C80nCfpayPbnqRAg95XWbBf4vCcmmWSjRZRnkaeeM9VOkqdYD2qb9XrsGKpYATSkSb-MHKTh6EOfO189hH79fmzzTbReQmcrVhe-itZRmGWGfTdNhnK_0aRQtNeieJLka5-e0InwyDUPs45btlM1ZxmN6-a0zaArCNuiwQ6jeyL9L6w2IhevBRAoueSI8gL0DOxCMPXTzB9OM4CqniwKfxfF3R9o/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Frfc6701%2F >> >> <https://secure-web.cisco.com/1bzy25SwjQCIJWWvrWtLcFcoMeQdFHsF_q2H57wkEMqQriDhfXIPs6UkWyUoJkloRgAKnjklrq7Mv3G-C80nCfpayPbnqRAg95XWbBf4vCcmmWSjRZRnkaeeM9VOkqdYD2qb9XrsGKpYATSkSb-MHKTh6EOfO189hH79fmzzTbReQmcrVhe-itZRmGWGfTdNhnK_0aRQtNeieJLka5-e0InwyDUPs45btlM1ZxmN6-a0zaArCNuiwQ6jeyL9L6w2IhevBRAoueSI8gL0DOxCMPXTzB9OM4CqniwKfxfF3R9o/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Frfc6701%2F> >> >> The IETF datatracker status page for this Internet-Draft is: >> https://secure-web.cisco.com/15P3a7l8Q3tCyt2hhuq9024LbHnPMvxJ6uW3bfC9gTmfF4L9kUBeiZBz8SyubmOZjVRfrNya4Iqdc93mdH53pVINftWtjWB1a9KJWx6ysD5OYZVL7Oka6FiwPgMjtNoGpoCKJzUVLGIiVzXt6LggUi15Hg0igtkXwN6EhPWpRlXKdbzeNKVW-DQCOdHWdUmPs2PqKxCFVFx0U7EZPZ0pPK5ImwSoI5zpBqHTK5IBFMpgMOyGxiqkvQuATutoMeb2W0BoD6a_Qtcvn1_uGgeD3Oh-dKjWjSDLqNjIRmbVZyzA/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-carney-regext-rfc3915bis%2F >> >> <https://secure-web.cisco.com/15P3a7l8Q3tCyt2hhuq9024LbHnPMvxJ6uW3bfC9gTmfF4L9kUBeiZBz8SyubmOZjVRfrNya4Iqdc93mdH53pVINftWtjWB1a9KJWx6ysD5OYZVL7Oka6FiwPgMjtNoGpoCKJzUVLGIiVzXt6LggUi15Hg0igtkXwN6EhPWpRlXKdbzeNKVW-DQCOdHWdUmPs2PqKxCFVFx0U7EZPZ0pPK5ImwSoI5zpBqHTK5IBFMpgMOyGxiqkvQuATutoMeb2W0BoD6a_Qtcvn1_uGgeD3Oh-dKjWjSDLqNjIRmbVZyzA/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-carney-regext-rfc3915bis%2F> >> >> There is also an HTMLized version available at: >> https://secure-web.cisco.com/1MygE6wy3IWEJu86tYvWwdQ2a9x-66toFo_LrlZAG2X_f8rfqOmBUDdPnS64LU0ugOCSzj5IZ0Mj7OKhyRt6ttx1B5p175CeP_m3pPEfot769i2NxVQ4Q-3e6I3VtDIjiyvesurRLC8bgLk2927ykDy1LsqkCR_jlgRANMeoD31xKNFvaGfu-V2migyA6wLrWA4iM-kU9ajnVEaObYglaUO6fpLb8-PeuZKkfpsBmsxK6GMwOAyY0NFFKvyC1TvsumqZEHLMDk9i4-iYoi1Z3K8vOxqF1CGP6BQrmBZ6Hy8I/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-carney-regext-rfc3915bis-02 >> >> <https://secure-web.cisco.com/1MygE6wy3IWEJu86tYvWwdQ2a9x-66toFo_LrlZAG2X_f8rfqOmBUDdPnS64LU0ugOCSzj5IZ0Mj7OKhyRt6ttx1B5p175CeP_m3pPEfot769i2NxVQ4Q-3e6I3VtDIjiyvesurRLC8bgLk2927ykDy1LsqkCR_jlgRANMeoD31xKNFvaGfu-V2migyA6wLrWA4iM-kU9ajnVEaObYglaUO6fpLb8-PeuZKkfpsBmsxK6GMwOAyY0NFFKvyC1TvsumqZEHLMDk9i4-iYoi1Z3K8vOxqF1CGP6BQrmBZ6Hy8I/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-carney-regext-rfc3915bis-02> >> >> A diff from the previous version is available at: >> https://secure-web.cisco.com/1mj-SdPsvOVvFsRae_SCQ49DXup2hhmrtugEpe6RU-MnzoeYIqBo4sBDTtrFezPPiCPscUJnoXPVIzuN1TwLue96PQMLMkuIL2CantZOG8WhhznLGdFP8Lc37FRssPvmtYyg2_BUmW1gTG0XdQc2NXe1AsMzu5HetK27EQjpPzZMpm5pUmqmzbs-sLNwD9-UVEvmfVT7nXd0G4YtziXlTgeDc_XLmXAgAKeUYD-c0ECKop0QKaW_vUxHtNUFmmffIki6nmj3QzY_OIFBhapoYl54IlrbJIeylJ1LVUmNN9kU/https%3A%2F%2Fauthor-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-carney-regext-rfc3915bis-02 >> >> <https://secure-web.cisco.com/1mj-SdPsvOVvFsRae_SCQ49DXup2hhmrtugEpe6RU-MnzoeYIqBo4sBDTtrFezPPiCPscUJnoXPVIzuN1TwLue96PQMLMkuIL2CantZOG8WhhznLGdFP8Lc37FRssPvmtYyg2_BUmW1gTG0XdQc2NXe1AsMzu5HetK27EQjpPzZMpm5pUmqmzbs-sLNwD9-UVEvmfVT7nXd0G4YtziXlTgeDc_XLmXAgAKeUYD-c0ECKop0QKaW_vUxHtNUFmmffIki6nmj3QzY_OIFBhapoYl54IlrbJIeylJ1LVUmNN9kU/https%3A%2F%2Fauthor-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-carney-regext-rfc3915bis-02> > > > _______________________________________________ > regext mailing list -- [email protected] <mailto:[email protected]> > To unsubscribe send an email to [email protected] > <mailto:[email protected]> > > > > _______________________________________________ > regext mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
