Hi all, If this has been discussed before, my apologies.
RFC 1997 already talks about using the first 16 bits of the BGP community value to identify an AS and then the remaining 16 bits to indicate something relevant in that AS. Later this was made easier by formatting communities as AS:nn rather than a 32-bit integer in decimal form. But now we have 32-bit AS numbers. The obvious solution is to use an extended community as per RFC 5668. However, the trouble with that is that you can't do anything with such a community unless your routers have built-in support for RFC 5668. So this creates a huge chicken and egg problem. (If anyone has any data on RFC 5668 support out in the wild that would be useful.) Obviously using AS:nn where AS:nn is 32 bits and AS is 32 bits doesn't leave much room for nn. But AS numbers are given out at ~ 10k/year so if we can support a million or so then we can still do something useful and backward compatible here while we wait for RFC 5668 support. My question: have there been any previous efforts to define an AS:nn format for regular BGP communities that support 32-bit ASNs to some degree? _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
