A YANG Data Model for Client-layer Tunnel Huawei TechnologiesH1, XiliuBeipo Village, Songshan LakeDongguanGuangdong523808Chinazhenghaomian@huawei.comFutureweiaihuaguo.ietf@gmail.comHuawei TechnologiesItalo.Busi@huawei.comCAICTxuyunbin@caict.ca.cnChina Mobilezhaoyangyjy@chinamobile.comVolta Networksxufeng.liu.ietf@gmail.comCCAMP Working Group
A transport network is a server-layer network to provide connectivity services to its client. In this draft the tunnel of client is described, with the definition of client tunnel YANG model.
A transport network is a server-layer network designed to provide connectivity services for a client-layer network to carry the client traffic transparently across the server-layer network resources. The tunnel model in Traffic-Engineered network has been defined in both generic way and technology-specific way. The generic model, which is the base TE tunnel YANG model, can be found at . Technology-specific models, such as OTN/WSON tunnel model, have also been defined in and respectively. Corresponding tunnel on client-layer is also required, to have a complete topology view from the perspective of network controllers.
This document defines a data model of all client-layer tunnel, using YANG language defined in . The model is augmenting the generic TE tunnel model, and can be used by applications exposing to a network controller via a REST interface. Furthermore, it can be used by an application to describe the client tunnel that constructed above the server-layer network. It is also worth noting that the client layer network will only need the tunnel model when there is a demand for switching techniques, such as Carrier Ethernet and MPLS-TP. The transparent signals do not need this model.
A simplified graphical representation of the data model is used in this document. The meaning of the symbols in the YANG data tree presented later in this document is defined in . They are provided below for reference.
Brackets "[" and "]" enclose list keys.
Abbreviations before data node names: "rw" means configuration (read-write) and "ro" state data (read-only).
Symbols after data node names: "?" means an optional node, "!" means a presence container, and "*" denotes a list and leaf-list.
Parentheses enclose choice and case nodes, and case nodes are also marked with a colon (":").
Ellipsis ("...") stands for contents of subtrees that are not shown.
This section will be completed later.
TBD.
Editor Notes: This section is used to note temporary discussion/conclusion that to be fixed in the future version, and will be removed before publication.
This is a part of L2 work, need to discuss how to go with other L2 network models. The expectation is to include all potential L2 TE part in this work.
TBD.
TBD.
The data following the model defined in this document is exchanged via, for example, the interface between an orchestrator and a transport network controller. The security concerns mentioned in also applies to this document.
The YANG module defined in this document can be accessed via the RESTCONF protocol defined in , or maybe via the NETCONF protocol .
We would like to thank Igor Bryskin and Daniel King for their comments and discussions.
Yanlei Zheng
China Unicom
Email: zhengyl@dimpt.com
Zhe Liu
Huawei Technologies,
Email: liuzhe123@huawei.com
Sergio Belotti
Nokia,
Email: sergio.belotti@nokia.com
Yingxi Yao
Shanghai Bell,
yingxi.yao@nokia-sbell.com
Giuseppe Fioccola
Huawei Technologies
giuseppe.fioccola@huawei.com