Hi both, The next version will mirror the text in Section 5.2 of RFC 7480.
Thanks, G. > On 17 Dec 2025, at 6:45 am, Pawel Kowalik <[email protected]> wrote: > > Hi Gavin, > To the same topic I was wondering what is the rationale to narrow down the > choice specified in 5.2 of 7480? > Kind Regards, > Pawel > On 16.12.25 23:53, Jasdip Singh wrote: >> Gavin, I do recall section 5.2 on redirects from RFC 7480 which mentions >> 301, 302, 303, and 307 but not 308. Nonetheless, thought of asking if it >> would be safer with 307 and 308 here. >> >> Jasdip >> >> From: Jasdip Singh <[email protected]> >> Date: Tuesday, December 16, 2025 at 4:46 PM >> To: Gavin Brown <[email protected]>, [email protected] <[email protected]> >> Cc: [email protected] <[email protected]> >> Subject: [regext] Re: [Ext] I-D Action: >> draft-ietf-regext-rdap-referrals-01.txt >> >> Hi Gavin, >> >> Wouldn’t it be safer to return 307 (Temporary Redirect) instead of 302 >> (Found), and 308 (Permanent Redirect) instead of 301 (Moved Permanently), >> since RDAP only allows the GET method and we don’t want the server altering >> that method when redirecting? >> >> (Please ignore in case I missed the rationale for choosing 301 and 302 here. >> :)) >> >> Jasdip >> >> From: Gavin Brown <[email protected]> >> Date: Tuesday, December 16, 2025 at 9:06 AM >> To: [email protected] <[email protected]> >> Cc: [email protected] <[email protected]> >> Subject: [regext] Re: [Ext] I-D Action: >> draft-ietf-regext-rdap-referrals-01.txt >> >> Greetings, >> >> As discussed during the meeting in Montreal, here is an updated version of >> the RDAP referrals draft, which switches to a path-based approach. >> >> This draft also discusses how the server selects *which* link to use when >> providing the referral, which was one of the open items that we presented on. >> >> Feedback greatly appreciated! >> >> Thanks, >> >> Gavin. >> >> > On 16 Dec 2025, at 13:43, [email protected] wrote: >> > >> > Internet-Draft draft-ietf-regext-rdap-referrals-01.txt is now available. >> > It is >> > a work item of the Registration Protocols Extensions (REGEXT) WG of the >> > IETF. >> > >> > Title: Efficient RDAP Referrals >> > Authors: Gavin Brown >> > Andy Newton >> > Name: draft-ietf-regext-rdap-referrals-01.txt >> > Pages: 7 >> > Dates: 2025-12-16 >> > >> > Abstract: >> > >> > This document describes an RDAP extension that allows RDAP clients to >> > request to be referred to a related RDAP record for a resource. >> > >> > The IETF datatracker status page for this Internet-Draft is: >> > https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-referrals/ >> > >> > There is also an HTML version available at: >> > https://www.ietf.org/archive/id/draft-ietf-regext-rdap-referrals-01.html >> > >> > A diff from the previous version is available at: >> > https://author-tools.ietf.org/iddiff?url2=draft-ietf-regext-rdap-referrals-01 >> > >> > Internet-Drafts are also available by rsync at: >> > rsync.ietf.org::internet-drafts >> > >> > >> > _______________________________________________ >> > regext mailing list -- [email protected] >> > To unsubscribe send an email to [email protected] >> >> -- >> Gavin Brown >> Principal Engineer, Global Domains & Strategy >> Internet Corporation for Assigned Names and Numbers (ICANN) >> >> https://www.icann.org >> >> _______________________________________________ >> regext mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> >> _______________________________________________ >> regext mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
