[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 ]
Clement Cavadore
ccavadore at vedege.net
Mon Jul 6 19:15:14 CEST 2020
Hello, Thanks Sebastien for your support, Le lundi 06 juillet 2020 à 17:08 +0000, Sebastien Brossier a écrit : > 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. And, if the aim is to prevent fraudulent resource transfer: Why not adding to the procedure a 24months lock period to the resources after the LIR contractual name change? That could at least prevent fraudulent mechanism to take profit of such a procedure, isn't it? Regards, -- Clément Cavadore
- 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 ]