idnits 2.17.1 draft-ietf-v6ops-mobile-device-profile-03.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 (April 29, 2013) is 4008 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-00 == Outdated reference: A later version (-10) exists of draft-ietf-v6ops-64share-04 == Outdated reference: A later version (-06) exists of draft-ietf-v6ops-rfc3316bis-01 -- 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: October 31, 2013 A. Vizdal 6 Deutsche Telekom AG 7 C. Byrne 8 T-Mobile 9 G. Chen 10 China Mobile 11 April 29, 2013 13 Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices 14 draft-ietf-v6ops-mobile-device-profile-03 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 October 31, 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 . . . . . . . . . . . . . . . . . . . . . . . . . 13 78 9.1. Normative References . . . . . . . . . . . . . . . . . . 13 79 9.2. Informative References . . . . . . . . . . . . . . . . . 15 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 all requirements a mobile device is 114 to comply with to connect to an IPv6 or dual-stack mobile 115 network. These requirements cover various network types such as 116 GPRS (General Packet Radio Service), EPC (Evolved Packet Core) or 117 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 minimal set of requirements to allow for 125 IPv6 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 [I-D.ietf-pcp-base]. 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 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 SHOULD support IPv6 Router Advertisement 445 Flags Options ([RFC5175]). 447 This is a stronger form compared to what is specified in 448 [RFC6434]. 450 REQ#26: The cellular host MUST comply with Section 5.3 of [RFC6434] 451 and SHOULD support Router Advertisement extension for 452 communicating default router preferences and more-specific 453 routes as described in [RFC4191]. 455 This function can be used for instance for traffic offload. 457 4. Cellular Devices with LAN Capabilities 459 This section focuses on cellular devices (e.g., CPE, smartphones or 460 dongles with tethering features) which provide IP connectivity to 461 other devices connected to them. In such case, all connected devices 462 are sharing the same 2G, 3G or LTE connection. In addition to the 463 generic requirements listed in Section 2, these cellular devices have 464 to meet the requirements listed below. 466 REQ#27: The cellular device MUST support Prefix Delegation 467 capabilities [RFC3633] and MUST support Prefix Exclude Option 468 for DHCPv6-based Prefix Delegation as defined in [RFC6603]. 469 Particularly, it MUST behave as a Requesting Router. 471 Cellular networks are more and more perceived as an 472 alternative to fixed networks for home IP-based services 473 delivery; especially with the advent of smartphones and 474 3GPP data dongles. There is a need for an efficient 475 mechanism to assign shorter prefix than /64 to cellular 476 hosts so that each LAN segment can get its own /64 prefix 477 and multilink subnet issues to be avoided. 479 In case a prefix is delegated to a cellular host using 480 DHCPv6, the cellular device will be configured with two 481 prefixes: 483 (1) one for 3GPP link allocated using SLAAC mechanism 484 and 486 (2) another one delegated for LANs acquired during 487 Prefix Delegation operation. 489 Note that the 3GPP network architecture requires both the 490 WAN (Wide Area Network) and the delegated prefix to be 491 aggregatable, so the subscriber can be identified using a 492 single prefix. 494 Without the Prefix Exclude Option, the delegating router 495 (GGSN/PGW) will have to ensure [RFC3633] compliancy (e.g., 496 halving the delegated prefix and assigning the WAN prefix 497 out of the 1st half and the prefix to be delegated to the 498 terminal from the 2nd half). 500 REQ#28: The cellular device MUST be compliant with the CPE 501 requirements specified in [RFC6204]. 503 REQ#29: For deployments requiring to share the same /64 prefix, the 504 cellular device SHOULD support [I-D.ietf-v6ops-64share] to 505 enable sharing a /64 prefix between the 3GPP interface towards 506 the GGSN/PGW (WAN interface) and the LAN interfaces. 508 REQ#30: The cellular device SHOULD support the Customer Side 509 Translator (CLAT) [RFC6877]. 511 Various IP devices are likely to be connected to cellular 512 device, acting as a CPE. Some of these devices can be 513 dual-stack, others are IPv6-only or IPv4-only. IPv6-only 514 connectivity for cellular device does not allow IPv4-only 515 sessions to be established for hosts connected on the LAN 516 segment of cellular devices. 518 In order to allow IPv4 sessions establishment initiated 519 from devices located on LAN segment side and target IPv4 520 nodes, a solution consists in integrating the CLAT function 521 in the cellular device. As elaborated in Section 2, the 522 CLAT function allows also IPv4 applications to continue 523 running over an IPv6-only host. 525 REQ#31: If a RA MTU is advertised from the 3GPP network, the 526 cellular device SHOULD relay that upstream MTU information to 527 the downstream attached LAN devices in RA. 529 Receiving and relaying RA MTU values facilitates a more 530 harmonious functioning of the mobile core network where end 531 nodes transmit packets that do not exceed the MTU size of 532 the mobile network's GTP tunnels. 534 [TS.23060] indicates providing a link MTU value of 1358 535 octets to the 3GPP cellular device will prevent the IP 536 layer fragmentation within the transport network between 537 the cellular device and the GGSN/PGW. 539 5. APIs & Applications 541 REQ#32: Name resolution libraries MUST support both IPv4 and IPv6. 543 In particular, the cellular host MUST support [RFC3596]. 545 REQ#33: Applications MUST be independent of the underlying IP 546 address family. 548 This means applications must be IP version agnostic. 550 REQ#34: Applications using URIs MUST follow [RFC3986]. For example, 551 SIP applications MUST follow the correction defined in 552 [RFC5954]. 554 6. Security Considerations 556 The security considerations identified in [I-D.ietf-v6ops-rfc3316bis] 557 and [RFC6459] are to be taken into account. 559 REQ#35: If the cellular device provides LAN features, it SHOULD be 560 compliant with the security requirements specified in 561 [RFC6092]. 563 7. IANA Considerations 565 This document does not require any action from IANA. 567 8. Acknowledgements 569 Many thanks to H. Soliman, H. Singh, L. Colliti, T. Lemon, B. 570 Sarikaya, M. Mawatari, M. Abrahamsson, P. Vickers, V. Kuarsingh, 571 and J. Woodyatt for the discussion in the v6ops mailing list. 573 Special thanks to T. Savolainen and J. Korhonen for the detailed 574 review. 576 9. References 578 9.1. Normative References 580 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 581 Requirement Levels", BCP 14, RFC 2119, March 1997. 583 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 584 A., Peterson, J., Sparks, R., Handley, M., and E. 585 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 586 June 2002. 588 [RFC3596] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi, 589 "DNS Extensions to Support IP Version 6", RFC 3596, 590 October 2003. 592 [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic 593 Host Configuration Protocol (DHCP) version 6", RFC 3633, 594 December 2003. 596 [RFC3736] Droms, R., "Stateless Dynamic Host Configuration Protocol 597 (DHCP) Service for IPv6", RFC 3736, April 2004. 599 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 600 Resource Identifier (URI): Generic Syntax", STD 66, RFC 601 3986, January 2005. 603 [RFC4191] Draves, R. and D. Thaler, "Default Router Preferences and 604 More-Specific Routes", RFC 4191, November 2005. 606 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 607 "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, 608 September 2007. 610 [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless 611 Address Autoconfiguration", RFC 4862, September 2007. 613 [RFC4941] Narten, T., Draves, R., and S. Krishnan, "Privacy 614 Extensions for Stateless Address Autoconfiguration in 615 IPv6", RFC 4941, September 2007. 617 [RFC5175] Haberman, B. and R. Hinden, "IPv6 Router Advertisement 618 Flags Option", RFC 5175, March 2008. 620 [RFC5795] Sandlund, K., Pelletier, G., and L-E. Jonsson, "The RObust 621 Header Compression (ROHC) Framework", RFC 5795, March 622 2010. 624 [RFC5942] Singh, H., Beebee, W., and E. Nordmark, "IPv6 Subnet 625 Model: The Relationship between Links and Subnet 626 Prefixes", RFC 5942, July 2010. 628 [RFC5954] Gurbani, V., Carpenter, B., and B. Tate, "Essential 629 Correction for IPv6 ABNF and URI Comparison in RFC 3261", 630 RFC 5954, August 2010. 632 [RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X. 633 Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052, 634 October 2010. 636 [RFC6106] Jeong, J., Park, S., Beloeil, L., and S. Madanapalli, 637 "IPv6 Router Advertisement Options for DNS Configuration", 638 RFC 6106, November 2010. 640 [RFC6145] Li, X., Bao, C., and F. Baker, "IP/ICMP Translation 641 Algorithm", RFC 6145, April 2011. 643 [RFC6146] Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful 644 NAT64: Network Address and Protocol Translation from IPv6 645 Clients to IPv4 Servers", RFC 6146, April 2011. 647 [RFC6147] Bagnulo, M., Sullivan, A., Matthews, P., and I. van 648 Beijnum, "DNS64: DNS Extensions for Network Address 649 Translation from IPv6 Clients to IPv4 Servers", RFC 6147, 650 April 2011. 652 [RFC6434] Jankiewicz, E., Loughney, J., and T. Narten, "IPv6 Node 653 Requirements", RFC 6434, December 2011. 655 [RFC6535] Huang, B., Deng, H., and T. Savolainen, "Dual-Stack Hosts 656 Using "Bump-in-the-Host" (BIH)", RFC 6535, February 2012. 658 [RFC6555] Wing, D. and A. Yourtchenko, "Happy Eyeballs: Success with 659 Dual-Stack Hosts", RFC 6555, April 2012. 661 [RFC6603] Korhonen, J., Savolainen, T., Krishnan, S., and O. Troan, 662 "Prefix Exclude Option for DHCPv6-based Prefix 663 Delegation", RFC 6603, May 2012. 665 [RFC6724] Thaler, D., Draves, R., Matsumoto, A., and T. Chown, 666 "Default Address Selection for Internet Protocol Version 6 667 (IPv6)", RFC 6724, September 2012. 669 9.2. Informative References 671 [I-D.ietf-behave-nat64-discovery-heuristic] 672 Savolainen, T., Korhonen, J., and D. Wing, "Discovery of 673 the IPv6 Prefix Used for IPv6 Address Synthesis", draft- 674 ietf-behave-nat64-discovery-heuristic-17 (work in 675 progress), April 2013. 677 [I-D.ietf-pcp-base] 678 Wing, D., Cheshire, S., Boucadair, M., Penno, R., and P. 679 Selkirk, "Port Control Protocol (PCP)", draft-ietf-pcp- 680 base-29 (work in progress), November 2012. 682 [I-D.ietf-pcp-nat64-prefix64] 683 Boucadair, M., "Learn NAT64 PREFIX64s using PCP", draft- 684 ietf-pcp-nat64-prefix64-00 (work in progress), February 685 2013. 687 [I-D.ietf-v6ops-64share] 688 Byrne, C., Drown, D., and V. Ales, "Extending an IPv6 /64 689 Prefix from a 3GPP Mobile Interface to a LAN", draft-ietf- 690 v6ops-64share-04 (work in progress), April 2013. 692 [I-D.ietf-v6ops-rfc3316bis] 693 Korhonen, J., Arkko, J., Savolainen, T., and S. Krishnan, 694 "IPv6 for 3GPP Cellular Hosts", draft-ietf-v6ops- 695 rfc3316bis-01 (work in progress), February 2013. 697 [IR92] GSMA, , "IR.92.V4.0 - IMS Profile for Voice and SMS", 698 March 2011, . 701 [RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S. 702 Rose, "DNS Security Introduction and Requirements", RFC 703 4033, March 2005. 705 [RFC4034] Arends, R., Austein, R., Larson, M., Massey, D., and S. 706 Rose, "Resource Records for the DNS Security Extensions", 707 RFC 4034, March 2005. 709 [RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S. 710 Rose, "Protocol Modifications for the DNS Security 711 Extensions", RFC 4035, March 2005. 713 [RFC6092] Woodyatt, J., "Recommended Simple Security Capabilities in 714 Customer Premises Equipment (CPE) for Providing 715 Residential IPv6 Internet Service", RFC 6092, January 716 2011. 718 [RFC6204] Singh, H., Beebee, W., Donley, C., Stark, B., and O. 719 Troan, "Basic Requirements for IPv6 Customer Edge 720 Routers", RFC 6204, April 2011. 722 [RFC6459] Korhonen, J., Soininen, J., Patil, B., Savolainen, T., 723 Bajko, G., and K. Iisakkila, "IPv6 in 3rd Generation 724 Partnership Project (3GPP) Evolved Packet System (EPS)", 725 RFC 6459, January 2012. 727 [RFC6877] Mawatari, M., Kawashima, M., and C. Byrne, "464XLAT: 728 Combination of Stateful and Stateless Translation", RFC 729 6877, April 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; 746 Core 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 763 David Binet 764 France Telecom 765 Rennes 766 France 768 Email: david.binet@orange.com 770 Mohamed Boucadair 771 France Telecom 772 Rennes 35000 773 France 775 Email: mohamed.boucadair@orange.com 777 Ales Vizdal 778 Deutsche Telekom AG 780 Email: ales.vizdal@t-mobile.cz 782 Cameron Byrne 783 T-Mobile 784 USA 786 Email: Cameron.Byrne@T-Mobile.com 788 Gang Chen 789 China Mobile 791 Email: phdgang@gmail.com