idnits 2.17.1 draft-ietf-v6ops-mobile-device-profile-04.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 : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([I-D.ietf-v6ops-RFC3316bis]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 10, 2013) is 3967 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 3633 (Obsoleted by RFC 8415) ** Obsolete normative reference: RFC 3736 (Obsoleted by RFC 8415) ** Obsolete normative reference: RFC 4941 (Obsoleted by RFC 8981) ** Obsolete normative reference: RFC 6106 (Obsoleted by RFC 8106) ** Obsolete normative reference: RFC 6145 (Obsoleted by RFC 7915) ** Obsolete normative reference: RFC 6434 (Obsoleted by RFC 8504) ** Obsolete normative reference: RFC 6555 (Obsoleted by RFC 8305) == Outdated reference: A later version (-06) exists of draft-ietf-pcp-nat64-prefix64-03 == Outdated reference: A later version (-10) exists of draft-ietf-v6ops-64share-07 == Outdated reference: A later version (-06) exists of draft-ietf-v6ops-rfc3316bis-03 -- Obsolete informational reference (is this intentional?): RFC 6204 (Obsoleted by RFC 7084) Summary: 8 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 V6OPS Working Group D. Binet 3 Internet-Draft M. Boucadair 4 Intended status: Informational France Telecom 5 Expires: December 12, 2013 A. Vizdal 6 Deutsche Telekom AG 7 C. Byrne 8 T-Mobile 9 G. Chen 10 China Mobile 11 June 10, 2013 13 Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices 14 draft-ietf-v6ops-mobile-device-profile-04 16 Abstract 18 This document specifies an IPv6 profile for 3GPP mobile devices. It 19 lists the set of features a 3GPP mobile device is to be compliant 20 with to connect to an IPv6-only or dual-stack wireless network 21 (including 3GPP cellular network and IEEE 802.11 network). 23 This document defines a different profile than the one for general 24 connection to IPv6 cellular networks defined in 25 [I-D.ietf-v6ops-rfc3316bis]. In particular, this document identifies 26 also features to deliver IPv4 connectivity service over an IPv6-only 27 transport. 29 Both hosts and devices with capability to share their WAN (Wide Area 30 Network) connectivity are in scope. 32 Status of This Memo 34 This Internet-Draft is submitted in full conformance with the 35 provisions of BCP 78 and BCP 79. 37 Internet-Drafts are working documents of the Internet Engineering 38 Task Force (IETF). Note that other groups may also distribute 39 working documents as Internet-Drafts. The list of current Internet- 40 Drafts is at http://datatracker.ietf.org/drafts/current/. 42 Internet-Drafts are draft documents valid for a maximum of six months 43 and may be updated, replaced, or obsoleted by other documents at any 44 time. It is inappropriate to use Internet-Drafts as reference 45 material or to cite them other than as "work in progress." 47 This Internet-Draft will expire on December 12, 2013. 49 Copyright Notice 51 Copyright (c) 2013 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (http://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 67 1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 4 68 1.2. Special Language . . . . . . . . . . . . . . . . . . . . 4 69 2. Connectivity Requirements . . . . . . . . . . . . . . . . . . 5 70 2.1. WLAN Connectivity Requirements . . . . . . . . . . . . . 8 71 3. Advanced Requirements . . . . . . . . . . . . . . . . . . . . 9 72 4. Cellular Devices with LAN Capabilities . . . . . . . . . . . 10 73 5. APIs & Applications . . . . . . . . . . . . . . . . . . . . . 12 74 6. Security Considerations . . . . . . . . . . . . . . . . . . . 12 75 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 76 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 77 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 78 9.1. Normative References . . . . . . . . . . . . . . . . . . 12 79 9.2. Informative References . . . . . . . . . . . . . . . . . 14 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 82 1. Introduction 84 IPv6 deployment in 3GPP mobile networks is the only perennial 85 solution to the exhaustion of IPv4 addresses in those networks. 86 Several mobile operators have already deployed IPv6 or are in the 87 pre-deployment phase. One of the major hurdles encountered by mobile 88 operators is the availability of non-broken IPv6 implementation in 89 mobile devices. 91 [I-D.ietf-v6ops-rfc3316bis] lists a set of features to be supported 92 by cellular hosts to connect to 3GPP mobile networks. In the light 93 of recent IPv6 production deployments, additional features to 94 facilitate IPv6-only deployments while accessing IPv4-only service 95 are to be considered. 97 This document defines a different profile than the one for general 98 connection to IPv6 mobile networks defined in 99 [I-D.ietf-v6ops-rfc3316bis]; in particular: 101 o It lists an extended list of required features while 102 [I-D.ietf-v6ops-rfc3316bis] identifies issues and explains how to 103 implement basic IPv6 features in a cellular context. 105 o It identifies also features to ensure IPv4 service delivery over 106 an IPv6-only transport. 108 This document specifies an IPv6 profile for mobile devices listing 109 required specifications produced by various Standards Developing 110 Organizations (in particular 3GPP and IETF). The objectives of this 111 effort are: 113 1. List in one single document a comprehensive list of IPv6 features 114 for a mobile device, including both IPv6-only and dual-stack 115 mobile deployment contexts. These features cover various network 116 types such as GPRS (General Packet Radio Service), EPC (Evolved 117 Packet Core) or IEEE 802.11 network. 119 2. Help Operators with the detailed device requirement list 120 preparation (to be exchanged with device suppliers). This is 121 also a contribution to harmonize Operators' requirements towards 122 device vendors. 124 3. Vendors to be aware of a set of features to allow for IPv6 125 connectivity and IPv4 service continuity (over an IPv6-only 126 transport). 128 Pointers to some requirements listed in [RFC6434] are included in 129 this profile. The justification for using a stronger language 130 compared to what is specified in [RFC6434] is provided for some 131 requirements. 133 The requirements do not include 3GPP release details. For more 134 information on the 3GPP releases detail, the reader may refer to 135 Section 6.2 of [RFC6459]. 137 Some of the features listed in this profile document require to 138 activate dedicated functions at the network side. It is out of scope 139 of this document to list these network-side functions. 141 A detailed overview of IPv6 support in 3GPP architectures is provided 142 in [RFC6459]. 144 This document makes use of the terms defined in [RFC6459]. In 145 addition, the following terms are used: 147 o "3GPP cellular host" (or cellular host for short) denotes a 3GPP 148 device which can be connected to 3GPP mobile networks or IEEE 149 802.11 networks. 151 o "3GPP cellular device" (or cellular device for short) refers to a 152 cellular host which supports the capability to share its WAN (Wide 153 Area Network) connectivity. 155 o "Cellular host" and "mobile host" are used interchangeably. 157 o "Cellular device" and "mobile device" are used interchangeably. 159 PREFIX64 denotes an IPv6 prefix used to build IPv4-converted IPv6 160 addresses [RFC6052]. 162 1.1. Scope 164 A 3GPP mobile network can be used to connect various user equipments 165 such as a mobile telephone, a CPE (Customer Premises Equipment) or a 166 M2M (machine-to-machine) device. Because of this diversity of 167 terminals, it is necessary to define a set of IPv6 functionalities 168 valid for any node directly connecting to a 3GPP mobile network. 169 This document describes these functionalities. 171 This document is structured to provide the generic IPv6 requirements 172 which are valid for all nodes, whatever their function or service 173 (e.g., SIP [RFC3261]) capability. The document also contains, 174 dedicated sections covering specific functionalities the specific 175 device types must support (e.g., smartphones, devices providing some 176 LAN functions (mobile CPE or broadband dongles)). 178 The requirements listed below are valid for both 3GPP GPRS and 3GPP 179 EPS (Evolved Packet System) access. For EPS, PDN-Connection term is 180 used instead of PDP-Context. 182 This document identifies also some WLAN-related IPv6 requirements. 183 Other non-3GPP accesses [TS.23402] are out of scope of this document. 185 1.2. Special Language 187 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 188 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 189 document are to be interpreted as described in RFC 2119 [RFC2119]. 191 This document is not a standard. It uses the normative keywords only 192 for precision. 194 2. Connectivity Requirements 196 REQ#1: The cellular host MUST be compliant with Section 5.9.1 (IPv6 197 Addressing Architecture) and Section 5.8 (ICMPv6 support) of 198 [RFC6434]. 200 REQ#2: The cellular host MUST support both IPv6 and IPv4v6 PDP- 201 Contexts. 203 This allows each operator to select their own strategy 204 regarding IPv6 introduction. Both IPv6 and IPv4v6 PDP- 205 Contexts MUST be supported. IPv4, IPv6 or IPv4v6 PDP-Context 206 request acceptance depends on the cellular network 207 configuration. 209 REQ#3: The cellular host MUST comply with the behavior defined in 210 [TS.23060] [TS.23401] [TS.24008] for requesting a PDP-Context 211 type. In particular, the cellular host MUST request by default 212 an IPv6 PDP-Context if the cellular host is IPv6-only and 213 requesting an IPv4v6 PDP-Context if the cellular host is dual- 214 stack or when the cellular host is not aware of connectivity 215 types requested by devices connected to it (e.g., cellular host 216 with LAN capabilities as discussed in Section 4): 218 * If the requested IPv4v6 PDP-Context is not supported by the 219 network, but IPv4 and IPv6 PDP types are allowed, then the 220 cellular host will be configured with an IPv4 address or an 221 IPv6 prefix by the network. It MUST initiate another PDP- 222 Context activation in addition to the one already activated 223 for a given APN (Access Point Name). 225 * If the requested PDP type and subscription data allows only 226 one IP address family (IPv4 or IPv6), the cellular host MUST 227 NOT request a second PDP-Context to the same APN for the 228 other IP address family. 230 The text above focuses on the specification part which explains 231 the behavior for requesting IPv6-related PDP-Context(s). 232 Understanding this behavior is important to avoid having broken 233 IPv6 implementations in cellular devices. 235 REQ#4: The cellular host MUST support the PCO (Protocol 236 Configuration Options) [TS.24008] to retrieve the IPv6 237 address(es) of the Recursive DNS server(s). 239 In-band signaling is a convenient method to inform the 240 cellular host about various services, including DNS server 241 information. It does not require any specific protocol to be 242 supported and it is already deployed in IPv4 cellular 243 networks to convey such DNS information. 245 REQ#5: The cellular host MUST support IPv6 aware Traffic Flow 246 Templates (TFT) [TS.24008]. 248 Traffic Flow Templates are employing a packet filter to 249 couple an IP traffic with a PDP-Context. Thus a dedicated 250 PDP-Context and radio resources can be provided by the 251 cellular network for certain IP traffic. 253 REQ#6: The device MUST support the Neighbor Discovery Protocol 254 ([RFC4861] and [RFC5942]). 256 This is a stronger form compared to what is specified in 257 Section 5.2 and Section 12.2 of [RFC6434]. 259 The support of Neighbor Discovery Protocol is mandatory in 260 3GPP cellular environment as it is the only way to convey 261 IPv6 prefix towards the 3GPP cellular device. 263 In particular, MTU (Maximum Transmission Unit) communication 264 via Router Advertisement MUST be supported since many 3GPP 265 networks do not have a standard MTU setting. 267 REQ#7: The cellular host MUST comply with Section 5.6.1 of 268 [RFC6434]. If the MTU used by cellular hosts is larger than 269 1280 bytes, they can rely on Path MTU discovery function to 270 discover the real path MTU. 272 REQ#8: The cellular host MUST support IPv6 Stateless Address 273 Autoconfiguration ([RFC4862]) apart from the exceptions noted in 274 [TS.23060] (3G) and [TS.23401] (LTE): 276 Stateless mode is the only way to configure a cellular host. 277 The GGSN/PGW must allocate a prefix that is unique within its 278 scope to each primary PDP-Context. 280 To configure its link local address, the cellular host MUST 281 use the Interface Identifier conveyed in 3GPP PDP-Context 282 setup signaling received from a GGSN/PGW. The cellular host 283 may use a different Interface Identifiers to configure its 284 global addresses (see also REQ#23 about privacy addressing 285 requirement). 287 For more details, refer to [RFC6459] and 288 [I-D.ietf-v6ops-rfc3316bis]. 290 REQ#9: The cellular host MUST comply with Section 7.3 of [RFC6434]. 292 REQ#10: The cellular host MUST comply with Section 7.2.1 of 293 [RFC6434]. 295 Stateless DHCPv6 is useful to retrieve other information than 296 DNS. 298 If [RFC6106] is not supported, the cellular host SHOULD 299 retrieve DNS information using stateless DHCPv6 [RFC3736]. 301 REQ#11: If the cellular host receives the DNS information in several 302 channels for the same interface, the following preference order 303 MUST be followed: 305 1. PCO 307 2. RA 309 3. DHCPv6 311 REQ#12: The cellular host SHOULD support a method to locally 312 construct IPv4-embedded IPv6 addresses [RFC6052]. A method to 313 learn PREFIX64 SHOULD be supported by the cellular host. 315 This solves the issue when applications use IPv4 referrals on 316 IPv6-only access networks. 318 In PCP-based environments, cellular hosts SHOULD follow 319 [I-D.ietf-pcp-nat64-prefix64] to learn the IPv6 Prefix used 320 by an upstream PCP-controlled NAT64 device. If PCP is not 321 enabled, the cellular host SHOULD implement the method 322 specified in [I-D.ietf-behave-nat64-discovery-heuristic] to 323 retrieve the PREFIX64. 325 REQ#13: The cellular host SHOULD implement the Customer Side 326 Translator (CLAT, [RFC6877]) function which is compliant with 327 [RFC6052][RFC6145][RFC6146]. 329 CLAT function in the cellular host allows for IPv4-only 330 application and IPv4-referals to work on an IPv6-only 331 connectivity. CLAT function requires a NAT64 capability 332 [RFC6146] in the core network. 334 REQ#14: The cellular device SHOULD embed a DNS64 function [RFC6147]. 336 Local DNS64 functionality allows for compatibility with DNS 337 Security Extensions (DNSSEC, [RFC4033], [RFC4034], 338 [RFC4035]). Means to configure or discover a PREFIX64 is 339 also required on the cellular device as discussed in REQ#12. 341 REQ#15: The cellular host SHOULD support PCP [RFC6887]. 343 The support of PCP is seen as a driver to save battery 344 consumption exacerbated by keepalive messages. PCP also 345 gives the possibility of enabling incoming connections to the 346 cellular device. Indeed, because several stateful devices 347 may be deployed in wireless networks (e.g., NAT and/or 348 Firewalls), PCP can be used by the cellular host to control 349 network-based NAT and Firewall functions which will reduce 350 per-application signaling and save battery consumption. 352 REQ#16: When the cellular host is dual-stack connected (i.e., 353 configured with an IPv4 address and IPv6 prefix), it SHOULD 354 support means to prefer native IPv6 connection over connection 355 established through translation devices (e.g., NAT44 and NAT64). 357 When both IPv4 and IPv6 DNS servers are configured, a dual- 358 stack host MUST contact first its IPv6 DNS server. 360 Cellular hosts SHOULD follow the procedure specified in 361 [RFC6724] for source address selection. 363 REQ#17: The cellular host SHOULD support Happy Eyeballs procedure 364 defined in [RFC6555]. 366 REQ#18: The cellular device MAY embed a BIH function [RFC6535] 367 facilitating the communication between an IPv4 application and 368 an IPv6 server. 370 2.1. WLAN Connectivity Requirements 372 It is increasingly common for cellular hosts have a WLAN interface in 373 addition to their cellular interface. These hosts are likely to be 374 connected to private or public hotspots. Below are listed some 375 generic requirements: 377 REQ#19: IPv6 MUST be supported on the WLAN interface. In 378 particular, IPv6-only connectivity MUST be supported over the 379 WLAN interface. 381 Some tests revealed that IPv4 configuration is required to 382 enable IPv6-only connectivity. Indeed, some cellular 383 handsets can access a WLAN IPv6-only network by configuring 384 first a static IPv4 address. Once the device is connected 385 to the network and the wlan0 interface got an IPv6 global 386 address, the IPv4 address can be deleted from the 387 configuration. This avoids the device to ask automatically 388 for a DHCPv4 server, and allows to connect to IPv6-only 389 networks. Failing to configure an IPv4 address on the 390 interface MUST NOT prohibit using IPv6 on the same 391 interface. 393 IPv6 Stateless Address Autoconfiguration ([RFC4862]) MUST 394 be supported. 396 REQ#20: DHCPv6 client SHOULD be supported on WLAN interface. 398 Refer to Section 7.2.1 of [RFC6434]. 400 REQ#21: WLAN interface SHOULD support Router Advertisement Options 401 for DNS configuration (See Section 7.3 of [RFC6434]). 403 REQ#22: If the device receives the DNS information in several 404 channels for the same interface, the following preference 405 order MUST be followed: 407 1. RA 409 2. DHCPv6 411 3. Advanced Requirements 413 REQ#23: The cellular host MUST be able to generate IPv6 addresses 414 which preserve privacy. 416 The activation of privacy extension (e.g., using [RFC4941]) 417 makes it more difficult to track a host over time when 418 compared to using a permanent Interface Identifier. Note, 419 [RFC4941] does not require any DAD mechanism to be 420 activated as the GGSN/PGW MUST NOT configure any global 421 address based on the prefix allocated to the cellular host. 423 Tracking a host is still possible based on the first 64 424 bits of the IPv6 address. Means to prevent against such 425 tracking issues may be enabled in the network side. 427 REQ#24: The cellular host MUST support ROHC RTP Profile (0x0001) and 428 ROHC UDP Profile (0x0002) for IPv6 ([RFC5795]). Other ROHC 429 profiles MAY be supported. 431 Bandwidth in cellular networks must be optimized as much as 432 possible. ROHC provides a solution to reduce bandwidth 433 consumption and to reduce the impact of having bigger 434 packet headers in IPv6 compared to IPv4. 436 "RTP/UDP/IP" ROHC profile (0x0001) to compress RTP packets 437 and "UDP/IP" ROHC profile (0x0002) to compress RTCP packets 438 are required for Voice over LTE (VoLTE) by IR.92.4.0 439 section 4.1 [IR92]. Note, [IR92] indicates also the host 440 must be able to apply the compression to packets that are 441 carried over the radio bearer dedicated for the voice 442 media. 444 REQ#25: The cellular host MUST comply with Section 5.3 of [RFC6434] 445 and SHOULD support Router Advertisement extension for 446 communicating default router preferences and more-specific 447 routes as described in [RFC4191]. 449 This function can be used for instance for traffic offload. 451 4. Cellular Devices with LAN Capabilities 453 This section focuses on cellular devices (e.g., CPE, smartphones or 454 dongles with tethering features) which provide IP connectivity to 455 other devices connected to them. In such case, all connected devices 456 are sharing the same 2G, 3G or LTE connection. In addition to the 457 generic requirements listed in Section 2, these cellular devices have 458 to meet the requirements listed below. 460 REQ#26: The cellular device MUST support Prefix Delegation 461 capabilities [RFC3633] and MUST support Prefix Exclude Option 462 for DHCPv6-based Prefix Delegation as defined in [RFC6603]. 463 Particularly, it MUST behave as a Requesting Router. 465 Cellular networks are more and more perceived as an 466 alternative to fixed networks for home IP-based services 467 delivery; especially with the advent of smartphones and 468 3GPP data dongles. There is a need for an efficient 469 mechanism to assign shorter prefix than /64 to cellular 470 hosts so that each LAN segment can get its own /64 prefix 471 and multi-link subnet issues to be avoided. 473 In case a prefix is delegated to a cellular host using 474 DHCPv6, the cellular device will be configured with two 475 prefixes: 477 (1) one for 3GPP link allocated using SLAAC mechanism 478 and 479 (2) another one delegated for LANs acquired during 480 Prefix Delegation operation. 482 Note that the 3GPP network architecture requires both the 483 WAN (Wide Area Network) and the delegated prefix to be 484 aggregatable, so the subscriber can be identified using a 485 single prefix. 487 Without the Prefix Exclude Option, the delegating router 488 (GGSN/PGW) will have to ensure [RFC3633] compliancy (e.g., 489 halving the delegated prefix and assigning the WAN prefix 490 out of the 1st half and the prefix to be delegated to the 491 terminal from the 2nd half). 493 REQ#27: The cellular device MUST be compliant with the CPE 494 requirements specified in [RFC6204]. 496 REQ#28: For deployments requiring to share the same /64 prefix, the 497 cellular device SHOULD support [I-D.ietf-v6ops-64share] to 498 enable sharing a /64 prefix between the 3GPP interface towards 499 the GGSN/PGW (WAN interface) and the LAN interfaces. 501 REQ#29: The cellular device SHOULD support the Customer Side 502 Translator (CLAT) [RFC6877]. 504 Various IP devices are likely to be connected to cellular 505 device, acting as a CPE. Some of these devices can be 506 dual-stack, others are IPv6-only or IPv4-only. IPv6-only 507 connectivity for cellular device does not allow IPv4-only 508 sessions to be established for hosts connected on the LAN 509 segment of cellular devices. 511 In order to allow IPv4 sessions establishment initiated 512 from devices located on LAN segment side and target IPv4 513 nodes, a solution consists in integrating the CLAT function 514 in the cellular device. As elaborated in Section 2, the 515 CLAT function allows also IPv4 applications to continue 516 running over an IPv6-only host. 518 REQ#30: If a RA MTU is advertised from the 3GPP network, the 519 cellular device SHOULD relay that upstream MTU information to 520 the downstream attached LAN devices in RA. 522 Receiving and relaying RA MTU values facilitates a more 523 harmonious functioning of the mobile core network where end 524 nodes transmit packets that do not exceed the MTU size of 525 the mobile network's GTP tunnels. 527 [TS.23060] indicates providing a link MTU value of 1358 528 octets to the 3GPP cellular device will prevent the IP 529 layer fragmentation within the transport network between 530 the cellular device and the GGSN/PGW. 532 5. APIs & Applications 534 REQ#31: Name resolution libraries MUST support both IPv4 and IPv6. 536 In particular, the cellular host MUST support [RFC3596]. 538 REQ#32: Applications MUST be independent of the underlying IP 539 address family. 541 This means applications must be IP version agnostic. 543 REQ#33: Applications using URIs MUST follow [RFC3986]. For example, 544 SIP applications MUST follow the correction defined in 545 [RFC5954]. 547 6. Security Considerations 549 The security considerations identified in [I-D.ietf-v6ops-rfc3316bis] 550 and [RFC6459] are to be taken into account. 552 REQ#34: If the cellular device provides LAN features, it SHOULD be 553 compliant with the security requirements specified in 554 [RFC6092]. 556 7. IANA Considerations 558 This document does not require any action from IANA. 560 8. Acknowledgements 562 Many thanks to H. Soliman, H. Singh, L. Colliti, T. Lemon, B. 563 Sarikaya, M. Mawatari, M. Abrahamsson, P. Vickers, V. Kuarsingh, and 564 J. Woodyatt for the discussion in the v6ops mailing list. 566 Special thanks to T. Savolainen and J. Korhonen for the detailed 567 review. 569 9. References 571 9.1. Normative References 573 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 574 Requirement Levels", BCP 14, RFC 2119, March 1997. 576 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 577 A., Peterson, J., Sparks, R., Handley, M., and E. 578 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 579 June 2002. 581 [RFC3596] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi, 582 "DNS Extensions to Support IP Version 6", RFC 3596, 583 October 2003. 585 [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic 586 Host Configuration Protocol (DHCP) version 6", RFC 3633, 587 December 2003. 589 [RFC3736] Droms, R., "Stateless Dynamic Host Configuration Protocol 590 (DHCP) Service for IPv6", RFC 3736, April 2004. 592 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 593 Resource Identifier (URI): Generic Syntax", STD 66, RFC 594 3986, January 2005. 596 [RFC4191] Draves, R. and D. Thaler, "Default Router Preferences and 597 More-Specific Routes", RFC 4191, November 2005. 599 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 600 "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, 601 September 2007. 603 [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless 604 Address Autoconfiguration", RFC 4862, September 2007. 606 [RFC4941] Narten, T., Draves, R., and S. Krishnan, "Privacy 607 Extensions for Stateless Address Autoconfiguration in 608 IPv6", RFC 4941, September 2007. 610 [RFC5795] Sandlund, K., Pelletier, G., and L-E. Jonsson, "The RObust 611 Header Compression (ROHC) Framework", RFC 5795, March 612 2010. 614 [RFC5942] Singh, H., Beebee, W., and E. Nordmark, "IPv6 Subnet 615 Model: The Relationship between Links and Subnet 616 Prefixes", RFC 5942, July 2010. 618 [RFC5954] Gurbani, V., Carpenter, B., and B. Tate, "Essential 619 Correction for IPv6 ABNF and URI Comparison in RFC 3261", 620 RFC 5954, August 2010. 622 [RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X. 623 Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052, 624 October 2010. 626 [RFC6106] Jeong, J., Park, S., Beloeil, L., and S. Madanapalli, 627 "IPv6 Router Advertisement Options for DNS Configuration", 628 RFC 6106, November 2010. 630 [RFC6145] Li, X., Bao, C., and F. Baker, "IP/ICMP Translation 631 Algorithm", RFC 6145, April 2011. 633 [RFC6146] Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful 634 NAT64: Network Address and Protocol Translation from IPv6 635 Clients to IPv4 Servers", RFC 6146, April 2011. 637 [RFC6147] Bagnulo, M., Sullivan, A., Matthews, P., and I. van 638 Beijnum, "DNS64: DNS Extensions for Network Address 639 Translation from IPv6 Clients to IPv4 Servers", RFC 6147, 640 April 2011. 642 [RFC6434] Jankiewicz, E., Loughney, J., and T. Narten, "IPv6 Node 643 Requirements", RFC 6434, December 2011. 645 [RFC6535] Huang, B., Deng, H., and T. Savolainen, "Dual-Stack Hosts 646 Using "Bump-in-the-Host" (BIH)", RFC 6535, February 2012. 648 [RFC6555] Wing, D. and A. Yourtchenko, "Happy Eyeballs: Success with 649 Dual-Stack Hosts", RFC 6555, April 2012. 651 [RFC6603] Korhonen, J., Savolainen, T., Krishnan, S., and O. Troan, 652 "Prefix Exclude Option for DHCPv6-based Prefix 653 Delegation", RFC 6603, May 2012. 655 [RFC6724] Thaler, D., Draves, R., Matsumoto, A., and T. Chown, 656 "Default Address Selection for Internet Protocol Version 6 657 (IPv6)", RFC 6724, September 2012. 659 9.2. Informative References 661 [I-D.ietf-behave-nat64-discovery-heuristic] 662 Savolainen, T., Korhonen, J., and D. Wing, "Discovery of 663 the IPv6 Prefix Used for IPv6 Address Synthesis", draft- 664 ietf-behave-nat64-discovery-heuristic-17 (work in 665 progress), April 2013. 667 [I-D.ietf-pcp-nat64-prefix64] 668 Boucadair, M., "Learning NAT64 PREFIX64s using PCP", 669 draft-ietf-pcp-nat64-prefix64-03 (work in progress), June 670 2013. 672 [I-D.ietf-v6ops-64share] 673 Byrne, C., Drown, D., and V. Ales, "Extending an IPv6 /64 674 Prefix from a 3GPP Mobile Interface to a LAN", draft-ietf- 675 v6ops-64share-07 (work in progress), May 2013. 677 [I-D.ietf-v6ops-rfc3316bis] 678 Korhonen, J., Arkko, J., Savolainen, T., and S. Krishnan, 679 "IPv6 for 3GPP Cellular Hosts", draft-ietf-v6ops- 680 rfc3316bis-03 (work in progress), May 2013. 682 [IR92] GSMA, "IR.92.V4.0 - IMS Profile for Voice and SMS", March 683 2011, . 686 [RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S. 687 Rose, "DNS Security Introduction and Requirements", RFC 688 4033, March 2005. 690 [RFC4034] Arends, R., Austein, R., Larson, M., Massey, D., and S. 691 Rose, "Resource Records for the DNS Security Extensions", 692 RFC 4034, March 2005. 694 [RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S. 695 Rose, "Protocol Modifications for the DNS Security 696 Extensions", RFC 4035, March 2005. 698 [RFC6092] Woodyatt, J., "Recommended Simple Security Capabilities in 699 Customer Premises Equipment (CPE) for Providing 700 Residential IPv6 Internet Service", RFC 6092, January 701 2011. 703 [RFC6204] Singh, H., Beebee, W., Donley, C., Stark, B., and O. 704 Troan, "Basic Requirements for IPv6 Customer Edge 705 Routers", RFC 6204, April 2011. 707 [RFC6459] Korhonen, J., Soininen, J., Patil, B., Savolainen, T., 708 Bajko, G., and K. Iisakkila, "IPv6 in 3rd Generation 709 Partnership Project (3GPP) Evolved Packet System (EPS)", 710 RFC 6459, January 2012. 712 [RFC6877] Mawatari, M., Kawashima, M., and C. Byrne, "464XLAT: 713 Combination of Stateful and Stateless Translation", RFC 714 6877, April 2013. 716 [RFC6887] Wing, D., Cheshire, S., Boucadair, M., Penno, R., and P. 717 Selkirk, "Port Control Protocol (PCP)", RFC 6887, April 718 2013. 720 [TS.23060] 721 3GPP, "General Packet Radio Service (GPRS); Service 722 description; Stage 2", September 2011. 724 [TS.23401] 725 3GPP, "General Packet Radio Service (GPRS) enhancements 726 for Evolved Universal Terrestrial Radio Access Network 727 (E-UTRAN) access", September 2011. 729 [TS.23402] 730 3GPP, "Architecture enhancements for non-3GPP accesses", 731 September 2011. 733 [TS.24008] 734 3GPP, "Mobile radio interface Layer 3 specification; Core 735 network protocols; Stage 3", June 2011. 737 [TS.29060] 738 3GPP, "General Packet Radio Service (GPRS); GPRS 739 Tunnelling Protocol (GTP) across the Gn and Gp interface", 740 September 2011. 742 [TS.29274] 743 3GPP, "3GPP Evolved Packet System (EPS); Evolved General 744 Packet Radio Service (GPRS) Tunnelling Protocol for 745 Control plane (GTPv2-C); Stage 3", June 2011. 747 [TS.29281] 748 3GPP, "General Packet Radio System (GPRS) Tunnelling 749 Protocol User Plane (GTPv1-U)", September 2011. 751 Authors' Addresses 753 David Binet 754 France Telecom 755 Rennes 756 France 758 Email: david.binet@orange.com 759 Mohamed Boucadair 760 France Telecom 761 Rennes 35000 762 France 764 Email: mohamed.boucadair@orange.com 766 Ales Vizdal 767 Deutsche Telekom AG 769 Email: ales.vizdal@t-mobile.cz 771 Cameron Byrne 772 T-Mobile 773 USA 775 Email: Cameron.Byrne@T-Mobile.com 777 Gang Chen 778 China Mobile 780 Email: phdgang@gmail.com