Hi, On Nov 15, 2012, at 12:57 AM, Jared Mauch <[email protected]> wrote:
> On Nov 14, 2012, at 6:52 PM, Nick Hilliard <[email protected]> wrote: > >> On 14/11/2012 22:18, Christopher Morrow wrote: >>> 1) What is a 'route leak' (perhaps the above draft identifies one >>> examplar to be used in that definition) >> >> dunno really. Some foo which involves prefixes being sent to places where >> they oughtn't have been sent to. This is possibly more of a legal / >> wordsmithing problem than anything else. > > I would say unexpected paths that appear as a result of poorly constructed > routing policies or software defaults and lax filtering policies. I'd define it as following: Route Leak: When a misconfigured BGP speaker sends an NLRI Update to another Autonomous System and subsequently becomes a potential transit network for the given NLRI while this transit service is not aligned with the routing policy between the two networks, the NLRI Update is considered a route leak. Kind regards, Job _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
