ISC, operator of the F-Root nameserver was recently made aware of draft-ietf-grow-unique-origin-as. After some discussion internally on the benefits and pitfalls of this method, as well as taking our own operational experience with the F-Root Anycast instance I drafted our thoughts into a blog post on our web site.
https://www.isc.org/community/blog/201109/origin-asn-anycasted-services The short version is that we don't feel this provides any added benefit over the method we currently use, but does come with a number of down sides. We would find it disappointing if this method further eroded the usefulness of inconsistent origin ASN reports, or caused increased routing table bloat. Further, given we don't see any benefits it is unlikely ISC would consider changing its current practice as a result of this draft. Note that I am not a member of the GROW mailing list. Feel free to reply to me directly or keep me CC'ed if you want discussion to remain on the GROW list. -- Leo Bicknell; E-mail: [email protected], Phone: +1 650 423 1358 INOC*DBA *3357*592; Internet Systems Consortium, Inc. www.isc.org
pgpapFdWCUPUA.pgp
Description: PGP signature
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
