Hi Geoff, Do you have any plan for another trial longer and notified so that everyone with various implementations of OLD SPEAKER can observe this and check if they normally handle a 4-byte ASN?
Regards, Akinori In message <[EMAIL PROTECTED]> "4 Byte AS tested" "Geoff Huston <[EMAIL PROTECTED]>" wrote: | | # bgpctl show rib 203.10.62.0/24 | flags: * = Valid, > = Selected, I = via IBGP, A = Announced | origin: i = IGP, e = EGP, ? = Incomplete | | flags destination gateway lpref med aspath origin | *> 203.10.62.0/24 147.28.0.1 100 0 0.3130 0.1239 | 0.4637 0.4637 0.4637 0.4637 0.4637 0.4637 0.1221 1.202 i | | | George Michaelson, Randy Bush and myself have successfully tested the | implementation of 4Byte AS BGP on a public Internet transit. The | above BGP RIB snapshot was taken at a 4Byte BGP speaker in North | America, showing a transit path across AS 1221, AS 4637, AS 1239 and | AS 3130 , with correct reconstruction of the originating AS at the | other (4Byte AS) end. | | The code base used was OpenBGPD, with 4 byte patches that I've added | to the code in the past couple of weeks. | | (Patched versions of openbgpd to include 4-byte AS support can be | found at http://www.potaroo.net/tools/bgpd/) | | cheers, | | Geoff | | | |
