Registration Protocols Extensions (regext)
|WG||Name||Registration Protocols Extensions|
|Area||Applications and Real-Time Area (art)|
|Additional resources||Issue tracker, Wiki, Zulip stream|
|Personnel||Chairs||Antoin Verschuren, James Galvin|
|Area Director||Murray Kucherawy|
|Jabber chat||Room address||xmpp:firstname.lastname@example.org?join|
Charter for Working Group
Charter for Working Group
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 RFC 7451. 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 are targeted for the Standards Track 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 RFC 7451 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. When there are no more proposals for Standards-Track extensions,
the working group will either close or become dormant, with the
decision made in consultation with the responsible AD. In any case,
the mailing list will remain open and available for the use of the
expert review process as described in RFC 7451.
The working group may also take on work to develop specifications that
describe the following types of information exchanged between entities
involved in Internet identifier registration that are using the RDAP or
* Uniform representation formats for publishing local policy or
configuration options regarding EPP and RDAP use.
* Data formats for files exchanged between registration entities that
need insertion in or extraction from EPP or RDAP.
* Technical guidance for registration processes that are supported by
EPP or RDAP.
|May 2022||Submit for publication "Redacted Fields in the Registration Data Access Protocol (RDAP) Response"||
|Mar 2022||Submit for publication "Federated Authentication for the Registration Data Access Protocol (RDAP) using OpenID Connect"||
|Jan 2022||Submit for publication "Using JSContact in Registration Data Access Protocol (RDAP) JSON Responses"||
|Nov 2021||Submit for publication "Simple Registration Reporting"||
|Sep 2021||Submit for publication "Registration Data Access Protocol (RDAP) Reverse search capabilities"||
|Done||Submit for publication "Use of Internationalized Email Addresses in EPP protocol"||
|Done||Submit for publication "Finding the Authoritative Registration Data (RDAP) Service"||
|Done||Submit for publication "Registry Maintenance Notifications for the EPP"||
|Done||Submit for publication "Registration Data Access Protocol (RDAP) Query Format"||
|Done||Submit for publication "JSON Responses for the Registration Data Access Protocol (RDAP)"||
|Done||Submit for publication "EPP Unhandled Namespaces"||
|Done||Submit for publication "EPP Secure Authorization Information for Transfer"||
|Done||Submit for publication "Registration Data Access Protocol (RDAP) Query Parameters for Result Sorting and Paging"|
|Done||Submit for publication "Registration Data Access Protocol (RDAP) Partial Response"|
|Done||Submit for publication "Domain Name Registration Data (DNRD) Objects Mapping"||
|Done||Submit for publication "Registry Data Escrow Specification"||
|Done||Submit for publication "Login Security Extension for the Extensible Provisioning Protocol (EPP)"|
|Done||Submit for publication "EPP Domain Name Mapping Extension for Bundling Registration"|
|Done||Submit for publication "Change Poll Extension for EPP"|
|Done||Submit for publication "Registry Fee Extension for EPP"|
1 new milestone currently in Area Director review.