- 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.
- Initial Certification Policy in the RIPE NCC Service Region
2008-08: The RIPE NCC plans to deploy a certification service that can be used to secure uniqueness of resources. This proposal lays out guidelines for how LIRs can receive certificates over their Provider Aggregatable (PA) address space holdings and how these certificates should be maintained.
- 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.
- Global Policy for post exhaustion IPv4 allocation mechanisms by the IANA
2011-01: This proposal describes the process that IANA will follow to allocate IPv4 resources to Regional Internet Registries (RIRs) after the central pool of addresses is exhausted. The processes for how IPv4 space may be placed in the IANA Recovered IPv4 Pool is out of the scope of this proposal
- Post-depletion IPv4 address recycling
2011-03: This proposal intends to define better how the address management of returned IPv4 address space will be performed when the final /8 policy comes into effect.
- Removal of multihomed requirement for IPv6 PI
2011-02: This proposal intends to remove the multihome requirement necessary to receive PI IPv6 address space in the policy ripe-538, “IPv6 Address Allocation and Assignment Policy”. There are enough End Users (businesses) that have a valid reason for their own address space, without the desire to become a LIR or multihoming.
- Inter-RIR IPv4 Address Transfers
2012-01: Inter-RIR IPv4 Address Transfers. This proposal is intended to allow IPv4 address space transfers between the RIPE NCC and other RIRs in order to supplement the pool of available IPv4 addresses.
- Extension of the Minimum Size for IPv6 Initial Allocation
2011-04: This proposal modifies the eligibility for an organisation to receive an initial IPv6 allocation up to a /29. This is in order to enable small LIRs to deploy IPv6 using “IPv6 Rapid Deployment”, also known as “6rd”, as defined in RFC 5969 in a manner that does not encourage issuing a single /64 to end customers when an LIR has a minimum allocation of /32.
- Safeguarding future IXPs with IPv4 space
2011-05: Safeguarding future IXPs with IPv4 space. This policy proposal will permit the operators in the RIPE NCC service region to continue building successful Internet Exchange Point communities after IPv4 depletion.