Registration Protocols Extensions (regext) Internet Drafts


      
 Federated Authentication for the Registration Data Access Protocol (RDAP) using OpenID Connect
 
 draft-ietf-regext-rdap-openid-27.txt
 Date: 05/11/2023
 Authors: Scott Hollenbeck
 Working Group: Registration Protocols Extensions (regext)
The Registration Data Access Protocol (RDAP) provides "RESTful" web services to retrieve registration metadata from domain name and regional internet registries. RDAP allows a server to make access control decisions based on client identity, and as such it includes support for client identification features provided by the Hypertext Transfer Protocol (HTTP). Identification methods that require clients to obtain and manage credentials from every RDAP server operator present management challenges for both clients and servers, whereas a federated authentication system would make it easier to operate and use RDAP without the need to maintain server-specific client credentials. This document describes a federated authentication system for RDAP based on OpenID Connect.
 Using JSContact in Registration Data Access Protocol (RDAP) JSON Responses
 
 draft-ietf-regext-rdap-jscontact-17.txt
 Date: 07/12/2023
 Authors: Mario Loffredo, Gavin Brown
 Working Group: Registration Protocols Extensions (regext)
This document describes an RDAP extension which represents entity contact information in JSON responses using JSContact.
 Use of Internationalized Email Addresses in the Extensible Provisioning Protocol (EPP)
 
 draft-ietf-regext-epp-eai-20.txt
 Date: 06/11/2023
 Authors: Dmitry Belyavsky, James Gould
 Working Group: Registration Protocols Extensions (regext)
