draft-ietf-v6ops-3gpp-eps-06.txt   draft-ietf-v6ops-3gpp-eps-07.txt 
Individual Submission J. Korhonen, Ed. Individual Submission J. Korhonen, Ed.
Internet-Draft Nokia Siemens Networks Internet-Draft Nokia Siemens Networks
Intended status: Informational J. Soininen Intended status: Informational J. Soininen
Expires: March 23, 2012 Renesas Mobile Expires: March 25, 2012 Renesas Mobile
B. Patil B. Patil
T. Savolainen T. Savolainen
G. Bajko G. Bajko
Nokia Nokia
K. Iisakkila K. Iisakkila
Renesas Mobile Renesas Mobile
September 20, 2011 September 22, 2011
IPv6 in 3GPP Evolved Packet System IPv6 in 3GPP Evolved Packet System
draft-ietf-v6ops-3gpp-eps-06 draft-ietf-v6ops-3gpp-eps-07
Abstract Abstract
Use of data services in smart phones and broadband services via HSPA Use of data services in smart phones and broadband services via HSPA
and HSPA+, in particular Internet services, has increased rapidly and and HSPA+, in particular Internet services, has increased rapidly and
operators that have deployed networks based on 3GPP network operators that have deployed networks based on 3GPP network
architectures are facing IPv4 address shortages at the Internet architectures are facing IPv4 address shortages at the Internet
registries and are feeling a pressure to migrate to IPv6. This registries and are feeling a pressure to migrate to IPv6. This
document describes the support for IPv6 in 3GPP network document describes the support for IPv6 in 3GPP network
architectures. architectures.
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 March 23, 2012. This Internet-Draft will expire on March 25, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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
skipping to change at page 17, line 28 skipping to change at page 17, line 28
not contain a Target Link-Layer address option (as suggested in not contain a Target Link-Layer address option (as suggested in
[RFC4861] Section 4.4). Then it is possible that the address [RFC4861] Section 4.4). Then it is possible that the address
resolution never completes when the UE tries to resolve the link- resolution never completes when the UE tries to resolve the link-
layer address of the GGSN, thus stalling all IPv6 traffic. layer address of the GGSN, thus stalling all IPv6 traffic.
Second, the GGSN may simply discard all address resolution triggered Second, the GGSN may simply discard all address resolution triggered
Neighbor Solicitation messages (as sometimes misinterpreted from Neighbor Solicitation messages (as sometimes misinterpreted from
[RFC3316] Section 2.4.1 that responding to address resolution and [RFC3316] Section 2.4.1 that responding to address resolution and
next-hop determination are not needed). As a result the address next-hop determination are not needed). As a result the address
resolution never completes when the UE tries to resolve the link- resolution never completes when the UE tries to resolve the link-
layer address of the GGSN, thus stalling all IPv6 traffic. layer address of the GGSN, thus stalling all IPv6 traffic. There is
little that can be done about this in the GGSN, assuming the Neighbor
Discovery implementation already does the right thing. But the UE
stacks must be able to handle address resolution in the manner that
they have chosen to represent the interface. In other words, if they
emulate IEEE802 type interfaces, they also need to process Neighbor
Discovery messages correctly.
6. 3GPP Dual-Stack Approach to IPv6 6. 3GPP Dual-Stack Approach to IPv6
6.1. 3GPP Networks Prior to Release-8 6.1. 3GPP Networks Prior to Release-8
3GPP standards prior to Release-8 provide IPv6 access for cellular 3GPP standards prior to Release-8 provide IPv6 access for cellular
devices with PDP contexts of type IPv6 [TS.23060]. For dual-stack devices with PDP contexts of type IPv6 [TS.23060]. For dual-stack
access, a PDP context of type IPv6 is established in parallel to the access, a PDP context of type IPv6 is established in parallel to the
PDP context of type IPv4, as shown in Figure 5 and Figure 6. For PDP context of type IPv4, as shown in Figure 5 and Figure 6. For
IPv4-only service, connections are created over the PDP context of IPv4-only service, connections are created over the PDP context of
 End of changes. 5 change blocks. 
5 lines changed or deleted 11 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/