REGEXT

IETF 125 Working Group Session

Summary

The REGEXT Working Group met to discuss the status of ongoing RDAP and EPP drafts, review technical updates to existing specifications, and evaluate new proposals for adoption. Key topics included the alignment of RDAP versioning and extension drafts, the transport of EPP over HTTPS/QUIC, and proposed fixes for the RDAP TTL extension. The chairs noted a significant number of documents are nearing completion or Working Group Last Call (WGLC).

Key Discussion Points

Document Status Updates

draft-ietf-regext-rdap-ttl-extension: Submitted to the IESG.
draft-ietf-regext-rdap-jscontact: Standard track conversion is complete. A minor nit identified by Martin (SIDN) will be fixed before WGLC.
draft-ietf-regext-epp-quic: James Gould reported that feedback from the QUIC working group has been addressed. The WG discussed whether to pair this with the HTTPS transport draft for WGLC.
RDAP Versioning and Extensions: James Gould, Andy Newton, Jasdip Singh, and Tom Harrison will meet to ensure compatibility between draft-ietf-regext-rdap-versioning, draft-ietf-regext-rdap-x-media-type, and draft-ietf-regext-rdap-extensions. The extensions draft is intended to progress first.
draft-ietf-regext-rdap-referrals: Gavin Brown noted that HTTP Directorate feedback is being incorporated. The draft significantly changes client-server interaction and requires more WG review before WGLC.
draft-ietf-regext-balance: Werner Staub has joined as a co-editor. New changes are expected in the -01 version.

RDAP RPKI Extension Update

Slide Deck: RDAP RPKI Extension Update

Presenter: Jasdip Singh
Technical Details: The -03 version includes renames for ASPA profiles, SHA-256/512 message digests for RPKI objects, and a new rdap-help link relation type to support hosted, delegated, and hybrid RPKI configurations.
Discussion: Rick Wilhelm queried the general utility of the rdap-help relation. Jasdip Singh and Andy Newton noted it follows the rdap- prefix convention suggested by Mark Nottingham to assist clients in identifying specific RDAP help resources.

EPP Transport over HTTPS

Slide Deck: draft-ietf-regext-epp-https

Presenter: Mario Loffredo
Technical Details: The discussion centered on BCP 56 compliance. The HTTP Directorate suggested mapping EPP directly to HTTP methods or using the CONNECT method. Authors argued that EPP is a stateful protocol and draft-ietf-regext-epp-https defines a transport mapping, not a new HTTP-native application.
Discussion: James Gould reported a productive meeting with Mark Nottingham, who appeared receptive to using HTTP as a transport for existing stateful protocols like EPP (similar to DoH). Andy Newton emphasized the need for registrar input. Mario Loffredo noted that .it has successfully used this implementation since 2009. Martin (SIDN) requested clearer documentation on the mapping between HTTP and EPP sessions.

RDAP Verified Contacts

Slide Deck: IETF 125 REGEXT Kowalik draft-loffredo-regext-rdap-verified-contacts

Presenter: Pavel Kalousek
Technical Details: The draft was updated to align with OpenID Connect (OIDC) verified claims. It introduces an array-based structure for claims, evidence types (e.g., ID card, utility statement), and verification methods (e.g., physical, remote).
Discussion: Gavin Brown cautioned against "extensible extensions" (arbitrary JSON objects) and suggested that the reorganization of JSON value registries should be handled in a separate document.

Updating RFC 9803 (RDAP TTL Extension)

Slide Deck: Updating RFC 9803

Presenter: Gavin Brown
Technical Details: An error was identified in the XML schema of RFC 9803 that prevents multiple custom resource records.
Discussion: A poll was taken regarding whether to change the namespace URI to ttl-1.1.
- Result: 12 in favor, 1 opposed (James Gould).
- James Gould argued the change was a minor fix for a "true mistake" and might not warrant a namespace roll.
- The WG reached a sense that while there is no immediate urgency, a bis document should be prepared.

Same Entity Set Support for EPP

Slide Deck: Same Entity Set Support for EPP

Presenter: Jim Galvin (participating as an individual)
Technical Details: The draft has been rewritten to use "Same Entity Set" terminology (replacing "variants") to encompass IDN variants and Latin diacritics. It relies on registry-defined policies for equivalence.
Discussion: James Gould requested the addition of XML schemas and concrete examples. Gavin Brown and Antoine Fressancourt discussed the implications of policy changes (e.g., changing the primary domain in a set). Jim Galvin noted that the current design assumes the primary domain is fixed once the set is created, largely to support IDN variant logic.

Decisions and Action Items

Decision: The WG will treat draft-ietf-regext-epp-quic and draft-ietf-regext-epp-https as a pair for WGLC unless the mailing list indicates a preference to split them.
Action Item: James Gould to ask the mailing list regarding the separation of the EPP-QUIC and EPP-HTTPS drafts.
Action Item: Document Shepherd (Gavin Brown) to capture the BCP 56 architectural justification in the shepherd write-up for draft-ietf-regext-epp-https.
Action Item: Gavin Brown to prepare a bis draft for RFC 9803 to address the XML schema error.

Next Steps

Adoption Calls: The chairs will issue calls for adoption on the mailing list for:
- draft-loffredo-regext-rdap-verified-contacts
- The updated proposal for Same Entity Set Support for EPP.
Working Group Last Calls: Pending minor nits and list consensus, WGLC is expected soon for:
- draft-ietf-regext-rdap-jscontact
- draft-ietf-regext-epp-quic
- draft-ietf-regext-rdap-rpki (after implementation status update).

Automatic IETF Minutes