idnits 2.17.1 draft-ietf-ccamp-layer1-types-09.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 (February 19, 2021) is 1156 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) == Unused Reference: 'IEEE' is defined on line 1676, but no explicit reference was found in the text == Unused Reference: 'RFC4203' is defined on line 1699, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'ANSI' -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE' -- 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 == Outdated reference: A later version (-12) exists of draft-ietf-ccamp-client-signal-yang-04 == Outdated reference: A later version (-26) exists of draft-ietf-ccamp-l1csm-yang-13 == Outdated reference: A later version (-18) 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-12 Summary: 1 error (**), 0 flaws (~~), 9 warnings (==), 7 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: August 23, 2021 February 19, 2021 7 A YANG Data Model for Layer 1 Types 8 draft-ietf-ccamp-layer1-types-09 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 August 23, 2021. 35 Copyright Notice 37 Copyright (c) 2021 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 . . . . . . . . . . . . . . . . . . . 34 63 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 64 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 35 65 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 35 66 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 36 67 10.1. Normative References . . . . . . . . . . . . . . . . . . 36 68 10.2. Informative References . . . . . . . . . . . . . . . . . 38 69 Appendix A. Examples of OTN Label Ranges . . . . . . . . . . . . 39 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45 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 [ANSI] 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@2021-02-19.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) 2021 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 "2021-02-19" { 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 "ITU-T G.709 v6.0 (06/2020), Table 7-8 and L.7: Interfaces for 485 the Optical Transport Network (OTN)"; 486 } 488 typedef flexe-client-rate { 489 type union { 490 type uint16; 491 type enumeration { 492 enum "10G" { 493 description 494 "Represents a 10G FlexE Client signal (s=2)"; 495 } 496 enum "40G" { 497 description 498 "Represents a 40G FlexE Client signal (s=8)"; 499 } 500 } 501 } 502 description 503 "The FlexE Client signal rate (s x 5,156,250.000 kbit/s) 504 used to compute the rate of an ODUflex(IMP, s). 505 Valid values for s are s=2 (10G), s=4 (40G) and 506 s=5 x n (n x 25G). 507 In the first two cases an enumeration value 508 (either 10G or 40G) is used, while in the latter case 509 the value of n is used"; 510 reference 511 "ITU-T G.709 v6.0 (06/2020), Table 7-2: Interfaces for the 512 Optical Transport Network (OTN)"; 513 } 515 /* 516 * Identities 517 */ 519 identity tributary-slot-granularity { 520 description 521 "Tributary slot granularity"; 522 reference 523 "ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 524 Transport Network (OTN)"; 525 } 527 identity tsg-1.25G { 528 base tributary-slot-granularity; 529 description 530 "1.25G tributary slot granularity"; 531 } 533 identity tsg-2.5G { 534 base tributary-slot-granularity; 535 description 536 "2.5G tributary slot granularity"; 537 } 539 identity tsg-5G { 540 base tributary-slot-granularity; 541 description 542 "5G tributary slot granularity"; 543 } 545 identity odu-type { 546 description 547 "Base identity from which specific ODU protocol is derived."; 548 } 550 identity ODU0 { 551 base odu-type; 552 description 553 "ODU0 protocol (1.24Gb/s)."; 554 reference 555 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 556 G.709 Optical Transport Networks 558 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 559 Transport Network (OTN)"; 560 } 562 identity ODU1 { 563 base odu-type; 564 description 565 "ODU1 protocol (2.49Gb/s)."; 566 reference 567 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 568 G.709 Optical Transport Networks 570 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 571 Transport Network (OTN)"; 572 } 574 identity ODU1e { 575 base odu-type; 576 description 577 "ODU1e protocol (10.35Gb/s)."; 578 reference 579 "RFC7963: RSVP-TE Extension for Additional Signal Types in 580 G.709 Optical Transport Networks (OTNs) 582 ITU-T G.sup43 v5.0 (02/2011): Transport of IEEE 10GBASE-R 583 in optical transport networks (OTN)"; 584 } 586 identity ODU2 { 587 base odu-type; 588 description 589 "ODU2 protocol (10.03Gb/s)."; 590 reference 591 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 592 G.709 Optical Transport Networks 594 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 595 Transport Network (OTN)"; 596 } 598 identity ODU2e { 599 base odu-type; 600 description 601 "ODU2e protocol (10.39Gb/s)."; 602 reference 603 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 604 G.709 Optical Transport Networks 606 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 607 Transport Network (OTN)"; 608 } 610 identity ODU3 { 611 base odu-type; 612 description 613 "ODU3 protocol (40.31Gb/s)."; 614 reference 615 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 616 G.709 Optical Transport Networks 618 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 619 Transport Network (OTN)"; 620 } 622 identity ODU3e1 { 623 base odu-type; 624 description 625 "ODU3e1 protocol (41.77Gb/s)."; 626 reference 627 "RFC7963: RSVP-TE Extension for Additional Signal Types in 628 G.709 Optical Transport Networks (OTNs) 630 ITU-T G.sup43 v5.0 (02/2011): Transport of IEEE 10GBASE-R 631 in optical transport networks (OTN)"; 632 } 634 identity ODU3e2 { 635 base odu-type; 636 description 637 "ODU3e2 protocol (41.78Gb/s)."; 638 reference 639 "RFC7963: RSVP-TE Extension for Additional Signal Types in 640 G.709 Optical Transport Networks (OTNs) 642 ITU-T G.sup43 v5.0 (02/2011): Transport of IEEE 10GBASE-R 643 in optical transport networks (OTN)"; 644 } 646 identity ODU4 { 647 base odu-type; 648 description 649 "ODU4 protocol (104.79Gb/s)."; 650 reference 651 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 652 G.709 Optical Transport Networks 654 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 655 Transport Network (OTN)"; 656 } 658 identity ODUflex { 659 base odu-type; 660 description 661 "ODUflex protocol (flexibile bit rate, not resizable). 663 It could be used for any type of ODUflex, including 664 ODUflex(CBR), ODUflex(GFP), ODUflex(GFP,n,k), ODUflex(IMP,s), 665 ODUflex(IMP) and ODUflex(FlexE-aware)."; 666 reference 667 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 668 G.709 Optical Transport Networks 670 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 671 Transport Network (OTN)"; 672 } 674 identity ODUflex-resizable { 675 base odu-type; 676 description 677 "ODUflex protocol (flexibile bit rate, resizable). 679 It could be used only for ODUflex(GFP,n,k)."; 680 reference 681 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 682 G.709 Optical Transport Networks 684 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 685 Transport Network (OTN)"; 686 } 688 identity protocol { 689 description 690 "Base identity from which specific protocol is derived."; 691 reference 692 "MEF63: Subscriber Layer 1 Service Attributes"; 693 } 695 identity Ethernet { 696 base protocol; 697 description 698 "Ethernet protocol."; 699 reference 700 "MEF63: Subscriber Layer 1 Service Attributes"; 701 } 702 identity Fibre-Channel { 703 base protocol; 704 description 705 "Fibre-Channel (FC) protocol."; 706 reference 707 "MEF63: Subscriber Layer 1 Service Attributes"; 708 } 710 identity SDH { 711 base protocol; 712 description 713 "SDH protocol."; 714 reference 715 "MEF63: Subscriber Layer 1 Service Attributes"; 716 } 718 identity SONET { 719 base protocol; 720 description 721 "SONET protocol."; 722 reference 723 "MEF63: Subscriber Layer 1 Service Attributes"; 724 } 726 identity client-signal { 727 description 728 "Base identity from which specific client signal is derived"; 729 } 731 identity coding-func { 732 description 733 "Base identity from which specific coding function 734 is derived."; 735 reference 736 "MEF63: Subscriber Layer 1 Service Attributes"; 737 } 739 identity ETH-1Gb { 740 base client-signal; 741 description 742 "Client signal type of 1GbE"; 743 reference 744 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 745 G.709 Optical Transport Networks 747 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 748 Transport Network (OTN)"; 749 } 750 identity ETH-10Gb-LAN { 751 base client-signal; 752 description 753 "Client signal type of ETH-10Gb-LAN (10.3 Gb/s)"; 754 reference 755 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 756 G.709 Optical Transport Networks 758 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 759 Transport Network (OTN) 761 IEEE 802.3-2018, Clause 49: IEEE Standard for Ethernet"; 762 } 764 identity ETH-10Gb-WAN { 765 base client-signal; 766 description 767 "Client signal type of ETH-10Gb-WAN (9.95 Gb/s)"; 768 reference 769 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 770 G.709 Optical Transport Networks 772 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 773 Transport Network (OTN) 775 IEEE 802.3-2018, Clause 50: IEEE Standard for Ethernet"; 776 } 778 identity ETH-40Gb { 779 base client-signal; 780 description 781 "Client signal type of 40GbE"; 782 reference 783 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 784 G.709 Optical Transport Networks 786 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 787 Transport Network (OTN)"; 788 } 790 identity ETH-100Gb { 791 base client-signal; 792 description 793 "Client signal type of 100GbE"; 794 reference 795 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 796 G.709 Optical Transport Networks 797 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 798 Transport Network (OTN)"; 799 } 801 identity STM-1 { 802 base client-signal; 803 base coding-func; 804 description 805 "Client signal type of STM-1; 806 STM-1 G.707 (N=1) coding function."; 807 reference 808 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 809 G.709 Optical Transport Networks 811 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 812 Transport Network (OTN) 814 MEF63: Subscriber Layer 1 Service Attributes"; 815 } 817 identity STM-4 { 818 base client-signal; 819 base coding-func; 820 description 821 "Client signal type of STM-4; 822 STM-4 G.707 (N=4) coding function."; 823 reference 824 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 825 G.709 Optical Transport Networks 827 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 828 Transport Network (OTN) 830 MEF63: Subscriber Layer 1 Service Attributes"; 831 } 833 identity STM-16 { 834 base client-signal; 835 base coding-func; 836 description 837 "Client signal type of STM-16; 838 STM-16 G.707 (N=16) coding function."; 839 reference 840 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 841 G.709 Optical Transport Networks 843 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 844 Transport Network (OTN) 845 MEF63: Subscriber Layer 1 Service Attributes"; 846 } 848 identity STM-64 { 849 base client-signal; 850 base coding-func; 851 description 852 "Client signal type of STM-64; 853 STM-64 G.707 (N=64) coding function."; 854 reference 855 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 856 G.709 Optical Transport Networks 858 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 859 Transport Network (OTN) 861 MEF63: Subscriber Layer 1 Service Attributes"; 862 } 864 identity STM-256 { 865 base client-signal; 866 base coding-func; 867 description 868 "Client signal type of STM-256; 869 STM-256 G.707 (N=256) coding function."; 870 reference 871 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 872 G.709 Optical Transport Networks 874 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 875 Transport Network (OTN) 877 MEF63: Subscriber Layer 1 Service Attributes"; 878 } 880 identity OC-3 { 881 base client-signal; 882 base coding-func; 883 description 884 "Client signal type of OC3; 885 OC-3 GR-253-CORE (N=3) coding function."; 886 reference 887 "ANSI T1.105-1995: Synchronous Optical Network (SONET) 888 Basic Description including Multiplex Structure, Rates, 889 and Formats 891 MEF63: Subscriber Layer 1 Service Attributes"; 892 } 893 identity OC-12 { 894 base client-signal; 895 base coding-func; 896 description 897 "Client signal type of OC12; 898 OC-12 GR-253-CORE (N=12) coding function."; 899 reference 900 "ANSI T1.105-1995: Synchronous Optical Network (SONET) 901 Basic Description including Multiplex Structure, Rates, 902 and Formats 904 MEF63: Subscriber Layer 1 Service Attributes"; 905 } 907 identity OC-48 { 908 base client-signal; 909 base coding-func; 910 description 911 "Client signal type of OC48; 912 OC-48 GR-253-CORE (N=48) coding function."; 913 reference 914 "ANSI T1.105-1995: Synchronous Optical Network (SONET) 915 Basic Description including Multiplex Structure, Rates, 916 and Formats 918 MEF63: Subscriber Layer 1 Service Attributes"; 919 } 921 identity OC-192 { 922 base client-signal; 923 base coding-func; 924 description 925 "Client signal type of OC192; 926 OC-192 GR-253-CORE (N=192) coding function."; 927 reference 928 "ANSI T1.105-1995: Synchronous Optical Network (SONET) 929 Basic Description including Multiplex Structure, Rates, 930 and Formats 932 MEF63: Subscriber Layer 1 Service Attributes"; 933 } 935 identity OC-768 { 936 base client-signal; 937 base coding-func; 938 description 939 "Client signal type of OC768; 940 OC-768 GR-253-CORE (N=768) coding function."; 942 reference 943 "ANSI T1.105-1995: Synchronous Optical Network (SONET) 944 Basic Description including Multiplex Structure, Rates, 945 and Formats 947 MEF63: Subscriber Layer 1 Service Attributes"; 948 } 950 identity FC-100 { 951 base client-signal; 952 base coding-func; 953 description 954 "Client signal type of Fibre Channel FC-100; 955 FC-100 FC-FS-2 (1.0625 Gb/s) coding function."; 956 reference 957 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 958 G.709 Optical Transport Networks 960 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 961 Transport Network (OTN) 963 MEF63: Subscriber Layer 1 Service Attributes"; 964 } 966 identity FC-200 { 967 base client-signal; 968 base coding-func; 969 description 970 "Client signal type of Fibre Channel FC-200; 971 FC-200 FC-FS-2 (2.125 Gb/s) coding function."; 972 reference 973 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 974 G.709 Optical Transport Networks 976 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 977 Transport Network (OTN) 979 MEF63: Subscriber Layer 1 Service Attributes"; 980 } 982 identity FC-400 { 983 base client-signal; 984 base coding-func; 985 description 986 "Client signal type of Fibre Channel FC-400; 987 FC-400 FC-FS-2 (4.250 Gb/s) coding function."; 988 reference 989 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 990 G.709 Optical Transport Networks 992 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 993 Transport Network (OTN) 995 MEF63: Subscriber Layer 1 Service Attributes"; 996 } 998 identity FC-800 { 999 base client-signal; 1000 base coding-func; 1001 description 1002 "Client signal type of Fibre Channel FC-800; 1003 FC-800 FC-FS-2 (8.500 Gb/s) coding function."; 1004 reference 1005 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1006 G.709 Optical Transport Networks 1008 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1009 Transport Network (OTN) 1011 MEF63: Subscriber Layer 1 Service Attributes"; 1012 } 1014 identity FC-1200 { 1015 base client-signal; 1016 base coding-func; 1017 description 1018 "Client signal type of Fibre Channel FC-1200; 1019 FC-1200 FC-10GFC (10.51875 Gb/s) coding function."; 1020 reference 1021 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1022 G.709 Optical Transport Networks 1024 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1025 Transport Network (OTN) 1027 MEF63: Subscriber Layer 1 Service Attributes"; 1028 } 1030 identity FC-1600 { 1031 base client-signal; 1032 base coding-func; 1033 description 1034 "Client signal type of Fibre Channel FC-1600; 1035 FC-1600 FC-FS-3 (14.025 Gb/s) coding function."; 1036 reference 1037 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1038 G.709 Optical Transport Networks 1040 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1041 Transport Network (OTN) 1043 MEF63: Subscriber Layer 1 Service Attributes"; 1044 } 1046 identity FC-3200 { 1047 base client-signal; 1048 base coding-func; 1049 description 1050 "Client signal type of Fibre Channel FC-3200; 1051 FC-3200 FC-FS-4 (28.05 Gb/s) coding function."; 1052 reference 1053 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1054 G.709 Optical Transport Networks 1056 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1057 Transport Network (OTN) 1059 MEF63: Subscriber Layer 1 Service Attributes"; 1060 } 1062 identity FICON-4G { 1063 base client-signal; 1064 description 1065 "Client signal type of Fibre Connection 4G"; 1066 reference 1067 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1068 G.709 Optical Transport Networks 1070 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1071 Transport Network (OTN)"; 1072 } 1074 identity FICON-8G { 1075 base client-signal; 1076 description 1077 "Client signal type of Fibre Connection 8G"; 1078 reference 1079 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1080 G.709 Optical Transport Networks 1082 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1083 Transport Network (OTN)"; 1084 } 1085 identity ETH-1000X { 1086 base coding-func; 1087 description 1088 "1000BASE-X PCS clause 36 coding function."; 1089 reference 1090 "MEF63: Subscriber Layer 1 Service Attributes"; 1091 } 1093 identity ETH-10GW { 1094 base coding-func; 1095 description 1096 "10GBASE-W (WAN PHY) PCS clause 49 and WIS clause 50 1097 coding function."; 1098 reference 1099 "MEF63: Subscriber Layer 1 Service Attributes"; 1100 } 1102 identity ETH-10GR { 1103 base coding-func; 1104 description 1105 "10GBASE-R (LAN PHY) PCS clause 49 coding function."; 1106 reference 1107 "MEF63: Subscriber Layer 1 Service Attributes"; 1108 } 1110 identity ETH-40GR { 1111 base coding-func; 1112 description 1113 "40GBASE-R PCS clause 82 coding function."; 1114 reference 1115 "MEF63: Subscriber Layer 1 Service Attributes"; 1116 } 1118 identity ETH-100GR { 1119 base coding-func; 1120 description 1121 "100GBASE-R PCS clause 82 coding function."; 1122 reference 1123 "MEF63: Subscriber Layer 1 Service Attributes"; 1124 } 1126 identity optical-interface-func { 1127 description 1128 "Base identity from which optical-interface-function 1129 is derived."; 1130 reference 1131 "MEF63: Subscriber Layer 1 Service Attributes"; 1132 } 1133 identity SX-PMD-1000 { 1134 base optical-interface-func; 1135 description 1136 "SX-PMD-clause-38 Optical Interface function for 1137 1000BASE-X PCS-36"; 1138 reference 1139 "MEF63: Subscriber Layer 1 Service Attributes"; 1140 } 1142 identity LX-PMD-1000 { 1143 base optical-interface-func; 1144 description 1145 "LX-PMD-clause-38 Optical Interface function for 1146 1000BASE-X PCS-36"; 1147 reference 1148 "MEF63: Subscriber Layer 1 Service Attributes"; 1149 } 1151 identity LX10-PMD-1000 { 1152 base optical-interface-func; 1153 description 1154 "LX10-PMD-clause-59 Optical Interface function for 1155 1000BASE-X PCS-36"; 1156 reference 1157 "MEF63: Subscriber Layer 1 Service Attributes"; 1158 } 1160 identity BX10-PMD-1000 { 1161 base optical-interface-func; 1162 description 1163 "BX10-PMD-clause-59 Optical Interface function for 1164 1000BASE-X PCS-36"; 1165 reference 1166 "MEF63: Subscriber Layer 1 Service Attributes"; 1167 } 1169 identity LW-PMD-10G { 1170 base optical-interface-func; 1171 description 1172 "LW-PMD-clause-52 Optical Interface function for 1173 10GBASE-W PCS-49-WIS-50"; 1174 reference 1175 "MEF63: Subscriber Layer 1 Service Attributes"; 1176 } 1178 identity EW-PMD-10G { 1179 base optical-interface-func; 1180 description 1181 "EW-PMD-clause-52 Optical Interface function for 1182 10GBASE-W PCS-49-WIS-50"; 1183 reference 1184 "MEF63: Subscriber Layer 1 Service Attributes"; 1185 } 1187 identity LR-PMD-10G { 1188 base optical-interface-func; 1189 description 1190 "LR-PMD-clause-52 Optical Interface function for 1191 10GBASE-R PCS-49"; 1192 reference 1193 "MEF63: Subscriber Layer 1 Service Attributes"; 1194 } 1196 identity ER-PMD-10G { 1197 base optical-interface-func; 1198 description 1199 "ER-PMD-clause-52 Optical Interface function for 1200 10GBASE-R PCS-49"; 1201 reference 1202 "MEF63: Subscriber Layer 1 Service Attributes"; 1203 } 1205 identity LR4-PMD-40G { 1206 base optical-interface-func; 1207 description 1208 "LR4-PMD-clause-87 Optical Interface function for 1209 40GBASE-R PCS-82"; 1210 reference 1211 "MEF63: Subscriber Layer 1 Service Attributes"; 1212 } 1214 identity ER4-PMD-40G { 1215 base optical-interface-func; 1216 description 1217 "ER4-PMD-clause-87 Optical Interface function for 1218 40GBASE-R PCS-82"; 1219 reference 1220 "MEF63: Subscriber Layer 1 Service Attributes"; 1221 } 1223 identity FR-PMD-40G { 1224 base optical-interface-func; 1225 description 1226 "FR-PMD-clause-89 Optical Interface function for 1227 40GBASE-R PCS-82"; 1228 reference 1229 "MEF63: Subscriber Layer 1 Service Attributes"; 1230 } 1232 identity LR4-PMD-100G { 1233 base optical-interface-func; 1234 description 1235 "LR4-PMD-clause-88 Optical Interface function for 1236 100GBASE-R PCS-82"; 1237 reference 1238 "MEF63: Subscriber Layer 1 Service Attributes"; 1239 } 1241 identity ER4-PMD-100G { 1242 base optical-interface-func; 1243 description 1244 "ER4-PMD-clause-88 Optical Interface function for 1245 100GBASE-R PCS-82"; 1246 reference 1247 "MEF63: Subscriber Layer 1 Service Attributes"; 1248 } 1250 /* 1251 * Groupings 1252 */ 1254 grouping otn-link-bandwidth { 1255 description 1256 "Bandwidth attributes for OTN links"; 1257 list odulist { 1258 key "odu-type"; 1259 description 1260 "OTN bandwidth definition"; 1261 leaf odu-type { 1262 type identityref { 1263 base odu-type; 1264 } 1265 description "ODU type"; 1266 } 1267 leaf number { 1268 type uint16; 1269 description "Number of ODUs"; 1270 } 1271 } 1272 } 1274 grouping otn-path-bandwidth { 1275 description 1276 "Bandwidth attributes for OTN paths."; 1278 container otn { 1279 description 1280 "Bandwidth attributes for OTN paths."; 1281 leaf odu-type { 1282 type identityref { 1283 base odu-type; 1284 } 1285 description "ODU type"; 1286 } 1287 choice oduflex-type { 1288 when 'derived-from-or-self(./odu-type,"ODUflex") or 1289 derived-from-or-self(./odu-type,"ODUflex-resizable")'{ 1290 description 1291 "Applicable when odu-type is ODUflex or 1292 ODUflex-resizable"; 1293 } 1294 description 1295 "Types of ODUflex used to compute the ODUflex 1296 nominal bit rate."; 1297 reference 1298 "ITU-T G.709 v6.0 (06/2020), Table 7-2: Interfaces for the 1299 Optical Transport Network (OTN)"; 1300 case generic { 1301 leaf nominal-bit-rate { 1302 type uint64; 1303 units "bps"; 1304 mandatory true; 1305 description 1306 "Nominal ODUflex bit rate."; 1307 } 1308 } 1309 case cbr { 1310 leaf client-type { 1311 type identityref { 1312 base client-signal; 1313 } 1314 mandatory true; 1315 description 1316 "The CBR client signal for an ODUflex(CBR)."; 1317 } 1318 } 1319 case gfp-n-k { 1320 leaf gfp-n { 1321 type uint8 { 1322 range "1..80"; 1323 } 1324 mandatory true; 1325 description 1326 "The value of n for an ODUflex(GFP,n,k)."; 1327 reference 1328 "ITU-T G.709 v6.0 (06/2020), Tables 7-8 and L.7: 1329 Interfaces for the Optical Transport Network (OTN)"; 1330 } 1331 leaf gfp-k { 1332 type gfp-k; 1333 description 1334 "The value of k for an ODUflex(GFP,n,k). 1336 If omitted, it is calculated from the value of gfp-n 1337 as described in Table 7-8 of G.709"; 1338 reference 1339 "ITU-T G.709 v6.0 (06/2020), Tables 7-8 and L.7: 1340 Interfaces for the Optical Transport Network (OTN)"; 1341 } 1342 } 1343 case flexe-client { 1344 leaf flexe-client { 1345 type flexe-client-rate; 1346 mandatory true; 1347 description 1348 "The rate of the FlexE-client for an ODUflex(IMP,s)."; 1349 } 1350 } 1351 case flexe-aware { 1352 leaf flexe-aware-n { 1353 type uint16; 1354 mandatory true; 1355 description 1356 "The rate of FlexE-aware client signal 1357 for ODUflex(FlexE-aware)"; 1358 } 1359 } 1360 case packet { 1361 leaf opuflex-payload-rate { 1362 type uint64; 1363 units "Kbps"; 1364 mandatory true; 1365 description 1366 "Either the GFP-F encapsulated packet client nominal 1367 bit rate for an ODUflex(GFP) or the 64b/66b encoded 1368 packet client nominal bit rate for an ODUflex(IMP)."; 1369 } 1370 } 1371 } 1372 } 1373 } 1374 grouping otn-label-range-info { 1375 description 1376 "Label range information for OTN. 1378 This grouping should be used together with the 1379 otn-label-start-end and otn-label-step groupings to provide 1380 OTN technology-specific label information to the models which 1381 use the label-restriction-info grouping defined in the module 1382 ietf-te-types."; 1383 leaf range-type { 1384 type otn-label-range-type; 1385 description "The type of range (e.g., TPN or TS) 1386 to which the label range applies"; 1387 } 1388 leaf tsg { 1389 type identityref { 1390 base tributary-slot-granularity; 1391 } 1392 description 1393 "Tributary slot granularity (TSG) to which the label range 1394 applies. 1396 This leaf shall be present when the range-type is TS. 1398 This leaf can be omitted when mapping an ODUk over an OTUk 1399 Link. In this case the range-type is tpn, with only one 1400 entry (ODUk), and the tpn range has only one value (1)."; 1401 reference 1402 "ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1403 Transport Network (OTN)"; 1404 } 1405 leaf-list odu-type-list { 1406 type identityref { 1407 base odu-type; 1408 } 1409 description 1410 "List of ODU types to which the label range applies. 1412 An Empty odu-type-list means that the label range 1413 applies to all the supported ODU types."; 1414 } 1415 leaf priority { 1416 type uint8; 1417 description 1418 "Priority in Interface Switching Capability 1419 Descriptor (ISCD)."; 1420 reference 1421 "RFC4203: OSPF Extensions in Support of Generalized 1422 Multi-Protocol Label Switching (GMPLS)"; 1423 } 1424 } 1426 grouping otn-label-start-end { 1427 description 1428 "The OTN label-start or label-end used to specify an OTN label 1429 range. 1431 This grouping is dependent on the range-type defined in the 1432 otn-label-range-info grouping. 1434 This grouping should be used together with the 1435 otn-label-range-info and otn-label-step groupings to provide 1436 OTN technology-specific label information to the models which 1437 use the label-restriction-info grouping defined in the module 1438 ietf-te-types."; 1439 choice range-type { 1440 description 1441 "OTN label range type, either TPN range or TS range"; 1442 case trib-port { 1443 leaf otn-tpn { 1444 when "../../../range-type = 'trib-port'" { 1445 description 1446 "Valid only when range-type represented by trib-port"; 1447 } 1448 type otn-tpn; 1449 description 1450 "Tributary Port Number."; 1451 reference 1452 "RFC7139: GMPLS Signaling Extensions for Control of 1453 Evolving G.709 Optical Transport Networks."; 1454 } 1455 } 1456 case trib-slot { 1457 leaf otn-ts { 1458 when "../../../range-type = 'trib-slot'" { 1459 description 1460 "Valid only when range-type represented by trib-slot"; 1461 } 1462 type otn-ts; 1463 description 1464 "Tributary Slot Number."; 1465 reference 1466 "RFC7139: GMPLS Signaling Extensions for Control of 1467 Evolving G.709 Optical Transport Networks"; 1468 } 1469 } 1471 } 1472 } 1474 grouping otn-label-hop { 1475 description "OTN Label"; 1476 reference 1477 "RFC7139, section 6: GMPLS Signaling Extensions for Control of 1478 Evolving G.709 Optical Transport Networks"; 1479 leaf otn-tpn { 1480 type otn-tpn; 1481 description 1482 "Tributary Port Number."; 1483 reference 1484 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1485 G.709 Optical Transport Networks."; 1486 } 1487 leaf tsg { 1488 type identityref { 1489 base tributary-slot-granularity; 1490 } 1491 description "Tributary slot granularity."; 1492 reference 1493 "ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1494 Transport Network (OTN)"; 1495 } 1496 leaf ts-list { 1497 type string { 1498 pattern "([1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?" 1499 + "(,[1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?)*)"; 1500 } 1501 description 1502 "A list of available tributary slots ranging 1503 between 1 and 4095. If multiple values or 1504 ranges are given, they all must be disjoint 1505 and must be in ascending order. 1506 For example 1-20,25,50-1000."; 1507 reference 1508 "RFC 7139: GMPLS Signaling Extensions for Control 1509 of Evolving G.709 Optical Transport Networks"; 1510 } 1511 } 1513 grouping otn-label-step { 1514 description 1515 "Label step for OTN. 1517 This grouping is dependent on the range-type defined in the 1518 otn-label-range-info grouping. 1520 This grouping should be used together with the 1521 otn-label-range-info and otn-label-start-end groupings to 1522 provide OTN technology-specific label information to the models 1523 which use the label-restriction-info grouping defined in the 1524 module ietf-te-types."; 1525 choice range-type { 1526 description 1527 "OTN label range type, either TPN range or TS range"; 1528 case trib-port { 1529 leaf otn-tpn { 1530 when "../../range-type = 'trib-port'" { 1531 description 1532 "Valid only when range-type represented by trib-port"; 1533 } 1534 type otn-tpn; 1535 description 1536 "Label step which represents possible increments for 1537 Tributary Port Number."; 1538 reference 1539 "RFC7139: GMPLS Signaling Extensions for Control of 1540 Evolving G.709 Optical Transport Networks."; 1541 } 1542 } 1543 case trib-slot { 1544 leaf otn-ts { 1545 when "../../range-type = 'trib-slot'" { 1546 description 1547 "Valid only when range-type represented by trib-slot"; 1548 } 1549 type otn-ts; 1550 description 1551 "Label step which represents possible increments for 1552 Tributary Slot Number."; 1553 reference 1554 "RFC7139: GMPLS Signaling Extensions for Control of 1555 Evolving G.709 Optical Transport Networks."; 1556 } 1557 } 1558 } 1559 } 1560 } 1561 1563 6. Security Considerations 1565 The YANG module specified in this document defines a schema for data 1566 that is designed to be accessed via network management protocols such 1567 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 1568 is the secure transport layer, and the mandatory-to-implement secure 1569 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 1570 is HTTPS, and the mandatory-to-implement secure transport is TLS 1571 [RFC8446]. 1573 The NETCONF access control model [RFC8341] provides the means to 1574 restrict access for particular NETCONF or RESTCONF users to a 1575 preconfigured subset of all available NETCONF or RESTCONF protocol 1576 operations and content. 1578 The YANG module in this document defines layer 1 type definitions 1579 (i.e., typedef, identity and grouping statements) in YANG data 1580 modeling language to be imported and used by other layer 1 1581 technology-specific modules. When imported and used, the resultant 1582 schema will have data nodes that can be writable, or readable. The 1583 access to such data nodes may be considered sensitive or vulnerable 1584 in some network environments. Write operations (e.g., edit-config) 1585 to these data nodes without proper protection can have a negative 1586 effect on network operations. 1588 The security considerations spelled out in the YANG 1.1 specification 1589 [RFC7950] apply for this document as well. 1591 7. IANA Considerations 1593 It is proposed that IANA should assign new URIs from the "IETF XML 1594 Registry" [RFC3688] as follows: 1596 URI: urn:ietf:params:xml:ns:yang:ietf-layer1-types 1597 Registrant Contact: The IESG 1598 XML: N/A; the requested URI is an XML namespace. 1600 This document registers following YANG modules in the YANG Module 1601 Names registry [RFC7950]. 1603 name: ietf-layer1-types 1604 namespace: urn:ietf:params:xml:ns:yang:ietf-layer1-types 1605 prefix: l1-types 1606 reference: RFC XXXX 1608 8. Acknowledgements 1610 The authors and the working group give their sincere thanks for 1611 Robert Wilton for the YANG doctor review, and Tom Petch for his 1612 comments during the model and document development. 1614 9. Contributors 1616 Dieter Beller 1617 Nokia 1618 Email: dieter.beller@nokia.com 1620 Sergio Belotti 1621 Nokia 1622 Email: sergio.belotti@nokia.com 1624 Yanlei Zheng 1625 China Unicom 1626 Email: zhengyanlei@chinaunicom.cn 1628 Aihua Guo 1629 Futurewei Technologies 1630 Email: aihuaguo@futurewei.com 1632 Young Lee 1633 Samsung 1634 Email: younglee.tx@gmail.com 1636 Lei Wang 1637 China Mobile 1638 Email: wangleiyj@chinamobile.com 1640 Oscar Gonzalez de Dios 1641 Telefonica 1642 Email: oscar.gonzalezdedios@telefonica.com 1644 Xufeng Liu 1645 Volta Networks 1646 Email: xufeng.liu.ietf@gmail.com 1648 Yunbin Xu 1649 CAICT 1650 Email: xuyunbin@caict.ac.cn 1652 Anurag Sharma 1653 Google 1654 Email: ansha@google.com 1655 Rajan Rao 1656 Infinera 1657 Email: rrao@infinera.com 1659 Victor Lopez 1660 Telefonica 1661 Email: victor.lopezalvarez@telefonica.com 1663 Yunbo Li 1664 China Mobile 1665 Email: liyunbo@chinamobile.com 1667 10. References 1669 10.1. Normative References 1671 [ANSI] American National Standards Institute, "Synchronous 1672 Optical Network (SONET) Basic Description including 1673 Multiplex Structure, Rates, and Formats", ANSI T1.105, 1674 January 1995. 1676 [IEEE] Institute of Electrical and Electronics Engineers, "IEEE 1677 Standard for Ethernet", IEEE 802.3-2018, June 2018. 1679 [ITU-Tg7044] 1680 International Telecommunication Union, "Hitless adjustment 1681 of ODUflex(GFP)", ITU-T G.7044, October 2011. 1683 [ITU-Tg709] 1684 International Telecommunication Union, "Interfaces for the 1685 optical transport network", ITU-T G.709, June 2020. 1687 [ITU-Tgsup43] 1688 International Telecommunication Union, "Transport of IEEE 1689 10GBASE-R in optical transport networks (OTN)", 1690 ITU-T G.sup43, November 2011. 1692 [MEF63] Metro Ethernet Forum, "Subscriber Layer1 Service 1693 Attributes Technical Specification", MEF 63, August 2018. 1695 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1696 DOI 10.17487/RFC3688, January 2004, 1697 . 1699 [RFC4203] Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions in 1700 Support of Generalized Multi-Protocol Label Switching 1701 (GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005, 1702 . 1704 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 1705 and A. Bierman, Ed., "Network Configuration Protocol 1706 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 1707 . 1709 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 1710 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 1711 . 1713 [RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, D., 1714 and K. Pithewan, "GMPLS Signaling Extensions for Control 1715 of Evolving G.709 Optical Transport Networks", RFC 7139, 1716 DOI 10.17487/RFC7139, March 2014, 1717 . 1719 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 1720 RFC 7950, DOI 10.17487/RFC7950, August 2016, 1721 . 1723 [RFC7963] Ali, Z., Bonfanti, A., Hartley, M., and F. Zhang, "RSVP-TE 1724 Extension for Additional Signal Types in G.709 Optical 1725 Transport Networks (OTNs)", RFC 7963, 1726 DOI 10.17487/RFC7963, August 2016, 1727 . 1729 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 1730 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 1731 . 1733 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 1734 Access Control Model", STD 91, RFC 8341, 1735 DOI 10.17487/RFC8341, March 2018, 1736 . 1738 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 1739 and R. Wilton, "Network Management Datastore Architecture 1740 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 1741 . 1743 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 1744 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 1745 . 1747 [RFC8776] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, 1748 "Common YANG Data Types for Traffic Engineering", 1749 RFC 8776, DOI 10.17487/RFC8776, June 2020, 1750 . 1752 10.2. Informative References 1754 [I-D.ietf-ccamp-client-signal-yang] 1755 Zheng, H., Guo, A., Busi, I., Snitser, A., Lazzeri, F., 1756 Xu, Y., Zhao, Y., Liu, X., and G. Fioccola, "A YANG Data 1757 Model for Transport Network Client Signals", draft-ietf- 1758 ccamp-client-signal-yang-04 (work in progress), January 1759 2021. 1761 [I-D.ietf-ccamp-l1csm-yang] 1762 Lee, Y., Lee, K., Zheng, H., Dios, O., and D. Ceccarelli, 1763 "A YANG Data Model for L1 Connectivity Service Model 1764 (L1CSM)", draft-ietf-ccamp-l1csm-yang-13 (work in 1765 progress), November 2020. 1767 [I-D.ietf-ccamp-otn-topo-yang] 1768 Zheng, H., Busi, I., Liu, X., Belotti, S., and O. Dios, "A 1769 YANG Data Model for Optical Transport Network Topology", 1770 draft-ietf-ccamp-otn-topo-yang-11 (work in progress), 1771 September 2020. 1773 [I-D.ietf-ccamp-otn-tunnel-model] 1774 Zheng, H., Busi, I., Belotti, S., Lopez, V., and Y. Xu, 1775 "OTN Tunnel YANG Model", draft-ietf-ccamp-otn-tunnel- 1776 model-11 (work in progress), September 2020. 1778 [I-D.ietf-ccamp-transport-nbi-app-statement] 1779 Busi, I., King, D., Zheng, H., and Y. Xu, "Transport 1780 Northbound Interface Applicability Statement", draft-ietf- 1781 ccamp-transport-nbi-app-statement-12 (work in progress), 1782 January 2021. 1784 [RFC7062] Zhang, F., Ed., Li, D., Li, H., Belotti, S., and D. 1785 Ceccarelli, "Framework for GMPLS and PCE Control of G.709 1786 Optical Transport Networks", RFC 7062, 1787 DOI 10.17487/RFC7062, November 2013, 1788 . 1790 [RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and 1791 J. Drake, "Traffic Engineering Extensions to OSPF for 1792 GMPLS Control of Evolving G.709 Optical Transport 1793 Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014, 1794 . 1796 [RFC8792] Watsen, K., Auerswald, E., Farrel, A., and Q. Wu, 1797 "Handling Long Lines in Content of Internet-Drafts and 1798 RFCs", RFC 8792, DOI 10.17487/RFC8792, June 2020, 1799 . 1801 Appendix A. Examples of OTN Label Ranges 1803 This appendix provides some examples of how the TPN and TS label 1804 ranges described in Table 3 and Table 4 of [RFC7139] can be 1805 represented in YANG using the groupings defined in this document. 1807 It also considers the OTUk links in addition to HO-ODUk links. 1809 The JSON code examples provided in this appendix provides some 1810 embedded comments following the conventions in section 3.2 of 1811 [I-D.ietf-ccamp-transport-nbi-app-statement] and have been folded 1812 using the tool in [RFC8792]. 1814 ========== NOTE: '\\' line wrapping per BCP XXX (RFC XXXX) ========== 1816 { 1817 "examples of label-restrictions for different OTN Links": [ 1818 { 1819 "// ": "HO-ODU1 or OTU1 Link", 1820 "label-restrictions": { 1821 "label-restriction": [ 1822 { 1823 "index ": 1, 1824 "// ___DEFAULT___ restriction": "inclusive", 1825 "range-type": "label-range-trib-port", 1826 "// ___NOT-PRESENT___ tsg": "", 1827 "odu-type-list": "[ ODU1 ]", 1828 "// ___DEFAULT___ priority": 7, 1829 "// tpn-range": 1, 1830 "// ___ COMMENT ___": "Since no TS range and no TSG are \ 1831 \reported for ODU1, the link is an OTU1 Link. TS allocation is not n\ 1832 \eeded and TPN shall be set to '1' for mapping ODU1 over OTU1. This \ 1833 \entry is not present if the OTN Link is an HO-ODU1 Link." 1834 }, 1835 { 1836 "index ": 2, 1837 "// ___DEFAULT___ restriction": "inclusive", 1838 "range-type": "label-range-trib-slot", 1839 "tsg": "tsg-1.25G", 1840 "odu-type-list": "[ ODU0 ]", 1841 "// ts-range": "1-2", 1842 "// ___ COMMENT ___": "Since no TPN range is reportd for\ 1843 \ ODU0 with 1.25G TSG, the TPN allocation rule is fixed (TPN = TS#) \ 1844 \for mapping LO-ODU0 over HO-ODU1 with 1.25G TSG. See Table 4 of [RF\ 1845 \C7139]." 1846 } 1847 ] 1849 } 1850 }, 1851 { 1852 "// ": "HO-ODU2 or OTU2 Link", 1853 "label-restrictions": { 1854 "label-restriction": [ 1855 { 1856 "index ": 1, 1857 "// ___DEFAULT___ restriction": "inclusive", 1858 "range-type": "label-range-trib-port", 1859 "// ___NOT-PRESENT___ tsg": "", 1860 "odu-type-list": "[ ODU2 ]", 1861 "// ___ DEFAULT ___ priority": 7, 1862 "// tpn-range": 1, 1863 "// ___ COMMENT ___": "Since no TS range and no TSG are \ 1864 \reported for ODU2, the link is an OTU2 Link. TS allocation is not n\ 1865 \eeded and TPN shall be set to '1' for mapping ODU2 over OTU2. This \ 1866 \entry is not present if the OTN Link is an HO-ODU2 Link." 1867 }, 1868 { 1869 "index ": 2, 1870 "// ___DEFAULT___ restriction": "inclusive", 1871 "range-type": "label-range-trib-slot", 1872 "tsg": "tsg-1.25G", 1873 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ 1874 \ ]", 1875 "// ___ DEFAULT ___ priority": 7, 1876 "// ts-range": "1-8" 1877 }, 1878 { 1879 "index ": 3, 1880 "// ___DEFAULT___ restriction": "inclusive", 1881 "range-type": "label-range-trib-port", 1882 "tsg": "tsg-1.25G ", 1883 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0 ]", 1884 "// ___ DEFAULT ___ priority": 7, 1885 "// tpn-range": "1-8", 1886 "// ___ COMMENT ___": "Since this TPN range is reported \ 1887 \for ODUflex and ODU0 with 1.25G TSG, the TPN assignment rule is fle\ 1888 \xible within a common range for mapping LO-ODUflex and LO-ODU0 over\ 1889 \ HO-ODU2 with 1.25G TSG. See Table 4 of [RFC7139]." 1890 }, 1891 { 1892 "index ": 4, 1893 "// ___DEFAULT___ restriction": "inclusive", 1894 "range-type": "label-range-trib-port", 1895 "tsg": "tsg-1.25G", 1896 "odu-type-list": "[ ODU1 ]", 1897 "// ___ DEFAULT ___ priority": 7, 1898 "// tpn-range": "1-4", 1899 "// ___ COMMENT ___": "Since this TPN range is reported \ 1900 \for ODU1 with 1.25G TSG, the TPN assignment rule is flexible within\ 1901 \ a common range for mapping LO-ODU1 over HO-ODU2 with 1.25G TSG. Se\ 1902 \e Table 4 of [RFC7139]." 1903 }, 1904 { 1905 "index ": 5, 1906 "// ___DEFAULT___ restriction": "inclusive", 1907 "range-type": "label-range-trib-slot", 1908 "tsg": "tsg-2.5G", 1909 "odu-type-list": "[ ODU1 ]", 1910 "// ___ DEFAULT ___ priority": 7, 1911 "// ts-range": "1-4", 1912 "// ___ COMMENT ___": "Since no TPN range is reported fo\ 1913 \r ODU1 with 2.5G TSG, the TPN allocation rule is fixed (TPN = TS#) \ 1914 \for mapping LO-ODU1 over HO-ODU2 with 2.5G TSG. See Table 3 of [RFC\ 1915 \7139]." 1916 } 1917 ] 1918 } 1919 }, 1920 { 1921 "// ": "HO-ODU3 or OTU3 Link", 1922 "label-restrictions": { 1923 "label-restriction": [ 1924 { 1925 "index ": 1, 1926 "// ___DEFAULT___ restriction": "inclusive", 1927 "range-type": "label-range-trib-port", 1928 "// ___NOT-PRESENT___ tsg": "", 1929 "odu-type-list": "[ ODU3 ]", 1930 "// ___ DEFAULT ___ priority": 7, 1931 "// tpn-range": 1, 1932 "// ___ COMMENT ___": "Since no TS range and no TSG are \ 1933 \reported for ODU3, the link is an OTU3 Link. TS allocation is not n\ 1934 \eeded and TPN shall be set to '1' for mapping ODU3 over OTU3. This \ 1935 \entry is not present if the OTN Link is an HO-ODU3 Link." 1936 }, 1937 { 1938 "index ": 2, 1939 "// ___DEFAULT___ restriction": "inclusive", 1940 "range-type": "label-range-trib-slot", 1941 "tsg": "tsg-1.25G", 1942 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ 1943 \, ODU2, ODU2e ]", 1944 "// ___ DEFAULT ___ priority": 7, 1945 "// ts-range": "1-32" 1946 }, 1947 { 1948 "index ": 3, 1949 "// ___DEFAULT___ restriction": "inclusive", 1950 "range-type": "label-range-trib-port", 1951 "tsg": "tsg-1.25G", 1952 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU2\ 1953 \e ]", 1954 "// ___ DEFAULT ___ priority": 7, 1955 "// tpn-range": "1-32", 1956 "// ___ COMMENT ___": "Since this TPN range is reported \ 1957 \for ODUflex, ODU0 and ODU2e with 1.25G TSG, the TPN assignment rule\ 1958 \ is flexible within a common range for mapping LO-ODUflex, LO-ODU0 \ 1959 \and LO-ODU2e over HO-ODU3 with 1.25G TSG. See Table 4 of [RFC7139]." 1960 }, 1961 { 1962 "index ": 4, 1963 "// ___DEFAULT___ restriction": "inclusive", 1964 "range-type": "label-range-trib-port", 1965 "tsg": "tsg-1.25G", 1966 "odu-type-list": "[ ODU1 ]", 1967 "// ___ DEFAULT ___ priority": 7, 1968 "// tpn-range": "1-16", 1969 "// ___ COMMENT ___": "Since this TPN range is reported \ 1970 \for ODU1 with 1.25G TSG, the TPN assignment rule is flexible within\ 1971 \ a common range for mapping LO-ODU1 over HO-ODU3 with 1.25G TSG. Se\ 1972 \e Table 4 of [RFC7139]." 1973 }, 1974 { 1975 "index ": 5, 1976 "// ___DEFAULT___ restriction": "inclusive", 1977 "range-type": "label-range-trib-port", 1978 "tsg": "tsg-1.25G", 1979 "odu-type-list": "[ ODU2 ]", 1980 "// ___ DEFAULT ___ priority": 7, 1981 "// tpn-range": "1-4", 1982 "// ___ COMMENT ___": "Since this TPN range is reported \ 1983 \for ODU2 with 1.25G TSG, the TPN assignment rule is flexible within\ 1984 \ a common range for mapping LO-ODU2 over HO-ODU3 with 1.25G TSG. Se\ 1985 \e Table 4 of [RFC7139]." 1986 }, 1987 { 1988 "index ": 6, 1989 "// ___DEFAULT___ restriction": "inclusive", 1990 "range-type": "label-range-trib-slot", 1991 "tsg": "tsg-2.5G", 1992 "odu-type-list": "[ ODU1, ODU2 ]", 1993 "// ___ DEFAULT ___ priority": 7, 1994 "// ts-range": "1-16" 1995 }, 1996 { 1997 "index ": 7, 1998 "// ___DEFAULT___ restriction": "inclusive", 1999 "range-type": "label-range-trib-port", 2000 "tsg": "tsg-2.5G ", 2001 "odu-type-list": "[ ODU2 ]", 2002 "// ___ DEFAULT ___ priority": 7, 2003 "// tpn-range": "1-4", 2004 "// ___ COMMENT ___": "Since this TPN range is reported \ 2005 \for ODU2 with 2.5G TSG, the TPN assignment rule is flexible within \ 2006 \a common range for mapping LO-ODU2 over HO-ODU3. Since no TPN range\ 2007 \ is reported for ODU1 with 2.5G TSG, the TPN allocation rule is fix\ 2008 \ed (TPN = TS#) for mapping LO-ODU1 over HO-ODU3 with 2.5G TSG. See \ 2009 \Table 3 of [RFC7139]." 2010 } 2011 ] 2012 } 2013 }, 2014 { 2015 "// ": "HO-ODU4 or OTU4 Link", 2016 "label-restrictions": { 2017 "label-restriction": [ 2018 { 2019 "index ": 1, 2020 "// ___DEFAULT___ restriction": "inclusive", 2021 "range-type": "label-range-trib-port", 2022 "// ___NOT-PRESENT___ tsg": "", 2023 "odu-type-list": "[ ODU4 ]", 2024 "// ___ DEFAULT ___ priority": 7, 2025 "// tpn-range": 1, 2026 "// ___ COMMENT ___": "Since no TS range and no TSG are \ 2027 \reported for ODU4, the link is an OTU4 Link. TS allocation is not n\ 2028 \eeded and TPN shall be set to '1' for mapping ODU4 over OTU4. This \ 2029 \entry is not present if the OTN Link is an HO-ODU4 Link." 2030 }, 2031 { 2032 "index ": 2, 2033 "// ___DEFAULT___ restriction": "inclusive", 2034 "range-type": "label-range-trib-slot", 2035 "tsg": "tsg-1.25G", 2036 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ 2037 \, ODU2, ODU2e, ODU3 ]", 2038 "// ___ DEFAULT ___ priority": 7, 2039 "// ts-range": "1-80" 2040 }, 2041 { 2042 "index ": 3, 2043 "// ___DEFAULT___ restriction": "inclusive", 2044 "range-type": "label-range-trib-port", 2045 "tsg": "tsg-1.25G", 2046 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ 2047 \, ODU2, ODU2e, ODU3 ]", 2048 "// ___ DEFAULT ___ priority": 7, 2049 "// tpn-range": "1-80", 2050 "// ___ COMMENT ___": "Since this TPN range is reported \ 2051 \for any LO-ODUj with 1.25G TSG, the TPN assignment rule is flexible\ 2052 \ within a common range for mapping any LO-ODUj over HO-ODU4 with 1.\ 2053 \25G TSG. See Table 4 of [RFC7139]." 2054 } 2055 ] 2056 } 2057 }, 2058 { 2059 "// ": "ODUC1 Link", 2060 "label-restrictions": { 2061 "label-restriction": [ 2062 { 2063 "index ": 1, 2064 "// ___DEFAULT___ restriction": "inclusive", 2065 "range-type": "label-range-trib-slot", 2066 "tsg": "tsg-5G", 2067 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ 2068 \, ODU2, ODU2e, ODU3, ODU4 ]", 2069 "// ___ DEFAULT ___ priority": 7, 2070 "// ts-range": "1-20", 2071 "// ___ COMMENT ___": "Since the TS range is specified f\ 2072 \or any ODUk, the OTN Link is an ODUCn Link." 2073 }, 2074 { 2075 "index ": 2, 2076 "// ___DEFAULT___ restriction": "inclusive", 2077 "range-type": "label-range-trib-port", 2078 "tsg": "tsg-5G", 2079 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ 2080 \, ODU2, ODU2e, ODU3, ODU4 ]", 2081 "// ___ DEFAULT ___ priority": 7, 2082 "// tpn-range": "1-10", 2083 "// ___ COMMENT ___": "Since this TPN range is reported \ 2084 \for any ODUk with 5G TSG, the TPN assignment rule is flexible withi\ 2085 \n a common range for mapping any ODUk over ODUCn with 5G TSG." 2086 } 2087 ] 2088 } 2090 } 2091 ] 2092 } 2094 Authors' Addresses 2096 Haomian Zheng 2097 Huawei Technologies 2098 H1, Huawei Xiliu Beipo Village, Songshan Lake 2099 Dongguan, Guangdong 523808 2100 China 2102 Email: zhenghaomian@huawei.com 2104 Italo Busi 2105 Huawei Technologies 2106 Milan 2107 Italy 2109 Email: Italo.Busi@huawei.com