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] 2023-03 Voluntary Transfer Lock
- Previous message (by thread): [ncc-services-wg] 2023-03 Voluntary Transfer Lock
- Next message (by thread): [ncc-services-wg] 2023-03 Voluntary Transfer Lock
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
James Kennedy
jameskennedy001 at gmail.com
Fri May 12 12:34:35 CEST 2023
Hello, > Why don't we keep it simple? Let's modify ripe-682 and include an opt out clause to disallow transfers. If you invoke this opt out it is a part of ripe-682 so you are not violating it. All the transfer rules are in one policy, self contained and consistent. +1. This is the best permanent solution that I've heard so far. It would take some time to get through the PDP though, and a transfer lock mechanism is urgently needed by some members immediately. So I also support 2023-03 as a stopgap. 2023-03 may contradict ripe-682 as Denis flagged, but IMHO it's more important to get a ‘better-than-nothing’ temporary solution implemented ASAP. Regards, James
- Previous message (by thread): [ncc-services-wg] 2023-03 Voluntary Transfer Lock
- Next message (by thread): [ncc-services-wg] 2023-03 Voluntary Transfer Lock
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]