[arin-ppml] 2-byte ASN policy

Ron Grant rgrant at skywaywest.com
Sun Apr 3 20:41:59 EDT 2016

Sorry, your humour is completely evading me tonight. Can you explain?

BTW, this comment is not intended to be an obtuse rejoinder, I'm 
sincerely interested in what you're trying to say.

On 2016-04-03 5:34 PM, Michel Py wrote:
>> Ron Grant wrote :
>> The biggest technical problem with 4-byte ASNs that I'm aware of comes when propagating BGP communities
>> - AFAIK even with extended communities, you can't specify two 4-byte ASNs in a single community.
> Indeed. I am perverting RT:ASN:Comm (that part does accept and propagate multiple 4-byte ASNs) instead of ROO:ASN:Comm; I wanted to propagate a community that said something about the source of the prefix, not the target. I'm evil.
> Michel.
> ip extcommunity-list standard COMM-EX-CBBC permit rt 4200065532:666 rt 4200065532:667
> route-map RM-EXABGP permit 10
>   set extcommunity rt 4200065532:666 4200065532:667
> cisco2821#sh ip bgp x.x.x.x
> BGP routing table entry for x.x.x.x/32, version 19852973
> Paths: (1 available, best #1, table default)
>    Not advertised to any peer
>    65532
> from (
>        Origin IGP, localpref 100, valid, external, best
>        Community: 65532:666 65532:667
>        Extended Community: RT:4200065532:666 RT:4200065532:667

Ron Grant                             Managed DSL/Cable/Wireless/Fibre
Skyway West Business Internet          Internet and Private Networking
rgrant at skywaywest.com                  Bonding and Fail Over Solutions
cell: 604-737-2113              Virtual Data Centre and Private Clouds
direct: 604-484-5263                         http://www.skywaywest.com

Sales, Support and Billing    http://www.skywaywest.com/contact-us.htm


More information about the ARIN-PPML mailing list