RIPE Policy Proposal 2009-08

This proposal is to allow LIRs to receive IPv6 PI assignments in addition to an IPv6 allocation.

[Following text is to appear in the RIPE Policy document IPv6 Address Allocation and Assignment Policy, if the proposal reaches consensus.]

8.a <removed by this proposal>
8.1. IPv6 Provider Independent (PI) Assignments for LIRs

LIRs can qualify for an IPv6 PI assignment for parts of their own infrastructure, which are not be used for customer end sites. Where an LIR has an IPv6 allocation, the LIR must demonstrate the unique routing requirements for the PI assignment.

The LIR must return the IPv6 PI assignment within a period of six months should the unique routing requirements for the PI assignment no longer be met.

If an organisation already received a PI assignment before becoming an LIR, the PI assignment should be returned upon receiving an IPv6 allocation if there are no specific routing requirements to justify both.

a. Arguments Supporting the Proposal

LIRs with a need for a different routing policy currently do not qualify for an IPv6 PI assignment. End Users do have that option under the current IPv6 policy:

"Additional assignments may also be made when the need is demonstrated and documented based on address usage, or because different routing requirements exist for additional assignments. When possible, these further assignments will be made from an adjacent address block."

An LIR may need to run two discrete networks for some load balancing, resilience, and continuity applications. They may have PA for their usual services, and for making assignments to End Users, and PI for their own infrastructure or services, which must be announced independently.

b. Arguments Opposing the Proposal

There may be negative effects on the routing table growth.