Policy Proposals

2007-04: IANA Policy for Allocation of ASN Blocks to RIRs. This This proposal is to have a global policy for the Regional Internet Registries (RIRs) to receive blocks of Autonomous System Numbers (ASNs) from the Internet Assigned Numbers Authority (IANA).

2007-02: Change in IP Assignments for Anycasting DNS Policy. This proposal suggested that there should no longer be a requirement to be a ccTLD or a gTLD to receive IPv4 and IPv6 assignments for anycasting DNS.

2006-02: IPv6 Address Allocation and Assignment Policy. This proposal is to change the IPv6 Initial Allocation criteria and the End Site definition in the "IPv6 Address Allocation and Assignment Policy".

2006-07: First Raise in IPv4 Assignment Window Size. This proposal suggests the Assignment Window (AW) available to new LIRs should automatically be raised from zero (0) to /21 (2,048 IPv4 addresses) six months after they receive their first allocation. Because the sub-allocation policy references the AW policy, the sub-allocation policy also needs to be updated. This proposal suggests that the maximum sub-allocation should be kept at /20 (4,096 IPv4 addresses).

2006-06: IPv4 Maximum Allocation Period. This proposal is to have the RIPE NCC allocate address space to Local Internet Registries (LIRs) based on their one-year needs. In other words, it suggests setting a maximum allocation period of 12 months.

2006-04: Contact E-Mail Address Requirements. This proposal suggested that working and up-to-date contact e-mail addresses should be maintained at all times for address space that is registered in the RIPE Database.

2010-06: Registration Requirements for IPv6 End User Assignments. This proposal has two purposes: to create a new policy that defines the use of new attributes in the RIPE Database and to change the policy text of ripe-481 to require the use of these new database attributes

2010-02: This proposal describes how the RIPE NCC should distribute IPv4 address space from the final /8 address block it receives from the IANA. The proposal only discusses PA allocations; any other type of allocation or assignment is out of scope for this proposal.

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.

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.