Hi drc,
On 5 Oct 2024, at 9:47 AM, David Conrad via rssac-caucus <rssac-caucus@icann.org> wrote:
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-specia..., 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).
"since there isn’t an IANA RPKI TA" I agree with you that these addresses are "special purpose" addresses and they should exist in the IANA Special Purpose Address Registries. But at that point why shouldn't IANA run its own RPKI TA and announce these and the other addresses that are listed in these registries? If the address is not globally routable it could issue a ROA with AS0. Otherwise it could announce ROAs with the relevant originating addresses. In my view, if these are addresses in an IANA registry then the RPKI structure should accurately reflect that. regards, Geoff