This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[routing-wg]Representation of four byte AS numbers.
- Previous message (by thread): [routing-wg]Representation of four byte AS numbers.
- Next message (by thread): [routing-wg]Representation of four byte AS numbers.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Sun Oct 19 15:19:31 CEST 2008
In past working group sessions we've already discussed the benefits and > disadvantages of the various methods of representing 32 bit ASNs (i.e. > 'asplain,' 'asdot'). There is now an internet-draft recommending > asplain (which is just a single 32 bit integer) in last call at the IETF > which can be obtained from the following URL: > > http://www.ietf.org/internet-drafts/draft-ietf-idr-as-representation-01.txt > > A related policy proposal reached consensus at the last APNIC meeting > and is now in last call there: > > http://www.apnic.net/policy/proposals/prop-065-v001.html this proposal was accepted by the apnic sig and member meetings, and is in final discussion on the mailing list. it has no significant additional comment, and would be passed to the apnic ec before the end of this month. but, friends at the ietf have said that they believe they can get the ietf document done and fully processed before the end of the year. so we plan to stall the apnic process in hopes that the ietf can execute theirs. randy, apnic policy chair
- Previous message (by thread): [routing-wg]Representation of four byte AS numbers.
- Next message (by thread): [routing-wg]Representation of four byte AS numbers.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]