I think you mean paths with valleys are all instances of unintended routing.
Surely, that can be fixed:
A provider can reject valleyed routes from a customer BY DEFAULT,
but allow some through if so configured.
The point is that such a valley attribute can provide good information to
prevent
On Fri, Nov 22, 2013 at 6:40 PM, Jakob Heitz jakob.he...@ericsson.com wrote:
I think you mean paths with valleys are all instances of unintended routing.
Surely, that can be fixed:
A provider can reject valleyed routes from a customer BY DEFAULT,
but allow some through if so configured.
The
On 23 Nov 2013, at 10:40 am, Jakob Heitz jakob.he...@ericsson.com wrote:
I think you mean paths with valleys are all instances of unintended routing.
sorry, yes, that is what I meant to say! :-)
geoff
___
sidr mailing list
sidr@ietf.org
On 23 Nov 2013, at 1:17 pm, Geoff Huston g...@apnic.net wrote:
On 23 Nov 2013, at 10:40 am, Jakob Heitz jakob.he...@ericsson.com wrote:
I think you mean paths with valleys are all instances of unintended
routing.
sorry, yes, that is what I meant to say! :-)
and lest this be
is this a default-on property? or do I configure bgp-peer-A as 'i am a
customer' and peer-b as 'I am a transit'?
that can vary by prefix
randy
___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr
