IETF publishes RFC 10091 creating an IANA registry for EPP extensions
in plain words
EPP is a computer language that domain registries use to create, change and delete domain names. Some registries added their own extra features, which sometimes clashed with each other. This new RFC creates a shared public list so developers can see what already exists.
Full summary
The Internet Engineering Steering Group (IESG) has published RFC Request for Comments A numbered document in the series recording the internet's technical standards and practices. Full definition of RFC 10091, a specification for a registry The central database and system of a top-level domain, or loosely the organization that runs it. Full definition of registry of extensions to the Extensible Provisioning Protocol (EPP Extensible Provisioning Protocol The protocol registrars use to manage domain names at registries. Full definition of EPP), maintained by IANA Internet Assigned Numbers Authority The functions that coordinate the root zone, IP addresses and protocol numbers. Full definition of IANA. The document was written by S. Hollenbeck of Verisign Labs as part of the IETF Internet Engineering Task Force The open body that writes internet standards such as DNS, EPP and RDAP. Full definition of IETF regext working group A volunteer team chartered to study a policy issue and make recommendations. Full definition of working group. It replaces RFC 7451 and changes its status from informational to best practice.
EPP is mainly used by domain registries, and by registrant The person or organization that holds a domain name registration. Full definition of registrant or their registrar A company that registers domain names for customers with the registry. Full definition of registrar, to create, modify and delete domain name A readable internet name made of labels separated by dots. Full definition of domain name. Because each registry has its own registration Obtaining the right to use a domain name for a set period. Full definition of registration policy, the standard schema does not fit everyone, so many registries built their own extensions. RFC 3735 gives guidance on creating extensions but says little about how to publish them, and several registries have built different, incompatible extensions for the same problem, such as recording VAT information on objects created through EPP.
Under the new registry, extensions are registered under the “specification required” policy described in RFC 8126. This means a public specification must exist and be reviewed by an expert appointed by IANA, currently Gavin Brown. Discussion about a proposed extension or the quality of its documentation takes place on the regext mailing list. Reviewers must consider privacy effects, a concern the document says was absent from RFC 3735.
The RFC asks reviewers to be flexible. An extension that is documented and deployed should be registered even if the expert has technical objections. Several similar extensions may be registered, and a applicant An organization that has applied to ICANN to run a new gTLD. Full definition of applicant proposing a close copy of an existing extension will be told about it, but will not be blocked.
The RFC also says that XML-related information for EPP must be recorded in the XML registry under RFC 3688. To register, applicants send IANA a form giving the extension name, a link to its specification, contact details, the TLD top-level domain The last part of a domain name, after the final dot. Full definition of TLD it applies to or “Any”, and any intellectual property disclosures, such as patents under RFC 8179. The document includes an example form and a real registration, for the grace period A window after a registry action when it can be reversed, usually with a refund to the registrar. Full definition of grace period extension in RFC 3915, where the IESG is the contact.
The document also summarises the main changes from RFC 7451, including the new status and the move of the discussion list from eppext@ietf.org to regext@ietf.org.