i think the document is ready for adoption. This may make life easier for the client, but the server must now include more data in the response even if clients don’t care to use the Link headers For the next version maybe it would be nice to figure out how to make the Links header response optional for GET requests, maybe client does signaling using mime-type?
- Maarten Op 13 aug 2025, om 13:09 heeft Gavin Brown <gavin.br...@icann.org> het volgende geschreven: I should add that this document has previously been presented to the WG (in Dublin last year), where I feel it was well received. It has also been discussed on the list, and again I believe the discussion was positive. I am not aware of any objections to the WG taking this document on. Thanks, Gavin. On 12 Aug 2025, at 15:08, Gavin Brown <gavin.br...@icann.org> wrote: Greetings, I would like to ask the WG to consider adopting this document: http://datatracker.ietf.org/doc/draft-brown-rdap-referrals/ Many thanks for your consideration! G. -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org<https://www.icann.org/> _______________________________________________ regext mailing list -- regext@ietf.org<mailto:regext@ietf.org> To unsubscribe send an email to regext-le...@ietf.org<mailto:regext-le...@ietf.org>
_______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
