--- 1/draft-ietf-ccamp-flexigrid-yang-06.txt 2020-09-22 20:13:13.224924738 -0700 +++ 2/draft-ietf-ccamp-flexigrid-yang-07.txt 2020-09-22 20:13:13.356928106 -0700 @@ -1,97 +1,89 @@ -CCAMP Working Group J.E. Lopez de Vergara -Internet Draft Universidad Autonoma de Madrid -Intended status: Standards Track D. Perdices -Expires: January 13, 2021 Naudit HPCN + +CCAMP Working Group J. Lopez de Vergara +Internet-Draft Universidad Autonoma de Madrid +Intended status: Informational D. Perdices Burrero +Expires: March 26, 2021 Naudit D. King - Lancaster University + Old Dog Consulting Y. Lee Samsung H. Zheng Huawei Technologies - July 12, 2020 + September 22, 2020 - YANG data model for Flexi-Grid Optical Networks - draft-ietf-ccamp-flexigrid-yang-06.txt + A YANG Data Model for Flexi-Grid Optical Networks + draft-ietf-ccamp-flexigrid-yang-07 Abstract This document defines a YANG module for managing flexi-grid optical networks. The model defined in this document specifies a flexi-grid traffic engineering database that is used to describe the topology of a flexi-grid network. It is based on and augments existing YANG models that describe network and traffic engineering topologies. A partner document defines a second YANG module for flexi-grid media channels, i.e., the paths from source to destination through a number of intermediate nodes. -Status of this Memo +Status of This Memo This Internet-Draft is submitted in full conformance with the - provisions of BCP 78 and BCP 79. This document may not be modified, - and derivative works of it may not be created, except to publish it - as an RFC and to translate it into languages other than English. + 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 + Task Force (IETF). Note that other groups may also distribute + working documents as Internet-Drafts. The list of current Internet- + Drafts is at https://datatracker.ietf.org/drafts/current/. - The list of Internet-Draft Shadow Directories can be accessed at - http://www.ietf.org/shadow.html + 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 January 13, 2020. + This Internet-Draft will expire on March 26, 2021. Copyright Notice Copyright (c) 2020 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 + (https://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. + 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 - 2.1. Terminology ..........................................3 - 2.2. Tree diagram .........................................4 - 2.3. Prefixes in Data Node Names ..........................4 - 3. Main Building Blocks of the Flexi-grid TED.................4 - 4. Example of Use ............................................8 - 5. Flexi-grid Topology YANG Model.............................9 - 5.1. YANG Model - Tree ....................................9 - 5.2. YANG Model - Code ....................................30 - 6. Security Considerations ...................................69 - 7. IANA Considerations .......................................70 - 8. References ................................................70 - 8.1. Normative References .................................70 - 8.2. Informative References ...............................71 - 9. Contributors ..............................................72 - 10. Acknowledgments ..........................................72 - Authors' Addresses ...........................................73 + 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 + 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 + 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 + 4. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . . . 4 + 4.1. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4 + 5. Main Components of the Flexi-grid Topology . . . . . . . . . 5 + 6. Example of Use . . . . . . . . . . . . . . . . . . . . . . . 11 + 7. YANG Model (Tree Structure) for Flexi-grid topology . . . . . 13 + 8. The YANG Code for Flexi-grid topology . . . . . . . . . . . . 30 + 9. Security Considerations . . . . . . . . . . . . . . . . . . . 64 + 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 65 + 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 65 + 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 66 + 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 67 + 13.1. Normative References . . . . . . . . . . . . . . . . . . 67 + 13.2. Informative References . . . . . . . . . . . . . . . . . 68 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 69 1. Introduction The flexible grid (flexi-grid) optical network technology defined by the International Telecommunication Union Telecommunication Standardization Sector (ITU-T) and documented in Recommendation G.694.1 [G.694.1] and G.872 [G.872] provides an enhanced Dense Wavelength Division Multiplexing (DWDM) grid by defining a set of nominal central frequencies, channel spacings, and the concept of the "frequency slot". In such an environment, a data-plane connection is @@ -99,174 +91,180 @@ the optical spectrum, creating what is known as a flexible grid (flexi-grid). This technology increases both transport network scalability and flexibility, allowing the optimization of bandwidth usage. [RFC7698] provides a framework GMPLS-Based control of flexi-grid DWDM networks while [RFC7699] defines generalized labels for the use in flexi-grid in GMPLS networks. This document presents a YANG [RFC7950] model for flexi-grid objects - in the dynamic optical network, including the nodes, transponders - and links between them, as well as how such links interconnect nodes - and transponders. + in the dynamic optical network, including the nodes, transponders and + links between them, as well as how such links interconnect nodes and + transponders. The YANG model for flexi-grid networks allows the representation of the flexi-grid optical layer of a network, combined with the underlying physical layer. This document identifies the flexi-grid components, parameters and their values, characterizes the features and the performances of the flexi-grid elements. An application example is provided towards the end of the document to better understand their utility. A partner document defines a second YANG module that described flexi- - grid media channels, i.e., the paths from source to destination - through a number of intermediate nodes - [I-D.draft-ietf-ccamp-flexigrid-media-channel-yang]. + grid tunnels, i.e., the paths from source to destination through a + number of intermediate nodes + [I-D.ietf-ccamp-flexigrid-media-channel-yang]. -2. Conventions used in this document +2. Conventions 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 BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. -2.1. Terminology +3. Terminology Refer to [RFC7446] and [RFC7581] for the key terms used in this document. The following terms are defined in [RFC7950] and are not redefined here: o client + o server + o augment o data model + o data node The following terms are defined in [RFC6241] and are not redefined here: o configuration data + o state data The terminology for describing YANG data models is found in [RFC7950]. -2.2. Tree Diagram +4. Tree Diagram A simplified graphical representation of the data model is used in - Section 5 of this this document. The meaning of the symbols in - these diagrams is defined in [RFC8340]. + this document. The meaning of the symbols in these diagrams is + defined in [RFC8340]. -2.3. Prefixes in Data Node Names +4.1. Prefixes in Data Node Names In this document, names of data nodes and other data model objects are prefixed using the standard prefix associated with the - corresponding YANG imported modules, as shown in Table 1. + corresponding YANG imported modules, as shown in Figure 1. It uses + prefixes from [I-D.ietf-ccamp-layer0-types], [RFC8345], and + [RFC8795]. +-------------+-------------------------+-----------------+ | Prefix | YANG module | Reference | +-------------+-------------------------+-----------------+ - | l0-types | ietf-layer0-types | [Layer0-Types] | - | flexi-grid | ietf-flexi-grid-topology| [RFCXXXX] | + | l0-types | ietf-layer0-types | [RFCXXXX] | + | flexi-grid | ietf-flexi-grid-topology| [RFCYYYY] | | nw | ietf-network | [RFC8345] | | nt | ietf-network-topology | [RFC8345] | - | tet | ietf-te-topology | [TE-TOPO] | + | tet | ietf-te-topology | [RFC8795] | +-------------+-------------------------+-----------------+ - Table 1: Prefixes and corresponding YANG modules + Figure 1: Prefixes and Corresponding YANG modules - RFC Editor Note: Please replace XXXX with the RFC number assigned to - this document when it is published. Please remove this note. + RFC Editor Note: Please replace XXXX with the RFC numbers assigned to + draft-ietf-ccamp-layer0-types. Please replace YYYY with the RFC + number assigned to this document. Please remove this note. -3. Main building Blocks of the Flexi-grid Topology +5. Main Components of the Flexi-grid Topology - This section describes the YANG module. It is specified in Section 5. + This section describes the YANG module. It is specified in + Section 8. - The description of the three main components, flexi-grid-node, - flexi-grid-transponder and flexi-grid-link is provided below. - flexi-grid-sliceable-transponders are also defined. + The description of the three main components, flexi-grid-node, flexi- + grid-transponder and flexi-grid-link is provided below. flexi-grid- + sliceable-transponders are also defined. - The syntax specification below uses the augmented Backus-Naur - Form (BNF) as described in [RFC5234]. + The syntax specification below uses the augmented Backus-Naur Form + (BNF) as described in [RFC5234]. ::= : This element designates a node in the network. ::= : Contains the configuration of a node. ::= : Contains all the - attributes related to the node configuration, such as - its interfaces or its management addresses. + attributes related to the node configuration, such as its + interfaces or its management addresses. + ::= [ / ] - : The list containing all the - information of the interfaces. + : The list containing all the information of + the interfaces. : Determines the interface name. : Port number of the interface. - : Boolean value that defines - whether the interface is input or not. + : Boolean value that defines whether the interface + is input or not. - : Boolean value that defines - whether the interface is output or not. + : Boolean value that defines whether the interface + is output or not. - : Description of the usage of - the interface. + : Description of the usage of the interface. - : Determines if the interface - is numbered or unnumbered. + : Determines if the interface is numbered or + unnumbered. ::= - : An interface with - its own IP address. - : Only available if - is "numbered-interface". - Determines the IP address of the interface. + : An interface with its own IP address. - ::= -