draft-ietf-v6ops-3gpp-eps-02.txt   draft-ietf-v6ops-3gpp-eps-03.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: January 7, 2012 Renesas Mobile Expires: January 12, 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
July 6, 2011 July 11, 2011
IPv6 in 3GPP Evolved Packet System IPv6 in 3GPP Evolved Packet System
draft-ietf-v6ops-3gpp-eps-02 draft-ietf-v6ops-3gpp-eps-03
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 January 7, 2012. This Internet-Draft will expire on January 12, 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 15, line 49 skipping to change at page 15, line 49
3GPP network allocates each default bearer a unique /64 prefix, and 3GPP network allocates each default bearer a unique /64 prefix, and
uses layer-2 signaling to suggest user equipment an Interface uses layer-2 signaling to suggest user equipment an Interface
Identifier that is guaranteed not to conflict with gateway's Identifier that is guaranteed not to conflict with gateway's
Interface Identifier. The UE must configure its link-local address Interface Identifier. The UE must configure its link-local address
using this Interface Identifier. The UE is allowed to use any using this Interface Identifier. The UE is allowed to use any
Interface Identifier it wishes for the other addresses it configures. Interface Identifier it wishes for the other addresses it configures.
There is no restriction, for example, of using Privacy Extension for There is no restriction, for example, of using Privacy Extension for
SLAAC [RFC4941] or other similar types of mechanisms. SLAAC [RFC4941] or other similar types of mechanisms.
In the 3GPP link model the /64 prefix assigned to the UE is always In the 3GPP link model the /64 prefix assigned to the UE cannot be
off-link (i.e. the L-bit in the Prefix Information Option (PIO) in used for on-link determination (because the L-bit in the Prefix
the RA must be set to zero). If the advertised prefix is used for Information Option (PIO) in the RA must always be set to zero). If
SLAAC then the A-bit in the PIO must be set to one. The details of the advertised prefix is used for SLAAC then the A-bit in the PIO
the 3GPP link-model and address configuration is described in Section must be set to one. The details of the 3GPP link-model and address
11.2.1.3.2a of [TS.29061]. More specifically, the GGSN/PDN-GW configuration is described in Section 11.2.1.3.2a of [TS.29061].
guarantees that the /64 prefix is unique for the mobile host. More specifically, the GGSN/PDN-GW guarantees that the /64 prefix is
Therefore, there is no need to perform any Duplicate Address unique for the mobile host. Therefore, there is no need to perform
Detection (DAD) on addresses the mobile host creates (i.e., the any Duplicate Address Detection (DAD) on addresses the mobile host
'DupAddrDetectTransmits' variable in the mobile host should be zero). creates (i.e., the 'DupAddrDetectTransmits' variable in the mobile
The GGSN/PDN-GW is not allowed to generate any globally unique IPv6 host could be zero). The GGSN/PDN-GW is not allowed to generate any
addresses for itself using the /64 prefix assigned to the mobile host globally unique IPv6 addresses for itself using the /64 prefix
in the RA. assigned to the mobile host in the RA.
The current 3GPP architecture limits number of prefixes in each The current 3GPP architecture limits number of prefixes in each
bearer to a single /64 prefix. If the mobile host finds more than bearer to a single /64 prefix. If the mobile host finds more than
one prefix in the RA, it only considers the first one and silently one prefix in the RA, it only considers the first one and silently
discards the others [TS.29061]. Therefore, multi-homing within a discards the others [TS.29061]. Therefore, multi-homing within a
single bearer is not possible. Renumbering without closing layer-2 single bearer is not possible. Renumbering without closing layer-2
connection is also not possible. The lifetime of /64 prefix is bound connection is also not possible. The lifetime of /64 prefix is bound
to lifetime of layer-2 connection even if the advertised prefix to lifetime of layer-2 connection even if the advertised prefix
lifetime would be longer than the layer-2 connection lifetime. lifetime is longer than the layer-2 connection lifetime.
5.3. Prefix Delegation 5.3. Prefix Delegation
IPv6 prefix delegation is a part of Release-10 and is not covered by IPv6 prefix delegation is a part of Release-10 and is not covered by
any earlier release. However, the /64 prefix allocated for each any earlier release. However, the /64 prefix allocated for each
default bearer (and to the user equipment) may be shared to local default bearer (and to the user equipment) may be shared to local
area network by user equipment implementing Neighbor Discovery proxy area network by user equipment implementing Neighbor Discovery proxy
(ND proxy) [RFC4389] functionality. (ND proxy) [RFC4389] functionality.
Release-10 prefix delegation uses the DHCPv6-based prefix delegation Release-10 prefix delegation uses the DHCPv6-based prefix delegation
 End of changes. 6 change blocks. 
18 lines changed or deleted 18 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/