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: Poul-Henning Kamp < >
  • From: Engin Gunduz < >
  • Date: Wed, 17 Mar 1999 10:40:31 +0100
  • Cc: "Wilfried Woeber, UniVie/ACOnet" < >
  • Organization: RIPE NCC

Hi,

Personally, I would like to see  2030:0:5::/48  instead of
2030:0:5:0:0:0:0:0/48 as the result of the query in the
whois database, since shorthand notation is, IMHO, more
"readable" by human eye. However, maybe we can introduce
yet another option to the whois server and client to show
the query result on inet6num objects without shorthand
notation?

Well, restricting the usage of shorthand notation could
ease the implementation of the whois server. But, IMHO,
in the user side, it is better to allow it.

Best regards,

Engin Gunduz
RIPE NCC

Poul-Henning Kamp wrote:
> 
> In message <009D5362.46E0DF3C.25@localhost>, "Wilfried Woeber, UniVie/ACO
> net" writes:
> 
> >  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?
> 
> There is certainly something to be said for making it easy for programs
> to parse the registry.
> 
> --
> Poul-Henning Kamp             FreeBSD coreteam member
> phk@localhost               "Real hackers run -current on their laptop."
> FreeBSD -- It will take a long time before progress goes too far!




  • 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