On 10/15/14, 6:04 PM, "Christopher Morrow" <[email protected]> wrote:
>> >>- A set of communities that indicate whether a prefix is a more specific >>that is covered by an aggregate and/or is safe to filter without loss of >>connectivity. >> > >so, add communities to global routes, because people don't strip these >in ingress as a matter of best practice? (if you don't you REALLY >should consider it, i think) Right.. Even if we could make the communities not be stripped (not proposing that), the originator would still not know the policy between any two ASNs ‹ not even the receive policy of its direct neighbor! So the originator still couldn¹t guarantee that the route is in fact covered. The only way to determine coverage and no connectivity loss is on the receive side. There you can look at the incoming routes and determine how the routes overlap and mark them appropriately according to local policy. http://tools.ietf.org/html/draft-white-grow-overlapping-routes Alvaro. _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
