{"service":"corpus","corpus":"rfc","source":"RFC Editor","license":"IETF Trust / RFC Editor terms","record":{"id":"10091","title":"Extension Registry for the Extensible Provisioning Protocol","text":"﻿\n\n\n\nInternet Engineering Task Force (IETF)                     S. Hollenbeck\nRequest for Comments: 10091                                Verisign Labs\nBCP: 248                                                   November 2026\nObsoletes: 7451                                                         \nCategory: Best Current Practice                                         \nISSN: 2070-1721\n\n\n      Extension Registry for the Extensible Provisioning Protocol\n\nAbstract\n\n   The Extensible Provisioning Protocol (EPP) includes features to add\n   functionality by extending the protocol.  It does not, however,\n   describe how those extensions are maintained.  This document\n   describes a procedure for the registration and management of\n   extensions to EPP, and it specifies a format for an IANA registry to\n   record those extensions.  This document obsoletes RFC 7451.\n\nStatus of This Memo\n\n   This memo documents an Internet Best Current Practice.\n\n   This document is a product of the Internet Engineering Task Force\n   (IETF).  It represents the consensus of the IETF community.  It has\n   received public review and has been approved for publication by the\n   Internet Engineering Steering Group (IESG).  Further information on\n   BCPs is available in Section 2 of RFC 7841.\n\n   Information about the current status of this document, any errata,\n   and how to provide feedback on it may be obtained at\n   https://www.rfc-editor.org/info/rfc10091.\n\nCopyright Notice\n\n   Copyright (c) 2026 IETF Trust and the persons identified as the\n   document authors.  All rights reserved.\n\n   This document is subject to BCP 78 and the IETF Trust's Legal\n   Provisions Relating to IETF Documents\n   (https://trustee.ietf.org/license-info) in effect on the date of\n   publication of this document.  Please review these documents\n   carefully, as they describe your rights and restrictions with respect\n   to this document.  Code Components extracted from this document must\n   include Revised BSD License text as described in Section 4.e of the\n   Trust Legal Provisions and are provided without warranty as described\n   in the Revised BSD License.\n\nTable of Contents\n\n   1.  Introduction\n     1.1.  Changes Since RFC 7451\n     1.2.  Conventions Used in This Document\n   2.  Extension Specification and Registration Procedure\n     2.1.  Extension Specification\n       2.1.1.  Designated Expert Evaluation Criteria\n     2.2.  Registration Procedure\n       2.2.1.  Required Information\n       2.2.2.  Registration Form\n       2.2.3.  Registration Processing\n       2.2.4.  Updating Registry Entries\n   3.  IANA Considerations\n   4.  Security Considerations\n   5.  Operational Considerations\n   6.  References\n     6.1.  Normative References\n     6.2.  Informative References\n   Acknowledgements\n   Author's Address\n\n1.  Introduction\n\n   Domain name registries implement a variety of operational and\n   business models.  The differences in these models make it impossible\n   to develop a \"one size fits all\" provisioning protocol; the\n   Extensible Provisioning Protocol [STD69] was designed to focus on a\n   minimal set of common functionality with built-in extension\n   capabilities that allow new features to be specified on an \"as\n   needed\" basis.  Guidelines for extending EPP are documented in\n   [RFC3735] (or its future replacement).\n\n   [STD69] and [RFC3735] do not describe how extension development can\n   be managed and coordinated.  This has led to a situation in which\n   server operators can develop different extensions to address similar\n   needs, such as the provisioning of Value Added Tax (VAT) information.\n   Clients then need to support multiple extensions that serve similar\n   purposes, and interoperability suffers as a result.\n\n   [RFC7451] filled that gap by defining the \"Extensions for the\n   Extensible Provisioning Protocol (EPP)\" IANA registry [IANA-REG] to\n   help manage and coordinate the development of EPP extensions.\n\n   This document addresses issues that were identified with [RFC7451]\n   over time.  Refer to Section 1.1 for more details.\n\n1.1.  Changes Since RFC 7451\n\n   *  The intended status has been changed from Informational to Best\n      Current Practice (BCP).\n\n   *  The name of the mailing list used to review and discuss\n      registration requests was changed from \"eppext\" to \"regext\"\n      throughout the document.\n\n   *  Section 2.1 has been updated to note that Internet-Draft documents\n      are not acceptable specifications for this registry.\n\n   *  Section 2.1.1 has been updated to describe that designated experts\n      are responsible for confirming the correctness of URIs used in\n      extension registration requests, and that IETF namespaces MUST be\n      reserved for specifications published in the IETF Stream.\n\n   *  Section 2.2.1 has been updated by adding \"Other\" to the set of\n      document status values for the registry to avoid confusion with\n      \"Informational\" RFCs and removing use of \"Informational\" for\n      proprietary extensions.  This document includes instructions for\n      IANA to update existing registry entries appropriately.\n\n   *  Section 2.2.2 has been updated by changing \"<registrant name>,\n      <email address>\" to \"<name>, <address>\" to meet right margin\n      constraints.\n\n   *  Section 2.2.3 has been updated to note that registry entries can\n      be removed with IESG approval.\n\n   *  Section 5 (Operational Considerations) has been added.\n\n1.2.  Conventions Used in This Document\n\n   The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n   \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"NOT RECOMMENDED\", \"MAY\", and\n   \"OPTIONAL\" in this document are to be interpreted as described in\n   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all\n   capitals, as shown here.\n\n2.  Extension Specification and Registration Procedure\n\n   This section describes the format of the Extensions for the\n   Extensible Provisioning Protocol (EPP) IANA registry [IANA-REG] and\n   the procedures used to populate and manage registry entries.\n\n2.1.  Extension Specification\n\n   This registry uses the \"Specification Required\" policy described in\n   [RFC8126].  Note that Section 2.1 of [RFC3735] (or its future\n   replacement) provides specific guidelines for documenting EPP\n   extensions.\n\n   The \"Specification Required\" policy requires review by a designated\n   expert.  Section 5 of [RFC8126] describes the role of designated\n   experts and the function they perform.  For this registry, acceptable\n   specifications include RFC documents and proprietary specifications\n   that meet the \"permanent and readily available\" requirement described\n   in Section 4.6 of [RFC8126].  An English language version of the\n   extension specification MUST be referenced from the registry, though\n   non-English versions of the specification may also be provided.\n   Internet-Draft documents are not acceptable specifications for future\n   registrations.  Early allocations [RFC7120] do not apply to the\n   Extensions for the EPP IANA registry [IANA-REG].\n\n2.1.1.  Designated Expert Evaluation Criteria\n\n   Section 5.2 of [RFC8126] describes the role of designated experts.\n   This section describes how the practices described in [RFC8126] are\n   applied for evaluation of EPP extension registration requests.\n\n   The IESG should appoint a primary designated expert and a small\n   number of individuals (perhaps 3 - 5) to serve as backup designated\n   experts as described in Section 5.2 of [RFC8126].  The primary\n   designated expert is responsible for conducting all reviews requested\n   by IANA.  The secondary designated experts are responsible for\n   conducting reviews as a simple majority, consensus-based group if the\n   primary designated expert is unavailable.  In cases where a\n   registration decision could be perceived as creating a conflict of\n   interest for a particular Designated Expert, that Expert MUST defer\n   to the judgment of the other Experts.  The designated experts MUST\n   use the existing regext mailing list (regext@ietf.org) or its\n   successor for public discussion of registration requests.\n\n   Extensions should be evaluated for architectural soundness using the\n   guidelines described in [RFC3735] (or its future replacement),\n   including the Security Considerations section of that document.\n   Expert evaluation should explicitly include consideration of the\n   privacy consequences of proposed extensions, and, at a minimum,\n   ensure that any privacy considerations are fully documented in the\n   relevant specification(s).\n\n   URIs proposed in extensions (XML namespace and schema registration\n   requests are commonly found in EPP extensions) should be evaluated\n   for both syntactic and semantic correctness.  XML schemas, XML schema\n   URIs, and XML namespace URIs defined in the extension specification\n   MUST be registered in the \"IETF XML Registry\" using the procedures\n   described in [RFC3688].  IETF namespaces MUST be reserved for\n   specifications published in the IETF Stream.  Non-IETF namespaces\n   MUST be used for non-IETF specifications (which includes RFC\n   documents produced by all non-IETF streams); the designated experts\n   may need to work with a registrant to identify URIs that can be added\n   to the \"IETF XML Registry\".  Extensions and any normative references\n   necessary to implement the extensions MUST NOT be denoted with \"work\n   in progress\" or any similar description.  Issues discovered during\n   the evaluation MUST be shared with, and can be corrected by, the\n   registrant until the designated experts explicitly decide to accept\n   or reject the registration request.\n\n   Designated experts should be permissive in their evaluation of\n   requests to register extensions that have been implemented and\n   deployed by at least one registry/registrar or server/client pair.\n   This implies that it may indeed be possible to register multiple\n   extensions that provide the same functionality.  Requests to register\n   extensions that have not been deployed should be evaluated with a\n   goal of reducing functional duplication.  A potential registrant who\n   submits a request to register a new, undeployed extension that\n   includes similar functionality to an existing, registered extension\n   should be made aware of the existing extension.  The registrant\n   should be asked to reconsider their request given the existence of a\n   similar extension.  Should they decline to do so, perceived\n   similarity SHOULD NOT be a sufficient reason for rejection as long as\n   all other requirements are met.\n\n2.2.  Registration Procedure\n\n   The registry contains information describing each registered\n   extension.  Registry entries are created and managed by sending forms\n   to IANA that describe the extension and the operation to be performed\n   on the registry entry.\n\n2.2.1.  Required Information\n\n   Name of Extension:\n      A case-insensitive, ASCII text string that contains the name of\n      the extension specification and does not overlap with an existing\n      registered extension.  Non-ASCII representations of the extension\n      name can be included in the \"Notes\" described below.\n\n   Document Status:\n      The document status of the specification document.  For RFCs, the\n      possible set of values includes \"Standards Track\",\n      \"Informational\", \"Experimental\", \"Historic\", and \"BCP\" as\n      described in Sections 4 and 5 of [RFC2026].  For documents that\n      are not RFCs, this will always be \"Other\".\n\n   Reference:\n      A permanent, publicly available reference to the specification of\n      this extension as described in Section 2.1.1.\n\n   Registrant Name and Email Address:\n      The name and email address of the entity that is responsible for\n      managing the registry entry.  If the extension is registered by an\n      IETF Stream RFC, this can simply be listed as \"IETF,\n      <iesg@ietf.org>\".\n\n   TLDs:\n      A text string containing the top-level domain name (or domain\n      names), including the preceding \".\", for which the extension has\n      been specified (e.g., \".org\").  If there are multiple TLDs, they\n      are given as a list of domain names separated by commas, (e.g.\n      \".com\", \".net\").  Internationalized Domain Name (IDN) TLDs MUST be\n      specified in A-label [RFC5890] format.  If the extension is not\n      associated with a specific top-level domain, the case-insensitive\n      text string \"Any\" can be used to indicate that.  If the extension\n      is not associated with domain name processing, the case-\n      insensitive text string \"N/A\" (Not Applicable) can be used to\n      indicate that.\n\n   IPR Disclosure:\n      A pointer to any Intellectual Property Rights (IPR) disclosure\n      document(s) related to this extension, or \"None\" may be used if\n      there are no such disclosures.  This can be an IPR disclosure\n      filed with the IETF in accordance with BCP 79 [BCP79] if the\n      extension is part of an IETF Contribution, or it can be other IPR\n      disclosure documents identifying the claimed intellectual property\n      rights and terms of use for extensions that are not part of an\n      IETF Contribution.\n\n   Status:\n      Either \"Active\" or \"Inactive\".  The \"Active\" status is used for\n      extensions that are currently implemented and in use.  The\n      \"Inactive\" status is used for extensions that are not implemented\n      or are otherwise not being used.  \"Inactive\" can also be used for\n      extensions for which a reference specification becomes unavailable\n      as described in Section 2.2.4.\n\n   Notes: Either \"None\" or other text that describes optional notes to\n   be included with the registered extension.  If the Status value is\n   being changed, text MUST be included to describe the rationale for\n   the status change.\n\n2.2.2.  Registration Form\n\n   The required information MUST be provided using the following\n   registration form.  Form field names and values MAY appear on the\n   same line.\n\n      Name of Extension:  <text string> (quotes are optional)\n\n      Document Status:  <document status>\n\n      Reference:  <RFC number, URL, etc.>\n\n      Registrant Name and Email Address:  <name>, <address>\n\n      TLDs:  \"Any\"|\"N/A\"|<one or more TLD text strings separated by\n         commas>\n\n      IPR Disclosure:  \"None\"|<URL>\n\n      Status:  \"Active\"|\"Inactive\"\n\n      Notes:  \"None\"|<optional text>\n\n   Example form with RFC specification:\n\n      Name of Extension:  \"An Extension RFC for the Extensible\n         Provisioning Protocol (EPP)\"\n\n      Document Status:  Standards Track\n\n      Reference:  RFC XXXX\n\n      Registrant Name and Email Address:  IETF, <iesg@ietf.org>\n\n      TLDs:  Any\n\n      IPR Disclosure:  None\n\n      Status:  Active\n\n      Notes:  None\n\n   Example form with non-RFC specification:\n\n      Name of Extension:  \"An Example Extension for the .example Top-\n         Level Domain\"\n\n      Document Status:  Other\n\n      Reference:  https://www.example.com/html/example-epp-ext.txt\n\n      Registrant Name and Email Address:  John Doe, jdoe@example.com\n\n      TLDs:  .example\n\n      IPR Disclosure:\n         https://www.example.com/ipr/example-epp-ext-ipr.html\n\n      Status:  Active\n\n      Notes:  None\n\n2.2.3.  Registration Processing\n\n   Registrants should send each registration form to IANA with a single\n   record for incorporation into the registry (see\n   <https://www.iana.org/assignments/epp-extensions>).  Send the form\n   via email to <iana@iana.org> or complete the online form.  The\n   subject line MUST indicate the type of request by including one of\n   the following:\n\n   INSERT:  indicates insertion of a new record,\n\n   MODIFY:  indicates replacement of an existing record,\n\n   DEACTIVATE:  indicates deactivation of an existing record, or\n\n   REMOVE:  indicates removal of an existing record.\n\n   Removal of registrations created through IETF consensus MUST be\n   approved by the IESG using the IESG Approval process described in\n   Section 4.10 of [RFC8126].  Registrations not created through IETF\n   consensus can be removed or deactivated with the approval of the\n   IESG, or at the request of the original registrant, in consultation\n   with or at the request of the designated experts.\n\n   On receipt of a registration request, IANA will initiate review by\n   the designated expert(s), who will evaluate the request using the\n   criteria in Section 2.1.1 in consultation with the current working\n   group mailing list focused on the development of EPP extensions, if\n   such a working group exists.\n\n2.2.4.  Updating Registry Entries\n\n   When submitting changes to existing registry entries, include text in\n   the \"Notes\" field of the registration form describing the change.\n   Under normal circumstances, registry entries are only to be updated\n   by the registrant.  If the registrant becomes unavailable or is\n   otherwise unresponsive, a designated expert can submit a registration\n   form to IANA to update the registrant information.  Entries can\n   change state from \"Active\" to \"Inactive\" and back again as long as\n   state-change requests conform to the processing requirements\n   identified in this document.  In addition to entries that become\n   \"Inactive\" due to a lack of implementation, entries for which a\n   specification becomes consistently unavailable over time should be\n   marked \"Inactive\" by the designated expert until the specification\n   again becomes reliably available.\n\n3.  IANA Considerations\n\n   Section 2 provides IANA registration considerations.  These\n   considerations are not repeated here.\n\n   IANA has created the \"Extensions for the Extensible Provisioning\n   Protocol (EPP)\" registry [IANA-REG] to manage EPP extensions,\n   described in Section 2.  In the registry, IANA has replaced the\n   reference to [RFC7451] with a reference to this RFC and added a note\n   to explain that the early allocation policy defined in [RFC7120] does\n   not apply.  IANA has also changed the \"Document Status\" of all non-\n   RFC documents from \"Informational\" to \"Other\".\n\n4.  Security Considerations\n\n   This document introduces no new security considerations to EPP.\n   However, extensions should be evaluated according to the Security\n   Considerations of [RFC3735] (or its future replacement) and [STD69].\n\n5.  Operational Considerations\n\n   The updates defined in this document are meant to enhance the\n   guidance for reviewing EPP extensions (e.g., avoid non-IETF\n   specifications squatting on IETF XML namespaces) and thus allow for\n   better interoperability.\n\n   Section 2 includes provisions for modifying and deleting existing\n   registration entries by registrants.  Such requests may have\n   operational implications on other entities that deploy those\n   extensions.  Note that the registry does not include a history\n   mechanism and there is no way to track deleted entries once they have\n   been removed.\n\n   Section 3 updates the content of \"Document Status\" to be compliant\n   with the guidance in Section 2.  The update does not impact the\n   extension itself or induce any operational issues.\n\n6.  References\n\n6.1.  Normative References\n\n   [BCP79]    Best Current Practice 79,\n              <https://www.rfc-editor.org/info/bcp79>.\n              At the time of writing, this BCP comprises the following:\n\n              Bradner, S. and J. Contreras, \"Intellectual Property\n              Rights in IETF Technology\", BCP 79, RFC 8179,\n              DOI 10.17487/RFC8179, May 2017,\n              <https://www.rfc-editor.org/info/rfc8179>.\n\n   [STD69]    Internet Standard 69,\n              <https://www.rfc-editor.org/info/std69>.\n              At the time of writing, this STD comprises the following:\n\n              Hollenbeck, S., \"Extensible Provisioning Protocol (EPP)\",\n              STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,\n              <https://www.rfc-editor.org/info/rfc5730>.\n\n              Hollenbeck, S., \"Extensible Provisioning Protocol (EPP)\n              Domain Name Mapping\", STD 69, RFC 5731,\n              DOI 10.17487/RFC5731, August 2009,\n              <https://www.rfc-editor.org/info/rfc5731>.\n\n              Hollenbeck, S., \"Extensible Provisioning Protocol (EPP)\n              Host Mapping\", STD 69, RFC 5732, DOI 10.17487/RFC5732,\n              August 2009, <https://www.rfc-editor.org/info/rfc5732>.\n\n              Hollenbeck, S., \"Extensible Provisioning Protocol (EPP)\n              Contact Mapping\", STD 69, RFC 5733, DOI 10.17487/RFC5733,\n              August 2009, <https://www.rfc-editor.org/info/rfc5733>.\n\n              Hollenbeck, S., \"Extensible Provisioning Protocol (EPP)\n              Transport over TCP\", STD 69, RFC 5734,\n              DOI 10.17487/RFC5734, August 2009,\n              <https://www.rfc-editor.org/info/rfc5734>.\n\n   [RFC2026]  Bradner, S., \"The Internet Standards Process -- Revision\n              3\", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996,\n              <https://www.rfc-editor.org/info/rfc2026>.\n\n   [RFC2119]  Bradner, S., \"Key words for use in RFCs to Indicate\n              Requirement Levels\", BCP 14, RFC 2119,\n              DOI 10.17487/RFC2119, March 1997,\n              <https://www.rfc-editor.org/info/rfc2119>.\n\n   [RFC3688]  Mealling, M., \"The IETF XML Registry\", BCP 81, RFC 3688,\n              DOI 10.17487/RFC3688, January 2004,\n              <https://www.rfc-editor.org/info/rfc3688>.\n\n   [RFC3735]  Hollenbeck, S., \"Guidelines for Extending the Extensible\n              Provisioning Protocol (EPP)\", RFC 3735,\n              DOI 10.17487/RFC3735, March 2004,\n              <https://www.rfc-editor.org/info/rfc3735>.\n\n   [RFC5890]  Klensin, J., \"Internationalized Domain Names for\n              Applications (IDNA): Definitions and Document Framework\",\n              RFC 5890, DOI 10.17487/RFC5890, August 2010,\n              <https://www.rfc-editor.org/info/rfc5890>.\n\n   [RFC8126]  Cotton, M., Leiba, B., and T. Narten, \"Guidelines for\n              Writing an IANA Considerations Section in RFCs\", BCP 26,\n              RFC 8126, DOI 10.17487/RFC8126, June 2017,\n              <https://www.rfc-editor.org/info/rfc8126>.\n\n   [RFC8174]  Leiba, B., \"Ambiguity of Uppercase vs Lowercase in RFC\n              2119 Key Words\", BCP 14, RFC 8174, DOI 10.17487/RFC8174,\n              May 2017, <https://www.rfc-editor.org/info/rfc8174>.\n\n6.2.  Informative References\n\n   [RFC7120]  Cotton, M., \"Early IANA Allocation of Standards Track Code\n              Points\", BCP 100, RFC 7120, DOI 10.17487/RFC7120, January\n              2014, <https://www.rfc-editor.org/info/rfc7120>.\n\n   [RFC7451]  Hollenbeck, S., \"Extension Registry for the Extensible\n              Provisioning Protocol\", RFC 7451, DOI 10.17487/RFC7451,\n              February 2015, <https://www.rfc-editor.org/info/rfc7451>.\n\n   [IANA-REG] IANA, \"Extensions for the Extensible Provisioning Protocol\n              (EPP)\", <https://www.iana.org/assignments/epp-extensions>.\n\nAcknowledgements\n\n   The information described in the registry is based on a suggestion\n   posted to the provreg mailing list by Jay Daley in August 2013.  The\n   need to update [RFC7451] was first proposed by Gavin Brown.\n   Additional feedback for the update was provided by the following\n   people: Gavin Brown, James Galvin, James Gould, Pawel Kowalik, Andrew\n   Newton, and Jasdip Singh.\n\nAuthor's Address\n\n   Scott Hollenbeck\n   Verisign Labs\n   12061 Bluemont Way\n   Reston, VA 20190\n   United States of America\n   Email: sah@sahollenbeck.com\n   URI:   https://www.verisignlabs.com/\n","snippet":"","snippet_marked":"","source":"RFC Editor","citation":"https://www.rfc-editor.org/rfc/rfc10091","license":"IETF Trust / RFC Editor terms","year":"","url":"/record/10091","fields":{"status":"BEST CURRENT PRACTICE","stream":"IETF","wg":"regext","date":"November 2026","obsoletes":"RFC7451","updates":""}},"generated_at":"2026-11-22T20:18:34Z"}