Organization Extension for the Extensible Provisioning Protocol (EPP)
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: IETF-Announce <firstname.lastname@example.org> Cc: The IESG <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, Pieter Vandepitte <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org Subject: Protocol Action: 'Organization Extension for the Extensible Provisioning Protocol (EPP)' to Proposed Standard (draft-ietf-regext-org-ext-11.txt) The IESG has approved the following document: - 'Organization Extension for the Extensible Provisioning Protocol (EPP)' (draft-ietf-regext-org-ext-11.txt) as Proposed Standard This document is the product of the Registration Protocols Extensions Working Group. The IESG contact persons are Adam Roach, Alexey Melnikov and Ben Campbell. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-regext-org-ext/
Technical Summary This document describes an extension to EPP object mappings that is designed to support assigning an organization to any existing object (domain, host, contact) as well as any future objects. Working Group Summary The document has received community review and is of interest to multiple parties, as it covers a basic need among domain name registrars and registries. The document has been discussed on the regext mailing list and various IETF meetings of the regext working group. The authors have addressed all comments and changes have been incorporated in the document. The document was updated several times during the WGLC due to several thorough reviews. Document Quality Verisign and CNNIC have working implementations of the specification and at least 2 other Registry operators have plans or are interested in implementing the specification. All EPP XML examples have been validated against the XML schema provided in the drafts by the Document Shepherd. Personnel The document shepherd is Pieter Vandepitte, email@example.com The responsible Area Director is Adam Roach, firstname.lastname@example.org
RFC Editor Note Please ensure that draft-ietf-regext-org and draft-ietf-regext-org-ext are published with consecutive RFC numbers (and preferably in that order).