> From: William Herrin <[email protected]>
> If its practical for anycast to be an integral part of unicast routing
> then it's likely to be suboptimal or even destructive to architect it
> as a peer to unicast routing.
Anycast 'addresses' are service names. What we are doing, then, is using the
routing to route to service names.
This might be seen as good in the short term, but this kind of mixing of
fundamentally different functions in one mechanism is exactly the kind of
thing that, in the long run, can be a problem.
For one thing, it's a truism of system architecture that as a system gets
larger, mechanisms that are used to do two different things don't scale well.
For another, it makes the resulting system more rigid, less adaptable, etc,
etc.
Noel
_______________________________________________
rrg mailing list
[email protected]
http://www.irtf.org/mailman/listinfo/rrg
