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

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
Multicast Monitoring on RIPE NCC Test Traffic Boxes
2005-11 Test Traffic Working Group May 2006
Summary: A proposal to add testing of multicast connectivity between the RIPE NCC Test Traffic boxes that are connected to multicast-capable networks.

Reason for Withdrawal: During the discussion phase, the working group decided that the RIPE NCC should do the work and that there was no need to complete the full PDP cycle for this proposal.
Consumer Broadband Monitoring Feasibility
2005-10 Test Traffic Working Group May 2006
Summary: 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.

Reason for Withdrawal: During the discussion phase, the working group decided that the RIPE NCC should do the work and that there was no need to complete the full PDP cycle for this proposal.
Internet Assigned Numbers Authority (IANA) Policy for Allocation of IPv6 Blocks to Regional Internet Registries
2005-09 Address Policy Working Group April 2006
Summary: The proposal was to have a policy governing the allocation of IPv6 address space from the IANA to the Regional Internet Registries (RIRs).
Proposal to Amend the IPv6 Assignment and Utilisation Requirement Policy
2005-08 Address Policy Working Group November 2007

Summary: To amend the RIPE IPv6 address allocation policies regarding the definition of the default size of End Site allocations, the threshold value for End Site allocation efficiency, and the method of calculation of the End Site allocation efficiency metric.

Introducing DNSSEC Service to Reverse DNS Trees
2005-07 DNS Working Group October 2005

Summary: To implement DNSSEC, we propose extending the policy for Reverse Address Delegation of IPv4 and IPv6 Address Space in the RIPE NCC Service Region.

Proposal to Add Regional Boundaries to Policy Documents
2005-06 Address Policy Working Group July 2005
Summary: Our AS assignment policy has the following statement in it - "The RIPE NCC assigns AS Numbers for Autonomous Systems located in the RIPE NCC service region". Neither the IPv4 nor the IPv6 policy documents have such a clear statement in them. It might be a good idea to add a similar statement to those documents when they are updated.

Reason for Withdrawal: The proposer decided to withdraw this proposal.
Proposal to Remove Special African Policies From RIPE Policy Documents
2005-05 Address Policy Working Group July 2005
Summary: To modify the policy document text to reflect full recognition of AFRINIC as a functioning RIR.
IPv6 Address Allocation and Assignment Policy - definition for "End-Site"
2005-04 Address Policy Working Group January 2006

Summary: There are various terms for "end-site" in the IPv6 allocation and assignment policy (ripe-267) and the RFC3177. We need to have a final definition for "End-Site" to establish clear internal assignment policies.

Reason for Withdrawal: During discussions the proposer decided that the proposal was no longer necessary.

IPv6 Initial Allocation
2005-03 Address Policy Working Group June 2006
Summary: 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.

Reason for Withdrawal: Withdrawn by proposer who thought this proposal is superceded by 2006-02, IPv6 Address Allocation and Assignment Policy.
IP Assignments for Anycasting DNS
2005-02 Address Policy Working Group September 2006

Summary: 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.