Registration Protocols Extensions
|The information below is for an old version of the document
Registration Protocols Extensions WG
||Registration Protocols Extensions
Start Chartering/Rechartering (Internal IESG/IAB Review)
||Charter Edit AD
||Send notices to
The Extensible Provisioning Protocol (EPP, Standard 69) is the
standard domain name provisioning protocol for top-level domain name
registries. To avoid many separate EPP extensions that provide
the same functions, it's important to coordinate and standardize EPP
The EPP Extensions (EPPEXT) working group completed its first goal of
creating an IANA registry of EPP extensions. The registration process
of the registry is documented in RFC7451. Extensions may be
registered for informational purposes as long as there is a published
specification that has been reviewed by a designated expert.
The Registration Data Access Protocol (RDAP, RFCs 7480-7484) is the
proposed standard for retrieving registration metadata from both
domain name and Regional Internet Registries. To ensure interoperable
implementations it's important to coordinate and standardize
extensions and profiles to be used by registries.
Extensions in both cases that seek the status of Internet standard are
subject to more thorough review and open discussion within the IETF.
In addition, commonality may be discovered in related extensions,
especially EPP extensions listed on the EPP extension registry, for
which it would makes sense to merge them into a single standard
extension everybody agrees on.
The REGEXT working group is the home of the coordination effort for
standards track extensions. The selection of extensions for standards
track shall incorporate the following guidelines.
1. Proprietary documented extensions and individual submissions of
informational or experimental EPP extensions will follow the expert
review process as described in RFC7451 for inclusion in the EPP
extensions registry. These documents will not be part of the REGEXT
working group work or milestones. The working group may discuss or
advise on these documents.
2. Extensions that seek standards track status can be suggested for WG
adoption. If accepted by the working group then the development of
the standard may proceed.
3. The working group will exist as long as there is an extension
seeking standards track status. When there are no more proposals
for a standards track extension the working group will either close or
go dormant according to IETF rules. The mailing list will remain open
and available for the use of the expert review process as described in
The working group will also identify the requirements for a
registration protocol where a third-party DNS provider is involved.
These requirements will be documented in an Informational RFC.
The working group will focus initially on the backlog of EPP and RDAP