idnits 2.17.1 draft-ietf-ccamp-layer1-types-13.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 176 has weird spacing: '...du-type ide...' == Line 346 has weird spacing: '...ad-rate uin...' -- The document date (8 April 2022) is 748 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 1745, but no explicit reference was found in the text == Unused Reference: 'RFC4203' is defined on line 1768, 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-06 == Outdated reference: A later version (-26) exists of draft-ietf-ccamp-l1csm-yang-16 == Outdated reference: A later version (-18) exists of draft-ietf-ccamp-otn-topo-yang-14 == Outdated reference: A later version (-20) exists of draft-ietf-ccamp-otn-tunnel-model-15 == Outdated reference: A later version (-17) exists of draft-ietf-ccamp-transport-nbi-app-statement-14 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: 10 October 2022 8 April 2022 7 A YANG Data Model for Layer 1 Types 8 draft-ietf-ccamp-layer1-types-13 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 10 October 2022. 35 Copyright Notice 37 Copyright (c) 2022 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 (https://trustee.ietf.org/ 42 license-info) in effect on the date of publication of this document. 43 Please review these documents carefully, as they describe your rights 44 and restrictions with respect to this document. Code Components 45 extracted from this document must include Revised BSD License text as 46 described in Section 4.e of the Trust Legal Provisions and are 47 provided without warranty as described in the Revised BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 2. Terminology and Notations . . . . . . . . . . . . . . . . . . 3 53 3. Prefix in Data Node Names . . . . . . . . . . . . . . . . . . 3 54 4. Layer 1 Types Overview . . . . . . . . . . . . . . . . . . . 3 55 4.1. Relationship with other Modules . . . . . . . . . . . . . 3 56 4.2. Content in Layer 1 Type Module . . . . . . . . . . . . . 3 57 4.3. OTN Label and Label Range . . . . . . . . . . . . . . . . 6 58 4.4. ODUflex . . . . . . . . . . . . . . . . . . . . . . . . . 8 59 4.4.1. Resizable ODUflex . . . . . . . . . . . . . . . . . . 10 60 5. YANG Code for Layer1 Types . . . . . . . . . . . . . . . . . 10 61 6. Security Considerations . . . . . . . . . . . . . . . . . . . 36 62 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 63 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37 64 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 37 65 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 66 10.1. Normative References . . . . . . . . . . . . . . . . . . 37 67 10.2. Informative References . . . . . . . . . . . . . . . . . 39 68 Appendix A. Examples of OTN Label Ranges . . . . . . . . . . . . 41 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 47 71 1. Introduction 73 This document specifies common data types, groupings and identities 74 for use in YANG [RFC7950] data models of Layer 1 networks. The 75 derived types and groupings are types applicable to modeling Traffic 76 Engineering (TE) for Layer 1 networks. 78 The Optical Transport Networking, a typical Layer 1 network, is 79 specified in [RFC7062]. The corresponding routing and signaling 80 protocol are specified in [RFC7138] and [RFC7139]. The types and 81 groupings defined in this document are consistent to those documents, 82 and can be imported into other Layer 1 data models, including but not 83 limited to, [I-D.ietf-ccamp-otn-topo-yang], 84 [I-D.ietf-ccamp-otn-tunnel-model], 85 [I-D.ietf-ccamp-client-signal-yang] and [I-D.ietf-ccamp-l1csm-yang]. 87 The document is consistent with other specifications, including 88 [MEF63] for Layer 1 service attributes, [ITU-Tg709] and [ITU-Tgsup43] 89 for OTN data plane definitions. 91 The YANG data model in this document only defines groupings, typedef 92 and identities and it does not define any configuration or state 93 data, as specified in the Network Management Datastore Architecture 94 defined in [RFC8342]. 96 2. Terminology and Notations 98 Refer to [RFC7062] for the key terms used in this document. The 99 terminology for describing YANG data models can be found in 100 [RFC7950]. 102 3. Prefix in Data Node Names 104 In this document, names of data nodes and other data model objects 105 are prefixed using the standard prefix associated with the 106 corresponding YANG imported modules, as shown in table 1. 108 +-------------+---------------------------+----------------------+ 109 | Prefix | YANG module | Reference | 110 +-------------+---------------------------+----------------------+ 111 | l1-types | ietf-layer1-types | This Document | 112 +-------------+---------------------------+----------------------+ 113 Table 1: Prefixes and Corresponding YANG Modules 115 RFC Editor Note: Please replace XXXX with the number assigned to the 116 RFC once this draft becomes an RFC. 118 4. Layer 1 Types Overview 120 4.1. Relationship with other Modules 122 This document defines one YANG module for common Layer 1 types. The 123 aim is to specify common Layer 1 TE types (i.e. typedef, identity, 124 grouping) that can be imported by layer 1 specific technology, for 125 example OTN, in its technology-specific modules, such as topology and 126 tunnels. It is worth noting that the generic traffic-engineering 127 (TE) types module is specified in [RFC8776] as ietf-te-types, and 128 both YANG modules, ietf-te-types and ietf-layer1-types, will need 129 importing when the OTN is configured. Generic attributes such as te- 130 bandwidth and te-label, are specified in ietf-te-types in [RFC8776], 131 while the OTN-specific attributes, such as odu-type, are specified in 132 ietf-layer1-types in this document. 134 4.2. Content in Layer 1 Type Module 136 The module ietf-layer1-types contains the following YANG reusable 137 types and groupings: 139 tributary-slot-granularity: 141 This specifies the granularity of the time slots used by the server 142 layer ODU Link (HO ODUk or ODUCn) when supporting client layer ODU 143 LSPs (LO ODUj or ODUk, respectively). Three granularities, 144 1.25G/2.5G/5G, have been specified. 146 odu-type: 148 This specifies the type of ODUk LSP, including the types specified in 149 [RFC7139] and [RFC7963]. 151 client-signal: 153 This specifies the client signal types of OTN networks. The initial 154 input was the G-PID specified in [RFC7139]. Identities for some of 155 the categories of client signal types, including ETH, STM-n, OC 156 [ANSI] and Fiber Channel, have been specified. 158 otn-label-range-type: 160 The label range type of OTN is represented in one of two ways, 161 tributary slots (TS) and tributary port number (TPN), as specified in 162 [RFC7139]. Two representations are enumerated in the otn-label- 163 range-type. 165 otn-link-bandwidth: 167 This grouping defines the link bandwidth information and could be 168 used in OTN topology model for link bandwidth representation. All 169 the bandwidth related sections in generic module, [RFC8776], need to 170 be augmented with this grouping for the usage of Layer 1. The link 171 bandwidth is represented by the number of ODUs that can be supported 172 by the link for each ODU type as follow. 174 +--:(otn) 175 +--rw odulist* [odu-type] 176 +--rw odu-type identityref 177 +--rw number? uint16 179 For example, an OTN link with 100G bandwidth can support either 180 1xODU4, 10xODU2 or 80xODU0. 182 This grouping is also used to represent the ODUflex resources 183 available on a link, as described in section Section 4.4. 185 otn-path-bandwidth: 187 This grouping defines the path bandwidth information and could be 188 used in OTN topology model for path bandwidth representation. All 189 the bandwidth related sections in generic module, [RFC8776], need to 190 be augmented with this grouping for the usage of Layer 1. This 191 grouping is also applicable when setting up the OTN tunnel. The path 192 bandwidth is usually represented by the type of ODU (e.g., ODU0, 193 ODU2, ODU4) being setup along the path as follow. 195 +--:(otn) 196 +--rw odu-type? identityref 198 In case of ODUflex paths, more information about the bandwidth of the 199 ODUflex needs to be provided, as described in section Section 4.4. 201 otn-label-range-info: 203 This grouping is used to augment the label-restriction list, defined 204 in [RFC8776], with OTN technology-specific attributes, as defined in 205 section Section 4.3. 207 +--rw range-type? otn-label-range-type 208 +--rw tsg? identityref 209 +--rw odu-type-list* identityref 210 +--rw priority? uint8 212 otn-label-start-end: 214 This grouping is used to augment the label-start and label-end 215 containers within the label-restriction list, defined in [RFC8776], 216 with OTN technology-specific attributes, as defined in section 217 Section 4.3. 219 +--:(otn) 220 +--rw (range-type)? 221 +--:(trib-port) 222 | +--rw otn-tpn? otn-tpn 223 +--:(trib-slot) 224 +--rw otn-ts? otn-ts 226 otn-label-step: 228 This grouping is used to augment the label-step container within the 229 label-restriction list, defined in [RFC8776], with OTN technology- 230 specific attributes, as defined in section Section 4.3. 232 +--:(otn) 233 +--rw (range-type)? 234 +--:(trib-port) 235 | +--rw otn-tpn? otn-tpn 236 +--:(trib-slot) 237 +--rw otn-ts? otn-ts 239 otn-label-hop: 241 This grouping is used to augment the label-hop container, defined in 242 [RFC8776], with OTN technology-specific attributes, as defined in 243 section Section 4.3. 245 +--:(otn) 246 +--rw otn-tpn? otn-tpn 247 +--rw tsg? identityref 248 +--rw ts-list? string 250 optical-interface-func: 252 The optical interface function is specified in [MEF63]. Identities 253 that describe the functionality are specified to encode bits for 254 transmission and to decode bits upon reception. 256 4.3. OTN Label and Label Range 258 As described in [RFC7139], the OTN label usually represents the 259 Tributary Port Number (TPN) and the related set of Tributary Slots 260 (TS) assigned to a client layer ODU LSP (LO ODUj or ODUk) on a given 261 server layer ODU (HO-ODU or ODUCn, respectively) Link (e.g., ODU2 LSP 262 over ODU3 Link). Some special OTN label values are also defined for 263 an ODUk LSP being set up over an OTUk Link. 265 The same OTN label must be assigned to the same ODUk LSP at the two 266 ends of an OTN Link. 268 As described in [RFC7139], TPN can be a number from 1 to 4095 and TS 269 are numbered from 1 to 4095, although the actual maximum values 270 depend on the type of server layer ODU. For example, a server layer 271 ODU4 provides 80 time slots (numbered from 1 to 80) and the TPN 272 values can be any number from 1 to 80. 274 The OTN Label Range represents the values for the TPN and TS that are 275 available for ODUk LSPs to be setup over a given OTN Link. 277 The OTN Label Range is defined by the label-restriction list, defined 278 in [RFC8776], which, for OTN, should be augmented using the otn- 279 label-range-info grouping. 281 Each entry in the label-restriction list represents either the range 282 of the available TPN values or the range of the available TS values: 283 the range-type attribute in the otn-label-range-info grouping defines 284 the type of range for each entry of the list. 286 Each entry of the label-restriction list, as defined in [RFC8776], 287 defines a label-start, a label-end, a label-step and a range-bitmap. 288 The label-start and label-end definitions for OTN should be augmented 289 using the otn-label-start-end grouping. The label-step definition 290 for OTN should be augmented using the otn-label-step grouping. It is 291 expected that the otn-label-step will always be equal to its default 292 value (i.e., 1), which is defined in [RFC8776]. 294 As described in [RFC7139], in some cases, the TPN assignment rules 295 are flexible (e.g., ODU4 Link) while in other cases the TPN 296 assignment rules are fixed (e.g., ODU1 Link). In the former case, 297 both TPN and TS ranges are reported, while in the latter case, the 298 TPN range is not reported which indicates that the TPN shall be set 299 equal to the TS number assigned to the ODUk LSP. 301 As described in [RFC7139], in some cases, the TPN assignment rules 302 depends on the TS Granularity (e.g., ODU2 or ODU3 Links). Different 303 entries in the label-restriction list will report different TPN 304 ranges for each TS granularity supported by the link, as indicated by 305 the tsg attribute in the otn-label-range-info grouping. 307 As described in [RFC7139], in some cases the TPN ranges are different 308 for different types of ODUk LSPs. For example, on an ODU2 Link with 309 1.25G TS granularity, the TPN range is 1-4 for ODU1 but 1-8 for ODU0 310 and ODUflex. Different entries in the label-restriction list will 311 report different TPN ranges for different set of ODUk types, as 312 indicated by the odu-type-list in the otn-label-range-info grouping. 314 Appendix A provides some examples of how the TPN and TS label ranges 315 described in Table 3 and Table 4 of [RFC7139] can be represented in 316 YANG using the groupings defined in this document. 318 4.4. ODUflex 320 ODUflex is a type of ODU which has a flexible bit rate which is 321 configured when setting up an ODUflex LSP. 323 [ITU-Tg709], defines six types of ODUflex: ODUflex(CBR), 324 ODUflex(GFP), ODUflex(GFP,n,k), ODUflex(IMP), ODUflex(IMP,s) and 325 ODUflex(FlexE-aware). 327 The main difference between these types of ODUflex is the formula 328 used to calculate the nominal bit rate of the ODUflex, as described 329 in Table 7-2 of [ITU-Tg709]. A YANG choice has been defined to 330 describe these cases: 332 +--rw (oduflex-type)? 333 +--:(generic) 334 | +--rw nominal-bit-rate uint64 335 +--:(cbr) 336 | +--rw client-type identityref 337 +--:(gfp-n-k) 338 | +--rw gfp-n uint8 339 | +--rw gfp-k? l1-types:gfp-k 340 +--:(flexe-client) 341 | +--rw flexe-client 342 | l1-types:flexe-client-rate 343 +--:(flexe-aware) 344 | +--rw flexe-aware-n uint16 345 +--:(packet) 346 +--rw opuflex-payload-rate uint64 348 The 'generic' case has been added to allow the ODUflex nominal bit 349 rate to be defined independently from the type of ODUflex. This 350 could be useful for forward compatibility in the transit domain/nodes 351 where the setup of ODUflex LSPs does not depend on the ODUflex type. 353 In order to simplify interoperability the 'generic' case should be 354 used only when it is needed; the ODUflex type-specific case should be 355 used whenever possible. 357 The 'cbr' case is used for Constant Bit Rate (CBR) client signals. 358 The client-type indicates which CBR client signal is carried by the 359 ODUflex and, implicitly, the client signal bit rate which is then 360 used to calculate the ODUflex(CBR) nominal bit rate as described in 361 Table 7-2 of [ITU-Tg709]. 363 The 'gfp-n-k' case is used for GFP-F mapped client signals based on 364 ODUk.ts and 'n' 1.25G tributary slots. 'gfp-k' defines the nominal 365 bit-rate of the ODUk.ts which, together with the value of 'gfp-n', is 366 used to calculated the ODUflex(GFP,n,k) nominal bit rate as described 367 in Table 7-8 and Table L-7 of [ITU-Tg709] . With a few exceptions, 368 shown in Table L-7 of [ITU-Tg709], the nominal bit-rate of the 369 ODUk.ts could be inferred from the value of 'n', as shown in 370 Table 7-8 of [ITU-Tg709] and therefore the 'gfp-k' is optional. 372 The 'flexe-client' case is used for Idle Mapping Procedure(IMP) 373 mapped FlexE client signals, The 'flexe-client' represents the type 374 of FlexE client carried by the ODUflex which implicitly defines the 375 value of 's' used to calculate the ODUflex(s) nominal bit rate as 376 described in Table 7-2 of [ITU-Tg709]. The '10G' and '40G' 377 enumeration values are used for 10G and 40G FlexE clients to 378 implicitly define the values of s=2 and s=8. For the 'n x 25G' FlexE 379 Clients the value of 'n' is used to defines the value of s=5 x n. 381 The 'flexe-aware' case is used for FlexE-aware client signals. The 382 flexe-aware-n represents the value n (n = n1 + n2 + ... + np) which 383 is used to calculate the ODUflex(FlexE-aware) nominal bit rate as 384 described in Table 7-2 of [ITU-Tg709]. 386 The 'packet' case is used for both the GFP-F mapped client signals 387 and the IMP mapped client signals. The opuflex-payload-rate is 388 either the GFP-F encapsulated-packet client nominal bit rate or the 389 64b/66b encoded-packet client nominal bit rate. The calculation of 390 ODUflex(GFP) nominal bit rate is defined in section 12.2.5 of 391 [ITU-Tg709], and the calculation of ODUflex(IMP) nominal bit rate is 392 defined in section 12.2.6 of [ITU-Tg709]. The same formula is used 393 in both cases. 395 Section 5.1 and 5.2 of [RFC7139] defines two rules to compute the 396 number of tributary slots to be allocated to ODUflex(CBR) and 397 ODUflex(GFP) LSPs when carried over a HO-ODUk link. According to 398 section 19.6 of [ITU-Tg709], the rules in section 5.2 apply only to 399 ODUflex(GFP,n,k) while the rules defined in section 5.1 apply to any 400 other ODUflex type, including, but not limited, to ODUflex(CBR). 401 Section 20.5 of [ITU-Tg709] defines the rules for computing the 402 number of tributary slots to be allocated to ODUflex LSPs when 403 carried over an ODUCn link. 405 Following the [ITU-Tg709] definitions, the rules defined for 406 ODUflex(GFP,n,k) are used only when the 'gfp-n-k' case is used. In 407 all the other cases, including the (generic) case, the rules defined 408 any other ODUflex type are used. 410 The number of available ODUs, defined for each ODUk type, including 411 ODUflex, together with the number of available time-slots, reported 412 as part of the OTN label range, provide sufficient information to 413 infer the OTN link bandwidth availability for ODUflex LSPs. This 414 information is independent of the ODUflex type. 416 4.4.1. Resizable ODUflex 418 Resizable ODUflex is a special type of ODUflex that supports the 419 procedures defined in [ITU-Tg7044] for hitless resizing of the 420 ODUflex nominal bit rate. 422 Two odu-type identities have been defined for ODUflex: 424 * The ODUflex identity, which is used with any type of non-resizable 425 ODUflex, as defined in Table 7-2 of [ITU-Tg709]. 427 * The ODUflex-resizable identity, which is used only with resizable 428 ODUflex(GFP,n,k). 430 These two identities are used to identify whether an ODUflex(GFP,n,k) 431 LSP does or does support the [ITU-Tg7044] hitless resizing 432 procedures. They also identify whether an OTN link only supports the 433 setup of non-resizable ODUflex LSPs or also supports the setup of 434 resizable ODUflex(GFP,n,k) LSP but with different capabilities (e.g., 435 a lower number of LSPs). 437 5. YANG Code for Layer1 Types 439 440 file "ietf-layer1-types@2022-04-07.yang" 441 module ietf-layer1-types { 442 yang-version 1.1; 443 namespace "urn:ietf:params:xml:ns:yang:ietf-layer1-types"; 444 prefix "l1-types"; 446 organization 447 "IETF CCAMP Working Group"; 448 contact 449 "WG Web: 450 WG List: 452 Editor: Haomian Zheng 453 455 Editor: Italo Busi 456 "; 458 description 459 "This module defines Layer 1 types. The model fully conforms 460 to the Network Management Datastore Architecture (NMDA). 462 Copyright (c) 2022 IETF Trust and the persons 463 identified as authors of the code. All rights reserved. 465 Redistribution and use in source and binary forms, with or 466 without modification, is permitted pursuant to, and subject 467 to the license terms contained in, the Simplified BSD License 468 set forth in Section 4.c of the IETF Trust's Legal Provisions 469 Relating to IETF Documents 470 (https://trustee.ietf.org/license-info). 471 This version of this YANG module is part of RFC XXXX; see 472 the RFC itself for full legal notices."; 474 revision "2022-04-07" { 475 description 476 "Initial Version"; 477 reference 478 "RFC XXXX: A YANG Data Model for Layer 1 Types"; 479 // RFC Editor: replace XXXX with actual RFC number, update date 480 // information and remove this note 481 } 483 /* 484 * Identities 485 */ 487 identity tributary-slot-granularity { 488 description 489 "Tributary slot granularity"; 490 reference 491 "ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 492 Transport Network (OTN)"; 493 } 495 identity tsg-1.25G { 496 base tributary-slot-granularity; 497 description 498 "1.25G tributary slot granularity"; 499 } 500 identity tsg-2.5G { 501 base tributary-slot-granularity; 502 description 503 "2.5G tributary slot granularity"; 504 } 506 identity tsg-5G { 507 base tributary-slot-granularity; 508 description 509 "5G tributary slot granularity"; 510 } 512 identity odu-type { 513 description 514 "Base identity from which specific ODU protocol is derived."; 515 } 517 identity ODU0 { 518 base odu-type; 519 description 520 "ODU0 protocol (1.24Gb/s)."; 521 reference 522 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 523 G.709 Optical Transport Networks 525 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 526 Transport Network (OTN)"; 527 } 529 identity ODU1 { 530 base odu-type; 531 description 532 "ODU1 protocol (2.49Gb/s)."; 533 reference 534 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 535 G.709 Optical Transport Networks 537 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 538 Transport Network (OTN)"; 539 } 541 identity ODU1e { 542 base odu-type; 543 description 544 "ODU1e protocol (10.35Gb/s)."; 545 reference 546 "RFC7963: RSVP-TE Extension for Additional Signal Types in 547 G.709 Optical Transport Networks (OTNs) 548 ITU-T G.sup43 v5.0 (02/2011): Transport of IEEE 10GBASE-R 549 in optical transport networks (OTN)"; 550 } 552 identity ODU2 { 553 base odu-type; 554 description 555 "ODU2 protocol (10.03Gb/s)."; 556 reference 557 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 558 G.709 Optical Transport Networks 560 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 561 Transport Network (OTN)"; 562 } 564 identity ODU2e { 565 base odu-type; 566 description 567 "ODU2e protocol (10.39Gb/s)."; 568 reference 569 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 570 G.709 Optical Transport Networks 572 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 573 Transport Network (OTN)"; 574 } 576 identity ODU3 { 577 base odu-type; 578 description 579 "ODU3 protocol (40.31Gb/s)."; 580 reference 581 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 582 G.709 Optical Transport Networks 584 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 585 Transport Network (OTN)"; 586 } 588 identity ODU3e1 { 589 base odu-type; 590 description 591 "ODU3e1 protocol (41.77Gb/s)."; 592 reference 593 "RFC7963: RSVP-TE Extension for Additional Signal Types in 594 G.709 Optical Transport Networks (OTNs) 595 ITU-T G.sup43 v5.0 (02/2011): Transport of IEEE 10GBASE-R 596 in optical transport networks (OTN)"; 597 } 599 identity ODU3e2 { 600 base odu-type; 601 description 602 "ODU3e2 protocol (41.78Gb/s)."; 603 reference 604 "RFC7963: RSVP-TE Extension for Additional Signal Types in 605 G.709 Optical Transport Networks (OTNs) 607 ITU-T G.sup43 v5.0 (02/2011): Transport of IEEE 10GBASE-R 608 in optical transport networks (OTN)"; 609 } 611 identity ODU4 { 612 base odu-type; 613 description 614 "ODU4 protocol (104.79Gb/s)."; 615 reference 616 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 617 G.709 Optical Transport Networks 619 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 620 Transport Network (OTN)"; 621 } 623 identity ODUflex { 624 base odu-type; 625 description 626 "ODUflex protocol (flexibile bit rate, not resizable). 628 It could be used for any type of ODUflex, including 629 ODUflex(CBR), ODUflex(GFP), ODUflex(GFP,n,k), ODUflex(IMP,s), 630 ODUflex(IMP) and ODUflex(FlexE-aware)."; 631 reference 632 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 633 G.709 Optical Transport Networks 635 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 636 Transport Network (OTN)"; 637 } 639 identity ODUflex-resizable { 640 base odu-type; 641 description 642 "ODUflex protocol (flexibile bit rate, resizable). 644 It could be used only for ODUflex(GFP,n,k)."; 645 reference 646 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 647 G.709 Optical Transport Networks 649 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 650 Transport Network (OTN)"; 651 } 653 identity protocol { 654 description 655 "Base identity from which specific protocol is derived."; 656 reference 657 "MEF63: Subscriber Layer 1 Service Attributes"; 658 } 660 identity Ethernet { 661 base protocol; 662 description 663 "Ethernet protocol."; 664 reference 665 "MEF63: Subscriber Layer 1 Service Attributes"; 666 } 668 identity Fibre-Channel { 669 base protocol; 670 description 671 "Fibre-Channel (FC) protocol."; 672 reference 673 "MEF63: Subscriber Layer 1 Service Attributes"; 674 } 676 identity SDH { 677 base protocol; 678 description 679 "SDH protocol."; 680 reference 681 "MEF63: Subscriber Layer 1 Service Attributes"; 682 } 684 identity SONET { 685 base protocol; 686 description 687 "SONET protocol."; 688 reference 689 "MEF63: Subscriber Layer 1 Service Attributes"; 690 } 691 identity client-signal { 692 description 693 "Base identity from which specific client signal is derived"; 694 } 696 identity coding-func { 697 description 698 "Base identity from which specific coding function 699 is derived."; 700 reference 701 "MEF63: Subscriber Layer 1 Service Attributes"; 702 } 704 identity ETH-1Gb { 705 base client-signal; 706 description 707 "Client signal type of 1GbE"; 708 reference 709 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 710 G.709 Optical Transport Networks 712 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 713 Transport Network (OTN)"; 714 } 716 identity ETH-10Gb-LAN { 717 base client-signal; 718 description 719 "Client signal type of ETH-10Gb-LAN (10.3 Gb/s)"; 720 reference 721 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 722 G.709 Optical Transport Networks 724 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 725 Transport Network (OTN) 727 IEEE 802.3-2018, Clause 49: IEEE Standard for Ethernet"; 728 } 730 identity ETH-10Gb-WAN { 731 base client-signal; 732 description 733 "Client signal type of ETH-10Gb-WAN (9.95 Gb/s)"; 734 reference 735 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 736 G.709 Optical Transport Networks 738 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 739 Transport Network (OTN) 741 IEEE 802.3-2018, Clause 50: IEEE Standard for Ethernet"; 742 } 744 identity ETH-40Gb { 745 base client-signal; 746 description 747 "Client signal type of 40GbE"; 748 reference 749 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 750 G.709 Optical Transport Networks 752 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 753 Transport Network (OTN)"; 754 } 756 identity ETH-100Gb { 757 base client-signal; 758 description 759 "Client signal type of 100GbE"; 760 reference 761 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 762 G.709 Optical Transport Networks 764 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 765 Transport Network (OTN)"; 766 } 768 identity STM-1 { 769 base client-signal; 770 base coding-func; 771 description 772 "Client signal type of STM-1; 773 STM-1 G.707 (N=1) coding function."; 774 reference 775 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 776 G.709 Optical Transport Networks 778 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 779 Transport Network (OTN) 781 MEF63: Subscriber Layer 1 Service Attributes"; 782 } 784 identity STM-4 { 785 base client-signal; 786 base coding-func; 787 description 788 "Client signal type of STM-4; 789 STM-4 G.707 (N=4) coding function."; 790 reference 791 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 792 G.709 Optical Transport Networks 794 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 795 Transport Network (OTN) 797 MEF63: Subscriber Layer 1 Service Attributes"; 798 } 800 identity STM-16 { 801 base client-signal; 802 base coding-func; 803 description 804 "Client signal type of STM-16; 805 STM-16 G.707 (N=16) coding function."; 806 reference 807 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 808 G.709 Optical Transport Networks 810 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 811 Transport Network (OTN) 813 MEF63: Subscriber Layer 1 Service Attributes"; 814 } 816 identity STM-64 { 817 base client-signal; 818 base coding-func; 819 description 820 "Client signal type of STM-64; 821 STM-64 G.707 (N=64) coding function."; 822 reference 823 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 824 G.709 Optical Transport Networks 826 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 827 Transport Network (OTN) 829 MEF63: Subscriber Layer 1 Service Attributes"; 830 } 832 identity STM-256 { 833 base client-signal; 834 base coding-func; 835 description 836 "Client signal type of STM-256; 837 STM-256 G.707 (N=256) coding function."; 838 reference 839 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 840 G.709 Optical Transport Networks 842 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 843 Transport Network (OTN) 845 MEF63: Subscriber Layer 1 Service Attributes"; 846 } 848 identity OC-3 { 849 base client-signal; 850 base coding-func; 851 description 852 "Client signal type of OC3; 853 OC-3 GR-253-CORE (N=3) coding function."; 854 reference 855 "ANSI T1.105-1995: Synchronous Optical Network (SONET) 856 Basic Description including Multiplex Structure, Rates, 857 and Formats 859 MEF63: Subscriber Layer 1 Service Attributes"; 860 } 862 identity OC-12 { 863 base client-signal; 864 base coding-func; 865 description 866 "Client signal type of OC12; 867 OC-12 GR-253-CORE (N=12) coding function."; 868 reference 869 "ANSI T1.105-1995: Synchronous Optical Network (SONET) 870 Basic Description including Multiplex Structure, Rates, 871 and Formats 873 MEF63: Subscriber Layer 1 Service Attributes"; 874 } 876 identity OC-48 { 877 base client-signal; 878 base coding-func; 879 description 880 "Client signal type of OC48; 881 OC-48 GR-253-CORE (N=48) coding function."; 882 reference 883 "ANSI T1.105-1995: Synchronous Optical Network (SONET) 884 Basic Description including Multiplex Structure, Rates, 885 and Formats 887 MEF63: Subscriber Layer 1 Service Attributes"; 888 } 890 identity OC-192 { 891 base client-signal; 892 base coding-func; 893 description 894 "Client signal type of OC192; 895 OC-192 GR-253-CORE (N=192) coding function."; 896 reference 897 "ANSI T1.105-1995: Synchronous Optical Network (SONET) 898 Basic Description including Multiplex Structure, Rates, 899 and Formats 901 MEF63: Subscriber Layer 1 Service Attributes"; 902 } 904 identity OC-768 { 905 base client-signal; 906 base coding-func; 907 description 908 "Client signal type of OC768; 909 OC-768 GR-253-CORE (N=768) coding function."; 910 reference 911 "ANSI T1.105-1995: Synchronous Optical Network (SONET) 912 Basic Description including Multiplex Structure, Rates, 913 and Formats 915 MEF63: Subscriber Layer 1 Service Attributes"; 916 } 918 identity FC-100 { 919 base client-signal; 920 base coding-func; 921 description 922 "Client signal type of Fibre Channel FC-100; 923 FC-100 FC-FS-2 (1.0625 Gb/s) coding function."; 924 reference 925 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 926 G.709 Optical Transport Networks 928 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 929 Transport Network (OTN) 930 MEF63: Subscriber Layer 1 Service Attributes"; 931 } 933 identity FC-200 { 934 base client-signal; 935 base coding-func; 936 description 937 "Client signal type of Fibre Channel FC-200; 938 FC-200 FC-FS-2 (2.125 Gb/s) coding function."; 939 reference 940 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 941 G.709 Optical Transport Networks 943 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 944 Transport Network (OTN) 946 MEF63: Subscriber Layer 1 Service Attributes"; 947 } 949 identity FC-400 { 950 base client-signal; 951 base coding-func; 952 description 953 "Client signal type of Fibre Channel FC-400; 954 FC-400 FC-FS-2 (4.250 Gb/s) coding function."; 955 reference 956 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 957 G.709 Optical Transport Networks 959 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 960 Transport Network (OTN) 962 MEF63: Subscriber Layer 1 Service Attributes"; 963 } 965 identity FC-800 { 966 base client-signal; 967 base coding-func; 968 description 969 "Client signal type of Fibre Channel FC-800; 970 FC-800 FC-FS-2 (8.500 Gb/s) coding function."; 971 reference 972 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 973 G.709 Optical Transport Networks 975 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 976 Transport Network (OTN) 977 MEF63: Subscriber Layer 1 Service Attributes"; 978 } 980 identity FC-1200 { 981 base client-signal; 982 base coding-func; 983 description 984 "Client signal type of Fibre Channel FC-1200; 985 FC-1200 FC-10GFC (10.51875 Gb/s) coding function."; 986 reference 987 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 988 G.709 Optical Transport Networks 990 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 991 Transport Network (OTN) 993 MEF63: Subscriber Layer 1 Service Attributes"; 994 } 996 identity FC-1600 { 997 base client-signal; 998 base coding-func; 999 description 1000 "Client signal type of Fibre Channel FC-1600; 1001 FC-1600 FC-FS-3 (14.025 Gb/s) coding function."; 1002 reference 1003 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1004 G.709 Optical Transport Networks 1006 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1007 Transport Network (OTN) 1009 MEF63: Subscriber Layer 1 Service Attributes"; 1010 } 1012 identity FC-3200 { 1013 base client-signal; 1014 base coding-func; 1015 description 1016 "Client signal type of Fibre Channel FC-3200; 1017 FC-3200 FC-FS-4 (28.05 Gb/s) coding function."; 1018 reference 1019 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1020 G.709 Optical Transport Networks 1022 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1023 Transport Network (OTN) 1024 MEF63: Subscriber Layer 1 Service Attributes"; 1025 } 1027 identity FICON-4G { 1028 base client-signal; 1029 description 1030 "Client signal type of Fibre Connection 4G"; 1031 reference 1032 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1033 G.709 Optical Transport Networks 1035 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1036 Transport Network (OTN)"; 1037 } 1039 identity FICON-8G { 1040 base client-signal; 1041 description 1042 "Client signal type of Fibre Connection 8G"; 1043 reference 1044 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1045 G.709 Optical Transport Networks 1047 ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1048 Transport Network (OTN)"; 1049 } 1051 identity ETH-1000X { 1052 base coding-func; 1053 description 1054 "1000BASE-X PCS clause 36 coding function."; 1055 reference 1056 "MEF63: Subscriber Layer 1 Service Attributes"; 1057 } 1059 identity ETH-10GW { 1060 base coding-func; 1061 description 1062 "10GBASE-W (WAN PHY) PCS clause 49 and WIS clause 50 1063 coding function."; 1064 reference 1065 "MEF63: Subscriber Layer 1 Service Attributes"; 1066 } 1068 identity ETH-10GR { 1069 base coding-func; 1070 description 1071 "10GBASE-R (LAN PHY) PCS clause 49 coding function."; 1073 reference 1074 "MEF63: Subscriber Layer 1 Service Attributes"; 1075 } 1077 identity ETH-40GR { 1078 base coding-func; 1079 description 1080 "40GBASE-R PCS clause 82 coding function."; 1081 reference 1082 "MEF63: Subscriber Layer 1 Service Attributes"; 1083 } 1085 identity ETH-100GR { 1086 base coding-func; 1087 description 1088 "100GBASE-R PCS clause 82 coding function."; 1089 reference 1090 "MEF63: Subscriber Layer 1 Service Attributes"; 1091 } 1093 identity optical-interface-func { 1094 description 1095 "Base identity from which optical-interface-function 1096 is derived."; 1097 reference 1098 "MEF63: Subscriber Layer 1 Service Attributes"; 1099 } 1101 identity SX-PMD-1000 { 1102 base optical-interface-func; 1103 description 1104 "SX-PMD-clause-38 Optical Interface function for 1105 1000BASE-X PCS-36"; 1106 reference 1107 "MEF63: Subscriber Layer 1 Service Attributes"; 1108 } 1110 identity LX-PMD-1000 { 1111 base optical-interface-func; 1112 description 1113 "LX-PMD-clause-38 Optical Interface function for 1114 1000BASE-X PCS-36"; 1115 reference 1116 "MEF63: Subscriber Layer 1 Service Attributes"; 1117 } 1119 identity LX10-PMD-1000 { 1120 base optical-interface-func; 1121 description 1122 "LX10-PMD-clause-59 Optical Interface function for 1123 1000BASE-X PCS-36"; 1124 reference 1125 "MEF63: Subscriber Layer 1 Service Attributes"; 1126 } 1128 identity BX10-PMD-1000 { 1129 base optical-interface-func; 1130 description 1131 "BX10-PMD-clause-59 Optical Interface function for 1132 1000BASE-X PCS-36"; 1133 reference 1134 "MEF63: Subscriber Layer 1 Service Attributes"; 1135 } 1137 identity LW-PMD-10G { 1138 base optical-interface-func; 1139 description 1140 "LW-PMD-clause-52 Optical Interface function for 1141 10GBASE-W PCS-49-WIS-50"; 1142 reference 1143 "MEF63: Subscriber Layer 1 Service Attributes"; 1144 } 1146 identity EW-PMD-10G { 1147 base optical-interface-func; 1148 description 1149 "EW-PMD-clause-52 Optical Interface function for 1150 10GBASE-W PCS-49-WIS-50"; 1151 reference 1152 "MEF63: Subscriber Layer 1 Service Attributes"; 1153 } 1155 identity LR-PMD-10G { 1156 base optical-interface-func; 1157 description 1158 "LR-PMD-clause-52 Optical Interface function for 1159 10GBASE-R PCS-49"; 1160 reference 1161 "MEF63: Subscriber Layer 1 Service Attributes"; 1162 } 1164 identity ER-PMD-10G { 1165 base optical-interface-func; 1166 description 1167 "ER-PMD-clause-52 Optical Interface function for 1168 10GBASE-R PCS-49"; 1170 reference 1171 "MEF63: Subscriber Layer 1 Service Attributes"; 1172 } 1174 identity LR4-PMD-40G { 1175 base optical-interface-func; 1176 description 1177 "LR4-PMD-clause-87 Optical Interface function for 1178 40GBASE-R PCS-82"; 1179 reference 1180 "MEF63: Subscriber Layer 1 Service Attributes"; 1181 } 1183 identity ER4-PMD-40G { 1184 base optical-interface-func; 1185 description 1186 "ER4-PMD-clause-87 Optical Interface function for 1187 40GBASE-R PCS-82"; 1188 reference 1189 "MEF63: Subscriber Layer 1 Service Attributes"; 1190 } 1192 identity FR-PMD-40G { 1193 base optical-interface-func; 1194 description 1195 "FR-PMD-clause-89 Optical Interface function for 1196 40GBASE-R PCS-82"; 1197 reference 1198 "MEF63: Subscriber Layer 1 Service Attributes"; 1199 } 1201 identity LR4-PMD-100G { 1202 base optical-interface-func; 1203 description 1204 "LR4-PMD-clause-88 Optical Interface function for 1205 100GBASE-R PCS-82"; 1206 reference 1207 "MEF63: Subscriber Layer 1 Service Attributes"; 1208 } 1210 identity ER4-PMD-100G { 1211 base optical-interface-func; 1212 description 1213 "ER4-PMD-clause-88 Optical Interface function for 1214 100GBASE-R PCS-82"; 1215 reference 1216 "MEF63: Subscriber Layer 1 Service Attributes"; 1217 } 1218 /* 1219 * Typedefs 1220 */ 1222 typedef otn-tpn { 1223 type uint16 { 1224 range "1..4095"; 1225 } 1226 description 1227 "Tributary Port Number for OTN. "; 1228 reference 1229 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1230 G.709 Optical Transport Networks."; 1231 } 1233 typedef otn-ts { 1234 type uint16 { 1235 range "1..4095"; 1236 } 1237 description 1238 "Tributary Slot for OTN. "; 1239 reference 1240 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 1241 G.709 Optical Transport Networks."; 1242 } 1244 typedef otn-label-range-type { 1245 type enumeration { 1246 enum trib-slot { 1247 description 1248 "Defines a range of OTN tributary slots. "; 1249 } 1250 enum trib-port { 1251 description 1252 "Defines a range of OTN tributary ports. "; 1253 } 1254 } 1255 description 1256 "Defines the type of OTN label range: TS or TPN. "; 1257 } 1259 typedef gfp-k { 1260 type enumeration { 1261 enum 2 { 1262 description 1263 "The ODU2.ts rate (1,249,177.230 kbit/s) is used 1264 to compute the rate of an ODUflex(GFP,n,2). "; 1265 } 1266 enum 3 { 1267 description 1268 "The ODU3.ts rate (1,254,470.354 kbit/s) is used 1269 to compute the rate of an ODUflex(GFP,n,3). "; 1270 } 1271 enum 4 { 1272 description 1273 "The ODU4.ts rate (1,301,467.133 kbit/s) is used 1274 to compute the rate of an ODUflex(GFP,n,4). "; 1275 } 1276 } 1277 description 1278 "The ODUk.ts used to compute the rate of an ODUflex(GFP,n,k)"; 1279 reference 1280 "ITU-T G.709 v6.0 (06/2020), Table 7-8 and L.7: Interfaces for 1281 the Optical Transport Network (OTN)"; 1282 } 1284 typedef flexe-client-rate { 1285 type union { 1286 type uint16; 1287 type enumeration { 1288 enum "10G" { 1289 description 1290 "Represents a 10G FlexE Client signal (s=2)"; 1291 } 1292 enum "40G" { 1293 description 1294 "Represents a 40G FlexE Client signal (s=8)"; 1295 } 1296 } 1297 } 1298 description 1299 "The FlexE Client signal rate (s x 5,156,250.000 kbit/s) 1300 used to compute the rate of an ODUflex(IMP, s). 1301 Valid values for s are s=2 (10G), s=4 (40G) and 1302 s=5 x n (n x 25G). 1303 In the first two cases an enumeration value 1304 (either 10G or 40G) is used, while in the latter case 1305 the value of n is used"; 1306 reference 1307 "ITU-T G.709 v6.0 (06/2020), Table 7-2: Interfaces for the 1308 Optical Transport Network (OTN)"; 1309 } 1311 /* 1312 * Groupings 1313 */ 1315 grouping otn-link-bandwidth { 1316 description 1317 "Bandwidth attributes for OTN links"; 1318 container otn { 1319 description 1320 "Bandwidth attributes for OTN links"; 1321 list odulist { 1322 key "odu-type"; 1323 description 1324 "OTN bandwidth definition"; 1325 leaf odu-type { 1326 type identityref { 1327 base odu-type; 1328 } 1329 description "ODU type"; 1330 } 1331 leaf number { 1332 type uint16; 1333 description "Number of ODUs"; 1334 } 1335 } 1336 } 1337 } 1339 grouping otn-path-bandwidth { 1340 description 1341 "Bandwidth attributes for OTN paths."; 1342 container otn { 1343 description 1344 "Bandwidth attributes for OTN paths."; 1345 leaf odu-type { 1346 type identityref { 1347 base odu-type; 1348 } 1349 description "ODU type"; 1350 } 1351 choice oduflex-type { 1352 when 'derived-from-or-self(./odu-type,"ODUflex") or 1353 derived-from-or-self(./odu-type,"ODUflex-resizable")'{ 1354 description 1355 "Applicable when odu-type is ODUflex or 1356 ODUflex-resizable"; 1357 } 1358 description 1359 "Types of ODUflex used to compute the ODUflex 1360 nominal bit rate."; 1361 reference 1362 "ITU-T G.709 v6.0 (06/2020), Table 7-2: Interfaces for the 1363 Optical Transport Network (OTN)"; 1364 case generic { 1365 leaf nominal-bit-rate { 1366 type uint64; 1367 units "bps"; 1368 mandatory true; 1369 description 1370 "Nominal ODUflex bit rate."; 1371 } 1372 } 1373 case cbr { 1374 leaf client-type { 1375 type identityref { 1376 base client-signal; 1377 } 1378 mandatory true; 1379 description 1380 "The CBR client signal for an ODUflex(CBR)."; 1381 } 1382 } 1383 case gfp-n-k { 1384 leaf gfp-n { 1385 type uint8 { 1386 range "1..80"; 1387 } 1388 mandatory true; 1389 description 1390 "The value of n for an ODUflex(GFP,n,k)."; 1391 reference 1392 "ITU-T G.709 v6.0 (06/2020), Tables 7-8 and L.7: 1393 Interfaces for the Optical Transport Network (OTN)"; 1394 } 1395 leaf gfp-k { 1396 type gfp-k; 1397 description 1398 "The value of k for an ODUflex(GFP,n,k). 1400 If omitted, it is calculated from the value of gfp-n 1401 as described in Table 7-8 of G.709"; 1402 reference 1403 "ITU-T G.709 v6.0 (06/2020), Tables 7-8 and L.7: 1404 Interfaces for the Optical Transport Network (OTN)"; 1405 } 1406 } 1407 case flexe-client { 1408 leaf flexe-client { 1409 type flexe-client-rate; 1410 mandatory true; 1411 description 1412 "The rate of the FlexE-client for an ODUflex(IMP,s)."; 1413 } 1414 } 1415 case flexe-aware { 1416 leaf flexe-aware-n { 1417 type uint16; 1418 mandatory true; 1419 description 1420 "The rate of FlexE-aware client signal 1421 for ODUflex(FlexE-aware)"; 1422 } 1423 } 1424 case packet { 1425 leaf opuflex-payload-rate { 1426 type uint64; 1427 units "Kbps"; 1428 mandatory true; 1429 description 1430 "Either the GFP-F encapsulated packet client nominal 1431 bit rate for an ODUflex(GFP) or the 64b/66b encoded 1432 packet client nominal bit rate for an ODUflex(IMP)."; 1433 } 1434 } 1435 } 1436 } 1437 } 1439 grouping otn-label-range-info { 1440 description 1441 "Label range information for OTN. 1443 This grouping should be used together with the 1444 otn-label-start-end and otn-label-step groupings to provide 1445 OTN technology-specific label information to the models which 1446 use the label-restriction-info grouping defined in the module 1447 ietf-te-types."; 1448 container otn-label-range { 1449 description 1450 "Label range information for OTN."; 1451 leaf range-type { 1452 type otn-label-range-type; 1453 description "The type of range (e.g., TPN or TS) 1454 to which the label range applies"; 1455 } 1456 leaf tsg { 1457 type identityref { 1458 base tributary-slot-granularity; 1460 } 1461 description 1462 "Tributary slot granularity (TSG) to which the label range 1463 applies. 1465 This leaf shall be present when the range-type is TS. 1467 This leaf can be omitted when mapping an ODUk over an OTUk 1468 Link. In this case the range-type is tpn, with only one 1469 entry (ODUk), and the tpn range has only one value (1)."; 1470 reference 1471 "ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1472 Transport Network (OTN)"; 1473 } 1474 leaf-list odu-type-list { 1475 type identityref { 1476 base odu-type; 1477 } 1478 description 1479 "List of ODU types to which the label range applies. 1481 An Empty odu-type-list means that the label range 1482 applies to all the supported ODU types."; 1483 } 1484 leaf priority { 1485 type uint8; 1486 description 1487 "Priority in Interface Switching Capability 1488 Descriptor (ISCD)."; 1489 reference 1490 "RFC4203: OSPF Extensions in Support of Generalized 1491 Multi-Protocol Label Switching (GMPLS)"; 1492 } 1493 } 1494 } 1496 grouping otn-label-start-end { 1497 description 1498 "The OTN label-start or label-end used to specify an OTN label 1499 range. 1501 This grouping is dependent on the range-type defined in the 1502 otn-label-range-info grouping. 1504 This grouping should be used together with the 1505 otn-label-range-info and otn-label-step groupings to provide 1506 OTN technology-specific label information to the models which 1507 use the label-restriction-info grouping defined in the module 1508 ietf-te-types."; 1509 container otn { 1510 description 1511 "Label start or label end for OTN."; 1512 choice range-type { 1513 description 1514 "OTN label range type, either TPN range or TS range"; 1515 case trib-port { 1516 leaf tpn { 1517 when "../../../../otn-label-range/range-type = 1518 'trib-port'" { 1519 description 1520 "Valid only when range-type represented by 1521 trib-port"; 1522 } 1523 type otn-tpn; 1524 description 1525 "Tributary Port Number (TPN)."; 1526 reference 1527 "RFC7139: GMPLS Signaling Extensions for Control of 1528 Evolving G.709 Optical Transport Networks."; 1529 } 1530 } 1531 case trib-slot { 1532 leaf ts { 1533 when "../../../../otn-label-range/range-type = 1534 'trib-slot'" { 1535 description 1536 "Valid only when range-type represented by 1537 trib-slot"; 1538 } 1539 type otn-ts; 1540 description 1541 "Tributary Slot (TS) number."; 1542 reference 1543 "RFC7139: GMPLS Signaling Extensions for Control of 1544 Evolving G.709 Optical Transport Networks"; 1545 } 1546 } 1547 } 1548 } 1549 } 1551 grouping otn-label-hop { 1552 description "OTN Label"; 1553 reference 1554 "RFC7139, section 6: GMPLS Signaling Extensions for Control of 1555 Evolving G.709 Optical Transport Networks"; 1557 container otn { 1558 description 1559 "Label hop for OTN."; 1560 leaf tpn { 1561 type otn-tpn; 1562 description 1563 "Tributary Port Number (TPN)."; 1564 reference 1565 "RFC7139: GMPLS Signaling Extensions for Control of 1566 Evolving G.709 Optical Transport Networks."; 1567 } 1568 leaf tsg { 1569 type identityref { 1570 base tributary-slot-granularity; 1571 } 1572 description "Tributary Slot Granularity (TSG)."; 1573 reference 1574 "ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical 1575 Transport Network (OTN)"; 1576 } 1577 leaf ts-list { 1578 type string { 1579 pattern "([1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?" 1580 + "(,[1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?)*)"; 1581 } 1582 description 1583 "A list of available Tributary Slots (TS) ranging 1584 between 1 and 4095. If multiple values or 1585 ranges are given, they all must be disjoint 1586 and must be in ascending order. 1587 For example 1-20,25,50-1000."; 1588 reference 1589 "RFC 7139: GMPLS Signaling Extensions for Control 1590 of Evolving G.709 Optical Transport Networks"; 1591 } 1592 } 1593 } 1595 grouping otn-label-step { 1596 description 1597 "Label step for OTN. 1599 This grouping is dependent on the range-type defined in the 1600 otn-label-range-info grouping. 1602 This grouping should be used together with the 1603 otn-label-range-info and otn-label-start-end groupings to 1604 provide OTN technology-specific label information to the 1605 models which use the label-restriction-info grouping defined 1606 in the module ietf-te-types."; 1607 container otn { 1608 description 1609 "Label step for OTN"; 1610 choice range-type { 1611 description 1612 "OTN label range type, either TPN range or TS range"; 1613 case trib-port { 1614 leaf tpn { 1615 when "../../../otn-label-range/range-type = 1616 'trib-port'" { 1617 description 1618 "Valid only when range-type represented by 1619 trib-port"; 1620 } 1621 type otn-tpn; 1622 description 1623 "Label step which represents possible increments for 1624 Tributary Port Number (TPN)."; 1625 reference 1626 "RFC7139: GMPLS Signaling Extensions for Control of 1627 Evolving G.709 Optical Transport Networks."; 1628 } 1629 } 1630 case trib-slot { 1631 leaf ts { 1632 when "../../../otn-label-range/range-type = 1633 'trib-slot'" { 1634 description 1635 "Valid only when range-type represented by 1636 trib-slot"; 1637 } 1638 type otn-ts; 1639 description 1640 "Label step which represents possible increments for 1641 Tributary Slot (TS) number."; 1642 reference 1643 "RFC7139: GMPLS Signaling Extensions for Control of 1644 Evolving G.709 Optical Transport Networks."; 1645 } 1646 } 1647 } 1648 } 1649 } 1650 } 1651 1653 6. Security Considerations 1655 The YANG module specified in this document defines a schema for data 1656 that is designed to be accessed via network management protocols such 1657 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 1658 is the secure transport layer, and the mandatory-to-implement secure 1659 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 1660 is HTTPS, and the mandatory-to-implement secure transport is TLS 1661 [RFC8446]. 1663 The NETCONF access control model [RFC8341] provides the means to 1664 restrict access for particular NETCONF or RESTCONF users to a 1665 preconfigured subset of all available NETCONF or RESTCONF protocol 1666 operations and content. 1668 The YANG module in this document defines layer 1 type definitions 1669 (i.e., typedef, identity and grouping statements) in YANG data 1670 modeling language to be imported and used by other layer 1 1671 technology-specific modules. When imported and used, the resultant 1672 schema will have data nodes that can be writable, or readable. The 1673 access to such data nodes may be considered sensitive or vulnerable 1674 in some network environments. Write operations (e.g., edit-config) 1675 to these data nodes without proper protection can have a negative 1676 effect on network operations. 1678 The security considerations spelled out in the YANG 1.1 specification 1679 [RFC7950] apply for this document as well. 1681 7. IANA Considerations 1683 It is proposed that IANA should assign new URIs from the "IETF XML 1684 Registry" [RFC3688] as follows: 1686 URI: urn:ietf:params:xml:ns:yang:ietf-layer1-types 1687 Registrant Contact: The IESG 1688 XML: N/A; the requested URI is an XML namespace. 1690 This document registers following YANG modules in the YANG Module 1691 Names registry [RFC7950]. 1693 name: ietf-layer1-types 1694 namespace: urn:ietf:params:xml:ns:yang:ietf-layer1-types 1695 prefix: l1-types 1696 reference: RFC XXXX 1698 RFC Editor Note: Please replace XXXX with the number assigned to the 1699 RFC once this draft becomes an RFC. 1701 8. Acknowledgements 1703 The authors and the working group give their sincere thanks for 1704 Robert Wilton for the YANG doctor review, and Tom Petch for his 1705 comments during the model and document development. 1707 9. Contributors 1709 Dieter Beller Nokia Email: dieter.beller@nokia.com 1711 Sergio Belotti Nokia Email: sergio.belotti@nokia.com 1713 Yanlei Zheng China Unicom Email: zhengyanlei@chinaunicom.cn 1715 Aihua Guo Futurewei Technologies Email: aihuaguo@futurewei.com 1717 Young Lee Samsung Email: younglee.tx@gmail.com 1719 Lei Wang China Mobile Email: wangleiyj@chinamobile.com 1721 Oscar Gonzalez de Dios Telefonica Email: 1722 oscar.gonzalezdedios@telefonica.com 1724 Xufeng Liu Volta Networks Email: xufeng.liu.ietf@gmail.com 1726 Yunbin Xu CAICT Email: xuyunbin@caict.ac.cn 1728 Anurag Sharma Google Email: ansha@google.com 1730 Rajan Rao Infinera Email: rrao@infinera.com 1732 Victor Lopez Telefonica Email: victor.lopezalvarez@telefonica.com 1734 Yunbo Li China Mobile Email: liyunbo@chinamobile.com 1736 10. References 1738 10.1. Normative References 1740 [ANSI] American National Standards Institute, "Synchronous 1741 Optical Network (SONET) Basic Description including 1742 Multiplex Structure, Rates, and Formats", ANSI T1.105, 1743 January 1995. 1745 [IEEE] Institute of Electrical and Electronics Engineers, "IEEE 1746 Standard for Ethernet", IEEE 802.3-2018, June 2018. 1748 [ITU-Tg7044] 1749 International Telecommunication Union, "Hitless adjustment 1750 of ODUflex(GFP)", ITU-T G.7044, October 2011. 1752 [ITU-Tg709] 1753 International Telecommunication Union, "Interfaces for the 1754 optical transport network", ITU-T G.709, June 2020. 1756 [ITU-Tgsup43] 1757 International Telecommunication Union, "Transport of IEEE 1758 10GBASE-R in optical transport networks (OTN)", 1759 ITU-T G.sup43, November 2011. 1761 [MEF63] Metro Ethernet Forum, "Subscriber Layer1 Service 1762 Attributes Technical Specification", MEF 63, August 2018. 1764 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1765 DOI 10.17487/RFC3688, January 2004, 1766 . 1768 [RFC4203] Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions in 1769 Support of Generalized Multi-Protocol Label Switching 1770 (GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005, 1771 . 1773 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 1774 and A. Bierman, Ed., "Network Configuration Protocol 1775 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 1776 . 1778 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 1779 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 1780 . 1782 [RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, D., 1783 and K. Pithewan, "GMPLS Signaling Extensions for Control 1784 of Evolving G.709 Optical Transport Networks", RFC 7139, 1785 DOI 10.17487/RFC7139, March 2014, 1786 . 1788 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 1789 RFC 7950, DOI 10.17487/RFC7950, August 2016, 1790 . 1792 [RFC7963] Ali, Z., Bonfanti, A., Hartley, M., and F. Zhang, "RSVP-TE 1793 Extension for Additional Signal Types in G.709 Optical 1794 Transport Networks (OTNs)", RFC 7963, 1795 DOI 10.17487/RFC7963, August 2016, 1796 . 1798 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 1799 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 1800 . 1802 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 1803 Access Control Model", STD 91, RFC 8341, 1804 DOI 10.17487/RFC8341, March 2018, 1805 . 1807 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 1808 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 1809 . 1811 [RFC8776] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, 1812 "Common YANG Data Types for Traffic Engineering", 1813 RFC 8776, DOI 10.17487/RFC8776, June 2020, 1814 . 1816 10.2. Informative References 1818 [I-D.ietf-ccamp-client-signal-yang] 1819 Zheng, H., Guo, A., Busi, I., Snitser, A., and F. Lazzeri, 1820 "A YANG Data Model for Transport Network Client Signals", 1821 Work in Progress, Internet-Draft, draft-ietf-ccamp-client- 1822 signal-yang-06, 5 January 2022, 1823 . 1826 [I-D.ietf-ccamp-l1csm-yang] 1827 Lee, Y., Lee, K., Zheng, H., Dios, O. G. D., and D. 1828 Ceccarelli, "A YANG Data Model for L1 Connectivity Service 1829 Model (L1CSM)", Work in Progress, Internet-Draft, draft- 1830 ietf-ccamp-l1csm-yang-16, 13 December 2021, 1831 . 1834 [I-D.ietf-ccamp-otn-topo-yang] 1835 Zheng, H., Busi, I., Liu, X., Belotti, S., and O. G. D. 1836 Dios, "A YANG Data Model for Optical Transport Network 1837 Topology", Work in Progress, Internet-Draft, draft-ietf- 1838 ccamp-otn-topo-yang-14, 7 March 2022, 1839 . 1842 [I-D.ietf-ccamp-otn-tunnel-model] 1843 Zheng, H., Busi, I., Belotti, S., Lopez, V., and Y. Xu, 1844 "OTN Tunnel YANG Model", Work in Progress, Internet-Draft, 1845 draft-ietf-ccamp-otn-tunnel-model-15, 7 March 2022, 1846 . 1849 [I-D.ietf-ccamp-transport-nbi-app-statement] 1850 Busi, I., King, D., Zheng, H., and Y. Xu, "Transport 1851 Northbound Interface Applicability Statement", Work in 1852 Progress, Internet-Draft, draft-ietf-ccamp-transport-nbi- 1853 app-statement-14, 25 March 2022, 1854 . 1857 [RFC7062] Zhang, F., Ed., Li, D., Li, H., Belotti, S., and D. 1858 Ceccarelli, "Framework for GMPLS and PCE Control of G.709 1859 Optical Transport Networks", RFC 7062, 1860 DOI 10.17487/RFC7062, November 2013, 1861 . 1863 [RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and 1864 J. Drake, "Traffic Engineering Extensions to OSPF for 1865 GMPLS Control of Evolving G.709 Optical Transport 1866 Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014, 1867 . 1869 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 1870 and R. Wilton, "Network Management Datastore Architecture 1871 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 1872 . 1874 [RFC8792] Watsen, K., Auerswald, E., Farrel, A., and Q. Wu, 1875 "Handling Long Lines in Content of Internet-Drafts and 1876 RFCs", RFC 8792, DOI 10.17487/RFC8792, June 2020, 1877 . 1879 Appendix A. Examples of OTN Label Ranges 1881 This appendix provides some examples of how the TPN and TS label 1882 ranges described in Table 3 and Table 4 of [RFC7139] can be 1883 represented in YANG using the groupings defined in this document. 1885 It also considers the OTUk links in addition to HO-ODUk links. 1887 The JSON code examples provided in this appendix provides some 1888 embedded comments following the conventions in section 3.2 of 1889 [I-D.ietf-ccamp-transport-nbi-app-statement] and have been folded 1890 using the tool in [RFC8792]. 1892 =============== NOTE: '\\' line wrapping per RFC 8792 =============== 1894 { 1895 "// examples of label-restrictions for different OTN Links": [ 1896 { 1897 "// example": "HO-ODU1 or OTU1 Link", 1898 "label-restrictions": { 1899 "label-restriction": [ 1900 { 1901 "index ": 1, 1902 "// default restriction": "inclusive", 1903 "otn-label-range": { 1904 "range-type": "label-range-trib-port", 1905 "// not-present tsg": "", 1906 "odu-type-list": "[ ODU1 ]", 1907 "// default priority": 7 1908 }, 1909 "// tpn-range": 1, 1910 "// comment": "Since no TS range and no TSG are reported\ 1911 \ for ODU1, the link is an OTU1 Link. TS allocation is not needed an\ 1912 \d TPN shall be set to '1' for mapping ODU1 over OTU1. This entry is\ 1913 \ not present if the OTN Link is an HO-ODU1 Link." 1914 }, 1915 { 1916 "index ": 2, 1917 "// default restriction": "inclusive", 1918 "otn-label-range": { 1919 "range-type": "label-range-trib-slot", 1920 "tsg": "tsg-1.25G", 1921 "odu-type-list": "[ ODU0 ]", 1922 "// default priority": 7 1923 }, 1924 "// ts-range": "1-2", 1925 "// comment": "Since no TPN range is reportd for ODU0 wi\ 1926 \th 1.25G TSG, the TPN allocation rule is fixed (TPN = TS#) for mapp\ 1927 \ing LO-ODU0 over HO-ODU1 with 1.25G TSG. See Table 4 of [RFC7139]." 1928 } 1929 ] 1930 } 1931 }, 1932 { 1933 "// example": "HO-ODU2 or OTU2 Link", 1934 "label-restrictions": { 1935 "label-restriction": [ 1936 { 1937 "index ": 1, 1938 "// default restriction": "inclusive", 1939 "otn-label-range": { 1940 "range-type": "label-range-trib-port", 1941 "//not-present tsg": "", 1942 "odu-type-list": "[ ODU2 ]", 1943 "// default priority": 7 1944 }, 1945 "// tpn-range": 1, 1946 "// comment": "Since no TS range and no TSG are reported\ 1947 \ for ODU2, the link is an OTU2 Link. TS allocation is not needed an\ 1948 \d TPN shall be set to '1' for mapping ODU2 over OTU2. This entry is\ 1949 \ not present if the OTN Link is an HO-ODU2 Link." 1950 }, 1951 { 1952 "index ": 2, 1953 "// default restriction": "inclusive", 1954 "otn-label-range": { 1955 "range-type": "label-range-trib-slot", 1956 "tsg": "tsg-1.25G", 1957 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, OD\ 1958 \U1 ]", 1959 "// default priority": 7 1960 }, 1961 "// ts-range": "1-8" 1962 }, 1963 { 1964 "index ": 3, 1965 "// default restriction": "inclusive", 1966 "otn-label-range": { 1967 "range-type": "label-range-trib-port", 1968 "tsg": "tsg-1.25G ", 1969 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0 ]", 1970 "// default priority": 7 1971 }, 1972 "// tpn-range": "1-8", 1973 "// comment": "Since this TPN range is reported for ODUf\ 1974 \lex and ODU0 with 1.25G TSG, the TPN assignment rule is flexible wi\ 1975 \thin a common range for mapping LO-ODUflex and LO-ODU0 over HO-ODU2\ 1976 \ with 1.25G TSG. See Table 4 of [RFC7139]." 1977 }, 1978 { 1979 "index ": 4, 1980 "// default restriction": "inclusive", 1981 "otn-label-range": { 1982 "range-type": "label-range-trib-port", 1983 "tsg": "tsg-1.25G", 1984 "odu-type-list": "[ ODU1 ]", 1985 "// default priority": 7 1986 }, 1987 "// tpn-range": "1-4", 1988 "// comment": "Since this TPN range is reported for ODU1\ 1989 \ with 1.25G TSG, the TPN assignment rule is flexible within a commo\ 1990 \n range for mapping LO-ODU1 over HO-ODU2 with 1.25G TSG. See Table \ 1991 \4 of [RFC7139]." 1992 }, 1993 { 1994 "index ": 5, 1995 "// default restriction": "inclusive", 1996 "otn-label-range": { 1997 "range-type": "label-range-trib-slot", 1998 "tsg": "tsg-2.5G", 1999 "odu-type-list": "[ ODU1 ]", 2000 "// default priority": 7 2001 }, 2002 "// ts-range": "1-4", 2003 "// comment": "Since no TPN range is reported for ODU1 w\ 2004 \ith 2.5G TSG, the TPN allocation rule is fixed (TPN = TS#) for mapp\ 2005 \ing LO-ODU1 over HO-ODU2 with 2.5G TSG. See Table 3 of [RFC7139]." 2006 } 2007 ] 2008 } 2009 }, 2010 { 2011 "// example": "HO-ODU3 or OTU3 Link", 2012 "label-restrictions": { 2013 "label-restriction": [ 2014 { 2015 "index ": 1, 2016 "// default restriction": "inclusive", 2017 "otn-label-range": { 2018 "range-type": "label-range-trib-port", 2019 "//not-present tsg": "", 2020 "odu-type-list": "[ ODU3 ]", 2021 "// default priority": 7 2022 }, 2023 "// tpn-range": 1, 2024 "// comment": "Since no TS range and no TSG are reported\ 2025 \ for ODU3, the link is an OTU3 Link. TS allocation is not needed an\ 2026 \d TPN shall be set to '1' for mapping ODU3 over OTU3. This entry is\ 2027 \ not present if the OTN Link is an HO-ODU3 Link." 2028 }, 2029 { 2030 "index ": 2, 2031 "// default restriction": "inclusive", 2032 "otn-label-range": { 2033 "range-type": "label-range-trib-slot", 2034 "tsg": "tsg-1.25G", 2035 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, OD\ 2036 \U1, ODU2, ODU2e ]", 2037 "// default priority": 7 2038 }, 2039 "// ts-range": "1-32" 2040 }, 2041 { 2042 "index ": 3, 2043 "// default restriction": "inclusive", 2044 "otn-label-range": { 2045 "range-type": "label-range-trib-port", 2046 "tsg": "tsg-1.25G", 2047 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, OD\ 2048 \U2e ]", 2049 "// default priority": 7 2050 }, 2051 "// tpn-range": "1-32", 2052 "// comment": "Since this TPN range is reported for ODUf\ 2053 \lex, ODU0 and ODU2e with 1.25G TSG, the TPN assignment rule is flex\ 2054 \ible within a common range for mapping LO-ODUflex, LO-ODU0 and LO-O\ 2055 \DU2e over HO-ODU3 with 1.25G TSG. See Table 4 of [RFC7139]." 2056 }, 2057 { 2058 "index ": 4, 2059 "// default restriction": "inclusive", 2060 "otn-label-range": { 2061 "range-type": "label-range-trib-port", 2062 "tsg": "tsg-1.25G", 2063 "odu-type-list": "[ ODU1 ]", 2064 "// default priority": 7 2065 }, 2066 "// tpn-range": "1-16", 2067 "// comment": "Since this TPN range is reported for ODU1\ 2068 \ with 1.25G TSG, the TPN assignment rule is flexible within a commo\ 2069 \n range for mapping LO-ODU1 over HO-ODU3 with 1.25G TSG. See Table \ 2070 \4 of [RFC7139]." 2071 }, 2072 { 2073 "index ": 5, 2074 "// default restriction": "inclusive", 2075 "otn-label-range": { 2076 "range-type": "label-range-trib-port", 2077 "tsg": "tsg-1.25G", 2078 "odu-type-list": "[ ODU2 ]", 2079 "// default priority": 7 2080 }, 2081 "// tpn-range": "1-4", 2082 "// comment": "Since this TPN range is reported for ODU2\ 2083 \ with 1.25G TSG, the TPN assignment rule is flexible within a commo\ 2084 \n range for mapping LO-ODU2 over HO-ODU3 with 1.25G TSG. See Table \ 2085 \4 of [RFC7139]." 2086 }, 2087 { 2088 "index ": 6, 2089 "// default restriction": "inclusive", 2090 "otn-label-range": { 2091 "range-type": "label-range-trib-slot", 2092 "tsg": "tsg-2.5G", 2093 "odu-type-list": "[ ODU1, ODU2 ]", 2094 "// default priority": 7 2095 }, 2096 "// ts-range": "1-16" 2097 }, 2098 { 2099 "index ": 7, 2100 "// default restriction": "inclusive", 2101 "otn-label-range": { 2102 "range-type": "label-range-trib-port", 2103 "tsg": "tsg-2.5G ", 2104 "odu-type-list": "[ ODU2 ]", 2105 "// default priority": 7 2106 }, 2107 "// tpn-range": "1-4", 2108 "// comment": "Since this TPN range is reported for ODU2\ 2109 \ with 2.5G TSG, the TPN assignment rule is flexible within a common\ 2110 \ range for mapping LO-ODU2 over HO-ODU3. Since no TPN range is repo\ 2111 \rted for ODU1 with 2.5G TSG, the TPN allocation rule is fixed (TPN \ 2112 \= TS#) for mapping LO-ODU1 over HO-ODU3 with 2.5G TSG. See Table 3 \ 2113 \of [RFC7139]." 2114 } 2115 ] 2116 } 2117 }, 2118 { 2119 "// example": "HO-ODU4 or OTU4 Link", 2120 "label-restrictions": { 2121 "label-restriction": [ 2122 { 2123 "index ": 1, 2124 "// default restriction": "inclusive", 2125 "otn-label-range": { 2126 "range-type": "label-range-trib-port", 2127 "//not-present tsg": "", 2128 "odu-type-list": "[ ODU4 ]", 2129 "// default priority": 7 2130 }, 2131 "// tpn-range": 1, 2132 "// comment": "Since no TS range and no TSG are reported\ 2133 \ for ODU4, the link is an OTU4 Link. TS allocation is not needed an\ 2134 \d TPN shall be set to '1' for mapping ODU4 over OTU4. This entry is\ 2135 \ not present if the OTN Link is an HO-ODU4 Link." 2136 }, 2137 { 2138 "index ": 2, 2139 "// default restriction": "inclusive", 2140 "otn-label-range": { 2141 "range-type": "label-range-trib-slot", 2142 "tsg": "tsg-1.25G", 2143 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, OD\ 2144 \U1, ODU2, ODU2e, ODU3 ]", 2145 "// default priority": 7 2146 }, 2147 "// ts-range": "1-80" 2148 }, 2149 { 2150 "index ": 3, 2151 "// default restriction": "inclusive", 2152 "otn-label-range": { 2153 "range-type": "label-range-trib-port", 2154 "tsg": "tsg-1.25G", 2155 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, OD\ 2156 \U1, ODU2, ODU2e, ODU3 ]", 2157 "// default priority": 7 2158 }, 2159 "// tpn-range": "1-80", 2160 "// comment": "Since this TPN range is reported for any \ 2161 \LO-ODUj with 1.25G TSG, the TPN assignment rule is flexible within \ 2162 \a common range for mapping any LO-ODUj over HO-ODU4 with 1.25G TSG.\ 2163 \ See Table 4 of [RFC7139]." 2164 } 2165 ] 2166 } 2168 }, 2169 { 2170 "// example": "ODUC1 Link", 2171 "label-restrictions": { 2172 "label-restriction": [ 2173 { 2174 "index ": 1, 2175 "// default restriction": "inclusive", 2176 "otn-label-range": { 2177 "range-type": "label-range-trib-slot", 2178 "tsg": "tsg-5G", 2179 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, OD\ 2180 \U1, ODU2, ODU2e, ODU3, ODU4 ]", 2181 "// default priority": 7 2182 }, 2183 "// ts-range": "1-20", 2184 "// comment": "Since the TS range is specified for any O\ 2185 \DUk, the OTN Link is an ODUCn Link." 2186 }, 2187 { 2188 "index ": 2, 2189 "// default restriction": "inclusive", 2190 "otn-label-range": { 2191 "range-type": "label-range-trib-port", 2192 "tsg": "tsg-5G", 2193 "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, OD\ 2194 \U1, ODU2, ODU2e, ODU3, ODU4 ]", 2195 "// default priority": 7 2196 }, 2197 "// tpn-range": "1-10", 2198 "// comment": "Since this TPN range is reported for any \ 2199 \ODUk with 5G TSG, the TPN assignment rule is flexible within a comm\ 2200 \on range for mapping any ODUk over ODUCn with 5G TSG." 2201 } 2202 ] 2203 } 2204 } 2205 ] 2206 } 2208 Authors' Addresses 2210 Haomian Zheng 2211 Huawei Technologies 2212 H1, Huawei Xiliu Beipo Village, Songshan Lake 2213 Dongguan 2214 Guangdong, 523808 2215 China 2216 Email: zhenghaomian@huawei.com 2218 Italo Busi 2219 Huawei Technologies 2220 Milan 2221 Italy 2222 Email: Italo.Busi@huawei.com