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