An Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices
draft-ietf-v6ops-mobile-device-profile-13
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Active Internet-Draft (v6ops WG) | |
| Authors | David Binet , Mohamed Boucadair , Vizdal Ales , Gang Chen , Nick Heatley , Ross Chandler | ||
| Last updated | 2014-10-30 (latest revision 2014-09-26) | ||
| Replaces | draft-binet-v6ops-cellular-host-requirements | ||
| Stream | IETF | ||
| Intended RFC status | Informational | ||
| Formats | pdf htmlized (tools) htmlized bibtex | ||
| Reviews | |||
| IETF conflict review | conflict-review-ietf-v6ops-mobile-device-profile | ||
| Stream | WG state | WG Document | |
| Document shepherd | Fred Baker | ||
| Shepherd write-up | Show (last changed 2014-09-22) | ||
| IESG | IESG state | IESG Evaluation::AD Followup | |
| Consensus Boilerplate | Yes | ||
| Telechat date |
Needs a YES. |
||
| Responsible AD | Joel Jaeggli | ||
| Send notices to | v6ops-chairs@tools.ietf.org, draft-ietf-v6ops-mobile-device-profile@tools.ietf.org | ||
| IANA | IANA review state | IANA OK - No Actions Needed | |
V6OPS Working Group D. Binet
Internet-Draft M. Boucadair
Intended status: Informational France Telecom
Expires: March 30, 2015 A. Vizdal
Deutsche Telekom AG
G. Chen
China Mobile
N. Heatley
EE
R. Chandler
eircom | meteor
September 26, 2014
An Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices
draft-ietf-v6ops-mobile-device-profile-13
Abstract
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).
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.
Both hosts and devices with capability to share their WAN (Wide Area
Network) connectivity are in scope.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
Binet, et al. Expires March 30, 2015 [Page 1]
Internet-Draft IPv6 Profile for Cellular Devices September 2014
This Internet-Draft will expire on March 30, 2015.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
1.2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3. Language Considerations . . . . . . . . . . . . . . . . . 4
2. Connectivity Recommendations . . . . . . . . . . . . . . . . 5
2.1. WLAN Connectivity Recommendations . . . . . . . . . . . . 8
3. Advanced Recommendations . . . . . . . . . . . . . . . . . . 9
4. Recommendations for Cellular Devices with LAN Capabilities . 12
5. APIs & Applications Recommendations . . . . . . . . . . . . . 14
6. Security Considerations . . . . . . . . . . . . . . . . . . . 14
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . 16
1. Introduction
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 [RFC2460] 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.
[RFC7066] 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.
Show full document text