Gaurab,A suggestion: Why not approach IANA and/or IETF about reserving all of 65535.0 - 65535.65534 (or 4294901760 - 4294967294 in ASPLAIN), and identify a small number of those for documentation?
I make this suggestion on the basis:- It would be a block that could be readily configured for exclusion from public BGP routing (rather than having 4 arbitrary numbers to be excluded from the midst of an otherwise public set of ASs);
- Some of this space might be able to be used later for extensions of private AS numbers (I have no idea now why there would ever be a need for more than 1024 private ASs, but it's possible someone will find a requirement some day);
- Even if ASDOT is ultimately deprecated, it may still be a useful range to have reserved (again for purposes like private AS extensions, or other as yet unknown reasons);
- I seriously hope that there will never be 4 billion ASs simultaneously active in the Internet table, so I doubt the reservation of those 65,535 numbers would be a noticeable loss to the overall public 4-byte space. (Yes, I know previous statements like that have been regretted later, but 4 billion ASs is a very different concept from 4 billion addresses.)
Regards,
David
At 12:56 PM 28/07/2008, Gaurab Raj Upadhaya wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David Woodgate wrote: | |> But anyway, just so that Gaurab and I are clear, the only way you'd |> support this idea is if it was taken to the IETF and worked through |> the standard process? | | Correct. There are no current IETF standards for 4byte ASN representation in ASDOT format. If there was a standard, there would have been a documentation set assigned. If APNIC has decided to use ASDOT as the preferred way to represent 4byte ASN, it's also required of it to make necessary assignments for documentation. I am also wondering what APNIC is using in current documentation on 4byte ASNs. It would be fitting to APNIC objectives to prepare proper documentations for use by its community of members. If you are aware of any means to appeal to IANA directly for documentation assignment then let us know. - -gaurab -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkiNNXYACgkQSo7fU26F3X0urgCgpWYVHVamHj8BZmAuh2iRs+cj FIoAoLu9boG9PLYqUfGrp4Da80rHylvl =y8/+ -----END PGP SIGNATURE-----