One document matched: draft-ietf-v6ops-mobile-device-profile-08.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc rfcedstyle="yes"?>
<rfc category="info" docName="draft-ietf-v6ops-mobile-device-profile-08"
ipr="trust200902" updates="">
<front>
<title abbrev="IPv6 Profile for Cellular Devices">An Internet Protocol
Version 6 (IPv6) Profile for 3GPP Mobile Devices</title>
<author fullname="David Binet" initials="D." surname="Binet">
<organization>France Telecom</organization>
<address>
<postal>
<street></street>
<city>Rennes</city>
<region></region>
<code></code>
<country>France</country>
</postal>
<email>david.binet@orange.com</email>
</address>
</author>
<author fullname="Mohamed Boucadair" initials="M." surname="Boucadair">
<organization>France Telecom</organization>
<address>
<postal>
<street></street>
<city>Rennes</city>
<region></region>
<code>35000</code>
<country>France</country>
</postal>
<email>mohamed.boucadair@orange.com</email>
</address>
</author>
<author fullname="Ales Vizdal" initials="A." surname="Vizdal">
<organization>Deutsche Telekom AG</organization>
<address>
<postal>
<street></street>
<city></city>
<region></region>
<country></country>
</postal>
<phone></phone>
<email>ales.vizdal@t-mobile.cz</email>
<uri></uri>
</address>
</author>
<author fullname="Cameron Byrne" initials="C." surname="Byrne">
<organization>T-Mobile</organization>
<address>
<postal>
<street></street>
<city></city>
<region></region>
<code></code>
<country>USA</country>
</postal>
<phone></phone>
<email>Cameron.Byrne@T-Mobile.com</email>
</address>
</author>
<author fullname="Gang Chen" initials="G." surname="Chen">
<organization>China Mobile</organization>
<address>
<postal>
<street></street>
<city></city>
<region></region>
<code></code>
<country></country>
</postal>
<email>phdgang@gmail.com</email>
</address>
</author>
<date day="" month="" year="2014" />
<workgroup>V6OPS Working Group</workgroup>
<abstract>
<t>This document defines an IPv6 profile that a number of operators
recommend in order to connect 3GPP mobile devices to an IPv6-only or
dual-stack wireless network (including 3GPP cellular network and IEEE
802.11 network).</t>
<t>This document defines a different profile than the one for general
connection to IPv6 cellular networks defined in the IPv6 for Third
Generation Partnership Project (3GPP) Cellular Hosts document. In
particular, this document identifies also features to deliver IPv4
connectivity service over an IPv6-only transport.</t>
<t>Both hosts and devices with capability to share their WAN (Wide Area
Network) connectivity are in scope.</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>IPv6 deployment in 3GPP mobile networks is the only perennial
solution to the exhaustion of IPv4 addresses in those networks. Several
mobile operators have already deployed IPv6 <xref
target="RFC2460"></xref> or are in the pre-deployment phase. One of the
major hurdles encountered by mobile operators is the availability of
non-broken IPv6 implementation in mobile devices.</t>
<t><xref target="RFC7066"></xref> lists a set of features to be
supported by cellular hosts to connect to 3GPP mobile networks. In the
light of recent IPv6 production deployments, additional features to
facilitate IPv6-only deployments while accessing IPv4-only service are
to be considered.</t>
<t>This document defines a different profile than the one for general
connection to IPv6 mobile networks defined in <xref
target="RFC7066"></xref>; in particular: <list style="symbols">
<t>It lists an extended list of features while <xref
target="RFC7066"></xref> identifies issues and explains how to
implement basic IPv6 features in a cellular context.</t>
<t>It identifies also features to ensure IPv4 service delivery over
an IPv6-only transport.</t>
</list></t>
<t>This document defines an IPv6 profile for mobile devices listing
specifications produced by various Standards Developing Organizations
(in particular 3GPP and IETF). The objectives of this effort are:<list
style="numbers">
<t>List in one single document a comprehensive list of IPv6 features
for a mobile device, including both IPv6-only and dual-stack mobile
deployment contexts. These features cover various network types such
as GPRS (General Packet Radio Service), EPC (Evolved Packet Core) or
IEEE 802.11 network.</t>
<t>Help Operators with the detailed device requirement list
preparation (to be exchanged with device suppliers). This is also a
contribution to harmonize Operators’ requirements towards
device vendors.</t>
<t>Vendors to be aware of a set of features to allow for IPv6
connectivity and IPv4 service continuity (over an IPv6-only
transport).</t>
</list></t>
<t>Pointers to some requirements listed in <xref
target="RFC6434"></xref> are included in this profile. The justification
for using a stronger language compared to what is specified in <xref
target="RFC6434"></xref> is provided for some recommendations.</t>
<t>The recommendations do not include 3GPP release details. For more
information on the 3GPP releases detail, the reader may refer to Section
6.2 of <xref target="RFC6459"></xref>.</t>
<t>Some of the features listed in this profile document require to
activate dedicated functions at the network side. It is out of scope of
this document to list these network-side functions.</t>
<t>A detailed overview of IPv6 support in 3GPP architectures is provided
in <xref target="RFC6459"></xref>.</t>
<section title="Terminology">
<t>This document makes use of the terms defined in <xref
target="RFC6459"></xref>. In addition, the following terms are
used:<list style="symbols">
<t>"3GPP cellular host" (or cellular host for short) denotes a
3GPP device which can be connected to 3GPP mobile networks or IEEE
802.11 networks.</t>
<t>"3GPP cellular device" (or cellular device for short) refers to
a cellular host which supports the capability to share its WAN
(Wide Area Network) connectivity.</t>
<t>"Cellular host" and "mobile host" are used interchangeably.</t>
<t>"Cellular device" and "mobile device" are used
interchangeably.</t>
</list></t>
<t>PREFIX64 denotes an IPv6 prefix used to build IPv4-converted IPv6
addresses <xref target="RFC6052"></xref>.</t>
</section>
<section title="Scope">
<t>A 3GPP mobile network can be used to connect various user
equipments such as a mobile telephone, a CPE (Customer Premises
Equipment) or a M2M (machine-to-machine) device. Because of this
diversity of terminals, it is necessary to define a set of IPv6
functionalities valid for any node directly connecting to a 3GPP
mobile network. This document describes these functionalities.</t>
<t>This document is structured to provide the generic IPv6
recommendations which are valid for all nodes, whatever their function
(e.g., host or CPE) or service (e.g., Session Initiation Protocol
(SIP, <xref target="RFC3261"></xref>)) capability. The document also
contains sections covering specific functionalities for devices
providing some LAN functions (e.g., mobile CPE or broadband
dongles).</t>
<t>The recommendations listed below are valid for both 3GPP GPRS and
3GPP EPS (Evolved Packet System) access. For EPS, PDN-Connection term
is used instead of PDP-Context.</t>
<t>This document identifies also some WLAN-related IPv6
recommendations. Other non-3GPP accesses <xref
target="TS.23402"></xref> are out of scope of this document.</t>
</section>
<section title="Language Considerations">
<t>The key words "must", "must not", "should", "should not", and "may"
in this document are to be interpreted as described in <xref
target="RFC2119">RFC 2119</xref>.</t>
<t>This document is not a standard, and conformance with it is not
required in order to claim conformance with IETF standards for IPv6.
The support of the full set of features may not be required in some
deployment contexts. The authors believe that the support of a subset
of the features included in this protocol may lead to degraded level
of service in some deployment contexts.</t>
<t>This document uses these keywords only for precision.</t>
</section>
</section>
<section anchor="generic" title="Connectivity Recommendations">
<t>This section identifies the main connectivity recommendations to be
followed by a cellular host to attach to a network using IPv6. Both
dual-stack and IPv6-only deployment models are considered. IPv4 service
continuity features are listed in this section because these are
critical for Operators with an IPv6-only deployment model.</t>
<t><list counter="" style="format C_REC#%d:">
<t hangText="REC#1:">The cellular host must be compliant with
Section 5.9.1 (IPv6 Addressing Architecture) and Section 5.8 (ICMPv6
support) of <xref target="RFC6434"></xref>.</t>
<t hangText="REC#2:">In order to allow each operator to select their
own strategy regarding IPv6 introduction, the cellular host must
support both IPv6 and IPv4v6 PDP-Contexts <xref
target="TS.23060"></xref>. Both IPv6 and IPv4v6 PDP-Contexts must be
supported. IPv4, IPv6 or IPv4v6 PDP-Context request acceptance
depends on the cellular network configuration.</t>
<t hangText="REQ#3:">The cellular host must comply with the behavior
defined in <xref target="TS.23060"></xref> <xref
target="TS.23401"></xref> <xref target="TS.24008"></xref> for
requesting a PDP-Context type. In particular, the cellular host must
request by default an IPv6 PDP-Context if the cellular host is
IPv6-only and requesting an IPv4v6 PDP-Context if the cellular host
is dual-stack or when the cellular host is not aware of connectivity
types requested by devices connected to it (e.g., cellular host with
LAN capabilities as discussed in <xref target="cpe"></xref>): <list
style="symbols">
<t>If the requested IPv4v6 PDP-Context is not supported by the
network, but IPv4 and IPv6 PDP types are allowed, then the
cellular host will be configured with an IPv4 address or an IPv6
prefix by the network. It must initiate another PDP-Context
activation in addition to the one already activated for a given
APN (Access Point Name).</t>
<t>If the requested PDP type and subscription data allows only
one IP address family (IPv4 or IPv6), the cellular host must not
request a second PDP-Context to the same APN for the other IP
address family.</t>
</list>The text above focuses on the specification part which
explains the behavior for requesting IPv6-related PDP-Context(s).
Understanding this behavior is important to avoid having broken IPv6
implementations in cellular devices.</t>
<t hangText="REQ#4:">The cellular host must support the PCO
(Protocol Configuration Options) <xref target="TS.24008"></xref> to
retrieve the IPv6 address(es) of the Recursive DNS server(s). <list
style="empty">
<t>In-band signaling is a convenient method to inform the
cellular host about various services, including DNS server
information. It does not require any specific protocol to be
supported and it is already deployed in IPv4 cellular networks
to convey such DNS information.</t>
</list></t>
<t hangText="REQ#5:">The cellular host must support IPv6 aware
Traffic Flow Templates (TFT) <xref target="TS.24008"></xref>.<list
style="empty">
<t>Traffic Flow Templates are employing a packet filter to
couple an IP traffic with a PDP-Context. Thus a dedicated
PDP-Context and radio resources can be provided by the cellular
network for certain IP traffic.</t>
</list></t>
<t hangText="REQ#6:">The cellular host must support the Neighbor
Discovery Protocol (<xref target="RFC4861"></xref> and <xref
target="RFC5942"></xref>).<list style="empty">
<t>This is a stronger form compared to what is specified in
Section 5.2 and Section 12.2 of <xref
target="RFC6434"></xref>.</t>
<t>The support of Neighbor Discovery Protocol is mandatory in
3GPP cellular environment as it is the only way to convey IPv6
prefix towards the 3GPP cellular device.</t>
<t>In particular, MTU (Maximum Transmission Unit) communication
via Router Advertisement must be supported since many 3GPP
networks do not have a standard MTU setting.</t>
</list></t>
<t hangText="REQ#7:">The cellular host must comply with Section
5.6.1 of <xref target="RFC6434"></xref>. If the MTU used by cellular
hosts is larger than 1280 bytes, they can rely on Path MTU discovery
function to discover the real path MTU.</t>
<t hangText="REQ#8:">The cellular host must support IPv6 Stateless
Address Autoconfiguration (<xref target="RFC4862"></xref>) apart
from the exceptions noted in <xref target="TS.23060"></xref> (3G)
and <xref target="TS.23401"></xref> (LTE):<list style="empty">
<t>Stateless mode is the only way to configure a cellular host.
The GGSN/PGW must allocate a prefix that is unique within its
scope to each primary PDP-Context.</t>
<t>To configure its link local address, the cellular host must
use the Interface Identifier conveyed in 3GPP PDP-Context setup
signaling received from a GGSN/PGW. The cellular host may use a
different Interface Identifiers to configure its global
addresses (see also A_REC#1 about privacy addressing
recommendation).</t>
<t>For more details, refer to <xref target="RFC6459"></xref> and
<xref target="RFC7066"></xref>.</t>
</list></t>
<t hangText="REQ#9:">The cellular host must comply with Section 7.3
of <xref target="RFC6434"></xref>.</t>
<t hangText="REQ#10:">The cellular host must comply with Section
7.2.1 of <xref target="RFC6434"></xref>.<list style="empty">
<t>Stateless DHCPv6 is useful to retrieve other information than
DNS.</t>
<t>If <xref target="RFC6106"></xref> is not supported at the
network side, the cellular host should retrieve DNS information
using stateless DHCPv6 <xref target="RFC3736"></xref>.</t>
</list></t>
<t hangText="REQ#11:">If the cellular host receives the DNS
information in several channels for the same interface, the
following preference order must be followed:<list style="empty">
<t>1. PCO</t>
<t>2. RA</t>
<t>3. DHCPv6</t>
</list></t>
<t hangText="REQ#12:">Because of potential operational deficiencies
to be experienced in some roaming situations, the cellular host must
be able to be configured with a home IP profile and a roaming IP
profile. The aim of the roaming profile is to limit the PDP type(s)
requested by the cellular host when out of the home network. Note,
distinct PDP type(s) can be configured for home and roaming
cases.</t>
<t hangText="REQ#12:">In order to ensure IPv4 service continuity in
an IPv6-only deployment context, the cellular host should support a
method to locally construct IPv4-embedded IPv6 addresses <xref
target="RFC6052"></xref>. A method to learn PREFIX64 should be
supported by the cellular host. <list style="empty">
<t>This solves the issue when applications use IPv4 referrals on
IPv6-only access networks.</t>
<t>In PCP-based environments, cellular hosts should follow <xref
target="RFC7225"></xref> to learn the IPv6 Prefix used by an
upstream PCP-controlled NAT64 device. If PCP is not enabled, the
cellular host should implement the method specified in <xref
target="RFC7050"></xref> to retrieve the PREFIX64.</t>
</list></t>
<t hangText="REQ#13:">In order to ensure IPv4 service continuity in
an IPv6-only deployment context, the cellular host should implement
the Customer Side Translator (CLAT, <xref target="RFC6877"></xref>)
function which is compliant with <xref target="RFC6052"></xref><xref
target="RFC6145"></xref><xref target="RFC6146"></xref>. <list
style="empty">
<t>CLAT function in the cellular host allows for IPv4-only
application and IPv4-referals to work on an IPv6-only
connectivity. CLAT function requires a NAT64 capability <xref
target="RFC6146"></xref> in the core network.</t>
</list></t>
<t hangText="REQ#14:">In order to ensure IPv4 service continuity in
an IPv6-only deployment context, the cellular host should embed a
DNS64 function <xref target="RFC6147"></xref>. <list style="empty">
<t>Local DNS64 functionality allows for compatibility with DNS
Security Extensions (DNSSEC, <xref target="RFC4033"></xref>,
<xref target="RFC4034"></xref>, <xref target="RFC4035"></xref>).
Means to configure or discover a PREFIX64 is also required on
the cellular device as discussed in C_REC#13.</t>
</list></t>
<t hangText="REQ#15:">The cellular host should support PCP <xref
target="RFC6887"></xref>.<list style="empty">
<t>The support of PCP is seen as a driver to save battery
consumption exacerbated by keepalive messages. PCP also gives
the possibility of enabling incoming connections to the cellular
device. Indeed, because several stateful devices may be deployed
in wireless networks (e.g., NAT and/or Firewalls), PCP can be
used by the cellular host to control network-based NAT and
Firewall functions which will reduce per-application signaling
and save battery consumption.</t>
</list></t>
<t hangText="REQ#16:">When the cellular host is dual-stack connected
(i.e., configured with an IPv4 address and IPv6 prefix), it should
support means to prefer native IPv6 connection over connection
established through translation devices (e.g., NAT44 and
NAT64).<list style="empty">
<t>When both IPv4 and IPv6 DNS servers are configured, a
dual-stack host must contact first its IPv6 DNS server.</t>
<t>Cellular hosts should follow the procedure specified in <xref
target="RFC6724"></xref> for source address selection.</t>
</list></t>
<t hangText="REQ#17:">The cellular host should support Happy
Eyeballs procedure defined in <xref target="RFC6555"></xref>.</t>
</list></t>
<section title="WLAN Connectivity Recommendations">
<t>It is increasingly common for cellular hosts have a WLAN interface
in addition to their cellular interface. These hosts are likely to be
connected to private or public hotspots. Below are listed some generic
recommendations:</t>
<t><list style="format W_REC#%d:">
<t hangText="REQ#19:">IPv6 must be supported on the WLAN
interface. In particular, WLAN interface must behave properly when
only an IPv6 connectivity is provided.<list style="empty">
<t>Some tests revealed that IPv4 configuration is required to
enable IPv6-only connectivity. Indeed, some cellular handsets
can access a WLAN IPv6-only network by configuring first a
static IPv4 address. Once the device is connected to the
network and the wlan0 interface got an IPv6 global address,
the IPv4 address can be deleted from the configuration. This
avoids the device to ask automatically for a DHCPv4 server,
and allows to connect to IPv6-only networks. Failing to
configure an IPv4 address on the interface must not prohibit
using IPv6 on the same interface.</t>
<t>IPv6 Stateless Address Autoconfiguration (<xref
target="RFC4862"></xref>) must be supported.</t>
</list></t>
<t hangText="REQ#20:">DHCPv6 client should be supported on WLAN
interface.<list style="empty">
<t>Refer to Section 7.2.1 of <xref
target="RFC6434"></xref>.</t>
</list></t>
<t hangText="REQ#21:">WLAN interface should support Router
Advertisement Options for DNS configuration (See Section 7.3 of
<xref target="RFC6434"></xref>).</t>
<t hangText="REQ#22:">If the device receives the DNS information
in several channels for the same interface, the following
preference order must be followed: <list style="empty">
<t>1. RA</t>
<t>2. DHCPv6</t>
</list></t>
</list></t>
</section>
</section>
<section title="Advanced Recommendations">
<t>This section identifies a set of advanced recommendations to meet
regulatory constraints in some countries, fulfill requirements of
critical services such as VoLTE (Voice over LTE), or enforce policies
such as traffic offload.</t>
<t><list style="format A_REC#%d:">
<t hangText="REQ#23:">The cellular host must be able to generate
IPv6 addresses which preserve privacy. <list style="empty">
<t>The activation of privacy extension (e.g., using <xref
target="RFC4941"></xref> or <xref target="RFC7217"></xref>)
makes it more difficult to track a host over time when compared
to using a permanent Interface Identifier. Note, <xref
target="RFC4941"></xref> does not require any DAD mechanism to
be activated as the GGSN/PGW must not configure any global
address based on the prefix allocated to the cellular host.</t>
<t>Tracking a host is still possible based on the first 64 bits
of the IPv6 address. Means to prevent against such tracking
issues may be enabled in the network side.</t>
<t>Privacy extensions are required by regulatory bodies in some
countries.</t>
</list></t>
<t hangText="REQ#24:">The cellular host must support ROHC RTP
Profile (0x0001) and ROHC UDP Profile (0x0002) for IPv6 (<xref
target="RFC5795"></xref>). Other ROHC profiles may be
supported.<list style="empty">
<t>Bandwidth in cellular networks must be optimized as much as
possible. ROHC provides a solution to reduce bandwidth
consumption and to reduce the impact of having bigger packet
headers in IPv6 compared to IPv4.</t>
<t>"RTP/UDP/IP" ROHC profile (0x0001) to compress RTP packets
<xref target="RFC3550"></xref> and "UDP/IP" ROHC profile
(0x0002) to compress RTCP packets <xref target="RFC3550"></xref>
are required for Voice over LTE (VoLTE) by IR.92.4.0 section 4.1
<xref target="IR92"></xref>. Note, <xref target="IR92"></xref>
indicates also the host must be able to apply the compression to
packets that are carried over the radio bearer dedicated for the
voice media.</t>
</list></t>
<t hangText="REQ#25:">The cellular host must comply with Section 5.3
of <xref target="RFC6434"></xref> and should support Router
Advertisement extension for communicating default router preferences
and more-specific routes as described in <xref
target="RFC4191"></xref>.<list style="empty">
<t>This function can be used for instance for traffic
offload.</t>
</list></t>
</list></t>
</section>
<section anchor="cpe"
title="Recommendations for Cellular Devices with LAN Capabilities">
<t>This section focuses on cellular devices (e.g., CPE, smartphones, or
dongles with tethering features) which provide IP connectivity to other
devices connected to them. In such case, all connected devices are
sharing the same 2G, 3G or LTE connection. In addition to the generic
recommendations listed in <xref target="generic"></xref>, these cellular
devices have to meet the recommendations listed below.</t>
<t><list style="format L_REC#%d:">
<t hangText="REQ#26:">The cellular device must support Prefix
Delegation capabilities <xref target="RFC3633"></xref> and must
support Prefix Exclude Option for DHCPv6-based Prefix Delegation as
defined in <xref target="RFC6603"></xref>. Particularly, it must
behave as a Requesting Router. <list style="empty">
<t>Cellular networks are more and more perceived as an
alternative to fixed networks for home IP-based services
delivery; especially with the advent of smartphones and 3GPP
data dongles. There is a need for an efficient mechanism to
assign shorter prefix than /64 to cellular hosts so that each
LAN segment can get its own /64 prefix and multi-link subnet
issues to be avoided.</t>
<t>In case a prefix is delegated to a cellular host using
DHCPv6, the cellular device will be configured with two
prefixes: <list style="empty">
<t>(1) one for 3GPP link allocated using SLAAC mechanism
and</t>
<t>(2) another one delegated for LANs acquired during Prefix
Delegation operation.</t>
</list>Note that the 3GPP network architecture requires both
the WAN (Wide Area Network) and the delegated prefix to be
aggregatable, so the subscriber can be identified using a single
prefix.</t>
<t>Without the Prefix Exclude Option, the delegating router
(GGSN/PGW) will have to ensure <xref target="RFC3633"></xref>
compliancy (e.g., halving the delegated prefix and assigning the
WAN prefix out of the 1st half and the prefix to be delegated to
the terminal from the 2nd half).</t>
</list></t>
<t hangText="REQ#27:">The cellular CPE must be compliant with the
requirements specified in <xref target="RFC6204"></xref>.<list
style="empty">
<t>There are several deployments, particularly in emerging
countries, that relies on mobile networks to provide broadband
services (e.g., customers are provided with mobile CPEs).</t>
</list></t>
<t hangText="REQ#28:">For deployments requiring to share the same
/64 prefix, the cellular device should support <xref
target="RFC7278"></xref> to enable sharing a /64 prefix between the
3GPP interface towards the GGSN/PGW (WAN interface) and the LAN
interfaces.</t>
<t hangText="REQ#29:">In order to ensure IPv4 service continuity in
an IPv6-only deployment context, the cellular device should support
the Customer Side Translator (CLAT) <xref target="RFC6877"></xref>.
<list style="empty">
<t>Various IP devices are likely to be connected to cellular
device, acting as a CPE. Some of these devices can be
dual-stack, others are IPv6-only or IPv4-only. IPv6-only
connectivity for cellular device does not allow IPv4-only
sessions to be established for hosts connected on the LAN
segment of cellular devices.</t>
<t>In order to allow IPv4 sessions establishment initiated from
devices located on LAN segment side and target IPv4 nodes, a
solution consists in integrating the CLAT function in the
cellular device. As elaborated in <xref
target="generic"></xref>, the CLAT function allows also IPv4
applications to continue running over an IPv6-only host.</t>
</list></t>
<t hangText="REQ#30:">If a RA MTU is advertised from the 3GPP
network, the cellular device should relay that upstream MTU
information to the downstream attached LAN devices in RA. <list
style="empty">
<t>Receiving and relaying RA MTU values facilitates a more
harmonious functioning of the mobile core network where end
nodes transmit packets that do not exceed the MTU size of the
mobile network's GTP tunnels.</t>
<t><xref target="TS.23060"></xref> indicates providing a link
MTU value of 1358 octets to the 3GPP cellular device will
prevent the IP layer fragmentation within the transport network
between the cellular device and the GGSN/PGW.</t>
</list></t>
</list></t>
</section>
<section title="APIs & Applications Recommendations">
<t>The use of address family dependent APIs (Application Programming
Interfaces) or hard-coded IPv4 address literals may lead to broken
applications when IPv6 connectivity is in use. This section identifies a
set of recommendations aiming to minimize broken applications when the
cellular device is attached to an IPv6 network.</t>
<t><list style="format APP_REC#%d:">
<t hangText="REQ#31:">Name resolution libraries must support both
IPv4 and IPv6.<list style="empty">
<t>In particular, the cellular host must support <xref
target="RFC3596"></xref>.</t>
</list></t>
<t hangText="REQ#32:">Applications provided by the mobile device
vendor must be independent of the underlying IP address family.<list
style="empty">
<t>This means applications must be IP version agnostic.</t>
</list></t>
<t hangText="REQ#33:">Applications provided by the mobile device
vendor that use Uniform Resource Identifiers (URIs) must follow
<xref target="RFC3986"></xref>. For example, SIP applications must
follow the correction defined in <xref target="RFC5954"></xref>.</t>
</list></t>
</section>
<section anchor="security" title="Security Considerations">
<t>The security considerations identified in <xref
target="RFC7066"></xref> and <xref target="RFC6459"></xref> are to be
taken into account.</t>
<t>Security-related considerations that apply when the cellular device
provides LAN features are specified in <xref
target="RFC6092"></xref>.</t>
<t>Address privacy considerations are discussed in <xref
target="RFC4941"></xref> <xref target="RFC7217"></xref>.</t>
</section>
<section anchor="iana" title="IANA Considerations">
<t>This document does not require any action from IANA.</t>
</section>
<section anchor="Acknowledgements" title="Acknowledgements">
<t>Many thanks to H. Soliman, H. Singh, L. Colliti, T. Lemon, B.
Sarikaya, M. Mawatari, M. Abrahamsson, P. Vickers, V. Kuarsingh, N.
Heatley, E. Kline, S. Josefsson, A. Baryun, and J. Woodyatt for the
discussion in the v6ops mailing list.</t>
<t>Special thanks to T. Savolainen, J. Korhonen, and J. Jaeggli for
their detailed reviews and comments.</t>
</section>
</middle>
<back>
<references title="Normative References">
<?rfc include="reference.RFC.2119"?>
<?rfc include='reference.RFC.6052'?>
<?rfc include='reference.RFC.4861'?>
<?rfc include='reference.RFC.4862'?>
<?rfc include='reference.RFC.3633'?>
<?rfc include='reference.RFC.6603'?>
<?rfc include='reference.RFC.5954'?>
<?rfc include='reference.RFC.3596'?>
<?rfc include='reference.RFC.5795'?>
<?rfc include='reference.RFC.5942'?>
<?rfc include='reference.RFC.3986'?>
<?rfc include='reference.RFC.2460'?>
<?rfc include='reference.RFC.7066'?>
<reference anchor="TS.23060">
<front>
<title>General Packet Radio Service (GPRS); Service description;
Stage 2</title>
<author fullname="" surname="">
<organization>3GPP</organization>
</author>
<date day="0" month="September" year="2011" />
</front>
</reference>
<reference anchor="TS.24008">
<front>
<title>Mobile radio interface Layer 3 specification; Core network
protocols; Stage 3</title>
<author fullname="" surname="">
<organization>3GPP</organization>
</author>
<date day="0" month="June" year="2011" />
</front>
</reference>
<reference anchor="TS.23401">
<front>
<title>General Packet Radio Service (GPRS) enhancements for Evolved
Universal Terrestrial Radio Access Network (E-UTRAN) access</title>
<author fullname="" surname="">
<organization>3GPP</organization>
</author>
<date day="0" month="September" year="2011" />
</front>
</reference>
<reference anchor="IR92"
target="http://www.gsma.com/newsroom/ir-92-v4-0-ims-profile-for-voice-and-sms">
<front>
<title>IR.92.V4.0 – IMS Profile for Voice and SMS</title>
<author fullname="" surname="">
<organization>GSMA</organization>
</author>
<date day="0" month="March" year="2011" />
</front>
</reference>
</references>
<references title="Informative References">
<?rfc include='reference.RFC.6459'?>
<?rfc include='reference.RFC.6145'?>
<?rfc include='reference.RFC.6147'?>
<?rfc include='reference.RFC.6204'?>
<?rfc include='reference.RFC.6555'?>
<?rfc include='reference.RFC.4191'?>
<?rfc include='reference.RFC.6434'?>
<?rfc include='reference.RFC.6724'?>
<?rfc include='reference.RFC.6146'?>
<?rfc include='reference.RFC.6106'?>
<?rfc include='reference.RFC.3736'?>
<?rfc include='reference.RFC.7217'?>
<?rfc include='reference.RFC.4941'?>
<?rfc include='reference.RFC.3261'?>
<?rfc include='reference.RFC.3550'?>
<?rfc include='reference.RFC.6092'?>
<?rfc include='reference.RFC.4033'?>
<?rfc include='reference.RFC.4034'?>
<?rfc include='reference.RFC.4035'?>
<?rfc include='reference.RFC.7225'?>
<?rfc include='reference.RFC.7050'?>
<?rfc include='reference.RFC.6887'?>
<?rfc include='reference.RFC.6877'?>
<?rfc include='reference.RFC.7278'?>
<reference anchor="TS.23402">
<front>
<title>Architecture enhancements for non-3GPP accesses</title>
<author fullname="" surname="">
<organization>3GPP</organization>
</author>
<date day="0" month="September" year="2011" />
</front>
</reference>
</references>
<!--
-->
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 19:37:59 |