This policy proposal has been accepted
You're looking at an older version: 4
The current (published) version is 5This proposal introduced a solution for organisations that needed IPv6 Provider Independent (PI) address space.
This proposal introduces a solution for organisations that need IPv6 Provider Independent (PI) address space.
The PI assignment cannot be further assigned to other organisations.
a. Arguments Supporting the Proposal
At the moment there is no solution for the End User Organisations which require redundancy in IPv6. This is perceived as a clear barrier for deployment of IPv6 in some organisations. This policy proposal addresses that barrier by means of providing a direct assignment from the RIPE NCC.
All the other regions already have a policy for IPv6 PI address space.
By setting up this policy, we would avoid creating an unfair situation among different regions, and meet the needs of any organisation that required PI address space. All organisations that opt for the IPv6 PI address space will be in an equal position once the community agrees a long-term technical solution and will have to either move to this new solution or become an LIR, if they qualify.
b. Arguments Opposing the Proposal
The possible effect of this proposal is the growth of the global routing table to a level that, together with the existing and forecasted IPv4 routing entries, could create significant issues for operators unless vendors can provide products that address such issues. Even if such technical solutions were found, the proposal could still have a major impact on the cost and/or depreciation period for infrastructure investments.