]> Huawei Technologies

yuchaode@huawei.com

Huawei Technologies

H1, Huawei Xiliu Beipo Village, Songshan Lake Dongguan Guangdong 523808 China zhenghaomian@huawei.com

Futurewei

aihuaguo@futurewei.com

Huawei Technologies

italo.busi@huawei.com

CAICT

xuyunbin@caict.ac.cn

China Mobile

zhaoyangyjy@chinamobile.com

Alef Edge

xufeng.liu.ietf@gmail.com

Routing CCAMP Working Group next generation unicorn sparkling distributed ledger 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. About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the Common Control and Measurement Plane Working Group mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .

Introduction 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.

Terminology and Notations 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.

YANG Model for Client-layer Tunnel

YANG Tree for Ethernet Tunnel

Ethernet TE Tunnel YANG tree

YANG Tree for Tunnel of other Client Signal Model This section will be completed later.

YANG Code for Client-layer Tunnel

The ETH Tunnel YANG Code

Ethernet TE Tunnel YANG module 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; } } } ]]>

Other Client-layer Tunnel YANG Code TBD.

Considerations and Open Issue 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.

IANA Considerations TBD.

Manageability Considerations TBD.

Security Considerations 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 .

References Normative References Cisco Systems Inc Cisco Systems Inc Alef Edge Juniper Networks Individual This document defines a YANG data model for the provisioning and management of Traffic Engineering (TE) tunnels, Label Switched Paths (LSPs), and interfaces. The model covers data that is independent of any technology or dataplane encapsulation and is divided into two YANG modules that cover device-specific, and device independent data. This model covers data for configuration, operational state, remote procedural calls, and event notifications. YANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols. This document describes the syntax and semantics of version 1.1 of the YANG language. YANG version 1.1 is a maintenance release of the YANG language, addressing ambiguities and defects in the original specification. There are a small number of backward incompatibilities from YANG version 1. This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF). This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF). The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK] Informative References Huawei Technologies Huawei Technologies Nokia Nokia CAICT This document describes the YANG data model for tunnels in OTN TE networks. The model can be used to do the configuration in order to establish the tunnel in OTN network. This work is independent with the control plane protocols. Samsung Huawei Technologies Futurewei Nokia Lancaster University ETRI CTTC This document provides a YANG data model for WSON TE tunnel. This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language.

Acknowledgments We would like to thank Igor Bryskin and Daniel King for their comments and discussions.

Contributors Huawei Technologies

liuzhe123@huawei.com

Nokia

sergio.belotti@nokia.com

Shanghai Bell

yingxi.yao@nokia-sbell.com

Huawei Technologies

giuseppe.fioccola@huawei.com

China Unicom

zhengyanlei@chinaunicom.cn