|
|
|
|
|
|
by kloch
1402 days ago
|
|
|
Running BGP with 4-byte ASN's is well supported by all major vendors by now. The issue is policies that use ASN:XXXXX communities which is 2-byte:2-byte. There is an RFC to extend this to 4-byte for the ASN part but that is not widely supported yet. https://community.cisco.com/t5/routing/how-to-set-up-in-the-... https://datatracker.ietf.org/doc/rfc5668/ For small enterprises/end users (that might not define their own communities at all) this is usually not a problem but for larger networks or ISP's you end up with a compromise where you are truncating the 6-digit ASN or using a private ASN, neither of which are desirable. Arin let's you request a 2-byte ASN and if they have one in inventory (they usually do) you can get it. |
|
|