Dear colleagues,
Consensus has been reached on 2023-03 "Voluntary Transfer Lock".
This policy proposal aimed to allow holders of resources registered with
the RIPE NCC to inform the RIPE NCC that certain resources must not be
transferred for a certain amount of time.
You can find the full proposal at:
https://www.ripe.net/participate/policies/proposals/2023-03
The new RIPE Document is called ripe-806 and is available at:
https://www.ripe.net/publications/docs/ripe-806
The following RIPE policy has been updated as well and received a new
document number:
ripe-807, "RIPE Resource Transfer Policies"
https://www.ripe.net/publications/docs/ripe-807
We estimate that this proposal will take around two months to fully
implement.
In order to ensure a correct and consistent handling of requests, the
current procedures remain in place until the implementation is completed.
This applies in particular to:
RIPE NCC Executive Board resolution EB#163-R-02
https://www.ripe.net/about-us/executive-board/minutes/2022/minutes-163rd-ex…
Registry Lock Request Form
https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-mergers/reg…
We will send another announcement once the implementation is complete
and the new procedures are in place.
Thanks to everyone who provided input.
Kind regards,
Angela Dall'Ara
Policy Officer
RIPE NCC
Hi all,
No additional comments were received during the Concluding Phase (Last Call) for policy proposal 2023-03, allowing the RIPE NCC to implement a Voluntary Transfer Lock.
https://www.ripe.net/participate/policies/proposals/2023-03
As the PDP states, "If there is no feedback from the community at this stage, this is likely to be regarded as consensus and it will mean the previous call of rough consensus from the WG chairs at the end of the Review Phase still holds.”
Hence, we believe consensus has been reached and the RIPE NCC may assume there is community backing to implement the Voluntary Transfer Lock as described in the proposal.
Cheers,
Rob on behalf of the NCC Services WG Co-chairs.
