Hi Lorenzo, Could you tell me, as libbgpdump user, how 4-byte AS numbers smaller than 65536 will appear in the (ascii) AS paths? i.e. are you following draft-michaelson (4-byte AS = 0.3333) or the approach in Henk's RPSL draft (drop the 0 on output, 3333 always printed as 3333)? The first would make libbgpdump and thus RIS in general show identical behaviour as routers (if the michaelson draft is adopted by IESG). The second would make life easy for RISwhois (simply take the last component of the ASpath as origin AS/ASset, no added complexity checking for 0.x and translating it to ASx). -- Rene
For all ASN32 and RIS types:
I have just finished ASN32 support in libbgpdump, including support for the transitional attributes (NEW_AS_PATH and NEW_AGGREGATOR). The implementation based on the current MRT draft, plus Henk's suggestion for RIB dumps, plus my suggestions on what state changes might look like (neither the WG nor Larry Blunk have reacted to those). As agreed with Henk, extended communities have not been implemented yet.
I am reasonably confident that this code does the right thing, but implementing a decoder without being able to test it on data produced by real implementations is a hit-and-miss affair. I also couldn't understand the last sentence specifying ASN32 transition [1] and could find nobody who did, so I didn't implement it specifically.
The code has been committed to CVS and has been released as libbgpdump-1.4.99.0.tar.gz on http://www.ris.ripe.net/source/
Cheers, Lorenzo
[1] "Note that a valid AS_CONFED_SEQUENCE or AS_CONFED_SET path segment SHALL be prepended if it is either the leading path segment or adjacent to a path segment that is prepended".
-- Lorenzo Colitti lorenzo@ripe.net Network Engineer +31-20-5354471 RIPE NCC www.ripe.net