--- 1/draft-ietf-v6ops-64share-03.txt 2013-04-06 01:56:34.276086229 +0200 +++ 2/draft-ietf-v6ops-64share-04.txt 2013-04-06 01:56:34.292086855 +0200 @@ -1,20 +1,20 @@ V6OPS Working Group C. Byrne Internet-Draft T-Mobile USA Intended Status: Informational D. Drown -Expires: August 24, 2013 A. Vizdal +Expires: October 7, 2013 A. Vizdal Deutsche Telekom AG - February 20, 2013 + April 5, 2013 Extending an IPv6 /64 Prefix from a 3GPP Mobile Interface to a LAN - draft-ietf-v6ops-64share-03 + draft-ietf-v6ops-64share-04 Abstract This document describes three methods for extending an IPv6 /64 prefix from a User Equipment 3GPP radio interface to a LAN. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. @@ -22,57 +22,57 @@ 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 August 24, 2013. + This Internet-Draft will expire on October 7, 2013. Copyright and License Notice Copyright (c) 2013 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 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. -V6OPS Working Group draft-ietf-v6ops-64share-03 February 20, 2013 +V6OPS Working Group draft-ietf-v6ops-64share-03 April 5, 2013 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. The Challenge of Providing IPv6 Addresses to a LAN via a 3GPP UE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Methods for Extending the 3GPP Interface /64 IPv6 Prefix to a LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.0 General Behavior for All Scenarios . . . . . . . . . . . . . 3 3.1 Scenario 1: No Global Address on the UE . . . . . . . . . . 4 3.2 Scenario 2: Global Address Only Assigned to LAN . . . . . . 5 3.3 Scenario 3: A Single Global Address Assigned to 3GPP Radio and LAN Interface . . . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7 7. Informative References . . . . . . . . . . . . . . . . . . . . 7 -V6OPS Working Group draft-ietf-v6ops-64share-03 February 20, 2013 +V6OPS Working Group draft-ietf-v6ops-64share-03 April 5, 2013 1. Introduction 3GPP mobile cellular networks such as GSM, UMTS, and LTE have architectural support for IPv6 [RFC6459], but only 3GPP Release-10 and onwards of the 3GPP specification supports DHCPv6 Prefix Delegation [RFC3633] for delegating IPv6 prefixes to a LAN. To facilitate the use of IPv6 in a LAN prior to the deployment of DHCPv6 Prefix Delegation in 3GPP networks and in User Equipment (UE), this document describes how the 3GPP UE radio interface assigned global @@ -109,21 +109,21 @@ described in this document should only be applied when deploying DHCPv6 Prefix Delegation is not achievable in the 3GPP network and the UE. 3. Methods for Extending the 3GPP Interface /64 IPv6 Prefix to a LAN 3.0 General Behavior for All Scenarios As [RFC6459] describes, the 3GPP network assigned /64 is completely -V6OPS Working Group draft-ietf-v6ops-64share-03 February 20, 2013 +V6OPS Working Group draft-ietf-v6ops-64share-03 April 5, 2013 dedicated to the UE and the gateway does not consume any of the /64 addresses. The gateway routes the entire /64 to the UE and does not perform ND or Network Unreachability Detection (NUD) [RFC4861]. Communication between the UE and the gateway is only done using link- local addresses and the link is point-to-point. This allows for the UE to reliably manipulate the /64 from the 3GPP radio interface without negatively impacting the point-to-point 3GPP radio link interface. The LAN interface RA configuration must be tightly coupled with the 3GPP interface state. If the 3GPP interface goes @@ -159,21 +159,21 @@ an IPv6 address. If the interface does not have an IPv6 address, an attempt will be made to acquire one, or else the procedure will terminate. 3. In this example, the UE finds the 3GPP interface has the IPv6 address 2001:db8:ac10:f002:1234:4567:0:9/64 assigned and active. 4. The UE copies the prefix 2001:db8:ac10:f002::/64 from the 3GPP interface to the LAN interface, removes the global IPv6 address -V6OPS Working Group draft-ietf-v6ops-64share-03 February 20, 2013 +V6OPS Working Group draft-ietf-v6ops-64share-03 April 5, 2013 configuration from the 3GPP radio interface, disables the IPv6 Stateless Address Autoconfiguration (SLAAC) [RFC4862] feature for global addresses on the 3GPP radio interface to avoid address autoconfiguration, and begins announcing the global prefix 2001:db8:ac10:f002::/64 via RA to the LAN. The 3GPP interface and LAN interface only maintain link-local addresses while the UE uses RA to announce the /64 to the LAN. 5. Since the UE and gateway do not assign any of the addresses from @@ -209,21 +209,21 @@ 2. The UE checks to make sure the 3GPP interface is active and has an IPv6 address. If the interface does not have an IPv6 address, an attempt will be made to acquire one, or else the procedure will terminate. 3. In this example, the UE finds the 3GPP interface has the IPv6 address 2001:db8:ac10:f002:1234:4567:0:9 assigned and active. 4. The UE moves the address 2001:db8:ac10:f002:1234:4567:0:9 as a -V6OPS Working Group draft-ietf-v6ops-64share-03 February 20, 2013 +V6OPS Working Group draft-ietf-v6ops-64share-03 April 5, 2013 /64 from the 3GPP interfaces to the LAN interface, disables the IPv6 SLAAC feature on the 3GPP radio interface to avoid address autoconfiguration, and begins announcing the prefix 2001:db8:ac10:f002::/64 via RA to the LAN. For this example, the LAN has 2001:db8:ac10:f002:1234:4567:0:9/64 and the 3GPP radio only has a link-local address. 5. The UE directly processes all packets destined to itself at 2001:db8:ac10:f002:1234:4567:0:9. @@ -239,41 +239,47 @@ 3.3 Scenario 3: A Single Global Address Assigned to 3GPP Radio and LAN Interface In this method, the UE assigns itself one address from the 3GPP network RA announced /64. This one address is configured as anycast [RFC4291] on both the 3GPP radio interface as a /128 and on the LAN interface as a /64. This allows the UE to maintain long lived data connections since the 3GPP radio interface address does not change when the router function is activated. This method may cause complications for certain software that may not support multiple - interfaces with the same anycast IPv6 address. This method also - creates complications for ensuring uniqueness for Privacy Extensions - [RFC4941]. Privacy Extensions should be disabled on the 3GPP radio - interface while this method is enabled. + interfaces with the same anycast IPv6 address or are sensitive to + prefix length changes. This method also creates complications for + ensuring uniqueness for Privacy Extensions [RFC4941]. Privacy + Extensions should be disabled on the 3GPP radio interface while this + method is enabled. + + There might also be more complex scenarios in which the prefix length + is not changed and privacy extensions are supported by having the + subnet span multiple interfaces, as ND Proxy does [RFC4389]. Further + elaboration is out of scope of the present document. Below is the general procedure for this scenario: 1. The user activates router functionality for a LAN on the UE. 2. The UE checks to make sure the 3GPP interfaces is active and has an IPv6 address. If the interface does not have an IPv6 address, + +V6OPS Working Group draft-ietf-v6ops-64share-03 April 5, 2013 + an attempt will be made to acquire one, or else the procedure will terminate. 3. In this example, the UE finds the 3GPP interface has the IPv6 address 2001:db8:ac10:f002:1234:4567:0:9 assigned and active. 4. The UE moves the address 2001:db8:ac10:f002:1234:4567:0:9 as an - -V6OPS Working Group draft-ietf-v6ops-64share-03 February 20, 2013 - anycast /64 from the 3GPP interface to the LAN interface and begins announcing the prefix 2001:db8:ac10:f002::/64 via RA to the LAN. The 3GPP interface maintains the same IPv6 anycast address with a /128. For this example, the LAN has 2001:db8:ac10:f002:1234:4567:0:9/64 and the 3GPP radio interface has 2001:db8:ac10:f002:1234:4567:0:9/128. 5. The UE directly processes all packets destined to itself at 2001:db8:ac10:f002:1234:4567:0:9. @@ -288,42 +294,43 @@ 3GPP interface, UEs that require this functionality must find an alternative method or only associate the IPv6 Privacy Extension procedure on the LAN. 5. IANA Considerations This document does not require any action from IANA. 6. Acknowledgments - Many thanks for review and discussion from Sylvain Decremps, Mark - Smith, Dmitry Anipko, Masanobu Kawashima, Teemu Savolainen, Mikael - Abrahamsson, Eric Vyncke, Alexandru Petrescu, Jouni Korhonen, and - Julien Laganier. + Many thanks for review and discussion from Dave Thaler, Sylvain + Decremps, Mark Smith, Dmitry Anipko, Masanobu Kawashima, Teemu + Savolainen, Mikael Abrahamsson, Eric Vyncke, Alexandru Petrescu, + Jouni Korhonen, and Julien Laganier. 7. Informative References [RFC1981] McCann, J., Deering, S., and J. Mogul, "Path MTU Discovery for IP version 6", RFC 1981, August 1996. [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6", RFC 3633, + +V6OPS Working Group draft-ietf-v6ops-64share-03 April 5, 2013 + December 2003. [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006. [RFC4389] Thaler, D., Talwar, M., and C. Patel, "Neighbor Discovery Proxies (ND Proxy)", RFC 4389, April 2006. -V6OPS Working Group draft-ietf-v6ops-64share-03 February 20, 2013 - [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, September 2007. [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless Address Autoconfiguration", RFC 4862, September 2007. [RFC4941] Narten, T., Draves, R., and S. Krishnan, "Privacy Extensions for Stateless Address Autoconfiguration in IPv6", RFC 4941, September 2007.