The policy proposals on this page have been archived. You can see at a glance if they were accepted and adopted by the RIPE community or withdrawn at any stage.
Summary: This proposal gives the RIPE NCC a mandate to regularly validate "abuse-mailbox:" information and to follow up in cases where the attribute is deemed to be incorrect.
Summary: The goal of this proposal was to re-define the term "sub-assignment" for IPv6.
Summary: This proposal aimed to reduce the IPv4 allocations made by the RIPE NCC to a /24 (currently a /22) and only to LIRs that have not received an IPv4 allocation directly from the RIPE NCC before.
Reason for Withdrawal: The proposers felt unable to create a second draft that addressed conflicting objections.
This proposal aimed to to add the requirement that the RIPE NCC publish all changes to the holdership of legacy resources in the existing transfer statistics.
Reason for Withdrawal: The proposer didn't see enough community support, especially from Legacy Resource Holders as the parties that would be most affected.
Summary: This policy change matches the subsequent IPv6 allocation requirements with the initial allocation requirements.
Summary: This proposal creates a single policy document for Internet number resource transfers, replacing text in several RIPE Policies. It also introduces a 24-month holding period for IPv4 addresses and 16-bit ASNs after any change of holdership.
Summary: This proposal aimed to ban transfers of allocations made under the final /8 policy.
Reason for Withdrawal: The proposer decided to abandon the proposal as he felt that the ongoing discussion was damaging the RIPE community’s reputation. As nobody stepped forward to take over the authorship of this proposal, the proposal was withdrawn.
Summary: This proposal aimed to allow all number resources, in exacts and more specifics, to be authenticated via an API-key that expires on a certain date.
Reason for withdrawal: The proposer didn't see enough community support, especially from the external database holders who would have needed to perform their own development work.
Summary: This proposal aimed for a mandatory abuse contact for Legacy Internet Resource Holders in the RIPE Database.
Reason for withdrawal: The proposer decided to withdraw the proposal due to the inability to find an acceptable agreement which satisfied all
parties.
Summary: This proposal aimed to allow LIRs to request an additional /22 IPv4 allocation from the RIPE NCC every 18 months. The latest version of the proposal introduced several requirements, such as that the LIR cannot hold more than a /20 of IPv4, must document their IPv6 deployment, and must not have transferred any IPv4 address space before.
Reason for withdrawal: The proposers decided to withdraw the proposal due to the inability to find an acceptable agreement which satisfied all parties.