--- 1/draft-ietf-v6ops-64share-06.txt 2013-05-17 21:14:21.512591078 +0100 +++ 2/draft-ietf-v6ops-64share-07.txt 2013-05-17 21:14:21.532591580 +0100 @@ -1,20 +1,20 @@ V6OPS Working Group C. Byrne Internet-Draft T-Mobile USA Intended Status: Informational D. Drown Expires: November 18, 2013 A. Vizdal Deutsche Telekom AG May 17, 2013 Extending an IPv6 /64 Prefix from a 3GPP Mobile Interface to a LAN - draft-ietf-v6ops-64share-06 + draft-ietf-v6ops-64share-07 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. @@ -39,56 +39,56 @@ 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-06 May 17, 2013 +V6OPS Working Group draft-ietf-v6ops-64share-07 May 17, 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.0 General Behavior for All Scenarios . . . . . . . . . . . . . 4 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-06 May 17, 2013 +V6OPS Working Group draft-ietf-v6ops-64share-07 May 17, 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 /64 prefix may be extended from the 3GPP radio interface to a LAN. This is achieved by receiving the Router Advertisement (RA) [RFC4861] announced globally unique /64 IPv6 prefix from the 3GPP radio interface and then advertising the same IPv6 prefix to the LAN with RA. For all of the cases in the scope of this document, the UE may - be any device that function as an IPv6 router between the 3GPP + be any device that functions as an IPv6 router between the 3GPP network and a LAN. This document describes three methods for achieving IPv6 prefix extension from a 3GPP radio interface to a LAN including: 1) The 3GPP UE does not have a global scope IPv6 address on any interface, only link-local IPv6 addresses are present on the UE 2) The 3GPP UE only has a global scope address on the LAN interface 3) The 3GPP UE maintains the same consistent 128 bit global scope IPv6 anycast address [RFC4291] on the 3GPP radio interface and the @@ -106,24 +106,24 @@ Neighbor Discovery Proxy (ND Proxy) [RFC4389] functionality has been suggested as an option for extending the assigned /64 from the 3GPP radio interface to the LAN, but ND Proxy is an experimental protocol and has some limitations with loop-avoidance. DHCPv6 is the best way to delegate a prefix to a LAN. The methods described in this document should only be applied when deploying DHCPv6 Prefix Delegation is not achievable in the 3GPP network and the UE. The methods described in this document are at various stages of implementation and deployment planning. The goal of this memo is - to document the available methods which may used prior to DHCPv6 + to document the available methods which may be used prior to DHCPv6 deployment. -V6OPS Working Group draft-ietf-v6ops-64share-06 May 17, 2013 +V6OPS Working Group draft-ietf-v6ops-64share-07 May 17, 2013 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 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- @@ -159,21 +159,21 @@ 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 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. -V6OPS Working Group draft-ietf-v6ops-64share-06 May 17, 2013 +V6OPS Working Group draft-ietf-v6ops-64share-07 May 17, 2013 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 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 @@ -209,21 +209,21 @@ 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 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. -V6OPS Working Group draft-ietf-v6ops-64share-06 May 17, 2013 +V6OPS Working Group draft-ietf-v6ops-64share-07 May 17, 2013 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 /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 @@ -256,21 +256,21 @@ 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: -V6OPS Working Group draft-ietf-v6ops-64share-06 May 17, 2013 +V6OPS Working Group draft-ietf-v6ops-64share-07 May 17, 2013 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, 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. @@ -306,21 +306,21 @@ 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 -V6OPS Working Group draft-ietf-v6ops-64share-06 May 17, 2013 +V6OPS Working Group draft-ietf-v6ops-64share-07 May 17, 2013 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, December 2003. [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006.