RIPE NCC · Vigilancia de RIR
Voluntary Transfer Lock
Consulta aquí el historial de cada propuesta: qué cambió, por qué fue relevante, quién defendió cada postura, cómo evolucionaron las posiciones, qué se decidió y dónde persisten las lagunas en la evidencia.
Hechos con fuentes
- ID de política
- 2023-03
- RIR
- RIPE NCC
- Estado oficial
- Accepted
- Presentada
- 8 mar 2023
- Última actualización de fuentes
- 18 nov 2026
¿Quiénes marcaron realmente el debate?
Evolución de la política
Strength of constraints, recommendations and implementation choices · Version 2 explicitly distinguishes mandatory constraints, recommendations that need a strong reason for departure, and optional implementation choices that must be documented. This clarifies the force of the existing three sections. It does not change the resource types covered, the exclusion of legacy resources, or the irrevocability of an agreed lock.
Hechos con fuentes −
When requesting a Voluntary Transfer Lock, the procedural documentation published by the RIPE NCC is leading. These procedures must comply with the constraints set by this policy.Hechos con fuentes ↗
Hechos con fuentes +
All the Constraints defined below must be followed during the implementation of the policy by the RIPE NCC. All Recommendations should be followed unless there is a strong reason to deviate from them. The Implementation choices explicitly give the RIPE NCC leeway. The RIPE NCC may implement them if they so choose, provided that the choices are explicitly documented.Hechos con fuentes ↗
Reason for pursuing a community policy · Version 2 adds the proponents’ explanation for moving into review: after discussion with RIPE NCC staff, they considered a community policy necessary to implement the service. This is reported procedural rationale, not a newly imposed lock or evidence that every resource holder wants one.
Hechos con fuentes −
There have been requests from parts of the community to implement this option. The policy gives resource holders an option they can use, it doesn’t affect those who don’t want to use it.Hechos con fuentes ↗
Hechos con fuentes +
After deliberations with the responsible RIPE NCC staff, we have decided to go ahead and propose this policy. Although others felt it was unnecessary, the RIPE NCC made it clear that it could not implement this option without a policy.Hechos con fuentes ↗
Working-group remit and transfer-policy cross-reference · The added rationale says the proposal stays in the RIPE NCC Services Working Group because it concerns a requested service, with a linked amendment to ripe-682 intended to avoid contradictory transfer-policy wording. The retained version describes that companion amendment but does not reproduce its complete text; no additional transfer restriction can be inferred from the reference alone.
Hechos con fuentes −
This policy only defines the constraints on the implementation of a Voluntary Transfer Lock. It explicitly does not prescribe a specific implementation by RIPE NCC.Hechos con fuentes ↗
Hechos con fuentes +
We decided to leave it in the RIPE NCC Services Working Group as the content of the policy mainly concerns a service that the community wants the RIPE NCC to provide. We added a small update [2] to the transfer policy (ripe-682) to refer to this new service in order to avoid any contradiction between the texts of the policy.Hechos con fuentes ↗
Cronología del debate
Entidades
Cargando
Fuentes y cobertura
Fuentes oficiales
Archivos de debates públicos
- ripencc-address-policy-wg –
- ripencc-accountability-tf-ripe.net –
- ripencc-agm-nominations-ripe.net –
- ripencc-all-anchors-ripe.net –
- ripencc-anti-abuse-wg-ripe.net –
- ripencc-atlas-sponsors-ripe.net –
- ripencc-atlas-sw-probes-ripe.net –
- ripencc-bcop-ripe.net –
- ripencc-coc-tf-ripe.net –
- ripencc-connect-bof-ripe.net –
- ripencc-connect-wg-ripe.net –
- ripencc-cooperation-wg-ripe.net –
- ripencc-db-help-ripe.net –
- ripencc-db-wg-ripe.net –
- ripencc-diversity-ripe.net –
- ripencc-dns-resolver-tf-ripe.net –
- ripencc-dns-wg-ripe.net –
- ripencc-dp-tf-ripe.net –
- ripencc-eb-candidates-ripe.net –
- ripencc-eix-wg-ripe.net –
- ripencc-election-cc-team-ripe.net –
- ripencc-enum-announce-ripe.net –
- ripencc-enum-wg-ripe.net –
- ripencc-hackathon-list-ripe.net –
- ripencc-icann-plan-ripe.net –
- ripencc-iot-wg-ripe.net –
- ripencc-ipmap-ripe.net –
- ripencc-ipmt-dev-ripe.net –
- ripencc-ipv6-wg-ripe.net –
- ripencc-irrtoolset-ripe.net –
- ripencc-lir-wg-ripe.net –
- ripencc-mat-wg-ripe.net –
- ripencc-measure-voip-ripe.net –
- ripencc-members-discuss-unmoderated-ripe.net –
- ripencc-members-discuss-ripe.net –
- ripencc-myasntesting-ripe.net –
- ripencc-ncc-announce-ripe.net –
- ripencc-ncc-services-wg-ripe.net –
- ripencc-opensource-wg-ripe.net –
- ripencc-persian-lir-ripe.net –
- ripencc-policy-announce-ripe.net –
- ripencc-raci-list-ripe.net –
- ripencc-regional-russia-ripe.net –
- ripencc-regional-ukraine-ripe.net –
- ripencc-ripe-atlas-ambassadors-ripe.net –
- ripencc-ripe-atlas-tools-maintainers-ripe.net –
- ripencc-ripe-atlas-ripe.net –
- ripencc-ripe-chair-discuss-ripe.net –
- ripencc-ripe-db-requirements-tf-ripe.net –
- ripencc-ripe-forum-test-ripe.net –
- ripencc-ripe-list-unmoderated-ripe.net –
- ripencc-ripe-list-ripe.net –
- ripencc-ripe-parents-ripe.net –
- ripencc-ripecast-ripe.net –
- ripencc-rirs-lea-ripe.net –
- ripencc-ris-int-ripe.net –
- ripencc-ris-users-ripe.net –
- ripencc-routing-wg-ripe.net –
- ripencc-rpslng-ripe.net –
- ripencc-security-wg-ripe.net –
- ripencc-see-regional-ripe.net –
- ripencc-techsec-wg-ripe.net –
- ripencc-tld-wg-ripe.net –
- ripencc-tt-tf-ripe.net –
- www.ripe.net/community/wg/active-wg/ap/minutes
- ripencc-green-tech-hackathon-orga-ripe.net
- ripencc-nccdays-pc-ripe.net
Cobertura
Primera captura: 30 jun 1992
Última captura: 14 nov 2026
