On Sep 29, 2011, at 9:35 AM, Leo Bicknell wrote: > > Ok, fair enough. So let's ask the direct question: > > Would it not be even better then for them to have a unique origin > ASN, and publish the list of paths that originate the route, > achieving the same result without needing to have an inconsistent > origin?
With normal unicast there's a single tree for the prefix in the routing system, while anycasting inherently introduces a polytree for the prefix. However, anycasting with a common origin AS creates a 'pseudo AS' at the root of the graph (i.e., the illusion of a single tree). By doing what you describe, you force anyone doing routing system analysis to know 'a priori' which prefixes employ a pseudo AS at the root of the tree - only so that they can step deeper into the tree, to the actual polytree roots, and then evaluate the adjacent nodes of those roots. This is particularly problematic when new nodes are introduced to the system. I don't see how this is simpler. -danny _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
