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/db-wg@ripe.net/
Modifications to the inet6num in the RIPE Database
- Previous message (by thread): Modifications to the inet6num in the RIPE Database
- Next message (by thread): Modifications to the inet6num in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Engin Gunduz
engin at ripe.net
Wed Mar 17 10:40:31 CET 1999
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 at cc.univie.ac.at>, "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 at FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far!
- Previous message (by thread): Modifications to the inet6num in the RIPE Database
- Next message (by thread): Modifications to the inet6num in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]