[regext] Re: draft-ietf-regext-rdap-x-media-type and draft-ietf-regext-rdap-versioning Compatibility Topic 1: Query Identifiers

[Jasdip Singh <[e-mail]>]

Hi,

One other takeaway from yesterday’s virtual meeting was that the proposed versioning scheme is intended to facilitate the RDAP draft authoring process. Would help to discuss if that’s something RDAP should support.

Thanks,
Jasdip

From: Pawel Kowalik <kowalik=[e-mail]>
Date: Tuesday, April 14, 2026 at 3:08 PM
To: Gould, James <jgould=[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>
Subject: [regext] Re: draft-ietf-regext-rdap-x-media-type and draft-ietf-regext-rdap-versioning Compatibility Topic 1: Query Identifiers


Jim,

I think it is just the secondary question being asked.

First we must clarify the relation between extension identifier, breaking/non-breaking changes and major/minor logic from the versioning draft.

In my opinion, extension identifier stands for stable extension interface and is therefore redundant to major logic from versioning draft.

After having clarified that we may discuss the question whether x-media-type shall allow signalling of versions.

Kind Regards,
Pawel

On 14.04.26 20:56, Gould, James wrote:

Pawel,

If you have other options or a preference with the options presented, it would be great to hear what you think.

Thanks,


--

JG



James Gould
Fellow Engineer
[e-mail]<mailto:[e-mail]> <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[e-mail]><mailto:applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[e-mail]>

703-948-3271
12061 Bluemont Way
Reston, VA 20190

Verisign.com <http://verisigninc.com/><http://verisigninc.com/>




On 4/14/26, 1:40 PM, "Pawel Kowalik" <kowalik=[e-mail]<mailto:kowalik=[e-mail]> <mailto:[e-mail]><mailto:[e-mail]>> wrote:


That means we are not talking about a choice between the two options
really, but whether draft-ietf-regext-rdap-versioning is well aligned
with the whole RDAP standard when it comes to breaking changes.


Kind Regards,
Pawel


On 14.04.26 17:55, Andy Newton wrote:


We definitely need an interim because the issues require
high-bandwidth conversation.

As we discussed in our virtual side meeting last night, the maturity
versioning introduces a problem where the extension identifier in the
rdapConformance array may not represent an extension understood by the
client because it can represent multiple versions of that extension,
even those with breaking changes. That is a fundamental problem that
goes against STD 95.

The maturity versioning, as I understand it, is also a break from the
semantic versioning that was previously in the draft and a break from
the discussion of simple major-minor versioning discussed in our side
meeting in Montreal.

-andy, no hats

On 14-04-2026 9:56 AM, Gould, James wrote:


For an action item from the IETF-125 REGEXT meeting, I setup a
meeting with the co-editors of draft-ietf-regext-rdap-x-media-type,
draft-ietf-regext-rdap-versioning, and
draft-ietf-regext-rdap-extensions to discuss compatibility across the
drafts. We only got to the first compatibility topic between
draft-ietf-regext-rdap-x-media-type and
draft-ietf-regext-rdap-versioning, which is called “Query
Identifiers”. Unfortunately, we couldn’t come to agreement on the
path forward for the “Query Identifiers” compatibility issue, so the
topic is being brought to the mailing list for discussion. An
interim meeting may be needed post discussion on the mailing list.
Problem:

Currently, draft-ietf-regext-rdap-x-media-type only supports the
passing of Extension Identifiers and not the Extension Version
Identifiers per “Figure 2: Versioning Query Parameter ABNF” of
draft-ietf-regext-rdap-versioning. The Extension Version Identifier
adds ["-" 1*( ALPHA / DIGIT / "." )] to the end of the Extension
Identifier, so additional structured version information can be
passed, such as
maturity_ext1-0.1. draft-ietf-regext-rdap-versioning supports both
Opaque Versioning, that uses Extension Identifiers, and Maturity
Versioning that uses Extension Version Identifiers, and there is a
normative reference to draft-ietf-regext-rdap-x-media-type with the
requirement for the server to support both the X-media Parameter in
draft-ietf-regext-rdap-x-media-type and the Query Parameter in
draft-ietf-regext-rdap-versioning. The ABNF in “Figure 2: Versioning
Query Parameter ABNF” of draft-ietf-regext-rdap-versioning is
incompatible with the description “whitespace-separated list of RDAP
extension identifiers (as would be found in the "rdapConformance"
array)” in draft-ietf-regext-rdap-x-media-type. NOTE – upon review
the reference to the “extensions” parameter in
draft-ietf-regext-rdap-versioning needs to be updated to the
“exts_lists” parameter.
Options:
1. X-media Parameter Equal to Query Parameter – The X-Media
Parameter can support the same features as the Versioning Query
Parameter by using the ABNF in Section 3.2.2 of
draft-ietf-regext-rdap-versioning. Both Opaque Version Identifiers
and Maturity Extension Version Identifiers can be passed via the
X-Media Parameter that equals what can be done with the Versioning
Query Parameter. Example is exts_list="maturity_ext1-0.1 opaque_ext2".
2. X-media Parameter Subset of Query Parameter - The X-Media
Parameter will only support the Extension Identifiers, where the
Maturity Extension Version Identifiers cannot be passed. Clients can
choose to use the Versioning Query Parameter to be able to specify
the MAJOR and MINOR version numbers of extensions supporting the
Maturity Versioning type. When using the X-Media Parameter, the
server will choose the default extension version of an extension
identifier supporting the Maturity Versioning type. Example is
exts_list="maturity_ext1 opaque_ext2", which would return the default
maturity_ext1 version “maturity_ext1-1.0”.
Please add any additional options to the list and let us know your
preference of the options to address the incompatibility. My personal
preference is option 1 “X-media Parameter Equal to Query Parameter”.
There are additional incompatibility topics between
draft-ietf-regext-rdap-x-media-type,
draft-ietf-regext-rdap-versioning, and
draft-ietf-regext-rdap-extensions that will be covered separately.

Thanks,



_______________________________________________
regext mailing list -- [e-mail]<mailto:[e-mail]> <mailto:[e-mail]><mailto:[e-mail]>
To unsubscribe send an email to [e-mail]<mailto:[e-mail]> <mailto:[e-mail]><mailto:[e-mail]>


_______________________________________________
regext mailing list -- [e-mail]<mailto:[e-mail]>
To unsubscribe send an email to [e-mail]<mailto:[e-mail]>