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 ]
Geoff Huston
gih at apnic.net
Sun Oct 19 19:34:18 CEST 2008
Hi, Here's a bit more background, if you are at all interested. The recent action in the APNIC policy SIG has prompted the submission of a draft to the IETF that proposed the adoption of a plain integer format for AS Numbers an Internet Standard. The document, draft-ietf-idr-as- representation-01.txt, has now been through an IETF review process of acceptance by the IDR Working Group, review in a Working Group Last Call, the preparation of an implementation report, and has now been passed across to the IESG for publication as a Proposed Standard. The document is currently in IETF Last Call (https://datatracker.ietf.org/idtracker/?search_button=SEARCH&search_filename=draft-ietf-idr-as-representation-01.txt&sub_state_id=6 ). The Last Call ends today (20th October 2008). Within the context of the APNIC policy development process, the APNIC proposal's authors have been requested to consider delaying the APNIC implementation procedure in order to allow the IETF Standards process to run to completion in this case (http://mailman.apnic.net/mailing-lists/sig-policy/archive/2008/10/msg00008.html ). Speaking personally, I'm not sure what the objective would be in introducing a similar proposal to RIPE at this stage, given that the IETF process of standardization of nomenclature for 32-bit AS numbers is reaching a conclusion in the coming couple of weeks or so, but I guess (hope?) that the motivation for doing this in parallel in the context of the RIPE policy development process will become apparent once the proposal you refer to is actually posted to the address- policy mailing list. regards, Geoff Huston Disclaimer - speaking just for me, as usual! On 19/10/2008, at 8:47 PM, Rob Evans wrote: > Hi all, > > At some point in the coming week I expect to see a new policy > proposal hit the policy-announce and address-policy mailing lists > that we might want to be aware of here. > > 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 > > Whilst we already have a presentation on experiences of using a 32 > bit ASN scheduled for the Routing working group session, the policy > is being discussed in the Address Policy working group. At the > moment it will be presented during the session just before lunch on > Tuesday morning. At the same time there will also be a presentation > on the proposal for certification of PA resources, which you may > also be interested in. > > All the best, > Rob >
- 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 ]