Registration Protocols Extensions (regext)
| WG | Name | Registration Protocols Extensions | |
|---|---|---|---|
| Acronym | regext | ||
| Area | Operations and Management Area (ops) | ||
| State | Active | ||
| Charter | charter-ietf-regext-03 Approved | ||
| Document dependencies | |||
| Additional resources |
GitHub Issue tracker Wiki Zulip stream |
||
| Personnel | Chairs | Antoin Verschuren, James Galvin, Jorge Cano | |
| Area Director | Mohamed Boucadair | ||
| Mailing list | Address | [email protected] | |
| To subscribe | https://www.ietf.org/mailman/listinfo/regext | ||
| Archive | https://mailarchive.ietf.org/arch/browse/regext/ | ||
| Chat | Room address | https://zulip.ietf.org/#narrow/stream/regext |
Charter for Working Group
The Extensible Provisioning Protocol (EPP, STD 69) is an application-layer client-server protocol for the provisioning and management of objects stored in a shared central repository. The Registration Data Access Protocol (RDAP, STD 95) is a protocol for retrieving registration data and metadata from both Domain Name Registries (DNRs) and Regional Internet Registries (RIRs).
The Registration Protocols Extensions Working Group (REGEXT WG) is responsible for maintenance and operations of both EPP and RDAP. Also, REGEXT provides practitioners, domain registries and registrars, number resources registries, and other interested parties who wish to share operational experience, challenges, and lessons learned, a venue to engage in discussions around the operational requirements of EPP and RDAP deployments.
Work Scope
The WG is responsible for specifying updates and extensions to these protocols (Standards Track or Experimental), documenting operational issues and specifying mitigations to those (Informational/Best Current Practice/Standards Track), providing guidance for defining extensions (Informational or Best Current Practice), and elaborating deployment recommendations (Informational or Best Current Practice). Also, the WG is responsible for maintenance of the registration procedures for the EPP and RDAP IANA registries.
Additionally, the WG will publish documents addressing interoperability issues related to EPP and RDAP. This includes, in particular:
- Data formats for exchanges between registration entities that need insertion or extraction using EPP or extraction using RDAP (Standards Track or Experimental).
- New application transport mappings for EPP following relevant and appropriate IETF standards to address operational gaps for which at least one domain registry and at least one domain registrar have made a commitment to deploy (Standards Track or Experimental).
- Best practices for the deployment and operation of EPP and RDAP, including security and scalability considerations (Informational or Best Current Practice).
The WG is responsible for the maintenance of RFC 3735 (Guidelines for Extending the Extensible Provisioning Protocol (EPP)), including progressing it from Informational to Best Current Practice.
Liaison and Coordination
The WG will follow existing BCPs (mainly BCP 56 on Building Protocols with HTTP) and will seek advice from the WIT area on HTTP and transport matters, in particular. Likewise, the WG will solicit feedback from other relevant WGs (e.g., DNSOP and SIDROPS) as needed.
The WG will discuss revisions of EPP and RDAP registration procedures with past and current Designated Experts for such registries to take into account their experience.
Milestones
| Date | Milestone | Associated documents |
|---|---|---|
| Sep 2026 | Submit for publication "Extensible Provisioning Protocol (EPP) Transport over HTTPS" |
draft-ietf-regext-epp-https
|
Done milestones
| Date | Milestone | Associated documents |
|---|---|---|
| Done | Submit for publication "Extensible Provisioning Protocol (EPP) Transport over QUIC" |
draft-ietf-regext-epp-quic
|