draft-ietf-v6ops-unique-ipv6-prefix-per-host-09.txt   draft-ietf-v6ops-unique-ipv6-prefix-per-host-10.txt 
v6ops J. Brzozowski v6ops J. Brzozowski
Internet-Draft Comcast Cable Internet-Draft Comcast Cable
Intended status: Best Current Practice G. Van De Velde Intended status: Best Current Practice G. Van De Velde
Expires: March 18, 2018 Nokia Expires: March 22, 2018 Nokia
September 14, 2017 September 18, 2017
Unique IPv6 Prefix Per Host Unique IPv6 Prefix Per Host
draft-ietf-v6ops-unique-ipv6-prefix-per-host-09 draft-ietf-v6ops-unique-ipv6-prefix-per-host-10
Abstract Abstract
This document outlines an approach utilising existing IPv6 protocols This document outlines an approach utilising existing IPv6 protocols
to allow hosts to be assigned a unique IPv6 prefix (instead of a to allow hosts to be assigned a unique IPv6 prefix (instead of a
unique IPv6 address from a shared IPv6 prefix). Benefits of unique unique IPv6 address from a shared IPv6 prefix). Benefits of unique
IPv6 prefix over a unique service provider IPv6 address include IPv6 prefix over a unique service provider IPv6 address include
improved host isolation and enhanced subscriber management on shared improved host isolation and enhanced subscriber management on shared
network segments. network segments.
skipping to change at page 1, line 36 skipping to change at page 1, line 36
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 18, 2018. This Internet-Draft will expire on March 22, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 17 skipping to change at page 2, line 17
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Motivation and Scope of Applicability . . . . . . . . . . . . 3 2. Motivation and Scope of Applicability . . . . . . . . . . . . 3
3. Design Principles . . . . . . . . . . . . . . . . . . . . . . 4 3. Design Principles . . . . . . . . . . . . . . . . . . . . . . 4
4. IPv6 Unique Prefix Assignment . . . . . . . . . . . . . . . . 4 4. IPv6 Unique Prefix Assignment . . . . . . . . . . . . . . . . 4
5. IPv6 Neighbor Discovery Best Practices . . . . . . . . . . . 6 5. IPv6 Neighbor Discovery Best Practices . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 7 7. Security Considerations . . . . . . . . . . . . . . . . . . . 7
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
9. Normative References . . . . . . . . . . . . . . . . . . . . 8 9. Normative References . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
The concepts in this document are originally developed as part of a The concepts in this document are originally developed as part of a
large scale, production deployment of IPv6 support for a provider large scale, production deployment of IPv6 support for a provider
managed shared access network service. managed shared access network service.
A shared network service, is a service offering where a particular L2 A shared network service, is a service offering where a particular L2
skipping to change at page 4, line 51 skipping to change at page 4, line 51
IPv6 gateway, the IPv6 prefix information, the DNS information IPv6 gateway, the IPv6 prefix information, the DNS information
RFC8106 [RFC8106], and the remaining information required to RFC8106 [RFC8106], and the remaining information required to
establish globally routable IPv6 connectivity. For that purpose, the establish globally routable IPv6 connectivity. For that purpose, the
the subscriber sends a RS (Router Solicitation) message. the subscriber sends a RS (Router Solicitation) message.
The First Hop Router receives this subscriber RS message and starts The First Hop Router receives this subscriber RS message and starts
the process to compose the response to the subscriber originated RS the process to compose the response to the subscriber originated RS
message. The First Hop Provider Router will answer using a solicited message. The First Hop Provider Router will answer using a solicited
RA (Router Advertisement) to the subscriber. RA (Router Advertisement) to the subscriber.
When the First Hop Provider Router sends the solicited RA response, When the First Hop Provider Router sends a solicited RA response, or
or a periodic unsolicited RA, the RA MUST be sent only to the UE/ periodically sends unsolicited RAs, the RA MUST be sent only to the
subscriber that has been assigned the Unique IPv6 prefix contained in subscriber that has been assigned the Unique IPv6 prefix contained in
the RA. This is achieved by sending a unicast RA response, as the RA. This is achieved by sending a solicited RA response or
detailed in [RFC4861] section 6.2.6, or by sending a multicast RA unsolicited RAs to the all-nodes group, as detailed in RFC4861
response or unsolicited RA to the all-nodes group, as detailed in
[RFC4861] section 6.2.4 and 6.2.6, but instead of using the link- [RFC4861] section 6.2.4 and 6.2.6, but instead of using the link-
layer multicast address associated with the all-nodes group, the layer multicast address associated with the all-nodes group, the
link-layer unicast address of the UE/subscriber that has been link-layer unicast address of the subscriber that has been assigned
assigned the Unique IPv6 prefix contained in the RA MUST be used as the Unique IPv6 prefix contained in the RA MUST be used as the link-
the link-layer destination RFC6085 [RFC6085]. layer destination RFC6085 [RFC6085]. Or, optionally in some cases, a
solicited RA response could be sent unicast to the link-local address
of the subscriber as detailed in RFC4861 [RFC4861] section 6.2.6,
nevertheless unsolicited RAs are always sent to the all-nodes group.
This solicited RA contains two important parameters for the EU/ This solicited RA contains two important parameters for the
subscriber to consume: a Unique IPv6 prefix (currently a /64 prefix) subscriber to consume: a Unique IPv6 prefix (currently a /64 prefix)
and some flags. The Unique IPv6 prefix can be derived from a locally and some flags. The Unique IPv6 prefix can be derived from a locally
managed pool or aggregate IPv6 block assigned to the First Hop managed pool or aggregate IPv6 block assigned to the First Hop
Provider Router or from a centrally allocated pool. The flags Provider Router or from a centrally allocated pool. The flags
indicate to the subscriber to use SLAAC and/or DHCPv6 for address indicate to the subscriber to use SLAAC and/or DHCPv6 for address
assignment; it may indicate if the autoconfigured address is on/off- assignment; it may indicate if the autoconfigured address is on/off-
link and if 'Other' information (e.g. DNS server address) needs to link and if 'Other' information (e.g. DNS server address) needs to
be requested. be requested.
The IPv6 RA flags used for best common practice in IPv6 SLAAC based The IPv6 RA flags used for best common practice in IPv6 SLAAC based
 End of changes. 8 change blocks. 
14 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/