Your IP address is 3.233.219.62

Filters

Clarification on IPv6 Sub-Assignments

Details
  • Ref. Name:AFPUB-2018-V6-002-DRAFT01
  • Submitted:14 March 2018
  • Versions: 1.0
  • Amends: CPM art 6.8
  • Obsoletes:
  • Author:
    - Jordi Palet Martinez, jordi.palet[at]theipv6company.com  The IPv6 Company

1.0 Summary of the Problem Being Addressed by this Policy Proposal

When the policy was drafted, the concept of assignments/sub-assignments did not consider a practice very common in IPv4 which is replicated and even amplified in IPv6: the use of IP addresses for point-to-point links or VPNs.

In the case of IPv6, instead of unique addresses, the use of unique prefixes (/64) is increasingly common.

Likewise, the policy failed to consider the use of IP addresses in hotspots, or the use of IP addresses by guests or employees in Bring Your Own Device (BYOD) and many other similar cases.

Finally, the IETF has recently approved the use of a unique /64 prefix per interface/host (RFC8273) instead of a unique address. This, for example, allows users to connect to a hotspot, receive a /64 such that they are “isolated” from other users (for reasons of security, regulatory requirements, etc.) and they can also use multiple virtual machines on their devices with a unique address for each one (within the same /64).

 

2.0 Summary of how this proposal addresses the problem

Section 2.6 (General Definitions/Assignment), explicitly prohibits such assignments, stating that “Assignments... are not to be sub-assigned to other parties”.

This proposal clarifies this situation in this regard and better define the concept, particularly considering new uses of IPv6 (RFC 8273), by means of new text at the end of whatever text is available at the IPv6 PI assignments policy.

 

3. Proposal

New Paragraph at the end of 6.8 of the CPM, as follows:

Current Proposed

6.8 PI Assignments

(at the end of the section, precedent text unchanged by this proposal)

6.8 PI Assignments

(at the end of the section, precedent text unchanged by this proposal)

The fact that a unique address or even a unique /64 prefix is non-permanently provided to third parties, on a link operated by the original receiver of the assignment, shall not be considered a sub-assignment. This includes, for example, guests or employees (devices or servers), hotspots, and point-to-point links or VPNs. The provision of addressing for permanent connectivity or broadband services is still considered a sub-assignment. Only the addressing of the point-to-point link itself can be permanent and that addressing can't be used (neither directly or indirectly) for the actual communication.

 

4. Revision History

Date Details

20 March 2018

Version 1: AFPUB-2018-V6-002-DRAFT01

Initial Draft Posted to rpd

 

5. References

A similar proposal has been discussed in the RIPE region and is waiting for forum chairs to declare consensus.

Discussions are taking place on the policy working group mailing list if you want to subscribe to the mailing send your subscription request to rpd-request [at] afrinic.net with 'Subscribe' as subject line


Mailing list archives can be found at https://lists.afrinic.net/pipermail/rpd