> -----Original Message----- > From: Andy Newton <[email protected]> > Sent: Thursday, March 5, 2026 2:40 PM > To: [email protected] > Subject: [EXTERNAL] [regext] Re: WG Last Call: draft-ietf-regext-ext-registry- > epp-03 (Ends 2026-03-09) > > 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. > > I agree. If 50% of EPP extensions have not been registered than the goal of > this registry has not been met. > > Given that, the following paragraphs from Section 1 should be struck: > > > RFCs 3735 and 5730 do not describe how extension development can be > managed and coordinated. This has led to a situation in which server > operators can develop different extensions to address similar needs, such as > the provisioning of Value Added Tax (VAT) information. Clients then need to > support multiple extensions that serve similar purposes, and interoperability > suffers as a result. > > > > An IANA registry can be used to help manage and coordinate the > development of protocol extensions. This document describes an IANA > registry that will be used to coordinate the development of EPP extensions. > > > > Thanks for pointing this out.
[SAH] I'd like to keep all of that text. The goal of the registry isn't changing. Scott _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
