RPSL list, RFC2622 and 4012 say: <as-number> An AS number x is represented as the string "ASx". That is, the AS 226 is represented as AS226. This was written assuming 16 bit (0-65536) AS numbers (ASN16). There is now a draft to expand the AS number space to 32 bits (ASN32, see draft-ietf-idr-as4bytes-12.txt) as well as proposals in the various regions to start deploying those (RIPE2005-08, ARIN 2005-9, APNIC 032-v2 and others) as of January 2007. Draft draft-michaelson-4byte-as-representation-01.txt suggests that ASN are written as: <16 msb in decimal>.<16 lsb in decimal> with the first part dropped for values <65536. (In other words, the AS are labelled 0, 1, 2, .... 65534, 65535, 1.0, 1.1, 1.2 ... 1.65535, 2.0). I can imagine that people will want to use 32 bit ASN in RPSL starting 1/2007. Question: How to adapt RPSL for this? Solutions: 1) Change the definition in RFC2622 to <as-number> An AS number x is represented as the string "AS[0-9]+ or AS[0-9]+.[0-9]+. (In other words, follow the Michealson draft). 2) Other? If so, what? I guess in all cases, implementors will have to check that their implementations can deal with ASN >65535. Is there a WG where we can submit a draft with these extensions? Henk ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------