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/[email protected]/
NIC Handles
- Previous message (by thread): NIC Handles
- Next message (by thread): NIC Handles
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marten Terpstra
Marten.Terpstra at ripe.net
Thu Nov 25 09:52:31 CET 1993
* A still open question is what to do with people residing in Europe having * a InterNIC handle already. You surely want these people to have a RIPE * handle as well, I presume. This, however, would mean that such a person * has two handles, which is confusing. Andrew is right here. One person, one nic-handle. We have been talking about the way to introduce this, and we came up with something along the lines of: - no flag day, ie no day where we assign everyone in the database a handle - assign handles where there are conflicts using the new scheme - assign nic handles on request (by sending in a person with nic-handle: assign) * Possible solutions?: * - flag these people and assign them a RIPE handle and reject the INIC * handle. * - leave the INIC handle as is, and use this inside the RIPE Data Base. * - Live with the confusion of more than one handle per person. * * A totally different thing is that there are people in the data base more * than once. I guess this is really hard to flag automatically, but this * needs to be sorted out as well. That is on my list now. I will write some script to find all possible and real conflicts currently in the database. Our guess is that it is not that many today. These have to solved by manually. -Marten
- Previous message (by thread): NIC Handles
- Next message (by thread): NIC Handles
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]