Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices
draft-ietf-v6ops-mobile-device-profile-02
V6OPS Working Group D. Binet
Internet-Draft M. Boucadair
Intended status: Informational France Telecom
Expires: October 28, 2013 A. Vizdal
Deutsche Telekom AG
C. Byrne
T-Mobile
G. Chen
China Mobile
April 26, 2013
Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices
draft-ietf-v6ops-mobile-device-profile-02
Abstract
This document specifies an IPv6 profile for 3GPP mobile devices. It
lists the set of features a 3GPP mobile device is to be compliant
with to connect 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
[I-D.ietf-v6ops-rfc3316bis]. 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."
This Internet-Draft will expire on October 28, 2013.
Binet, et al. Expires October 28, 2013 [Page 1]
Internet-Draft IPv6 Profile for Cellular Devices April 2013
Copyright Notice
Copyright (c) 2013 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. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2. Special Language . . . . . . . . . . . . . . . . . . . . 4
2. Connectivity Requirements . . . . . . . . . . . . . . . . . . 5
2.1. WLAN Connectivity Requirements . . . . . . . . . . . . . 8
3. Advanced Requirements . . . . . . . . . . . . . . . . . . . . 9
4. Cellular Devices with LAN Capabilities . . . . . . . . . . . 10
5. APIs & Applications . . . . . . . . . . . . . . . . . . . . . 12
6. Security Considerations . . . . . . . . . . . . . . . . . . . 12
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.1. Normative References . . . . . . . . . . . . . . . . . . 13
9.2. Informative References . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
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 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.
[I-D.ietf-v6ops-rfc3316bis] 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