Archived Policy Proposals

Summary: The goal of this proposal was to change the registration of  IPv4 assignments from mandatory to optional.

Reason for withdrawal: The proposer decided to withdraw this proposal, feeling that a new proposal would be more suitable for including the suggestions and feedback provided by the community during the discussion phase.

Summary: The goal of this proposal was to allow the publication of verified Personal Data in the RIPE Database only when justified by its purpose.

Reason for withdrawal: The proposer felt that the scope of this proposal was too wide and decided to withdraw the proposal. Raised concerns like the potential consequences of the consent based publication of personal data and the efficacy of their verification might be addressed in future discrete proposals.

Summary: The proposal aimed to have the RIPE NCC validate "abuse-c:” information more often and introduce a new validation process.

Reason for withdrawal: The proposal did not reach consensus and the WG chairs did not feel that any further redrafting of the proposal would achieve consensus.

Appeal: The proposer appealed against the decision of the WG Chairs on October 5, 2020
https://www.ripe.net/ripe/mail/archives/policy-announce/2020-October/000569.html

Outcome of the Appeal: October 26, 2020 - The WG Chairs Collective (WGCC) decided to uphold the decision of the Co-Chairs of the Anti-Abuse Working Group.
https://www.ripe.net/ripe/mail/archives/policy-announce/2020-October/000571.html

Summary: The proposal aimed for the RIPE NCC to publish a SLURM file (Simplified Local Internet Number Resource Management with the RPKI), containing assertions with the origin “AS0” for all unallocated and unassigned address space under our control.

Reason for withdrawal: The WG Chair felt that raised concerns remained unaddressed and that there was a strong opposition against the proposal in the community.

Summary: This proposal aimed to remove obsoleted text and simplify the IPv6 policy.

Summary: This proposal aimed to change the default IXP assignment size from a /24 to a needs-based model, with a /27 as a minimum.

Reason for Withdrawal: The proposer felt that there was no clear direction on how to proceed with the proposal.

Summary: This proposal created a process to delete a non-authoritative object stored in the RIPE IRR, if it conflicts with an RPKI ROA.

Summary: This proposal aimed to increase the reserved IPv4 pool for IXPs to a /15 and finetune assignment criteria.

Summary: This proposal aimed to define that BGP hijacking is not accepted as normal practice within the RIPE NCC service region.

Reason for Withdrawal: The proposers felt they were unable to address concerns that the policy would expose the RIPE NCC to unacceptable liability risks. These concerns were expressed by both the Executive Board and some community members.

Summary: This proposal created a waiting list based on an allocation size of /24 once the RIPE NCC’s free IPv4 pool is exhausted.