idnits 2.17.1 draft-ietf-ccamp-flexigrid-yang-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (July 12, 2020) is 1377 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFCXXXX' is mentioned on line 174, but not defined == Outdated reference: A later version (-09) exists of draft-ietf-ccamp-layer0-types-03 == Outdated reference: A later version (-04) exists of draft-ietf-ccamp-flexigrid-media-channel-yang-02 Summary: 0 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 CCAMP Working Group J.E. Lopez de Vergara 2 Internet Draft Universidad Autonoma de Madrid 3 Intended status: Standards Track D. Perdices 4 Expires: January 13, 2021 Naudit HPCN 5 D. King 6 Lancaster University 7 Y. Lee 8 Samsung 9 H. Zheng 10 Huawei Technologies 11 July 12, 2020 13 YANG data model for Flexi-Grid Optical Networks 14 draft-ietf-ccamp-flexigrid-yang-06.txt 16 Abstract 18 This document defines a YANG module for managing flexi-grid optical 19 networks. The model defined in this document specifies a flexi-grid 20 traffic engineering database that is used to describe the topology of 21 a flexi-grid network. It is based on and augments existing YANG 22 models that describe network and traffic engineering topologies. 24 A partner document defines a second YANG module for flexi-grid media 25 channels, i.e., the paths from source to destination through a number 26 of intermediate nodes. 28 Status of this Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. This document may not be modified, 32 and derivative works of it may not be created, except to publish it 33 as an RFC and to translate it into languages other than English. 35 Internet-Drafts are working documents of the Internet Engineering 36 Task Force (IETF), its areas, and its working groups. Note that 37 other groups may also distribute working documents as Internet- 38 Drafts. 40 Internet-Drafts are draft documents valid for a maximum of six 41 months and may be updated, replaced, or obsoleted by other documents 42 at any time. It is inappropriate to use Internet-Drafts as 43 reference material or to cite them other than as "work in progress." 45 The list of current Internet-Drafts can be accessed at 46 http://www.ietf.org/ietf/1id-abstracts.txt 48 The list of Internet-Draft Shadow Directories can be accessed at 49 http://www.ietf.org/shadow.html 51 This Internet-Draft will expire on January 13, 2020. 53 Copyright Notice 55 Copyright (c) 2020 IETF Trust and the persons identified as the 56 document authors. All rights reserved. 58 This document is subject to BCP 78 and the IETF Trust's Legal 59 Provisions Relating to IETF Documents 60 (http://trustee.ietf.org/license-info) in effect on the date of 61 publication of this document. Please review these documents 62 carefully, as they describe your rights and restrictions with 63 respect to this document. Code Components extracted from this 64 document must include Simplified BSD License text as described in 65 Section 4.e of the Trust Legal Provisions and are provided without 66 warranty as described in the Simplified BSD License. 68 Table of Contents 70 1. Introduction ..............................................2 71 2. Conventions used in this document .........................3 72 2.1. Terminology ..........................................3 73 2.2. Tree diagram .........................................4 74 2.3. Prefixes in Data Node Names ..........................4 75 3. Main Building Blocks of the Flexi-grid TED.................4 76 4. Example of Use ............................................8 77 5. Flexi-grid Topology YANG Model.............................9 78 5.1. YANG Model - Tree ....................................9 79 5.2. YANG Model - Code ....................................30 80 6. Security Considerations ...................................69 81 7. IANA Considerations .......................................70 82 8. References ................................................70 83 8.1. Normative References .................................70 84 8.2. Informative References ...............................71 85 9. Contributors ..............................................72 86 10. Acknowledgments ..........................................72 87 Authors' Addresses ...........................................73 89 1. Introduction 91 The flexible grid (flexi-grid) optical network technology defined by 92 the International Telecommunication Union Telecommunication 93 Standardization Sector (ITU-T) and documented in Recommendation 94 G.694.1 [G.694.1] and G.872 [G.872] provides an enhanced Dense 95 Wavelength Division Multiplexing (DWDM) grid by defining a set of 96 nominal central frequencies, channel spacings, and the concept of the 97 "frequency slot". In such an environment, a data-plane connection is 98 switched based on allocated, variable-sized frequency ranges within 99 the optical spectrum, creating what is known as a flexible grid 100 (flexi-grid). This technology increases both transport network 101 scalability and flexibility, allowing the optimization of bandwidth 102 usage. 104 [RFC7698] provides a framework GMPLS-Based control of flexi-grid DWDM 105 networks while [RFC7699] defines generalized labels for the use in 106 flexi-grid in GMPLS networks. 108 This document presents a YANG [RFC7950] model for flexi-grid objects 109 in the dynamic optical network, including the nodes, transponders 110 and links between them, as well as how such links interconnect nodes 111 and transponders. 113 The YANG model for flexi-grid networks allows the representation of 114 the flexi-grid optical layer of a network, combined with the 115 underlying physical layer. 117 This document identifies the flexi-grid components, parameters and 118 their values, characterizes the features and the performances of the 119 flexi-grid elements. An application example is provided towards the 120 end of the document to better understand their utility. 122 A partner document defines a second YANG module that described flexi- 123 grid media channels, i.e., the paths from source to destination 124 through a number of intermediate nodes 125 [I-D.draft-ietf-ccamp-flexigrid-media-channel-yang]. 127 2. Conventions used in this document 129 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 130 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 131 "OPTIONAL" in this document are to be interpreted as described in BCP 132 14 [RFC2119] [RFC8174] when, and only when, they appear in all 133 capitals, as shown here. 135 2.1. Terminology 137 Refer to [RFC7446] and [RFC7581] for the key terms used in this 138 document. 140 The following terms are defined in [RFC7950] and are not redefined 141 here: 143 o client 144 o server 145 o augment 146 o data model 147 o data node 149 The following terms are defined in [RFC6241] and are not redefined 150 here: 152 o configuration data 153 o state data 155 The terminology for describing YANG data models is found in 156 [RFC7950]. 158 2.2. Tree Diagram 160 A simplified graphical representation of the data model is used in 161 Section 5 of this this document. The meaning of the symbols in 162 these diagrams is defined in [RFC8340]. 164 2.3. Prefixes in Data Node Names 166 In this document, names of data nodes and other data model objects 167 are prefixed using the standard prefix associated with the 168 corresponding YANG imported modules, as shown in Table 1. 170 +-------------+-------------------------+-----------------+ 171 | Prefix | YANG module | Reference | 172 +-------------+-------------------------+-----------------+ 173 | l0-types | ietf-layer0-types | [Layer0-Types] | 174 | flexi-grid | ietf-flexi-grid-topology| [RFCXXXX] | 175 | nw | ietf-network | [RFC8345] | 176 | nt | ietf-network-topology | [RFC8345] | 177 | tet | ietf-te-topology | [TE-TOPO] | 178 +-------------+-------------------------+-----------------+ 180 Table 1: Prefixes and corresponding YANG modules 182 RFC Editor Note: Please replace XXXX with the RFC number assigned to 183 this document when it is published. Please remove this note. 185 3. Main building Blocks of the Flexi-grid Topology 187 This section describes the YANG module. It is specified in Section 5. 189 The description of the three main components, flexi-grid-node, 190 flexi-grid-transponder and flexi-grid-link is provided below. 191 flexi-grid-sliceable-transponders are also defined. 193 The syntax specification below uses the augmented Backus-Naur 194 Form (BNF) as described in [RFC5234]. 196 ::= 198 : This element designates a node in the 199 network. 201 ::= 203 : Contains the configuration of a node. 205 ::= 206 208 : Contains all the 209 attributes related to the node configuration, such as 210 its interfaces or its management addresses. 211 ::= 212 213 214 [ / ] 216 : The list containing all the 217 information of the interfaces. 219 : Determines the interface name. 221 : Port number of the interface. 223 : Boolean value that defines 224 whether the interface is input or not. 226 : Boolean value that defines 227 whether the interface is output or not. 229 : Description of the usage of 230 the interface. 232 : Determines if the interface 233 is numbered or unnumbered. 235 ::= 236 : An interface with 237 its own IP address. 239 : Only available if 240 is "numbered-interface". 241 Determines the IP address of the interface. 243 ::= 244