draft-ietf-v6ops-mobile-device-profile-06.txt   draft-ietf-v6ops-mobile-device-profile-07.txt 
V6OPS Working Group D. Binet V6OPS Working Group D. Binet
Internet-Draft M. Boucadair Internet-Draft M. Boucadair
Intended status: Informational France Telecom Intended status: Informational France Telecom
Expires: March 15, 2014 A. Vizdal Expires: September 12, 2014 A. Vizdal
Deutsche Telekom AG Deutsche Telekom AG
C. Byrne C. Byrne
T-Mobile T-Mobile
G. Chen G. Chen
China Mobile China Mobile
September 11, 2013 March 11, 2014
An Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices An Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices
draft-ietf-v6ops-mobile-device-profile-06 draft-ietf-v6ops-mobile-device-profile-07
Abstract Abstract
This document defines an IPv6 profile that a number of operators This document defines an IPv6 profile that a number of operators
recommend in order to connect 3GPP mobile devices to an IPv6-only or recommend in order to connect 3GPP mobile devices to an IPv6-only or
dual-stack wireless network (including 3GPP cellular network and IEEE dual-stack wireless network (including 3GPP cellular network and IEEE
802.11 network). 802.11 network).
This document defines a different profile than the one for general This document defines a different profile than the one for general
connection to IPv6 cellular networks defined in connection to IPv6 cellular networks defined in [RFC7066]. In
[I-D.ietf-v6ops-rfc3316bis]. In particular, this document identifies particular, this document identifies also features to deliver IPv4
also features to deliver IPv4 connectivity service over an IPv6-only connectivity service over an IPv6-only transport.
transport.
Both hosts and devices with capability to share their WAN (Wide Area Both hosts and devices with capability to share their WAN (Wide Area
Network) connectivity are in scope. Network) connectivity are in scope.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 15, 2014. This Internet-Draft will expire on September 12, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 46 skipping to change at page 2, line 46
1. Introduction 1. Introduction
IPv6 deployment in 3GPP mobile networks is the only perennial IPv6 deployment in 3GPP mobile networks is the only perennial
solution to the exhaustion of IPv4 addresses in those networks. solution to the exhaustion of IPv4 addresses in those networks.
Several mobile operators have already deployed IPv6 [RFC2460] or are Several mobile operators have already deployed IPv6 [RFC2460] or are
in the pre-deployment phase. One of the major hurdles encountered by in the pre-deployment phase. One of the major hurdles encountered by
mobile operators is the availability of non-broken IPv6 mobile operators is the availability of non-broken IPv6
implementation in mobile devices. implementation in mobile devices.
[I-D.ietf-v6ops-rfc3316bis] lists a set of features to be supported [RFC7066] lists a set of features to be supported by cellular hosts
by cellular hosts to connect to 3GPP mobile networks. In the light to connect to 3GPP mobile networks. In the light of recent IPv6
of recent IPv6 production deployments, additional features to production deployments, additional features to facilitate IPv6-only
facilitate IPv6-only deployments while accessing IPv4-only service deployments while accessing IPv4-only service are to be considered.
are to be considered.
This document defines a different profile than the one for general This document defines a different profile than the one for general
connection to IPv6 mobile networks defined in connection to IPv6 mobile networks defined in [RFC7066]; in
[I-D.ietf-v6ops-rfc3316bis]; in particular: particular:
o It lists an extended list of features while o It lists an extended list of features while [RFC7066] identifies
[I-D.ietf-v6ops-rfc3316bis] identifies issues and explains how to issues and explains how to implement basic IPv6 features in a
implement basic IPv6 features in a cellular context. cellular context.
o It identifies also features to ensure IPv4 service delivery over o It identifies also features to ensure IPv4 service delivery over
an IPv6-only transport. an IPv6-only transport.
This document defines an IPv6 profile for mobile devices listing This document defines an IPv6 profile for mobile devices listing
specifications produced by various Standards Developing Organizations specifications produced by various Standards Developing Organizations
(in particular 3GPP and IETF). The objectives of this effort are: (in particular 3GPP and IETF). The objectives of this effort are:
1. List in one single document a comprehensive list of IPv6 features 1. List in one single document a comprehensive list of IPv6 features
for a mobile device, including both IPv6-only and dual-stack for a mobile device, including both IPv6-only and dual-stack
skipping to change at page 7, line 8 skipping to change at page 7, line 8
The GGSN/PGW must allocate a prefix that is unique within its The GGSN/PGW must allocate a prefix that is unique within its
scope to each primary PDP-Context. scope to each primary PDP-Context.
To configure its link local address, the cellular host MUST To configure its link local address, the cellular host MUST
use the Interface Identifier conveyed in 3GPP PDP-Context use the Interface Identifier conveyed in 3GPP PDP-Context
setup signaling received from a GGSN/PGW. The cellular host setup signaling received from a GGSN/PGW. The cellular host
may use a different Interface Identifiers to configure its may use a different Interface Identifiers to configure its
global addresses (see also REQ#23 about privacy addressing global addresses (see also REQ#23 about privacy addressing
requirement). requirement).
For more details, refer to [RFC6459] and For more details, refer to [RFC6459] and [RFC7066].
[I-D.ietf-v6ops-rfc3316bis].
REQ#9: The cellular host MUST comply with Section 7.3 of [RFC6434]. REQ#9: The cellular host MUST comply with Section 7.3 of [RFC6434].
REQ#10: The cellular host MUST comply with Section 7.2.1 of REQ#10: The cellular host MUST comply with Section 7.2.1 of
[RFC6434]. [RFC6434].
Stateless DHCPv6 is useful to retrieve other information than Stateless DHCPv6 is useful to retrieve other information than
DNS. DNS.
If [RFC6106] is not supported at the network side, the If [RFC6106] is not supported at the network side, the
skipping to change at page 7, line 44 skipping to change at page 7, line 43
construct IPv4-embedded IPv6 addresses [RFC6052]. A method to construct IPv4-embedded IPv6 addresses [RFC6052]. A method to
learn PREFIX64 SHOULD be supported by the cellular host. learn PREFIX64 SHOULD be supported by the cellular host.
This solves the issue when applications use IPv4 referrals on This solves the issue when applications use IPv4 referrals on
IPv6-only access networks. IPv6-only access networks.
In PCP-based environments, cellular hosts SHOULD follow In PCP-based environments, cellular hosts SHOULD follow
[I-D.ietf-pcp-nat64-prefix64] to learn the IPv6 Prefix used [I-D.ietf-pcp-nat64-prefix64] to learn the IPv6 Prefix used
by an upstream PCP-controlled NAT64 device. If PCP is not by an upstream PCP-controlled NAT64 device. If PCP is not
enabled, the cellular host SHOULD implement the method enabled, the cellular host SHOULD implement the method
specified in [I-D.ietf-behave-nat64-discovery-heuristic] to specified in [RFC7050] to retrieve the PREFIX64.
retrieve the PREFIX64.
REQ#13: The cellular host SHOULD implement the Customer Side REQ#13: The cellular host SHOULD implement the Customer Side
Translator (CLAT, [RFC6877]) function which is compliant with Translator (CLAT, [RFC6877]) function which is compliant with
[RFC6052][RFC6145][RFC6146]. [RFC6052][RFC6145][RFC6146].
CLAT function in the cellular host allows for IPv4-only CLAT function in the cellular host allows for IPv4-only
application and IPv4-referals to work on an IPv6-only application and IPv4-referals to work on an IPv6-only
connectivity. CLAT function requires a NAT64 capability connectivity. CLAT function requires a NAT64 capability
[RFC6146] in the core network. [RFC6146] in the core network.
skipping to change at page 12, line 46 skipping to change at page 12, line 43
independent of the underlying IP address family. independent of the underlying IP address family.
This means applications must be IP version agnostic. This means applications must be IP version agnostic.
REQ#33: Applications provided by the mobile device vendor that use REQ#33: Applications provided by the mobile device vendor that use
URIs MUST follow [RFC3986]. For example, SIP applications URIs MUST follow [RFC3986]. For example, SIP applications
MUST follow the correction defined in [RFC5954]. MUST follow the correction defined in [RFC5954].
6. Security Considerations 6. Security Considerations
The security considerations identified in [I-D.ietf-v6ops-rfc3316bis] The security considerations identified in [RFC7066] and [RFC6459] are
and [RFC6459] are to be taken into account. to be taken into account.
Security-related considerations that apply when the cellular device Security-related considerations that apply when the cellular device
provides LAN features are specified in [RFC6092]. provides LAN features are specified in [RFC6092].
7. IANA Considerations 7. IANA Considerations
This document does not require any action from IANA. This document does not require any action from IANA.
8. Acknowledgements 8. Acknowledgements
skipping to change at page 13, line 23 skipping to change at page 13, line 23
Heatley, E. Kline, S. Josefsson, A. Baryun, and J. Woodyatt for the Heatley, E. Kline, S. Josefsson, A. Baryun, and J. Woodyatt for the
discussion in the v6ops mailing list. discussion in the v6ops mailing list.
Special thanks to T. Savolainen and J. Korhonen for the detailed Special thanks to T. Savolainen and J. Korhonen for the detailed
review. review.
9. References 9. References
9.1. Normative References 9.1. Normative References
[I-D.ietf-v6ops-rfc3316bis]
Korhonen, J., Arkko, J., Savolainen, T., and S. Krishnan,
"IPv6 for 3GPP Cellular Hosts", draft-ietf-v6ops-
rfc3316bis-04 (work in progress), September 2013.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998. (IPv6) Specification", RFC 2460, December 1998.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002. June 2002.
skipping to change at page 15, line 16 skipping to change at page 15, line 13
Dual-Stack Hosts", RFC 6555, April 2012. Dual-Stack Hosts", RFC 6555, April 2012.
[RFC6603] Korhonen, J., Savolainen, T., Krishnan, S., and O. Troan, [RFC6603] Korhonen, J., Savolainen, T., Krishnan, S., and O. Troan,
"Prefix Exclude Option for DHCPv6-based Prefix "Prefix Exclude Option for DHCPv6-based Prefix
Delegation", RFC 6603, May 2012. Delegation", RFC 6603, May 2012.
[RFC6724] Thaler, D., Draves, R., Matsumoto, A., and T. Chown, [RFC6724] Thaler, D., Draves, R., Matsumoto, A., and T. Chown,
"Default Address Selection for Internet Protocol Version 6 "Default Address Selection for Internet Protocol Version 6
(IPv6)", RFC 6724, September 2012. (IPv6)", RFC 6724, September 2012.
9.2. Informative References [RFC7066] Korhonen, J., Arkko, J., Savolainen, T., and S. Krishnan,
"IPv6 for Third Generation Partnership Project (3GPP)
Cellular Hosts", RFC 7066, November 2013.
[I-D.ietf-behave-nat64-discovery-heuristic] 9.2. Informative References
Savolainen, T., Korhonen, J., and D. Wing, "Discovery of
the IPv6 Prefix Used for IPv6 Address Synthesis", draft-
ietf-behave-nat64-discovery-heuristic-17 (work in
progress), April 2013.
[I-D.ietf-pcp-nat64-prefix64] [I-D.ietf-pcp-nat64-prefix64]
Boucadair, M., "Learning NAT64 PREFIX64s using PCP", Boucadair, M., "Learning NAT64 PREFIX64s using Port
draft-ietf-pcp-nat64-prefix64-04 (work in progress), July Control Protocol (PCP)", draft-ietf-pcp-nat64-prefix64-06
2013. (work in progress), February 2014.
[I-D.ietf-v6ops-64share] [I-D.ietf-v6ops-64share]
Byrne, C., Drown, D., and V. Ales, "Extending an IPv6 /64 Byrne, C., Drown, D., and V. Ales, "Extending an IPv6 /64
Prefix from a 3GPP Mobile Interface to a LAN link", draft- Prefix from a 3GPP Mobile Interface to a LAN link", draft-
ietf-v6ops-64share-08 (work in progress), July 2013. ietf-v6ops-64share-09 (work in progress), October 2013.
[IR92] GSMA, "IR.92.V4.0 - IMS Profile for Voice and SMS", March [IR92] GSMA, "IR.92.V4.0 - IMS Profile for Voice and SMS", March
2011, <http://www.gsma.com/newsroom/ir-92-v4-0-ims- 2011, <http://www.gsma.com/newsroom/
profile-for-voice-and-sms>. ir-92-v4-0-ims-profile-for-voice-and-sms>.
[RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S. [RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "DNS Security Introduction and Requirements", RFC Rose, "DNS Security Introduction and Requirements", RFC
4033, March 2005. 4033, March 2005.
[RFC4034] Arends, R., Austein, R., Larson, M., Massey, D., and S. [RFC4034] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "Resource Records for the DNS Security Extensions", Rose, "Resource Records for the DNS Security Extensions",
RFC 4034, March 2005. RFC 4034, March 2005.
[RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S. [RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S.
skipping to change at page 16, line 27 skipping to change at page 16, line 18
RFC 6459, January 2012. RFC 6459, January 2012.
[RFC6877] Mawatari, M., Kawashima, M., and C. Byrne, "464XLAT: [RFC6877] Mawatari, M., Kawashima, M., and C. Byrne, "464XLAT:
Combination of Stateful and Stateless Translation", RFC Combination of Stateful and Stateless Translation", RFC
6877, April 2013. 6877, April 2013.
[RFC6887] Wing, D., Cheshire, S., Boucadair, M., Penno, R., and P. [RFC6887] Wing, D., Cheshire, S., Boucadair, M., Penno, R., and P.
Selkirk, "Port Control Protocol (PCP)", RFC 6887, April Selkirk, "Port Control Protocol (PCP)", RFC 6887, April
2013. 2013.
[RFC7050] Savolainen, T., Korhonen, J., and D. Wing, "Discovery of
the IPv6 Prefix Used for IPv6 Address Synthesis", RFC
7050, November 2013.
[TS.23060] [TS.23060]
3GPP, "General Packet Radio Service (GPRS); Service 3GPP, "General Packet Radio Service (GPRS); Service
description; Stage 2", September 2011. description; Stage 2", September 2011.
[TS.23401] [TS.23401]
3GPP, "General Packet Radio Service (GPRS) enhancements 3GPP, "General Packet Radio Service (GPRS) enhancements
for Evolved Universal Terrestrial Radio Access Network for Evolved Universal Terrestrial Radio Access Network
(E-UTRAN) access", September 2011. (E-UTRAN) access", September 2011.
[TS.23402] [TS.23402]
 End of changes. 19 change blocks. 
42 lines changed or deleted 35 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/