This document describes an EPP command-response extension that permits usage of Internationalized Email Addresses in the EPP protocol and specifies the terms when it can be used by EPP clients and servers. The Extensible Provisioning Protocol (EPP), being developed before the standards for SMTPUTF8 compliant addresses, does not support such email addresses. TO BE REMOVED on turning to RFC: The document is edited in the dedicated github repo (https://github.com/beldmit/eppeai). Please send your submissions via GitHub.
 Versioning in the Registration Data Access Protocol (RDAP)
 
 draft-gould-regext-rdap-versioning-02.txt
 Date: 08/12/2023
 Authors: James Gould, Dan Keathley, Mario Loffredo
 Working Group: Registration Protocols Extensions (regext)
This document describes an RDAP extension for an extensible set of versioning types with the features of identifying the RDAP extension versions supported by the server, the RDAP extension versions included in an RDAP response, and enabling a client to specify the desired RDAP extension versions to include in the RDAP query and RDAP response.
 RDAP RIR Search
 
 draft-ietf-regext-rdap-rir-search-09.txt
 Date: 24/03/2024
 Authors: Tom Harrison, Jasdip Singh
 Working Group: Registration Protocols Extensions (regext)
The Registration Data Access Protocol (RDAP) is used by Regional Internet Registries (RIRs) and Domain Name Registries (DNRs) to provide access to their resource registration information. The core specifications for RDAP define basic search functionality, but there are various IP and ASN-related search options provided by RIRs via their Whois services for which there is no corresponding RDAP functionality. This document extends RDAP to support those search options.
 Extensible Provisioning Protocol (EPP) mapping for DNS Time-To-Live (TTL) values
 
 draft-ietf-regext-epp-ttl-08.txt
 Date: 16/04/2024
 Authors: Gavin Brown
 Working Group: Registration Protocols Extensions (regext)
This document describes an extension to the Extensible Provisioning Protocol (EPP) that allows EPP clients to manage the Time-To-Live (TTL) value for domain name delegation records. About this draft This note is to be removed before publishing as an RFC. The source for this draft, and an issue tracker, may can be found at https://github.com/gbxyz/epp-ttl-extension.
 An RDAP Extension for Geofeed Data
 
 draft-ietf-regext-rdap-geofeed-05.txt
 Date: 19/04/2024
 Authors: Jasdip Singh, Tom Harrison
 Working Group: Registration Protocols Extensions (regext)
This document defines a new Registration Data Access Protocol (RDAP) extension, "geofeed1", for indicating that an RDAP server hosts geofeed URLs for its IP network objects. It also defines a new media type and link relation type for the associated link objects included in responses.
 Best Practices for Deletion of Domain and Host Objects in the Extensible Provisioning Protocol (EPP)
 
 draft-ietf-regext-epp-delete-bcp-01.txt
 Date: 28/02/2024
 Authors: Scott Hollenbeck, William Carroll, Gautam Akiwate
 Working Group: Registration Protocols Extensions (regext)
The Extensible Provisioning Protocol (EPP) includes commands for clients to delete domain and host objects, both of which are used to publish information in the Domain Name System (DNS). EPP includes guidance concerning those deletions that is intended to avoid DNS resolution disruptions and maintain data consistency. However, operational relationships between objects can make that guidance difficult to implement. Some EPP clients have developed operational practices to delete those objects that have unintended impacts on DNS resolution and security. This document describes best practices to delete domain and host objects that reduce the risk of DNS resolution failure and maintain client-server data consistency.
 Versioning in the Registration Data Access Protocol (RDAP)
 
 draft-ietf-regext-rdap-versioning-00.txt
 Date: 27/02/2024
 Authors: James Gould, Dan Keathley, Mario Loffredo
 Working Group: Registration Protocols Extensions (regext)
This document describes an RDAP extension for an extensible set of versioning types with the features of identifying the RDAP extension versions supported by the server, the RDAP extension versions included in an RDAP response, and enabling a client to specify the desired RDAP extension versions to include in the RDAP query and RDAP response.
 An RDAP With Extensions Media Type
 
 draft-ietf-regext-rdap-x-media-type-00.txt
 Date: 27/02/2024
 Authors: Andy Newton, Jasdip Singh
 Working Group: Registration Protocols Extensions (regext)
This document defines a media type for RDAP that can be used to describe RDAP content with RDAP extensions. Additionally, this document describes the usage of this media type with RDAP.
 RDAP Extensions
 
 draft-ietf-regext-rdap-extensions-00.txt
 Date: 27/02/2024
 Authors: Andy Newton, Jasdip Singh, Tom Harrison
 Working Group: Registration Protocols Extensions (regext)
This document describes and clarifies the usage of extensions in RDAP.


data-group-menu-data-url="/group/groupmenu.json"> Skip to main content

Registration Protocols Extensions (regext)

WG Name Registration Protocols Extensions
Acronym regext
Area Applications and Real-Time Area (art)
State Active
Charter charter-ietf-regext-02 Approved
Document dependencies
Additional resources Issue tracker, Wiki, Zulip stream
Personnel Chairs Antoin Verschuren, James Galvin
Area Director Orie Steele
Mailing list Address regext@ietf.org
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

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
extensions.

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
EPP protocols:

  • 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.

Milestones

Date Milestone Associated documents
May 2024 Submit for publication "Extensible Provisioning Protocol (EPP) mapping for DNS Time-To-Live (TTL) values" draft-ietf-regext-epp-ttl
Mar 2024 Submit for publication "RDAP RIR Search" draft-ietf-regext-rdap-rir-search
Jun 2023 Submit for publication "DNS Data Dictionary" draft-ietf-regext-datadictionary
Mar 2023 Submit for publication "Using JSContact in Registration Data Access Protocol (RDAP) JSON Responses" draft-ietf-regext-rdap-jscontact

Done milestones

Date Milestone Associated documents
Done Submit for publication "Federated Authentication for the Registration Data Access Protocol (RDAP) using OpenID Connect" draft-ietf-regext-rdap-openid
Done Submit for publication "Registration Data Access Protocol (RDAP) Reverse search capabilities" draft-ietf-regext-rdap-reverse-search
Done Submit for publication "Redacted Fields in the Registration Data Access Protocol (RDAP) Response" draft-ietf-regext-rdap-redacted
Done Submit for publication "Use of Internationalized Email Addresses in EPP protocol" draft-ietf-regext-epp-eai
Done Submit for publication "Finding the Authoritative Registration Data (RDAP) Service" draft-ietf-regext-rfc7484bis
Done Submit for publication "Registry Maintenance Notifications for the EPP" draft-ietf-regext-epp-registry-maintenance
Done Submit for publication "Registration Data Access Protocol (RDAP) Query Format" draft-ietf-regext-rfc7482bis
Done Submit for publication "JSON Responses for the Registration Data Access Protocol (RDAP)" draft-ietf-regext-rfc7483bis
Done Submit for publication "EPP Unhandled Namespaces" draft-ietf-regext-unhandled-namespaces
Done Submit for publication "EPP Secure Authorization Information for Transfer" draft-ietf-regext-secure-authinfo-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" draft-ietf-regext-dnrd-objects-mapping
Done Submit for publication "Registry Data Escrow Specification" draft-ietf-regext-data-escrow
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"

2 new milestones currently in Area Director review.