A YANG Data Model for Client-layer Tunnel

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.

file "ietf-eth-te-tunnel@2018-03-01.yang" module ietf-eth-te-tunnel { namespace "urn:ietf:params:xml:ns:yang:ietf-eth-te-tunnel"; prefix "eth-tunnel"; import ietf-te { prefix "te"; } import ietf-eth-tran-types { prefix "etht-types"; } organization "Internet Engineering Task Force (IETF) CCAMP WG"; contact " WG List: ID-draft editor: Haomian Zheng (zhenghaomian@huawei.com); Italo Busi (italo.busi@huawei.com); Aihua Guo (aihuaguo.ietf@gmail.com); Yunbin Xu (xuyunbin@caict.ac.cn); Yang Zhao (zhaoyangyjy@chinamobile.com); Xufeng Liu (xufeng.liu.ietf@gmail.com); "; description "This module defines a model for ETH transport tunnel"; revision 2018-03-01 { description "Initial revision"; reference "draft-zheng-ccamp-client-tunnel-yang"; } grouping eth-tunnel-endpoint { description "Parameters for ETH tunnel."; leaf vlanid { type etht-types:vlanid; description "VLAN tag id."; } leaf tag-type { type etht-types:eth-tag-type; description "VLAN tag type."; } } augment "/te:te/te:tunnels/te:tunnel" { description "Augment with additional parameters required for ETH service."; container src-eth-tunnel-endpoint { description "Source ETH tunnel endpoint."; uses eth-tunnel-endpoint; } container dst-eth-tunnel-endpoint { description "Destination ETH tunnel endpoint."; uses eth-tunnel-endpoint; } container bandwidth-profile { description "ETH tunnel bandwidth profile specification."; uses etht-types:etht-bandwidth-profiles; } } }

]]>


 

 
  
  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