Hi, > I would like to issue last call for draft-ietf-grow-unique-origin-as-00. We > will close last call Jan 2nd 2011.
I have reviewed it and think it's a good idea. And some comments for [4. Addtional Reccomendations] network operators need official information about the anycasted network configuration such as a list of origin ASNs so that ops can avoid a rogue anycast node. An AS-SET in the IRRs or a web-site would be fine. A discrete set of peering ASNs for each anycast node is also helpful for downstream ASNs that receive a prefix of the anycasted node via their upstreams (sometimes peering ASNs of the anycasted node). And researchers who get BGP information from these downstreams are also happy with these information because they do not need an assumption of 'upstream-downstream' relationship. But this probably costs too much for ops of the anycasted services. :( ----- Matsuzaki Yoshinobu <[email protected]> - IIJ/AS2497 INOC-DBA: 2497*629 _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
