UTTARO, JAMES, ATTLABS wrote:
It seems that trading off the work that a PE has to do to parse the routes that have been sourced by itself needs to be weighed against the added complexity and additional work a RR must do to ensure that it does not send the routes back to said PE. I would guess that the RR would need to maintain multiple data structures associated with each client peer, have multiple update groups etc... The main point is which network device should do the work? My approach has always been to minimize the work on the RR as it is most important to the viability of the entire service/network.. The RR infrastructure is more critical and important than any single PE...
There's nothing special about that in the RR. It's the exact same mechanisms that any BGP speaker needs anyways.
Tony _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
