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 ]
Peter Hessler
phessler at theapt.org
Fri May 19 10:36:37 CEST 2023
I support 2023-03 Voluntary Transfer Lock. This is a good option for all members to have available. Since it is voluntary, and has the same authority requirements as transfers, I feel there is minimal risk that this will be inappropriately used. I also feel that we should _not_ unduely delay acceptance of this policy, even if we wish to propose another policy on this topic. Crucially, the very first sentence of: https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-mergers/transfer-of-ip-addresses-and-as-numbers/transfers-in-the-ripe-ncc-service-region gives us all of the authority needed: """All resource holders in the RIPE NCC region can transfer resources in accordance with RIPE policies.""" Furthermore, I disagree with Denis that there is a conflict between policies. This policy is clearly intended to carve out an exception, and it is very specific in describing how. -peter -- There are no data that cannot be plotted on a straight line if the axis are chosen correctly.
- 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 ]