draft-ietf-v6ops-3gpp-eps-04.txt   draft-ietf-v6ops-3gpp-eps-05.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: February 21, 2012 Renesas Mobile Expires: March 3, 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
August 20, 2011 August 31, 2011
IPv6 in 3GPP Evolved Packet System IPv6 in 3GPP Evolved Packet System
draft-ietf-v6ops-3gpp-eps-04 draft-ietf-v6ops-3gpp-eps-05
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 February 21, 2012. This Internet-Draft will expire on March 3, 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 3, line 4 skipping to change at page 3, line 4
8.3. Operational Aspects of Running Dual-Stack Networks . . . . 25 8.3. Operational Aspects of Running Dual-Stack Networks . . . . 25
8.4. Operational Aspects of Running a Network with 8.4. Operational Aspects of Running a Network with
IPv6-only Bearers . . . . . . . . . . . . . . . . . . . . 25 IPv6-only Bearers . . . . . . . . . . . . . . . . . . . . 25
8.5. Restricting Outbound IPv6 Roaming . . . . . . . . . . . . 26 8.5. Restricting Outbound IPv6 Roaming . . . . . . . . . . . . 26
8.6. Inter-RAT Handovers and IP Versions . . . . . . . . . . . 27 8.6. Inter-RAT Handovers and IP Versions . . . . . . . . . . . 27
8.7. Provisioning of IPv6 Subscribers and Various 8.7. Provisioning of IPv6 Subscribers and Various
Combinations During Initial Network Attachment . . . . . . 28 Combinations During Initial Network Attachment . . . . . . 28
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
10. Security Considerations . . . . . . . . . . . . . . . . . . . 30 10. Security Considerations . . . . . . . . . . . . . . . . . . . 30
11. Summary and Conclusion . . . . . . . . . . . . . . . . . . . . 30 11. Summary and Conclusion . . . . . . . . . . . . . . . . . . . . 30
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 30 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 31
13. Informative References . . . . . . . . . . . . . . . . . . . . 30 13. Informative References . . . . . . . . . . . . . . . . . . . . 31
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33
1. Introduction 1. Introduction
IPv6 has been specified in the 3rd Generation Partnership Project IPv6 has been specified in the 3rd Generation Partnership Project
(3GPP) standards since the early architectures developed for R99 (3GPP) standards since the early architectures developed for R99
General Packet Radio Service (GPRS). However, the support for IPv6 General Packet Radio Service (GPRS). However, the support for IPv6
in commercially deployed networks remains low. There are many in commercially deployed networks remains low. There are many
factors that can be attributed to the lack of IPv6 deployment in 3GPP factors that can be attributed to the lack of IPv6 deployment in 3GPP
networks. The most relevant one is essentially the same as the networks. The most relevant one is essentially the same as the
reason for IPv6 not being deployed by other networks as well, i.e. reason for IPv6 not being deployed by other networks as well, i.e.
skipping to change at page 11, line 15 skipping to change at page 11, line 15
3G 3G
.--. .--. .--. .--.
Uu _( `. Iu +----+ +----+ _( `. Uu _( `. Iu +----+ +----+ _( `.
[UE]~~|~~~( UTRAN )--|---|SGSN|--|---|GGSN|--|----( PDN ) [UE]~~|~~~( UTRAN )--|---|SGSN|--|---|GGSN|--|----( PDN )
( ` . ) ) +----+ Gn +----+ Gi ( ` . ) ) ( ` . ) ) +----+ Gn +----+ Gi ( ` . ) )
`--(___.-' / | `--(___.-' `--(___.-' / | `--(___.-'
/ | / |
2G Gb-- | 2G Gb-- |
.--. / | .--. / |
_( `. / --Gp _( `. / --Gp
[UE]~~|~~( PDN )__/ | [UE]~~|~~~( PDN )__/ |
Um ( ` . ) ) .--. Um ( ` . ) ) .--.
`--(___.-' _(. `) `--(___.-' _(. `)
_( [GGSN] `)_ _( [GGSN] `)_
( other `) ( other `)
( ` . PLMN ) ) ( ` . PLMN ) )
`--(_______)---' `--(_______)---'
Figure 2: Overview of the 2G/3G GPRS Logical Architecture Figure 2: Overview of the 2G/3G GPRS Logical Architecture
Gn/Gp: These interfaces provide a network based mobility service for Gn/Gp: These interfaces provide a network based mobility service for
skipping to change at page 30, line 8 skipping to change at page 30, line 8
not understand the requested PDN Type, then the PDN Type is handled not understand the requested PDN Type, then the PDN Type is handled
as IPv6. as IPv6.
9. IANA Considerations 9. IANA Considerations
This document has no requests to IANA. This document has no requests to IANA.
10. Security Considerations 10. Security Considerations
This document does not introduce any security related concerns. This document does not introduce any security related concerns.
However, there are several general security concerns to take into
consideration.
In 3GPP access the UE and the network always perform a mutual
authentication during the network attachment [TS.33102][TS.33401].
Furthermore, each time a PDP Context/PDN Connection gets created, a
new connection, a modification of an existing connection and an
assignment of an IPv6 prefix or an IP address can be authorized
against the PCC infrastructure [TS.23203] and/or PDN's AAA server.
The wireless part of the 3GPP link between the UE and the (e)NodeB as
well as the signaling messages between the UE and the MME/SGSN can be
protected depending on the regional regulation and operators'
deployment policy. User plane traffic can be confidentiality
protected. The control plane is always at least integrity and replay
protected, and may also be confidentiality protected. The protection
within the transmission part of the network depends on operators'
deployment policy. [TS.33401]
Due the nature of 3GPP point to point link model, the UE and the
first hop router (PGW/GGSN or SGW) are the only nodes on the link,
which mitigates most of the known on-link attacks. For off-link IPv6
attacks the 3GPP EPS is as vulnerable as any IPv6 system. There have
also been concerns that the UE IP stack might use permanent
subscriber identities, such as IMSI, as the source for IPv6 address
Interface Identifier. This would be a privacy threat and allow
tracking of subscribers, and therefore use of IMSI (or any [TS.23003]
defined identity) as the Interface Identifier is prohibited
[TS.23401]. However, there is no standardized method to block such
misbehaving UEs.
11. Summary and Conclusion 11. Summary and Conclusion
The 3GPP network architecture and specifications enable the The 3GPP network architecture and specifications enable the
establishment of IPv4 and IPv6 connections through the use of establishment of IPv4 and IPv6 connections through the use of
appropriate PDP context types. The current generation of deployed appropriate PDP context types. The current generation of deployed
networks can support dual-stack connectivity if the packet core networks can support dual-stack connectivity if the packet core
network elements such as the SGSN and GGSN have the capability. With network elements such as the SGSN and GGSN have the capability. With
Release-8, 3GPP has specified a more optimal PDP context type which Release-8, 3GPP has specified a more optimal PDP context type which
enables the transport of IPv4 and IPv6 packets within a single PDP enables the transport of IPv4 and IPv6 packets within a single PDP
skipping to change at page 30, line 34 skipping to change at page 31, line 16
of relief to the IPv4 address space as many of the applications and of relief to the IPv4 address space as many of the applications and
services can start to work over IPv6. However without comprehensive services can start to work over IPv6. However without comprehensive
testing of different applications and solutions that exist today and testing of different applications and solutions that exist today and
are widely used, for their ability to operate over IPv6 PDN are widely used, for their ability to operate over IPv6 PDN
connections, an IPv6-only access would cause disruptions. connections, an IPv6-only access would cause disruptions.
12. Acknowledgements 12. Acknowledgements
The authors thank Shabnam Sultana, Sri Gundavelli, Hui Deng, and The authors thank Shabnam Sultana, Sri Gundavelli, Hui Deng, and
Zhenqiang Li, Mikael Abrahamsson, James Woodyatt, Martin Thomson, Zhenqiang Li, Mikael Abrahamsson, James Woodyatt, Martin Thomson,
Cameron Byrne, Ales Vizdal and Frank Brockners for their reviews and Russ Mundy, Cameron Byrne, Ales Vizdal and Frank Brockners for their
comments on this document. reviews and comments on this document.
13. Informative References 13. Informative References
[GSMA.IR.34] [GSMA.IR.34]
GSMA, "Inter-PLMN Backbone Guidelines", GSMA GSMA, "Inter-PLMN Backbone Guidelines", GSMA
PRD IR.34.4.9, March 2010. PRD IR.34.4.9, March 2010.
[I-D.ietf-dhc-pd-exclude] [I-D.ietf-dhc-pd-exclude]
Korhonen, J., Savolainen, T., Krishnan, S., and O. Troan, Korhonen, J., Savolainen, T., Krishnan, S., and O. Troan,
"Prefix Exclude Option for DHCPv6-based Prefix "Prefix Exclude Option for DHCPv6-based Prefix
skipping to change at page 31, line 50 skipping to change at page 32, line 32
[RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K., [RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K.,
and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008. and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008.
[RFC6144] Baker, F., Li, X., Bao, C., and K. Yin, "Framework for [RFC6144] Baker, F., Li, X., Bao, C., and K. Yin, "Framework for
IPv4/IPv6 Translation", RFC 6144, April 2011. IPv4/IPv6 Translation", RFC 6144, April 2011.
[TR.23975] [TR.23975]
3GPP, "IPv6 Migration Guidelines", 3GPP TR 23.975 1.1.1, 3GPP, "IPv6 Migration Guidelines", 3GPP TR 23.975 1.1.1,
June 2010. June 2010.
[TS.23003]
3GPP, "Numbering, addressing and identification", 3GPP
TS 23.003 10.2.0, June 2011.
[TS.23060] [TS.23060]
3GPP, "General Packet Radio Service (GPRS); Service 3GPP, "General Packet Radio Service (GPRS); Service
description; Stage 2", 3GPP TS 23.060 8.8.0, March 2010. description; Stage 2", 3GPP TS 23.060 8.8.0, March 2010.
[TS.23203] [TS.23203]
3GPP, "Policy and charging control architecture (PCC)", 3GPP, "Policy and charging control architecture (PCC)",
3GPP TS 23.203 8.11.0, September 2010. 3GPP TS 23.203 8.11.0, September 2010.
[TS.23401] [TS.23401]
3GPP, "General Packet Radio Service (GPRS) enhancements 3GPP, "General Packet Radio Service (GPRS) enhancements
skipping to change at page 33, line 5 skipping to change at page 33, line 29
3GPP, "Interworking between the Public Land Mobile Network 3GPP, "Interworking between the Public Land Mobile Network
(PLMN) supporting packet based services and Packet Data (PLMN) supporting packet based services and Packet Data
Networks (PDN)", 3GPP TS 29.061 8.5.0, April 2010. Networks (PDN)", 3GPP TS 29.061 8.5.0, April 2010.
[TS.29274] [TS.29274]
3GPP, "3GPP Evolved Packet System (EPS); Evolved General 3GPP, "3GPP Evolved Packet System (EPS); Evolved General
Packet Radio Service (GPRS) Tunnelling Protocol for Packet Radio Service (GPRS) Tunnelling Protocol for
Control plane (GTPv2-C)", 3GPP TS 29.060 8.11.0, Control plane (GTPv2-C)", 3GPP TS 29.060 8.11.0,
December 2010. December 2010.
[TS.33102]
3GPP, "3G Security; Security architecture", 3GPP
TS 33.102 10.0.0, December 2010.
[TS.33401]
3GPP, "3GPP System Architecture Evolution (SAE); Security
architecture", 3GPP TS 33.401 10.1.1, June 2011.
Authors' Addresses Authors' Addresses
Jouni Korhonen (editor) Jouni Korhonen (editor)
Nokia Siemens Networks Nokia Siemens Networks
Linnoitustie 6 Linnoitustie 6
FI-02600 Espoo FI-02600 Espoo
FINLAND FINLAND
Email: jouni.nospam@gmail.com Email: jouni.nospam@gmail.com
Jonne Soininen Jonne Soininen
Renesas Mobile Renesas Mobile
Porkkalankatu 24 Porkkalankatu 24
FI-00180 Helsinki FI-00180 Helsinki
FINLAND FINLAND
Email: jonne.soininen@renesasmobile.com Email: jonne.soininen@renesasmobile.com
Basavaraj Patil Basavaraj Patil
Nokia Nokia
 End of changes. 11 change blocks. 
11 lines changed or deleted 52 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/