> Le 1 mars 2024 à 18:36, James Mitchell <james.mitch...@iana.org> a écrit : > > Hi all, > > Following a few off-list discussions, I’m going to hold on including the root > in the DNS bootstrap file at this time. > > The intention is to enable RDAP clients to be able lookup the contact > information for TLDs, as suggested or implied by the following sentence in > RFC9224, Section 4. > > The entry for the root of the domain name space is specified as "". > > However, a client following the matching text earlier in that section will > never match the root entry when there exists a TLD in the bootstrap file. > This is because the longest-match rules will have the query for “com” > matching the entry for “com”, and not the entry for “”. > > I’d say the matching logic is arguably incorrect – matching should begin with > the parent of the supplied domain name. However, I acknowledge this arguably > affects only queries for TLDs themselves, as a TLD’s RDAP server could > redirect down to a more specific registry where necessary.
The text for the longest match was intended for “typical” domain names. The sentence for the root was added late (if I remember well, near or during the weirds last call) in the draft that became RFC7484 but I guess nobody thought enough of the effect of the combination of both sentences. I wonder if we should say root is “.” And add a sentence about exact match of the root. Marc. > > A second consideration is that the root entry will match domains where there > is no published RDAP server for that TLD. This will affect the behaviour > described in RFC 9224, Section 7 Non-existent Entries or RDAP URL Values > provides. > > I’m interested in your thoughts to whether the matching logic needs updating, > and whether guidance or changes to the bootstrap file can reduce lookups for > “non-existent entries” to the root, e.g. publishing an empty RDAP URL for > delegated TLDs. > > James > > From: regext <regext-boun...@ietf.org <mailto:regext-boun...@ietf.org>> on > behalf of James Mitchell <james.mitch...@iana.org > <mailto:james.mitch...@iana.org>> > Date: Tuesday, February 20, 2024 at 11:42 AM > To: Marc Blanchet <marc.blanc...@viagenie.ca > <mailto:marc.blanc...@viagenie.ca>> > Cc: "regext@ietf.org <mailto:regext@ietf.org>" <regext@ietf.org > <mailto:regext@ietf.org>> > Subject: Re: [regext] [Ext] Re: Adding the DNS root to the bootstrap file > > Hi Marc, > > I’ll share a version of the bootstrap file in a few weeks, once the host is > globally reachable. > > Thanks, > James > > From: Marc Blanchet <marc.blanc...@viagenie.ca > <mailto:marc.blanc...@viagenie.ca>> > Date: Tuesday, February 20, 2024 at 6:40 AM > To: James Mitchell <james.mitch...@iana.org <mailto:james.mitch...@iana.org>> > Cc: "regext@ietf.org <mailto:regext@ietf.org>" <regext@ietf.org > <mailto:regext@ietf.org>> > Subject: [Ext] Re: [regext] Adding the DNS root to the bootstrap file > > > > > Le 19 févr. 2024 à 20:28, James Mitchell <james.mitch...@iana.org > <mailto:james.mitch...@iana.org>> a écrit : > > Hi all, > > IANA is planning to add the DNS root to the RDAP DNS bootstrap file. We do > not yet have a date for this change and are currently looking to understand > potential impact to RDAP clients. > > > Hi James, > Thanks for letting us know. > > <me as an RDAP mobile app developer> Would it be possible to share the > targeted file so that implementations can be tested against it before it goes > out? </me> > > Regards, Marc. > > > > Please reach out to me with any questions or comments. > > Note, the entry for the root of the domain name space is specified as "" [RFC > 9224]. > > Kind regards, > James Mitchell > IANA > _______________________________________________ > regext mailing list > regext@ietf.org <mailto:regext@ietf.org> > https://www.ietf.org/mailman/listinfo/regext [ietf.org] > <https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/regext__;!!PtGJab4!-RS9EOVBx9m9MdVNKWC1GUh_OVYkmjDd-CEa4IfEY9sOMDtXIAymNU_S-ACTTnrHaukjKFvlVlczd6riKCUdxN5j2SQJ2e6D4nWSPw$>
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
