Internet DRAFT - draft-zhou-netmod-openv6-transition-cfg
draft-zhou-netmod-openv6-transition-cfg
Internet Engineering Task Force C. Zhou
Internet-Draft Huawei Technologies
Intended status: Standards Track Q. Sun
Expires: April 24, 2014 China Telecom
October 21, 2013
A YANG Data Model for Open IPv6 Transition
draft-zhou-netmod-openv6-transition-cfg-00
Abstract
During the transition from IPv4 to IPv6, there are many kinds of
transition methods and scenarios that have been or are currently
being defined in IETF, e.g., DS-Lite, Lw4over6, MAP-E, 4rd, 6rd and
etc. Carriers have to select and determine their transition ways
among all of these techniques, which brings slow transition to IPv6.
Currently, we face two main challenges in IPv6 transition: the legacy
equipment does not support multiple IPv6 transition technologies at
the same time and there are not enough native IPv6 applications.
This document describes an open IPv6 YANG [RFC6020] data model which
serves as a framework for configuring and managing an IPv6 service to
provide a low-cost and unified way to IPv6 transition.
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 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
Zhou & Sun Expires April 24, 2014 [Page 1]
Internet-Draft A YANG Data Model for Open IPv6 Transition October 2013
(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. Requirements Language . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. The Design of the Open IPv6 Transition Data Model . . . . . . 3
4.1. Flow Table . . . . . . . . . . . . . . . . . . . . . . . 4
4.2. Resource . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . 5
8. Normative References . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
Each IPv6 transition technology has its own specific characteristics.
In order to support a specific IPv6 transition scheme and not need to
upgrade the devices, we propose two elements for OSS to configure the
IPv6 service related parameters: the resource template and the flow
table template. These two elements together define the so-called
open IPv6 data model, which is proposed as a basis for the
development of data models for configuration and management of the
specific IPv6 transition technology. This data model could
accommodate existing and future IPv6 transition schemes.
1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
2. Terminology
The following terms are used in this document:
o Resource template: the template for IP pool and port/port set;
Zhou & Sun Expires April 24, 2014 [Page 2]
Internet-Draft A YANG Data Model for Open IPv6 Transition October 2013
o Flow table template: the template for various transition
technologies, described by NAT and/or tunnel.
3. Objectives
The initial design of the open IPv6 data model was driven by the
following objectives:
o The data model should support the particular technology (any of
the v4-v6 transition technology). The resource template and the
flow table template should be general templates suitable for all
the transition schemes;
o The users/applications should be able to decide for themselves
when and how to start the IPv6 transition;
o The data model is generic and protocol-independent for packets and
flow-tables interaction between network devices and applications.
o Provides the management functions (e.g.,OSS) for the applications
to configure and manage the installed modules in the network
devices.
4. The Design of the Open IPv6 Transition Data Model
The open IPv6 transition data model consists of two YANG modules.
The first module, "flow table", defines the action (tunnel and NAT)
of a specific transiton technology. The other module, "resource",
defines the general IP prefix and port set/mapping rules for a
specific transition technology. Figure 1 show abridged views of the
configuration and operational state data hierarchies.
+--rw ipv6-transition
+--rw flow table [name]
| +--rw name string
| +--rw description? string
| +--rw enabled? boolean
| +--rw tunnel
| | +--rw name string
| | +--rw description? string
| | +--rw enabled? boolean
| | +--rw type identityref
| | +--rw inner-ip-address-src inet:ip-address
| | +--rw inner-ip-address-dst inet:ip-address
| | +--rw outer-ip-address-src inet:ip-address
| | +--rw outer-ip-address-dst inet:ip-address
| +--rw translation
| +--rw name string
Zhou & Sun Expires April 24, 2014 [Page 3]
Internet-Draft A YANG Data Model for Open IPv6 Transition October 2013
| +--rw description? string
| +--rw enabled? boolean
| +--rw type identityref
| +--rw proto? string
| +--rw inner-ip-address inet:ip-address
| +--rw outer-ip-addres inet:ip-address
| +--rw inner-port? inet:port-number
| +--rw outer-port? inet:port-number
+--rw resource [name]
+--rw name
+--rw description? string
+--rw enabled? boolean
+--rw ip prefix inet:ip-prefix
|
+--rw port set inet:port-set
Figure 1: Open IPv6 Configuration data hierarchy.
4.1. Flow Table
The flow table element defines the two basic components of a specific
IPv6 transition technology: tunnel and translation.
The main attributes of the tunnel are explained as below:
o "inner-ip-address-src": the source ip address of a packet or inner
source ip address when the packet type is IP-in-IP tunnel;
o "inner-ip-address-dst":the dstination ip address of a packet or
inner dstination ip address when the packet type is IP-in-IP
tunnel;
o "outer-ip-address-src": the source ip address of a packet or outer
source ip address when the packet type is IP-in-IP tunnel;
o "outer-ip-address-dst": the destination ip address of a packet or
outer destination ip address when the packet type is IP-in-IP
tunnel.
The IP address could be IPv4 or IPv6 dependending on the
technologies.
The main attributes of the translation are explained as below:
o "inner-ip-address": the source ip address of a packet;
o "outer-ip-addresss":the dstination ip address of a packet;
Zhou & Sun Expires April 24, 2014 [Page 4]
Internet-Draft A YANG Data Model for Open IPv6 Transition October 2013
o "inner-port": the source port of a packet;
o "outer-port": the destination port of a packet.
The IP address could be IPv4 or IPv6 depending on the specific
technologies.
4.2. Resource
The resource element defines the general IP pool and the port set of
the specific transition technology if the ipv4 address sharing
mechanism is adopted.
5. Acknowledgements
TBD
6. IANA Considerations
7. Security Considerations
To come.
8. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the
Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010.
[RFC6431] Boucadair, M., Levis, P., Bajko, G., Savolainen, T., and
T. Tsou, "Huawei Port Range Configuration Options for PPP
IP Control Protocol (IPCP)", RFC 6431, November 2011.
Authors' Addresses
Cathy Zhou
Huawei Technologies
Bantian, Longgang District
Shenzhen 518129
P.R. China
Email: cathy.zhou@huawei.com
Zhou & Sun Expires April 24, 2014 [Page 5]
Internet-Draft A YANG Data Model for Open IPv6 Transition October 2013
Qiong Sun
China Telecom
P.R.China
Phone: 86 10 58552936
Email: sunqiong@ctbri.com.cn
Zhou & Sun Expires April 24, 2014 [Page 6]
