--- 1/draft-ietf-v6ops-unique-ipv6-prefix-per-host-05.txt 2017-06-30 09:14:05.958017049 -0700 +++ 2/draft-ietf-v6ops-unique-ipv6-prefix-per-host-06.txt 2017-06-30 09:14:05.982017619 -0700 @@ -1,19 +1,19 @@ v6ops J. Brzozowski Internet-Draft Comcast Cable Intended status: Informational G. Van De Velde -Expires: December 28, 2017 Nokia - June 26, 2017 +Expires: January 1, 2018 Nokia + June 30, 2017 Unique IPv6 Prefix Per Host - draft-ietf-v6ops-unique-ipv6-prefix-per-host-05 + draft-ietf-v6ops-unique-ipv6-prefix-per-host-06 Abstract In some IPv6 environments, the need has arisen for hosts to be able to utilize a unique IPv6 prefix, even though the link or media may be shared. Typically hosts (subscribers) on a shared network, either wired or wireless, such as Ethernet, WiFi, etc., will acquire unique IPv6 addresses from a common IPv6 prefix that is allocated or assigned for use on a specific link. @@ -39,21 +39,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on December 28, 2017. + This Internet-Draft will expire on January 1, 2018. Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -177,45 +177,45 @@ IPv6 gateway, the IPv6 prefix information, the DNS information RFC8106 [RFC8106], and the remaining information required to establish globally routable IPv6 connectivity. For that purpose, the the UE/subscriber sends a RS (Router Solicitation) message. The First Hop Router receives this UE/subscriber RS message and starts the process to compose the response to the UE/subscriber originated RS message. The First Hop Provider Router will answer using a unicast RA (Router Advertisement) to the UE/subscriber. This RA contains two important parameters for the EU/subscriber to - consume: (1) a Unique IPv6 prefix (most likely a /64 prefix - consistent with RFC7608 [RFC7608]) and (2) flags. The Unique IPv6 - prefix can be derived from a locally managed pool or aggregate IPv6 - block assigned to the First Hop Provider Router or from a centrally - allocated pool. The flags indicate to the UE/subscriber to use SLAAC - and/or DHCPv6 for address assignment; it may indicate if the - autoconfigured address is on/off-link and if 'Other' information - (e.g. DNS server address) needs to be requested. + consume: a Unique IPv6 prefix (currently a /64 prefix) and some + flags. The Unique IPv6 prefix can be derived from a locally managed + pool or aggregate IPv6 block assigned to the First Hop Provider + Router or from a centrally allocated pool. The flags indicate to the + UE/subscriber to use SLAAC and/or DHCPv6 for address assignment; it + may indicate if the autoconfigured address is on/off-link and if + 'Other' information (e.g. DNS server address) needs to be requested. The IPv6 RA flags used for best common practice in IPv6 SLAAC based Provider managed shared networks are: o M-flag = 0 (UE/subscriber address is not managed through DHCPv6), this flag may be set to 1 in the future if/when DHCPv6 prefix delegation support is desired) o O-flag = 1 (DHCPv6 is used to request configuration information i.e. DNS, NTP information, not for IPv6 addressing) o A-flag = 1 (The UE/subscriber can configure itself using SLAAC) o L-flag = 0 (the prefix is not an on-link prefix, which means that the UE/subscriber will NEVER assume destination addresses that match the prefix are on-link and will ALWAYS send packets to those - addresses to its default gateway.) + addresses to the appropriate gateway according to route selection + rules.) The use of a unique IPv6 prefix per UE adds an additional level of protection and efficiency as it relates to how IPv6 Neighbor Discovery and Router Discovery processing. Since the UE has a unique IPv6 prefix all traffic by default will be directed to the First Hop provider router. Further, the flag combinations documented above maximise the IPv6 configurations that are available by hosts including the use of privacy IPv6 addressing. The architected result of designing the RA as documented above is @@ -343,25 +343,20 @@ [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless Address Autoconfiguration", RFC 4862, DOI 10.17487/RFC4862, September 2007, . [RFC4941] Narten, T., Draves, R., and S. Krishnan, "Privacy Extensions for Stateless Address Autoconfiguration in IPv6", RFC 4941, DOI 10.17487/RFC4941, September 2007, . - [RFC7608] Boucadair, M., Petrescu, A., and F. Baker, "IPv6 Prefix - Length Recommendation for Forwarding", BCP 198, RFC 7608, - DOI 10.17487/RFC7608, July 2015, - . - [RFC7934] Colitti, L., Cerf, V., Cheshire, S., and D. Schinazi, "Host Address Availability Recommendations", BCP 204, RFC 7934, DOI 10.17487/RFC7934, July 2016, . [RFC8106] Jeong, J., Park, S., Beloeil, L., and S. Madanapalli, "IPv6 Router Advertisement Options for DNS Configuration", RFC 8106, DOI 10.17487/RFC8106, March 2017, .