idnits 2.17.1 draft-ietf-v6ops-3gpp-eps-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 22, 2011) is 4599 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'GGSN' is mentioned on line 434, but not defined == Outdated reference: A later version (-04) exists of draft-ietf-dhc-pd-exclude-03 -- Obsolete informational reference (is this intentional?): RFC 3315 (Obsoleted by RFC 8415) -- Obsolete informational reference (is this intentional?): RFC 3316 (Obsoleted by RFC 7066) -- Obsolete informational reference (is this intentional?): RFC 3633 (Obsoleted by RFC 8415) -- Obsolete informational reference (is this intentional?): RFC 3736 (Obsoleted by RFC 8415) -- Obsolete informational reference (is this intentional?): RFC 4941 (Obsoleted by RFC 8981) Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Individual Submission J. Korhonen, Ed. 3 Internet-Draft Nokia Siemens Networks 4 Intended status: Informational J. Soininen 5 Expires: March 25, 2012 Renesas Mobile 6 B. Patil 7 T. Savolainen 8 G. Bajko 9 Nokia 10 K. Iisakkila 11 Renesas Mobile 12 September 22, 2011 14 IPv6 in 3GPP Evolved Packet System 15 draft-ietf-v6ops-3gpp-eps-07 17 Abstract 19 Use of data services in smart phones and broadband services via HSPA 20 and HSPA+, in particular Internet services, has increased rapidly and 21 operators that have deployed networks based on 3GPP network 22 architectures are facing IPv4 address shortages at the Internet 23 registries and are feeling a pressure to migrate to IPv6. This 24 document describes the support for IPv6 in 3GPP network 25 architectures. 27 Status of this Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at http://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on March 25, 2012. 44 Copyright Notice 46 Copyright (c) 2011 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (http://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 2. 3GPP Terminology and Concepts . . . . . . . . . . . . . . . . 5 63 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5 64 2.2. The concept of APN . . . . . . . . . . . . . . . . . . . . 10 65 3. IP over 3GPP GPRS . . . . . . . . . . . . . . . . . . . . . . 10 66 3.1. Introduction to 3GPP GPRS . . . . . . . . . . . . . . . . 10 67 3.2. PDP Context . . . . . . . . . . . . . . . . . . . . . . . 12 68 4. IP over 3GPP EPS . . . . . . . . . . . . . . . . . . . . . . . 13 69 4.1. Introduction to 3GPP EPS . . . . . . . . . . . . . . . . . 13 70 4.2. PDN Connection . . . . . . . . . . . . . . . . . . . . . . 14 71 4.3. EPS bearer model . . . . . . . . . . . . . . . . . . . . . 14 72 5. Address Management . . . . . . . . . . . . . . . . . . . . . . 15 73 5.1. IPv4 Address Configuration . . . . . . . . . . . . . . . . 15 74 5.2. IPv6 Address Configuration . . . . . . . . . . . . . . . . 15 75 5.3. Prefix Delegation . . . . . . . . . . . . . . . . . . . . 16 76 5.4. IPv6 Neighbor Discovery Considerations . . . . . . . . . . 16 77 6. 3GPP Dual-Stack Approach to IPv6 . . . . . . . . . . . . . . . 17 78 6.1. 3GPP Networks Prior to Release-8 . . . . . . . . . . . . . 17 79 6.2. 3GPP Release-8 and -9 Networks . . . . . . . . . . . . . . 18 80 6.3. PDN Connection Establishment Process . . . . . . . . . . . 19 81 6.4. Mobility of 3GPP IPv4v6 Type of Bearers . . . . . . . . . 22 82 7. Dual-Stack Approach to IPv6 Transition in 3GPP Networks . . . 22 83 8. Deployment issues . . . . . . . . . . . . . . . . . . . . . . 23 84 8.1. Overlapping IPv4 Addresses . . . . . . . . . . . . . . . . 23 85 8.2. IPv6 for transport . . . . . . . . . . . . . . . . . . . . 24 86 8.3. Operational Aspects of Running Dual-Stack Networks . . . . 25 87 8.4. Operational Aspects of Running a Network with 88 IPv6-only Bearers . . . . . . . . . . . . . . . . . . . . 25 89 8.5. Restricting Outbound IPv6 Roaming . . . . . . . . . . . . 26 90 8.6. Inter-RAT Handovers and IP Versions . . . . . . . . . . . 27 91 8.7. Provisioning of IPv6 Subscribers and Various 92 Combinations During Initial Network Attachment . . . . . . 28 93 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 94 10. Security Considerations . . . . . . . . . . . . . . . . . . . 30 95 11. Summary and Conclusion . . . . . . . . . . . . . . . . . . . . 30 96 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 31 97 13. Informative References . . . . . . . . . . . . . . . . . . . . 31 98 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33 100 1. Introduction 102 IPv6 has been specified in the 3rd Generation Partnership Project 103 (3GPP) standards since the early architectures developed for R99 104 General Packet Radio Service (GPRS). However, the support for IPv6 105 in commercially deployed networks remains low. There are many 106 factors that can be attributed to the lack of IPv6 deployment in 3GPP 107 networks. The most relevant one is essentially the same as the 108 reason for IPv6 not being deployed by other networks as well, i.e. 109 the lack of business and commercial incentives for deployment. 3GPP 110 network architectures have also evolved since 1999 (since R99). The 111 most recent version of the 3GPP architecture, the Evolved Packet 112 System (EPS), which is commonly referred to as SAE, LTE or Release-8, 113 is a packet centric architecture. The number of subscribers and 114 devices that are using the 3GPP networks for Internet connectivity 115 and data services has also increased significantly. With the 116 subscriber growth numbers projected to increase even further and the 117 IPv4 addresses depletion problem looming in the near term, 3GPP 118 operators and vendors have started the process of identifying the 119 scenarios and solutions needed to transition to IPv6. 121 This document describes the establishment of IP connectivity in 3GPP 122 network architectures, specifically in the context of IP bearers for 123 3GPP GPRS and for 3GPP EPS. It provides an overview of how IPv6 is 124 supported as per the current set of 3GPP specifications. Some of the 125 issues and concerns with respect to deployment and shortage of 126 private IPv4 addresses within a single network domain are also 127 discussed. 129 The IETF has specified a set of tools and mechanisms that can be 130 utilized for transitioning to IPv6. In addition to operating dual- 131 stack networks during the transition from IPv4 to IPv6 phase, the two 132 alternative categories for the transition are encapsulation and 133 translation. The IETF continues to specify additional solutions for 134 enabling the transition based on the deployment scenarios and 135 operator/ISP requirements. There is no single approach for 136 transition to IPv6 that can meet the needs for all deployments and 137 models. The 3GPP scenarios for transition, described in [TR.23975], 138 can be addressed using transition mechanisms that are already 139 available in the toolbox. The objective of transition to IPv6 in 140 3GPP networks is to ensure that: 142 1. Legacy devices and hosts which have an IPv4-only stack will 143 continue to be provided with IP connectivity to the Internet and 144 services, 146 2. Devices which are dual-stack can access the Internet either via 147 IPv6 or IPv4. The choice of using IPv6 or IPv4 depends on the 148 capability of: 150 A. the application on the host, 152 B. the support for IPv4 and IPv6 bearers by the network and/or, 154 C. the capability of the server(s) and other end points. 156 3GPP networks are capable of providing a host with IPv4 and IPv6 157 connectivity today, albeit in many cases with upgrades to network 158 elements such as the SGSN and GGSN. 160 2. 3GPP Terminology and Concepts 162 2.1. Terminology 164 Access Point Name 166 Access Point Name (APN) is a fully qualified domain name and 167 resolves to a specific gateway in an operators network. The APNs 168 are piggybacked on the administration of the DNS namespace. 170 Dual Address PDN/PDP Type 172 The Dual Address PDN/PDP Type (IPv4v6) is used in 3GPP context in 173 many cases as a synonym for dual-stack i.e. a connection type 174 capable of serving both IPv4 and IPv6 simultaneously. 176 Evolved Packet Core 178 Evolved Packet Core (EPC) is an evolution of the 3GPP GPRS system 179 characterized by higher-data-rate, lower-latency, packet-optimized 180 system. EPC comprises of subcomponents such as Mobility 181 Management Entity (MME), Serving Gateway (SGW), Packet Data 182 Network Gateway (PDN-GW) and Home Subscriber Server (HSS). 184 Evolved Packet System 186 Evolved Packet System (EPS) is an evolution of the 3GPP GPRS 187 system characterized by higher-data-rate, lower-latency, packet- 188 optimized system that supports multiple Radio Access Technologies 189 (RAT). The EPS comprises the Evolved Packet Core (EPC) together 190 with the evolved radio access network (E-UTRA and E-UTRAN). 192 Evolved UTRAN 194 Evolved UTRAN (E-UTRAN) is communications network, sometimes 195 referred to as 4G, and consists of eNodeBs (4G base station) which 196 make up the E-UTRAN radio access network. The E-UTRAN allows 197 connectivity between the User Equipment and the core network. 199 GPRS tunnelling protocol 201 GPRS Tunnelling Protocol (GTP) [TS.29060] [TS.29274] is a 202 tunnelling protocol defined by 3GPP. It is a network based 203 mobility protocol and similar to Proxy Mobile IPv6 (PMIPv6) 204 [RFC5213]. However, GTP also provides functionality beyond 205 mobility such as inband signaling related to Quality of Service 206 (QoS) and charging among others. 208 GSM EDGE Radio Access Network 210 GSM EDGE Radio Access Network (GERAN) is communications network, 211 commonly referred to as 2G or 2.5G, and consists of base stations 212 and Base Station Controllers (BSC) which make up the GSM EDGE 213 radio access network. The GERAN allows connectivity between the 214 User Equipment and the core network. 216 Gateway GPRS Support Node 218 Gateway GPRS Support Node (GGSN) is a gateway function in GPRS, 219 which provides connectivity to Internet or other PDNs. The host 220 attaches to a GGSN identified by an APN assigned to it by an 221 operator. The GGSN also serves as the topological anchor for 222 addresses/prefixes assigned to the User Equipment. 224 General Packet Radio Service 226 General Packet Radio Service (GPRS) is a packet oriented mobile 227 data service available to users of the 2G and 3G cellular 228 communication systems Global System for Mobile communications 229 (GSM), and specified by 3GPP. 231 High Speed Packet Access 233 The High Speed Packet Access (HSPA) and the Evolved High Speed 234 Packet Access (HSPA+) are enhanced versions of the WCDMA and 235 UTRAN, thus providing more data throughput and lower latencies. 237 Home Location Register 239 The Home Location Register (HLR) is a pre-Release-5 database (but 240 is also used in Release-5 and later networks in real deployments) 241 that contains subscriber data and call routing related 242 information. Every subscriber of an operator including 243 subscribers' enabled services are provisioned in the HLR. 245 Home Subscriber Server 247 The Home Subscriber Server (HSS) is a database for a given 248 subscriber and got introduced in 3GPP Release-5. It is the entity 249 containing the subscription-related information to support the 250 network entities actually handling calls/sessions. 252 Mobility Management Entity 254 Mobility Management Entity (MME) is a network element that is 255 responsible for control plane functionalities, including 256 authentication, authorization, bearer management, layer-2 257 mobility, etc. The MME is essentially the control plane part of 258 the SGSN in GPRS. The user plane traffic bypasses the MME. 260 Mobile Terminal 262 The Mobile Terminal (MT) is the modem and the radio part of the 263 Mobile Station (MS). 265 Public Land Mobile Network 267 The Public Land Mobile Network (PLMN) is a network that is 268 operated by a single administration. A PLMN (and therefore also 269 an operator) is identified by the Mobile Country Code (MCC) and 270 the Mobile Network Code (MNC). Each (telecommunications) operator 271 providing mobile services has its own PLMN. 273 Policy and Charging Control 275 The Policy and Charging Control (PCC) framework is used for QoS 276 policy and charging control. It has two main functions: flow 277 based charging including online credit control, and policy control 278 (e.g. gating control, QoS control and QoS signaling). It is 279 optional to 3GPP EPS but needed if dynamic policy and charging 280 control by means of PCC rules based on user and services are 281 desired. 283 Packet Data Network 285 Packet Data Network (PDN) is a packet based network that either 286 belongs to the operator or is an external network such as Internet 287 and corporate intranet. The user eventually accesses services in 288 one or more PDNs. The operator's packet core network are 289 separated from packet data networks either by GGSNs or PDN 290 Gateways (PDN-GW). 292 Packet Data Network Gateway 294 Packet Data Network Gateway (PDN-GW) is a gateway function in 295 Evolved Packet System (EPS), which provides connectivity to 296 Internet or other PDNs. The host attaches to a PDN-GW identified 297 by an APN assigned to it by an operator. The PDN-GW also serves 298 as the topological anchor for addresses/prefixes assigned to the 299 User Equipment. 301 Packet Data Protocol Context 303 A Packet Data Protocol (PDP) Context is the equivalent of a 304 virtual connection between the host and a gateway. 306 Packet Data Protocol Type 308 A Packet Data Protocol Type (PDP Type) identifies the used/allowed 309 protocols within the PDP Context. Examples are IPv4, IPv6 and 310 IPv4v6 (dual stack). 312 S4 Serving Gateway Support Node 314 S4 Serving Gateway Support Node (S4-SGSN) is a Release-8 (and 315 onwards) compliant SGSN that connects 2G/3G radio access network 316 to EPC via new Release-8 interfaces like S3, S4, and S6d. 318 Serving Gateway 320 Serving Gateway (SGW) is a gateway function in EPS, which 321 terminates the interface towards E-UTRAN. The SGW is the Mobility 322 Anchor point for layer-2 mobility (inter-eNodeB handovers). For 323 each User Equipment connected with the EPS, at any given point of 324 time, there is only one SGW. The SGW is essentially the user 325 plane part of the GPRS' SGSN forwarding packets between a PDN-GW. 327 Serving Gateway Support Node 329 Serving Gateway Support Node (SGSN) is a network element that is 330 located between the radio access network (RAN) and the gateway 331 (GGSN). A per User Equipment point to point (p2p) tunnel between 332 the GGSN and SGSN transports the packets between the User 333 Equipment and the gateway. 335 Terminal Equipment 337 The Terminal Equipment (TE) is any device/host connected to the 338 Mobile Terminal (MT) offering services to the user. A TE may 339 communicate to a MT, for example, over Point to Point Protocol 340 (PPP). 342 UE, MS, MN and Mobile 344 The terms UE (User Equipment), MS (Mobile Station), MN (Mobile 345 Node) and, mobile refer to the devices which are hosts with 346 ability to obtain Internet connectivity via a 3GPP network. A MS 347 comprises of a Terminal Equipment (TE) and a Mobile Terminal (MT). 348 The terms UE, MS, MN and devices are used interchangeably within 349 this document. 351 UMTS Terrestrial Radio Access Network 353 UMTS Terrestrial Radio Access Network (UTRAN) is communications 354 network, commonly referred to as 3G, and consists of NodeBs (3G 355 base station) and Radio Network Controllers (RNC) which make up 356 the UMTS radio access network. The UTRAN allows connectivity 357 between the User Equipment and the core network. UTRAN comprises 358 of WCDMA, HSPA and HSPA+ radio technologies. 360 User Plane 362 Data traffic and the required bearers for the data traffic. In 363 practice IP is the only data traffic protocol used in user plane. 365 Wideband Code Division Multiple Access 367 The Wideband Code Division Multiple Access (WCDMA) is the radio 368 interface used in UMTS networks. 370 eNodeB 372 The eNodeB is a base station entity that supports the Long Term 373 Evolution (LTE) air interface. 375 2.2. The concept of APN 377 The Access Point Name (APN) essentially refers to a gateway in the 378 3GPP network. The 'complete' APN is expressed in a form of a Fully 379 Qualified Domain Name (FQDN) and also piggybacked on the 380 administration of the DNS namespace, thus effectively allowing the 381 discovery of gateways using the DNS. User Equipment (UE) can choose 382 to attach to a specific gateway in the packet core. The gateway 383 provides connectivity to the Packet Data Network (PDN) such as the 384 Internet. An operator may also include gateways which do not provide 385 Internet connectivity, rather a connectivity to closed network 386 providing a set of operator's own services. A UE can be attached to 387 one or more gateways simultaneously. The gateway in a 3GPP network 388 is the GGSN or PDN-GW. Figure 1 below illustrates the APN-based 389 network connectivity concept. 391 .--. 392 _(. `) 393 .--. +------------+ _( PDN `)_ 394 _(Core`. |GW1 |====( Internet `) 395 +---+ ( NW )------|APN=internet| ( ` . ) ) 396 [UE]~~~~|RAN|----( ` . ) )--+ +------------+ `--(_______)---' 397 ^ +---+ `--(___.-' | 398 | | .--. 399 | | +----------+ _(.PDN`) 400 | +--|GW2 | _(Operator`)_ 401 | |APN=OpServ|====( Services `) 402 UE is attached +----------+ ( ` . ) ) 403 to GW1 and GW2 `--(_______)---' 404 simultaneously 406 Figure 1: User Equipment attached to multiple APNs simultaneously 408 3. IP over 3GPP GPRS 410 3.1. Introduction to 3GPP GPRS 412 A simplified 2G/3G GPRS architecture is illustrated in Figure 2. 413 This architecture basically covers the GPRS core network since R99 to 414 Release-7, and radio access technologies such as GSM (2G), EDGE (2G, 415 often referred as 2.5G), WCDMA (3G) and HSPA(+) (3G, often referred 416 as 3.5G). The architecture shares obvious similarities with the 417 Evolved Packet System (EPS) as will be seen in Section 4. Based on 418 Gn/Gp interfaces, the GPRS core network functionality is logically 419 implemented on two network nodes, the SGSN and the GGSN. 421 3G 422 .--. .--. 423 Uu _( `. Iu +----+ +----+ _( `. 424 [UE]~~|~~~( UTRAN )--|---|SGSN|--|---|GGSN|--|----( PDN ) 425 ( ` . ) ) +----+ Gn +----+ Gi ( ` . ) ) 426 `--(___.-' / | `--(___.-' 427 / | 428 2G Gb-- | 429 .--. / | 430 _( `. / --Gp 431 [UE]~~|~~~( PDN )__/ | 432 Um ( ` . ) ) .--. 433 `--(___.-' _(. `) 434 _( [GGSN] `)_ 435 ( other `) 436 ( ` . PLMN ) ) 437 `--(_______)---' 439 Figure 2: Overview of the 2G/3G GPRS Logical Architecture 441 Gn/Gp: These interfaces provide a network based mobility service for 442 a UE and are used between a SGSN and a GGSN. The Gn 443 interface is used when GGSN and SGSN are located inside one 444 operator (i.e. PLMN). The Gp-interface is used if the GGSN 445 and the SGSN are located in different operator domains (i.e. 446 'other' PLMN). GTP protocol is defined for the Gn/Gp 447 interfaces (both GTP-C for the control plane and GTP-U for 448 the user plane). 450 Gb: Is the Base Station System (BSS) to SGSN interface, which is 451 used to carry information concerning packet data transmission 452 and layer-2 mobility management. The Gb-interface is based 453 on either on Frame Relay or IP. 455 Iu: Is the Radio Network System (RNS) to SGSN interface, which is 456 used to carry information concerning packet data transmission 457 and layer-2 mobility management. The user plane part of the 458 Iu-interface (actually the Iu-PS) is based on GTP-U. The 459 control plane part of the Iu-interface is based on Radio 460 Access Network Application Protocol (RANAP). 462 Gi: It is the interface between the GGSN and a PDN. The PDN may 463 be an operator external public or private packet data network 464 or an intra-operator packet data network. 466 Uu/Um: Are either 2G or 3G radio interfaces between a UE and a 467 respective radio access network. 469 The SGSN is responsible for the delivery of data packets from and to 470 the UE within its geographical service area when a direct tunnel 471 option is not used. If the direct tunnel is used, then the user 472 plane goes directly between the RNC (in the RNS) and the GGSN. The 473 control plane traffic always goes through the SGSN. For each UE 474 connected with the GPRS, at any given point of time, there is only 475 one SGSN. 477 3.2. PDP Context 479 A PDP (Packet Data Protocol) context is an association between a UE 480 represented by one IPv4 address and/or one /64 IPv6 prefix and a PDN 481 represented by an APN. Each PDN can be accessed via a gateway 482 (typically a GGSN or PDN-GW). On the UE a PDP context is equivalent 483 to a network interface. A UE may hence be attached to one or more 484 gateways via separate connections, i.e. PDP contexts. Each primary 485 PDP context has its own IPv4 address and/or one /64 IPv6 prefix 486 assigned to it by the PDN and anchored in the corresponding gateway. 487 Applications on the UE use the appropriate network interface (PDP 488 context) for connectivity to a specific PDN. Figure 3 represents a 489 high level view of what a PDP context implies in 3GPP networks. 491 Y 492 | +---------+ .--. 493 |--+ __________________________ | APNx in | _( `. 494 | |O______PDPc1_______________)| GGSN / |----(Internet) 495 | | | PDN-GW | ( ` . ) ) 496 |UE| +---------+ `--(___.-' 497 | | _______________________ +---------+ .--. 498 | |O______PDPc2____________)| APNy in | _(Priv`. 499 +--+ | GGSN / |-------(Network ) 500 | PDN-GW | ( ` . ) ) 501 +---------+ `--(___.-' 503 Figure 3: PDP contexts between the MS/UE and gateway 505 In the above figure there are two PDP contexts at the MS/UE (UE=User 506 Equipment in 3GPP parlance). The 'PDPc1' PDP context that is 507 connected to APNx provided Internet connectivity and the 'PDPc2' PDP 508 context provides connectivity to a private IP network via APNy (as an 509 example this network may include operator specific services such as 510 MMS (Multi media service). An application on the host such as a web 511 browser would use the PDP context that provides Internet connectivity 512 for accessing services on the Internet. An application such as MMS 513 would use APNy in the figure above because the service is provided 514 through the private network. 516 4. IP over 3GPP EPS 518 4.1. Introduction to 3GPP EPS 520 In its most basic form, the EPS architecture consists of only two 521 nodes on the user plane, a base station and a core network Gateway 522 (GW). The basic EPS architecture is illustrated in Figure 4. The 523 functional split of gateways allows for operators to choose optimized 524 topological locations of nodes within the network and enables various 525 deployment models including the sharing of radio networks between 526 different operators. This also allows independent scaling and growth 527 of traffic throughput and control signal processing. 529 +--------+ 530 S1-MME +-------+ S11 | IP | 531 +----|----| MME |---|----+ |Services| 532 | | | | +--------+ 533 | +-------+ | |SGi 534 +----+ LTE-Uu +-------+ S1-U +-------+ S5 +-------+ 535 |UE |----|---|eNodeB |---|----------------| SGW |--|---|PDN-GW | 536 | |========|=======|====================|=======|======| | 537 +----+ +-------+DualStack EPS Bearer+-------+ +-------+ 539 Figure 4: EPS Architecture for 3GPP Access 541 S5: It provides user plane tunnelling and tunnel management 542 between SGW and PDN-GW, using GTP or PMIPv6 as the network 543 based mobility management protocol. 545 S1-U: Provides user plane tunnelling and inter eNodeB path 546 switching during handover between eNodeB and SGW, using the 547 GTP-U protocol (GTP user plane). 549 S1-MME: Reference point for the control plane protocol between 550 eNodeB and MME. 552 SGi: It is the interface between the PDN-GW and the packet data 553 network. Packet data network may be an operator external 554 public or private packet data network or an intra operator 555 packet data network. 557 4.2. PDN Connection 559 A PDN connection is an association between a UE represented by one 560 IPv4 address and/or one /64 IPv6 prefix, and a PDN represented by an 561 APN. The PDN connection is the EPC equivalent of the GPRS PDP 562 context. Each PDN can be accessed via a gateway (a PDN-GW). PDN is 563 responsible for the IP address/prefix allocation to the UE. On the 564 UE a PDN connection is equivalent to a network interface. A UE may 565 hence be attached to one or more gateways via separate connections, 566 i.e. PDN connections. Each PDN connection has its own IP address/ 567 prefix assigned to it by the PDN and anchored in the corresponding 568 gateway. Applications on the UE use the appropriate network 569 interface (PDN connection) for connectivity. 571 4.3. EPS bearer model 573 The logical concept of a bearer has been defined to be an aggregate 574 of one or more IP flows related to one or more services. An EPS 575 bearer exists between the UE and the PDN-GW and is used to provide 576 the same level of packet forwarding treatment to the aggregated IP 577 flows constituting the bearer. Services with IP flows requiring a 578 different packet forwarding treatment would therefore require more 579 than one EPS bearer. The UE performs the binding of the uplink IP 580 flows to the bearer while the PDN-GW performs this function for the 581 downlink packets. 583 In order to provide low latency for always on connectivity, a default 584 bearer will be provided at the time of startup and an IPv4 address 585 and/or IPv6 prefix gets assigned to the UE (this is different from 586 GPRS, where UEs are not automatically assigned with an IP address or 587 prefix). This default bearer will be allowed to carry all traffic 588 which is not associated with a dedicated bearer. Dedicated bearers 589 are used to carry traffic for IP flows that have been identified to 590 require a specific packet forwarding treatment. They may be 591 established at the time of startup; for example, in the case of 592 services that require always-on connectivity and better QoS than that 593 provided by the default bearer. The default bearer and the dedicated 594 bearer(s) associated to it share the same IP address(es)/prefix. 596 An EPS bearer is referred to as a GBR bearer if dedicated network 597 resources related to a Guaranteed Bit Rate (GBR) value that is 598 associated with the EPS bearer are permanently allocated (e.g. by an 599 admission control function in the eNodeB) at bearer establishment/ 600 modification. Otherwise, an EPS bearer is referred to as a non-GBR 601 bearer. The default bearer is always non-GBR, with the resources for 602 the IP flows not guaranteed at eNodeB, and with no admission control. 603 However, the dedicated bearer can be either GBR or non-GBR. A GBR 604 bearer has a Guaranteed Bit Rate (GBR) and Maximum Bit Rate (MBR) 605 while more than one non-GBR bearer belonging to the same UE shares an 606 Aggregate Maximum Bit Rate (AMBR). Non-GBR bearers can suffer packet 607 loss under congestion while GBR bearers are immune to such losses. 609 5. Address Management 611 5.1. IPv4 Address Configuration 613 UE's IPv4 address configuration is always performed during PDP 614 context/EPS bearer setup procedures (on layer-2). DHCPv4-based 615 [RFC2131] address configuration is supported by the 3GPP 616 specifications, but is not used in wide scale. The UE must always 617 support address configuration as part of the bearer setup signaling, 618 since DHCPv4 is optional for both UEs and networks. 620 5.2. IPv6 Address Configuration 622 IPv6 Stateless Address Autoconfiguration (SLAAC) as specified in 623 [RFC4861][RFC4862] is the only supported address configuration 624 mechanism. Stateful DHCPv6-based address configuration [RFC3315] is 625 not supported by 3GPP specifications. On the other hand, Stateless 626 DHCPv6-service to obtain other configuration information is supported 627 [RFC3736]. This implies that the M-bit is always zero and the O-bit 628 may be set to one in the Router Advertisement (RA) sent to the UE. 630 3GPP network allocates each default bearer a unique /64 prefix, and 631 uses layer-2 signaling to suggest user equipment an Interface 632 Identifier that is guaranteed not to conflict with gateway's 633 Interface Identifier. The UE must configure its link-local address 634 using this Interface Identifier. The UE is allowed to use any 635 Interface Identifier it wishes for the other addresses it configures. 636 There is no restriction, for example, of using Privacy Extension for 637 SLAAC [RFC4941] or other similar types of mechanisms. However, there 638 are network drivers that fail to pass the Interface Identifier to the 639 stack and instead synthesize their own Interface Identifier (usually 640 a MAC address equivalent). If the UE skips the Duplicate Address 641 Detection (DAD) and also has other issues with the Neighbor Discovery 642 Protocol (see Section 5.4), then there is a small theoretical chance 643 that the UE configures exactly the same link-local address as the 644 GGSN/PDN-GW. The address collision may then cause issues in the IP 645 connectivity, for instance, the UE not being able to forward any 646 packets to uplink. 648 In the 3GPP link model the /64 prefix assigned to the UE cannot be 649 used for on-link determination (because the L-bit in the Prefix 650 Information Option (PIO) in the RA must always be set to zero). If 651 the advertised prefix is used for SLAAC then the A-bit in the PIO 652 must be set to one. The details of the 3GPP link-model and address 653 configuration is described in Section 11.2.1.3.2a of [TS.29061]. 654 More specifically, the GGSN/PDN-GW guarantees that the /64 prefix is 655 unique for the UE. Therefore, there is no need to perform any 656 Duplicate Address Detection (DAD) on addresses the UE creates (i.e., 657 the 'DupAddrDetectTransmits' variable in the UE could be zero). The 658 GGSN/PDN-GW is not allowed to generate any globally unique IPv6 659 addresses for itself using the /64 prefix assigned to the UE in the 660 RA. 662 The current 3GPP architecture limits number of prefixes in each 663 bearer to a single /64 prefix. If the UE finds more than one prefix 664 in the RA, it only considers the first one and silently discards the 665 others [TS.29061]. Therefore, multi-homing within a single bearer is 666 not possible. Renumbering without closing layer-2 connection is also 667 not possible. The lifetime of /64 prefix is bound to lifetime of 668 layer-2 connection even if the advertised prefix lifetime is longer 669 than the layer-2 connection lifetime. 671 5.3. Prefix Delegation 673 IPv6 prefix delegation is a part of Release-10 and is not covered by 674 any earlier release. However, the /64 prefix allocated for each 675 default bearer (and to the user equipment) may be shared to local 676 area network by user equipment implementing Neighbor Discovery proxy 677 (ND proxy) [RFC4389] functionality. 679 Release-10 prefix delegation uses the DHCPv6-based prefix delegation 680 [RFC3633]. The model defined for Release-10 requires aggregatable 681 prefixes, which means the /64 prefix allocated for the default bearer 682 (and to the user equipment) must be part of the shorter delegated 683 prefix. DHCPv6 prefix delegation has an explicit limitation 684 described in Section 12.1 of [RFC3633] that a prefix delegated to a 685 requesting router cannot be used by the delegating router (i.e., the 686 PDN-GW in this case). This implies the shorter 'delegated prefix' 687 cannot be given to the requesting router (i.e. the user equipment) as 688 such but has to be delivered by the delegating router (i.e. the 689 PDN-GW) in such a way the /64 prefix allocated to the default bearer 690 is not part of the 'delegated prefix'. An option to exclude a prefix 691 from delegation [I-D.ietf-dhc-pd-exclude] prevents this problem. 693 5.4. IPv6 Neighbor Discovery Considerations 695 3GPP link between the UE and the next hop router (e.g. GGSN) 696 resemble a point to point (p2p) link, which has no link-layer 697 addresses [RFC3316] and this has not changed from 2G/3G GPRS to EPS. 698 The UE IP stack has to take this into consideration. When the 3GPP 699 PDP Context appears as a PPP interface/link to the UE, the IP stack 700 is usually prepared to handle Neighbor Discovery protocol and the 701 related Neighbor Cache state machine transitions in an appropriate 702 way, even though Neighbor Discovery protocol messages contain no link 703 layer address information. However, some operating systems discard 704 Router Advertisements on their PPP interface/link as a default 705 setting. This causes the SLAAC to fail when the 3GPP PDP Context 706 gets established, thus stalling all IPv6 traffic. 708 Currently several operating systems and their network drivers can 709 make the 3GPP PDP Context to appear as an IEEE802 interface/link to 710 the IP stack. This has few known issues, especially when the IP 711 stack is made to believe the underlying link has link-layer 712 addresses. First, the Neighbor Advertisement sent by a GGSN as a 713 response to an address resolution triggered Neighbor Solicitation may 714 not contain a Target Link-Layer address option (as suggested in 715 [RFC4861] Section 4.4). Then it is possible that the address 716 resolution never completes when the UE tries to resolve the link- 717 layer address of the GGSN, thus stalling all IPv6 traffic. 719 Second, the GGSN may simply discard all address resolution triggered 720 Neighbor Solicitation messages (as sometimes misinterpreted from 721 [RFC3316] Section 2.4.1 that responding to address resolution and 722 next-hop determination are not needed). As a result the address 723 resolution never completes when the UE tries to resolve the link- 724 layer address of the GGSN, thus stalling all IPv6 traffic. There is 725 little that can be done about this in the GGSN, assuming the Neighbor 726 Discovery implementation already does the right thing. But the UE 727 stacks must be able to handle address resolution in the manner that 728 they have chosen to represent the interface. In other words, if they 729 emulate IEEE802 type interfaces, they also need to process Neighbor 730 Discovery messages correctly. 732 6. 3GPP Dual-Stack Approach to IPv6 734 6.1. 3GPP Networks Prior to Release-8 736 3GPP standards prior to Release-8 provide IPv6 access for cellular 737 devices with PDP contexts of type IPv6 [TS.23060]. For dual-stack 738 access, a PDP context of type IPv6 is established in parallel to the 739 PDP context of type IPv4, as shown in Figure 5 and Figure 6. For 740 IPv4-only service, connections are created over the PDP context of 741 type IPv4 and for IPv6-only service connections are created over the 742 PDP context of type IPv6. The two PDP contexts of different type may 743 use the same APN (and the gateway), however, this aspect is not 744 explicitly defined in standards. Therefore, cellular device and 745 gateway implementations from different vendors may have varying 746 support for this functionality. 748 Y .--. 749 | _(IPv4`. 750 |---+ +---+ +---+ ( PDN ) 751 | D |~~~~~~~//-----| |====| |====( ` . ) ) 752 | S | IPv4 context | S | | G | `--(___.-' 753 | | | G | | G | .--. 754 | U | | S | | S | _(IPv6`. 755 | E | IPv6 context | N | | N | ( PDN ) 756 |///|~~~~~~~//-----| |====|(s)|====( ` . ) ) 757 +---+ +---+ +---+ `--(___.-' 759 Figure 5: A dual-stack User Equipment connecting to both IPv4 and 760 IPv6 Internet using parallel IPv4-only and IPv6-only PDP contexts 762 Y 763 | 764 |---+ +---+ +---+ 765 | D |~~~~~~~//-----| |====| | .--. 766 | S | IPv4 context | S | | G | _( DS `. 767 | | | G | | G | ( PDN ) 768 | U | | S | | S |====( ` . ) ) 769 | E | IPv6 context | N | | N | `--(___.-' 770 |///|~~~~~~~//-----| |====| | 771 +---+ +---+ +---+ 773 Figure 6: A dual-stack User Equipment connecting to dual-stack 774 Internet using parallel IPv4-only and IPv6-only PDP contexts 776 The approach of having parallel IPv4 and IPv6 type of PDP contexts 777 open is not optimal, because two PDP contexts require double the 778 signaling and consume more network resources than a single PDP 779 context. In the figure above the IPv4 and IPv6 PDP contexts are 780 attached to the same GGSN. While this is possible, the dual-stack 781 (DS) MS may be attached to different GGSNs in the scenario where one 782 GGSN supports IPv4 PDN connectivity while another GGSN provides IPv6 783 PDN connectivity. 785 6.2. 3GPP Release-8 and -9 Networks 787 Since 3GPP Release-8, the powerful concept of a dual-stack type of 788 PDN connection and EPS bearer have been introduced [TS.23401]. This 789 enables parallel use of both IPv4 and IPv6 on a single bearer 790 (IPv4v6), as illustrated in Figure 7, and makes dual stack simpler 791 than in earlier 3GPP releases. As of Release-9, GPRS network nodes 792 also support dual-stack type (IPv4v6) PDP contexts. 794 Y 795 | 796 |---+ +---+ +---+ 797 | D | | | | P | .--. 798 | S | | | | D | _( DS `. 799 | | IPv4v6 (DS) | S | | N | ( PDN ) 800 | U |~~~~~~~//-----| G |====| - |====( ` . ) ) 801 | E | bearer | W | | G | `--(___.-' 802 |///| | | | W | 803 +---+ +---+ +---+ 805 Figure 7: A dual-stack User Equipment connecting to dual-stack 806 Internet using a single IPv4v6 type PDN connection 808 The following is a description of the various PDP contexts/PDN bearer 809 types that are specified by 3GPP: 811 1. For 2G/3G access to GPRS core (SGSN/GGSN) pre-Release-9 there are 812 two IP PDP Types, IPv4 and IPv6. Two PDP contexts are needed to 813 get dual stack connectivity. 815 2. For 2G/3G access to GPRS core (SGSN/GGSN) from Release-9 there 816 are three IP PDP Types, IPv4, IPv6 and IPv4v6. Minimum one PDP 817 context is needed to get dual stack connectivity. 819 3. For 2G/3G access to EPC core (PDN-GW via S4-SGSN) from Release-8 820 there are three IP PDP Types, IPv4, IPv6 and IPv4v6 which gets 821 mapped to PDN Connection type. Minimum one PDP Context is needed 822 to get dual stack connectivity. 824 4. For LTE (E-UTRAN) access to EPC core from Release-8 there are 825 three IP PDN Types, IPv4, IPv6 and IPv4v6. Minimum one PDN 826 Connection is needed to get dual stack connectivity. 828 6.3. PDN Connection Establishment Process 830 The PDN connection establishment process is specified in detail in 831 3GPP specifications. Figure 8 illustrates the high level process and 832 signaling involved in the establishment of a PDN connection. 834 UE eNb/ MME SGW PDN-GW HSS/ 835 | BS | | | AAA 836 | | | | | | 837 |---------->|(1) | | | | 838 | |---------->|(1) | | | 839 | | | | | | 840 |/---------------------------------------------------------\| 841 | Authentication and Authorization |(2) 842 |\---------------------------------------------------------/| 843 | | | | | | 844 | | |---------->|(3) | | 845 | | | |---------->|(3) | 846 | | | | | | 847 | | | |<----------|(4) | 848 | | |<----------|(4) | | 849 | |<----------|(5) | | | 850 |/---------\| | | | | 851 | RB setup |(6) | | | | 852 |\---------/| | | | | 853 | |---------->|(7) | | | 854 |---------->|(8) | | | | 855 | |---------->|(9) | | | 856 | | | | | | 857 |============= Uplink Data =========>==========>|(10) | 858 | | | | | | 859 | | |---------->|(11) | | 860 | | | | | | 861 | | |<----------|(12) | | 862 | | | | | | 863 |<============ Downlink Data =======<===========|(13) | 864 | | | | | | 866 Figure 8: Simplified PDN connection setup procedure in Release-8 868 1. The UE (i.e the MS) requires a data connection and hence decides 869 to establish a PDN connection with a PDN-GW. The UE sends an 870 "Attach Request" (layer-2) to the BS. The BS forwards this 871 attach request to the MME. 873 2. Authentication of the UE with the AAA server/HSS follows. If 874 the UE is authorized for establishing a data connection, the 875 following steps continue 877 3. The MME sends a "Create Session Request" message to the 878 Serving-GW. The SGW forwards the create session request to the 879 PDN-GW. The SGW knows the address of the PDN-GW to forward the 880 create session request to as a result of this information having 881 been obtained by the MME during the authentication/authorization 882 phase. 884 The UE IPv4 address and/or IPv6 prefix get assigned during this 885 step. If a subscribed IPv4 address and/or IPv6 prefix is 886 statically allocated for the UE for this APN, then the MME 887 already passes the address information to the SGW and eventually 888 to the PDN-GW in the "Create Session Request" message. 889 Otherwise, the PDN-GW manages the address assignment to the UE 890 (there is another variation to this where IPv4 address 891 allocation is delayed until the UE initiates a DHCPv4 exchange 892 but this is not discussed here). 894 4. The PDN-GW creates a PDN connection for the UE and sends "Create 895 Session Response" message to the SGW from which the session 896 request message was received from. The SGW forwards the 897 response to the corresponding MME which originated the request. 899 5. The MME sends the "Attach Accept/Initial Context Setup request" 900 message to the eNodeB/BS. 902 6. The radio bearer between the UE and the eNb is reconfigured 903 based on the parameters received from the MME. (See note 1 904 below) 906 7. The eNb sends "Initial Context Response" message to the MME. 908 8. The UE sends a "Direct Transfer" message to the eNodeB which 909 includes the Attach complete signal. 911 9. The eNodeB forwards the Attach complete message to the MME. 913 10. The UE can now start sending uplink packets to the PDN GW. 915 11. The MME sends a "Modify Bearer Request" message to the SGW. 917 12. The SGW responds with a "Modify Bearer Response" message. At 918 this time the downlink connection is also ready. 920 13. The UE can now start receiving downlink packets, including 921 possible SLAAC related IPv6 packets. 923 The type of PDN connection established between the UE and the PDN-GW 924 can be any of the types described in the previous section. The dual- 925 stack (DS) PDN connection, i.e the one which supports both IPv4 and 926 IPv6 packets is the default one that will be established if no 927 specific PDN connection type is specified by the UE in Release-8 928 networks. 930 Note 1: The UE receives the PDN Address Information Element 931 [TS.24301] at the end of radio bearer setup messaging. This 932 Information Element contains only the Interface Identifier of the 933 IPv6 address. In a case of GPRS the PDP Address Information 934 Element [TS.24008] would contain a complete IPv6 address. 935 However, the UE must ignore the IPv6 prefix if it receives one in 936 the message (see Section 11.2.1.3.2a of [TS.29061]). 938 6.4. Mobility of 3GPP IPv4v6 Type of Bearers 940 3GPP discussed at length various approaches to support mobility 941 between a Release-8 LTE network and a pre-Release-9 2G/3G network 942 without a S4-SGSN for the new dual-stack type of bearers. The chosen 943 approach for mobility is as follows, in short: if a UE is allowed for 944 doing handovers between a Release-8 LTE network and a pre-Release-9 945 2G/3G network without a S4-SGSN while having open PDN connections, 946 only single stack bearers are used. Essentially this means following 947 deployment options: 949 1. If a network knows a UE may do handovers between a Release-8 LTE 950 network and a pre-Release-9 2G/3G network without a S4-SGSN, then 951 the network is configured to provide only single stack bearers, 952 even if the UE requests dual-stack bearers. 954 2. If the network knows the UE does handovers only between a 955 Release-8 LTE network and a Release-9 2G/3G network or a pre- 956 Release-9 network with a S4-SGSN, then the network is configured 957 to provide the UE with dual-stack bearers on request. The same 958 also applies for LTE-only deployments. 960 When a network operator and their roaming partners have upgraded 961 their networks to Release-8, it is possible to use the new IPv4v6 962 dual-stack type of bearers. A Release-8 UE always requests for a 963 dual-stack bearer, but accepts what is assigned by the network. 965 7. Dual-Stack Approach to IPv6 Transition in 3GPP Networks 967 3GPP networks can natively transport IPv4 and IPv6 packets between 968 the UE and the gateway (GGSN or PDN-GW) as a result of establishing 969 either a dual-stack PDP context or parallel IPv4 and IPv6 PDP 970 contexts. 972 Current deployments of 3GPP networks primarily support IPv4-only. 973 These networks can be upgraded to also support IPv6 PDP contexts. By 974 doing so devices and applications that are IPv6 capable can start 975 utilizing the IPv6 connectivity. This will also ensure that legacy 976 devices and applications continue to work with no impact. As newer 977 devices start using IPv6 connectivity, the demand for actively used 978 IPv4 connections is expected to slowly decrease, helping operators 979 with a transition to IPv6. With a dual-stack approach, there is 980 always the potential to fallback to IPv4. A device which may be 981 roaming in a network wherein IPv6 is not supported by the visited 982 network could fall back to using IPv4 PDP contexts and hence the end 983 user would at least get some connectivity. Unfortunately, dual-stack 984 approach as such does not lower the number of used IPv4 addresses. 985 Every dual-stack bearer still needs to be given an IPv4 address, 986 private or public. This is a major concern with dual-stack bearers 987 concerning IPv6 transition. However, if the majority of active IP 988 communication has moved over to IPv6, then in case of Network Address 989 Translation from IPv4 to IPv4 (NAT44) [RFC1918] IPv4 connections the 990 number of active IPv4 connections can still be expected to gradually 991 decrease and thus giving some level of relief regarding NAT44 992 function scalability. 994 As the networks evolve to support Release-8 EPS architecture and the 995 dual-stack PDP contexts, newer devices will be able to leverage such 996 capability and have a single bearer which supports both IPv4 and 997 IPv6. Since IPv4 and IPv6 packets are carried as payload within GTP 998 between the MS and the gateway (GGSN/PDN-GW) the transport network 999 capability in terms of whether it supports IPv4 or IPv6 on the 1000 interfaces between the eNodeB and SGW or, SGW and PDN-GW is 1001 immaterial. 1003 8. Deployment issues 1005 8.1. Overlapping IPv4 Addresses 1007 Given the shortage of globally routable public IPv4 addresses, 1008 operators tend to assign private IPv4 addresses [RFC1918] to UEs when 1009 they establish an IPv4-only PDP context or an IPv4v6 type PDN 1010 context. About 16 million UEs can be assigned a private IPv4 address 1011 that is unique within a domain. However, in case of many operators 1012 the number of subscribers is greater than 16 million. The issue can 1013 be dealt with by assigning overlapping RFC 1918 IPv4 addresses to 1014 UEs. As a result the IPv4 address assigned to a UE within the 1015 context of a single operator realm would no longer be unique. This 1016 has the obvious and known issues of NATed IP connection in the 1017 Internet. Direct UE to UE connectivity becomes complicated, unless 1018 the UEs are within the same private address range pool and/or 1019 anchored to the same gateway, referrals using IP addresses will have 1020 issues and so forth. These are generic issues and not only a concern 1021 of the EPS. However, 3GPP as such does not have any mandatory 1022 language concerning NAT44 functionality in EPC. Obvious deployment 1023 choices apply also to EPC: 1025 1. Very large network deployments are partitioned, for example, 1026 based on a geographical areas. This partitioning allows for 1027 overlapping IPv4 addresses ranges to be assigned to UEs that are 1028 in different areas. Each area has its own pool of gateways that 1029 are dedicated for a certain overlapping IPv4 address range 1030 (referred here later as a zone). Standard NAT44 functionality 1031 allows for communication from the [RFC1918] private zone to the 1032 Internet. Communication between zones require special 1033 arrangement, such as using intermediate gateways (e.g. Back to 1034 Back User Agent (B2BUA) in case of SIP). 1036 2. A UE attaches to a gateway as part of the attach process. The 1037 number of UEs that a gateway supports is in the order of 1 to 10 1038 million. Hence all the UEs assigned to a single gateway can be 1039 assigned private IPv4 addresses. Operators with large subscriber 1040 bases have multiple gateways and hence the same [RFC1918] IPv4 1041 address space can be reused across gateways. The IPv4 address 1042 assigned to a UE is unique within the scope of a single gateway. 1044 3. New services requiring direct connectivity between UEs should be 1045 built on IPv6. Possible existing IPv4-only services and 1046 applications requiring direct connectivity can be ported to IPv6. 1048 8.2. IPv6 for transport 1050 The various reference points of the 3GPP architecture such as S1-U, 1051 S5 and S8 are based on either GTP or PMIPv6. The underlying 1052 transport for these reference points can be IPv4 or IPv6. GTP has 1053 been able to operate over IPv6 transport (optionally) since R99 and 1054 PMIPv6 has supported IPv6 transport starting from its introduction in 1055 Release-8. The user plane traffic between the UE and the gateway can 1056 use either IPv4 or IPv6. These packets are essentially treated as 1057 payload by GTP/PMIPv6 and transported accordingly with no real 1058 attention paid to the information (at least from a routing 1059 perspective) contained in the IPv4 or IPv6 headers. The transport 1060 links between the eNodeB and the SGW, and the link between the SGW 1061 and PDN-GW can be migrated to IPv6 without any direct implications to 1062 the architecture. 1064 Currently, the inter-operator (for 3GPP technology) roaming networks 1065 are all IPv4-only (see Inter-PLMN Backbone Guidelines [GSMA.IR.34]). 1066 Eventually these roaming networks will also get migrated to IPv6, if 1067 there is a business reason for that. The migration period can be 1068 prolonged considerably because the 3GPP protocols always tunnel user 1069 plane traffic in the core network and as described earlier the 1070 transport network IP version is not in any way tied to user plane IP 1071 version. Furthermore, the design of the inter-operator roaming 1072 networks is such that the user plane and transport network IP 1073 addressing is completely separated from each other. The inter- 1074 operator roaming network itself is also completely separated from the 1075 Internet. Only those core network nodes that must be connected to 1076 the inter-operator roaming networks are actually visible there, and 1077 be able to send and receive (tunneled) traffic within the inter- 1078 operator roaming networks. Obviously, in order the roaming to work 1079 properly, the operators have to agree on supported protocol versions 1080 so that the visited network does not, for example, unnecessarily drop 1081 user plane IPv6 traffic. 1083 8.3. Operational Aspects of Running Dual-Stack Networks 1085 Operating dual-stack networks does imply cost and complexity to a 1086 certain extent. However these factors are mitigated by the assurance 1087 that legacy devices and services are unaffected and there is always a 1088 fallback to IPv4 in case of issues with the IPv6 deployment or 1089 network elements. The model also enables operators to develop 1090 operational experience and expertise in an incremental manner. 1092 Running dual-stack networks requires the management of multiple IP 1093 address spaces. Tracking of UEs needs to be expanded since it can be 1094 identified by either an IPv4 address or IPv6 prefix. Network 1095 elements will also need to be dual-stack capable in order to support 1096 the dual-stack deployment model. 1098 Deployment and migration cases described in Section 6.1 for providing 1099 dual-stack like capability may mean doubled resource usage in 1100 operator's network. This is a major concern against providing dual- 1101 stack like connectivity using techniques discussed in Section 6.1. 1102 Also handovers between networks with different capabilities in terms 1103 of networks being dual-stack like service capable or not, may turn 1104 out hard to comprehend for users and for application/services to cope 1105 with. These facts may add other than just technical concerns for 1106 operators when planning to roll out dual-stack service offerings. 1108 8.4. Operational Aspects of Running a Network with IPv6-only Bearers 1110 It is possible to allocate IPv6-only type bearers to UEs in 3GPP 1111 networks. IPv6-only bearer type has been part of the 3GPP 1112 specification since the beginning. In 3GPP Release-8 (and later) it 1113 was defined that a dual-stack UE (or when the radio equipment has no 1114 knowledge of the UE IP stack capabilities) must first attempt to 1115 establish a dual-stack bearer and then possibly fall back to single 1116 IP version bearer. A Release-8 (or later) UE with IPv6-only stack 1117 can directly attempt to establish an IPv6-only bearer. The IPv6-only 1118 behaviour is up to a subscription provisioning or a PDN-GW 1119 configuration, and the fallback scenarios do not necessarily cause 1120 additional signaling. 1122 Although the bullets below introduce IPv6 to IPv4 address translation 1123 and specifically discuss NAT64 technology [RFC6144], the current 3GPP 1124 Release-8 architecture does not describe the use of address 1125 translation or NAT64. It is up to a specific deployment whether 1126 address translation is part of the network or not. Some operational 1127 aspects to consider for running a network with IPv6-only bearers: 1129 o The UE must have an IPv6 capable stack and a radio interface 1130 capable of establishing an IPv6 PDP context or PDN connection. 1132 o The GGSN/PDN-GW must be IPv6 capable in order to support IPv6 1133 bearers. Furthermore, the SGSN/MME must allow the creation of PDP 1134 Type or PDN Type of IPv6. 1136 o Many of the common applications are IP version agnostic and hence 1137 would work using an IPv6 bearer. However, applications that are 1138 IPv4 specific would not work. 1140 o Inter-operator roaming is another aspect which causes issues, at 1141 least during the ramp up phase of the IPv6 deployment. If the 1142 visited network to which outbound roamers attach to does not 1143 support PDP/PDN Type IPv6, then there needs to be a fallback 1144 option. The fallback option in this specific case is mostly up to 1145 the UE to implement. Several cases are discussed in the following 1146 sections. 1148 o If and when a UE using IPv6-only bearer needs to access to IPv4 1149 Internet/network, a translation of some type from IPv6 to IPv4 has 1150 to be deployed in the network. NAT64 (and DNS64) is one solution 1151 that can be used for this purpose and works for a certain set of 1152 protocols (read TCP, UDP and ICMP, and when applications actually 1153 use DNS for resolving name to IP addresses). 1155 8.5. Restricting Outbound IPv6 Roaming 1157 Roaming was briefly touched upon in Sections 8.2 and 8.4. While 1158 there is interest in offering roaming service for IPv6 enabled UEs 1159 and subscriptions, not all visited networks are prepared for IPv6 1160 outbound roamers: 1162 o The visited network SGSN does not support the IPv6 PDP Context or 1163 IPv4v6 PDP Context types. These should mostly concern pre- 1164 Release-9 2G/3G networks without S4-SGSN but there is no 1165 definitive rule as the deployed feature sets vary depending on 1166 implementations and licenses. 1168 o The visited network might not be commercially ready for IPv6 1169 outbound roamers, while everything might work technically at the 1170 user plane level. This would lead to "revenue leakage" especially 1171 from the visited operator point of view (note that the use of 1172 visited network GGSN/PDN-GW does not really exist in commercial 1173 deployments today for data roaming). 1175 It might be in the interest of operators to prohibit roaming 1176 selectively within specific visited networks until IPv6 roaming is in 1177 place. 3GPP does not specify a mechanism whereby IPv6 roaming is 1178 prohibited without also disabling IPv4 access and other packet 1179 services. The following options for disabling IPv6 access for 1180 roaming subscribers could be available in some network deployments: 1182 o Using Policy and Charging Control (PCC) [TS.23203] functionality 1183 and its rules to fail, for example, the bearer authorization when 1184 a desired criteria is met. In this case that would be PDN/PDP 1185 Type IPv6/IPv4v6 and a specific visited network. The rules can be 1186 provisioned either in the home network or locally in the visited 1187 network. 1189 o Some Home Location Register (HLR) and Home Subscriber Server (HSS) 1190 subscriber databases allow prohibiting roaming in a specific 1191 (visited) network for a specified PDN/PDP Type. 1193 The obvious problems are that these solutions are not mandatory, are 1194 not unified across networks, and therefore also lack well-specified 1195 fall back mechanism from the UE point of view. 1197 8.6. Inter-RAT Handovers and IP Versions 1199 It is obvious that operators start incrementally deploy EPS along 1200 with the existing UTRAN/GERAN, handovers between different radio 1201 technologies (inter-RAT handovers) become inevitable. In case of 1202 inter-RAT handovers 3GPP supports the following IP addressing 1203 scenarios: 1205 o E-UTRAN IPv4v6 bearer has to map one to one to UTRAN/GERAN IPv4v6 1206 bearer. 1208 o E-UTRAN IPv6 bearer has to map one to one to UTRAN/GERAN IPv6 1209 bearer. 1211 o E-UTRAN IPv4 bearer has to map one to one to UTRAN/GERAN IPv4 1212 bearer. 1214 Other types of configurations are not standardized. What the above 1215 rules essentially imply is that the network migration has to be 1216 planned and subscriptions provisioned based on the lowest common 1217 nominator, if inter-RAT handovers are desired. For example, if some 1218 part of the UTRAN network cannot serve anything but IPv4 bearers, 1219 then the E-UTRAN is also forced to provide only IPv4 bearers. 1220 Various combinations of subscriber provisioning regarding IP versions 1221 are discussed further in Section 8.7. 1223 8.7. Provisioning of IPv6 Subscribers and Various Combinations During 1224 Initial Network Attachment 1226 Subscribers' provisioned PDP/PDN Types have multiple configurations. 1227 The supported PDP/PDN Type is provisioned per each APN for every 1228 subscriber. The following PDN Types are possible in the HSS for a 1229 Release-8 subscription [TS.23401]: 1231 o IPv4v6 PDN Type (note that IPv4v6 PDP Type does not exist in a HLR 1232 and Mobile Application Part (MAP) [TS.29002] signaling prior 1233 Release-9). 1235 o IPv6-only PDN Type 1237 o IPv4-only PDN Type. 1239 o IPv4_or_IPv6 PDN Type (note that IPv4_or_IPv6 PDP Type does not 1240 exist in a HLR or MAP signaling. However, a HLR may have multiple 1241 APN configurations of different PDN Types, which effectively 1242 achieves the same functionality). 1244 A Release-8 dual-stack UE must always attempt to establish a PDP/PDN 1245 Type IPv4v6 bearer. The same also applies when the modem part of the 1246 UE does not have exact knowledge whether the UE operating system IP 1247 stack is a dual-stack capable or not. A UE that is IPv6-only capable 1248 must attempt to establish a PDP/PDN Type IPv6 bearer. Last, a UE 1249 that is IPv4-only capable must attempt to establish a PDN/PDP Type 1250 IPv4 bearer. 1252 In a case the PDP/PDN Type requested by a UE does not match what has 1253 been provisioned for the subscriber in the HSS (or HLR), the UE 1254 possibly falls back to a different PDP/PDN Type. The network (i.e. 1255 the MME or the S4-SGSN) is able to inform the UE during the network 1256 attachment signaling why it did not get the requested PDP/PDN Type. 1257 These response/cause codes are documented in [TS.24008] for requested 1258 PDP Types and [TS.24301] for requested PDN Types: 1260 o (E)SM cause #50 "PDN/PDP type IPv4-only allowed". 1262 o (E)SM cause #51 "PDN/PDP type IPv6-only allowed". 1264 o (E)SM cause #52 "single address bearers only allowed". 1266 The above response/cause codes apply to Release-8 and onwards. In 1267 pre-Release-8 networks used response/cause codes vary depending on 1268 the vendor, unfortunately. 1270 Possible fall back cases when the network deploys MMEs and/or S4- 1271 SGSNs include (as documented in [TS.23401]): 1273 o Requested and provisioned PDP/PDN Types match => requested. 1275 o Requested IPv4v6 and provisioned IPv6 => IPv6 and a UE receives 1276 indication that IPv6-only bearer is allowed. 1278 o Requested IPv4v6 and provisioned IPv4 => IPv4 and the UE receives 1279 indication that IPv4-only bearer is allowed. 1281 o Requested IPv4v6 and provisioned IPv4_or_IPv6 => IPv4 or IPv6 is 1282 selected by the MME/S4-SGSN based on an unspecified criteria. The 1283 UE may then attempt to establish, based on the UE implementation, 1284 a parallel bearer of a different PDP/PDN Type. 1286 o Other combinations cause the bearer establishment to fail. 1288 In addition to PDP/PDN Types provisioned in the HSS, it is also 1289 possible for a PDN-GW (and a MME/S4-SGSN) to affect the final 1290 selected PDP/PDN Type: 1292 o Requested IPv4v6 and configured IPv4 or IPv6 in the PDN-GW => IPv4 1293 or IPv6. If the MME operator had included the "Dual Address 1294 Bearer Flag" into the bearer establishment signaling, then the UE 1295 receives an indication that IPv6-only or IPv4-only bearer is 1296 allowed. 1298 o Requested IPv4v6 and configured IPv4 or IPv6 in the PDN-GW => IPv4 1299 or IPv6. If the MME operator had not included the "Dual Address 1300 Bearer Flag" into the bearer establishment signaling, then the UE 1301 may attempt to establish, based on the UE implementation, a 1302 parallel bearer of different PDP/PDN Type. 1304 A SGSN that does not understand the requested PDP Type is supposed to 1305 handle the requested PDP Type as IPv4. If for some reason a MME does 1306 not understand the requested PDN Type, then the PDN Type is handled 1307 as IPv6. 1309 9. IANA Considerations 1311 This document has no requests to IANA. 1313 10. Security Considerations 1315 This document does not introduce any security related concerns. 1316 Section 5 of [RFC3316] already contains in depth discussion of IPv6 1317 related security considerations in 3GPP networks prior Release-8. 1318 This section discusses few additional security concerns to take into 1319 consideration. 1321 In 3GPP access the UE and the network always perform a mutual 1322 authentication during the network attachment [TS.33102][TS.33401]. 1323 Furthermore, each time a PDP Context/PDN Connection gets created, a 1324 new connection, a modification of an existing connection and an 1325 assignment of an IPv6 prefix or an IP address can be authorized 1326 against the PCC infrastructure [TS.23203] and/or PDN's AAA server. 1328 The wireless part of the 3GPP link between the UE and the (e)NodeB as 1329 well as the signaling messages between the UE and the MME/SGSN can be 1330 protected depending on the regional regulation and operators' 1331 deployment policy. User plane traffic can be confidentiality 1332 protected. The control plane is always at least integrity and replay 1333 protected, and may also be confidentiality protected. The protection 1334 within the transmission part of the network depends on operators' 1335 deployment policy. [TS.33401] 1337 Several of the on-link and neighbor discovery related attacks can be 1338 mitigated due the nature of 3GPP point to point link model, and the 1339 fact the UE and the first hop router (PGW/GGSN or SGW) being the only 1340 nodes on the link. For off-link IPv6 attacks the 3GPP EPS is as 1341 vulnerable as any IPv6 system. 1343 There have also been concerns that the UE IP stack might use 1344 permanent subscriber identities, such as IMSI, as the source for IPv6 1345 address Interface Identifier. This would be a privacy threat and 1346 allow tracking of subscribers, and therefore use of IMSI (or any 1347 [TS.23003] defined identity) as the Interface Identifier is 1348 prohibited [TS.23401]. However, there is no standardized method to 1349 block such misbehaving UEs. 1351 11. Summary and Conclusion 1353 The 3GPP network architecture and specifications enable the 1354 establishment of IPv4 and IPv6 connections through the use of 1355 appropriate PDP context types. The current generation of deployed 1356 networks can support dual-stack connectivity if the packet core 1357 network elements such as the SGSN and GGSN have the capability. With 1358 Release-8, 3GPP has specified a more optimal PDP context type which 1359 enables the transport of IPv4 and IPv6 packets within a single PDP 1360 context between the UE and the gateway. 1362 As devices and applications are upgraded to support IPv6 they can 1363 start leveraging the IPv6 connectivity provided by the networks while 1364 maintaining the fall back to IPv4 capability. Enabling IPv6 1365 connectivity in the 3GPP networks by itself will provide some degree 1366 of relief to the IPv4 address space as many of the applications and 1367 services can start to work over IPv6. However without comprehensive 1368 testing of different applications and solutions that exist today and 1369 are widely used, for their ability to operate over IPv6 PDN 1370 connections, an IPv6-only access would cause disruptions. 1372 12. Acknowledgements 1374 The authors thank Shabnam Sultana, Sri Gundavelli, Hui Deng, 1375 Zhenqiang Li, Mikael Abrahamsson, James Woodyatt, Martin Thomson, 1376 Russ Mundy, Cameron Byrne, Ales Vizdal, Frank Brockners, Adrian 1377 Farrel, Stephen Farrell, and Jari Arkko for their reviews and 1378 comments on this document. 1380 13. Informative References 1382 [GSMA.IR.34] 1383 GSMA, "Inter-PLMN Backbone Guidelines", GSMA 1384 PRD IR.34.4.9, March 2010. 1386 [I-D.ietf-dhc-pd-exclude] 1387 Korhonen, J., Savolainen, T., Krishnan, S., and O. Troan, 1388 "Prefix Exclude Option for DHCPv6-based Prefix 1389 Delegation", draft-ietf-dhc-pd-exclude-03 (work in 1390 progress), August 2011. 1392 [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and 1393 E. Lear, "Address Allocation for Private Internets", 1394 BCP 5, RFC 1918, February 1996. 1396 [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", 1397 RFC 2131, March 1997. 1399 [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., 1400 and M. Carney, "Dynamic Host Configuration Protocol for 1401 IPv6 (DHCPv6)", RFC 3315, July 2003. 1403 [RFC3316] Arkko, J., Kuijpers, G., Soliman, H., Loughney, J., and J. 1404 Wiljakka, "Internet Protocol Version 6 (IPv6) for Some 1405 Second and Third Generation Cellular Hosts", RFC 3316, 1406 April 2003. 1408 [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic 1409 Host Configuration Protocol (DHCP) version 6", RFC 3633, 1410 December 2003. 1412 [RFC3736] Droms, R., "Stateless Dynamic Host Configuration Protocol 1413 (DHCP) Service for IPv6", RFC 3736, April 2004. 1415 [RFC4389] Thaler, D., Talwar, M., and C. Patel, "Neighbor Discovery 1416 Proxies (ND Proxy)", RFC 4389, April 2006. 1418 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 1419 "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, 1420 September 2007. 1422 [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless 1423 Address Autoconfiguration", RFC 4862, September 2007. 1425 [RFC4941] Narten, T., Draves, R., and S. Krishnan, "Privacy 1426 Extensions for Stateless Address Autoconfiguration in 1427 IPv6", RFC 4941, September 2007. 1429 [RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K., 1430 and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008. 1432 [RFC6144] Baker, F., Li, X., Bao, C., and K. Yin, "Framework for 1433 IPv4/IPv6 Translation", RFC 6144, April 2011. 1435 [TR.23975] 1436 3GPP, "IPv6 Migration Guidelines", 3GPP TR 23.975 1.1.1, 1437 June 2010. 1439 [TS.23003] 1440 3GPP, "Numbering, addressing and identification", 3GPP 1441 TS 23.003 10.2.0, June 2011. 1443 [TS.23060] 1444 3GPP, "General Packet Radio Service (GPRS); Service 1445 description; Stage 2", 3GPP TS 23.060 8.8.0, March 2010. 1447 [TS.23203] 1448 3GPP, "Policy and charging control architecture (PCC)", 1449 3GPP TS 23.203 8.11.0, September 2010. 1451 [TS.23401] 1452 3GPP, "General Packet Radio Service (GPRS) enhancements 1453 for Evolved Universal Terrestrial Radio Access Network 1454 (E-UTRAN) access", 3GPP TS 23.401 10.4.0, June 2011. 1456 [TS.24008] 1457 3GPP, "Mobile radio interface Layer 3 specification", 3GPP 1458 TS 24.008 8.12.0, December 2010. 1460 [TS.24301] 1461 3GPP, "Non-Access-Stratum (NAS) protocol for Evolved 1462 Packet System (EPS)", 3GPP TS 24.301 8.8.0, December 2010. 1464 [TS.29002] 1465 3GPP, "Mobile Application Part (MAP) specification", 3GPP 1466 TS 29.002 9.5.0, June 2011. 1468 [TS.29060] 1469 3GPP, "General Packet Radio Service (GPRS); GPRS 1470 Tunnelling Protocol (GTP) across the Gn and Gp interface", 1471 3GPP TS 29.274 8.8.0, April 2010. 1473 [TS.29061] 1474 3GPP, "Interworking between the Public Land Mobile Network 1475 (PLMN) supporting packet based services and Packet Data 1476 Networks (PDN)", 3GPP TS 29.061 8.5.0, April 2010. 1478 [TS.29274] 1479 3GPP, "3GPP Evolved Packet System (EPS); Evolved General 1480 Packet Radio Service (GPRS) Tunnelling Protocol for 1481 Control plane (GTPv2-C)", 3GPP TS 29.060 8.11.0, 1482 December 2010. 1484 [TS.33102] 1485 3GPP, "3G Security; Security architecture", 3GPP 1486 TS 33.102 10.0.0, December 2010. 1488 [TS.33401] 1489 3GPP, "3GPP System Architecture Evolution (SAE); Security 1490 architecture", 3GPP TS 33.401 10.1.1, June 2011. 1492 Authors' Addresses 1494 Jouni Korhonen (editor) 1495 Nokia Siemens Networks 1496 Linnoitustie 6 1497 FI-02600 Espoo 1498 FINLAND 1500 Email: jouni.nospam@gmail.com 1502 Jonne Soininen 1503 Renesas Mobile 1504 Porkkalankatu 24 1505 FI-00180 Helsinki 1506 FINLAND 1508 Email: jonne.soininen@renesasmobile.com 1510 Basavaraj Patil 1511 Nokia 1512 6021 Connection drive 1513 Irving, TX 75039 1514 USA 1516 Email: basavaraj.patil@nokia.com 1518 Teemu Savolainen 1519 Nokia 1520 Hermiankatu 12 D 1521 FI-33720 Tampere 1522 FINLAND 1524 Email: teemu.savolainen@nokia.com 1526 Gabor Bajko 1527 Nokia 1528 323 Fairchild drive 6 1529 Mountain view, CA 94043 1530 USA 1532 Email: gabor.bajko@nokia.com 1533 Kaisu Iisakkila 1534 Renesas Mobile 1535 Porkkalankatu 24 1536 FI-00180 Helsinki 1537 FINLAND 1539 Email: kaisu.iisakkila@renesasmobile.com