draft-ietf-v6ops-64share-04.txt   draft-ietf-v6ops-64share-05.txt 
V6OPS Working Group C. Byrne V6OPS Working Group C. Byrne
Internet-Draft T-Mobile USA Internet-Draft T-Mobile USA
Intended Status: Informational D. Drown Intended Status: Informational D. Drown
Expires: October 7, 2013 A. Vizdal Expires: November 18, 2013 A. Vizdal
Deutsche Telekom AG Deutsche Telekom AG
April 5, 2013 May 17, 2013
Extending an IPv6 /64 Prefix from a 3GPP Mobile Interface to a LAN Extending an IPv6 /64 Prefix from a 3GPP Mobile Interface to a LAN
draft-ietf-v6ops-64share-04 draft-ietf-v6ops-64share-05
Abstract Abstract
This document describes three methods for extending an IPv6 /64 This document describes three methods for extending an IPv6 /64
prefix from a User Equipment 3GPP radio interface to a LAN. prefix from a User Equipment 3GPP radio interface to a LAN.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 October 7, 2013. This Internet-Draft will expire on November 18, 2013.
Copyright and License Notice Copyright and License Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
V6OPS Working Group draft-ietf-v6ops-64share-03 April 5, 2013 V6OPS Working Group draft-ietf-v6ops-64share-05 May 17, 2013
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Challenge of Providing IPv6 Addresses to a LAN via a 3GPP 2. The Challenge of Providing IPv6 Addresses to a LAN via a 3GPP
UE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 UE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Methods for Extending the 3GPP Interface /64 IPv6 Prefix to a 3. Methods for Extending the 3GPP Interface /64 IPv6 Prefix to a
LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.0 General Behavior for All Scenarios . . . . . . . . . . . . . 3 3.0 General Behavior for All Scenarios . . . . . . . . . . . . . 4
3.1 Scenario 1: No Global Address on the UE . . . . . . . . . . 4 3.1 Scenario 1: No Global Address on the UE . . . . . . . . . . 4
3.2 Scenario 2: Global Address Only Assigned to LAN . . . . . . 5 3.2 Scenario 2: Global Address Only Assigned to LAN . . . . . . 5
3.3 Scenario 3: A Single Global Address Assigned to 3GPP Radio 3.3 Scenario 3: A Single Global Address Assigned to 3GPP Radio
and LAN Interface . . . . . . . . . . . . . . . . . . . . . 6 and LAN Interface . . . . . . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Informative References . . . . . . . . . . . . . . . . . . . . 7 7. Informative References . . . . . . . . . . . . . . . . . . . . 7
V6OPS Working Group draft-ietf-v6ops-64share-03 April 5, 2013 V6OPS Working Group draft-ietf-v6ops-64share-05 May 17, 2013
1. Introduction 1. Introduction
3GPP mobile cellular networks such as GSM, UMTS, and LTE have 3GPP mobile cellular networks such as GSM, UMTS, and LTE have
architectural support for IPv6 [RFC6459], but only 3GPP Release-10 architectural support for IPv6 [RFC6459], but only 3GPP Release-10
and onwards of the 3GPP specification supports DHCPv6 Prefix and onwards of the 3GPP specification supports DHCPv6 Prefix
Delegation [RFC3633] for delegating IPv6 prefixes to a LAN. To Delegation [RFC3633] for delegating IPv6 prefixes to a LAN. To
facilitate the use of IPv6 in a LAN prior to the deployment of DHCPv6 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 Prefix Delegation in 3GPP networks and in User Equipment (UE), this
document describes how the 3GPP UE radio interface assigned global document describes how the 3GPP UE radio interface assigned global
/64 prefix may be extended from the 3GPP radio interface to a LAN. /64 prefix may be extended from the 3GPP radio interface to a LAN.
This is achieved by receiving the Router Advertisement (RA) [RFC4861] This is achieved by receiving the Router Advertisement (RA) [RFC4861]
announced globally unique /64 IPv6 prefix from the 3GPP radio announced globally unique /64 IPv6 prefix from the 3GPP radio
interface and then advertising the same IPv6 prefix to the LAN with interface and then advertising the same IPv6 prefix to the LAN with
RA. RA. As in this case, the UE may be any device that can be function
as an IPv6 router.
This document describes three methods for achieving IPv6 prefix This document describes three methods for achieving IPv6 prefix
extension from a 3GPP radio interface to a LAN including: 1) The 3GPP extension from a 3GPP radio interface to a LAN including:
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 1) The 3GPP UE does not have a global scope IPv6 address on any
has a global scope address on the LAN interface 3) The 3GPP UE interface, only link-local IPv6 addresses are present on the UE
maintains the same consistent 128 bit global scope IPv6 anycast 2) The 3GPP UE only has a global scope address on the LAN interface
address [RFC4291] on the 3GPP radio interface and the LAN interface. 3) The 3GPP UE maintains the same consistent 128 bit global scope
The LAN interface is configured as a /64 and the 3GPP radio interface IPv6 anycast address [RFC4291] on the 3GPP radio interface and the
is configured as a /128. LAN interface. The LAN interface is configured as a /64 and the
3GPP radio interface is configured as a /128.
Section 3 describes the characteristics of each of the three Section 3 describes the characteristics of each of the three
approaches. approaches.
2. The Challenge of Providing IPv6 Addresses to a LAN via a 3GPP UE 2. The Challenge of Providing IPv6 Addresses to a LAN via a 3GPP UE
As described in [RFC6459], 3GPP networks assign a /64 global scope As described in [RFC6459], 3GPP networks assign a /64 global scope
prefix to each UE using RA. DHCPv6 Prefix Delegation is an optional prefix to each UE using RA. DHCPv6 Prefix Delegation is an optional
part of 3GPP Release-10 and is not covered by any earlier releases. part of 3GPP Release-10 and is not covered by any earlier releases.
Neighbor Discovery Proxy (ND Proxy) [RFC4389] functionality has been Neighbor Discovery Proxy (ND Proxy) [RFC4389] functionality has been
suggested as an option for extending the assigned /64 from the 3GPP suggested as an option for extending the assigned /64 from the 3GPP
radio interface to the LAN, but ND Proxy is an experimental protocol radio interface to the LAN, but ND Proxy is an experimental protocol
and has some limitations with loop-avoidance. and has some limitations with loop-avoidance.
DHCPv6 is the best way to delegate a prefix to a LAN. The methods DHCPv6 is the best way to delegate a prefix to a LAN. The methods
described in this document should only be applied when deploying described in this document should only be applied when deploying
DHCPv6 Prefix Delegation is not achievable in the 3GPP network and DHCPv6 Prefix Delegation is not achievable in the 3GPP network and
the UE. the UE. The methods described in this document are at various stages
of implementation and deployment planning. The goal of the document
is create a common understanding of the available methods which may
used prior to DHCPv6 deployment.
V6OPS Working Group draft-ietf-v6ops-64share-05 May 17, 2013
3. Methods for Extending the 3GPP Interface /64 IPv6 Prefix to a LAN 3. Methods for Extending the 3GPP Interface /64 IPv6 Prefix to a LAN
3.0 General Behavior for All Scenarios 3.0 General Behavior for All Scenarios
As [RFC6459] describes, the 3GPP network assigned /64 is completely As [RFC6459] describes, the 3GPP network assigned /64 is completely
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 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 addresses. The gateway routes the entire /64 to the UE and does not
perform ND or Network Unreachability Detection (NUD) [RFC4861]. perform ND or Network Unreachability Detection (NUD) [RFC4861].
Communication between the UE and the gateway is only done using link- 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 local addresses and the link is point-to-point. This allows for the
UE to reliably manipulate the /64 from the 3GPP radio interface UE to reliably manipulate the /64 from the 3GPP radio interface
without negatively impacting the point-to-point 3GPP radio link without negatively impacting the point-to-point 3GPP radio link
interface. The LAN interface RA configuration must be tightly interface. The LAN interface RA configuration must be tightly
coupled with the 3GPP interface state. If the 3GPP interface goes coupled with the 3GPP interface state. If the 3GPP interface goes
down or changes the IPv6 prefix, that state should be reflected in down or changes the IPv6 prefix, that state should be reflected in
the LAN IPv6 configuration. Just as in a standard IPv6 router, the the LAN IPv6 configuration. Just as in a standard IPv6 router, the
packet TTL will be decremented when passing packets between packet TTL will be decremented when passing packets between
interfaces across the UE. The RA function on the UE is exclusively interfaces across the UE. The RA function on the UE is exclusively
run on the LAN interface. run on the LAN interface.
3.1 Scenario 1: No Global Address on the UE 3.1 Scenario 1: No Global Address on the UE
In this case, the UE receives the /64 from the 3GPP network via RA In this case, the UE receives the /64 from the 3GPP network via RA
and simply configures Neighbor Discovery Protocol (NDP) [RFC4861] on and simply configures Neighbor Discovery Protocol (NDP) [RFC4861] on
the LAN interface to announce the /64 via RA. The UE shall not run the LAN interface to announce the /64 via RA. The UE forwards all
Stateless Address Autoconfiguration [RFC4862] to assign a global traffic destine to the /64 out of the LAN interface. The UE shall
address on the 3GPP radio interface while routing is enabled. The not run Stateless Address Autoconfiguration [RFC4862] to assign a
3GPP UE does not assign itself any global IPv6 addresses. The UE global address on the 3GPP radio interface while routing is enabled.
cannot originate or terminate any global scope packets in this case The 3GPP UE does not assign itself any global IPv6 addresses. Lack
since it does not have a global scope IPv6 address to source or of global scope connectivity will limit network services running on
receive packets. The LAN attached devices have complete access to the the UE (e.g. DNS caching that requires global connectivity) and
/64, but the 3GPP UE only has link-local addresses. prevent proper Path MTU Discovery [RFC1981] to occur on the UE. The
LAN attached devices have complete access to the /64, but the 3GPP UE
only has link-local addresses.
This method is appropriate for a use-case where the UE is effectively This method is appropriate for a use-case where the UE is only an
an IPv6 router that does not require any global connectivity. Lack IPv6 router that does not require any global connectivity.
of global scope connectivity will prevent proper Path MTU Discovery
[RFC1981] to occur on the UE.
Below is the general procedure for this scenario: Below is the general procedure for this scenario:
1. The user activates router functionality for a LAN on the UE. 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 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 IPv6 address. If the interface does not have an IPv6 address,
an attempt will be made to acquire one, or else the procedure an attempt will be made to acquire one, or else the procedure
will terminate. will terminate.
V6OPS Working Group draft-ietf-v6ops-64share-05 May 17, 2013
3. In this example, the UE finds the 3GPP interface has the IPv6 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. 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 4. The UE copies the prefix 2001:db8:ac10:f002::/64 from the 3GPP
interface to the LAN interface, removes the global IPv6 address interface to the LAN interface, removes the global IPv6 address
V6OPS Working Group draft-ietf-v6ops-64share-03 April 5, 2013
configuration from the 3GPP radio interface, disables the IPv6 configuration from the 3GPP radio interface, disables the IPv6
Stateless Address Autoconfiguration (SLAAC) [RFC4862] feature for Stateless Address Autoconfiguration (SLAAC) [RFC4862] feature for
global addresses on the 3GPP radio interface to avoid address global addresses on the 3GPP radio interface to avoid address
autoconfiguration, and begins announcing the global prefix autoconfiguration, and begins announcing the global prefix
2001:db8:ac10:f002::/64 via RA to the LAN. The 3GPP interface 2001:db8:ac10:f002::/64 via RA to the LAN. The 3GPP interface
and LAN interface only maintain link-local addresses while the UE and LAN interface only maintain link-local addresses while the UE
uses RA to announce the /64 to the LAN. uses RA to announce the /64 to the LAN.
5. Since the UE and gateway do not assign any of the addresses from 5. Since the UE and gateway do not assign any of the addresses from
the /64, there is no chance of an address conflict on the 3GPP the /64, there is no chance of an address conflict on the 3GPP
skipping to change at page 5, line 50 skipping to change at page 6, line 5
Below is the general procedure for this scenario: Below is the general procedure for this scenario:
1. The user activates router functionality for a LAN on the UE. 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 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 IPv6 address. If the interface does not have an IPv6 address,
an attempt will be made to acquire one, or else the procedure an attempt will be made to acquire one, or else the procedure
will terminate. will terminate.
V6OPS Working Group draft-ietf-v6ops-64share-05 May 17, 2013
3. In this example, the UE finds the 3GPP interface has the IPv6 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. 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 4. The UE moves the address 2001:db8:ac10:f002:1234:4567:0:9 as a
V6OPS Working Group draft-ietf-v6ops-64share-03 April 5, 2013
/64 from the 3GPP interfaces to the LAN interface, disables the /64 from the 3GPP interfaces to the LAN interface, disables the
IPv6 SLAAC feature on the 3GPP radio interface to avoid address IPv6 SLAAC feature on the 3GPP radio interface to avoid address
autoconfiguration, and begins announcing the prefix autoconfiguration, and begins announcing the prefix
2001:db8:ac10:f002::/64 via RA to the LAN. For this example, the 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 LAN has 2001:db8:ac10:f002:1234:4567:0:9/64 and the 3GPP radio
only has a link-local address. only has a link-local address.
5. The UE directly processes all packets destined to itself at 5. The UE directly processes all packets destined to itself at
2001:db8:ac10:f002:1234:4567:0:9. 2001:db8:ac10:f002:1234:4567:0:9.
skipping to change at page 6, line 48 skipping to change at page 7, line 5
Extensions should be disabled on the 3GPP radio interface while this Extensions should be disabled on the 3GPP radio interface while this
method is enabled. method is enabled.
There might also be more complex scenarios in which the prefix length There might also be more complex scenarios in which the prefix length
is not changed and privacy extensions are supported by having the is not changed and privacy extensions are supported by having the
subnet span multiple interfaces, as ND Proxy does [RFC4389]. Further subnet span multiple interfaces, as ND Proxy does [RFC4389]. Further
elaboration is out of scope of the present document. elaboration is out of scope of the present document.
Below is the general procedure for this scenario: Below is the general procedure for this scenario:
V6OPS Working Group draft-ietf-v6ops-64share-05 May 17, 2013
1. The user activates router functionality for a LAN on the UE. 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 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 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 an attempt will be made to acquire one, or else the procedure
will terminate. will terminate.
3. In this example, the UE finds the 3GPP interface has the IPv6 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. 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 4. The UE moves the address 2001:db8:ac10:f002:1234:4567:0:9 as an
anycast /64 from the 3GPP interface to the LAN interface and anycast /64 from the 3GPP interface to the LAN interface and
begins announcing the prefix 2001:db8:ac10:f002::/64 via RA to begins announcing the prefix 2001:db8:ac10:f002::/64 via RA to
the LAN. The 3GPP interface maintains the same IPv6 anycast the LAN. The 3GPP interface maintains the same IPv6 anycast
skipping to change at page 7, line 50 skipping to change at page 8, line 4
6. Acknowledgments 6. Acknowledgments
Many thanks for review and discussion from Dave Thaler, Sylvain Many thanks for review and discussion from Dave Thaler, Sylvain
Decremps, Mark Smith, Dmitry Anipko, Masanobu Kawashima, Teemu Decremps, Mark Smith, Dmitry Anipko, Masanobu Kawashima, Teemu
Savolainen, Mikael Abrahamsson, Eric Vyncke, Alexandru Petrescu, Savolainen, Mikael Abrahamsson, Eric Vyncke, Alexandru Petrescu,
Jouni Korhonen, and Julien Laganier. Jouni Korhonen, and Julien Laganier.
7. Informative References 7. Informative References
[RFC1981] McCann, J., Deering, S., and J. Mogul, "Path MTU Discovery [RFC1981] McCann, J., Deering, S., and J. Mogul, "Path MTU Discovery
V6OPS Working Group draft-ietf-v6ops-64share-05 May 17, 2013
for IP version 6", RFC 1981, August 1996. for IP version 6", RFC 1981, August 1996.
[RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic
Host Configuration Protocol (DHCP) version 6", RFC 3633, Host Configuration Protocol (DHCP) version 6", RFC 3633,
V6OPS Working Group draft-ietf-v6ops-64share-03 April 5, 2013
December 2003. December 2003.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006. Architecture", RFC 4291, February 2006.
[RFC4389] Thaler, D., Talwar, M., and C. Patel, "Neighbor Discovery [RFC4389] Thaler, D., Talwar, M., and C. Patel, "Neighbor Discovery
Proxies (ND Proxy)", RFC 4389, April 2006. Proxies (ND Proxy)", RFC 4389, April 2006.
[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
 End of changes. 21 change blocks. 
45 lines changed or deleted 46 lines changed or added

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