[153154] in North American Network Operators' Group
Re: HE.net BGP origin attribute rewriting
daemon@ATHENA.MIT.EDU (David Barak)
Thu May 31 11:48:10 2012
Date: Thu, 31 May 2012 08:46:46 -0700 (PDT)
From: David Barak <thegameiam@yahoo.com>
To: Nick Hilliard <nick@foobar.org>
In-Reply-To: <4FC77434.5000306@foobar.org>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Reply-To: David Barak <thegameiam@yahoo.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
=A0=0AFrom: Nick Hilliard <nick@foobar.org>=0A>If you don't rewrite your tr=
ansit providers' origin, then you are telling=0A>them that they can directl=
y influence your exit discrimination policy on=0A>the basis of a purely adv=
isory flag which has no real meaning.=A0 =0A=0AOn what precisely do you bas=
e the idea that a mandatory transitive attribute of a BGP prefix is a "pure=
ly advisory flag which has no real meaning"?=A0 I encourage you to reconsid=
er that opinion - it's actually a useful attribute, much the way that MED i=
s a useful attribute.=A0 Many providers re-write MED, and apparently some r=
e-write ORIGIN.=A0 Neither of those is "network abuse" - it's more accurate=
ly described as "network routing policy."=A0 As has been stated here before=
: your network, your rules.=0A=0A=A0=0ADavid Barak=0ANeed Geek Rock? Try Th=
e Franchise: =0Ahttp://www.listentothefranchise.com
