idnits 2.17.1 draft-ietf-ccamp-layer1-types-11.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 171 has weird spacing: '...du-type ide...' == Line 341 has weird spacing: '...ad-rate uin...' -- The document date (September 8, 2021) is 961 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 1738, but no explicit reference was found in the text == Unused Reference: 'RFC4203' is defined on line 1761, 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-05 == Outdated reference: A later version (-26) exists of draft-ietf-ccamp-l1csm-yang-14 == Outdated reference: A later version (-18) exists of draft-ietf-ccamp-otn-topo-yang-13 == Outdated reference: A later version (-20) exists of draft-ietf-ccamp-otn-tunnel-model-14 == Outdated reference: A later version (-17) exists of draft-ietf-ccamp-transport-nbi-app-statement-12 Summary: 1 error (**), 0 flaws (~~), 10 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: March 12, 2022 September 8, 2021 7 A YANG Data Model for Layer 1 Types 8 draft-ietf-ccamp-layer1-types-11 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 March 12, 2022. 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 . . . . . . . . . . . . . . . . 6 59 4.4. ODUflex . . . . . . . . . . . . . . . . . . . . . . . . . 7 60 4.4.1. Resizable ODUflex . . . . . . . . . . . . . . . . . . 10 61 5. YANG Code for Layer1 Types . . . . . . . . . . . . . . . . . 10 62 6. Security Considerations . . . . . . . . . . . . . . . . . . . 35 63 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 35 64 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 36 65 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 36 66 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 67 10.1. Normative References . . . . . . . . . . . . . . . . . . 37 68 10.2. Informative References . . . . . . . . . . . . . . . . . 39 69 Appendix A. Examples of OTN Label Ranges . . . . . . . . . . . . 40 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 46 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. The link 166 bandwidth is represented by the number of ODUs that can be supported 167 by the link for each ODU type as follow. 169 +--:(otn) 170 +--rw odulist* [odu-type] 171 +--rw odu-type identityref 172 +--rw number? uint16 174 For example, an OTN link with 100G bandwidth can support either 175 1xODU4, 10xODU2 or 80xODU0. 177 This grouping is also used to represent the ODUflex resources 178 available on a link, as described in section Section 4.4. 180 otn-path-bandwidth: 182 This grouping defines the path bandwidth information and could be 183 used in OTN topology model for path bandwidth representation. All 184 the bandwidth related sections in generic module, [RFC8776], need to 185 be augmented with this grouping for the usage of Layer 1. This 186 grouping is also applicable when setting up the OTN tunnel. The path 187 bandwidth is usually represented by the type of ODU (e.g., ODU0, 188 ODU2, ODU4) being setup along the path as follow. 190 +--:(otn) 191 +--rw odu-type? identityref 193 In case of ODUflex paths, more information about the bandwidth of the 194 ODUflex needs to be provided, as described in section Section 4.4. 196 otn-label-range-info: 198 This grouping is used to augment the label-restriction list, defined 199 in [RFC8776], with OTN technology-specific attributes, as defined in 200 section Section 4.3. 202 +--rw range-type? otn-label-range-type 203 +--rw tsg? identityref 204 +--rw odu-type-list* identityref 205 +--rw priority? uint8 207 otn-label-start-end: 209 This grouping is used to augment the label-start and label-end 210 containers within the label-restriction list, defined in [RFC8776], 211 with OTN technology-specific attributes, as defined in section 212 Section 4.3. 214 +--:(otn) 215 +--rw (range-type)? 216 +--:(trib-port) 217 | +--rw otn-tpn? otn-tpn 218 +--:(trib-slot) 219 +--rw otn-ts? otn-ts 221 otn-label-step: 223 This grouping is used to augment the label-step container within the 224 label-restriction list, defined in [RFC8776], with OTN technology- 225 specific attributes, as defined in section Section 4.3. 227 +--:(otn) 228 +--rw (range-type)? 229 +--:(trib-port) 230 | +--rw otn-tpn? otn-tpn 231 +--:(trib-slot) 232 +--rw otn-ts? otn-ts 234 otn-label-hop: 236 This grouping is used to augment the label-hop container, defined in 237 [RFC8776], with OTN technology-specific attributes, as defined in 238 section Section 4.3. 240 +--:(otn) 241 +--rw otn-tpn? otn-tpn 242 +--rw tsg? identityref 243 +--rw ts-list? string 245 optical-interface-func: 247 The optical interface function is specified in [MEF63]. Identities 248 that describe the functionality are specified to encode bits for 249 transmission and to decode bits upon reception. 251 4.3. OTN Label and Label Range 253 As described in [RFC7139], the OTN label usually represents the 254 Tributary Port Number (TPN) and the related set of Tributary Slots 255 (TS) assigned to a client layer ODU LSP (LO ODUj or ODUk) on a given 256 server layer ODU (HO-ODU or ODUCn, respectively) Link (e.g., ODU2 LSP 257 over ODU3 Link). Some special OTN label values are also defined for 258 an ODUk LSP being set up over an OTUk Link. 260 The same OTN label must be assigned to the same ODUk LSP at the two 261 ends of an OTN Link. 263 As described in [RFC7139], TPN can be a number from 1 to 4095 and TS 264 are numbered from 1 to 4095, although the actual maximum values 265 depend on the type of server layer ODU. For example, a server layer 266 ODU4 provides 80 time slots (numbered from 1 to 80) and the TPN 267 values can be any number from 1 to 80. 269 The OTN Label Range represents the values for the TPN and TS that are 270 available for ODUk LSPs to be setup over a given OTN Link. 272 The OTN Label Range is defined by the label-restriction list, defined 273 in [RFC8776], which, for OTN, should be augmented using the otn- 274 label-range-info grouping. 276 Each entry in the label-restriction list represents either the range 277 of the available TPN values or the range of the available TS values: 278 the range-type attribute in the otn-label-range-info grouping defines 279 the type of range for each entry of the list. 281 Each entry of the label-restriction list, as defined in [RFC8776], 282 defines a label-start, a label-end, a label-step and a range-bitmap. 283 The label-start and label-end definitions for OTN should be augmented 284 using the otn-label-start-end grouping. The label-step definition 285 for OTN should be augmented using the otn-label-step grouping. It is 286 expected that the otn-label-step will always be equal to its default 287 value (i.e., 1), which is defined in [RFC8776]. 289 As described in [RFC7139], in some cases, the TPN assignment rules 290 are flexible (e.g., ODU4 Link) while in other cases the TPN 291 assignment rules are fixed (e.g., ODU1 Link). In the former case, 292 both TPN and TS ranges are reported, while in the latter case, the 293 TPN range is not reported which indicates that the TPN shall be set 294 equal to the TS number assigned to the ODUk LSP. 296 As described in [RFC7139], in some cases, the TPN assignment rules 297 depends on the TS Granularity (e.g., ODU2 or ODU3 Links). Different 298 entries in the label-restriction list will report different TPN 299 ranges for each TS granularity supported by the link, as indicated by 300 the tsg attribute in the otn-label-range-info grouping. 302 As described in [RFC7139], in some cases the TPN ranges are different 303 for different types of ODUk LSPs. For example, on an ODU2 Link with 304 1.25G TS granularity, the TPN range is 1-4 for ODU1 but 1-8 for ODU0 305 and ODUflex. Different entries in the label-restriction list will 306 report different TPN ranges for different set of ODUk types, as 307 indicated by the odu-type-list in the otn-label-range-info grouping. 309 Appendix A provides some examples of how the TPN and TS label ranges 310 described in Table 3 and Table 4 of [RFC7139] can be represented in 311 YANG using the groupings defined in this document. 313 4.4. ODUflex 315 ODUflex is a type of ODU which has a flexible bit rate which is 316 configured when setting up an ODUflex LSP. 318 [ITU-Tg709], defines six types of ODUflex: ODUflex(CBR), 319 ODUflex(GFP), ODUflex(GFP,n,k), ODUflex(IMP), ODUflex(IMP,s) and 320 ODUflex(FlexE-aware). 322 The main difference between these types of ODUflex is the formula 323 used to calculate the nominal bit rate of the ODUflex, as described 324 in Table 7-2 of [ITU-Tg709]. A YANG choice has been defined to 325 describe these cases: 327 +--rw (oduflex-type)? 328 +--:(generic) 329 | +--rw nominal-bit-rate uint64 330 +--:(cbr) 331 | +--rw client-type identityref 332 +--:(gfp-n-k) 333 | +--rw gfp-n uint8 334 | +--rw gfp-k? l1-types:gfp-k 335 +--:(flexe-client) 336 | +--rw flexe-client 337 | l1-types:flexe-client-rate 338 +--:(flexe-aware) 339 | +--rw flexe-aware-n uint16 340 +--:(packet) 341 +--rw opuflex-payload-rate uint64 343 The 'generic' case has been added to allow the ODUflex nominal bit 344 rate to be defined independently from the type of ODUflex. This 345 could be useful for forward compatibility in the transit domain/nodes 346 where the setup of ODUflex LSPs does not depend on the ODUflex type. 348 In order to simplify interoperability the 'generic' case should be 349 used only when it is needed; the ODUflex type-specific case should be 350 used whenever possible. 352 The 'cbr' case is used for Constant Bit Rate (CBR) client signals. 353 The client-type indicates which CBR client signal is carried by the 354 ODUflex and, implicitly, the client signal bit rate which is then 355 used to calculate the ODUflex(CBR) nominal bit rate as described in 356 Table 7-2 of [ITU-Tg709]. 358 The 'gfp-n-k' case is used for GFP-F mapped client signals based on 359 ODUk.ts and 'n' 1.25G tributary slots. 'gfp-k' defines the nominal 360 bit-rate of the ODUk.ts which, together with the value of 'gfp-n', is 361 used to calculated the ODUflex(GFP,n,k) nominal bit rate as described 362 in Table 7-8 and Table L-7 of [ITU-Tg709] . With a few exceptions, 363 shown in Table L-7 of [ITU-Tg709], the nominal bit-rate of the 364 ODUk.ts could be inferred from the value of 'n', as shown in 365 Table 7-8 of [ITU-Tg709] and therefore the 'gfp-k' is optional. 367 The 'flexe-client' case is used for Idle Mapping Procedure(IMP) 368 mapped FlexE client signals, The 'flexe-client' represents the type 369 of FlexE client carried by the ODUflex which implicitly defines the 370 value of 's' used to calculate the ODUflex(s) nominal bit rate as 371 described in Table 7-2 of [ITU-Tg709]. The '10G' and '40G' 372 enumeration values are used for 10G and 40G FlexE clients to 373 implicitly define the values of s=2 and s=8. For the 'n x 25G' FlexE 374 Clients the value of 'n' is used to defines the value of s=5 x n. 376 The 'flexe-aware' case is used for FlexE-aware client signals. The 377 flexe-aware-n represents the value n (n = n1 + n2 + ... + np) which 378 is used to calculate the ODUflex(FlexE-aware) nominal bit rate as 379 described in Table 7-2 of [ITU-Tg709]. 381 The 'packet' case is used for both the GFP-F mapped client signals 382 and the IMP mapped client signals. The opuflex-payload-rate is 383 either the GFP-F encapsulated-packet client nominal bit rate or the 384 64b/66b encoded-packet client nominal bit rate. The calculation of 385 ODUflex(GFP) nominal bit rate is defined in section 12.2.5 of 386 [ITU-Tg709], and the calculation of ODUflex(IMP) nominal bit rate is 387 defined in section 12.2.6 of [ITU-Tg709]. The same formula is used 388 in both cases. 390 Section 5.1 and 5.2 of [RFC7139] defines two rules to compute the 391 number of tributary slots to be allocated to ODUflex(CBR) and 392 ODUflex(GFP) LSPs when carried over a HO-ODUk link. According to 393 section 19.6 of [ITU-Tg709], the rules in section 5.2 apply only to 394 ODUflex(GFP,n,k) while the rules defined in section 5.1 apply to any 395 other ODUflex type, including, but not limited, to ODUflex(CBR). 396 Section 20.5 of [ITU-Tg709] defines the rules for computing the 397 number of tributary slots to be allocated to ODUflex LSPs when 398 carried over an ODUCn link. 400 Following the [ITU-Tg709] definitions, the rules defined for 401 ODUflex(GFP,n,k) are used only when the 'gfp-n-k' case is used. In 402 all the other cases, including the (generic) case, the rules defined 403 any other ODUflex type are used. 405 The number of available ODUs, defined for each ODUk type, including 406 ODUflex, together with the number of available time-slots, reported 407 as part of the OTN label range, provide sufficient information to 408 infer the OTN link bandwidth availability for ODUflex LSPs. This 409 information is independent of the ODUflex type. 411 4.4.1. Resizable ODUflex 413 Resizable ODUflex is a special type of ODUflex that supports the 414 procedures defined in [ITU-Tg7044] for hitless resizing of the 415 ODUflex nominal bit rate. 417 Two odu-type identities have been defined for ODUflex: 419 o The ODUflex identity, which is used with any type of non-resizable 420 ODUflex, as defined in Table 7-2 of [ITU-Tg709]. 422 o The ODUflex-resizable identity, which is used only with resizable 423 ODUflex(GFP,n,k). 425 These two identities are used to identify whether an ODUflex(GFP,n,k) 426 LSP does or does support the [ITU-Tg7044] hitless resizing 427 procedures. They also identify whether an OTN link only supports the 428 setup of non-resizable ODUflex LSPs or also supports the setup of 429 resizable ODUflex(GFP,n,k) LSP but with different capabilities (e.g., 430 a lower number of LSPs). 432 5. YANG Code for Layer1 Types 434 file "ietf-layer1-types@2021-02-19.yang" 435 module ietf-layer1-types { 436 yang-version 1.1; 437 namespace "urn:ietf:params:xml:ns:yang:ietf-layer1-types"; 438 prefix "l1-types"; 440 organization 441 "IETF CCAMP Working Group"; 442 contact 443 "WG Web: 444 WG List: 446 Editor: Haomian Zheng 447 449 Editor: Italo Busi 450 "; 452 description 453 "This module defines Layer 1 types. The model fully conforms 454 to the Network Management Datastore Architecture (NMDA). 456 Copyright (c) 2021 IETF Trust and the persons 457 identified as authors of the code. All rights reserved. 459 Redistribution and use in source and binary forms, with or 460 without modification, is permitted pursuant to, and subject 461 to the license terms contained in, the Simplified BSD License 462 set forth in Section 4.c of the IETF Trust's Legal Provisions 463 Relating to IETF Documents 464 (https://trustee.ietf.org/license-info). 465 This version of this YANG module is part of RFC XXXX; see 466 the RFC itself for full legal notices."; 468 revision "2021-02-19" { 469 description 470 "Initial Version"; 471 reference 472 "RFC XXXX: A YANG Data Model for Layer 1 Types"; 473 // RFC Editor: replace XXXX with actual RFC number, update date 474 // information and remove this note 475 } 477 /* 478 * Typedefs 479 */ 481 typedef otn-tpn { 482 type uint16 { 483 range "1..4095"; 484 } 485 description 486 "Tributary Port Number for OTN. "; 487 reference 488 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 489 G.709 Optical Transport Networks."; 490 } 492 typedef otn-ts { 493 type uint16 { 494 range "1..4095"; 495 } 496 description 497 "Tributary Slot for OTN. "; 498 reference 499 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 500 G.709 Optical Transport Networks."; 501 } 503 typedef otn-label-range-type { 504 type enumeration { 505 enum trib-slot { 506 description 507 "Defines a range of OTN tributary slots. "; 508 } 509 enum trib-port { 510 description 511 "Defines a range of OTN tributary ports. "; 512 } 513 } 514 description 515 "Defines the type of OTN label range: TS or TPN. "; 516 } 518 typedef gfp-k { 519 type enumeration { 520 enum 2 { 521 description 522 "The ODU2.ts rate (1,249,177.230 kbit/s) is used 523 to compute the rate of an ODUflex(GFP,n,2). "; 524 } 525 enum 3 { 526 description 527 "The ODU3.ts rate (1,254,470.354 kbit/s) is used 528 to compute the rate of an ODUflex(GFP,n,3). "; 529 } 530 enum 4 { 531 description 532 "The ODU4.ts rate (1,301,467.133 kbit/s) is used 533 to compute the rate of an ODUflex(GFP,n,4). "; 534 } 535 } 536 description 537 "The ODUk.ts used to compute the rate of an ODUflex(GFP,n,k)"; 538 reference 539 "ITU-T G.709 v6.0 (06/2020), Table 7-8 and L.7: Interfaces for 540 the Optical Transport Network (OTN)"; 541 } 543 typedef flexe-client-rate { 544 type union { 545 type uint16; 546 type enumeration { 547 enum "10G" { 548 description 549 "Represents a 10G FlexE Client signal (s=2)"; 550 } 551 enum "40G" { 552 description 553 "Represents a 40G FlexE Client signal (s=8)"; 554 } 556 } 557 } 558 description 559 "The FlexE Client signal rate (s x 5,156,250.000 kbit/s) 560 used to compute the rate of an ODUflex(IMP, s). 561 Valid values for s are s=2 (10G), s=4 (40G) and 562 s=5 x n (n x 25G). 563 In the first two cases an enumeration value 564 (either 10G or 40G) is used, while in the latter case 565 the value of n is used"; 566 reference 567 "ITU-T G.709 v6.0 (06/2020), Table 7-2: Interfaces for the 568 Optical Transport Network (OTN)"; 569 } 571 /* 572 * Identities 573 */ 575 identity tributary-slot-granularity { 576 description 577 "Tributary slot granularity"; 578 reference 579 "ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 580 Transport Network (OTN)"; 581 } 583 identity tsg-1.25G { 584 base tributary-slot-granularity; 585 description 586 "1.25G tributary slot granularity"; 587 } 589 identity tsg-2.5G { 590 base tributary-slot-granularity; 591 description 592 "2.5G tributary slot granularity"; 593 } 595 identity tsg-5G { 596 base tributary-slot-granularity; 597 description 598 "5G tributary slot granularity"; 599 } 601 identity odu-type { 602 description 603 "Base identity from which specific ODU protocol is derived."; 605 } 607 identity ODU0 { 608 base odu-type; 609 description 610 "ODU0 protocol (1.24Gb/s)."; 611 reference 612 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 613 G.709 Optical Transport Networks 615 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 616 Transport Network (OTN)"; 617 } 619 identity ODU1 { 620 base odu-type; 621 description 622 "ODU1 protocol (2.49Gb/s)."; 623 reference 624 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 625 G.709 Optical Transport Networks 627 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 628 Transport Network (OTN)"; 629 } 631 identity ODU1e { 632 base odu-type; 633 description 634 "ODU1e protocol (10.35Gb/s)."; 635 reference 636 "RFC7963: RSVP-TE Extension for Additional Signal Types in 637 G.709 Optical Transport Networks (OTNs) 639 ITU-T G.sup43 v5.0 (02/2011): Transport of IEEE 10GBASE-R 640 in optical transport networks (OTN)"; 641 } 643 identity ODU2 { 644 base odu-type; 645 description 646 "ODU2 protocol (10.03Gb/s)."; 647 reference 648 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 649 G.709 Optical Transport Networks 651 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 652 Transport Network (OTN)"; 654 } 656 identity ODU2e { 657 base odu-type; 658 description 659 "ODU2e protocol (10.39Gb/s)."; 660 reference 661 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 662 G.709 Optical Transport Networks 664 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 665 Transport Network (OTN)"; 666 } 668 identity ODU3 { 669 base odu-type; 670 description 671 "ODU3 protocol (40.31Gb/s)."; 672 reference 673 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 674 G.709 Optical Transport Networks 676 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 677 Transport Network (OTN)"; 678 } 680 identity ODU3e1 { 681 base odu-type; 682 description 683 "ODU3e1 protocol (41.77Gb/s)."; 684 reference 685 "RFC7963: RSVP-TE Extension for Additional Signal Types in 686 G.709 Optical Transport Networks (OTNs) 688 ITU-T G.sup43 v5.0 (02/2011): Transport of IEEE 10GBASE-R 689 in optical transport networks (OTN)"; 690 } 692 identity ODU3e2 { 693 base odu-type; 694 description 695 "ODU3e2 protocol (41.78Gb/s)."; 696 reference 697 "RFC7963: RSVP-TE Extension for Additional Signal Types in 698 G.709 Optical Transport Networks (OTNs) 700 ITU-T G.sup43 v5.0 (02/2011): Transport of IEEE 10GBASE-R 701 in optical transport networks (OTN)"; 703 } 705 identity ODU4 { 706 base odu-type; 707 description 708 "ODU4 protocol (104.79Gb/s)."; 709 reference 710 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 711 G.709 Optical Transport Networks 713 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 714 Transport Network (OTN)"; 715 } 717 identity ODUflex { 718 base odu-type; 719 description 720 "ODUflex protocol (flexibile bit rate, not resizable). 722 It could be used for any type of ODUflex, including 723 ODUflex(CBR), ODUflex(GFP), ODUflex(GFP,n,k), ODUflex(IMP,s), 724 ODUflex(IMP) and ODUflex(FlexE-aware)."; 725 reference 726 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 727 G.709 Optical Transport Networks 729 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 730 Transport Network (OTN)"; 731 } 733 identity ODUflex-resizable { 734 base odu-type; 735 description 736 "ODUflex protocol (flexibile bit rate, resizable). 738 It could be used only for ODUflex(GFP,n,k)."; 739 reference 740 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 741 G.709 Optical Transport Networks 743 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 744 Transport Network (OTN)"; 745 } 747 identity protocol { 748 description 749 "Base identity from which specific protocol is derived."; 750 reference 751 "MEF63: Subscriber Layer 1 Service Attributes"; 752 } 754 identity Ethernet { 755 base protocol; 756 description 757 "Ethernet protocol."; 758 reference 759 "MEF63: Subscriber Layer 1 Service Attributes"; 760 } 762 identity Fibre-Channel { 763 base protocol; 764 description 765 "Fibre-Channel (FC) protocol."; 766 reference 767 "MEF63: Subscriber Layer 1 Service Attributes"; 768 } 770 identity SDH { 771 base protocol; 772 description 773 "SDH protocol."; 774 reference 775 "MEF63: Subscriber Layer 1 Service Attributes"; 776 } 778 identity SONET { 779 base protocol; 780 description 781 "SONET protocol."; 782 reference 783 "MEF63: Subscriber Layer 1 Service Attributes"; 784 } 786 identity client-signal { 787 description 788 "Base identity from which specific client signal is derived"; 789 } 791 identity coding-func { 792 description 793 "Base identity from which specific coding function 794 is derived."; 795 reference 796 "MEF63: Subscriber Layer 1 Service Attributes"; 797 } 798 identity ETH-1Gb { 799 base client-signal; 800 description 801 "Client signal type of 1GbE"; 802 reference 803 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 804 G.709 Optical Transport Networks 806 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 807 Transport Network (OTN)"; 808 } 810 identity ETH-10Gb-LAN { 811 base client-signal; 812 description 813 "Client signal type of ETH-10Gb-LAN (10.3 Gb/s)"; 814 reference 815 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 816 G.709 Optical Transport Networks 818 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 819 Transport Network (OTN) 821 IEEE 802.3-2018, Clause 49: IEEE Standard for Ethernet"; 822 } 824 identity ETH-10Gb-WAN { 825 base client-signal; 826 description 827 "Client signal type of ETH-10Gb-WAN (9.95 Gb/s)"; 828 reference 829 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 830 G.709 Optical Transport Networks 832 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 833 Transport Network (OTN) 835 IEEE 802.3-2018, Clause 50: IEEE Standard for Ethernet"; 836 } 838 identity ETH-40Gb { 839 base client-signal; 840 description 841 "Client signal type of 40GbE"; 842 reference 843 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 844 G.709 Optical Transport Networks 845 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 846 Transport Network (OTN)"; 847 } 849 identity ETH-100Gb { 850 base client-signal; 851 description 852 "Client signal type of 100GbE"; 853 reference 854 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 855 G.709 Optical Transport Networks 857 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 858 Transport Network (OTN)"; 859 } 861 identity STM-1 { 862 base client-signal; 863 base coding-func; 864 description 865 "Client signal type of STM-1; 866 STM-1 G.707 (N=1) coding function."; 867 reference 868 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 869 G.709 Optical Transport Networks 871 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 872 Transport Network (OTN) 874 MEF63: Subscriber Layer 1 Service Attributes"; 875 } 877 identity STM-4 { 878 base client-signal; 879 base coding-func; 880 description 881 "Client signal type of STM-4; 882 STM-4 G.707 (N=4) coding function."; 883 reference 884 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 885 G.709 Optical Transport Networks 887 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 888 Transport Network (OTN) 890 MEF63: Subscriber Layer 1 Service Attributes"; 891 } 892 identity STM-16 { 893 base client-signal; 894 base coding-func; 895 description 896 "Client signal type of STM-16; 897 STM-16 G.707 (N=16) coding function."; 898 reference 899 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 900 G.709 Optical Transport Networks 902 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 903 Transport Network (OTN) 905 MEF63: Subscriber Layer 1 Service Attributes"; 906 } 908 identity STM-64 { 909 base client-signal; 910 base coding-func; 911 description 912 "Client signal type of STM-64; 913 STM-64 G.707 (N=64) coding function."; 914 reference 915 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 916 G.709 Optical Transport Networks 918 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 919 Transport Network (OTN) 921 MEF63: Subscriber Layer 1 Service Attributes"; 922 } 924 identity STM-256 { 925 base client-signal; 926 base coding-func; 927 description 928 "Client signal type of STM-256; 929 STM-256 G.707 (N=256) coding function."; 930 reference 931 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 932 G.709 Optical Transport Networks 934 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 935 Transport Network (OTN) 937 MEF63: Subscriber Layer 1 Service Attributes"; 938 } 939 identity OC-3 { 940 base client-signal; 941 base coding-func; 942 description 943 "Client signal type of OC3; 944 OC-3 GR-253-CORE (N=3) coding function."; 945 reference 946 "ANSI T1.105-1995: Synchronous Optical Network (SONET) 947 Basic Description including Multiplex Structure, Rates, 948 and Formats 950 MEF63: Subscriber Layer 1 Service Attributes"; 951 } 953 identity OC-12 { 954 base client-signal; 955 base coding-func; 956 description 957 "Client signal type of OC12; 958 OC-12 GR-253-CORE (N=12) coding function."; 959 reference 960 "ANSI T1.105-1995: Synchronous Optical Network (SONET) 961 Basic Description including Multiplex Structure, Rates, 962 and Formats 964 MEF63: Subscriber Layer 1 Service Attributes"; 965 } 967 identity OC-48 { 968 base client-signal; 969 base coding-func; 970 description 971 "Client signal type of OC48; 972 OC-48 GR-253-CORE (N=48) coding function."; 973 reference 974 "ANSI T1.105-1995: Synchronous Optical Network (SONET) 975 Basic Description including Multiplex Structure, Rates, 976 and Formats 978 MEF63: Subscriber Layer 1 Service Attributes"; 979 } 981 identity OC-192 { 982 base client-signal; 983 base coding-func; 984 description 985 "Client signal type of OC192; 986 OC-192 GR-253-CORE (N=192) coding function."; 988 reference 989 "ANSI T1.105-1995: Synchronous Optical Network (SONET) 990 Basic Description including Multiplex Structure, Rates, 991 and Formats 993 MEF63: Subscriber Layer 1 Service Attributes"; 994 } 996 identity OC-768 { 997 base client-signal; 998 base coding-func; 999 description 1000 "Client signal type of OC768; 1001 OC-768 GR-253-CORE (N=768) coding function."; 1002 reference 1003 "ANSI T1.105-1995: Synchronous Optical Network (SONET) 1004 Basic Description including Multiplex Structure, Rates, 1005 and Formats 1007 MEF63: Subscriber Layer 1 Service Attributes"; 1008 } 1010 identity FC-100 { 1011 base client-signal; 1012 base coding-func; 1013 description 1014 "Client signal type of Fibre Channel FC-100; 1015 FC-100 FC-FS-2 (1.0625 Gb/s) coding function."; 1016 reference 1017 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1018 G.709 Optical Transport Networks 1020 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1021 Transport Network (OTN) 1023 MEF63: Subscriber Layer 1 Service Attributes"; 1024 } 1026 identity FC-200 { 1027 base client-signal; 1028 base coding-func; 1029 description 1030 "Client signal type of Fibre Channel FC-200; 1031 FC-200 FC-FS-2 (2.125 Gb/s) coding function."; 1032 reference 1033 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1034 G.709 Optical Transport Networks 1035 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1036 Transport Network (OTN) 1038 MEF63: Subscriber Layer 1 Service Attributes"; 1039 } 1041 identity FC-400 { 1042 base client-signal; 1043 base coding-func; 1044 description 1045 "Client signal type of Fibre Channel FC-400; 1046 FC-400 FC-FS-2 (4.250 Gb/s) coding function."; 1047 reference 1048 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1049 G.709 Optical Transport Networks 1051 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1052 Transport Network (OTN) 1054 MEF63: Subscriber Layer 1 Service Attributes"; 1055 } 1057 identity FC-800 { 1058 base client-signal; 1059 base coding-func; 1060 description 1061 "Client signal type of Fibre Channel FC-800; 1062 FC-800 FC-FS-2 (8.500 Gb/s) coding function."; 1063 reference 1064 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1065 G.709 Optical Transport Networks 1067 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1068 Transport Network (OTN) 1070 MEF63: Subscriber Layer 1 Service Attributes"; 1071 } 1073 identity FC-1200 { 1074 base client-signal; 1075 base coding-func; 1076 description 1077 "Client signal type of Fibre Channel FC-1200; 1078 FC-1200 FC-10GFC (10.51875 Gb/s) coding function."; 1079 reference 1080 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1081 G.709 Optical Transport Networks 1082 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1083 Transport Network (OTN) 1085 MEF63: Subscriber Layer 1 Service Attributes"; 1086 } 1088 identity FC-1600 { 1089 base client-signal; 1090 base coding-func; 1091 description 1092 "Client signal type of Fibre Channel FC-1600; 1093 FC-1600 FC-FS-3 (14.025 Gb/s) coding function."; 1094 reference 1095 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1096 G.709 Optical Transport Networks 1098 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1099 Transport Network (OTN) 1101 MEF63: Subscriber Layer 1 Service Attributes"; 1102 } 1104 identity FC-3200 { 1105 base client-signal; 1106 base coding-func; 1107 description 1108 "Client signal type of Fibre Channel FC-3200; 1109 FC-3200 FC-FS-4 (28.05 Gb/s) coding function."; 1110 reference 1111 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1112 G.709 Optical Transport Networks 1114 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1115 Transport Network (OTN) 1117 MEF63: Subscriber Layer 1 Service Attributes"; 1118 } 1120 identity FICON-4G { 1121 base client-signal; 1122 description 1123 "Client signal type of Fibre Connection 4G"; 1124 reference 1125 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1126 G.709 Optical Transport Networks 1128 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1129 Transport Network (OTN)"; 1131 } 1133 identity FICON-8G { 1134 base client-signal; 1135 description 1136 "Client signal type of Fibre Connection 8G"; 1137 reference 1138 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1139 G.709 Optical Transport Networks 1141 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1142 Transport Network (OTN)"; 1143 } 1145 identity ETH-1000X { 1146 base coding-func; 1147 description 1148 "1000BASE-X PCS clause 36 coding function."; 1149 reference 1150 "MEF63: Subscriber Layer 1 Service Attributes"; 1151 } 1153 identity ETH-10GW { 1154 base coding-func; 1155 description 1156 "10GBASE-W (WAN PHY) PCS clause 49 and WIS clause 50 1157 coding function."; 1158 reference 1159 "MEF63: Subscriber Layer 1 Service Attributes"; 1160 } 1162 identity ETH-10GR { 1163 base coding-func; 1164 description 1165 "10GBASE-R (LAN PHY) PCS clause 49 coding function."; 1166 reference 1167 "MEF63: Subscriber Layer 1 Service Attributes"; 1168 } 1170 identity ETH-40GR { 1171 base coding-func; 1172 description 1173 "40GBASE-R PCS clause 82 coding function."; 1174 reference 1175 "MEF63: Subscriber Layer 1 Service Attributes"; 1176 } 1178 identity ETH-100GR { 1179 base coding-func; 1180 description 1181 "100GBASE-R PCS clause 82 coding function."; 1182 reference 1183 "MEF63: Subscriber Layer 1 Service Attributes"; 1184 } 1186 identity optical-interface-func { 1187 description 1188 "Base identity from which optical-interface-function 1189 is derived."; 1190 reference 1191 "MEF63: Subscriber Layer 1 Service Attributes"; 1192 } 1194 identity SX-PMD-1000 { 1195 base optical-interface-func; 1196 description 1197 "SX-PMD-clause-38 Optical Interface function for 1198 1000BASE-X PCS-36"; 1199 reference 1200 "MEF63: Subscriber Layer 1 Service Attributes"; 1201 } 1203 identity LX-PMD-1000 { 1204 base optical-interface-func; 1205 description 1206 "LX-PMD-clause-38 Optical Interface function for 1207 1000BASE-X PCS-36"; 1208 reference 1209 "MEF63: Subscriber Layer 1 Service Attributes"; 1210 } 1212 identity LX10-PMD-1000 { 1213 base optical-interface-func; 1214 description 1215 "LX10-PMD-clause-59 Optical Interface function for 1216 1000BASE-X PCS-36"; 1217 reference 1218 "MEF63: Subscriber Layer 1 Service Attributes"; 1219 } 1221 identity BX10-PMD-1000 { 1222 base optical-interface-func; 1223 description 1224 "BX10-PMD-clause-59 Optical Interface function for 1225 1000BASE-X PCS-36"; 1226 reference 1227 "MEF63: Subscriber Layer 1 Service Attributes"; 1228 } 1230 identity LW-PMD-10G { 1231 base optical-interface-func; 1232 description 1233 "LW-PMD-clause-52 Optical Interface function for 1234 10GBASE-W PCS-49-WIS-50"; 1235 reference 1236 "MEF63: Subscriber Layer 1 Service Attributes"; 1237 } 1239 identity EW-PMD-10G { 1240 base optical-interface-func; 1241 description 1242 "EW-PMD-clause-52 Optical Interface function for 1243 10GBASE-W PCS-49-WIS-50"; 1244 reference 1245 "MEF63: Subscriber Layer 1 Service Attributes"; 1246 } 1248 identity LR-PMD-10G { 1249 base optical-interface-func; 1250 description 1251 "LR-PMD-clause-52 Optical Interface function for 1252 10GBASE-R PCS-49"; 1253 reference 1254 "MEF63: Subscriber Layer 1 Service Attributes"; 1255 } 1257 identity ER-PMD-10G { 1258 base optical-interface-func; 1259 description 1260 "ER-PMD-clause-52 Optical Interface function for 1261 10GBASE-R PCS-49"; 1262 reference 1263 "MEF63: Subscriber Layer 1 Service Attributes"; 1264 } 1266 identity LR4-PMD-40G { 1267 base optical-interface-func; 1268 description 1269 "LR4-PMD-clause-87 Optical Interface function for 1270 40GBASE-R PCS-82"; 1271 reference 1272 "MEF63: Subscriber Layer 1 Service Attributes"; 1273 } 1274 identity ER4-PMD-40G { 1275 base optical-interface-func; 1276 description 1277 "ER4-PMD-clause-87 Optical Interface function for 1278 40GBASE-R PCS-82"; 1279 reference 1280 "MEF63: Subscriber Layer 1 Service Attributes"; 1281 } 1283 identity FR-PMD-40G { 1284 base optical-interface-func; 1285 description 1286 "FR-PMD-clause-89 Optical Interface function for 1287 40GBASE-R PCS-82"; 1288 reference 1289 "MEF63: Subscriber Layer 1 Service Attributes"; 1290 } 1292 identity LR4-PMD-100G { 1293 base optical-interface-func; 1294 description 1295 "LR4-PMD-clause-88 Optical Interface function for 1296 100GBASE-R PCS-82"; 1297 reference 1298 "MEF63: Subscriber Layer 1 Service Attributes"; 1299 } 1301 identity ER4-PMD-100G { 1302 base optical-interface-func; 1303 description 1304 "ER4-PMD-clause-88 Optical Interface function for 1305 100GBASE-R PCS-82"; 1306 reference 1307 "MEF63: Subscriber Layer 1 Service Attributes"; 1308 } 1310 /* 1311 * Groupings 1312 */ 1314 grouping otn-link-bandwidth { 1315 description 1316 "Bandwidth attributes for OTN links"; 1317 list odulist { 1318 key "odu-type"; 1319 description 1320 "OTN bandwidth definition"; 1321 leaf odu-type { 1322 type identityref { 1323 base odu-type; 1324 } 1325 description "ODU type"; 1326 } 1327 leaf number { 1328 type uint16; 1329 description "Number of ODUs"; 1330 } 1331 } 1332 } 1334 grouping otn-path-bandwidth { 1335 description 1336 "Bandwidth attributes for OTN paths."; 1337 container otn { 1338 description 1339 "Bandwidth attributes for OTN paths."; 1340 leaf odu-type { 1341 type identityref { 1342 base odu-type; 1343 } 1344 description "ODU type"; 1345 } 1346 choice oduflex-type { 1347 when 'derived-from-or-self(./odu-type,"ODUflex") or 1348 derived-from-or-self(./odu-type,"ODUflex-resizable")'{ 1349 description 1350 "Applicable when odu-type is ODUflex or 1351 ODUflex-resizable"; 1352 } 1353 description 1354 "Types of ODUflex used to compute the ODUflex 1355 nominal bit rate."; 1356 reference 1357 "ITU-T G.709 v6.0 (06/2020), Table 7-2: Interfaces for the 1358 Optical Transport Network (OTN)"; 1359 case generic { 1360 leaf nominal-bit-rate { 1361 type uint64; 1362 units "bps"; 1363 mandatory true; 1364 description 1365 "Nominal ODUflex bit rate."; 1366 } 1367 } 1368 case cbr { 1369 leaf client-type { 1370 type identityref { 1371 base client-signal; 1372 } 1373 mandatory true; 1374 description 1375 "The CBR client signal for an ODUflex(CBR)."; 1376 } 1377 } 1378 case gfp-n-k { 1379 leaf gfp-n { 1380 type uint8 { 1381 range "1..80"; 1382 } 1383 mandatory true; 1384 description 1385 "The value of n for an ODUflex(GFP,n,k)."; 1386 reference 1387 "ITU-T G.709 v6.0 (06/2020), Tables 7-8 and L.7: 1388 Interfaces for the Optical Transport Network (OTN)"; 1389 } 1390 leaf gfp-k { 1391 type gfp-k; 1392 description 1393 "The value of k for an ODUflex(GFP,n,k). 1395 If omitted, it is calculated from the value of gfp-n 1396 as described in Table 7-8 of G.709"; 1397 reference 1398 "ITU-T G.709 v6.0 (06/2020), Tables 7-8 and L.7: 1399 Interfaces for the Optical Transport Network (OTN)"; 1400 } 1401 } 1402 case flexe-client { 1403 leaf flexe-client { 1404 type flexe-client-rate; 1405 mandatory true; 1406 description 1407 "The rate of the FlexE-client for an ODUflex(IMP,s)."; 1408 } 1409 } 1410 case flexe-aware { 1411 leaf flexe-aware-n { 1412 type uint16; 1413 mandatory true; 1414 description 1415 "The rate of FlexE-aware client signal 1416 for ODUflex(FlexE-aware)"; 1417 } 1419 } 1420 case packet { 1421 leaf opuflex-payload-rate { 1422 type uint64; 1423 units "Kbps"; 1424 mandatory true; 1425 description 1426 "Either the GFP-F encapsulated packet client nominal 1427 bit rate for an ODUflex(GFP) or the 64b/66b encoded 1428 packet client nominal bit rate for an ODUflex(IMP)."; 1429 } 1430 } 1431 } 1432 } 1433 } 1435 grouping otn-label-range-info { 1436 description 1437 "Label range information for OTN. 1439 This grouping should be used together with the 1440 otn-label-start-end and otn-label-step groupings to provide 1441 OTN technology-specific label information to the models which 1442 use the label-restriction-info grouping defined in the module 1443 ietf-te-types."; 1444 leaf range-type { 1445 type otn-label-range-type; 1446 description "The type of range (e.g., TPN or TS) 1447 to which the label range applies"; 1448 } 1449 leaf tsg { 1450 type identityref { 1451 base tributary-slot-granularity; 1452 } 1453 description 1454 "Tributary slot granularity (TSG) to which the label range 1455 applies. 1457 This leaf shall be present when the range-type is TS. 1459 This leaf can be omitted when mapping an ODUk over an OTUk 1460 Link. In this case the range-type is tpn, with only one 1461 entry (ODUk), and the tpn range has only one value (1)."; 1462 reference 1463 "ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1464 Transport Network (OTN)"; 1465 } 1466 leaf-list odu-type-list { 1467 type identityref { 1468 base odu-type; 1469 } 1470 description 1471 "List of ODU types to which the label range applies. 1473 An Empty odu-type-list means that the label range 1474 applies to all the supported ODU types."; 1475 } 1476 leaf priority { 1477 type uint8; 1478 description 1479 "Priority in Interface Switching Capability 1480 Descriptor (ISCD)."; 1481 reference 1482 "RFC4203: OSPF Extensions in Support of Generalized 1483 Multi-Protocol Label Switching (GMPLS)"; 1484 } 1485 } 1487 grouping otn-label-start-end { 1488 description 1489 "The OTN label-start or label-end used to specify an OTN label 1490 range. 1492 This grouping is dependent on the range-type defined in the 1493 otn-label-range-info grouping. 1495 This grouping should be used together with the 1496 otn-label-range-info and otn-label-step groupings to provide 1497 OTN technology-specific label information to the models which 1498 use the label-restriction-info grouping defined in the module 1499 ietf-te-types."; 1500 choice range-type { 1501 description 1502 "OTN label range type, either TPN range or TS range"; 1503 case trib-port { 1504 leaf otn-tpn { 1505 when "../../../range-type = 'trib-port'" { 1506 description 1507 "Valid only when range-type represented by trib-port"; 1508 } 1509 type otn-tpn; 1510 description 1511 "Tributary Port Number."; 1512 reference 1513 "RFC7139: GMPLS Signaling Extensions for Control of 1514 Evolving G.709 Optical Transport Networks."; 1516 } 1517 } 1518 case trib-slot { 1519 leaf otn-ts { 1520 when "../../../range-type = 'trib-slot'" { 1521 description 1522 "Valid only when range-type represented by trib-slot"; 1523 } 1524 type otn-ts; 1525 description 1526 "Tributary Slot Number."; 1527 reference 1528 "RFC7139: GMPLS Signaling Extensions for Control of 1529 Evolving G.709 Optical Transport Networks"; 1530 } 1531 } 1532 } 1533 } 1535 grouping otn-label-hop { 1536 description "OTN Label"; 1537 reference 1538 "RFC7139, section 6: GMPLS Signaling Extensions for Control of 1539 Evolving G.709 Optical Transport Networks"; 1540 leaf otn-tpn { 1541 type otn-tpn; 1542 description 1543 "Tributary Port Number."; 1544 reference 1545 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1546 G.709 Optical Transport Networks."; 1547 } 1548 leaf tsg { 1549 type identityref { 1550 base tributary-slot-granularity; 1551 } 1552 description "Tributary slot granularity."; 1553 reference 1554 "ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1555 Transport Network (OTN)"; 1556 } 1557 leaf ts-list { 1558 type string { 1559 pattern "([1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?" 1560 + "(,[1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?)*)"; 1561 } 1562 description 1563 "A list of available tributary slots ranging 1564 between 1 and 4095. If multiple values or 1565 ranges are given, they all must be disjoint 1566 and must be in ascending order. 1567 For example 1-20,25,50-1000."; 1568 reference 1569 "RFC 7139: GMPLS Signaling Extensions for Control 1570 of Evolving G.709 Optical Transport Networks"; 1571 } 1572 } 1574 grouping otn-label-step { 1575 description 1576 "Label step for OTN. 1578 This grouping is dependent on the range-type defined in the 1579 otn-label-range-info grouping. 1581 This grouping should be used together with the 1582 otn-label-range-info and otn-label-start-end groupings to 1583 provide OTN technology-specific label information to the models 1584 which use the label-restriction-info grouping defined in the 1585 module ietf-te-types."; 1586 choice range-type { 1587 description 1588 "OTN label range type, either TPN range or TS range"; 1589 case trib-port { 1590 leaf otn-tpn { 1591 when "../../range-type = 'trib-port'" { 1592 description 1593 "Valid only when range-type represented by trib-port"; 1594 } 1595 type otn-tpn; 1596 description 1597 "Label step which represents possible increments for 1598 Tributary Port Number."; 1599 reference 1600 "RFC7139: GMPLS Signaling Extensions for Control of 1601 Evolving G.709 Optical Transport Networks."; 1602 } 1603 } 1604 case trib-slot { 1605 leaf otn-ts { 1606 when "../../range-type = 'trib-slot'" { 1607 description 1608 "Valid only when range-type represented by trib-slot"; 1609 } 1610 type otn-ts; 1611 description 1612 "Label step which represents possible increments for 1613 Tributary Slot Number."; 1614 reference 1615 "RFC7139: GMPLS Signaling Extensions for Control of 1616 Evolving G.709 Optical Transport Networks."; 1617 } 1618 } 1619 } 1620 } 1621 } 1622 1624 6. Security Considerations 1626 The YANG module specified in this document defines a schema for data 1627 that is designed to be accessed via network management protocols such 1628 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 1629 is the secure transport layer, and the mandatory-to-implement secure 1630 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 1631 is HTTPS, and the mandatory-to-implement secure transport is TLS 1632 [RFC8446]. 1634 The NETCONF access control model [RFC8341] provides the means to 1635 restrict access for particular NETCONF or RESTCONF users to a 1636 preconfigured subset of all available NETCONF or RESTCONF protocol 1637 operations and content. 1639 The YANG module in this document defines layer 1 type definitions 1640 (i.e., typedef, identity and grouping statements) in YANG data 1641 modeling language to be imported and used by other layer 1 1642 technology-specific modules. When imported and used, the resultant 1643 schema will have data nodes that can be writable, or readable. The 1644 access to such data nodes may be considered sensitive or vulnerable 1645 in some network environments. Write operations (e.g., edit-config) 1646 to these data nodes without proper protection can have a negative 1647 effect on network operations. 1649 The security considerations spelled out in the YANG 1.1 specification 1650 [RFC7950] apply for this document as well. 1652 7. IANA Considerations 1654 It is proposed that IANA should assign new URIs from the "IETF XML 1655 Registry" [RFC3688] as follows: 1657 URI: urn:ietf:params:xml:ns:yang:ietf-layer1-types 1658 Registrant Contact: The IESG 1659 XML: N/A; the requested URI is an XML namespace. 1661 This document registers following YANG modules in the YANG Module 1662 Names registry [RFC7950]. 1664 name: ietf-layer1-types 1665 namespace: urn:ietf:params:xml:ns:yang:ietf-layer1-types 1666 prefix: l1-types 1667 reference: RFC XXXX 1669 8. Acknowledgements 1671 The authors and the working group give their sincere thanks for 1672 Robert Wilton for the YANG doctor review, and Tom Petch for his 1673 comments during the model and document development. 1675 9. Contributors 1677 Dieter Beller 1678 Nokia 1679 Email: dieter.beller@nokia.com 1681 Sergio Belotti 1682 Nokia 1683 Email: sergio.belotti@nokia.com 1685 Yanlei Zheng 1686 China Unicom 1687 Email: zhengyanlei@chinaunicom.cn 1689 Aihua Guo 1690 Futurewei Technologies 1691 Email: aihuaguo@futurewei.com 1693 Young Lee 1694 Samsung 1695 Email: younglee.tx@gmail.com 1697 Lei Wang 1698 China Mobile 1699 Email: wangleiyj@chinamobile.com 1701 Oscar Gonzalez de Dios 1702 Telefonica 1703 Email: oscar.gonzalezdedios@telefonica.com 1705 Xufeng Liu 1706 Volta Networks 1707 Email: xufeng.liu.ietf@gmail.com 1709 Yunbin Xu 1710 CAICT 1711 Email: xuyunbin@caict.ac.cn 1713 Anurag Sharma 1714 Google 1715 Email: ansha@google.com 1717 Rajan Rao 1718 Infinera 1719 Email: rrao@infinera.com 1721 Victor Lopez 1722 Telefonica 1723 Email: victor.lopezalvarez@telefonica.com 1725 Yunbo Li 1726 China Mobile 1727 Email: liyunbo@chinamobile.com 1729 10. References 1731 10.1. Normative References 1733 [ANSI] American National Standards Institute, "Synchronous 1734 Optical Network (SONET) Basic Description including 1735 Multiplex Structure, Rates, and Formats", ANSI T1.105, 1736 January 1995. 1738 [IEEE] Institute of Electrical and Electronics Engineers, "IEEE 1739 Standard for Ethernet", IEEE 802.3-2018, June 2018. 1741 [ITU-Tg7044] 1742 International Telecommunication Union, "Hitless adjustment 1743 of ODUflex(GFP)", ITU-T G.7044, October 2011. 1745 [ITU-Tg709] 1746 International Telecommunication Union, "Interfaces for the 1747 optical transport network", ITU-T G.709, June 2020. 1749 [ITU-Tgsup43] 1750 International Telecommunication Union, "Transport of IEEE 1751 10GBASE-R in optical transport networks (OTN)", 1752 ITU-T G.sup43, November 2011. 1754 [MEF63] Metro Ethernet Forum, "Subscriber Layer1 Service 1755 Attributes Technical Specification", MEF 63, August 2018. 1757 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1758 DOI 10.17487/RFC3688, January 2004, 1759 . 1761 [RFC4203] Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions in 1762 Support of Generalized Multi-Protocol Label Switching 1763 (GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005, 1764 . 1766 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 1767 and A. Bierman, Ed., "Network Configuration Protocol 1768 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 1769 . 1771 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 1772 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 1773 . 1775 [RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, D., 1776 and K. Pithewan, "GMPLS Signaling Extensions for Control 1777 of Evolving G.709 Optical Transport Networks", RFC 7139, 1778 DOI 10.17487/RFC7139, March 2014, 1779 . 1781 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 1782 RFC 7950, DOI 10.17487/RFC7950, August 2016, 1783 . 1785 [RFC7963] Ali, Z., Bonfanti, A., Hartley, M., and F. Zhang, "RSVP-TE 1786 Extension for Additional Signal Types in G.709 Optical 1787 Transport Networks (OTNs)", RFC 7963, 1788 DOI 10.17487/RFC7963, August 2016, 1789 . 1791 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 1792 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 1793 . 1795 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 1796 Access Control Model", STD 91, RFC 8341, 1797 DOI 10.17487/RFC8341, March 2018, 1798 . 1800 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 1801 and R. Wilton, "Network Management Datastore Architecture 1802 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 1803 . 1805 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 1806 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 1807 . 1809 [RFC8776] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, 1810 "Common YANG Data Types for Traffic Engineering", 1811 RFC 8776, DOI 10.17487/RFC8776, June 2020, 1812 . 1814 10.2. Informative References 1816 [I-D.ietf-ccamp-client-signal-yang] 1817 Zheng, H., Guo, A., Busi, I., Snitser, A., Lazzeri, F., 1818 Xu, Y., Zhao, Y., Liu, X., and G. Fioccola, "A YANG Data 1819 Model for Transport Network Client Signals", draft-ietf- 1820 ccamp-client-signal-yang-05 (work in progress), July 2021. 1822 [I-D.ietf-ccamp-l1csm-yang] 1823 Lee, Y., Lee, K., Zheng, H., Dios, O. G. D., and D. 1824 Ceccarelli, "A YANG Data Model for L1 Connectivity Service 1825 Model (L1CSM)", draft-ietf-ccamp-l1csm-yang-14 (work in 1826 progress), February 2021. 1828 [I-D.ietf-ccamp-otn-topo-yang] 1829 Zheng, H., Busi, I., Liu, X., Belotti, S., and O. G. D. 1830 Dios, "A YANG Data Model for Optical Transport Network 1831 Topology", draft-ietf-ccamp-otn-topo-yang-13 (work in 1832 progress), July 2021. 1834 [I-D.ietf-ccamp-otn-tunnel-model] 1835 Zheng, H., Busi, I., Belotti, S., Lopez, V., and Y. Xu, 1836 "OTN Tunnel YANG Model", draft-ietf-ccamp-otn-tunnel- 1837 model-14 (work in progress), July 2021. 1839 [I-D.ietf-ccamp-transport-nbi-app-statement] 1840 Busi, I., King, D., Zheng, H., and Y. Xu, "Transport 1841 Northbound Interface Applicability Statement", draft-ietf- 1842 ccamp-transport-nbi-app-statement-12 (work in progress), 1843 January 2021. 1845 [RFC7062] Zhang, F., Ed., Li, D., Li, H., Belotti, S., and D. 1846 Ceccarelli, "Framework for GMPLS and PCE Control of G.709 1847 Optical Transport Networks", RFC 7062, 1848 DOI 10.17487/RFC7062, November 2013, 1849 . 1851 [RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and 1852 J. Drake, "Traffic Engineering Extensions to OSPF for 1853 GMPLS Control of Evolving G.709 Optical Transport 1854 Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014, 1855 . 1857 [RFC8792] Watsen, K., Auerswald, E., Farrel, A., and Q. Wu, 1858 "Handling Long Lines in Content of Internet-Drafts and 1859 RFCs", RFC 8792, DOI 10.17487/RFC8792, June 2020, 1860 . 1862 Appendix A. Examples of OTN Label Ranges 1864 This appendix provides some examples of how the TPN and TS label 1865 ranges described in Table 3 and Table 4 of [RFC7139] can be 1866 represented in YANG using the groupings defined in this document. 1868 It also considers the OTUk links in addition to HO-ODUk links. 1870 The JSON code examples provided in this appendix provides some 1871 embedded comments following the conventions in section 3.2 of 1872 [I-D.ietf-ccamp-transport-nbi-app-statement] and have been folded 1873 using the tool in [RFC8792]. 1875 ========== NOTE: '\\' line wrapping per BCP XXX (RFC XXXX) ========== 1877 { 1878 "examples of label-restrictions for different OTN Links": [ 1879 { 1880 "// ": "HO-ODU1 or OTU1 Link", 1881 "label-restrictions": { 1882 "label-restriction": [ 1883 { 1884 "index ": 1, 1885 "// ___DEFAULT___ restriction": "inclusive", 1886 "range-type": "label-range-trib-port", 1887 "// ___NOT-PRESENT___ tsg": "", 1888 "odu-type-list": "[ ODU1 ]", 1889 "// ___DEFAULT___ priority": 7, 1890 "// tpn-range": 1, 1891 "// ___ COMMENT ___": "Since no TS range and no TSG are \ 1892 \reported for ODU1, the link is an OTU1 Link. TS allocation is not n\ 1893 \eeded and TPN shall be set to '1' for mapping ODU1 over OTU1. This \ 1894 \entry is not present if the OTN Link is an HO-ODU1 Link." 1895 }, 1896 { 1897 "index ": 2, 1898 "// ___DEFAULT___ restriction": "inclusive", 1899 "range-type": "label-range-trib-slot", 1900 "tsg": "tsg-1.25G", 1901 "odu-type-list": "[ ODU0 ]", 1902 "// ts-range": "1-2", 1903 "// ___ COMMENT ___": "Since no TPN range is reportd for\ 1904 \ ODU0 with 1.25G TSG, the TPN allocation rule is fixed (TPN = TS#) \ 1905 \for mapping LO-ODU0 over HO-ODU1 with 1.25G TSG. See Table 4 of [RF\ 1906 \C7139]." 1907 } 1908 ] 1909 } 1910 }, 1911 { 1912 "// ": "HO-ODU2 or OTU2 Link", 1913 "label-restrictions": { 1914 "label-restriction": [ 1915 { 1916 "index ": 1, 1917 "// ___DEFAULT___ restriction": "inclusive", 1918 "range-type": "label-range-trib-port", 1919 "// ___NOT-PRESENT___ tsg": "", 1920 "odu-type-list": "[ ODU2 ]", 1921 "// ___ DEFAULT ___ priority": 7, 1922 "// tpn-range": 1, 1923 "// ___ COMMENT ___": "Since no TS range and no TSG are \ 1924 \reported for ODU2, the link is an OTU2 Link. TS allocation is not n\ 1925 \eeded and TPN shall be set to '1' for mapping ODU2 over OTU2. This \ 1926 \entry is not present if the OTN Link is an HO-ODU2 Link." 1927 }, 1928 { 1929 "index ": 2, 1930 "// ___DEFAULT___ restriction": "inclusive", 1931 "range-type": "label-range-trib-slot", 1932 "tsg": "tsg-1.25G", 1933 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ 1935 \ ]", 1936 "// ___ DEFAULT ___ priority": 7, 1937 "// ts-range": "1-8" 1938 }, 1939 { 1940 "index ": 3, 1941 "// ___DEFAULT___ restriction": "inclusive", 1942 "range-type": "label-range-trib-port", 1943 "tsg": "tsg-1.25G ", 1944 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0 ]", 1945 "// ___ DEFAULT ___ priority": 7, 1946 "// tpn-range": "1-8", 1947 "// ___ COMMENT ___": "Since this TPN range is reported \ 1948 \for ODUflex and ODU0 with 1.25G TSG, the TPN assignment rule is fle\ 1949 \xible within a common range for mapping LO-ODUflex and LO-ODU0 over\ 1950 \ HO-ODU2 with 1.25G TSG. See Table 4 of [RFC7139]." 1951 }, 1952 { 1953 "index ": 4, 1954 "// ___DEFAULT___ restriction": "inclusive", 1955 "range-type": "label-range-trib-port", 1956 "tsg": "tsg-1.25G", 1957 "odu-type-list": "[ ODU1 ]", 1958 "// ___ DEFAULT ___ priority": 7, 1959 "// tpn-range": "1-4", 1960 "// ___ COMMENT ___": "Since this TPN range is reported \ 1961 \for ODU1 with 1.25G TSG, the TPN assignment rule is flexible within\ 1962 \ a common range for mapping LO-ODU1 over HO-ODU2 with 1.25G TSG. Se\ 1963 \e Table 4 of [RFC7139]." 1964 }, 1965 { 1966 "index ": 5, 1967 "// ___DEFAULT___ restriction": "inclusive", 1968 "range-type": "label-range-trib-slot", 1969 "tsg": "tsg-2.5G", 1970 "odu-type-list": "[ ODU1 ]", 1971 "// ___ DEFAULT ___ priority": 7, 1972 "// ts-range": "1-4", 1973 "// ___ COMMENT ___": "Since no TPN range is reported fo\ 1974 \r ODU1 with 2.5G TSG, the TPN allocation rule is fixed (TPN = TS#) \ 1975 \for mapping LO-ODU1 over HO-ODU2 with 2.5G TSG. See Table 3 of [RFC\ 1976 \7139]." 1977 } 1978 ] 1979 } 1980 }, 1981 { 1982 "// ": "HO-ODU3 or OTU3 Link", 1983 "label-restrictions": { 1984 "label-restriction": [ 1985 { 1986 "index ": 1, 1987 "// ___DEFAULT___ restriction": "inclusive", 1988 "range-type": "label-range-trib-port", 1989 "// ___NOT-PRESENT___ tsg": "", 1990 "odu-type-list": "[ ODU3 ]", 1991 "// ___ DEFAULT ___ priority": 7, 1992 "// tpn-range": 1, 1993 "// ___ COMMENT ___": "Since no TS range and no TSG are \ 1994 \reported for ODU3, the link is an OTU3 Link. TS allocation is not n\ 1995 \eeded and TPN shall be set to '1' for mapping ODU3 over OTU3. This \ 1996 \entry is not present if the OTN Link is an HO-ODU3 Link." 1997 }, 1998 { 1999 "index ": 2, 2000 "// ___DEFAULT___ restriction": "inclusive", 2001 "range-type": "label-range-trib-slot", 2002 "tsg": "tsg-1.25G", 2003 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ 2004 \, ODU2, ODU2e ]", 2005 "// ___ DEFAULT ___ priority": 7, 2006 "// ts-range": "1-32" 2007 }, 2008 { 2009 "index ": 3, 2010 "// ___DEFAULT___ restriction": "inclusive", 2011 "range-type": "label-range-trib-port", 2012 "tsg": "tsg-1.25G", 2013 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU2\ 2014 \e ]", 2015 "// ___ DEFAULT ___ priority": 7, 2016 "// tpn-range": "1-32", 2017 "// ___ COMMENT ___": "Since this TPN range is reported \ 2018 \for ODUflex, ODU0 and ODU2e with 1.25G TSG, the TPN assignment rule\ 2019 \ is flexible within a common range for mapping LO-ODUflex, LO-ODU0 \ 2020 \and LO-ODU2e over HO-ODU3 with 1.25G TSG. See Table 4 of [RFC7139]." 2021 }, 2022 { 2023 "index ": 4, 2024 "// ___DEFAULT___ restriction": "inclusive", 2025 "range-type": "label-range-trib-port", 2026 "tsg": "tsg-1.25G", 2027 "odu-type-list": "[ ODU1 ]", 2028 "// ___ DEFAULT ___ priority": 7, 2029 "// tpn-range": "1-16", 2030 "// ___ COMMENT ___": "Since this TPN range is reported \ 2032 \for ODU1 with 1.25G TSG, the TPN assignment rule is flexible within\ 2033 \ a common range for mapping LO-ODU1 over HO-ODU3 with 1.25G TSG. Se\ 2034 \e Table 4 of [RFC7139]." 2035 }, 2036 { 2037 "index ": 5, 2038 "// ___DEFAULT___ restriction": "inclusive", 2039 "range-type": "label-range-trib-port", 2040 "tsg": "tsg-1.25G", 2041 "odu-type-list": "[ ODU2 ]", 2042 "// ___ DEFAULT ___ priority": 7, 2043 "// tpn-range": "1-4", 2044 "// ___ COMMENT ___": "Since this TPN range is reported \ 2045 \for ODU2 with 1.25G TSG, the TPN assignment rule is flexible within\ 2046 \ a common range for mapping LO-ODU2 over HO-ODU3 with 1.25G TSG. Se\ 2047 \e Table 4 of [RFC7139]." 2048 }, 2049 { 2050 "index ": 6, 2051 "// ___DEFAULT___ restriction": "inclusive", 2052 "range-type": "label-range-trib-slot", 2053 "tsg": "tsg-2.5G", 2054 "odu-type-list": "[ ODU1, ODU2 ]", 2055 "// ___ DEFAULT ___ priority": 7, 2056 "// ts-range": "1-16" 2057 }, 2058 { 2059 "index ": 7, 2060 "// ___DEFAULT___ restriction": "inclusive", 2061 "range-type": "label-range-trib-port", 2062 "tsg": "tsg-2.5G ", 2063 "odu-type-list": "[ ODU2 ]", 2064 "// ___ DEFAULT ___ priority": 7, 2065 "// tpn-range": "1-4", 2066 "// ___ COMMENT ___": "Since this TPN range is reported \ 2067 \for ODU2 with 2.5G TSG, the TPN assignment rule is flexible within \ 2068 \a common range for mapping LO-ODU2 over HO-ODU3. Since no TPN range\ 2069 \ is reported for ODU1 with 2.5G TSG, the TPN allocation rule is fix\ 2070 \ed (TPN = TS#) for mapping LO-ODU1 over HO-ODU3 with 2.5G TSG. See \ 2071 \Table 3 of [RFC7139]." 2072 } 2073 ] 2074 } 2075 }, 2076 { 2077 "// ": "HO-ODU4 or OTU4 Link", 2078 "label-restrictions": { 2079 "label-restriction": [ 2080 { 2081 "index ": 1, 2082 "// ___DEFAULT___ restriction": "inclusive", 2083 "range-type": "label-range-trib-port", 2084 "// ___NOT-PRESENT___ tsg": "", 2085 "odu-type-list": "[ ODU4 ]", 2086 "// ___ DEFAULT ___ priority": 7, 2087 "// tpn-range": 1, 2088 "// ___ COMMENT ___": "Since no TS range and no TSG are \ 2089 \reported for ODU4, the link is an OTU4 Link. TS allocation is not n\ 2090 \eeded and TPN shall be set to '1' for mapping ODU4 over OTU4. This \ 2091 \entry is not present if the OTN Link is an HO-ODU4 Link." 2092 }, 2093 { 2094 "index ": 2, 2095 "// ___DEFAULT___ restriction": "inclusive", 2096 "range-type": "label-range-trib-slot", 2097 "tsg": "tsg-1.25G", 2098 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ 2099 \, ODU2, ODU2e, ODU3 ]", 2100 "// ___ DEFAULT ___ priority": 7, 2101 "// ts-range": "1-80" 2102 }, 2103 { 2104 "index ": 3, 2105 "// ___DEFAULT___ restriction": "inclusive", 2106 "range-type": "label-range-trib-port", 2107 "tsg": "tsg-1.25G", 2108 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ 2109 \, ODU2, ODU2e, ODU3 ]", 2110 "// ___ DEFAULT ___ priority": 7, 2111 "// tpn-range": "1-80", 2112 "// ___ COMMENT ___": "Since this TPN range is reported \ 2113 \for any LO-ODUj with 1.25G TSG, the TPN assignment rule is flexible\ 2114 \ within a common range for mapping any LO-ODUj over HO-ODU4 with 1.\ 2115 \25G TSG. See Table 4 of [RFC7139]." 2116 } 2117 ] 2118 } 2119 }, 2120 { 2121 "// ": "ODUC1 Link", 2122 "label-restrictions": { 2123 "label-restriction": [ 2124 { 2125 "index ": 1, 2126 "// ___DEFAULT___ restriction": "inclusive", 2127 "range-type": "label-range-trib-slot", 2128 "tsg": "tsg-5G", 2129 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ 2130 \, ODU2, ODU2e, ODU3, ODU4 ]", 2131 "// ___ DEFAULT ___ priority": 7, 2132 "// ts-range": "1-20", 2133 "// ___ COMMENT ___": "Since the TS range is specified f\ 2134 \or any ODUk, the OTN Link is an ODUCn Link." 2135 }, 2136 { 2137 "index ": 2, 2138 "// ___DEFAULT___ restriction": "inclusive", 2139 "range-type": "label-range-trib-port", 2140 "tsg": "tsg-5G", 2141 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ 2142 \, ODU2, ODU2e, ODU3, ODU4 ]", 2143 "// ___ DEFAULT ___ priority": 7, 2144 "// tpn-range": "1-10", 2145 "// ___ COMMENT ___": "Since this TPN range is reported \ 2146 \for any ODUk with 5G TSG, the TPN assignment rule is flexible withi\ 2147 \n a common range for mapping any ODUk over ODUCn with 5G TSG." 2148 } 2149 ] 2150 } 2151 } 2152 ] 2153 } 2155 Authors' Addresses 2157 Haomian Zheng 2158 Huawei Technologies 2159 H1, Huawei Xiliu Beipo Village, Songshan Lake 2160 Dongguan, Guangdong 523808 2161 China 2163 Email: zhenghaomian@huawei.com 2165 Italo Busi 2166 Huawei Technologies 2167 Milan 2168 Italy 2170 Email: Italo.Busi@huawei.com