nanog mailing list archives
Re: HE.net BGP origin attribute rewriting
From: Saku Ytti <saku () ytti fi>
Date: Fri, 1 Jun 2012 11:28:00 +0300
On (2012-06-01 10:19 +0200), Daniel Suchy wrote:
I think RFC 4271 (http://tools.ietf.org/html/rfc4271) is very clear here. Back to the standard, why condone it's violation? Yes, statement
It's extremely hard to find RFC which does not contain incorrect information or practically undeployable data. Many things if reading RFC anally are not standard compliant, like no one does IPv6 in the world and no one does MPLS VPNs etc. I'm repeating myself, but if you reset MED, you do it because you have reason why you do not allow peer to force you to cold-potato. There is little point in resetting MED and not resetting origin, as what you tried to stop from occurring still occurs. -- ++ytti
Current thread:
- Re: HE.net BGP origin attribute rewriting Daniel Suchy (Jun 01)
- Re: HE.net BGP origin attribute rewriting Saku Ytti (Jun 01)
- Accuracy of RFCs (was: Re: HE.net BGP origin attribute rewriting) John Curran (Jun 01)
- Re: HE.net BGP origin attribute rewriting Joe Provo (Jun 01)
- Re: HE.net BGP origin attribute rewriting Daniel Suchy (Jun 01)
- Re: HE.net BGP origin attribute rewriting Richard A Steenbergen (Jun 01)
- Re: HE.net BGP origin attribute rewriting Daniel Suchy (Jun 02)
- Re: HE.net BGP origin attribute rewriting Joe Provo (Jun 01)
- Re: HE.net BGP origin attribute rewriting Daniel Suchy (Jun 02)
- Re: HE.net BGP origin attribute rewriting Joe Provo (Jun 02)
- Re: HE.net BGP origin attribute rewriting Daniel Suchy (Jun 02)
- Re: HE.net BGP origin attribute rewriting Daniel Suchy (Jun 01)
- Re: HE.net BGP origin attribute rewriting Saku Ytti (Jun 01)