Internet DRAFT - draft-shen-l2tpext-l2tpv3-yang-model
draft-shen-l2tpext-l2tpv3-yang-model
Internet Engineering Task Force H. Shen
Internet-Draft B. Liu, Ed.
Intended status: Standards Track Huawei Technologies
Expires: June 24, 2016 D. Bannister
M. Abrahamsson
T-Systems
December 22, 2015
A YANG Data Model for L2TPv3 Tunnel
draft-shen-l2tpext-l2tpv3-yang-model-03
Abstract
This document defines a YANG data model for managing L2TPv3 tunnels.
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 June 24, 2016.
Copyright Notice
Copyright (c) 2015 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.
Shen, et al. Expires June 24, 2016 [Page 1]
Internet-Draft ietf l2tpv3 YANG Model December 2015
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language and Terminology . . . . . . . . . . . . 2
3. L2TPv3 YANG Model Overview . . . . . . . . . . . . . . . . . 2
3.1. l2tpv3CtrlInstance . . . . . . . . . . . . . . . . . . . 4
3.2. l2tpv3TunnelInstances . . . . . . . . . . . . . . . . . . 4
4. L2TPv3 YANG Module . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
8. Normative References . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction
This document defines a YANG [RFC6020] [RFC6021] data model for
L2TPv3 tunnels.
2. Requirements Language and Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
[RFC2119] when they appear in ALL CAPS. When these words are not in
ALL CAPS (such as "should" or "Should"), they have their usual
English meanings, and are not to be interpreted as [RFC2119] key
words.
Terminology:
o L2TPv3: Layer Two Tunneling Protocol - Version 3 [RFC3931]
3. L2TPv3 YANG Model Overview
The L2TPv3 YANG model mainly includes two objects. One
(l2tpv3CtrlInstances) is for the L2TPv3 control plane configuration.
The other one (l2tpv3TunnelInstances) is for managing the tunnels.
The overall structure of the model is dicpicted as the following.
Shen, et al. Expires June 24, 2016 [Page 2]
Internet-Draft ietf l2tpv3 YANG Model December 2015
module: ietf-l2tpv3
+--rw l2tpv3CtrlInstances
| +--rw l2tpv3CtrlInstance* [ctrlName]
| +-- rw ctrlName string
| +-- rw hostName string
| +-- rw routerID uint16
| +-- rw rcvWinSize? uint16
| +-- rw helloInterval? uint16
| +-- rw digestType? enum
| +-- rw authenNonce? password
+--rw l2tpv3TunnelInstances
+--rw l2tpv3TunnelInstance* [tunnelName]
+-- rw tunnelName string
+-- rw sourceIfName if:interface-ref
+-- rw sourceIP inet:ip-address
+-- rw destIP inet:ip-address
+-- rw tunnelType enum
| +-- rw static:
| | +-- rw localSessionId? uint32
| | +-- rw remoteSessionId? uint32
| | +-- rw localCookieAutoMode? enum
| | | +-- rw authNone:
| | | +-- rw authPlain:
| | | +-- rw localCookieLength enum
| | | +-- rw localHighCookie hexBinary
| | | +-- rw localLowCookie hexBinary
| | | +-- rw authCipher:
| | | +--rw localCookieCipher password
| | +-- rw remoteCookieAutoMode? enum
| | +-- rw authNone:
| | +-- rw authPlain:
| | +--rw remoteCookieLength enum
| | +--rw remoteHighCookie hexBinary
| | +--rw remoteLowCookie hexBinary
| | +-- rw authCipher:
| | +--rw remoteCookieCipher password
| +-- rw auto:
| +-- rw ctrlName string
| +-- rw encapType enum
+-- ro sendPacket uint64
+-- ro sendByte uint64
+-- ro rcvPacket uint64
+-- ro receiveByte uint64
+-- ro recvDropPacket uint64
+-- ro cookieMisDropPacket uint64
+-- ro state enum
Shen, et al. Expires June 24, 2016 [Page 3]
Internet-Draft ietf l2tpv3 YANG Model December 2015
3.1. l2tpv3CtrlInstance
The l2tpv3CtrlInstance container is a template used for configuring
the control plane of L2TPv3 tunnels. The leaves under the container
are the parameters of the control signaling datagram processing.
One l2tpv3CtrlInstance could be binding to a specific
l2tpv3TunnelInstances through the key "ctrlName" defined in auto mode
of the tunnel. One l2tpv3CtrlInstance could also be shared among
multiple l2tpv3TunnelInstances.
3.2. l2tpv3TunnelInstances
This container is to manage the L2TPv3 tunnels. Two tunnel modes are
supported: one is static tunnel, the other is automatic tunnel.
The basic information of a tunnle contains following elements:
o tunnelName: the identifier of the tunnel
o sourceIfName: the identifier of the loopback interface which is
corresponding with the Persudo-Wire interface of the tunnel
o sourceIP: the IPv4/IPv6 address of the tunnel starting point
o destIP: the IPv4/IPv6 address of the tunnel ending point
The tunnelType node is to distinguish statically configured tunnels
and dynamically configured tunnels. For static tunnels, the relevant
session and cookie information is included. For dynamic tunnels,
only the corresponding control instance is referenced as a key there.
At the end, some stastic elements were defined to represent the
running state of the tunnels.
4. L2TPv3 YANG Module
<CODE BEGINS> file "ietf-l2tpv3@2015-12-23.yang"
module ietf-l2tpv3 {
namespace "urn:ietf:params:xml:ns:yang:ietf-l2tpv3";
prefix "l2tpv3";
import ietf-interfaces {
prefix "if";
}
/* import ietf-yang-types {
prefix yang;
Shen, et al. Expires June 24, 2016 [Page 4]
Internet-Draft ietf l2tpv3 YANG Model December 2015
}
*/
import ietf-inet-types {
prefix "inet";
}
organization "ietf l2tpv3 working group";
contact "shenhaoxing@huawei.com
leo.liubing@huawei.com";
description "The module for implementing l2tpv3 protocol";
revision 2015-12-23 {
description "version-03, lots of grammar revision to pass pyang compiler";
reference "draft-shen-l2tpext-l2tpv3-yang-model-02";
}
typedef hexBinary {
type string {
length "1..127";
pattern "0[xX][0-9a-fA-F]+";
}
description "This is a hexadecimal variable.";
}
typedef password {
type string {
length "1..127";
}
description "This is a dedicated password variable.";
}
container l2tpv3CtrlInstances {
description "This is some general configuration of an l2tpv3 tunnel.";
list l2tpv3CtrlInstance {
key "ctrlName";
description "There could be multiple control instances, each
of them is mapping to a tunnel instance.";
leaf ctrlName {
type "string"{
length "1..19";
}
description "The name of the control instance.";
}
leaf hostName {
Shen, et al. Expires June 24, 2016 [Page 5]
Internet-Draft ietf l2tpv3 YANG Model December 2015
type "string";
mandatory "true";
description "The name of the host.";
}
leaf routerID {
type "uint16";
mandatory "true";
description "Router ID.";
}
leaf rcvWinSize {
type "uint16";
description "Receiving window size.";
}
leaf helloInterval {
type "uint16";
description "Hello interval time.";
}
leaf digestType{
type enumeration {
enum "HMAC_MD5" {
description "HMAC_MD5 algorithm.";
}
enum "HMAC_SHA_1" {
description "HMAC_SHA_1 algorithm.";
}
}
description "Digest algorithm selection.";
}
leaf authenNonce{
type password {
length "1..16";
}
description "The authentication Nonce is in the password format.";
}
}
}
container l2tpv3TunnelInstance {
description "In contrast to the above control instance,
this configuration is regarding to the
tunnel interface itself.";
list l2tpv3TunnelInstance {
Shen, et al. Expires June 24, 2016 [Page 6]
Internet-Draft ietf l2tpv3 YANG Model December 2015
key "tunnelName";
description "There could be multiple tunnel instance.";
leaf tunnelName {
type "string"{
length "1..19";
}
description "The tunnel name.";
}
leaf sourceIfName {
type if:interface-ref;
description
"Interface name as defined by ietf-interfaces";
}
leaf sourceIP {
type inet:ip-address;
mandatory "true";
description "Source IP address.";
}
leaf destIP {
type inet:ip-address;
mandatory "true";
description "Destination IP address.";
}
leaf tnlType {
type enumeration {
enum "static" {
description "Static tunnel.";
}
enum "auto" {
description "Automatic IP address.";
}
}
mandatory "true";
description "Tunnel type.";
}
choice tunnelType {
mandatory "true";
description "Each tunnel can be configured to only one type.";
case static{
when "tnlType = 'static'";
leaf localSessionId {
type uint32 {
range "1..4294967295";
Shen, et al. Expires June 24, 2016 [Page 7]
Internet-Draft ietf l2tpv3 YANG Model December 2015
}
default "4294967295";
description "Local session ID of the tunnel.";
}
leaf remoteSessionId {
type uint32 {
range "1..4294967295";
}
default "4294967295";
description "Remote session ID of the tunnel.";
}
leaf localCookieAutoMode {
type enumeration {
enum "authNone" {
description "No authentication.";
}
enum "authPlain" {
description "Plain text authentication.";
}
enum "authCipher" {
description "Ciper authentication.";
}
}
mandatory "true";
description "Local cookie authentication mode.";
}
choice localCookieMode {
default authNone;
description "Each tunnel can be configured to only one local cookie mode.";
case authNone {
when "localCookieAutoMode = 'authNone'";
}
case authPlain {
when "localCookieAutoMode = 'authPlain'";
leaf localCookieLength {
type enumeration {
enum "4" {
description "4 byte cookie.";
}
enum "8" {
description "8 byte cookie.";
}
Shen, et al. Expires June 24, 2016 [Page 8]
Internet-Draft ietf l2tpv3 YANG Model December 2015
}
default "4";
description "Local cookie length.";
}
leaf localHighCookie {
type "hexBinary"{
length "3..6";
}
description "Local high cookie.";
}
leaf localLowCookie {
type "hexBinary"{
length "3..6";
}
description "Local low cookie.";
}
}
case authCipher {
when "localCookieAutoMode = 'authCipher'";
leaf localCookieCipher {
type password {
length "1..8";
}
description "Local cookie cipher.";
}
}
}
leaf remoteCookieAutoMode {
type enumeration {
enum "authNone" {
description "No authentication.";
}
enum "authPlain" {
description "Plain text authentication.";
}
enum "authCipher" {
description "Plain text authentication.";
}
}
mandatory "true";
description "Remote Cookie AutoMode.";
}
choice remoteCookieMode {
default authNone;
Shen, et al. Expires June 24, 2016 [Page 9]
Internet-Draft ietf l2tpv3 YANG Model December 2015
description "Choosing one remote cookie mode.";
case authNone {
when "remoteCookieAutoMode = 'authNone'";
}
case authPlain {
when "remoteCookieAutoMode = 'authPlain'";
leaf remoteCookieLength {
type enumeration {
enum "4" {
description "Cookie length is 4 byte.";
}
enum "8" {
description "Cookie length is 4 byte.";
}
}
default "4";
description "Remote Cookie length.";
}
leaf remoteHighCookie {
type "hexBinary"{
length "3..6";
}
description "Remote high Cookie.";
}
leaf remoteLowCookie {
type "hexBinary"{
length "3..6";
}
description "Remote low Cookie.";
}
}
case authCipher {
when "remoteCookieAutoMode = 'authCipher'";
leaf remoteCookieCipher {
type password {
length "1..8";
}
description "Remote Cookie cipher.";
}
}
}
}
case auto{
when "tnlType = 'auto'";
Shen, et al. Expires June 24, 2016 [Page 10]
Internet-Draft ietf l2tpv3 YANG Model December 2015
leaf ctrlName {
type string{
length "1..19";
}
mandatory "true";
description "Relevant control instance name.";
}
leaf encapType {
type enumeration
{
enum "HDLC" {
description "HDLC encapsulation.";
}
enum "Ethernet" {
description "Ethernet encapsulation.";
}
enum "VLAN" {
description "VLAN encapsulation.";
}
enum "ATM" {
description "ATM encapsulation.";
}
}
mandatory "true";
description "Encapsulation type.";
}
}
}
leaf sendPacket {
type "uint64";
config "false";
description "Sent packet count.";
}
leaf sendByte {
type "uint64";
config "false";
description "Sent byte count.";
}
leaf rcvPacket {
type "uint64";
config "false";
description "Received packet count.";
Shen, et al. Expires June 24, 2016 [Page 11]
Internet-Draft ietf l2tpv3 YANG Model December 2015
}
leaf receiveByte {
type "uint64";
config "false";
description "Received byte count.";
}
leaf recvDropPacket {
type "uint64";
config "false";
description "Drop packet count among the received packets.";
}
leaf cookieMisDropPacket {
type "uint64";
config "false";
description "Cookie mis-drop packet count.";
}
leaf state {
type enumeration {
enum "down" {
value "0";
description "down:";
}
enum "up" {
value "1";
description "up:";
}
}
config "false";
description "Tunnel running state.";
}
}
}
}
<CODE ENDS>
5. Security Considerations
TBD.
6. IANA Considerations
This draft does not request any IANA action.
Shen, et al. Expires June 24, 2016 [Page 12]
Internet-Draft ietf l2tpv3 YANG Model December 2015
7. Acknowledgements
Gang Yan made significant contribution to design the YANG model.
Valuable comment was received from Xianping Zhang to improve the
draft.
This document was produced using the xml2rfc tool [RFC2629].
8. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
DOI 10.17487/RFC2629, June 1999,
<http://www.rfc-editor.org/info/rfc2629>.
[RFC3931] Lau, J., Ed., Townsley, M., Ed., and I. Goyret, Ed.,
"Layer Two Tunneling Protocol - Version 3 (L2TPv3)",
RFC 3931, DOI 10.17487/RFC3931, March 2005,
<http://www.rfc-editor.org/info/rfc3931>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<http://www.rfc-editor.org/info/rfc6020>.
[RFC6021] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6021, DOI 10.17487/RFC6021, October 2010,
<http://www.rfc-editor.org/info/rfc6021>.
Authors' Addresses
Haoxing Shen
Huawei Technologies
Huawei Nanjing R&D Center
101 Software Avenue, Yuhua District, Nanjing, Jiangsu, 210012
P.R. China
Email: shenhaoxing@huawei.com
Shen, et al. Expires June 24, 2016 [Page 13]
Internet-Draft ietf l2tpv3 YANG Model December 2015
Bing Liu
Huawei Technologies
Q14, Huawei Campus, No.156 Beiqing Road
Hai-Dian District, Beijing, 100095
P.R. China
Email: leo.liubing@huawei.com
David Bannister
T-Systems
Email: David.Bannister@t-systems.com
Mikael Abrahamsson
T-Systems
Stockholm
Sweden
Email: mikael.abrahamsson@t-systems.se
Shen, et al. Expires June 24, 2016 [Page 14]
