Network Working Group Y. Zha Internet Draft Huawei Technologies Intended status: Standard Track D. Zhang Expires: April 2016 Y. Cheng, Ed China Unicom M. Klyus NetCracker October 19, 2015 Layer 3 VPN Service deployment in ONOS draft-zha-l3sm-l3vpn-onos-deployment-00 Abstract This document defines a YANG model that is used to deliver layer 3 VPN service in ONOS project which is on the controller level. L3SM is focused on the service model which is on the orchestration level to help interaction between customers and network operators and also can be input to automated control and configuration applications. ONOS runs as an open source project for fast deployment. Use L3VPN service model defined in L3SM and deploy L3VPN service in ONOS project can be one step further. On the other hand, push real deployment in ONOS back to IETF is also beneficial. 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), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html This Internet-Draft will expire on Expires April 19, 2016. Zha, et al. Expires April 19, 2016 [Page 1] Internet-Draft L3VPN Deployment in ONOS October 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 2. Conventions used in this document ............................3 3. L3VPN Deployment in ONOS .....................................3 3.1. ONOS-based SDN Controller ...............................3 3.2. L3VPN Deployment in ONOS-based SDN Controller ...........4 4. L3VPN Data Model .............................................5 4.1. Design of the Data Model ................................5 4.1.1. VPN service topology ...............................6 4.1.2. L3 VPN access information ..........................6 4.1.3. Protect policy .....................................6 4.1.4. Tunnel service .....................................6 4.2. L3VPN YANG Model .......................................12 5. Security Considerations .....................................36 6. IANA Considerations .........................................36 7. Contributors and Acknowledgments ............................36 8. References ..................................................36 8.1. Normative References ...................................36 8.2. Informative References .................................37 1. Introduction ONOS, Open Networking Operating System, is an open source project that provides a platform for a vendor to build their controller through adding services/applications on top of ONOS. One of the principal motivations of ONOS is to facilitate service deployment, such as VPN service. [L3VPN] in L3SM WG defines a YANG model for layer 3 VPN service to deliver overall service. The description of the L3 service is more focused on the high level, orchestration level, with little information to guide the real configuration. A Zha, et al. Expires April 19, 2016 [Page 2] Internet-Draft L3VPN Deployment in ONOS October 2015 specific configuration related model that is especially working on controller level is necessary to fulfill the fast VPN provisioning. This document introduces YANG [RFC6020] [RFC6021] data models for L3VPN configuration in ONOS. Such models can facilitate the standardization for the interface of ONOS, as they are compatible to a variety of protocols such as NETCONF [RFC6241] and [RESTCONF]. Please note that in the context of ONOS, the term "application" refers to an operational and management applications employed, and possibly implemented, by an operator. 2. Conventions used in this document 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 [RFC2119]. In this document, these words will appear with that interpretation only when in ALL CAPS. Lower case uses of these words are not to be interpreted as carrying [RFC2119] significance. 3. L3VPN Deployment in ONOS In this section, a brief description of ONOS project as well as the L3 VPN deployment demo [ONOS-L3VPN] will be provided and relationship with L3SM will be addressed from an implementer's point of view. 3.1. ONOS-based SDN Controller ONOS is an open source project that allows users to build their own SDN controller on top of it by adding service or applications. Without building everything from scratch, ONOS platform delivers fast and agile service provisioning. First of all, ONOS has abstracted southbound common API allows single controller to control the devices from different vendors. The southbound details with diversified devices and protocols have been masked so as to support multi-vendor environment. Also this enables controller to control both OF and legacy network devices. Secondly, ONOS is architected as logically centralized but physically distributed clustering system. This design aims to offload users' development resource on performance and scalability. Lastly, Services provided by ONOS core are designed and implemented as a set of collaborating subsystems. Network control applications can use those services through the NB API. Zha, et al. Expires April 19, 2016 [Page 3] Internet-Draft L3VPN Deployment in ONOS October 2015 3.2. L3VPN Deployment in ONOS-based SDN Controller Deployment of L3VPN in ONOS is based on the requirement that fast and agile VPN provisioning. Using the ONOS given services as collaborating subsystems is the best way to avoid time consuming manual configurations. The overall architecture of L3 VPN deployment in ONOS is shown as figure 1. +-----------------------------------------------------------------+ | User's Application | | +----------+ +----------------------+ +---------+ | | | Topology | | L3 VPN service model | | PCE | | | +----------+ +----------------------+ +---------+ | +--------------+--------------------------------+-----------------+ | RESTful API | +----+----------------------+----+ C C C C \ / \ / Northbound API +-----------------------------------------------------------------+ | ONOS Core | | +----------+ +-------------------+ +-----------+ | | | Topology | | Resource manager | | Flow Rule | | | +----------+ | (MPLS label) | | extension | | | +-------------------+ +-----------+ | | +-------------------+ | | | Tunnel manager | | | +-------------------+ | +--------------+--------------------------------+-----------------+ / \ / \ / \ / \ / \ / \ Southbound API C C C C C C C C C C C C \ / \ / \ / \ / \ / \ / NE1 NE2 NEn NE1 NE2 NEn Figure 1 L3VPN in ONOS Architecture C: Communications More specifically, the deployment of L3VPN on ONOS platform is consisted of following implementations. Zha, et al. Expires April 19, 2016 [Page 4] Internet-Draft L3VPN Deployment in ONOS October 2015 1. A user defined application implemented as an external application running on the top of ONOS. In this project, user provides L3VPN service, PCE (Path Calculation Engine) engine, interface to Portal software, etc. 2. The application keeps a snapshot of global view and network resource availability, which is used by PCE for path calculation in the project. 3. Use Producer-Consumer model to provision VPN. In this P-C model, Producer and Consumer are separate applications. Producer provisions network that for Consumer to use. In this project, Producer provisions MPLS tunnel. Consumer is L3VPN service that uses the tunnel. 4. ONOS core is enhanced with WAN service, such as MPLS Label Manager (support global and local label management), Tunnel Manager, and FlowRule extension. 5. South bound provider allows ONOS to talk with both legacy and OF devices and control both Legacy and OF environment/requirement. 4. L3VPN Data Model This section is mainly focused on the L3VPN service model as mentioned in pervious section about implementation. 4.1. Design of the Data Model The L3SM is focused on the overall service to propose an abstracted interface to manage configuration of components of a L3VPN service. As shown in the document [L3VPN] section 4, it is service oriented and worked on the orchestration layer which does not specify network configuration. The data model in this document works on controller layer to guide the configuration by utilizing the given services in ONOS Core. The L3VPN service model in [L3VPN] is constructed with two containers, one with some generic VPN information and the other one called site which is composed of a customer edge router (CE) attached to a provider edge router (PE). Meanwhile, the VPN service is sites based and can be treated as connections among multiple sites. However, the L3VPN service in this ONOS project is based on tunnel as mentioned earlier. The L3VPN data model here does not contradict with the one in [L3VPN] since the latter one is working the orchestration level and not designed for specific implementation. Using the [L3VPN] as a reference and use some of Zha, et al. Expires April 19, 2016 [Page 5] Internet-Draft L3VPN Deployment in ONOS October 2015 its parameters with specific configuration information to design the data model for this deployment in ONOS is primary goal of this document. The YANG model in this document has two containers, one follows the vpn-svc in [L3VPN] to specify the parameter for L3VPN service and utilize the given service, and the latter one is to define the service path which contains ingress/egress information. Note that this configuration model utilizes only part of the parameters defined in the generic service model in [L3VPN] to deploy a VPN service. The key information such as "connection", "qos-policy", "connection", "protect-policy" and "oam-policy" all come from [L3VPN] The top level design of the data model is shown in the following YANG tree. 4.1.1. VPN service topology The type of topology of the VPN is required for configuration. Current version supports: hub and spoke (where hubs can exchange traffic), full-mesh. New topologies could be added by augmentation. The default service topology is "full-mesh". 4.1.2. L3 VPN access information The access information of the VPN contains "role" information to denote role of the lsp that it is a master, slave, hub or spoke. Also the qos information is provided with qos policy. Another important container here is the "connection" to define the ip connection between PE and CE. Note that [L3VPN] has "ip-connection" container defined in "sites", however the L3 VPN here is not site based so the connection information is defined as general parameters in access information. Following the structure in [L3VPN], the "connection" has ip address and the most important thing, "protocols" to connect PE and CE, such as OSPF, BGP or static. 4.1.3. Protect policy Protect policy defines the protect type as well as revertive type. 4.1.4. Tunnel service The "tunnel-service" is the most important container in vpn-svc. It tells the ONOS core to utilize the tunnel service with information on "tunnel-mode" and oam policy. Generally, this is very similar to the "sites" container in [L3VPN]. Zha, et al. Expires April 19, 2016 [Page 6] Internet-Draft L3VPN Deployment in ONOS October 2015 module: sd-onos-service-l3vpn +--rw service +--rw l3vpn-cfg | +--rw vpn-cfg* [name] | +--rw name string | +--rw id uint32 | +--rw user-label? string | +--rw parent-ncd-id? string | +--rw admin-status? types:admin-status | +--rw operate-status? types:operate-status | +--rw service-topology? enumeration | +--rw acess-information | | +--rw access-circuit* [id] | | +--rw id string | | +--ro name? string | | +--rw ne-id string | | +--rw ltp-id string | | +--rw admin-status? types:admin-status | | +--rw operate-status? types:operate-status | | +--rw l2-access | | | +--rw access-type enumeration | | | +--rw dot1q-vlan-bitmap string | | | +--rw qinq-svlan-bitmap string | | | +--rw qinq-cvlan-bitmap string | | | +--rw access-action enumeration | | | +--rw action-vlan-id? int32 | | +--rw role? enumeration | | +--rw qos-policy | | | +--rw qos-if-cars | | | +--rw qos-if-car* [direction] | | | +--rw direction enumeration | | | +--rw cir? int32 | | | +--rw pir? int32 | | | +--rw cbs? int32 | | | +--rw pbs? int32 | | +--rw connection | | +--rw ip-address? inet:ip-address | | +--rw mask-length? int32 | | +--rw protocols? enumeration | | +--rw static-routes | | +--rw static-route* [ip-prefix mask-length] | | +--rw ip-prefix inet:ipv4-address | | +--rw mask-length uint32 | | +--rw next-hop? inet:ipv4-address | | +--rw preference? uint32 | +--rw protect-policy | | +--rw protect-type? enumeration Zha, et al. Expires April 19, 2016 [Page 7] Internet-Draft L3VPN Deployment in ONOS October 2015 | | +--rw revertive-type? enumeration | | +--rw wtr? uint32 | +--rw tunnel-service | +--rw signaling-type? enumeration | +--rw tunnel-mode? enumeration | +--rw protect-policy | | +--rw protect-type? enumeration | | +--rw revertive-type? enumeration | | +--rw wtr? uint32 | +--rw oam-policy | | +--rw detect-type? enumeration | | +--rw bfd-detect-para | | +--rw ingress-discriminator? int32 | | +--rw egress-discriminator? int32 | | +--rw tx-interval? int32 | | +--rw rx-interval? int32 | | +--rw detect-interval? int32 | +--rw latency? int32 +--rw service-paths +--rw service-path* [service-id source-ne-id source-ac-id destination-ne-id destination-ac-id] +--rw service-id string +--rw source-ne-id string +--rw source-ac-id string +--rw destination-ne-id string +--rw destination-ac-id string +--rw path-lists +--rw path-list* [path-layer path-role] +--rw path-layer enumeration +--rw path-role enumeration +--rw paths +--rw path* [ne-id] +--rw ne-id string +--rw ingress-ltp-id? string +--rw backward-peer-id? string +--rw egress-ltp-id? string +--rw forward-peer-id? string rpcs: +---x create-l3vpn-instance | +--ro input | +--ro l3vpn-instance | +--ro name string | +--ro id uint32 | +--ro user-label? string | +--ro parent-ncd-id? string | +--ro admin-status? types:admin-status | +--ro operate-status? types:operate-status Zha, et al. Expires April 19, 2016 [Page 8] Internet-Draft L3VPN Deployment in ONOS October 2015 | +--ro service-topology? enumeration | +--ro acess-information | | +--ro access-circuit* [id] | | +--ro id string | | +--ro name? string | | +--ro ne-id string | | +--ro ltp-id string | | +--ro admin-status? types:admin-status | | +--ro operate-status? types:operate-status | | +--ro l2-access | | | +--ro access-type enumeration | | | +--ro dot1q-vlan-bitmap string | | | +--ro qinq-svlan-bitmap string | | | +--ro qinq-cvlan-bitmap string | | | +--ro access-action enumeration | | | +--ro action-vlan-id? int32 | | +--ro role? enumeration | | +--ro qos-policy | | | +--ro qos-if-cars | | | +--ro qos-if-car* [direction] | | | +--ro direction enumeration | | | +--ro cir? int32 | | | +--ro pir? int32 | | | +--ro cbs? int32 | | | +--ro pbs? int32 | | +--ro connection | | +--ro ip-address? inet:ip-address | | +--ro mask-length? int32 | | +--ro protocols? enumeration | | +--ro static-routes | | +--ro static-route* [ip-prefix mask-length] | | +--ro ip-prefix inet:ipv4-address | | +--ro mask-length uint32 | | +--ro next-hop? inet:ipv4-address | | +--ro preference? uint32 | +--ro protect-policy | | +--ro protect-type? enumeration | | +--ro revertive-type? enumeration | | +--ro wtr? uint32 | +--ro tunnel-service | +--ro signaling-type? enumeration | +--ro tunnel-mode? enumeration | +--ro protect-policy | | +--ro protect-type? enumeration | | +--ro revertive-type? enumeration | | +--ro wtr? uint32 | +--ro oam-policy Zha, et al. Expires April 19, 2016 [Page 9] Internet-Draft L3VPN Deployment in ONOS October 2015 | | +--ro detect-type? enumeration | | +--ro bfd-detect-para | | +--ro ingress-discriminator? int32 | | +--ro egress-discriminator? int32 | | +--ro tx-interval? int32 | | +--ro rx-interval? int32 | | +--ro detect-interval? int32 | +--ro latency? int32 +---x delete-l3vpn-instance | +--ro input | +--ro l3vpn-id? string +---x close-l3vpn | +--ro input | +--ro l3vpn-id? string | +--ro ac-status | +--ro acs* [id] | +--ro id string | +--ro admin-status? types:admin-status +---x modify-l3vpn-instance-basic | +--ro input | +--ro l3vpn-id? string | +--ro user-label? string +---x modify-l3vpn-instance-ac-qos | +--ro input | +--ro l3vpn-id? string | +--ro ac-qos | +--ro acs* [id] | +--ro id string | +--ro qos-policy | +--ro qos-if-cars | +--ro qos-if-car* [direction] | +--ro direction enumeration | +--ro cir? int32 | +--ro pir? int32 | +--ro cbs? int32 | +--ro pbs? int32 +---x modify-l3vpn-instance-connection | +--ro input | +--ro l3vpn-id? string | +--ro ac-connection | +--ro acs* | +--ro id? string | +--ro connection | +--ro ip-address? inet:ip-address | +--ro mask-length? int32 | +--ro protocols? enumeration | +--ro static-routes Zha, et al. Expires April 19, 2016 [Page 10] Internet-Draft L3VPN Deployment in ONOS October 2015 | +--ro static-route* [ip-prefix mask-length] | +--ro ip-prefix inet:ipv4-address | +--ro mask-length uint32 | +--ro next-hop? inet:ipv4-address | +--ro preference? uint32 +---x inquire-l3vpn-instance-work-path +--ro input | +--ro service-id? string | +--ro ingress-ne-id? string | +--ro destination-ne-id? string | +--ro ingress-ac-id? string | +--ro destination-ac-id? string | +--ro path-layer? string | +--ro path-role? string +--ro output +--ro service-path +--ro service-id? string +--ro ingress-ne-id? string +--ro destination-ne-id? string +--ro ingress-ac-id? string +--ro destination-ac-id? string +--ro path-layer? string +--ro path-role? string +--ro path-list* [ne-id] +--ro ne-id string +--ro ingress-ltp-id? string +--ro backward-peer-id? string +--ro egress-ltp-id? string +--ro forward-peer-id? string Zha, et al. Expires April 19, 2016 [Page 11] Internet-Draft L3VPN Deployment in ONOS October 2015 4.2. L3VPN YANG Model module sd-onos-common-types { namespace "urn:onos:types"; prefix types ; import ietf-inet-types{ prefix inet; } import ietf-yang-types { prefix yang-types; } organization ""; contact ""; revision "2015-10-14" {description "revised revision.";} typedef admin-status { type enumeration { enum admin-up { value 0 ; description "admin up, the operate-status is depend on the real running status ." ; } enum admin-down { value 1 ; description "admin down,the operate-status is forced to down no matter what the real status is" ; } enum config-up { value 2 ; description "the operate-status is forced to up no matter what the real status is." ; } } default admin-up; } typedef notification-status { type enumeration { enum up { value 0 ; description "up." ; } enum down { Zha, et al. Expires April 19, 2016 [Page 12] Internet-Draft L3VPN Deployment in ONOS October 2015 value 1 ; description "down." ; } } default up; } typedef notification-type { type enumeration { enum ne{ value 0 ; description "ncd change." ; } enum link{ value 1 ; description "link change." ; } enum ltp{ value 2 ; description "ltp change." ; } } default ltp; } typedef operate-status { type enumeration { enum operate-up { value 0 ; description "operate up." ; } enum operate-down { value 1 ; description "operate down." ; } } default operate-up; } grouping command-result { container command-result { leaf result { description "1 : success, 2 : failed, 3 : partly failed" ; type int8; } container success-resources { Zha, et al. Expires April 19, 2016 [Page 13] Internet-Draft L3VPN Deployment in ONOS October 2015 list success-resource-list { leaf resource-id { type string; } } } container failed-resources { list failed-resource-list { leaf resource-id { type string; } leaf error-code { type string; } } } } } } module sd-onos-service-types { namespace "urn:onos:service-types"; prefix service-types ; import ietf-inet-types {prefix inet; } import sd-onos-common-types {prefix types; revision-date "2015-10-14";} organization ""; contact ""; revision "2015-10-14" {description "revised revision.";} typedef exp { type enumeration { enum BE { value 0 ; description "BE." ; } enum AF1 { value 1 ; description "AF1." ; } enum AF2 { value 2 ; description "AF2." ; } enum AF3 { Zha, et al. Expires April 19, 2016 [Page 14] Internet-Draft L3VPN Deployment in ONOS October 2015 value 3 ; description "AF3." ; } enum AF4 { value 4 ; description "AF4." ; } enum EF { value 5 ; description "EF." ; } enum CS6 { value 6 ; description "CS6." ; } enum CS7 { value 7 ; description "CS7." ; } } default CS7; } typedef pw-role{ type enumeration { enum normal{ value 0 ; description "normal." ; } enum master { value 1 ; description "master." ; } enum slave { value 2 ; description "slave." ; } enum DNI-PW { value 3 ; description "DNI PW." ; } } default normal; } grouping qos-if-car { description "qos parameter." ; Zha, et al. Expires April 19, 2016 [Page 15] Internet-Draft L3VPN Deployment in ONOS October 2015 leaf direction { description "qos for interface car" ; type enumeration { enum inbound{ value 0 ; description "inbound." ; } enum outbound { value 1 ; description "outbound." ; } } } leaf cir { description "forward CIR. unit:Kbps" ; type int32; } leaf pir { description "forward PIR. unit:Kbps" ; type int32; } leaf cbs { description "forward CBS. unit:Kbps" ; type int32; } leaf pbs { description "forward PBS. unit:Kbps" ; type int32; } } grouping protect-policy { leaf protect-type { description "protection type" ; type enumeration { enum unprotected { value 0 ; description "unprotected." ; } enum protected { value 1 ; description "protection." ; } } default unprotected ; Zha, et al. Expires April 19, 2016 [Page 16] Internet-Draft L3VPN Deployment in ONOS October 2015 } leaf revertive-type { description "revertive mode" ; type enumeration { enum no-revertive { value 0 ; description "unprotected." ; } enum revertive { value 1 ; description "protection." ; } } } leaf wtr { description "WTR.unit:s" ; type uint32; default 300; } } grouping oam-policy { leaf detect-type { description "detect type" ; type enumeration { enum undetect { value 0 ; description "unprotected." ; } enum APS { value 1 ; description "protection." ; } enum BFD { value 2 ; description "unprotected." ; } } } container bfd-detect-para { leaf ingress-discriminator { description "ingress-discriminator" ; type int32; } leaf egress-discriminator { description "egress-discriminator" ; type int32; Zha, et al. Expires April 19, 2016 [Page 17] Internet-Draft L3VPN Deployment in ONOS October 2015 } leaf tx-interval { description "tx-interval" ; type int32; } leaf rx-interval { description "rx-interval" ; type int32; } leaf detect-interval { description "detect-interval" ; type int32; } } } grouping ac { leaf id{ mandatory true; description "ac id." ; type string; } leaf name{ config false; description "ac name." ; type string; } leaf ne-id { mandatory true; description "ne id." ; type string ; } leaf ltp-id { mandatory true; description "ltp id." ; type string ; } leaf admin-status { type types:admin-status; } leaf operate-status { type types:operate-status; } container l2-access { description "link layer access information of ac." ; uses l2-access; Zha, et al. Expires April 19, 2016 [Page 18] Internet-Draft L3VPN Deployment in ONOS October 2015 } leaf role { description "role of snc lsp." ; type enumeration { enum master { value 0 ; description "master." ; } enum slave { value 1 ; description "slave." ; } enum hub { value 2 ; description "hub." ; } enum spoke { value 3 ; description "spoke." ; } } default master; } container qos-policy { container qos-if-cars { list qos-if-car { key "direction"; uses qos-if-car; } } } } grouping l3-ac { uses ac; container connection { description "connection information of ac." ; uses connection; } } grouping l2-access { leaf access-type{ mandatory true; type enumeration { enum Port { value 0 ; description "master." ; Zha, et al. Expires April 19, 2016 [Page 19] Internet-Draft L3VPN Deployment in ONOS October 2015 } enum Dot1Q { value 1 ; description "Dot1Q." ; } enum QinQ { value 2 ; description "QinQ." ; } } } leaf dot1q-vlan-bitmap { mandatory true; description "Dot1Q Vlan Bitmap." ; type string; } leaf qinq-svlan-bitmap { mandatory true; description "QinQ svlan Bitmap." ; type string; } leaf qinq-cvlan-bitmap { mandatory true; description "QinQ cvlan Bitmap." ; type string; } leaf access-action { mandatory true; description "access type." ; type enumeration { enum Keep { value 0 ; description "keep." ; } enum Push { value 1 ; description "push." ; } enum Pop { value 2 ; description "pop." ; } enum Swap { value 3 ; description "swap." ; Zha, et al. Expires April 19, 2016 [Page 20] Internet-Draft L3VPN Deployment in ONOS October 2015 } } } leaf action-vlan-id { description "action vlan id." ; type int32 { range "1..4094"; } } } grouping connection { leaf ip-address { description "ip address of access circuit's connectio." ; type inet:ip-address ; } leaf mask-length { description "mask length of ip address." ; type int32 { range "1..32"; } } leaf protocols { description "protocols between PE and CE." ; type enumeration { enum static { value 0 ; description "static." ; } enum ospf { value 1 ; description "ospf." ; } enum isis { value 2 ; description "bgp" ; } enum bgp { value 3 ; description "bgp" ; } } } container static-routes { list static-route { Zha, et al. Expires April 19, 2016 [Page 21] Internet-Draft L3VPN Deployment in ONOS October 2015 key "ip-prefix mask-length"; leaf ip-prefix { type inet:ipv4-address; } leaf mask-length { type uint32 { range "1..32"; } } leaf next-hop { type inet:ipv4-address ; } leaf preference { type uint32 { range "1..65535"; } } } } } grouping pw{ leaf id { description "ID of pw." ; type string ; } uses encaplate-type-grouping; leaf ingress-ne-id { description "ingress ne id." ; type string ; } leaf egress-ne-id { description "egress ne id." ; type string ; } leaf ctrl-word-support { description "ctrl word support. 0 : not support, 1 : support" ; type enumeration { enum not-support { value 0 ; description "pw doesn't support control word" ; } enum support { Zha, et al. Expires April 19, 2016 [Page 22] Internet-Draft L3VPN Deployment in ONOS October 2015 value 1 ; description "pw supports control word" ; } } default support; } leaf sn-support { description "serial number support. 0 : not support, 1 : support" ; type enumeration { enum not-support { value 0 ; description "pw doesn't support control word" ; } enum support { value 1 ; description "pw supports control word" ; } } default not-support; } leaf vccv-type { description "vccv type" ; type enumeration { enum not-support { value 0 ; description "pw doesn't support vccv" ; } enum CWD { value 1 ; description "pw supports vccv" ; } enum Label-alert { value 2 ; description "pw supports vccv" ; } enum TTL { value 3 ; description "pw supports vccv" ; } enum CWD&Label-alert { value 4 ; description "pw supports vccv" ; } enum CWD&TTL { Zha, et al. Expires April 19, 2016 [Page 23] Internet-Draft L3VPN Deployment in ONOS October 2015 value 5 ; description "pw supports vccv" ; } enum Label-alert&TTL { value 6 ; description "pw supports vccv" ; } enum CWD&Label-alert&TTL { value 7 ; description "pw supports vccv" ; } } default not-support; } leaf conn-ack-type { description "Connectivity test type" ; type enumeration { enum not-support { value 0 ; description "pw doesn't support connection ack" ; } enum support { value 1 ; description "pw supports connection ack" ; } } default not-support; } container tunnels { list tunnel{ key "tunnel-id"; uses tunnel; } } } grouping tunnel { leaf tunnel-id { description "ID of tunnel." ; type string ; } description "tunnel infomation" ; } grouping encaplate-type-grouping { leaf encaplate-type { description "encaplate type." ; Zha, et al. Expires April 19, 2016 [Page 24] Internet-Draft L3VPN Deployment in ONOS October 2015 type enumeration { enum NONE { value 0 ; description "none." ; } enum fr-dlci-martini { value 1 ; description "fr-dlci-martini." ; } enum atm-aal5-sdu { value 2 ; description "atm-aal5-sdu." ; } enum atm-transparent { value 3 ; description "atm-transparent." ; } enum ethernet-vlan { value 4 ; description "ethernet-vlan." ; } enum ethernet { value 5 ; description "ethernet ." ; } enum hdlc { value 6 ; description " hdlc." ; } enum ppp { value 7 ; description "ppp." ; } enum cep-mpls { value 8 ; description " cep-mpls." ; } enum atm-ntol { value 9 ; description "atm-ntol." ; } enum atm-nto1-vpc { value 10 ; description "atm-nto1-vpc." ; } enum ip-layer2 { value 11 ; Zha, et al. Expires April 19, 2016 [Page 25] Internet-Draft L3VPN Deployment in ONOS October 2015 description " ip-layer2." ; } enum atm-1to1-vcc { value 12 ; description "atm-1to1-vcc." ; } enum atm-1to1-vpc { value 13 ; description "atm-1to1-vpc." ; } enum atm-aal5-pdu { value 14 ; description "atm-aal5-pdu." ; } enum fr-port { value 15 ; description "fr-port." ; } enum cep-packet { value 16 ; description "cep-packet." ; } enum e1 { value 17 ; description "e1." ; } enum t1 { value 18 ; description "t1." ; } enum e3 { value 19 ; description "e3." ; } enum t3 { value 20 ; description " t3." ; } enum cesopsn-basic { value 21 ; description "cesopsn-basic." ; } enum tdmoip-aal1 { value 22 ; description "tdmoip-aal1." ; } enum cesopsn-tdm { Zha, et al. Expires April 19, 2016 [Page 26] Internet-Draft L3VPN Deployment in ONOS October 2015 value 23 ; description "cesopsn-tdm." ; } enum tdmoip-aal2 { value 24 ; description "tdmoip-aal2." ; } enum fr-dlci { value 25 ; description "fr-dlci." ; } } } } grouping pw-trail{ leaf id { description "ID of pw-trail." ; type string ; } leaf role { description "role of pw-trail." ; type pw-role; } container pw-lists { list pw-list { key id; uses pw ; } } } grouping tunnel-service { leaf signaling-type { description "signaling type." ; type enumeration { enum RSVP-TE { value 0 ; description "RSVP-TE" ; } enum LDP { value 1 ; description "LDP" ; } enum GRE { value 2 ; description "GRE" ; Zha, et al. Expires April 19, 2016 [Page 27] Internet-Draft L3VPN Deployment in ONOS October 2015 } enum SR-BE { value 3 ; description "SR-BE" ; } enum SR-TE { value 4 ; description "SR-TE" ; } } default RSVP-TE; } leaf tunnel-mode { description "service to tunnel mode." ; type enumeration { enum Nto1 { value 0 ; description "multi service one tunnel" ; } enum 1to1 { value 1 ; description "oner service one tunnel" ; } } default Nto1; } container protect-policy { uses protect-policy; } container oam-policy { uses oam-policy; } leaf latency { description "tunnel latency requirement." ; type int32; } } grouping service-path { leaf service-id { description "l2vpn or l3vpn service id." ; type string ; } leaf source-ne-id { description "source ne id." ; type string ; } Zha, et al. Expires April 19, 2016 [Page 28] Internet-Draft L3VPN Deployment in ONOS October 2015 leaf source-ac-id { description "source ltp id." ; type string ; } leaf destination-ne-id { description "destination ne id." ; type string ; } leaf destination-ac-id { description "destination ltp id." ; type string ; } container path-lists{ list path-list { key "path-layer path-role"; leaf path-layer { description "path type. 0 : PW, 1 : BGP-LSP, 2 : PW" ; type enumeration { enum PW { value 0 ; description "pw path." ; } enum BGP-LSP { value 1 ; description "BGP-LSP Path." ; } enum LSP { value 2 ; description "LSP Path." ; } } } leaf path-role { description "path role.. 0 : master, 1 : backup, 2 : Bypass." ; type enumeration { enum Primary { value 0 ; description "master path." ; } enum Backup { value 1 ; description "backup path." ; } Zha, et al. Expires April 19, 2016 [Page 29] Internet-Draft L3VPN Deployment in ONOS October 2015 enum Active { value 2 ; description "active path." ; } } } container paths { list path { key "ne-id"; leaf ne-id { type string; } leaf ingress-ltp-id { type string; } leaf backward-peer-id { type string; } leaf egress-ltp-id { type string; } leaf forward-peer-id { type string; } } } } } } } module sd-onos-service-l3vpn { namespace "urn:onos:l3vpn"; prefix l3vpn ; import ietf-inet-types{ prefix inet; } import ietf-yang-types { prefix yang-types; } import sd-onos-service-types { prefix service-types; } import sd-onos-common-types { prefix types; } Zha, et al. Expires April 19, 2016 [Page 30] Internet-Draft L3VPN Deployment in ONOS October 2015 organization ""; contact ""; revision "2015-10-14" {description "revised revision.";} container service { container l3vpn-cfg { list vpn-cfg { key name; uses l3vpn; } } container service-paths { list service-path{ key "service-id source-ne-id source-ac-id destination-ne-id destination-ac-id"; uses service-types:service-path; } } } grouping l3vpn { leaf name { mandatory true; description "name of snc eline." ; type string ; } leaf id { mandatory true; description "ID of snc eline." ; type uint32 ; } leaf user-label { description "user label of snc eline." ; type string ; } leaf parent-ncd-id { description "parent ncd id." ; type string ; } leaf admin-status { type types:admin-status; } leaf operate-status { type types:operate-status; } Zha, et al. Expires April 19, 2016 [Page 31] Internet-Draft L3VPN Deployment in ONOS October 2015 uses service-type-grouping; container acess-information { list access-circuit { key "id"; uses service-types:l3-ac; } } container protect-policy{ description "L3VPN Service protect policy." ; uses service-types:protect-policy; } container tunnel-service { description "tunnel service." ; uses service-types:tunnel-service; } } grouping service-type-grouping { leaf service-topology { description "service topology type." ; default full-mesh; type enumeration { enum full-mesh { value 1 ; description "full-mesh." ; } enum hub-spoke { value 2 ; description "hub-spoke." ; } } } } rpc create-l3vpn-instance { input { container l3vpn-instance { uses l3vpn; } } } Zha, et al. Expires April 19, 2016 [Page 32] Internet-Draft L3VPN Deployment in ONOS October 2015 rpc delete-l3vpn-instance { input { leaf l3vpn-id { type string; } } } rpc close-l3vpn { input { leaf l3vpn-id { type string; } container ac-status { list acs{ key "id"; leaf id { type string; } leaf admin-status { type types:admin-status; } } } } } rpc modify-l3vpn-instance-basic { input { leaf l3vpn-id { type string; } leaf user-label { type string ; } } } rpc modify-l3vpn-instance-ac-qos { input { leaf l3vpn-id { type string; } container ac-qos { list acs{ key "id"; leaf id { type string; Zha, et al. Expires April 19, 2016 [Page 33] Internet-Draft L3VPN Deployment in ONOS October 2015 } container qos-policy { container qos-if-cars { list qos-if-car { key "direction"; uses service-types:qos-if-car; } } } } } } } rpc modify-l3vpn-instance-connection { input { leaf l3vpn-id { type string; } container ac-connection { list acs{ leaf id { description "ac id." ; type string ; } container connection { description "CE to PE connection." ; uses service-types:connection; } } } } } rpc inquire-l3vpn-instance-work-path { input { leaf service-id { type string; } leaf ingress-ne-id { type string ; } leaf destination-ne-id { type string ; } leaf ingress-ac-id { type string ; } Zha, et al. Expires April 19, 2016 [Page 34] Internet-Draft L3VPN Deployment in ONOS October 2015 leaf destination-ac-id { type string ; } leaf path-layer { type string ; } leaf path-role { type string ; } } output { container service-path { leaf service-id { type string; } leaf ingress-ne-id { type string ; } leaf destination-ne-id { type string ; } leaf ingress-ac-id { type string ; } leaf destination-ac-id { type string ; } leaf path-layer { type string ; } leaf path-role { type string ; } list path-list { key "ne-id"; leaf ne-id { type string; } leaf ingress-ltp-id { type string; } leaf backward-peer-id { type string; } leaf egress-ltp-id { type string; } Zha, et al. Expires April 19, 2016 [Page 35] Internet-Draft L3VPN Deployment in ONOS October 2015 leaf forward-peer-id { type string; } } } } } } 5. Security Considerations TBD 6. IANA Considerations This document has no actions for IANA. 7. Contributors and Acknowledgments Jan Lindblad Tail-F Email: janl@tail-f.com This document also has benefited from reviews, suggestions, comments and proposed text provided by the following members, listed in alphabetical order: Feng Dong, Jing Huang, Kepeng Li, Junru Lin, Felix Lu, Wu Nan, and Cathy Zhou. 8. References 8.1. 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. [RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021, October 2010. Zha, et al. Expires April 19, 2016 [Page 36] Internet-Draft L3VPN Deployment in ONOS October 2015 [RFC4110] Callon, R. and M. Suzuki, "A Framework for Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs)", RFC 4110, July 2005. [RFC3272] Awduche, D., Chiu, A., Elwalid, A., Widjaja, I., and X. Xiao, "Overview and Principles of Internet Traffic Engineering", RFC 3272, May 2002. [RFC2473] Conta, A. and S. Deering, "Generic Packet Tunneling in IPv6 Specification", RFC 2473, December 1998. [RFC4664] L. Andersson and E. Rosen, "Framework for Layer 2 Virtual Private Networks (L2VPNs)", RFC 4664, September 2006. 8.2. Informative References [RESTCONF] Bierman, A., Bjorklund, M., Watsen, K., and R. Fernando, "RESTCONF Protocol", draft-ietf-netconf-restconf (work in progress), July 2014. [ONOS-L3VPN]ONOS-based SDN Controller for China Unicom MPLS L3VPN Service. http://onosproject.org/wp- content/uploads/2015/06/PoC_Huawei-VPN.pdf [VPN] Mason, Andrew G. (2002). Cisco Secure Virtual Private Network. Cisco Press. p. 7. [L3VPN] S. Litkowski, R. Shakir, L. Tomotaki and K. D'Souza, "YANG Data Model for L3VPN service delivery", IETF Internet draft, draft-l3vpn-service-yang, February 2015. Zha, et al. Expires April 19, 2016 [Page 37] Internet-Draft L3VPN Deployment in ONOS October 2015 Authors' Addresses Yiyong Zha Huawei Technologies zhayiyong@huawei.com Dacheng Zhang Chaoyang Dist Beijing 100000 P.R. China Dacheng.zhang@gmail.com Ying Cheng (Editor) China Unicom P.R. China Email: chengying10@chinaunicom.cn Maxim Klyus NetCracker Email: klyus@NetCracker.com Zha, et al. Expires April 19, 2016 [Page 38]