Jaap Akkerhuis wrote:
It seems rather cumbersome to file a change proposal for each and every individual document where it basically comes down to a cosmetic change following international standards and will prevent us from a lot of discussion and the small risk some of these changes won't get consensus and we end up with 2 different models.
Yes, the proposal should be to move to the same format everywhere the RIPE NCC uses ASN.
Apart from this, it seems prudent to wait until draft-ietf-idr-as-representation-01.txt will become an official standard. Then it can be properly quoted.
Yes, while it is likely that this draft will be accepted, it is by no means certain. Since we have some 14,000 ASN in the 16 bit range left (where all representations are the same), there is no real hurry either. I'd suggest that we wait the +/- 2 months it will take to finalize the draft, then ask the RIPE NCC to "adjust the formatting of AS numbers to the standard set by the IETF everywhere". Henk Speaking as myself, not an NCC employee and not the person who'll be doing the work to move from ASDOT to ASPLAIN. -- ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Ceterum censeo Asplain esse delendam (Cato & Henk)