Hi James, On Mon, Nov 13, 2023 at 03:02:34PM +0000, Jasdip Singh wrote: > On Thu, Nov 09, 2023 at 08:34:57PM +0000, Gould, James wrote: >> After the IETF-118 REGEXT meeting, I found this message that I >> never replied to. I believe that draft-ietf-regext-rdap-rir-search >> needs to fully follow the extension identifier as a prefix rule >> defined in RFC 7480, RFC 9082, and RFC 9083. I don’t support the >> concept of two classes of extensions (IETF and non-IETF), as >> defined in section 6 of draft-newton-regext-rdap-extensions. IETF >> extensions must not receive an exception to the rules defined in >> the RDAP RFCs (RFC 7480, RFC 9082, and RFC 9083), but instead must >> lead by example and fully follow the rules. >> >> If use of “ips” and “autnums” is the intent, then go with the >> second option that I provided: >> >> Define an identifier for “ips” and an identifier for “autnums”, >> which would be represented independently in the rdapConformance. >> >> There is no requirement to include the “_suffix”, so this will >> result in optimal path segment values (“ips” and “autnums”) and >> provides for separation by object. >> >> It looks like you may need a 3rd identifier with rir_search, as >> defined in section 3.2 of draft-ietf-regext-rdap-rir-search, if you >> decide not to go with a single extension identifier prefix such as >> “rir” that prefixes all of the extension path segments. >> >> I’ll leave the makeup of the extension identifiers and the path >> segments up to you, but the draft needs to follow the extension >> identifier as a prefix rule defined in RFC 7480, RFC 9082, and RFC >> 9083. > > Given the feedback during the regext session in Prague, we’ll > proceed with your suggestion of registering 2 additional extension > id’s – “ips” and “autnums” – beside “rir_search”.
Thanks for your feedback, the document has now been updated to suit (see https://author-tools.ietf.org/iddiff?url2=draft-ietf-regext-rdap-rir-search-04 for the diff). Does the current version address your concerns? -Tom _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
