[ixpmanager] BGP Extended Communities

[Joe Wooller]

On another note the only real community we have of importance is:

>>> 0:PEERASN - Do not send prefix to route-server participant with specific ASN

But we do it like this;

PEERASN:999

This works for juniper under extended communities, haven't tested cisco though..

Joe

On 24/04/2013, at 10:33 PM, Joe Wooller <Joe at waia.asn.au> wrote:

> *nod, 
> 
> So what to people do currently.. Just deal with it? :(
> 
> Joe
> 
> On 24/04/2013, at 10:32 PM, Nick Hilliard <nick at inex.ie> wrote:
> 
>> On 24/04/2013 15:12, Joe Wooller wrote:
>>> Is anyone on here using extended communities, and if so what are your policies.
>>> Given this seems to be the standard that most lean towards.
>>> 
>>> 	IXASN:IXASN - Send prefixes to all other route-server participants
>>> 	IXASN:PEERASN - Send prefix to only route-server participant with specific ASN
>>> 	0:PEERASN - Do not send prefix to route-server participant with specific ASN
>>> 	0:0 - Do not echo prefix to any other route-server participants.
>>> 
>>> I was hoping to try and adopt some sort of standard to help make it easier for international peers to jump on board if they were to build down here.
>>> However under juniper you can not match an extended community with 0:asnhere, or origin:0:asnhere 
>> 
>> this community policy filtering convention breaks when dealing with 32 bit
>> communities.  The only hope is to get proper 32 bit community support into
>> BGP (i.e. 32:32 instead of the current hacks).  This isn't even at IETF
>> internet draft stage.
>> 
>> Nick
>> 
>> _______________________________________________
>> INEX IXP Manager mailing list
>> ixpmanager at inex.ie
>> https://www.inex.ie/mailman/listinfo/ixpmanager
>> 
>> 
>> 
>> 
> 
> _______________________________________________
> INEX IXP Manager mailing list
> ixpmanager at inex.ie
> https://www.inex.ie/mailman/listinfo/ixpmanager
> 
> !DSPAM:1,5177ed5280741824615823!
> 
>