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/ncc-services-wg@ripe.net/
[ncc-services-wg] Re: [db-wg] Change to NIC handle usage in the RIPE Database
- Previous message (by thread): [ncc-services-wg] Change to NIC handle usage in the RIPE Database
- Next message (by thread): [ncc-services-wg] LIR Portal PI doesn't work
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at time-travellers.org
Mon Sep 14 14:10:03 CEST 2009
Denis, On Mon, 2009-09-14 at 13:25 +0200, Denis Walker wrote: > This change does not affect automatically generated organisation names. > But we would like to hear feedback on whether it makes sense to also > have these map to organisations uniquely over time. The organisation objects are required to be created with AUTO-n as their identifier. IIRC, this was done to insure that they had no meaning, other than as arbitrary database identifiers. They do use the name of the organisation to pick some letters for the identifier, or you can specify the letters to use, so it is not completely random. This use of organisation name to get letters was done for aesthetic reasons, and also as a nod to tradition. Because of the AUTO-n requirement, it seems likely to me that the use of old handles is even less of a problem than with person/role objects. It is crazy that any identifier in the database is ever reused. Madness! -- Shane
- Previous message (by thread): [ncc-services-wg] Change to NIC handle usage in the RIPE Database
- Next message (by thread): [ncc-services-wg] LIR Portal PI doesn't work
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]