idnits 2.17.1 draft-ietf-ccamp-layer1-types-08.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 == Line 287 has weird spacing: '...ad-rate uin...' -- The document date (November 2, 2020) is 1243 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-Tg7044' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-Tg709' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-Tgsup43' -- Possible downref: Non-RFC (?) normative reference: ref. 'MEF63' ** Downref: Normative reference to an Informational RFC: RFC 7963 -- Possible downref: Non-RFC (?) normative reference: ref. 'Telcordia' == Outdated reference: A later version (-12) exists of draft-ietf-ccamp-client-signal-yang-03 == Outdated reference: A later version (-25) exists of draft-ietf-ccamp-l1csm-yang-12 == Outdated reference: A later version (-17) exists of draft-ietf-ccamp-otn-topo-yang-11 == Outdated reference: A later version (-20) exists of draft-ietf-ccamp-otn-tunnel-model-11 == Outdated reference: A later version (-17) exists of draft-ietf-ccamp-transport-nbi-app-statement-11 Summary: 1 error (**), 0 flaws (~~), 7 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CCAMP Working Group H. Zheng 3 Internet-Draft I. Busi 4 Intended status: Standards Track Huawei Technologies 5 Expires: May 6, 2021 November 2, 2020 7 A YANG Data Model for Layer 1 Types 8 draft-ietf-ccamp-layer1-types-08 10 Abstract 12 This document defines a collection of common data types and groupings 13 in the YANG data modeling language for use with layer 1 networks. 14 These derived common types and groupings are intended to be imported 15 by modules that specify OTN networks, such as topology, tunnel, 16 client signal adaptation and service. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on May 6, 2021. 35 Copyright Notice 37 Copyright (c) 2020 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. Terminology and Notations . . . . . . . . . . . . . . . . . . 3 54 3. Prefix in Data Node Names . . . . . . . . . . . . . . . . . . 3 55 4. Layer 1 Types Overview . . . . . . . . . . . . . . . . . . . 3 56 4.1. Relationship with other Modules . . . . . . . . . . . . . 3 57 4.2. Content in Layer 1 Type Module . . . . . . . . . . . . . 3 58 4.3. OTN Label and Label Range . . . . . . . . . . . . . . . . 5 59 4.4. ODUflex . . . . . . . . . . . . . . . . . . . . . . . . . 6 60 4.4.1. Resizable ODUflex . . . . . . . . . . . . . . . . . . 8 61 5. YANG Code for Layer1 Types . . . . . . . . . . . . . . . . . 9 62 6. Security Considerations . . . . . . . . . . . . . . . . . . . 29 63 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 64 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30 65 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 30 66 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 31 67 10.1. Normative References . . . . . . . . . . . . . . . . . . 31 68 10.2. Informative References . . . . . . . . . . . . . . . . . 33 69 Appendix A. Examples of OTN Label Ranges . . . . . . . . . . . . 34 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40 72 1. Introduction 74 This document specifies common data types for use in YANG [RFC7950] 75 data models of Layer 1 networks. The derived types and groupings are 76 types applicable to modeling Traffic Engineering (TE) for Layer 1 77 networks. 79 The Optical Transport Networking, a typical Layer 1 network, is 80 specified in [RFC7062]. The corresponding routing and signaling 81 protocol are specified in [RFC7138] and [RFC7139]. The types and 82 groupings defined in this document are consistent to those documents, 83 and can be imported into other Layer 1 data models, including but not 84 limited to, [I-D.ietf-ccamp-otn-topo-yang], 85 [I-D.ietf-ccamp-otn-tunnel-model], 86 [I-D.ietf-ccamp-client-signal-yang] and [I-D.ietf-ccamp-l1csm-yang]. 88 The data model in this draft only defines groupings, typedef and 89 identities. There is no configuration or state data as specified in 90 the Network Management Datastore Architecture [RFC8342]. The 91 document is consistent with other specifications, including [MEF63] 92 for Layer 1 service attributes, [ITU-Tg709] and [ITU-Tgsup43] for OTN 93 data plane definitions. 95 2. Terminology and Notations 97 Refer to [RFC7062] for the key terms used in this document. The 98 terminology for describing YANG data models can be found in 99 [RFC7950]. 101 3. Prefix in Data Node Names 103 In this document, names of data nodes and other data model objects 104 are prefixed using the standard prefix associated with the 105 corresponding YANG imported modules. 107 +-------------+---------------------------+----------------------+ 108 | Prefix | YANG module | Reference | 109 +-------------+---------------------------+----------------------+ 110 | l1-types | ietf-layer1-types | This Document | 111 +-------------+---------------------------+----------------------+ 113 4. Layer 1 Types Overview 115 4.1. Relationship with other Modules 117 This document defines one YANG module for common Layer 1 types. The 118 aim is to specify common Layer 1 TE types (i.e. typedef, identity, 119 grouping) that can be imported by layer 1 specific technology, for 120 example OTN, in its technology-specific modules, such as topology and 121 tunnels. It is worth noting that the generic traffic-engineering 122 (TE) types module is specified in [RFC8776] as ietf-te-types, and 123 both YANG modules, ietf-te-types and ietf-layer1-types, will need 124 importing when the OTN is configured. Generic attributes such as te- 125 bandwidth and te-label, are specified in ietf-te-types in [RFC8776], 126 while the OTN-specific attributes, such as odu-type, are specified in 127 ietf-layer1-types in this document. 129 4.2. Content in Layer 1 Type Module 131 The module ietf-layer1-types contains the following YANG reusable 132 types and groupings: 134 tributary-slot-granularity: 136 This specifies the granularity of the server layer ODU Link (HO ODUk 137 or ODUCn) supporting a client layer ODU LSP (LO ODUj or ODUk, 138 respectively). Three granularities, 1.25G/2.5G/5G, have been 139 specified. 141 odu-type: 143 This specifies the type of ODUk LSP, including the types specified in 144 [RFC7139] and [RFC7963]. 146 client-signal: 148 This specifies the client signal types of OTN networks. The initial 149 input was the G-PID specified in [RFC7139]. Identities for some of 150 the categories of client signal types, including ETH, STM-n, OC 151 [Telcordia] and Fiber Channel, have been specified. 153 otn-label-range-type: 155 The label range type of OTN is represented in one of two ways, 156 tributary slots (TS) and tributary port number (TPN), as specified in 157 [RFC7139]. Two representations are enumerated in the otn-label- 158 range-type. 160 otn-link-bandwidth: 162 This grouping defines the link bandwidth information and could be 163 used in OTN topology model for link bandwidth representation. All 164 the bandwidth related sections in generic module, [RFC8776], need to 165 be augmented with this grouping for the usage of Layer 1. 167 otn-path-bandwidth: 169 This grouping defines the path bandwidth information and could be 170 used in OTN topology model for path bandwidth representation. All 171 the bandwidth related sections in generic module, [RFC8776], need to 172 be augmented with this grouping for the usage of Layer 1. This 173 grouping is also applicable when setting up the OTN tunnel. 175 otn-label-range-info and otn-label-step: 177 These groupings are used to augment an OTN label with type, 178 granularity, priority and ODU types. 180 otn-label-start-end and otn-label-hop: 182 These groupings are used to augment a label for an OTN link and path 183 respectively. 185 optical-interface-func: 187 The optical interface function is specified in [MEF63]. This 188 grouping describes the functionality which encodes bits for 189 transmission and decodes bits upon reception. 191 service-performance-metric: 193 The service performance metric is a quantitative characterization of 194 the quality of the delivery of Layer 1 characteristic information as 195 experienced by the Layer 1 subscriber. 197 4.3. OTN Label and Label Range 199 As described in [RFC7139], the OTN label usually represents the 200 Tributary Port Number (TPN) and the related set of Tributary Slots 201 (TS) assigned to a client layer ODU LSP (LO ODUj or ODUk) on a given 202 server layer ODU (HO-ODU or ODUCn, respectively) Link (e.g., ODU2 LSP 203 over ODU3 Link). Some special OTN label values are also defined for 204 an ODUk LSP being set up over an OTUk Link. 206 The same OTN label must be assigned to the same ODUk LSP at the two 207 ends of an OTN Link. 209 As described in [RFC7139], TPN can be a number from 1 to 4095 and TS 210 are numbered from 1 to 4095, although the actual maximum values 211 depend on the type of server layer ODU. For example, a server layer 212 ODU4 provides 80 time slots (numbered from 1 to 80) and the TPN 213 values can be any number from 1 to 80. 215 The OTN Label Range represents the values for the TPN and TS that are 216 available for ODUk LSPs to be setup over a given OTN Link. 218 The OTN Label Range is defined by the label-restriction list, defined 219 in [RFC8776], which, for OTN, should be augmented using the otn- 220 label-range-info grouping. 222 Each entry in the label-restriction list represents either the range 223 of the available TPN values or the range of the available TS values: 224 the range-type attribute in the otn-label-range-info grouping defines 225 the type of range for each entry of the list. 227 Each entry of the label-restriction list, as defined in [RFC8776], 228 defines a label-start, a label-end, a label-step and a range-bitmap. 229 The label-start and label-end definitions for OTN should be augmented 230 using the otn-label-start-end grouping. The label-step definition 231 for OTN should be augmented using the otn-label-step grouping. It is 232 expected that the otn-label-step will always be equal to its default 233 value (i.e., 1), which is defined in [RFC8776]. 235 As described in [RFC7139], in some cases, the TPN assignment rules 236 are flexible (e.g., ODU4 Link) while in other cases the TPN 237 assignment rules are fixed (e.g., ODU1 Link). In the former case, 238 both TPN and TS ranges are reported, while in the latter case, the 239 TPN range is not reported which indicates that the TPN shall be set 240 equal to the TS number assigned to the ODUk LSP. 242 As described in [RFC7139], in some cases, the TPN assignment rules 243 depends on the TS Granularity (e.g., ODU2 or ODU3 Links). Different 244 entries in the label-restriction list will report different TPN 245 ranges for each TS granularity supported by the link, as indicated by 246 the tsg attribute in the otn-label-range-info grouping. 248 As described in [RFC7139], in some cases the TPN ranges are different 249 for different types of ODUk LSPs. For example, on an ODU2 Link with 250 1.25G TS granularity, the TPN range is 1-4 for ODU1 but 1-8 for ODU0 251 and ODUflex. Different entries in the label-restriction list will 252 report different TPN ranges for different set of ODUk types, as 253 indicated by the odu-type-list in the otn-label-range-info grouping. 255 Appendix A provides some examples of how the TPN and TS label ranges 256 described in Table 3 and Table 4 of [RFC7139] can be represented in 257 YANG using the groupings defined in this document. 259 4.4. ODUflex 261 ODUflex is a type of ODU which has a flexible bit rate which is 262 configured when setting up an ODUflex LSP. 264 [ITU-Tg709], defines six types of ODUflex: ODUflex(CBR), 265 ODUflex(GFP), ODUflex(GFP,n,k), ODUflex(IMP), ODUflex(IMP,s) and 266 ODUflex(FlexE-aware). 268 The main difference between these types of ODUflex is the formula 269 used to calculate the nominal bit rate of the ODUflex, as described 270 in Table 7-2 of [ITU-Tg709]. A YANG choice has been defined to 271 describe these cases: 273 +--rw (oduflex-type)? 274 +--:(generic) 275 | +--rw nominal-bit-rate uint64 276 +--:(cbr) 277 | +--rw client-type identityref 278 +--:(gfp-n-k) 279 | +--rw gfp-n uint8 280 | +--rw gfp-k? l1-types:gfp-k 281 +--:(flexe-client) 282 | +--rw flexe-client 283 | l1-types:flexe-client-rate 284 +--:(flexe-aware) 285 | +--rw flexe-aware-n uint16 286 +--:(packet) 287 +--rw opuflex-payload-rate uint64 289 The 'generic' case has been added to allow the ODUflex nominal bit 290 rate to be defined independently from the type of ODUflex. This 291 could be useful for forward compatibility in the transit domain/nodes 292 where the setup of ODUflex LSPs does not depend on the ODUflex type. 294 In order to simplify interoperability the 'generic' case should be 295 used only when it is needed; the ODUflex type-specific case should be 296 used whenever possible. 298 The 'cbr' case is used for Constant Bit Rate (CBR) client signals. 299 The client-type indicates which CBR client signal is carried by the 300 ODUflex and, implicitly, the client signal bit rate which is then 301 used to calculate the ODUflex(CBR) nominal bit rate as described in 302 Table 7-2 of [ITU-Tg709]. 304 The 'gfp-n-k' case is used for GFP-F mapped client signals based on 305 ODUk.ts and 'n' 1.25G tributary slots. 'gfp-k' defines the nominal 306 bit-rate of the ODUk.ts which, together with the value of 'gfp-n', is 307 used to calculated the ODUflex(GFP,n,k) nominal bit rate as described 308 in Table 7-8 and Table L-7 of [ITU-Tg709] . With a few exceptions, 309 shown in Table L-7 of [ITU-Tg709], the nominal bit-rate of the 310 ODUk.ts could be inferred from the value of 'n', as shown in 311 Table 7-8 of [ITU-Tg709] and therefore the 'gfp-k' is optional. 313 The 'flexe-client' case is used for Idle Mapping Procedure(IMP) 314 mapped FlexE client signals, The 'flexe-client' represents the type 315 of FlexE client carried by the ODUflex which implicitly defines the 316 value of 's' used to calculate the ODUflex(s) nominal bit rate as 317 described in Table 7-2 of [ITU-Tg709]. The '10G' and '40G' 318 enumeration values are used for 10G and 40G FlexE clients to 319 implicitly define the values of s=2 and s=8. For the 'n x 25G' FlexE 320 Clients the value of 'n' is used to defines the value of s=5 x n. 322 The 'flexe-aware' case is used for FlexE-aware client signals. The 323 flexe-aware-n represents the value n (n = n1 + n2 + ... + np) which 324 is used to calculate the ODUflex(FlexE-aware) nominal bit rate as 325 described in Table 7-2 of [ITU-Tg709]. 327 The 'packet' case is used for both the GFP-F mapped client signals 328 and the IMP mapped client signals. The opuflex-payload-rate is 329 either the GFP-F encapsulated-packet client nominal bit rate or the 330 64b/66b encoded-packet client nominal bit rate. The calculation of 331 ODUflex(GFP) nominal bit rate is defined in section 12.2.5 of 332 [ITU-Tg709], and the calculation of ODUflex(IMP) nominal bit rate is 333 defined in section 12.2.6 of [ITU-Tg709]. The same formula is used 334 in both cases. 336 Section 5.1 and 5.2 of [RFC7139] defines two rules to compute the 337 number of tributary slots to be allocated to ODUflex(CBR) and 338 ODUflex(GFP) LSPs when carried over a HO-ODUk link. According to 339 section 19.6 of [ITU-Tg709], the rules in section 5.2 apply only to 340 ODUflex(GFP,n,k) while the rules defined in section 5.1 apply to any 341 other ODUflex type, including, but not limited, to ODUflex(CBR). 342 Section 20.5 of [ITU-Tg709] defines the rules for computing the 343 number of tributary slots to be allocated to ODUflex LSPs when 344 carried over an ODUCn link. 346 Following the [ITU-Tg709] definitions, the rules defined for 347 ODUflex(GFP,n,k) are used only when the 'gfp-n-k' case is used. In 348 all the other cases, including the (generic) case, the rules defined 349 any other ODUflex type are used. 351 The number of available ODUs, defined for each ODUk type, including 352 ODUflex, together with the number of available time-slots, reported 353 as part of the OTN label range, provide sufficient information to 354 infer the OTN link bandwidth availability for ODUflex LSPs. This 355 information is independent of the ODUflex type. 357 4.4.1. Resizable ODUflex 359 Resizable ODUflex is a special type of ODUflex that supports the 360 procedures defined in [ITU-Tg7044] for hitless resizing of the 361 ODUflex nominal bit rate. 363 Two odu-type identities have been defined for ODUflex: 365 o The ODUflex identity, which is used with any type of non-resizable 366 ODUflex, as defined in Table 7-2 of [ITU-Tg709]. 368 o The ODUflex-resizable identity, which is used only with resizable 369 ODUflex(GFP,n,k). 371 These two identities are used to identify whether an ODUflex(GFP,n,k) 372 LSP does or does support the [ITU-Tg7044] hitless resizing 373 procedures. They also identify whether an OTN link only supports the 374 setup of non-resizable ODUflex LSPs or also supports the setup of 375 resizable ODUflex(GFP,n,k) LSP but with different capabilities (e.g., 376 a lower number of LSPs). 378 5. YANG Code for Layer1 Types 380 file "ietf-layer1-types@2020-10-27.yang" 381 module ietf-layer1-types { 382 yang-version 1.1; 383 namespace "urn:ietf:params:xml:ns:yang:ietf-layer1-types"; 384 prefix "l1-types"; 386 organization 387 "IETF CCAMP Working Group"; 388 contact 389 "WG Web: 390 WG List: 392 Editor: Haomian Zheng 393 395 Editor: Italo Busi 396 "; 398 description 399 "This module defines Layer 1 types. The model fully conforms 400 to the Network Management Datastore Architecture (NMDA). 402 Copyright (c) 2020 IETF Trust and the persons 403 identified as authors of the code. All rights reserved. 405 Redistribution and use in source and binary forms, with or 406 without modification, is permitted pursuant to, and subject 407 to the license terms contained in, the Simplified BSD License 408 set forth in Section 4.c of the IETF Trust's Legal Provisions 409 Relating to IETF Documents 410 (https://trustee.ietf.org/license-info). 411 This version of this YANG module is part of RFC XXXX; see 412 the RFC itself for full legal notices."; 414 revision "2020-10-27" { 415 description 416 "Initial Version"; 417 reference 418 "RFC XXXX: A YANG Data Model for Layer 1 Types"; 419 // RFC Editor: replace XXXX with actual RFC number, update date 420 // information and remove this note 421 } 423 /* 424 * Typedefs 425 */ 427 typedef otn-tpn { 428 type uint16 { 429 range "1..4095"; 430 } 431 description 432 "Tributary Port Number for OTN. "; 433 reference 434 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 435 G.709 Optical Transport Networks."; 436 } 438 typedef otn-ts { 439 type uint16 { 440 range "1..4095"; 441 } 442 description 443 "Tributary Slot for OTN. "; 444 reference 445 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 446 G.709 Optical Transport Networks."; 447 } 449 typedef otn-label-range-type { 450 type enumeration { 451 enum trib-slot { 452 description 453 "Defines a range of OTN tributary slots. "; 454 } 455 enum trib-port { 456 description 457 "Defines a range of OTN tributary ports. "; 458 } 459 } 460 description 461 "Defines the type of OTN label range: TS or TPN. "; 462 } 463 typedef gfp-k { 464 type enumeration { 465 enum 2 { 466 description 467 "The ODU2.ts rate (1,249,177.230 kbit/s) is used 468 to compute the rate of an ODUflex(GFP,n,2). "; 469 } 470 enum 3 { 471 description 472 "The ODU3.ts rate (1,254,470.354 kbit/s) is used 473 to compute the rate of an ODUflex(GFP,n,3). "; 474 } 475 enum 4 { 476 description 477 "The ODU4.ts rate (1,301,467.133 kbit/s) is used 478 to compute the rate of an ODUflex(GFP,n,4). "; 479 } 480 } 481 description 482 "The ODUk.ts used to compute the rate of an ODUflex(GFP,n,k)"; 483 reference 484 "Table 7-8 and L-7 of G.709"; 485 } 487 typedef flexe-client-rate { 488 type union { 489 type uint16; 490 type enumeration { 491 enum "10G" { 492 description 493 "Represents a 10G FlexE Client signal (s=2)"; 494 } 495 enum "40G" { 496 description 497 "Represents a 40G FlexE Client signal (s=8)"; 498 } 499 } 500 } 501 description 502 "The FlexE Client signal rate (s x 5,156,250.000 kbit/s) 503 used to compute the rate of an ODUflex(IMP, s). 504 Valid values for s are s=2 (10G), s=4 (40G) and 505 s=5 x n (n x 25G). 506 In the first two cases an enumeration value 507 (either 10G or 40G) is used, while in the latter case 508 the value of n is used"; 509 reference 510 "Table 7-2 of G.709"; 512 } 514 /* 515 * Identities 516 */ 518 identity tributary-slot-granularity { 519 description 520 "Tributary slot granularity"; 521 reference 522 "G.709/Y.1331, February 2016: Interfaces for the Optical 523 Transport Network (OTN)"; 524 } 526 identity tsg-1.25G { 527 base tributary-slot-granularity; 528 description 529 "1.25G tributary slot granularity"; 530 } 532 identity tsg-2.5G { 533 base tributary-slot-granularity; 534 description 535 "2.5G tributary slot granularity"; 536 } 538 identity tsg-5G { 539 base tributary-slot-granularity; 540 description 541 "5G tributary slot granularity"; 542 } 544 identity odu-type { 545 description 546 "Base identity from which specific ODU protocol is derived."; 547 } 549 identity ODU0 { 550 base odu-type; 551 description 552 "ODU0 protocol (1.24Gb/s)."; 553 reference "RFC7139/ITU-T G.709"; 554 } 556 identity ODU1 { 557 base odu-type; 558 description 559 "ODU1 protocol (2.49Gb/s)."; 561 reference "RFC7139/ITU-T G.709"; 562 } 564 identity ODU1e { 565 base odu-type; 566 description 567 "ODU1e protocol (10.35Gb/s)."; 568 reference "RFC7963/ITU-T G.sup43"; 569 } 571 identity ODU2 { 572 base odu-type; 573 description 574 "ODU2 protocol (10.03Gb/s)."; 575 reference "RFC7139/ITU-T G.709"; 576 } 578 identity ODU2e { 579 base odu-type; 580 description 581 "ODU2e protocol (10.39Gb/s)."; 582 reference "RFC7139/ITU-T G.709"; 583 } 585 identity ODU3 { 586 base odu-type; 587 description 588 "ODU3 protocol (40.31Gb/s)."; 589 reference "RFC7139/ITU-T G.709"; 590 } 592 identity ODU3e1 { 593 base odu-type; 594 description 595 "ODU3e1 protocol (41.77Gb/s)."; 596 reference "RFC7963/ITU-T G.sup43"; 597 } 599 identity ODU3e2 { 600 base odu-type; 601 description 602 "ODU3e2 protocol (41.78Gb/s)."; 603 reference "RFC7963/ITU-T G.sup43"; 604 } 606 identity ODU4 { 607 base odu-type; 608 description 609 "ODU4 protocol (104.79Gb/s)."; 610 reference "RFC7139/ITU-T G.709"; 611 } 613 identity ODUflex { 614 base odu-type; 615 description 616 "ODUflex protocol (flexibile bit rate, not resizable). 618 It could be used for any type of ODUflex, including 619 ODUflex(CBR), ODUflex(GFP), ODUflex(GFP,n,k), ODUflex(IMP,s), 620 ODUflex(IMP) and ODUflex(FlexE-aware)."; 621 reference "RFC7139/ITU-T G.709"; 622 } 624 identity ODUflex-resizable { 625 base odu-type; 626 description 627 "ODUflex protocol (flexibile bit rate, resizable). 629 It could be used only for ODUflex(GFP,n,k)."; 630 reference "RFC7139/ITU-T G.709 and ITU-T G.7044"; 631 } 633 identity protocol { 634 description 635 "Base identity from which specific protocol is derived."; 636 reference "MEF63: Subscriber Layer 1 Service Attributes"; 637 } 639 identity Ethernet { 640 base "protocol"; 641 description 642 "Ethernet protocol."; 643 reference "MEF63: Subscriber Layer 1 Service Attributes"; 644 } 646 identity Fibre-Channel { 647 base "protocol"; 648 description 649 "Fibre-Channel (FC) protocol."; 650 reference "MEF63: Subscriber Layer 1 Service Attributes"; 651 } 653 identity SDH { 654 base "protocol"; 655 description 656 "SDH protocol."; 658 reference "MEF63: Subscriber Layer 1 Service Attributes"; 659 } 661 identity SONET { 662 base "protocol"; 663 description 664 "SONET protocol."; 665 reference "MEF63: Subscriber Layer 1 Service Attributes"; 666 } 668 identity client-signal { 669 description 670 "Base identity from which specific client signal is derived"; 671 } 673 identity coding-func { 674 description 675 "Base identity from which specific coding function 676 is derived."; 677 reference "MEF63: Subscriber Layer 1 Service Attributes"; 678 } 680 identity ETH-1Gb { 681 base client-signal; 682 description 683 "Client signal type of 1GbE"; 684 reference "RFC7139/ITU-T G.709"; 685 } 687 identity ETH-10Gb-LAN { 688 base client-signal; 689 description 690 "Client signal type of ETH-10Gb-LAN (10.3 Gb/s)"; 691 reference "RFC7139/ITU-T G.709/IEEE 802.3 Clause 49"; 692 } 694 identity ETH-10Gb-WAN { 695 base client-signal; 696 description 697 "Client signal type of ETH-10Gb-WAN (9.95 Gb/s)"; 698 reference "RFC7139/ITU-T G.709/IEEE 802.3 Clause 50"; 699 } 701 identity ETH-40Gb { 702 base client-signal; 703 description 704 "Client signal type of 40GbE"; 705 reference "RFC7139/ITU-T G.709"; 707 } 709 identity ETH-100Gb { 710 base client-signal; 711 description 712 "Client signal type of 100GbE"; 713 reference "RFC7139/ITU-T G.709"; 714 } 716 identity STM-1 { 717 base client-signal; 718 base "coding-func"; 719 description 720 "Client signal type of STM-1; 721 STM-1 G.707 (N=1) coding function."; 722 reference 723 "RFC7139/ITU-T G.709 724 MEF63: Subscriber Layer 1 Service Attributes"; 725 } 727 identity STM-4 { 728 base client-signal; 729 base "coding-func"; 730 description 731 "Client signal type of STM-4; 732 STM-4 G.707 (N=4) coding function."; 733 reference 734 "RFC7139/ITU-T G.709 735 MEF63: Subscriber Layer 1 Service Attributes"; 736 } 738 identity STM-16 { 739 base client-signal; 740 base "coding-func"; 741 description 742 "Client signal type of STM-16; 743 STM-16 G.707 (N=16) coding function."; 744 reference 745 "RFC7139/ITU-T G.709 746 MEF63: Subscriber Layer 1 Service Attributes"; 747 } 749 identity STM-64 { 750 base client-signal; 751 base "coding-func"; 752 description 753 "Client signal type of STM-64; 754 STM-64 G.707 (N=64) coding function."; 756 reference 757 "RFC7139/ITU-T G.709 758 MEF63: Subscriber Layer 1 Service Attributes"; 759 } 761 identity STM-256 { 762 base client-signal; 763 base "coding-func"; 764 description 765 "Client signal type of STM-256; 766 STM-256 G.707 (N=256) coding function."; 767 reference 768 "RFC7139/ITU-T G.709 769 MEF63: Subscriber Layer 1 Service Attributes"; 770 } 772 identity OC-3 { 773 base client-signal; 774 base "coding-func"; 775 description 776 "Client signal type of OC3; 777 OC-3 GR-253-CORE (N=3) coding function."; 778 reference 779 "ANSI T1.105-1995, Synchronous Optical Network (SONET) 780 Basic Description including Multiplex Structure, Rates, 781 and Formats 782 MEF63: Subscriber Layer 1 Service Attributes"; 783 } 785 identity OC-12 { 786 base client-signal; 787 base "coding-func"; 788 description 789 "Client signal type of OC12; 790 OC-12 GR-253-CORE (N=12) coding function."; 791 reference 792 "ANSI T1.105-1995, Synchronous Optical Network (SONET) 793 Basic Description including Multiplex Structure, Rates, 794 and Formats 795 MEF63: Subscriber Layer 1 Service Attributes"; 796 } 798 identity OC-48 { 799 base client-signal; 800 base "coding-func"; 801 description 802 "Client signal type of OC48; 803 OC-48 GR-253-CORE (N=48) coding function."; 805 reference 806 "ANSI T1.105-1995, Synchronous Optical Network (SONET) 807 Basic Description including Multiplex Structure, Rates, 808 and Formats 809 MEF63: Subscriber Layer 1 Service Attributes"; 810 } 812 identity OC-192 { 813 base client-signal; 814 base "coding-func"; 815 description 816 "Client signal type of OC192; 817 OC-192 GR-253-CORE (N=192) coding function."; 818 reference 819 "ANSI T1.105-1995, Synchronous Optical Network (SONET) 820 Basic Description including Multiplex Structure, Rates, 821 and Formats 822 MEF63: Subscriber Layer 1 Service Attributes"; 823 } 825 identity OC-768 { 826 base client-signal; 827 base "coding-func"; 828 description 829 "Client signal type of OC768; 830 OC-768 GR-253-CORE (N=768) coding function."; 831 reference 832 "ANSI T1.105-1995, Synchronous Optical Network (SONET) 833 Basic Description including Multiplex Structure, Rates, 834 and Formats 835 MEF63: Subscriber Layer 1 Service Attributes"; 836 } 838 identity FC-100 { 839 base client-signal; 840 base "coding-func"; 841 description 842 "Client signal type of Fibre Channel FC-100; 843 FC-100 FC-FS-2 (1.0625 Gb/s) coding function."; 844 reference 845 "RFC7139/ITU-T G.709 846 MEF63: Subscriber Layer 1 Service Attributes"; 847 } 849 identity FC-200 { 850 base client-signal; 851 base "coding-func"; 852 description 853 "Client signal type of Fibre Channel FC-200; 854 FC-200 FC-FS-2 (2.125 Gb/s) coding function."; 855 reference 856 "RFC7139/ITU-T G.709 857 MEF63: Subscriber Layer 1 Service Attributes"; 858 } 860 identity FC-400 { 861 base client-signal; 862 base "coding-func"; 863 description 864 "Client signal type of Fibre Channel FC-400; 865 FC-400 FC-FS-2 (4.250 Gb/s) coding function."; 866 reference 867 "RFC7139/ITU-T G.709 868 MEF63: Subscriber Layer 1 Service Attributes"; 869 } 871 identity FC-800 { 872 base client-signal; 873 base "coding-func"; 874 description 875 "Client signal type of Fibre Channel FC-800; 876 FC-800 FC-FS-2 (8.500 Gb/s) coding function."; 877 reference 878 "RFC7139/ITU-T G.709 879 MEF63: Subscriber Layer 1 Service Attributes"; 880 } 882 identity FC-1200 { 883 base client-signal; 884 base "coding-func"; 885 description 886 "Client signal type of Fibre Channel FC-1200; 887 FC-1200 FC-10GFC (10.51875 Gb/s) coding function."; 888 reference 889 "RFC7139/ITU-T G.709 890 MEF63: Subscriber Layer 1 Service Attributes"; 891 } 893 identity FC-1600 { 894 base client-signal; 895 base "coding-func"; 896 description 897 "Client signal type of Fibre Channel FC-1600; 898 FC-1600 FC-FS-3 (14.025 Gb/s) coding function."; 899 reference 900 "RFC7139/ITU-T G.709 901 MEF63: Subscriber Layer 1 Service Attributes"; 902 } 904 identity FC-3200 { 905 base client-signal; 906 base "coding-func"; 907 description 908 "Client signal type of Fibre Channel FC-3200; 909 FC-3200 FC-FS-4 (28.05 Gb/s) coding function."; 910 reference 911 "RFC7139/ITU-T G.709 912 MEF63: Subscriber Layer 1 Service Attributes"; 913 } 915 identity FICON-4G { 916 base client-signal; 917 description 918 "Client signal type of Fibre Connection 4G"; 919 reference "RFC4328/RFC7139"; 920 } 922 identity FICON-8G { 923 base client-signal; 924 description 925 "Client signal type of Fibre Connection 8G"; 926 reference "RFC4328/RFC7139"; 927 } 929 identity ETH-1000X { 930 base "coding-func"; 931 description 932 "1000BASE-X PCS clause 36 coding function."; 933 reference "MEF63: Subscriber Layer 1 Service Attributes"; 934 } 936 identity ETH-10GW { 937 base "coding-func"; 938 description 939 "10GBASE-W (WAN PHY) PCS clause 49 and WIS clause 50 940 coding function."; 941 reference "MEF63: Subscriber Layer 1 Service Attributes"; 942 } 944 identity ETH-10GR { 945 base "coding-func"; 946 description 947 "10GBASE-R (LAN PHY) PCS clause 49 coding function."; 948 reference "MEF63: Subscriber Layer 1 Service Attributes"; 950 } 952 identity ETH-40GR { 953 base "coding-func"; 954 description 955 "40GBASE-R PCS clause 82 coding function."; 956 reference "MEF63: Subscriber Layer 1 Service Attributes"; 957 } 959 identity ETH-100GR { 960 base "coding-func"; 961 description 962 "100GBASE-R PCS clause 82 coding function."; 963 reference "MEF63: Subscriber Layer 1 Service Attributes"; 964 } 966 identity optical-interface-func { 967 description 968 "Base identity from which optical-interface-function 969 is derived."; 970 reference "MEF63: Subscriber Layer 1 Service Attributes"; 971 } 973 identity SX-PMD-1000 { 974 base "optical-interface-func"; 975 description 976 "SX-PMD-clause-38 Optical Interface function for 977 1000BASE-X PCS-36"; 978 reference "MEF63: Subscriber Layer 1 Service Attributes"; 979 } 981 identity LX-PMD-1000 { 982 base "optical-interface-func"; 983 description 984 "LX-PMD-clause-38 Optical Interface function for 985 1000BASE-X PCS-36"; 986 reference "MEF63: Subscriber Layer 1 Service Attributes"; 987 } 989 identity LX10-PMD-1000 { 990 base "optical-interface-func"; 991 description 992 "LX10-PMD-clause-59 Optical Interface function for 993 1000BASE-X PCS-36"; 994 reference "MEF63: Subscriber Layer 1 Service Attributes"; 995 } 997 identity BX10-PMD-1000 { 998 base "optical-interface-func"; 999 description 1000 "BX10-PMD-clause-59 Optical Interface function for 1001 1000BASE-X PCS-36"; 1002 reference "MEF63: Subscriber Layer 1 Service Attributes"; 1003 } 1005 identity LW-PMD-10G { 1006 base "optical-interface-func"; 1007 description 1008 "LW-PMD-clause-52 Optical Interface function for 1009 10GBASE-W PCS-49-WIS-50"; 1010 reference "MEF63: Subscriber Layer 1 Service Attributes"; 1011 } 1013 identity EW-PMD-10G { 1014 base "optical-interface-func"; 1015 description 1016 "EW-PMD-clause-52 Optical Interface function for 1017 10GBASE-W PCS-49-WIS-50"; 1018 reference "MEF63: Subscriber Layer 1 Service Attributes"; 1019 } 1021 identity LR-PMD-10G { 1022 base "optical-interface-func"; 1023 description 1024 "LR-PMD-clause-52 Optical Interface function for 1025 10GBASE-R PCS-49"; 1026 reference "MEF63: Subscriber Layer 1 Service Attributes"; 1027 } 1029 identity ER-PMD-10G { 1030 base "optical-interface-func"; 1031 description 1032 "ER-PMD-clause-52 Optical Interface function for 1033 10GBASE-R PCS-49"; 1034 reference "MEF63: Subscriber Layer 1 Service Attributes"; 1035 } 1037 identity LR4-PMD-40G { 1038 base "optical-interface-func"; 1039 description 1040 "LR4-PMD-clause-87 Optical Interface function for 1041 40GBASE-R PCS-82"; 1042 reference "MEF63: Subscriber Layer 1 Service Attributes"; 1043 } 1045 identity ER4-PMD-40G { 1046 base "optical-interface-func"; 1047 description 1048 "ER4-PMD-clause-87 Optical Interface function for 1049 40GBASE-R PCS-82"; 1050 reference "MEF63: Subscriber Layer 1 Service Attributes"; 1051 } 1053 identity FR-PMD-40G { 1054 base "optical-interface-func"; 1055 description 1056 "FR-PMD-clause-89 Optical Interface function for 1057 40GBASE-R PCS-82"; 1058 reference "MEF63: Subscriber Layer 1 Service Attributes"; 1059 } 1061 identity LR4-PMD-100G { 1062 base "optical-interface-func"; 1063 description 1064 "LR4-PMD-clause-88 Optical Interface function for 1065 100GBASE-R PCS-82"; 1066 reference "MEF63: Subscriber Layer 1 Service Attributes"; 1067 } 1069 identity ER4-PMD-100G { 1070 base "optical-interface-func"; 1071 description 1072 "ER4-PMD-clause-88 Optical Interface function for 1073 100GBASE-R PCS-82"; 1074 reference "MEF63: Subscriber Layer 1 Service Attributes"; 1075 } 1077 /* 1078 * Groupings 1079 */ 1081 grouping otn-link-bandwidth { 1082 description "link bandwidth attributes for OTN"; 1083 list odulist { 1084 key "odu-type"; 1085 description 1086 "OTN bandwidth definition"; 1087 leaf odu-type { 1088 type identityref { 1089 base odu-type; 1090 } 1091 description "ODU type"; 1092 } 1093 leaf number { 1094 type uint16; 1095 description "Number of ODUs"; 1096 } 1097 } 1098 } 1100 grouping otn-path-bandwidth { 1101 description 1102 "path bandwidth attributes grouping for OTN"; 1104 container otn { 1105 description 1106 "path bandwidth attributes for OTN"; 1107 leaf odu-type { 1108 type identityref { 1109 base odu-type; 1110 } 1111 description "ODU type"; 1112 } 1113 choice oduflex-type { 1114 when 'derived-from-or-self(./odu-type,"ODUflex") or 1115 derived-from-or-self(./odu-type,"ODUflex-resizable")'{ 1116 description 1117 "applicable when odu-type is ODUflex or 1118 ODUflex-resizable"; 1119 } 1120 description 1121 "Types of ODUflex used to compute the ODUflex 1122 nominal bit rate."; 1123 reference 1124 "Table 7-2 of G.709"; 1125 case generic { 1126 leaf nominal-bit-rate { 1127 type uint64; 1128 units "bps"; 1129 mandatory true; 1130 description 1131 "Nominal ODUflex bit rate."; 1132 } 1133 } 1134 case cbr { 1135 leaf client-type { 1136 type identityref { 1137 base client-signal; 1138 } 1139 mandatory true; 1140 description 1141 "The CBR client signal for an ODUflex(CBR)."; 1143 } 1144 } 1145 case gfp-n-k { 1146 leaf gfp-n { 1147 type uint8 { 1148 range "1..80"; 1149 } 1150 mandatory true; 1151 description 1152 "The value of n for an ODUflex(GFP,n,k)."; 1153 reference 1154 "Tables 7-8 and L-7 of G.709"; 1155 } 1156 leaf gfp-k { 1157 type gfp-k; 1158 description 1159 "The value of k for an ODUflex(GFP,n,k). 1160 If omitted, it is calculated from the value of gfp-n 1161 as described in Table 7-8 of G.709"; 1162 reference 1163 "Tables 7-8 and L-7 of G.709"; 1164 } 1165 } 1166 case flexe-client { 1167 leaf flexe-client { 1168 type flexe-client-rate; 1169 mandatory true; 1170 description 1171 "The rate of the FlexE-client for an ODUflex(IMP,s)."; 1172 } 1173 } 1174 case flexe-aware { 1175 leaf flexe-aware-n { 1176 type uint16; 1177 mandatory true; 1178 description 1179 "The rate of FlexE-aware client signal 1180 for ODUflex(FlexE-aware)"; 1181 } 1182 } 1183 case packet { 1184 leaf opuflex-payload-rate { 1185 type uint64; 1186 units "Kbps"; 1187 mandatory true; 1188 description 1189 "Either the GFP-F encapsulated packet client nominal 1190 bit rate for an ODUflex(GFP) or the 64b/66b encoded 1191 packet client nominal bit rate for an ODUflex(IMP)."; 1192 } 1193 } 1194 } 1195 } 1196 } 1198 grouping otn-label-range-info { 1199 description 1200 "label range information for OTN, is dependent on the 1201 range-type, must be used together with the following 1202 groupings: otn-label-start-end and otn-label-step. "; 1203 leaf range-type { 1204 type otn-label-range-type; 1205 description "The type of range (e.g., TPN or TS) 1206 to which the label range applies"; 1207 } 1208 leaf tsg { 1209 type identityref { 1210 base tributary-slot-granularity; 1211 } 1212 description 1213 "Tributary slot granularity (TSG) to which the label range 1214 applies. 1215 This leaf shall be present when the range-type is TS; 1216 This leaf can be omitted when mapping an ODUk over an OTUk 1217 Link. In this case the range-type is tpn, with only one 1218 entry (ODUk), and the tpn range has only one value (1)."; 1219 reference 1220 "G.709/Y.1331, February 2016: Interfaces for the 1221 Optical Transport Network (OTN)"; 1222 } 1223 leaf-list odu-type-list { 1224 type identityref { 1225 base odu-type; 1226 } 1227 description 1228 "List of ODU types to which the label range applies. 1229 An Empty odu-type-list means that the label range 1230 applies to all the supported ODU types."; 1231 } 1232 leaf priority { 1233 type uint8; 1234 description 1235 "Priority in Interface Switching Capability 1236 Descriptor (ISCD)."; 1237 reference "RFC4203."; 1238 } 1240 } 1242 grouping otn-label-start-end { 1243 description 1244 "The OTN label-start or label-end used to specify an OTN label 1245 range. this grouping is dependent on the range-type, 1246 must be used together with the following groupings: 1247 otn-label-range-info and otn-label-step."; 1248 choice range-type { 1249 description 1250 "OTN label range type, either TPN range or TS range"; 1251 case trib-port { 1252 leaf otn-tpn { 1253 when "../../../range-type = 'trib-port'" { 1254 description 1255 "valid only when range-type represented by trib-port"; 1256 } 1257 type otn-tpn; 1258 description 1259 "Tributary Port Number."; 1260 reference 1261 "RFC7139: GMPLS Signaling Extensions for Control of 1262 Evolving G.709 Optical Transport Networks."; 1263 } 1264 } 1265 case trib-slot { 1266 leaf otn-ts { 1267 when "../../../range-type = 'trib-slot'" { 1268 description 1269 "valid only when range-type represented by trib-slot"; 1270 } 1271 type otn-ts; 1272 description 1273 "Tributary Slot Number."; 1274 reference 1275 "RFC7139: GMPLS Signaling Extensions for Control of 1276 Evolving G.709 Optical Transport Networks."; 1277 } 1278 } 1279 } 1280 } 1282 grouping otn-label-hop { 1283 description "OTN Label. "; 1284 reference "RFC7139, section 6. "; 1285 leaf otn-tpn { 1286 type otn-tpn; 1287 description 1288 "Tributary Port Number."; 1289 reference 1290 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1291 G.709 Optical Transport Networks."; 1292 } 1293 leaf tsg { 1294 type identityref { 1295 base tributary-slot-granularity; 1296 } 1297 description "Tributary slot granularity."; 1298 reference 1299 "G.709/Y.1331, February 2016: Interfaces for the 1300 Optical Transport Network (OTN)"; 1301 } 1302 leaf ts-list { 1303 type string { 1304 pattern "([1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?" 1305 + "(,[1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?)*)"; 1306 } 1307 description 1308 "A list of available tributary slots ranging 1309 between 1 and 4095. If multiple values or 1310 ranges are given, they all must be disjoint 1311 and must be in ascending order. 1312 For example 1-20,25,50-1000."; 1313 reference 1314 "RFC 7139: GMPLS Signaling Extensions for Control 1315 of Evolving G.709 Optical Transport Networks"; 1316 } 1317 } 1319 grouping otn-label-step { 1320 description 1321 "Label step for OTN, is dependent on the range-type, 1322 must be used together with the following groupings: 1323 otn-label-range-info and otn-label-start-end. "; 1324 choice range-type { 1325 description 1326 "OTN label range type, either TPN range or TS range"; 1327 case trib-port { 1328 leaf otn-tpn { 1329 when "../../range-type = 'trib-port'" { 1330 description 1331 "valid only when range-type represented by trib-port"; 1332 } 1333 type otn-tpn; 1334 description 1335 "Label step which represents possible increments for 1336 Tributary Port Number."; 1337 reference 1338 "RFC7139: GMPLS Signaling Extensions for Control of 1339 Evolving G.709 Optical Transport Networks."; 1340 } 1341 } 1342 case trib-slot { 1343 leaf otn-ts { 1344 when "../../range-type = 'trib-slot'" { 1345 description 1346 "valid only when range-type represented by trib-slot"; 1347 } 1348 type otn-ts; 1349 description 1350 "Label step which represents possible increments for 1351 Tributary Slot Number."; 1352 reference 1353 "RFC7139: GMPLS Signaling Extensions for Control of 1354 Evolving G.709 Optical Transport Networks."; 1355 } 1356 } 1357 } 1358 } 1359 } 1360 1362 6. Security Considerations 1364 The YANG module specified in this document defines a schema for data 1365 that is designed to be accessed via network management protocols such 1366 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 1367 is the secure transport layer, and the mandatory-to-implement secure 1368 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 1369 is HTTPS, and the mandatory-to-implement secure transport is TLS 1370 [RFC8446]. 1372 The NETCONF access control model [RFC8341] provides the means to 1373 restrict access for particular NETCONF or RESTCONF users to a 1374 preconfigured subset of all available NETCONF or RESTCONF protocol 1375 operations and content. 1377 The YANG module in this document defines layer 1 type definitions 1378 (i.e., typedef, identity and grouping statements) in YANG data 1379 modeling language to be imported and used by other layer 1 1380 technology-specific modules. When imported and used, the resultant 1381 schema will have data nodes that can be writable, or readable. The 1382 access to such data nodes may be considered sensitive or vulnerable 1383 in some network environments. Write operations (e.g., edit-config) 1384 to these data nodes without proper protection can have a negative 1385 effect on network operations. 1387 The security considerations spelled out in the YANG 1.1 specification 1388 [RFC7950] apply for this document as well. 1390 7. IANA Considerations 1392 It is proposed that IANA should assign new URIs from the "IETF XML 1393 Registry" [RFC3688] as follows: 1395 URI: urn:ietf:params:xml:ns:yang:ietf-layer1-types 1396 Registrant Contact: The IESG 1397 XML: N/A; the requested URI is an XML namespace. 1399 This document registers following YANG modules in the YANG Module 1400 Names registry [RFC7950]. 1402 name: ietf-layer1-types 1403 namespace: urn:ietf:params:xml:ns:yang:ietf-layer1-types 1404 prefix: l1-types 1405 reference: RFC XXXX 1407 8. Acknowledgements 1409 The authors and the working group give their sincere thanks for 1410 Robert Wilton for the YANG doctor review, and Tom Petch for his 1411 comments during the model and document development. 1413 9. Contributors 1415 Dieter Beller 1416 Nokia 1417 Email: dieter.beller@nokia.com 1419 Sergio Belotti 1420 Nokia 1421 Email: sergio.belotti@nokia.com 1423 Yanlei Zheng 1424 China Unicom 1425 Email: zhengyanlei@chinaunicom.cn 1426 Aihua Guo 1427 Futurewei Technologies 1428 Email: aihuaguo@futurewei.com 1430 Young Lee 1431 Samsung 1432 Email: younglee.tx@gmail.com 1434 Lei Wang 1435 China Mobile 1436 Email: wangleiyj@chinamobile.com 1438 Oscar Gonzalez de Dios 1439 Telefonica 1440 Email: oscar.gonzalezdedios@telefonica.com 1442 Xufeng Liu 1443 Volta Networks 1444 Email: xufeng.liu.ietf@gmail.com 1446 Yunbin Xu 1447 CAICT 1448 Email: xuyunbin@caict.ac.cn 1450 Anurag Sharma 1451 Google 1452 Email: ansha@google.com 1454 Rajan Rao 1455 Infinera 1456 Email: rrao@infinera.com 1458 Victor Lopez 1459 Telefonica 1460 Email: victor.lopezalvarez@telefonica.com 1462 Yunbo Li 1463 China Mobile 1464 Email: liyunbo@chinamobile.com 1466 10. References 1468 10.1. Normative References 1470 [ITU-Tg7044] 1471 International Telecommunication Union, "Hitless adjustment 1472 of ODUflex(GFP)", ITU-T G.7044, October 2011. 1474 [ITU-Tg709] 1475 International Telecommunication Union, "Interfaces for the 1476 optical transport network", ITU-T G.709, March 2020. 1478 [ITU-Tgsup43] 1479 International Telecommunication Union, "Transport of IEEE 1480 10GBASE-R in optical transport networks (OTN)", 1481 ITU-T G.sup43, February 2011. 1483 [MEF63] Metro Ethernet Forum, "Subscriber Layer1 Service 1484 Attributes Technical Specification", MEF 63, August 2018. 1486 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1487 DOI 10.17487/RFC3688, January 2004, 1488 . 1490 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 1491 and A. Bierman, Ed., "Network Configuration Protocol 1492 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 1493 . 1495 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 1496 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 1497 . 1499 [RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, D., 1500 and K. Pithewan, "GMPLS Signaling Extensions for Control 1501 of Evolving G.709 Optical Transport Networks", RFC 7139, 1502 DOI 10.17487/RFC7139, March 2014, 1503 . 1505 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 1506 RFC 7950, DOI 10.17487/RFC7950, August 2016, 1507 . 1509 [RFC7963] Ali, Z., Bonfanti, A., Hartley, M., and F. Zhang, "RSVP-TE 1510 Extension for Additional Signal Types in G.709 Optical 1511 Transport Networks (OTNs)", RFC 7963, 1512 DOI 10.17487/RFC7963, August 2016, 1513 . 1515 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 1516 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 1517 . 1519 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 1520 Access Control Model", STD 91, RFC 8341, 1521 DOI 10.17487/RFC8341, March 2018, 1522 . 1524 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 1525 and R. Wilton, "Network Management Datastore Architecture 1526 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 1527 . 1529 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 1530 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 1531 . 1533 [RFC8776] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, 1534 "Common YANG Data Types for Traffic Engineering", 1535 RFC 8776, DOI 10.17487/RFC8776, June 2020, 1536 . 1538 [Telcordia] 1539 Telcordia, "Synchronous Optical Network Transport Systems: 1540 Common Generic Criteria, Issue 5", Telcordia GR-253-CORE, 1541 October 2009. 1543 10.2. Informative References 1545 [I-D.ietf-ccamp-client-signal-yang] 1546 Zheng, H., Guo, A., Busi, I., Snitser, A., Lazzeri, F., 1547 Xu, Y., Zhao, Y., Liu, X., and G. Fioccola, "A YANG Data 1548 Model for Transport Network Client Signals", draft-ietf- 1549 ccamp-client-signal-yang-03 (work in progress), July 2020. 1551 [I-D.ietf-ccamp-l1csm-yang] 1552 Lee, Y., Lee, K., Zheng, H., Dios, O., and D. Ceccarelli, 1553 "A YANG Data Model for L1 Connectivity Service Model 1554 (L1CSM)", draft-ietf-ccamp-l1csm-yang-12 (work in 1555 progress), September 2020. 1557 [I-D.ietf-ccamp-otn-topo-yang] 1558 Zheng, H., Busi, I., Liu, X., Belotti, S., and O. Dios, "A 1559 YANG Data Model for Optical Transport Network Topology", 1560 draft-ietf-ccamp-otn-topo-yang-11 (work in progress), 1561 September 2020. 1563 [I-D.ietf-ccamp-otn-tunnel-model] 1564 Zheng, H., Busi, I., Belotti, S., Lopez, V., and Y. Xu, 1565 "OTN Tunnel YANG Model", draft-ietf-ccamp-otn-tunnel- 1566 model-11 (work in progress), September 2020. 1568 [I-D.ietf-ccamp-transport-nbi-app-statement] 1569 Busi, I., King, D., Zheng, H., and Y. Xu, "Transport 1570 Northbound Interface Applicability Statement", draft-ietf- 1571 ccamp-transport-nbi-app-statement-11 (work in progress), 1572 July 2020. 1574 [RFC7062] Zhang, F., Ed., Li, D., Li, H., Belotti, S., and D. 1575 Ceccarelli, "Framework for GMPLS and PCE Control of G.709 1576 Optical Transport Networks", RFC 7062, 1577 DOI 10.17487/RFC7062, November 2013, 1578 . 1580 [RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and 1581 J. Drake, "Traffic Engineering Extensions to OSPF for 1582 GMPLS Control of Evolving G.709 Optical Transport 1583 Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014, 1584 . 1586 [RFC8792] Watsen, K., Auerswald, E., Farrel, A., and Q. Wu, 1587 "Handling Long Lines in Content of Internet-Drafts and 1588 RFCs", RFC 8792, DOI 10.17487/RFC8792, June 2020, 1589 . 1591 Appendix A. Examples of OTN Label Ranges 1593 This appendix provides some examples of how the TPN and TS label 1594 ranges described in Table 3 and Table 4 of [RFC7139] can be 1595 represented in YANG using the groupings defined in this document. 1597 It also considers the OTUk links in addition to HO-ODUk links. 1599 The JSON code examples provided in this appendix provides some 1600 embedded comments following the conventions in section 3.2 of 1601 [I-D.ietf-ccamp-transport-nbi-app-statement] and have been folded 1602 using the tool in [RFC8792]. 1604 ========== NOTE: '\\' line wrapping per BCP XXX (RFC XXXX) ========== 1606 { 1607 "examples of label-restrictions for different OTN Links": [ 1608 { 1609 "// ": "HO-ODU1 or OTU1 Link", 1610 "label-restrictions": { 1611 "label-restriction": [ 1612 { 1613 "index ": 1, 1614 "// ___DEFAULT___ restriction": "inclusive", 1615 "range-type": "label-range-trib-port", 1616 "// ___NOT-PRESENT___ tsg": "", 1617 "odu-type-list": "[ ODU1 ]", 1618 "// ___DEFAULT___ priority": 7, 1619 "// tpn-range": 1, 1620 "// ___ COMMENT ___": "Since no TS range and no TSG are \ 1621 \reported for ODU1, the link is an OTU1 Link. TS allocation is not n\ 1622 \eeded and TPN shall be set to '1' for mapping ODU1 over OTU1. This \ 1623 \entry is not present if the OTN Link is an HO-ODU1 Link." 1624 }, 1625 { 1626 "index ": 2, 1627 "// ___DEFAULT___ restriction": "inclusive", 1628 "range-type": "label-range-trib-slot", 1629 "tsg": "tsg-1.25G", 1630 "odu-type-list": "[ ODU0 ]", 1631 "// ts-range": "1-2", 1632 "// ___ COMMENT ___": "Since no TPN range is reportd for\ 1633 \ ODU0 with 1.25G TSG, the TPN allocation rule is fixed (TPN = TS#) \ 1634 \for mapping LO-ODU0 over HO-ODU1 with 1.25G TSG. See Table 4 of [RF\ 1635 \C7139]." 1636 } 1637 ] 1638 } 1639 }, 1640 { 1641 "// ": "HO-ODU2 or OTU2 Link", 1642 "label-restrictions": { 1643 "label-restriction": [ 1644 { 1645 "index ": 1, 1646 "// ___DEFAULT___ restriction": "inclusive", 1647 "range-type": "label-range-trib-port", 1648 "// ___NOT-PRESENT___ tsg": "", 1649 "odu-type-list": "[ ODU2 ]", 1650 "// ___ DEFAULT ___ priority": 7, 1651 "// tpn-range": 1, 1652 "// ___ COMMENT ___": "Since no TS range and no TSG are \ 1653 \reported for ODU2, the link is an OTU2 Link. TS allocation is not n\ 1654 \eeded and TPN shall be set to '1' for mapping ODU2 over OTU2. This \ 1655 \entry is not present if the OTN Link is an HO-ODU2 Link." 1656 }, 1657 { 1658 "index ": 2, 1659 "// ___DEFAULT___ restriction": "inclusive", 1660 "range-type": "label-range-trib-slot", 1661 "tsg": "tsg-1.25G", 1662 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ 1664 \ ]", 1665 "// ___ DEFAULT ___ priority": 7, 1666 "// ts-range": "1-8" 1667 }, 1668 { 1669 "index ": 3, 1670 "// ___DEFAULT___ restriction": "inclusive", 1671 "range-type": "label-range-trib-port", 1672 "tsg": "tsg-1.25G ", 1673 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0 ]", 1674 "// ___ DEFAULT ___ priority": 7, 1675 "// tpn-range": "1-8", 1676 "// ___ COMMENT ___": "Since this TPN range is reported \ 1677 \for ODUflex and ODU0 with 1.25G TSG, the TPN assignment rule is fle\ 1678 \xible within a common range for mapping LO-ODUflex and LO-ODU0 over\ 1679 \ HO-ODU2 with 1.25G TSG. See Table 4 of [RFC7139]." 1680 }, 1681 { 1682 "index ": 4, 1683 "// ___DEFAULT___ restriction": "inclusive", 1684 "range-type": "label-range-trib-port", 1685 "tsg": "tsg-1.25G", 1686 "odu-type-list": "[ ODU1 ]", 1687 "// ___ DEFAULT ___ priority": 7, 1688 "// tpn-range": "1-4", 1689 "// ___ COMMENT ___": "Since this TPN range is reported \ 1690 \for ODU1 with 1.25G TSG, the TPN assignment rule is flexible within\ 1691 \ a common range for mapping LO-ODU1 over HO-ODU2 with 1.25G TSG. Se\ 1692 \e Table 4 of [RFC7139]." 1693 }, 1694 { 1695 "index ": 5, 1696 "// ___DEFAULT___ restriction": "inclusive", 1697 "range-type": "label-range-trib-slot", 1698 "tsg": "tsg-2.5G", 1699 "odu-type-list": "[ ODU1 ]", 1700 "// ___ DEFAULT ___ priority": 7, 1701 "// ts-range": "1-4", 1702 "// ___ COMMENT ___": "Since no TPN range is reported fo\ 1703 \r ODU1 with 2.5G TSG, the TPN allocation rule is fixed (TPN = TS#) \ 1704 \for mapping LO-ODU1 over HO-ODU2 with 2.5G TSG. See Table 3 of [RFC\ 1705 \7139]." 1706 } 1707 ] 1708 } 1709 }, 1710 { 1711 "// ": "HO-ODU3 or OTU3 Link", 1712 "label-restrictions": { 1713 "label-restriction": [ 1714 { 1715 "index ": 1, 1716 "// ___DEFAULT___ restriction": "inclusive", 1717 "range-type": "label-range-trib-port", 1718 "// ___NOT-PRESENT___ tsg": "", 1719 "odu-type-list": "[ ODU3 ]", 1720 "// ___ DEFAULT ___ priority": 7, 1721 "// tpn-range": 1, 1722 "// ___ COMMENT ___": "Since no TS range and no TSG are \ 1723 \reported for ODU3, the link is an OTU3 Link. TS allocation is not n\ 1724 \eeded and TPN shall be set to '1' for mapping ODU3 over OTU3. This \ 1725 \entry is not present if the OTN Link is an HO-ODU3 Link." 1726 }, 1727 { 1728 "index ": 2, 1729 "// ___DEFAULT___ restriction": "inclusive", 1730 "range-type": "label-range-trib-slot", 1731 "tsg": "tsg-1.25G", 1732 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ 1733 \, ODU2, ODU2e ]", 1734 "// ___ DEFAULT ___ priority": 7, 1735 "// ts-range": "1-32" 1736 }, 1737 { 1738 "index ": 3, 1739 "// ___DEFAULT___ restriction": "inclusive", 1740 "range-type": "label-range-trib-port", 1741 "tsg": "tsg-1.25G", 1742 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU2\ 1743 \e ]", 1744 "// ___ DEFAULT ___ priority": 7, 1745 "// tpn-range": "1-32", 1746 "// ___ COMMENT ___": "Since this TPN range is reported \ 1747 \for ODUflex, ODU0 and ODU2e with 1.25G TSG, the TPN assignment rule\ 1748 \ is flexible within a common range for mapping LO-ODUflex, LO-ODU0 \ 1749 \and LO-ODU2e over HO-ODU3 with 1.25G TSG. See Table 4 of [RFC7139]." 1750 }, 1751 { 1752 "index ": 4, 1753 "// ___DEFAULT___ restriction": "inclusive", 1754 "range-type": "label-range-trib-port", 1755 "tsg": "tsg-1.25G", 1756 "odu-type-list": "[ ODU1 ]", 1757 "// ___ DEFAULT ___ priority": 7, 1758 "// tpn-range": "1-16", 1759 "// ___ COMMENT ___": "Since this TPN range is reported \ 1761 \for ODU1 with 1.25G TSG, the TPN assignment rule is flexible within\ 1762 \ a common range for mapping LO-ODU1 over HO-ODU3 with 1.25G TSG. Se\ 1763 \e Table 4 of [RFC7139]." 1764 }, 1765 { 1766 "index ": 5, 1767 "// ___DEFAULT___ restriction": "inclusive", 1768 "range-type": "label-range-trib-port", 1769 "tsg": "tsg-1.25G", 1770 "odu-type-list": "[ ODU2 ]", 1771 "// ___ DEFAULT ___ priority": 7, 1772 "// tpn-range": "1-4", 1773 "// ___ COMMENT ___": "Since this TPN range is reported \ 1774 \for ODU2 with 1.25G TSG, the TPN assignment rule is flexible within\ 1775 \ a common range for mapping LO-ODU2 over HO-ODU3 with 1.25G TSG. Se\ 1776 \e Table 4 of [RFC7139]." 1777 }, 1778 { 1779 "index ": 6, 1780 "// ___DEFAULT___ restriction": "inclusive", 1781 "range-type": "label-range-trib-slot", 1782 "tsg": "tsg-2.5G", 1783 "odu-type-list": "[ ODU1, ODU2 ]", 1784 "// ___ DEFAULT ___ priority": 7, 1785 "// ts-range": "1-16" 1786 }, 1787 { 1788 "index ": 7, 1789 "// ___DEFAULT___ restriction": "inclusive", 1790 "range-type": "label-range-trib-port", 1791 "tsg": "tsg-2.5G ", 1792 "odu-type-list": "[ ODU2 ]", 1793 "// ___ DEFAULT ___ priority": 7, 1794 "// tpn-range": "1-4", 1795 "// ___ COMMENT ___": "Since this TPN range is reported \ 1796 \for ODU2 with 2.5G TSG, the TPN assignment rule is flexible within \ 1797 \a common range for mapping LO-ODU2 over HO-ODU3. Since no TPN range\ 1798 \ is reported for ODU1 with 2.5G TSG, the TPN allocation rule is fix\ 1799 \ed (TPN = TS#) for mapping LO-ODU1 over HO-ODU3 with 2.5G TSG. See \ 1800 \Table 3 of [RFC7139]." 1801 } 1802 ] 1803 } 1804 }, 1805 { 1806 "// ": "HO-ODU4 or OTU4 Link", 1807 "label-restrictions": { 1808 "label-restriction": [ 1809 { 1810 "index ": 1, 1811 "// ___DEFAULT___ restriction": "inclusive", 1812 "range-type": "label-range-trib-port", 1813 "// ___NOT-PRESENT___ tsg": "", 1814 "odu-type-list": "[ ODU4 ]", 1815 "// ___ DEFAULT ___ priority": 7, 1816 "// tpn-range": 1, 1817 "// ___ COMMENT ___": "Since no TS range and no TSG are \ 1818 \reported for ODU4, the link is an OTU4 Link. TS allocation is not n\ 1819 \eeded and TPN shall be set to '1' for mapping ODU4 over OTU4. This \ 1820 \entry is not present if the OTN Link is an HO-ODU4 Link." 1821 }, 1822 { 1823 "index ": 2, 1824 "// ___DEFAULT___ restriction": "inclusive", 1825 "range-type": "label-range-trib-slot", 1826 "tsg": "tsg-1.25G", 1827 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ 1828 \, ODU2, ODU2e, ODU3 ]", 1829 "// ___ DEFAULT ___ priority": 7, 1830 "// ts-range": "1-80" 1831 }, 1832 { 1833 "index ": 3, 1834 "// ___DEFAULT___ restriction": "inclusive", 1835 "range-type": "label-range-trib-port", 1836 "tsg": "tsg-1.25G", 1837 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ 1838 \, ODU2, ODU2e, ODU3 ]", 1839 "// ___ DEFAULT ___ priority": 7, 1840 "// tpn-range": "1-80", 1841 "// ___ COMMENT ___": "Since this TPN range is reported \ 1842 \for any LO-ODUj with 1.25G TSG, the TPN assignment rule is flexible\ 1843 \ within a common range for mapping any LO-ODUj over HO-ODU4 with 1.\ 1844 \25G TSG. See Table 4 of [RFC7139]." 1845 } 1846 ] 1847 } 1848 }, 1849 { 1850 "// ": "ODUC1 Link", 1851 "label-restrictions": { 1852 "label-restriction": [ 1853 { 1854 "index ": 1, 1855 "// ___DEFAULT___ restriction": "inclusive", 1856 "range-type": "label-range-trib-slot", 1857 "tsg": "tsg-5G", 1858 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ 1859 \, ODU2, ODU2e, ODU3, ODU4 ]", 1860 "// ___ DEFAULT ___ priority": 7, 1861 "// ts-range": "1-20", 1862 "// ___ COMMENT ___": "Since the TS range is specified f\ 1863 \or any ODUk, the OTN Link is an ODUCn Link." 1864 }, 1865 { 1866 "index ": 2, 1867 "// ___DEFAULT___ restriction": "inclusive", 1868 "range-type": "label-range-trib-port", 1869 "tsg": "tsg-5G", 1870 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ 1871 \, ODU2, ODU2e, ODU3, ODU4 ]", 1872 "// ___ DEFAULT ___ priority": 7, 1873 "// tpn-range": "1-10", 1874 "// ___ COMMENT ___": "Since this TPN range is reported \ 1875 \for any ODUk with 5G TSG, the TPN assignment rule is flexible withi\ 1876 \n a common range for mapping any ODUk over ODUCn with 5G TSG." 1877 } 1878 ] 1879 } 1880 } 1881 ] 1882 } 1884 Authors' Addresses 1886 Haomian Zheng 1887 Huawei Technologies 1888 H1, Huawei Xiliu Beipo Village, Songshan Lake 1889 Dongguan, Guangdong 523808 1890 China 1892 Email: zhenghaomian@huawei.com 1894 Italo Busi 1895 Huawei Technologies 1896 Milan 1897 Italy 1899 Email: Italo.Busi@huawei.com