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] Locking unmaintained PERSON and ROLE objects in the RIPE Database
- Previous message (by thread): [db-wg] Locking unmaintained PERSON and ROLE objects in the RIPE Database
- Next message (by thread): [db-wg] Locking unmaintained PERSON and ROLE objects in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Piotr Strzyzewski
Piotr.Strzyzewski at polsl.pl
Thu Apr 14 00:31:47 CEST 2016
On Thu, Apr 14, 2016 at 12:00:45AM +0200, denis wrote: Denis >> Taking your arguments stated above, I once again (this time more clear) >> say that rolling back the change to allow changes to the PERSON object >> name would _not_ have fixed the problem. > > Maybe not, but it would have been a harmless change. Your action has This change has been discussed and expected in this community at least from the year 2000. And has been checked by You in 2014 with RIPE NCC's legal team. I haven't seen any technical, legal, procedural (nor any other) objections raised by You under issue 221 (https://github.com/RIPE-NCC/whois/issues/221). What has changed during last 1.5 year? Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski at polsl.pl
- Previous message (by thread): [db-wg] Locking unmaintained PERSON and ROLE objects in the RIPE Database
- Next message (by thread): [db-wg] Locking unmaintained PERSON and ROLE objects in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]