Haven’t been (and won’t be) participating in this particular facet of the RSSAC Caucus, but…
On Oct 4, 2024, at 1:26 PM, Robert Story via rssac-caucus <rssac-caucus@icann.org> wrote:
https://www.icann.org/en/blogs/details/ghosts-of-root-servers-past-19-5-2008-en
While that story had a happy ending, it is a cautionary tale.
While that particular incident caused a certain amount of heartburn, gnashing of teeth, and (international diplomatic) silliness, I do honestly miss Bill.
FWIW, that event led me to suggest root server addresses should be treated as protocol elements, specified by RFC and assigned by IANA in
https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml, such that the addresses _never_ change. In the event of a root server operator changing, the IP addresses that root server uses would transfer to the new operator. That is (in today’s terms) while a root server operator is performing root service, they’d have a ROA for their AS in all 5 RIRs (since there isn’t an IANA RPKI TA) to announce the prefix containing the root server “golden” address they’re operating. Should they no longer provide that service, the golden address moves to the new root server operator (or gets AS0 null routed if that root server identity is no longer needed).
Taking into consideration the truly ridiculously long tail of "mis-directed” queries to old root server addresses, the root servers’ addresses unique position in the context of the functioning of the DNS (and, as a result, pretty much the Internet), and the risks entailed when the addresses do change and hence the uselessness of the old address essentially forever, I figured permanently fixing the addresses was a reasonable solution. Others disagreed and it was clear to me it wasn’t worth exploring at that time. Maybe it is now. Or maybe not.
Regards,
-drc