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: Henk Uijterwaal henk@localhost
  • From: Paul Jakma paul@localhost
  • Date: Fri, 7 Dec 2007 18:56:48 +0000 (GMT)
  • Cc: Gert Doering gert@localhost, tp ripe@localhost, Rob Evans rhe@localhost, routing-wg@localhost
  • Mail-copies-to: paul@localhost
  • Mail-followup-to: paul@localhost

On Fri, 7 Dec 2007, Henk Uijterwaal wrote:

I fully agree for the real world.  Here it seems that RIRs and some of
the vendors use asdot(+), so a safe bet would be to use that.

You've left out the operators, *all* of whom are going to audit all their all their configuration state and update any string-form filters of ASNs. There's no point revisting the arguments though, so let's try avoid classifications like the above.

A decision would indeed be nice. Given "asdot" is a fait accompli, by way of unmandated implementation, and there's little will to turn this barge back to port, why not write up and approve whatever policy documents are required?

regards,
--
Paul Jakma	paul@localhost	paul@localhost	Key ID: 64A2FF6A
Fortune:
I don't know who my grandfather was; I am much more concerned to know
what his grandson will be.
		-- Abraham Lincoln



 

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