The last call for this draft ended on 9 March. I'm going to publish an updated draft on 14 March (we're currently in the draft lockout period ahead of IETF-125) that includes the following:
Updated "XML schemas, XML schema URIs, and XML namespace URIs" wording in Section 2.2.1. Noted that the value of "TLDs" can be "N/A" in Section 2.2.2. Updated "removed or deactivated" wording in Section 2.2.3. Changed RFC 3735 from an informative reference to a normative reference. In my opinion as editor, we had support for all of these changes. There were two other topics raised during the last call for which I don't believe we had support to make changes. These include: Adding text to describe how to register new EPP transports in the extension registry. A suggestion to remove this text from Section 1: > 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. Did I miss anything? Scott _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
