On 30-06-2026 4:51 AM, Mario Loffredo wrote:
[ML] Good. But what would be the suggested mechanism for signaling a non-breaking change ? Per Section 5.4.5, the versioning extension is mentioned as an example of a mechanism that allows clients to recognize a non-breaking change. Correct?
Yes. At least I think we are saying the same thing.
Additional suggested change: Section 5.4.1 OLD Removing a required protocol element from a response; NEW Removing a required protocol element from a response that has not yet been fully deprecated;
Is this really necessary? Why would a protocol element be in an extension if it was fully deprecated? Given your feedback, I have attempted to make 5.4 clearer. Here is the PR https://github.com/anewton1998/draft-regext-rdap-extensions/pull/85 Keep in mind that the I-D deadline is Monday, and I'd like to rev this before then. -andy _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
