You are here: Home > Participate > Policy Development > Policy Proposals

Document Actions

Policy Proposals

Ambiguity cleanup on IPv6 Address Space Policy for IXP

2010-07: Ambiguity cleanup on IPv6 Address Space Policy for IXP. This proposal aims to clarify an ambiguous definition in ripe-451, "IPv6 Address Space Policy for Internet Exchange Points", regarding the requirements to join an IXP. The ambiguity lies in the use of the phrase "open policy for others to join" in the definition of the IXP framework. Any restriction to IPv6 deployment that arises from policies on joining IXPs could be counterproductive.

Temporary Internet Number Assignment Policies

2010-01: This proposal expands the RIPE NCC's ability to assign number resources for temporary purposes and allows the RIPE NCC to reserve pools of IP addresses and Autonomous System (AS) Numbers, which can be used by the RIPE NCC to make temporary direct assignments to End Users.

PI Assignment Size

2006-05: PI Assignment Size. This proposal allows for End Users who request a Provider Independent IPv4 address assignment to be assigned limited additional address space to make the assignment size a multiple of /24. The End User must demonstrate the intent to multihome the assignment.

Abuse contact information

2010-08: Abuse contact information. This is a proposal to introduce a mandatory reference to irt objects in the inetnum, inet6num and aut-num objects in the RIPE Database. It provides a more accurate and efficient way for abuse reports to reach the correct network contact and helps reporting institutions to find the correct abuse contact information more easily.

4-Byte AS Number Policy

2005-12: 4-Byte AS Number Policy. This policy proposal details a set of actions and associated dates for RIR AS Number allocation policies to assist in an orderly transition to use of the 4-byte AS Number space.

IP Assignments for Anycasting DNS

2005-02: IP Assignments for Anycasting DNS. To enable country code Top Level Domain (ccTLD) and global Top Level Domain (gTLD) name server operators to provide their DNS service using shared unicast technology, RIPE NCC may assign one IPv4 and/or one IPv6 prefix to each TLD operator.


2006-03: LIR-PARTITIONED Status for IPv6. This proposal is to have a new status for IPv6 address space as "LIR-PARTITIONED".

IPv6 Initial Allocation

2005-03: IPv6 Initial Allocation. The proposal is to change the IPv6 Initial Allocation criteria outlined in the "IPv6 Address Allocation and Assignment Policy". The proposed change is to remove "have a plan for making at least 200 /48 assignments to other organisations within two years" and to remove the reference to "/48s" as the assignment size.

Multicast Monitoring on RIPE NCC Test Traffic Boxes

2005-11: Multicast Monitoring on RIPE NCC Test Traffic Boxes. This proposal is to add functionality to the Test Traffic Measurement (TTM) service that allows for testing of multicast-capable networks.

Consumer Broadband Monitoring Feasibility

2005-10: Consumer Broadband Monitoring Feasibility. This is a proposal to have the RIPE NCC, as a neutral body, develop a way of measuring performance for consumer broadband networks. The proposal requests funding for a limited deployment prototype with the purpose of assessing industry and consumer acceptance, functional requirements and technical issues.

RIPE Forum

The RIPE Forum is an additional way to participate in RIPE community mailing list discussions using a web-based interface rather than an email client.

Check out the forum

Please contact if you need more information.

Stay up to date!

Follow @PDO_RIPE_NCC on Twitter.