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/members-discuss@ripe.net/
[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
Wed Jul 8 17:24:57 CEST 2020
Hi, Le lundi 06 juillet 2020 à 15:15 +0200, Clement Cavadore a écrit : > TL;DR: I feel that the due diligence procedures at RIPE NCC are too > strict, and that they should be a bit more human when having to deal > with administrative changes. Addendum: RIPE-709 should be updated to be less painful in the case of mergers and acquisition. Sometimes, when a business acquires another, and reorganize its assets, companies are partially merged with others, and as a result, it is considered under section 3.2 of RIPE-709 (if the new structure is not a member). Wouldn't it be better to make that section a bit less restrictive ? For example: if ALL the resources coming from a legacy member are being integrated in a new member, why not simply allow rename the legacy LIR to the reflect the new structure (and for more security, we could also lock the resources within it, if it could help preventing hijacking of resources)? Less paperwork, more love ! -- 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 ]