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]/
[members-discuss] Administrative procedures within RIPE NCC: Any way to soften it ?
- Previous message (by thread): [members-discuss] Administrative procedures within RIPE NCC: Any way to soften it ?
- Next message (by thread): [members-discuss] Administrative procedures within RIPE NCC: Any way to soften it ?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sebastien Brossier
sebastien at brossier.org
Mon Jul 6 19:08:58 CEST 2020
I feel the same. Where all resources are transferable, RIPE NCC should allow a simple LIR name change with no more documentation than a LIR-to-LIR transfer. Or maybe require some link between old and new legal structures, but not the current strict requirements. A too strict procedure discourages people from updating their LIR details, which goes against what should be one of our primary goals: keeping the RIPE database up-to-date and accurate. -- Sébastien Brossier
- Previous message (by thread): [members-discuss] Administrative procedures within RIPE NCC: Any way to soften it ?
- Next message (by thread): [members-discuss] Administrative procedures within RIPE NCC: Any way to soften it ?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]