On Fri, Jan 31, 2025 at 7:37 AM Marc Blanchet <marc.blanc...@viagenie.ca> wrote: > > > > On Jan 31, 2025, at 06:20, Gavin Brown <gavin.br...@icann.org> wrote: > > > > Greetings, > > > > I am seeking the wisdom of the WG on the following. > > > > Section 4 of RFC 9224 states that: (a) "the domain name's authoritative > > registration data service is found by doing the label-wise longest match of > > the target domain name", and also that (b) "the entry for the root of the > > domain name space is specified as "".". > > > > The upshot of this is that if IANA were to add an entry for the root to the > > bootstrap file, RDAP clients that implement RFC 9224 would hit the IANA > > server for *all* queries for domains under TLDs that haven't added their > > base URL to the bootstrap file. As of writing, that's about 25% of all > > registered domains[1]. I believe that this has significant implications on > > the privacy of user queries, in addition to the operational impact it would > > have on IANA.
IMHO, there is a difference between "send all your queries for any domain name for which there is no authoritative server to this URL" and "send all your queries about the root zone to this URL". Some other things to note here: 1. There is no such provision for "send all your queries for IP addresses for which there is no authoritative server to this URL" (or for ASNs). 2. If a client is given "com", the label-wise longest match will be the .com registry which responds with a 404. In the icann-rdap-cli I compensate for this with a special lookup for TLDs that goes to IANA [1] because there is a difference between asking .com about itself and asking IANA about .com. -andy [1] https://github.com/icann/icann-rdap/wiki/RDAP-command#directing-queries-to-a-specific-server _______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
