nanog mailing list archives
Re: HE.net BGP origin attribute rewriting
From: Saku Ytti <saku () ytti fi>
Date: Thu, 31 May 2012 20:06:46 +0300
On (2012-05-31 08:46 -0700), David Barak wrote:
On what precisely do you base the idea that a mandatory transitive attribute of a BGP prefix is a "purely advisory flag which has no real meaning"? I encourage you to reconsider that opinion - it's actually a useful attribute, much the way that MED is a useful attribute. Many providers re-write MED, and apparently some re-write ORIGIN. Neither of those is "network abuse" - it's more accurately described as "network routing policy." As has been stated here before: your network, your rules.
When provider rewrites MED, they do it, because they don't want peer to cause them to cold-potato, to which they may have compelling reason. Then some clever people realise they forgot to rewrite origin, working around the implicit agreement you had with them. -- ++ytti
Current thread:
- Re: HE.net BGP origin attribute rewriting, (continued)
- Re: HE.net BGP origin attribute rewriting Keegan Holley (May 31)
- Re: HE.net BGP origin attribute rewriting David Barak (May 31)
- Re: HE.net BGP origin attribute rewriting Keegan Holley (May 31)
- Re: HE.net BGP origin attribute rewriting Richard A Steenbergen (May 31)
- Re: HE.net BGP origin attribute rewriting Leo Bicknell (May 31)
- Re: HE.net BGP origin attribute rewriting Keegan Holley (May 31)
- Re: HE.net BGP origin attribute rewriting Steve Meuse (May 31)
- Re: HE.net BGP origin attribute rewriting Keegan Holley (May 31)
- Re: HE.net BGP origin attribute rewriting Nick Hilliard (May 31)
- Re: HE.net BGP origin attribute rewriting Nick Hilliard (May 31)
- Re: HE.net BGP origin attribute rewriting Saku Ytti (May 31)