About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section

Re: [routing-wg]Four byte ASN notation

  • To: "Rob Evans" rhe@localhost, routing-wg@localhost
  • From: "tp" ripe@localhost
  • Date: Fri, 7 Dec 2007 12:12:03 +0100
  • Reply-to: "tp" ripe@localhost

Not sure if you aware but there is an IETF Internet Draft winging its way
through the system on this topic, namely

http://www.ietf.org/internet-drafts/draft-michaelson-4byte-as-representation-05.
txt


It did get discussed on the IETF idr list in October 2006, and met significant
resistance.  There were also comments then about NANOG taking a position on
this.  I haven't seen any discussion since.

Current status is Application Director Watching

Tom Petch

----- Original Message -----
From: "Rob Evans" rhe@localhost
Sent: Tuesday, December 04, 2007 11:59 PM
Subject: [routing-wg]Four byte ASN notation


> Folks,
>
> One of the items that was discussed during the working group meeting
> in Amsterdam was the relative benefits of using asplain, asdot or
> asdot+ to represent four byte autonomous system numbers.  The chairs
> feel that the discussion tended towards favouring asdot/asdot+, which
> is already used relatively widely, but with the note that people do
> need to review their in-house tools and scripts to ensure they will
> work with numbers expressed in this notation.
>
> Cheers,
> Rob
>



 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | © RIPE Community. All rights reserved.
RIPE.NET Homepage LIR Portal RIPE Community