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/
[db-wg] Change of Country entries in the database
- Previous message (by thread): [db-wg] Change of Country entries in the database
- Next message (by thread): [db-wg] Change of Country entries in the database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hank Nussbacher
hank at att.net.il
Wed Oct 22 18:53:49 CEST 2003
On Wed, 22 Oct 2003, Shane Kerr wrote: > Daniel Karrenberg wrote: > > On 10.10 11:20, Hank Nussbacher wrote: > > > >>>Indeed, because of this reason, it might be good idea to obsolete > >>>"country:" attribute in the inetnums. What do you think about > >>>this? > >> > >>Please don't.99.9% accurate info is better than 0% info. > > > > > > I agree with Hank. One has to clearly differentiate between *hard* info > > that needs as close to 100% accuracy as one can get, and *soft* info that > > is still useful even when full accuracy cannot be guaranteed. > > > > Examples of hard info are address space allocation and assignment chains. > > country: is an example of soft info. > > > > Removing an attribute because its information is becoming too soft should > > only be done when the usefulness is much less thanthe current country:. > > Perhaps we should make it optional then.People who want to maintain the > information can keep it up to date, and people who want to use the > information will have greater certainty that if the attribute is there > that it is correct. I wouldn't make it optional, but I very much like your idea below but will cause havoc on all those automated scripty things out there pulling out the country tag and assuming a 2 character string. If you make the change remember to post to many Internet lists so everyone knows of the change. -Hank > > Also, I suggest that it may make sense to make it list-valued.Right now > it is: > > country: [mandatory] [multiple] [ ] > > So users who have networks in multiple countries and want to document have > to do things like: > > country: NL > country: BE > country: DE > > Or worse, things like: > > country: NL # BE DE > > Allowing the use of: > > country:NL, BE, DE > > Would solve this issue. > > -- > Shane Kerr > RIPE NCC > Hank Nussbacher
- Previous message (by thread): [db-wg] Change of Country entries in the database
- Next message (by thread): [db-wg] Change of Country entries in the database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]