Purely as a point of information, I think its worth remembering that 32 bit
ASN cannot be used in currently specified BGP4 in communities, because its
a 32 bit field defined as two 16 bit halves. I believe there is work afoot
in IETF to fix this. I don't have concrete details.
Therefore there
This has come up several times before. There is support for asn32s in bgp
extended communities: you need the "Transitive Four-Octet AS-Specific
Extended Community" values from here:
http://www.iana.org/assignments/bgp-extended-communities
... and you need to hope that this is supported on your
Right. I mussed up some details. The substance remains: if you are exposed
to economics which depends on the use of communities for TE, and cannot
influence external agents you do BGP with to support extended communities,
then you may decide you need a 16bit ASN, and so they have inherent value
to
On 03/09/2015 18:09, Sascha Luck [ml] wrote:
> Mind, if yelling loudly is how you get policy made in the RIPE
> community, rest assured I can yell VERY loudly. I can, in fact,
> even automate the yelling if need be.
please don't: rfc7282 works much better.
Nick
