Hi Pawel, From: Pawel Kowalik <[email protected]> Date: Tuesday, December 16, 2025 at 2:08 PM To: Jasdip Singh <[email protected]>, Andy Newton <[email protected]>, [email protected] <[email protected]> Subject: Re: [regext] Re: I-D Action: draft-ietf-regext-rdap-extensions-09.txt
On 15.12.25 21:15, Jasdip Singh wrote: [snip PK2] "new required JSON member - this is typically valid for requests but not for responses, as "required" actually applies to the server not to the client. I would rather use "new JSON member which is critical to the client to properly understand the response”. [JS2] Yes, this is better. To further clarify, would “objectClassName” be considered such a critical member? [PK2] This for sure. This can be also other domain specific member. [JS3] Ack. Non-breaking: new JSON member, new query path, new query parameter, new HTTP header [PK] + New referral type [JS2] Right. By a new referral type, do you mean a new “rel” and “type” combination in a web link, or just the “type” in it? [PK2] Actually rfc9083 is not limiting "rel" anyhow and also is not even specifying what allowed values can be beyond what RFC8288 tells - meaning either registered types or extension types. I would say that from this perspective the client must be able to ignore anything unknown, because the registry of link types can be updated any time and extension types are open by definition. I may want to correct my previous feedback, that new referral type is actually not a breaking change. [JS3] IIUC, you had put it in the non-breaking category to start with. ;) With "type" I consider it even more relaxed, as "type" actually is only a hint about media type and should guide client whether the link is acceptable by the client as such. In this terms the clients are generally expected only to follow links with media type they know how to process and ignore others. However, if an extension is very specific about link types it delivers (like rfc9877 being specific about both "rel" and "type") one may consider that changing specification (like different "type") may be surprising to the clients. Adding new link type however shall still not be a problem. [JS3] That’s a good insight. Thanks for your feedback. Jasdip
_______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
