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]/
[ncc-services-wg] Update on Measures to Protect Ukrainian Networks
- Previous message (by thread): [ncc-services-wg] Update on Measures to Protect Ukrainian Networks
- Next message (by thread): [ncc-services-wg] Update on Measures to Protect Ukrainian Networks
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Mon Dec 19 15:30:08 CET 2022
Hi Hans Petter, > After discussions with our Executive Board, we are now ready to begin implementation of a ‘voluntary registry lock’ in the LIR Portal. This will be available for all RIPE NCC members, including those in Ukraine, on an opt-in basis. The lock will allow members to prevent their resources from being transferred for a defined period. We expect technical implementation to be completed before the end of the year. Awesome! Thank you and the board for getting this difficult step done. > The Board made this resolution taking into account: > - The concerns expressed by Ukrainian members at the RIPE 85 Meeting in October 2022 > - The RIPE NCC’s commitment to be neutral and impartial > - The time needed for the formation of a permanent solution addressing these concerns through the Policy Development Process (PDP) > - The RIPE community’s support to accommodate a temporary solution +1 much appreciated! > This resolution comes with an expiry date of 1 July 2023. We hope that the RIPE community will use this time to agree on a policy proposal that gives us a clear mandate to provide this lock as a lasting solution to all members who see the need for it. Our Policy Officer is available to offer guidance and administrative support to get the proposal through the RIPE Policy Development Process. After making so much noise I feel I should volunteer here :) > From comments at RIPE 85, we understand that some people do not think this should be a policy matter. However, as we explained at that meeting, the RIPE NCC cannot limit the transfer rights of paying members without either a solid legal basis or a clear mandate from the RIPE community. I still think that limiting an LIR based on their own request shouldn’t be a problem, but ok, let’s work together on this and get a policy. > It is in this context that we must note that the lock will not prevent resources from being transferred in cases of merger or acquisition. It will also not prevent transfers in cases where a bankrupt company goes into liquidation. Sensible limitations, I have no problem with them. > Finally, in my last email, I said that requests from Ukraine would receive the ‘highest levels of due diligence’, and I want to explain what this means. In recent years, we have developed a framework that describes what information our staff will ask for when handling requests. By applying the strongest approach within this framework, we will be going beyond our standard requirements and asking to verify additional documents. With the passing of this resolution, transfers will follow the process outlined here and will not be escalated to the Managing Director for approval. Sounds good, you shouldn’t need to involve yourself in the workflow. You have very experienced staff for that :) > We hope that our Ukrainian members will understand that this is part of our efforts to protect their resources. > > As mentioned above, we will share more specific information on the registry lock before the end of the year – including how it can be activated and by whom, and what it does and does not restrict. Thank you! Sander
- Previous message (by thread): [ncc-services-wg] Update on Measures to Protect Ukrainian Networks
- Next message (by thread): [ncc-services-wg] Update on Measures to Protect Ukrainian Networks
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]