idnits 2.17.1 draft-vergara-ccamp-flexigrid-media-channel-yang-01.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 date (November 11, 2017) is 2330 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) == Outdated reference: A later version (-06) exists of draft-vergara-ccamp-flexigrid-yang-05 == Outdated reference: A later version (-36) exists of draft-ietf-teas-yang-te-09 Summary: 0 errors (**), 0 flaws (~~), 3 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 Daniel Perdices 4 Expires: January 15, 2018 Naudit HPCN 5 V. Lopez 6 O. Gonzalez de Dios 7 Telefonica I+D/GCTO 8 D. King 9 Lancaster University 10 Y. Lee 11 Huawei 12 G. Galimberti 13 Cisco Photonics Srl 14 November 11, 2017 16 YANG data model for Flexi-Grid media-channels 17 draft-vergara-ccamp-flexigrid-media-channel-yang-01.txt 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. This document may not be modified, 23 and derivative works of it may not be created, except to publish it 24 as an RFC and to translate it into languages other than English. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF), its areas, and its working groups. Note that 28 other groups may also distribute working documents as Internet- 29 Drafts. 31 Internet-Drafts are draft documents valid for a maximum of six 32 months and may be updated, replaced, or obsoleted by other documents 33 at any time. It is inappropriate to use Internet-Drafts as 34 reference material or to cite them other than as "work in progress." 36 The list of current Internet-Drafts can be accessed at 37 http://www.ietf.org/ietf/1id-abstracts.txt 39 The list of Internet-Draft Shadow Directories can be accessed at 40 http://www.ietf.org/shadow.html 42 This Internet-Draft will expire on **EXPIRE_DATE** 44 Copyright Notice 46 Copyright (c) 2017 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (http://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with 54 respect to this document. Code Components extracted from this 55 document must include Simplified BSD License text as described in 56 Section 4.e of the Trust Legal Provisions and are provided without 57 warranty as described in the Simplified BSD License. 59 Abstract 61 This document defines a YANG model for managing flexi-grid optical 62 media channels, complementing the information provided by the 63 flexi-grid TED model. 64 It is also grounded on other defined YANG abstract models. 66 Table of Contents 68 1. Introduction .............................................. 2 69 2. Conventions used in this document ......................... 3 70 3. Flexi-grid media-channel overview ......................... 3 71 4. Example of use ............................................ 4 72 5. Media Channel YANG Model .................................. 5 73 5.1. YANG Model - Tree .................................... 5 74 5.2. YANG Model - Code .................................... 6 75 5.3. License .............................................. 10 76 6. Security Considerations ................................... 10 77 7. IANA Considerations ....................................... 10 78 8. References ................................................ 11 79 8.1. Normative References ................................. 11 80 8.2. Informative References ............................... 11 81 9. Contributors .............................................. 11 82 10. Acknowledgments ........................................... 11 83 Authors' Addresses ............................................ 12 85 1. Introduction 87 Transport networks are evolving from current DWDM systems towards 88 elastic optical networks, based on flexi-grid transmission and 89 switching technologies [RFC7698]. Such technology aims at increasing 90 both transport network scalability and flexibility, allowing the 91 optimization of bandwidth usage. 93 While [I-D.draft-vergara-ccamp-flexigrid-yang] focuses on flexi-grid 94 objects such as nodes, transponders and links, this document presents 95 a YANG model for the flexi-grid media-channel. This YANG module 96 defines the whole path from a source transponder or node to the 97 destination through a number of intermediate nodes in the flexi-grid 98 network. 100 This document identifies the flexi-grid media-channel components, 101 parameters and their values, characterizes the features and the 102 performances of the flexi-grid elements. An application example is 103 provided towards the end of the document to better understand 104 their utility. 106 2. Conventions used in this document 108 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 109 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 110 document are to be interpreted as described in [RFC2119]. 112 In this document, these words will appear with that interpretation 113 only when in ALL CAPS. Lower case uses of these words are not to be 114 interpreted as carrying RFC-2119 significance. 116 In this document, the characters ">>" preceding an indented line(s) 117 indicates a compliance requirement statement using the key words 118 listed above. This convention aids reviewers in quickly identifying 119 or finding the explicit compliance requirements of this RFC. 121 3. Flexi-grid media-channel overview 123 The present model defines a flexi-grid media-channel mainly 124 composed of: 125 - source address 126 - source flexi-grid port 127 - source flexi-grid transponder 128 - destination address 129 - destination flexi-grid port 130 - destination flexi-grid transponder 131 - A list of links that defines the path 132 - Other optical attributes 134 Each path can be a media-channel (only defined by source and 135 destination node) or a network media-channel (aditionally needs 136 source and destination transponders). Therefore, all the attributes 137 are optional to support both situations. 139 This is achieved by a combination of the traffic engineering tunnel 140 attributes explained in [I-D.draft-ietf-teas-yang-te] and augments 141 when necessary. For instance, source address, source flexi-grid 142 transponder, destination address and destination flexi-grid 143 transponder attributes are directly taken from tunnel, whereas other 144 attributes such as source flexi-grid port, destination flexi-grid 145 port are defined, as they are specific for flexi-grid. 147 4. Example of use 149 In order to explain how this model is used, we provide the following 150 example. An optical network usually has multiple transponders, 151 switches (nodes) and links between them. Figure 1 shows a simple 152 topology, where two physical paths interconnect two optical 153 transponders. 154 Media channel 155 <==================================================> 156 Path x 157 <--------------------------------------------------> 159 +----------+ +----------+ 160 Link 1 |Flexi-grid| Link 2 |Flexi-grid| Link 3 161 .--->| node |<-------->| node |<---. 162 | | B | | C | | 163 | +----------+ +----------+ | 164 v v 165 /-----------\ /-----------\ 166 / Flexi-grid \ / Flexi-grid \ 167 | transponder | | transponder | 168 \ A / \ E / 169 \-----------/ \-----------/ 170 ^ ^ 171 | +----------+ | 172 | Link 4 |Flexi-grid| Link 5 | 173 '------------>| node |<-----------' 174 | D | 175 +----------+ 176 <--------------------------------------------------> 177 Path y 179 Figure 1. Topology example. 181 After the nodes, links and transponders have been defined using 182 [I-D.draft-vergara-ccamp-flexigrid-yang], we can configure the 183 media-channel from the information we have stored in the 184 flexi-grid TED, by querying which elements are available, and 185 planning the resources that have to be provided on each situation. 186 Note that every element in the flexi-grid TED has a reference, and 187 this is the way in which they are called in the media-channel. 189 1. Depending on the case, it is possible to define either the source 190 and destination node ports, or the source and destination node 191 and transponder. In our case, we would define a network media 192 channel, with source transponder A and source node B, and 193 destination transponder E and destination node C. Thus, we are 194 going to follow path x. 196 2. Then, for each link in the path x, we indicate which channel we 197 are going to use, providing information about the slots, and what 198 nodes are connected. 200 3. Finally, the flexi-grid TED has to be updated with each element 201 usage status each time a media channel is created or torn down. 203 5. Media Channel YANG Model 205 5.1. YANG Model - Tree 207 module: ietf-flexi-grid-media-channel 208 augment /te:te/te:tunnels/te:tunnel: 209 +--rw source-port? fg-ted:flexi-grid-node-port-ref 210 +--rw destination-port? fg-ted:flexi-grid-node-port-ref 211 +--rw effective-freq-slot 212 +--rw N? int32 213 +--rw M? int32 214 augment /te:te/te:tunnels/te:tunnel/te:state: 215 +--ro source-port? fg-ted:flexi-grid-node-port-ref 216 +--ro destination-port? fg-ted:flexi-grid-node-port-ref 217 +--ro effective-freq-slot 218 +--ro N? int32 219 +--ro M? int32 220 augment /te:te/te:lsps-state/te:lsp: 221 +--ro N? int32 222 +--ro M? int32 223 +--ro source-port? fg-ted:flexi-grid-node-port-ref 224 +--ro destination-port? fg-ted:flexi-grid-node-port-ref 225 +--ro link? fg-ted:flexi-grid-link-ref 226 +--ro bidirectional? boolean 228 5.2. YANG Model - Code 230 file "ietf-flexi-grid-media-channel@2017-11-10.yang" 231 module ietf-flexi-grid-media-channel { 232 yang-version 1.1; 234 namespace 235 "urn:ietf:params:xml:ns:yang:ietf-flexi-grid-media-channel"; 236 prefix "fg-mc"; 238 import ietf-flexi-grid-ted { 239 prefix "fg-ted"; 240 } 242 import ietf-te { 243 prefix "te"; 244 } 246 import ietf-network { 247 prefix "nd"; 248 } 249 organization 250 "IETF CCAMP Working Group"; 251 contact 252 "Editor: Jorge Lopez de Vergara 253 "; 255 description 256 "This module contains a collection of YANG definitions for 257 a Flexi-Grid media channel. 259 Copyright (c) 2017 IETF Trust and the persons identified as 260 authors of the code. All rights reserved. 262 Redistribution and use in source and binary forms, with or 263 without modification, is permitted pursuant to, and subject 264 to the license terms contained in, the Simplified BSD 265 License set forth in Section 4.c of the IETF Trust's Legal 266 Provisions Relating to IETF Documents 267 (http://trustee.ietf.org/license-info)."; 269 revision 2017-11-11 { 270 description 271 "version 1."; 273 reference 274 "RFC XXX: A Yang Data Model for Flexi-Grid media-channels"; 275 } 276 grouping flexi-grid-media-channel { 277 description 278 "Media association that represents both the topology 279 (i.e., path through the media) and the resource 280 (frequency slot) that it occupies. As a topological 281 construct, it represents a (effective) frequency slot 282 supported by a concatenation of media elements (fibers, 283 amplifiers, filters, switching matrices...). This term 284 is used to identify the end-to-end physical layer entity 285 with its corresponding (one or more) frequency slots 286 local at each link filters."; 287 reference "rfc7698"; 288 leaf source-port { 289 type fg-ted:flexi-grid-node-port-ref; 290 description "Source port"; 291 } 292 leaf destination-port { 293 type fg-ted:flexi-grid-node-port-ref; 294 description "Destination port"; 295 } 296 container effective-freq-slot { 297 description "The effective frequency slot is an attribute 298 of a media channel and, being a frequency slot, it is 299 described by its nominal central frequency and slot 300 width"; 301 reference "rfc7698"; 302 leaf N { 303 type int32; 304 description 305 "Is used to determine the Nominal Central 306 Frequency. The set of nominal central frequencies 307 can be built using the following expression: 308 f = 193.1 THz + n x 0.00625 THz, 309 where 193.1 THz is ITU-T ''anchor frequency'' for 310 transmission over the C band, n is a positive or 311 negative integer including 0."; 312 reference "rfc7698"; 313 } 314 leaf M { 315 type int32; 316 description 317 "Is used to determine the slot width. A slot width 318 is constrained to be M x SWG (that is, M x 12.5 GHz), 319 where M is an integer greater than or equal to 1."; 320 reference "rfc7698"; 321 } 322 } 323 } 324 grouping link-channel-attributes { 325 description 326 "A link channel is one of the concatenated elements of 327 the media channel."; 328 leaf N { 329 type int32; 330 description 331 "Is used to determine the Nominal Central Frequency. 332 The set of nominal central frequencies can be built 333 using the following expression: 334 f = 193.1 THz + n x 0.00625 THz, 335 where 193.1 THz is ITU-T ''anchor frequency'' for 336 transmission over the C band, n is a positive or 337 negative integer including 0."; 338 reference "rfc7698"; 339 } 340 leaf M { 341 type int32; 342 description 343 "Is used to determine the slot width. A slot 344 width is constrained to be M x SWG (that is, 345 M x 12.5 GHz), where M is an integer greater than 346 or equal to 1."; 347 reference "rfc7698"; 348 } 349 leaf source-port { 350 type fg-ted:flexi-grid-node-port-ref; 351 description "Source port of the link channel"; 352 } 353 leaf destination-port { 354 type fg-ted:flexi-grid-node-port-ref; 355 description "Destination port of the link channel"; 356 } 357 leaf link { 358 type fg-ted:flexi-grid-link-ref; 359 description "Link of the link channel"; 360 } 361 leaf bidirectional { 362 type boolean; 363 description 364 "Determines whether the link is bidirectional or 365 not"; 366 } 367 } 368 /* Augment for media-channel */ 369 augment "/te:te/te:tunnels/te:tunnel" { 370 when "/nd:networks/nd:network/nd:network-types/ 371 fg-ted:flexi-grid-network"{ 372 description "Augment only for Flexigrid network."; 373 } 374 description "Augment tunnel with media-channel config"; 375 uses flexi-grid-media-channel; 377 } 379 augment "/te:te/te:tunnels/te:tunnel/te:state" { 380 when "/nd:networks/nd:network/nd:network-types/ 381 fg-ted:flexi-grid-network"{ 382 description "Augment only for Flexigrid network."; 383 } 384 uses flexi-grid-media-channel; 385 description "Augment tunnel with media-channel state"; 387 } 389 /* Augment for LSP */ 390 augment "/te:te/te:lsps-state/te:lsp" { 391 when "/nd:networks/nd:network/nd:network-types/ 392 fg-ted:flexi-grid-network"{ 393 description "Augment only for Flexigrid network."; 394 } 395 uses link-channel-attributes; 396 description "Augment LSP for paths"; 397 } 399 } 401 403 5.3. License 405 Copyright (c) 2017 IETF Trust and the persons identified as authors 406 of the code. All rights reserved. 408 Redistribution and use in source and binary forms, with or without 409 modification, are permitted provided that the following conditions 410 are met: 412 o Redistributions of source code must retain the above copyright 413 notice, this list of conditions and the following disclaimer. 415 o Redistributions in binary form must reproduce the above copyright 416 notice, this list of conditions and the following disclaimer in 417 the documentation and/or other materials provided with the 418 distribution. 420 o Neither the name of Internet Society, IETF or IETF Trust, nor the 421 names of specific contributors, may be used to endorse or promote 422 products derived from this software without specific prior 423 written permission. 425 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 426 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 427 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS 428 FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE 429 COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, 430 INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, 431 BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 432 LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 433 CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 434 LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN 435 ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 436 POSSIBILITY OF SUCH DAMAGE. 438 6. Security Considerations 440 The transport protocol used for sending the managed information MUST 441 support authentication and SHOULD support encryption. 443 The defined data-model by itself does not create any security 444 implications. 446 7. IANA Considerations 448 The namespace used in the defined models is currently based on the 449 METRO-HAUL project URI. Future versions of this document could 450 register a URI in the IETF XML registry [RFC3688], as well as in the 451 YANG Module Names registry [RFC6020]. 453 8. References 455 8.1. Normative References 457 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 458 Requirement Levels", BCP 14, RFC 2119, March 1997. 460 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 461 the Network Configuration Protocol (NETCONF)", RFC 6020, 462 October 2010. 464 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 465 January 2004. 467 8.2. Informative References 469 [RFC7698] Gonzalez de Dios, O., Casellas, R., Eds. "Framework and 470 Requirements for GMPLS-Based Control of Flexi-Grid Dense 471 Wavelength Division Multiplexing (DWDM) Networks", 472 RFC7698, November 2015. 473 [I-D.draft-vergara-ccamp-flexigrid-yang] Lopez de Vergara, J., 474 Perdices, D., Lopez, V., Gonzalez de Dios, O., King, D., 475 Lee, Y., Galimberti, G., "YANG data model for Flexi-Grid 476 Optical Networks", Internet Draft, 477 draft-vergara-ccamp-flexigrid-yang-05, 2017. 478 [I-D.draft-ietf-teas-yang-te] 479 Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., 480 Bryskin, I., Chen, X., Jones, R., and B. Wen, "A YANG Data 481 Model for Traffic Engineering Tunnels and Interfaces", 482 draft-ietf-teas-yang-te-09, 2017. 484 9. Contributors 486 The model presented in this paper was contributed to by more people 487 than can be listed on the author list. Additional contributors 488 include: 490 o Zafar Ali, Cisco Systems 491 o Daniel Michaud Vallinoto, Universidad Autonoma de Madrid 493 10. Acknowledgments 495 The work presented in this Internet-Draft has been partially funded 496 by the European Commission under the project H2020 METRO-HAUL 497 (Metro High bandwidth, 5G Application-aware optical network, with 498 edge storage, compUte and low Latency), Grant Agreement number: 499 761727, and by the Spanish Ministry of Economy and Competitiveness 500 under the project TRAFICA, MINECO/FEDER TEC2015-69417-C2-1-R. 502 Authors' Addresses 504 Jorge E. Lopez de Vergara 505 Universidad Autonoma de Madrid 506 Escuela Politecnica Superior 507 C/Francisco Tomas y Valiente, 11 508 E-28049 Madrid, Spain 510 Email: jorge.lopez_vergara@uam.es 512 Daniel Perdices Burrero 513 Naudit High Performance Computing and Networking, S.L. 514 C/Faraday, 7 515 E-28049 Madrid, Spain 517 Email: daniel.perdices@naudit.es 519 Victor Lopez 520 Telefonica I+D/GCTO 521 Distrito Telefonica 522 E-28050 Madrid, Spain 524 Email: victor.lopezalvarez@telefonica.com 526 Oscar Gonzalez de Dios 527 Telefonica I+D/GCTO 528 Distrito Telefonica 529 E-28050 Madrid, Spain 531 Email: oscar.gonzalezdedios@telefonica.com 533 Daniel King 534 Lancaster University 536 Email: d.king@lancaster.ac.uk 538 Young Lee 539 Huawei Technologies 541 Email: leeyoung@huawei.com 543 Gabriele Galimberti 544 Cisco Photonics Srl 546 Email: ggalimbe@cisco.com