On 10/17/24 08:05, Gould, James wrote:
Andy,
I'll provide a full review, but upon my initial review
draft-ietf-regext-rdap-x-media-type-02 still doesn't support the Extension
Version Identifier in draft-ietf-regext-rdap-versioning, following the ABNF:
extension-version-identifier = identifier versioning
identifier = ALPHA *( ALPHA / DIGIT / "_") ; Extension Identifer
versioning = ["-" 1*VCHAR]
The Extension Version Identifier needs to be unique from the Extension Identifier, which
is why the '-' separator is optionally used. All that is required in
draft-ietf-regext-rdap-x-media-type is to broaden the format of the
"extensions" values passed to include support for the Extension Version
Identifier. I provided a proposal in my prior feedback. I also don't believe the
behavior of draft-ietf-regext-rdap-x-media-type should be any different whether the
server is implementing draft-ietf-regext-rdap-versioning.
Sorry. I think I missed that. Yes, we need to be more specific about
that the version identification information, and I agree with you that
it should not change behavior.
I also see that we mistakenly say the version information is "prepended"
in Section 3.1.5. That needs to be corrected.
We should look to merge the two drafts, since
draft-ietf-regext-rdap-x-media-type is a subset of
draft-ietf-regext-rdap-versioning, and we need to ensure that there is full
compatibility.
With regard to the versioning draft, could we explore expanding the
scope of the metadata to include other server information, such as
server software version, server identification (similar to NSID), and
other information that can be used for debugging purposes? For those of
us who do troubleshooting of RDAP services, this would be very helpful.
-andy
_______________________________________________
regext mailing list -- regext@ietf.org
To unsubscribe send an email to regext-le...@ietf.org
