draft-ietf-v6ops-mobile-device-profile-13.txt | draft-ietf-v6ops-mobile-device-profile-14.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 30, 2015 A. Vizdal | Expires: June 4, 2015 A. Vizdal | |||
Deutsche Telekom AG | Deutsche Telekom AG | |||
G. Chen | G. Chen | |||
China Mobile | China Mobile | |||
N. Heatley | N. Heatley | |||
EE | EE | |||
R. Chandler | R. Chandler | |||
eircom | meteor | eircom | meteor | |||
September 26, 2014 | December 1, 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-13 | draft-ietf-v6ops-mobile-device-profile-14 | |||
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 the IPv6 for Third | connection to IPv6 cellular networks defined in the IPv6 for Third | |||
skipping to change at page 2, line 4 | skipping to change at page 2, line 4 | |||
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 30, 2015. | This Internet-Draft will expire on June 4, 2015. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2014 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 | |||
skipping to change at page 2, line 26 | skipping to change at page 2, line 26 | |||
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 | |||
described in the Simplified BSD License. | described in the Simplified BSD License. | |||
Table of Contents | Table of Contents | |||
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 | 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
1.2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 4 | 1.2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
1.3. Language Considerations . . . . . . . . . . . . . . . . . 4 | 2. Connectivity Recommendations . . . . . . . . . . . . . . . . 4 | |||
2. Connectivity Recommendations . . . . . . . . . . . . . . . . 5 | ||||
2.1. WLAN Connectivity Recommendations . . . . . . . . . . . . 8 | 2.1. WLAN Connectivity Recommendations . . . . . . . . . . . . 8 | |||
3. Advanced Recommendations . . . . . . . . . . . . . . . . . . 9 | 3. Advanced Recommendations . . . . . . . . . . . . . . . . . . 9 | |||
4. Recommendations for Cellular Devices with LAN Capabilities . 12 | 4. Recommendations for Cellular Devices with LAN Capabilities . 11 | |||
5. APIs & Applications Recommendations . . . . . . . . . . . . . 14 | 5. APIs & Applications Recommendations . . . . . . . . . . . . . 14 | |||
6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 | 6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 | |||
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 | 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 | |||
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 | 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 | |||
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 | 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 | |||
9.1. Normative References . . . . . . . . . . . . . . . . . . 15 | 9.1. Normative References . . . . . . . . . . . . . . . . . . 15 | |||
9.2. Informative References . . . . . . . . . . . . . . . . . 16 | 9.2. Informative References . . . . . . . . . . . . . . . . . 16 | |||
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 | |||
skipping to change at page 4, line 48 | skipping to change at page 4, line 48 | |||
sections covering specific functionalities for devices providing some | sections covering specific functionalities for devices providing some | |||
LAN functions (e.g., mobile CPE or broadband dongles). | LAN functions (e.g., mobile CPE or broadband dongles). | |||
The recommendations listed below are valid for both 3GPP GPRS and | The recommendations listed below are valid for both 3GPP GPRS and | |||
3GPP EPS (Evolved Packet System) access. For EPS, PDN-Connection | 3GPP EPS (Evolved Packet System) access. For EPS, PDN-Connection | |||
term is used instead of PDP-Context. | term is used instead of PDP-Context. | |||
This document identifies also some WLAN-related IPv6 recommendations. | This document identifies also some WLAN-related IPv6 recommendations. | |||
Other non-3GPP accesses [TS.23402] are out of scope of this document. | Other non-3GPP accesses [TS.23402] are out of scope of this document. | |||
1.3. Language Considerations | ||||
The key words "must", "must not", "should", "should not", and "may" | ||||
in this document are to be interpreted as described in RFC 2119 | ||||
[RFC2119]. | ||||
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. | ||||
This document uses these keywords only for precision. | ||||
2. Connectivity Recommendations | 2. Connectivity Recommendations | |||
This section identifies the main connectivity recommendations to be | This section identifies the main connectivity recommendations to be | |||
followed by a cellular host to attach to a network using IPv6. Both | followed by a cellular host to attach to a network using IPv6. Both | |||
dual-stack and IPv6-only deployment models are considered. IPv4 | dual-stack and IPv6-only deployment models are considered. IPv4 | |||
service continuity features are listed in this section because these | service continuity features are listed in this section because these | |||
are critical for Operators with an IPv6-only deployment model. | are critical for Operators with an IPv6-only deployment model. | |||
C_REC#1: The cellular host must be compliant with Section 5.9.1 | C_REC#1: The cellular host must be compliant with Section 5.9.1 | |||
(IPv6 Addressing Architecture) and Section 5.8 (ICMPv6 | (IPv6 Addressing Architecture) and Section 5.8 (ICMPv6 | |||
skipping to change at page 14, line 51 | skipping to change at page 14, line 42 | |||
correction defined in [RFC5954]. | correction defined in [RFC5954]. | |||
6. Security Considerations | 6. Security Considerations | |||
The security considerations identified in [RFC7066] and [RFC6459] are | The security considerations identified in [RFC7066] 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]. | |||
Address privacy considerations are discussed in [RFC4941] [RFC7217]. | Address privacy considerations are discussed in A_REC#1 (see | |||
Section 3). Host-based validation of DNSSEC is discussed in A_REC#4 | ||||
(see Section 3). | ||||
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 | |||
Many thanks to C. Byrne, H. Soliman, H. Singh, L. Colliti, T. | Many thanks to C. Byrne, H. Soliman, H. Singh, L. Colliti, T. | |||
Lemon, B. Sarikaya, M. Mawatari, M. Abrahamsson, P. Vickers, V. | Lemon, B. Sarikaya, M. Mawatari, M. Abrahamsson, P. Vickers, V. | |||
Kuarsingh, E. Kline, S. Josefsson, A. Baryun, J. Woodyatt, and T. | Kuarsingh, E. Kline, S. Josefsson, A. Baryun, J. Woodyatt, and T. | |||
skipping to change at page 15, line 27 | skipping to change at page 15, line 23 | |||
their detailed reviews and comments. | their detailed reviews and comments. | |||
9. References | 9. References | |||
9.1. Normative References | 9.1. Normative References | |||
[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/ | 2011, <http://www.gsma.com/newsroom/ | |||
ir-92-v4-0-ims-profile-for-voice-and-sms>. | ir-92-v4-0-ims-profile-for-voice-and-sms>. | |||
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | ||||
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. | |||
[RFC3596] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi, | [RFC3596] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi, | |||
"DNS Extensions to Support IP Version 6", RFC 3596, | "DNS Extensions to Support IP Version 6", RFC 3596, | |||
October 2003. | October 2003. | |||
[RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic | [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic | |||
Host Configuration Protocol (DHCP) version 6", RFC 3633, | Host Configuration Protocol (DHCP) version 6", RFC 3633, | |||
December 2003. | December 2003. | |||
End of changes. 10 change blocks. | ||||
27 lines changed or deleted | 10 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/ |