Revised IPv6 PI Assignment Policy

ummary of the Proposal This proposal aims to reduce operational burden operators working with PI experience, while clarifying long-standing issues in the IPv6 addressing policy.

ummary of the Proposal This proposal aims to reduce the operational burden that operators experience when working with PI.

ummary of the Proposal This proposal aims to reduce operational burden operators working with PI experience, while clarifying long-standing issues in the IPv6 addressing policy.

It also clarifies some long-standing issues in the IPv6 addressing policy.

Specifically, it makes the following changes: Separate notions of assignment requirements and End Sites for ‘PI Assignments’ and ‘Assignments from IPv6 Allocations to End Users’.

Specifically, it makes the following changes: Separates assignment requirements for ‘PI assignments’ from ‘assignments from IPv6 allocations to End Users’.

Clarify permitted and non-permitted use cases of PI Assignments.

Clarifies permitted and non-permitted use cases of PI assignments.

Clarify wording, definitions, and requirements in the text.

Clarifies wording, definitions, and requirements in the text.

Introduce PI Assignments at the Nibble boundary, an aggregation principle for PI, and registration in a single object for assignments.

Introduces PI assignments at the nibble boundary, an aggregation principle for PI, and registration in a single object for assignments.

Assignments must only be made for specific purposes documented by specific organisations, and it is not allowed to create further sub-assignments to another entity from address space partially or fully covering an assignment.

Assignments must only be made for specific purposes documented by specific organisations, and it is not allowed to fully or partially sub-assign them to another entity.

Providing connectivity to another entity inside the assignment holder’s network located at the same geographical End Site as the holder’s network with a prefix size of /56 or longer from the assignment is not considered a sub-assignment.

Providing connectivity to another entity inside the assignment holder’s network, at the same geographical End Site, with a prefix size of /56 or longer from the assignment, is not considered a sub-assignment.

This includes letting visitors connect to the assignment holder's network, providing static addresses when connecting a server or appliance to an assignment holder's network, providing a single service with multiple addresses, or using a /64 or longer when setting up point-to-point links with other ISPs for the purpose of exchanging traffic and Internet routing information.

This includes letting visitors connect to the assignment holder's network, providing static addresses when connecting a server or appliance to the assignment holder's network, providing a single service with multiple addresses, or using a /64 or longer when setting up point-to-point links with other ISPs for the purpose of exchanging traffic and Internet routing information.

Finally, using more specific prefixes from a less-specific assignment for different parts of the same infrastructure within one organisation does not constitute a sub-assignment, if the purpose of the assignment is the operation of that infrastructure.

Finally, using more specific prefixes from a less-specific assignment for different parts of the same infrastructure within one organisation does not constitute a sub-assignment, provided the purpose of the assignment is the operation of that infrastructure.

Any other use of a prefix from an assignment up to prefixes of /128 bit to connect a separate End Site of another entity to the Internet always constitutes a prohibited sub-assignment.

Any other use of a prefix from an assignment (up to prefixes of /128) to connect the separate End Site of another entity to the Internet constitutes a prohibited sub-assignment.

2.6 Purpose and Considerations 2.6 Purpose: Clarify that even assignment holders may, for example, host a customer’s server or VM in their network, providing more than a single IPv6 address as common for IPv6 (at least /64).

Any other use of a prefix from an assignment (up to prefixes of /128) to connect the separate End Site of another entity to the Internet constitutes a prohibited sub-assignment. 5.4 Current policy text 5.4 Assignment 5.4.2.

This includes letting visitors connect to the assignment holder's network, providing static addresses when connecting a server or appliance to the assignment holder's network, providing a single service with multiple addresses, or using a /64 or longer when setting up point-to-point links with other ISPs for the purpose of exchanging traffic and Internet routing information.

This includes letting visitors connect to the assignment holder's network, providing persistent addresses when connecting a server or appliance to the assignment holder's network, providing a single service with multiple addresses, or using a /64 or longer when setting up point-to-point links with other ISPs for the purpose of exchanging traffic and Internet routing information.

Any other use of a prefix from an assignment (up to prefixes of /128) to connect the separate End Site of another entity to the Internet constitutes a prohibited sub-assignment.

Any other use of a prefix from an assignment (up to prefixes of /128) to connect the separate End Site of another entity to the Internet without the exchange of Internet routing information constitutes a prohibited sub-assignment.

Purposes Clarifying PI assignment scope Assignment holders may assign more than a single IPv6 address (/64) for custom servers/VMs within their End Site, static prefixes and routable prefixes.

Purposes Clarifying PI assignment scope Assignment holders may assign more than a single IPv6 address (/64) for custom servers/VMs within their End Site, persistent prefixes and routable prefixes.