Hi,
Section 5.4 cites MNOT-VERSIONING and lists two general principles for
versioning RDAP extensions. I suggest adding a third principle that
captures the granularity aspect of the referenced guidance:
* The impact of a change should be limited to the RDAP extension
feature, protocol element, or resource whose semantics are being
changed; unrelated features of the same RDAP extension should not
be versioned or replaced solely because of that change.
AFAIU, MNOT-VERSIONING argues against applying versioning to a whole web
API surface when the actual change is local. It notes that putting a
version identifier into a URI causes even minor changes to mint an
entire new set of resources, with consequences for caches, links, and
deployed clients. It also gives a more granular example:
"/rather than bumping a version when you want to modify how a resource
handles query parameters, you mint a new, sibling resource with a
different name that takes the alternate query parameters./"
I believe this principle is especially relevant to RDAP extensions,
because Section 5.4 already defines compatibility in terms of specific
protocol elements, such as JSON names and values, query paths and
parameters, and other.
Therefore, the draft should make clear that the impact of a change ought
to be limited to the affected extension feature, and should not
unnecessarily force unrelated features of the extension to be versioned
or replaced.
Also, here are two small typos:
1) Add commas to separate the values of the array below:
"description":
[
"Query the database."
"JSON replaces the Whois."
"Structured data flows."
]
2) Add a closing curly brace as shown below
{
"rdapConformance": [
"rdap_level_0",
"exampleExt"
],
"exampleExt_authorSearchResult": [
{
"objectClassName": "exampleExt_author",
"author":
{
"firstInitial": "R",
"lastName": "SomePerson"
}
},
{
"objectClassName": "exampleExt_author",
"author":
{
"firstInitial": "J",
"lastName": "SomePerson"
}
<=== put aclosing curly bracket here
]
]
}
Best,
Mario
Il 06/07/2026 13:06, [email protected] ha scritto:
Internet-Draft draft-ietf-regext-rdap-extensions-14.txt is now available. It
is a work item of the Registration Protocols Extensions (REGEXT) WG of the
IETF.
Title: RDAP Extensions
Authors: Andy Newton
Jasdip Singh
Tom Harrison
Name: draft-ietf-regext-rdap-extensions-14.txt
Pages: 33
Dates: 2026-07-06
Abstract:
This document describes and clarifies the usage of extensions in
RDAP.
The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-extensions/
There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-regext-rdap-extensions-14.html
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-regext-rdap-extensions-14
Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts
_______________________________________________
regext mailing list [email protected]
To unsubscribe send an email [email protected]
--
Dott. Mario Loffredo
Senior Technologist
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
Address: Via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web:http://www.iit.cnr.it/mario.loffredo
_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]
