Hi James,
On 8/26/24 11:58, Gould, James wrote:
I have an issue with the “Query Parameters Considered Harmful” section
in draft-ietf-regext-rdap-x-media-type, where query parameters are
used in the base RDAP RFCs as well as other RDAP extensions including
the Versioning Extension. If use of query parameters should be
discouraged in RDAP, it should be moved from
draft-ietf-regext-rdap-x-media-type to
draft-ietf-regext-rdap-extensions. I personally don’t agree that the
use of query parameters in RDAP should be considered “harmful”, but it
can be pointed out in draft-ietf-regext-rdap-extensions that query
parameters may not be preserved via redirects. An author of an RDAP
extension that has the need for client input can take into
consideration that query parameters may not be presented via redirects
while creating the extension. I don’t view this as unique to the
passing of the desired set of extensions in the RDAP query.
I see your point here. That language should be changed because it is too
broad. I put an issue for that in the tracker [1]. Also, it needs to
point to the language in the rdap-extensions draft.
WRT to normative use of the versioning extension, I have a tracking
issue here [2].
-andy
[1]
https://github.com/anewton1998/draft-regext-ext-json-media-type/issues/30
[2]
https://github.com/anewton1998/draft-regext-ext-json-media-type/issues/31
_______________________________________________
regext mailing list -- regext@ietf.org
To unsubscribe send an email to regext-le...@ietf.org
