Upstream BGP community support

Jimmy Changa jimmy.changa007 at
Fri Jun 4 06:03:43 UTC 2010

Has anyone seen movement from HE on community support yet? I've heard
rumblings that they are looking to do something Q3/Q4 but my sales guy is
telling me that they will only support it if I go to a full 10Gb pipe.
Sounds more like an aggressive sales tactic, but was curious what others are

On Fri, Nov 6, 2009 at 4:34 PM, Richard A Steenbergen <ras at>wrote:

> On Fri, Nov 06, 2009 at 04:50:10PM +0100, Daniel Roesen wrote:
> > On Thu, Nov 05, 2009 at 11:06:56PM -0600, Richard A Steenbergen wrote:
> > > Definitely a problem. The point of using 65123:45678 in the first place
> > > (with a private ASN field in the "AS part") is to avoid stepping on
> > > anyone else's ASN with your internal use community.
> >
> > Actually, as far as I have seen yet, it's more like being able to
> > derrive/describe community from ASN-to-act-on, e.g.
> >
> > 61234 meaning "prepend 3 times"
> > 45678 meaning "this is the neighbor AS I want this to be applied to"
> No I'm not saying otherwise. My point was that the reason it is
> "65123:45678" instead of "45678:65123" is that they're using a value
> from the private ASN range for the "action" tag, thus eliminating the
> potential for collisions with anyone else's real ASNs. As you pointed
> out, the ASN and Data fields are no longer going to be the same bit
> size, so the "flipping the fields" trick will no longer work. The only
> solution will be to add a non-transitive target type and do
> "localtarget:45678:65123".
> --
> Richard A Steenbergen <ras at>
> GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)

More information about the NANOG mailing list