Extension Registry for the Extensible Provisioning Protocol

Extension Specification and Registration Procedure This section describes the format of an IANA registry and the procedures used to populate and manage registry entries.

Extension Specification This registry uses the "Specification Required" policy described in RFC 8126 . An English language version of the extension specification will be referenced from the registry, though non- English versions of the specification may also be provided. Note that Section 2.1 of RFC 3735 provides specific guidelines for documenting EPP extensions. Note that the "Specification Required" policy requires review by a "designated expert". Section 5 of RFC 8126 describes the role of designated experts and the function they perform. This policy also requires "a permanent and readily available public specification". RFC documents meet that requirement. Proprietary specifications may meet that requirement, depending on how they are archived and accessible. Internet-Draft documents do not meet that requirement. RFC 2026 notes that "Internet-Drafts have no formal status, and are subject to change or removal at any time".

Designated Expert Evaluation Criteria A high-level description of the role of the designated expert is described in Section 5.2 of RFC 8126 . Specific guidelines for the appointment of designated experts and the evaluation of EPP extensions are provided here. The IESG should appoint a small pool of individuals (perhaps 3 - 5) to serve as designated experts, as described in Section 5.2 of RFC 8126 . The pool should have a single administrative chair who is appointed by the IESG. The designated experts should use the existing regext mailing list (regext@ietf.org) or its successor for public discussion of registration requests. Extensions should be evaluated for architectural soundness using the guidelines described in RFC 3735 , including the Security Considerations section of that document. Expert evaluation should explicitly include consideration of the privacy consequences of proposed extensions, and, at a minimum, ensure that any privacy considerations are fully documented in the relevant specification(s). URIs proposed in extensions (XML namespace and schema registration requests are commonly found in EPP extensions) should be evaluated for both syntactic and semantic correctness. XML schema and namespace URIs must be registered in the IETF XML Registry using the procedures described in RFC 3688 . IETF namespaces must be reserved for IETF specifications. Non-IETF namespaces must be used for non-IETF specifications; the designated experts may need to work with a registrant to identify URIs that can be added to the IETF XML Registry. Extensions and any normative reference necessary to implement the extension must not be denoted with "work in-progress" or any similar description. The results of the evaluation should be shared via email with the registrant and the regext mailing list. Issues discovered during the evaluation can be corrected by the registrant, and those corrections can be submitted to the designated experts until the designated experts explicitly decide to accept or reject the registration request. The designated experts must make an explicit decision and that decision must be shared via email with the registrant and the regext mailing list. If the specification for an extension is an IETF Standards Track document, no review is required by the designated expert. Designated experts should be permissive in their evaluation of requests to register extensions that have been implemented and deployed by at least one registry/registrar pair. This implies that it may indeed be possible to register multiple extensions that provide the same functionality. Requests to register extensions that have not been deployed should be evaluated with a goal of reducing functional duplication. A potential registrant who submits a request to register a new, un-deployed extension that includes similar functionality to an existing, registered extension should be made aware of the existing extension. The registrant should be asked to reconsider their request given the existence of a similar extension. Should they decline to do so, perceived similarity should not be a sufficient reason for rejection as long as all other requirements are met.

Registration Procedure The registry contains information describing each registered extension. Registry entries are created and managed by sending forms to IANA that describe the extension and the operation to be performed on the registry entry.

Required Information Name of Extension: A case-insensitive, ASCII text string that contains the name of the extension specification. Non-ASCII representations of the extension name can be included in the "Notes" described below. Document Status: The document status of the specification document. For RFC documents, the possible set of values includes "Standards Track", "Informational", "Experimental", "Historic", and "BCP" as described in Sections 4 and 5 of RFC 2026 . For documents that are not RFCs, this will always be "Other". Reference: A permanent, publicly available reference to the specification of this extension. This could be an RFC number or some other pointer to the document defining the extension that meets the "Specification Required" registry policy. Registrant Name and Email Address: The name and email address of the person that is responsible for managing the registry entry. If the registration is of an IETF Standards Track extension, this can simply be listed as "IESG, <iesg@ietf.org>". TLDs: A text string containing the top-level domain name (or domain names), including the preceding ".", for which the extension has been specified (e.g., ".org"). If there are multiple TLDs, they are given as a list of domain names separated by commas, (e.g. ".com", ".net"). Internationalized Domain Name (IDN) TLDs should be specified in A-label format. If the extension is not associated with a specific top-level domain, the case-insensitive text string "Any" can be used to indicate that. IPR Disclosure: A pointer to any Intellectual Property Rights (IPR) disclosure document(s) related to this extension, or "None" may be used if there are no such disclosures. This can be an IPR disclosure filed with the IETF in accordance with RFC 3979 as updated by RFC 4879 if the extension is part of an IETF Contribution, or it can be other IPR disclosure documents identifying the claimed intellectual property rights and terms of use for extensions that are not part of an IETF Contribution. Status: Either "Active" or "Inactive". The "Active" status is used for extensions that are currently implemented and in use. The "Inactive" status is used for extensions that are not implemented or are otherwise not being used. Notes: Either "None" or other text that describes optional notes to be included with the registered extension. If the Status value is "Inactive", text should be included to describe how and when this state was reached.

Registration Form The required information must be formatted consistently using the following registration form. Form field names and values may appear on the same line. (quotes are optional) Document Status: Reference: Registrant Name and Email Address: ,

TLDs: "Any"| IPR Disclosure: "None"| Status: "Active"|"Inactive" Notes: "None"| -----END FORM----- Example form with RFC specification: -----BEGIN FORM----- Name of Extension: "An Extension RFC for the Extensible Provisioning Protocol (EPP)" Document Status: Standards Track Reference: RFC XXXX Registrant Name and Email Address: IESG, TLDs: Any IPR Disclosure: None Status: Active Notes: None -----END FORM----- Example form with non-RFC specification: -----BEGIN FORM----- Name of Extension: "An Example Extension for the .example Top-Level Domain" Document Status: Other Reference: http://www.example.com/html/example-epp-ext.txt Registrant Name and Email Address: John Doe, jdoe@example.com TLDs: .example IPR Disclosure: http://www.example.com/ipr/example-epp-ext-ipr.html Status: Active Notes: None -----END FORM----- ]]>

Registration Processing Registrants should send each registration form to IANA with a single record for incorporation into the registry. Send the form via email to <iana@iana.org> or complete the online form found on the IANA web site. The subject line should indicate whether the enclosed form represents an insertion of a new record (indicated by the word "INSERT" in the subject line), replacement of an existing record (indicated by the word "MODIFY" in the subject line), deactivation of an existing record (indicated by the word "DEACTIVATE" in the subject line), or removal of an existing record (indicated by the word "REMOVE" in the subject line). Records in this registry may only be removed or deactivated with IESG Approval (see ). On receipt of a registration request, IANA will initiate review by the designated expert(s), who will evaluate the request using the criteria in in consultation with the current working group mailing list focused on the development of EPP extensions.

Updating Registry Entries When submitting changes to existing registry entries, include text in the "Notes" field of the registration form describing the change. Under normal circumstances, registry entries are only to be updated by the registrant. If the registrant becomes unavailable or otherwise unresponsive, the designated expert can submit a registration form to IANA to update the registrant information. Entries can change state from "Active" to "Inactive" and back again as long as state-change requests conform to the processing requirements identified in this document. In addition to entries that become "Inactive" due to a lack of implementation, entries for which a specification becomes consistently unavailable over time should be marked "Inactive" by the designated expert until the specification again becomes reliably available.