draft-ietf-v6ops-64share-07.txt   draft-ietf-v6ops-64share-08.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: November 18, 2013 A. Vizdal Expires: January 15, 2014 A. Vizdal
Deutsche Telekom AG Deutsche Telekom AG
May 17, 2013 July 14, 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 link
draft-ietf-v6ops-64share-07 draft-ietf-v6ops-64share-08
Abstract Abstract
This document describes three methods for extending an IPv6 /64 This document describes two methods for extending an IPv6 /64 prefix
prefix from a User Equipment 3GPP radio interface to a LAN. from a User Equipment 3GPP radio interface to a LAN link.
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.
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/.
skipping to change at page 2, line 5 skipping to change at page 2, line 5
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-07 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 link via a
UE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3GPP 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 LAN link . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.0 General Behavior for All Scenarios . . . . . . . . . . . . . 4 3.1 General Behavior for All Scenarios . . . . . . . . . . . . . 4
3.1 Scenario 1: No Global Address on the UE . . . . . . . . . . 4 3.2 Scenario 1: Global Address Only Assigned to LAN link . . . . 4
3.2 Scenario 2: Global Address Only Assigned to LAN . . . . . . 5 3.3 Scenario 2: A Single Global Address Assigned to 3GPP Radio
3.3 Scenario 3: A Single Global Address Assigned to 3GPP Radio and LAN link . . . . . . . . . . . . . . . . . . . . . . . . 5
and LAN Interface . . . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Informative References . . . . . . . . . . . . . . . . . . . . 7 7. Informative References . . . . . . . . . . . . . . . . . . . . 7
V6OPS Working Group draft-ietf-v6ops-64share-07 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 single LAN
facilitate the use of IPv6 in a LAN prior to the deployment of DHCPv6 link. To facilitate the use of IPv6 in a LAN prior to the deployment
Prefix Delegation in 3GPP networks and in User Equipment (UE), this of DHCPv6 Prefix Delegation in 3GPP networks and in User Equipment
document describes how the 3GPP UE radio interface assigned global (UE), this document describes how the 3GPP UE radio interface
/64 prefix may be extended from the 3GPP radio interface to a LAN. assigned global /64 prefix may be extended from the 3GPP radio
This is achieved by receiving the Router Advertisement (RA) [RFC4861] interface to a LAN link. This is achieved by receiving the Router
announced globally unique /64 IPv6 prefix from the 3GPP radio Advertisement (RA) [RFC4861] announced globally unique /64 IPv6
interface and then advertising the same IPv6 prefix to the LAN with prefix from the 3GPP radio interface and then advertising the same
RA. For all of the cases in the scope of this document, the UE may IPv6 prefix to the LAN link with RA. For all of the cases in the
be any device that functions as an IPv6 router between the 3GPP scope of this document, the UE may be any device that functions as an
network and a LAN. IPv6 router between the 3GPP network and a LAN.
This document describes three methods for achieving IPv6 prefix This document describes two methods for achieving IPv6 prefix
extension from a 3GPP radio interface to a LAN including: extension from a 3GPP radio interface to a LAN link including:
1) The 3GPP UE does not have a global scope IPv6 address on any 1) The 3GPP UE only has a global scope address on the LAN link
interface, only link-local IPv6 addresses are present on the UE 2) The 3GPP UE maintains the same consistent 128 bit global scope
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 IPv6 anycast address [RFC4291] on the 3GPP radio interface and the
LAN interface. The LAN interface is configured as a /64 and the LAN link. The LAN link is configured as a /64 and the 3GPP radio
3GPP radio interface is configured as a /128. 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 two
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 link 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 link, but ND Proxy is an experimental
and has some limitations with loop-avoidance. 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 be used prior to DHCPv6
deployment.
V6OPS Working Group draft-ietf-v6ops-64share-07 May 17, 2013 DHCPv6 is the best way to delegate a prefix to a LAN link. 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 be used
prior to DHCPv6 deployment.
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
link
3.0 General Behavior for All Scenarios 3.1 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
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 link RA configuration must be tightly coupled
coupled with the 3GPP interface state. If the 3GPP interface goes with the 3GPP link state. If the 3GPP link goes down or changes the
down or changes the IPv6 prefix, that state should be reflected in IPv6 prefix, that state should be reflected in the LAN link IPv6
the LAN IPv6 configuration. Just as in a standard IPv6 router, the configuration. Just as in a standard IPv6 router, the packet TTL
packet TTL will be decremented when passing packets between will be decremented when passing packets between IPv6 links across
interfaces across the UE. The RA function on the UE is exclusively the UE. The UE is employing the weak host model. The RA function on
run on the LAN interface. the UE is exclusively run on the LAN link.
3.1 Scenario 1: No Global Address on the UE
In this case, the UE receives the /64 from the 3GPP network via RA
and simply configures Neighbor Discovery Protocol (NDP) [RFC4861] on
the LAN interface to announce the /64 via RA. The UE forwards all
traffic destine to the /64 out of the LAN interface. The UE shall
not run Stateless Address Autoconfiguration [RFC4862] to assign a
global address on the 3GPP radio interface while routing is enabled.
The 3GPP UE does not assign itself any global IPv6 addresses. Lack
of global scope connectivity will limit network services running on
the UE (e.g. DNS caching that requires global connectivity) and
prevent proper Path MTU Discovery [RFC1981] to occur on the UE
providing an IPv6 router function. 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 only an
IPv6 router that does not require any global connectivity.
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-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 The LAN link originated RA message carries a copy of the following
interface to the LAN interface, removes the global IPv6 address 3GPP radio link received RA message option fields:
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 o MTU (if not provided by the 3GPP network, the UE will provide its
the /64, there is no chance of an address conflict on the 3GPP 3GPP link MTU size)
radio interface. On the LAN interface, there is no chance of an o Prefix Information
address conflict since the hosts on the LAN will use Duplicate
Address Detection (DAD) [RFC4862].
3.2 Scenario 2: Global Address Only Assigned to LAN 3.2 Scenario 1: Global Address Only Assigned to LAN link
For this case, the UE receives the RA from the 3GPP network but does For this case, the UE receives the RA from the 3GPP network but does
not use a global address on the 3GPP interface. The 3GPP RA /64 not use a global address on the 3GPP interface. The 3GPP RA /64
prefix information is used to configure NDP on the LAN and assigns prefix information is used to configure NDP on the LAN and assigns
itself an address on the LAN link. The LAN interface uses RA to itself an address on the LAN link. The LAN link uses RA to announce
announce the prefix to the LAN. The UE LAN interface defends its LAN the prefix to the LAN. The UE LAN link interface defends its LAN
IPv6 address with DAD. The UE shall not run Stateless Address IPv6 address with DAD. The UE shall not run Stateless Address
Autoconfiguration [RFC4862] to assign a global address on the 3GPP Autoconfiguration [RFC4862] to assign a global address on the 3GPP
radio interface while routing is enabled. radio interface while routing is enabled.
This method allows the UE to originate and terminate IPv6 This method allows the UE to originate and terminate IPv6
communications as a host while acting as an IPv6 router. The communications as a host while acting as an IPv6 router. The
movement of the IPv6 prefix from the 3GPP radio interface to the LAN movement of the IPv6 prefix from the 3GPP radio interface to the LAN
interface may result in long-lived data connections being terminated link may result in long-lived data connections being terminated
during the transition from a host-only mode to router-and-host mode. during the transition from a host-only mode to router-and-host mode.
This method is appropriate if the UE or software on the UE cannot Connections which are likely to be effected are ones that have been
support multiple interfaces with the same anycast IPv6 address and specifically bound to the 3GPP radio interface. This method is
the UE requires global connectivity while acting as a router. appropriate if the UE or software on the UE cannot support multiple
interfaces with the same anycast IPv6 address and the UE requires
global connectivity while acting as a router.
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-07 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
/64 from the 3GPP interfaces to the LAN interface, disables the /64 from the 3GPP interfaces to the LAN link interface, disables
IPv6 SLAAC feature on the 3GPP radio interface to avoid address the IPv6 SLAAC feature on the 3GPP radio interface to avoid
autoconfiguration, and begins announcing the prefix address 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.
6. The UE, acting as a router running NDP on the LAN, will route 6. The UE, acting as a router running NDP on the LAN, will route
packets to and from the LAN. IPv6 packets passing between packets to and from the LAN. IPv6 packets passing between
interfaces will have the TTL decremented. interfaces will have the TTL decremented.
7. On the LAN interface, there is no chance of address conflict 7. On the LAN link interface, there is no chance of address conflict
since the address is defended using DAD. The 3GPP radio since the address is defended using DAD. The 3GPP radio
interface only has link-local addresses. interface only has a link-local address.
3.3 Scenario 3: A Single Global Address Assigned to 3GPP Radio and LAN 3.3 Scenario 2: A Single Global Address Assigned to 3GPP Radio and LAN
Interface link
In this method, the UE assigns itself one address from the 3GPP In this method, the UE assigns itself one address from the 3GPP
network RA announced /64. This one address is configured as anycast 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 [RFC4291] on both the 3GPP radio link as a /128 and on the LAN link
interface as a /64. This allows the UE to maintain long lived data as a /64. This allows the UE to maintain long lived data connections
connections since the 3GPP radio interface address does not change since the 3GPP radio interface address does not change when the
when the router function is activated. This method may cause router function is activated. This method may cause complications
complications for certain software that may not support multiple for certain software that may not support multiple interfaces with
interfaces with the same anycast IPv6 address or are sensitive to the same anycast IPv6 address or are sensitive to prefix length
prefix length changes. This method also creates complications for changes. This method also creates complications for ensuring
ensuring uniqueness for Privacy Extensions [RFC4941]. Privacy uniqueness for Privacy Extensions [RFC4941]. When Privacy Extensions
Extensions should be disabled on the 3GPP radio interface while this are in use all temporary addresses will be copied from the 3GPP radio
method is enabled. interface to the LAN link and the preferred and valid lifetimes will
be synchronized, such that the temporary anycast addresses on both
interfaces expire simultaneously.
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-07 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 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.
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
skipping to change at page 7, line 35 skipping to change at page 6, line 42
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.
6. On the LAN interface, there is no chance of address conflict 6. On the LAN interface, there is no chance of address conflict
since the address is defended using DAD. The 3GPP radio since the address is defended using DAD. The 3GPP radio
interface only has a /128 and no other systems on the 3GPP radio interface only has a /128 and no other systems on the 3GPP radio
point-to-point link may use the global /64. point-to-point link may use the global /64.
4. Security Considerations 4. Security Considerations
Since Scenario 3.3 does not allow for Privacy Extension to run on the tbd
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 5. IANA Considerations
This document does not require any action from IANA. This document does not require any action from IANA.
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, Lorenzo Colitti, Julien Laganier and Owen DeLong.
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-07 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,
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
skipping to change at page 8, line 30 skipping to change at page 7, line 35
"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
September 2007. September 2007.
[RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless
Address Autoconfiguration", RFC 4862, September 2007. Address Autoconfiguration", RFC 4862, September 2007.
[RFC4941] Narten, T., Draves, R., and S. Krishnan, "Privacy [RFC4941] Narten, T., Draves, R., and S. Krishnan, "Privacy
Extensions for Stateless Address Autoconfiguration in Extensions for Stateless Address Autoconfiguration in
IPv6", RFC 4941, September 2007. IPv6", RFC 4941, September 2007.
[RFC6459] Korhonen, J., Ed., Soininen, J., Patil, B., Savolainen,
T., Bajko, G., and K. Iisakkila, "IPv6 in 3rd Generation
Partnership Project (3GPP) Evolved Packet System (EPS)",
RFC 6459, January 2012.
Authors' Addresses Authors' Addresses
Cameron Byrne Cameron Byrne
T-Mobile USA T-Mobile USA
Bellevue, Washington, USA Bellevue, Washington, USA
EMail: Cameron.Byrne@T-Mobile.com EMail: Cameron.Byrne@T-Mobile.com
Dan Drown Dan Drown
Email: Dan@Drown.org Email: Dan@Drown.org
Ales Vizdal Ales Vizdal
Deutsche Telekom AG Deutsche Telekom AG
Tomickova 2144/1 Tomickova 2144/1
Prague, 149 00 Prague, 149 00
Czech Republic Czech Republic
EMail: Ales.Vizdal@t-mobile.cz EMail: Ales.Vizdal@T-Mobile.cz
 End of changes. 39 change blocks. 
151 lines changed or deleted 89 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/