Okay, I completely missed the support for publication. Email sorting - what a problem.
Anyway, given the material nature of the discussion it is still appropriate to withdraw publication of this document at this time. The WG should continue the discussion until it comes to a consensus resolution and then the Chairs will re-issue the Last Call. Thanks, Jorge, Antoin, and Jim On 2 Nov 2025, at 15:57, James Galvin wrote: > This WG Last Call is now officially closed. > > Although there has been quite some discussion on the list regarding this > draft, not a single person indicated support for submitting this document for > publication. For completeness, there were no objections for submission. > > The discussion has focused on what started as a suggested “editorial” change > and quickly became a material change with differences of opinion regarding > the impact of the change. > > Absent support and with the continuing discussion, clearly this document is > not ready for submission to the IESG for publication. > > The document remains a WG document and the discussion that has started should > continue, ideally with a different subject line so the thread can be followed > more easily on the list. > > The Chairs will issue another WG Last Call when there is a consensus view on > how to resolve the issue. > > Thanks, > > Jorge, Antoin, and Jim > > > On 13 Oct 2025, at 16:33, James Galvin via Datatracker wrote: > >> Subject: WG Last Call: draft-ietf-regext-ext-registry-epp-00 (Ends >> 2025-10-27) >> >> This message starts a 2-week WG Last Call for this document. >> >> Abstract: >> The Extensible Provisioning Protocol (EPP) includes features to add >> functionality by extending the protocol. It does not, however, >> describe how those extensions are managed. This document describes a >> procedure for the registration and management of extensions to EPP, >> and it specifies a format for an IANA registry to record those >> extensions. >> >> File can be retrieved from: >> https://datatracker.ietf.org/doc/draft-ietf-regext-ext-registry-epp/ >> >> Please review and indicate your support or objection to proceed with the >> publication of this document by replying to this email keeping >> [email protected] in copy. Objections should be motivated and suggestions to >> resolve them are highly appreciated. >> >> Authors, and WG participants in general, are reminded again of the >> Intellectual Property Rights (IPR) disclosure obligations described in BCP 79 >> [1]. 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/ >> >> >> >> _______________________________________________ >> 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]
