Document Actions
Policy Proposals
- 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.
- Allocating/Assigning Resources to the RIPE NCC
-
2009-02: This proposal sets out how the RIPE NCC can allocate/assign resources to itself.
- 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.
- 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.
- 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.
- Global Policy for IPv4 Allocation by the IANA Post Exhaustion
-
2010-05: This is a proposal to create a policy allowing for the allocation of IPv4 address space after the depletion of the IANA IPv4 address pool.
- Frequent Update Request
-
2010-09: This proposal suggests to have the minimum assignment size for PI assignments to be a /24 when routing is a major issue for a multihoming End User.
- Adding Reference to Sponsoring LIR in inetnum, inet6num and aut-num objects
-
2010-10: This is a proposal to add a reference to sponsoring LIR in inetnum, inet6num and aut-num objects to increase the possibility of abuse tracking and handling.
- Ensuring Efficient Use of Historical IPv4 Resources
-
2008-07: This was a proposal to require documentation of all address resources held when assessing a RIPE NCC member's eligibility for further IPv4 address space.