On Fri, Mar 1, 2024 at 6:36 PM James Mitchell <james.mitch...@iana.org> wrote: > > 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. >
It does need clarification. > > > 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. > > I am not comprehending what you are asking with regard to non-existent entries. Can you elaborate? Also, if we are taking the time to fix up the matching logic, we should probably reword section 7 as well. -andy _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
