Hi Dessalegn,
While I am emailing from my personal email address for this response, let's assume for this response only, I am wearing my ICANN hat as the person who is responsible for the ICANN Managed Root Server (IMRS), otherwise known technically as
L.ROOT-SERVERS.NET.
We are well aware of the publication of Code BGP regarding the presumed routing anomaly. We are actively working with the entity involved (one of our IMRS hosts) as to why the routing advertisement is as reported. (noting also this particular route has an ASPATH of 10 ASs due to prepending, and effectively it us unlikely to be the selected path)
I'd also like to point out that Code BGP has a tendency to report first, and investigate later. You can of course interpret that how you will.
That said because it is an IMRS host that is involved there is actually no impact to Root DNS service and I suspect this is a zero impact routing artefact that can be trivially rectified with education.
Cheers,
Terry
--
Mobile device, don't expect grammar.
This might be of interest.
Kind regards,
Dessalegn
_______________________________________________rssac-caucus mailing listrssac-caucus@icann.orghttps://mm.icann.org/mailman/listinfo/rssac-caucus_______________________________________________By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
_______________________________________________