Internet Engineering Task Force T. Yang
Internet-Draft L. Li
Intended status: Informational Q. Ma
Expires: April 24, 2014 China Mobile
Oct 21, 2013
IPv6 Transition Technologies Selection using DHCP/DHCPv6
draft-yang-v6ops-ipv6tran-select-02
Abstract
Nowadays, many IPv6 transition technologies has been proposed, such
as Dual-Stack, DS-Lite, 6rd and so on. An CPE may support some of
them instead of only one. But ISPs usually deploy just an unique
transition technology in an area, for example, under a BRAS/SR or in
a MAN. So they must control all the CPEs to ues the exact transition
tech through the CPEs' management system or configuring them before
issuing to the customers. Another question is that if subscriber buy
a new CPE from supermarket to substitute the one received from the
ISP, he may not access internet because of the wrong configuration.
To solve these problems,this document defines a new DHCP/DHCPv6
option named TRAN_TYPE which can control CPEs to select the
appropriate IPv6 transition technology which ISP deployed instend of
the CPEs' default configration. This method can also solve the
configurating problem when various CPEs work together without a
uniform configuration in advance.
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 April 24, 2014.
Copyright NoticeYang, et al. Expires April 24, 2014 [Page 1]Internet-Draft IPv6tran-select Oct 2013
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3
3. DHCP Solution . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. DHCPv6 Solution . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Other questions . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
8. Refrences . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
Yang, et al. Expires April 24, 2014 [Page 2]Internet-Draft IPv6tran-select Oct 20131. Introduction
Nowadays, many IPv6 transitioning technologies has been proposed such
as Dual-Stack, DS-Lite, 6rd and so on. Each of them proposes
individual requirment to the CPEs. To promote the competitive
ability of products,the CPE manufacturers certainly will try to
support more technologies as much as possible. Meanwhile, the
operators tend to use single or less technologies. Moreover, users
can buy and use their own equipments instead of using the one which
operator gives them, that will bring the diversity of CPEs.
Assume that an operator uses one transitioning strategy in its
network. There are two ways to make the CPEs available. The first
one is to make a pre-configuration for each CPE in advance. But,
when the users modify the configuration or change to their own
equipment, the connection will fail. The Second method is to deploy
datatracker.ietf.org