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
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Re: Modifications to the inet6num in the RIPE Database

  • To: "Wilfried Woeber, UniVie/ACOnet" < >
  • From: Guy Davies < >
  • Date: Tue, 16 Mar 1999 20:24:38 +0000 (BST)
  • Cc:

>   interesting, indeed.
>   
>   Taking this one step further, and looking back at what we did with IPv4,
>   where it would be feasible to say 131.130/16, implying 131.130.0.0/16,
>   I wonder if it wouldn't again be worthwhile to restrict the use of these
>   shorthand notations in the Address Registry?
>   
>   Is there a danger for braking something by _not_ allowing the "::"
>   construct in the registry at all, or - in particular - not _in the
>   middle_ of a prefix?

I have to admit that in recording address allocations in UUNET UK's
networks, I write the addresses out in full.  I tabular format, it makes
for much easier identification of errors and anomalies.  In the RPSL
format, it's a little more difficult to point to benefits for humans but,
as PHK pointed out, it's easier for machines to parse.  However, given
that at least a few dozen hardware and software vendors have come up with
a reliable way to parse the abbreviated form, it can't be that difficult.

Regards,

Guy





  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

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