Archived Policy Proposals
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.
| Name | Status | Proposal Number | Working Group | Date Archived |
| Resource Hijacking is a RIPE Policy Violation |
WITHDRAWN
|
2019-03 | Anti-Abuse Working Group | October 2019 |
|
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. |
||||
| IPv4 Waiting List Implementation |
ACCEPTED
|
2019-02 | Address Policy Working Group | July 2019 |
|
Summary: This proposal created a waiting list based on an allocation size of /24 once the RIPE NCC’s free IPv4 pool is exhausted. |
||||
| Clarification of Definition for "ASSIGNED PA" |
ACCEPTED
|
2019-01 | Address Policy Working Group | May 2019 |
|
Summary: This proposal made it clear in the IPv4 Policy that the status "ASSIGNED PA" can also be used for assignments to an LIR's infrastructure. |
||||
| Assignment Clarification in IPv6 Policy |
WITHDRAWN
|
2018-02 | Address Policy Working Group | March 2019 |
|
Summary: This proposal aimed to clarify the definition of "Assign" in ripe-707 (section 2.6). Reason for Withdrawal: The proposer decided it was best to find agreement on a problem statement before developing new policy text. |
||||
| Publication of Legal Address of Internet Number Resource Holders |
WITHDRAWN
|
2018-05 | RIPE NCC Services Working Group | January 2019 |
|
Summary: This proposal aimed for the RIPE NCC to publish the validated legal address information of all holders of Internet number resources. Reason for Withdrawal: The proposer decided it was not possible to find an acceptable agreement which satisfied all parties. There is still heavy resistance in the community that cannot be resolved at this stage. |
||||
| PDP Clarification |
ACCEPTED
|
2018-04 | September 2018 | |
|
Summary: This proposal clarified the options available to the Working Group chairs at the end of the Review Phase of the RIPE Policy Development Process (PDP). |
||||
| Fixing Outdated Information in the IPv4 Policy |
ACCEPTED
|
2018-03 | Address Policy Working Group | August 2018 |
|
Summary: This proposal fixed outdated information in the RIPE Policy "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region". |
||||
| Organisation-LIR Clarification in IPv6 Policy |
ACCEPTED
|
2018-01 | Address Policy Working Group | July 2018 |
|
Summary: This proposal aimed to clarify the wording used in RIPE-699 regarding terms such as “organisation” and “LIR”. |
||||
| Regular abuse-c Validation |
ACCEPTED
|
2017-02 | Anti-Abuse Working Group | June 2018 |
|
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. |
||||
| IPv6 Sub-assignment Clarification |
ACCEPTED
|
2016-04 | Address Policy Working Group | March 2018 |
|
Summary: The goal of this proposal was to re-define the term "sub-assignment" for IPv6. |
||||