idnits 2.17.1 draft-ietf-ccamp-layer1-types-03.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 : ---------------------------------------------------------------------------- ** There are 9 instances of too long lines in the document, the longest one being 9 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (November 1, 2019) is 1637 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-13) exists of draft-ietf-teas-yang-te-types-11 -- Possible downref: Non-RFC (?) normative reference: ref. 'MEF63' == Outdated reference: A later version (-26) exists of draft-ietf-ccamp-l1csm-yang-10 == Outdated reference: A later version (-18) exists of draft-ietf-ccamp-otn-topo-yang-08 == Outdated reference: A later version (-20) exists of draft-ietf-ccamp-otn-tunnel-model-08 Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CCAMP Working Group H. Zheng 3 Internet-Draft I. Busi 4 Intended status: Standards Track Huawei Technologies 5 Expires: May 4, 2020 November 1, 2019 7 A YANG Data Model for Layer 1 Types 8 draft-ietf-ccamp-layer1-types-03 10 Abstract 12 This document defines a collection of common data types and groupings 13 in YANG data modeling language for layer 1 networks. These derived 14 common types and groupings are intended to be imported by modules 15 that specifies the OTN networks, including the topology, tunnel, 16 client signal adaptation and service. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on May 4, 2020. 35 Copyright Notice 37 Copyright (c) 2019 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 . . . . . . . . . . . . . . . . . . 2 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. Usage of groupings in Layer1-types . . . . . . . . . . . 5 59 5. YANG Code for Layer1 Types . . . . . . . . . . . . . . . . . 6 60 6. Security Considerations . . . . . . . . . . . . . . . . . . . 20 61 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 62 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 63 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 21 64 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 65 10.1. Normative References . . . . . . . . . . . . . . . . . . 22 66 10.2. Informative References . . . . . . . . . . . . . . . . . 23 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 69 1. Introduction 71 This document introduces a collection of common data types which 72 would be used in Layer 1 networks. The derived types and groupings 73 are designed to be the common types applicable for modeling Traffic 74 Engineering (TE) features for Layer 1 optical networks. 76 Typical L1 network, the Optical Transport Networking, was specified 77 in [RFC7062]. Corresponding routing and signaling protocol have been 78 specified in [RFC7138] and [RFC7139]. The types and groupings 79 defined in this document is consistent to these document, and will be 80 imported in other Layer 1 data models, including but not restrictive 81 to, [I-D.ietf-ccamp-otn-topo-yang], [I-D.ietf-ccamp-otn-tunnel-model] 82 and [I-D.ietf-ccamp-l1csm-yang]. 84 The data model in this draft has only types defined including 85 groupings, typedef and identities. There is no need to include 86 configuration and state data according to the new Network Management 87 Datastore Architecture [RFC8342]. The content in this draft is in 88 consistent with [MEF63]. 90 2. Terminology and Notations 92 Refer to [RFC7062] for the key terms used in this document, and the 93 terminology for describing YANG data models can be found in 94 [RFC7950]. 96 3. Prefix in Data Node Names 98 In this document, names of data nodes and other data model objects 99 are prefixed using the standard prefix associated with the 100 corresponding YANG imported modules. 102 +-------------+---------------------------+----------------------+ 103 | Prefix | YANG module | Reference | 104 +-------------+---------------------------+----------------------+ 105 | layer1-types| ietf-layer1-types | This Document | 106 +-------------+---------------------------+----------------------+ 108 4. Layer 1 Types Overview 110 4.1. Relationship with other Modules 112 This document defines one YANG module for common Layer 1 types. The 113 objective is to specifies common Layer 1 TE types that can be 114 imported by layer 1 specific technology, for example OTN, in its 115 technology-specific modules such as topology and tunnels. It is 116 worth noting that the generic traffic-engineering (TE) types module 117 is specified in [I-D.ietf-teas-yang-te-types] as ietf-te-types, and 118 both the module ietf-te-types and ietf-layer1-types are needed to be 119 imported when the OTN is configured. 121 4.2. Content in Layer 1 Type Module 123 The module ietf-layer1-types contains the following YANG reusable 124 types and groupings: 126 tributary-slot-granularity: 128 This is to define the granularity of the server layer ODU Link (HO 129 ODUk or ODUCn) supporting a client layer ODU LSP (LO ODUj or ODUk, 130 respectively). Three granularities, 1.25G/2.5G/5G, have been 131 specified. 133 odu-type: 135 This is to specify the type of ODUk LSP. 137 client-signal: 139 This is to specify the client signal types of OTN networks. The 140 initial input was the G-PID specified in [RFC7139]. Identities about 141 a few categories of client signal types, including ETH, STM-n, OC and 142 Fiber Channel have been specified. 144 otn-label-range-type: 146 The label range type of OTN has two different representations, 147 tributary slots (TS) and tributary port number (TPN), according to 148 [RFC7139]. Respective representation is specified under this same 149 base type. 151 otn-link-bandwidth: 153 This grouping defines the link bandwidth information and could be 154 used in OTN topology model for bandwidth representation. All the 155 bandwidth related sections in generic topology module, ietf-te- 156 topology, need to be augmented with this grouping for the usage of 157 Layer 1. 159 otn-path-bandwidth: 161 This grouping defines the path bandwidth information and could be 162 used in OTN topology model for bandwidth representation. All the 163 bandwidth related sections in generic topology module, ietf-te- 164 topology, need to be augmented with this grouping for the usage of 165 Layer 1. This grouping is also applicable to set up the OTN tunnel. 167 otn-label-restriction and otn-label-step: 169 These groupings are used for the augmentation of OTN label in a 170 specific way. 172 otn-label-start-end and otn-label-hop: 174 These groupings are used for the augmentation of label for OTN link 175 and path respectively. 177 optical-interface-func: 179 The optical interface function is specified in [MEF63]. This 180 grouping describes the functionality which encodes bits for 181 transmission and the corresponding decode upon reception. 183 service-performance-metric: 185 The service performance metric is a quantitative characterization of 186 Layer 1 characteristic information delivery quality experienced by 187 the Layer 1 subscriber. 189 4.3. Usage of groupings in Layer1-types 191 As described in [RFC7139], the OTN label usually represents the 192 Tributary Port Number (TPN) and the related set of Tributary Slots 193 (TS) assigned to a client layer ODU LSP (LO ODUj or ODUk) on a given 194 server layer ODU (HO-ODU or ODUCn, respectively) Link (e.g., ODU2 LSP 195 over ODU3 Link). Some special OTN label values are also defined for 196 an ODUk LSP being setup over an OTUk Link. 198 The same OTN label shall be assigned to the same ODUk LSP at the two 199 ends of an OTN Link. 201 As described in [RFC7139], TPN can be a number from 1 to 4095 and TS 202 are numbered from 1 to 4095, although the actual maximum values 203 depend on the type of server layer ODU. For example, a server layer 204 ODU4 provides 80 time slots (numbered from 1 to 80) and the TPN 205 values can be any number from 1 to 80. 207 The OTN Label Range represents the values for the TPN and TS that are 208 available for ODUk LSPs to be setup over a given OTN Link. 210 The OTN Label Range is defined by the label-restriction list, defined 211 in [I-D.ietf-teas-yang-te-types], which, for OTN, should be augmented 212 using the otn-label-restriction grouping. 214 Each entry in the label-restriction list represents either the range 215 of the available TPN values or the range of the available TS values: 216 the range-type attribute defines the type of range for each entry of 217 the list. 219 Each entry of the label-restriction list, as defined in 220 [I-D.ietf-teas-yang-te-types], defines a label-start, a label-end, a 221 label-step and a range-bitmap. The label-start and label-end 222 definitions for OTN should be augmented using the otn-link-label 223 grouping. The label-step definition for OTN should be augmented 224 using the otn-label-step grouping. It is expected that the otn- 225 label-step will always be equal to its default value (i.e., 1). 227 As described in [RFC7139], in some cases, the TPN assignment rules is 228 flexible (e.g., ODU4 Link) while in other cases the TPN assignment 229 rules are fixed (e.g., ODU1 Link). In the latter case, only the TS 230 range is reported: not reporting the TPN range means that the TPN 231 shall be set equal to the TS number assigned to the ODUk LSP. 233 As described in [RFC7139], in some cases, the TPN assignment rules 234 depends on the TS Granularity (e.g., ODU2 or ODU3 Links). Different 235 entries in the label-restriction list will report different TPN 236 ranges for each TS granularity supported by the link, as indicated by 237 the tsg attribute. 239 As described in [RFC7139], in some cases, the TPN ranges are 240 different for different types of ODUk LSPs. For example, on an ODU2 241 Link with 1,25G TS granularity, there is TPN range 1-4 for ODU1 and 242 another TPN range 1-8 in common for ODU0 and ODUflex. Different 243 entries in the label-restriction list will report different TPN 244 ranges for different set of ODUk types, as indicated by the odu-type- 245 list . 247 5. YANG Code for Layer1 Types 249 file "ietf-layer1-types@2019-11-01.yang" 250 module ietf-layer1-types { 251 namespace "urn:ietf:params:xml:ns:yang:ietf-layer1-types"; 252 prefix "layer1-types"; 254 organization 255 "IETF CCAMP Working Group"; 256 contact 257 "WG Web: 258 WG List: 260 Editor: Haomian Zheng 261 263 Editor: Italo Busi 264 "; 266 description 267 "This module defines Layer 1 types. The model fully conforms 268 to the Network Management Datastore Architecture (NMDA). 270 Copyright (c) 2018 IETF Trust and the persons 271 identified as authors of the code. All rights reserved. 273 Redistribution and use in source and binary forms, with or 274 without modification, is permitted pursuant to, and subject 275 to the license terms contained in, the Simplified BSD License 276 set forth in Section 4.c of the IETF Trust's Legal Provisions 277 Relating to IETF Documents 278 (https://trustee.ietf.org/license-info). 279 This version of this YANG module is part of RFC XXXX; see 280 the RFC itself for full legal notices."; 282 revision "2019-11-01" { 283 description 284 "Initial Version"; 285 reference 286 "RFC XXXX: A YANG Data Model for Layer 1 Types"; 287 // RFC Ed.: replace XXXX with actual RFC number, update date 288 // information and remove this note 289 } 291 identity tributary-slot-granularity { 292 description 293 "Tributary slot granularity"; 294 reference 295 "G.709/Y.1331, February 2016: Interfaces for the Optical 296 Transport Network (OTN)"; 297 } 299 identity tsg-1.25G { 300 base tributary-slot-granularity; 301 description 302 "1.25G tributary slot granularity"; 303 } 305 identity tsg-2.5G { 306 base tributary-slot-granularity; 307 description 308 "2.5G tributary slot granularity"; 309 } 311 identity tsg-5G { 312 base tributary-slot-granularity; 313 description 314 "5G tributary slot granularity"; 315 } 317 identity odu-type { 318 description 319 "Base identity for protocol framing used by tributary signals."; 320 } 322 identity ODU0 { 323 base odu-type; 324 description 325 "ODU0 protocol (1.24G), RFC7139/ITU-T G.709, as standard track."; 326 } 328 identity ODU1 { 329 base odu-type; 330 description 331 "ODU1 protocol (2.49G), RFC7139/ITU-T G.709, as standard track."; 332 } 334 identity ODU1e { 335 base odu-type; 336 description 337 "ODU1e protocol (10.35G), RFC7963/ITU-T G.sup43, as informational."; 338 } 340 identity ODU2 { 341 base odu-type; 342 description 343 "ODU2 protocol (10.03G), RFC7139/ITU-T G.709, as standard track."; 344 } 346 identity ODU2e { 347 base odu-type; 348 description 349 "ODU2e protocol (10.39G), RFC7139/ITU-T G.709, as standard track."; 350 } 352 identity ODU3 { 353 base odu-type; 354 description 355 "ODU3 protocol (40.31G), RFC7139/ITU-T G.709, as standard track."; 356 } 358 identity ODU3e1 { 359 base odu-type; 360 description 361 "ODU3e1 protocol (41.77G), RFC7963/ITU-T G.sup43, as informational."; 362 } 364 identity ODU3e2 { 365 base odu-type; 366 description 367 "ODU3e2 protocol (41.78G), RFC7963/ITU-T G.sup43, as informational."; 368 } 370 identity ODU4 { 371 base odu-type; 372 description 373 "ODU4 protocol (104.79G), RFC7139/ITU-T G.709, as standard track."; 374 } 376 identity ODUFlex-cbr { 377 base odu-type; 378 description 379 "ODU Flex CBR protocol for transporting constant bit rate 380 signal"; 381 } 383 identity ODUFlex-gfp { 384 base odu-type; 385 description 386 "ODU Flex GFP protocol for transporting stream of packets 387 using Generic Framing Procedure"; 388 } 390 identity client-signal { 391 description 392 "Base identity from which specific client signals for the 393 tunnel are derived"; 394 } 396 identity ETH-1Gb { 397 base client-signal; 398 description 399 "Client signal type of 1GbE"; 400 } 402 identity ETH-10Gb-LAN { 403 base client-signal; 404 description 405 "Client signal type of 10GbE LAN"; 406 } 408 identity ETH-10Gb-WAN { 409 base client-signal; 410 description 411 "Client signal type of 10GbE WAN"; 412 } 414 identity ETH-40Gb { 415 base client-signal; 416 description 417 "Client signal type of 40GbE"; 418 } 420 identity ETH-100Gb { 421 base client-signal; 422 description 423 "Client signal type of 100GbE"; 424 } 426 identity STM-1 { 427 base client-signal; 428 description 429 "Client signal type of STM-1"; 430 } 432 identity STM-4 { 433 base client-signal; 434 description 435 "Client signal type of STM-4"; 436 } 438 identity STM-16 { 439 base client-signal; 440 description 441 "Client signal type of STM-16"; 442 } 444 identity STM-64 { 445 base client-signal; 446 description 447 "Client signal type of STM-64"; 448 } 450 identity STM-256 { 451 base client-signal; 452 description 453 "Client signal type of STM-256"; 454 } 455 identity OC-3 { 456 base client-signal; 457 description 458 "Client signal type of OC3"; 459 } 461 identity OC-12 { 462 base client-signal; 463 description 464 "Client signal type of OC12"; 465 } 467 identity OC-48 { 468 base client-signal; 469 description 470 "Client signal type of OC48"; 471 } 473 identity OC-192 { 474 base client-signal; 475 description 476 "Client signal type of OC192"; 477 } 479 identity OC-768 { 480 base client-signal; 481 description 482 "Client signal type of OC768"; 483 } 485 identity FC-100 { 486 base client-signal; 487 description 488 "Client signal type of Fibre Channel FC-100"; 489 } 491 identity FC-200 { 492 base client-signal; 493 description 494 "Client signal type of Fibre Channel FC-200"; 495 } 497 identity FC-400 { 498 base client-signal; 499 description 500 "Client signal type of Fibre Channel FC-400"; 501 } 503 identity FC-800 { 504 base client-signal; 505 description 506 "Client signal type of Fibre Channel FC-800"; 507 } 509 identity FC-1200 { 510 base client-signal; 511 description 512 "Client signal type of Fibre Channel FC-1200"; 513 } 515 identity FC-1600 { 516 base client-signal; 517 description 518 "Client signal type of Fibre Channel FC-1600"; 519 } 521 identity FC-3200 { 522 base client-signal; 523 description 524 "Client signal type of Fibre Channel FC-3200"; 525 } 527 identity FICON-4G { 528 base client-signal; 529 description 530 "Client signal type of Fibre Connection 4G"; 531 } 533 identity FICON-8G { 534 base client-signal; 535 description 536 "Client signal type of Fibre Connection 8G"; 537 } 539 identity otn-label-range-type { 540 description 541 "Base identity from which specific OTN label 542 range types derived"; 543 } 545 identity label-range-trib-slot { 546 base otn-label-range-type; 547 description 548 "Defines a range of OTN tributary slots"; 549 } 551 identity label-range-trib-port { 552 base otn-label-range-type; 553 description 554 "Defines a range of OTN tributary ports"; 555 } 557 grouping otn-link-bandwidth { 558 description "link bandwidth attributes for OTN"; 559 list odulist { 560 key "odu-type"; 561 description 562 "OTN bandwidth definition"; 563 leaf odu-type { 564 type identityref { 565 base layer1-types:odu-type; 566 } 567 description "ODU type"; 568 } 569 leaf number { 570 type uint16; 571 description "Number of ODUs"; 572 } 573 } 574 } 576 grouping otn-path-bandwidth { 577 description 578 "path bandwidth attributes for OTN"; 579 leaf odu-type { 580 type identityref { 581 base layer1-types:odu-type; 582 } 583 description "ODU type"; 584 } 585 } 587 grouping otn-label-range-info { 588 description "label range information for OTN"; 589 leaf range-type { 590 type identityref { 591 base layer1-types:otn-label-range-type; 592 } 593 description "type for range"; 594 } 595 leaf tsg { 596 type identityref { 597 base layer1-types:tributary-slot-granularity; 598 } 599 description 600 "Tributary slot granularity."; 601 reference 602 "G.709/Y.1331, February 2016: Interfaces for the 603 Optical Transport Network (OTN)"; 604 } 605 leaf-list odu-type-list { 606 type identityref { 607 base odu-type; 608 } 609 description 610 "List of ODU types to which the label range applies. 611 Empty odu-type-list means all the ODU types are applicable 612 per label range. "; 613 } 614 leaf priority { 615 type uint8; 616 description "priority."; 617 } 618 } 619 grouping otn-label-start-end { 620 description 621 "The OTN label-start or label-end used to specify an OTN label range."; 622 choice otn-label-type { 623 description 624 "OTN label range type, either TPN range or TS range"; 625 case tributary-port { 626 leaf tpn { 627 type uint16 { 628 range "1..4095"; 629 } 630 description 631 "Tributary Port Number. Applicable in case of mux services."; 632 reference 633 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 634 G.709 Optical Transport Networks."; 635 } 636 } 637 case tributary-slot { 638 leaf ts { 639 type uint16 { 640 range "1..4095"; 641 } 642 description 643 "Tributary Slot Number. Applicable in case of mux services."; 644 reference 645 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 646 G.709 Optical Transport Networks."; 647 } 648 } 649 } 650 } 652 grouping otn-label-hop { 653 description "label information for OTN, for label-hop"; 654 leaf tpn { 655 type uint16 { 656 range "1..4095"; 657 } 658 description 659 "Tributary Port Number. Applicable in case of mux services."; 660 reference 661 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 662 G.709 Optical Transport Networks."; 663 } 664 leaf tsg { 665 type identityref { 666 base layer1-types:tributary-slot-granularity; 668 } 669 description "Tributary slot granularity."; 670 reference 671 "G.709/Y.1331, February 2016: Interfaces for the 672 Optical Transport Network (OTN)"; 673 } 674 leaf ts-list { 675 type string { 676 pattern "([1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?" 677 + "(,[1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?)*)"; 678 } 679 description 680 "A list of available tributary slots ranging 681 between 1 and 4095. 682 For example 1-20,25,50-1000"; 683 reference "RFC 7139: GMPLS Signaling Extensions for Control 684 of Evolving G.709 Optical Transport Networks"; 685 } 686 } 688 grouping otn-label-step { 689 description "Label step for OTN"; 690 choice otn-label-type { 691 description 692 "OTN label range type, either TPN range or TS range"; 693 case tributary-port { 694 leaf tpn { 695 type uint16 { 696 range "1..4095"; 697 } 698 default 1; 699 description 700 "Label step which represents possible increments for 701 Tributary Port Number."; 702 reference 703 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 704 G.709 Optical Transport Networks."; 705 } 706 } 707 case tributary-slot { 708 leaf ts { 709 type uint16 { 710 range "1..4095"; 711 } 712 default 1; 713 description 714 "Label step which represents possible increments for 715 Tributary Slot Number."; 717 reference 718 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 719 G.709 Optical Transport Networks."; 720 } 721 } 722 } 723 } 725 identity coding-func { 726 description 727 "base identity from which coding func is derived."; 728 } 730 identity ETH-1000X-PCS-36 { 731 base "coding-func"; 732 description 733 "PCS clause 36 coding function that corresponds to 734 1000BASE-X"; 735 reference "MEF63 & IEEE802.3"; 736 } 738 identity ETH-10GW-PCS-49-WIS-50 { 739 base "coding-func"; 740 description 741 "PCS clause 49 and WIS clause 50 coding func that 742 corresponds to 10GBASE-W (WAN PHY)"; 743 reference "MEF63 & IEEE802.3"; 744 } 746 identity ETH-10GR-PCS-49 { 747 base "coding-func"; 748 description 749 "PCS clause 49 coding function that corresponds to 750 10GBASE-R (LAN PHY)"; 751 reference "MEF63 & IEEE802.3"; 752 } 754 identity ETH-40GR-PCS-82 { 755 base "coding-func"; 756 description 757 "PCS clause 82 coding function that corresponds to 758 40GBASE-R"; 759 reference "MEF63 & IEEE802.3"; 760 } 762 identity ETH-100GR-PCS-82 { 763 base "coding-func"; 764 description 765 "PCS clause 82 coding function that corresponds to 766 100GBASE-R"; 767 reference "MEF63 & IEEE802.3"; 768 } 770 identity optical-interface-func { 771 description 772 "base identity from which optical-interface-function is 773 derived."; 774 } 776 identity SX-PMD-clause-38 { 777 base "optical-interface-func"; 778 description 779 "SX-PMD-clause-38 Optical Interface function for 780 1000BASE-X PCS-36"; 781 reference "MEF63 & IEEE802.3"; 782 } 784 identity LX-PMD-clause-38 { 785 base "optical-interface-func"; 786 description 787 "LX-PMD-clause-38 Optical Interface function for 788 1000BASE-X PCS-36"; 789 reference "MEF63 & IEEE802.3"; 790 } 792 identity LX10-PMD-clause-59 { 793 base "optical-interface-func"; 794 description 795 "LX10-PMD-clause-59 Optical Interface function for 796 1000BASE-X PCS-36"; 797 reference "MEF63 & IEEE802.3"; 798 } 800 identity BX10-PMD-clause-59 { 801 base "optical-interface-func"; 802 description 803 "BX10-PMD-clause-59 Optical Interface function for 804 1000BASE-X PCS-36"; 805 reference "MEF63 & IEEE802.3"; 806 } 808 identity LW-PMD-clause-52 { 809 base "optical-interface-func"; 810 description 811 "LW-PMD-clause-52 Optical Interface function for 812 10GBASE-W PCS-49-WIS-50"; 814 reference "MEF63 & IEEE802.3"; 815 } 817 identity EW-PMD-clause-52 { 818 base "optical-interface-func"; 819 description 820 "EW-PMD-clause-52 Optical Interface function for 821 10GBASE-W PCS-49-WIS-50"; 822 reference "MEF63 & IEEE802.3"; 823 } 825 identity LR-PMD-clause-52 { 826 base "optical-interface-func"; 827 description 828 "LR-PMD-clause-52 Optical Interface function for 829 10GBASE-R PCS-49"; 830 reference "MEF63 & IEEE802.3"; 831 } 833 identity ER-PMD-clause-52 { 834 base "optical-interface-func"; 835 description 836 "ER-PMD-clause-52 Optical Interface function for 837 10GBASE-R PCS-49"; 838 reference "MEF63 & IEEE802.3"; 839 } 841 identity LR4-PMD-clause-87 { 842 base "optical-interface-func"; 843 description 844 "LR4-PMD-clause-87 Optical Interface function for 845 40GBASE-R PCS-82"; 846 reference "MEF63 & IEEE802.3"; 847 } 849 identity ER4-PMD-clause-87 { 850 base "optical-interface-func"; 851 description 852 "ER4-PMD-clause-87 Optical Interface function for 853 40GBASE-R PCS-82"; 854 reference "MEF63 & IEEE802.3"; 855 } 857 identity FR-PMD-clause-89 { 858 base "optical-interface-func"; 859 description 860 "FR-PMD-clause-89 Optical Interface function for 861 40GBASE-R PCS-82"; 863 reference "MEF63 & IEEE802.3"; 864 } 866 identity LR4-PMD-clause-88 { 867 base "optical-interface-func"; 868 description 869 "LR4-PMD-clause-88 Optical Interface function for 870 100GBASE-R PCS-82"; 871 reference "MEF63 & IEEE802.3"; 872 } 874 identity ER4-PMD-clause-88 { 875 base "optical-interface-func"; 876 description 877 "ER4-PMD-clause-88 Optical Interface function for 878 100GBASE-R PCS-82"; 879 reference "MEF63 & IEEE802.3"; 880 } 882 identity service-performance-metric { 883 description 884 "list of service-specific performance metric"; 885 } 887 identity One-way-Delay { 888 base "service-performance-metric"; 889 description "one-way-delay"; 890 } 892 identity One-way-Errored-Second { 893 base "service-performance-metric"; 894 description "one-way-errored-second"; 895 } 897 identity One-way-Severely-Errored-Second { 898 base "service-performance-metric"; 899 description "one-way-severely-errored-second"; 900 } 902 identity One-way-Unavailable-Second { 903 base "service-performance-metric"; 904 description "one-way-unavailable-second"; 905 } 907 identity One-way-Availability { 908 base "service-performance-metric"; 909 description "one-way-availability"; 910 } 911 identity network-performance-metric { 912 description "list of network-specific performance metric"; 913 } 915 } 916 918 6. Security Considerations 920 The YANG module specified in this document defines a schema for data 921 that is designed to be accessed via network management protocols such 922 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 923 is the secure transport layer, and the mandatory-to-implement secure 924 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 925 is HTTPS, and the mandatory-to-implement secure transport is TLS 926 [RFC8446]. 928 The NETCONF access control model [RFC8341] provides the means to 929 restrict access for particular NETCONF or RESTCONF users to a 930 preconfigured subset of all available NETCONF or RESTCONF protocol 931 operations and content. 933 The YANG module in this document defines layer 1 type definitions 934 (i.e., typedef, identity and grouping statements) in YANG data 935 modeling language to be imported and used by other layer 1 936 technology-specific modules. When imported and used, the resultant 937 schema will have data nodes that can be writable, or readable. The 938 access to such data nodes may be onsidered sensitive or vulnerable in 939 some network environments. Write operations (e.g., edit-config) to 940 these data nodes without proper protection can have a negative effect 941 on network operations. 943 The security considerations spelled out in the YANG 1.1 specification 944 [RFC7950] apply for this document as well. 946 7. IANA Considerations 948 It is proposed that IANA should assign new URIs from the "IETF XML 949 Registry" [RFC3688] as follows: 951 URI: urn:ietf:params:xml:ns:yang:ietf-layer1-types 952 Registrant Contact: The IESG 953 XML: N/A; the requested URI is an XML namespace. 955 This document registers following YANG modules in the YANG Module 956 Names registry [RFC7950]. 958 name: ietf-layer1-types 959 namespace: urn:ietf:params:xml:ns:yang:ietf-otn-types 960 prefix: layer1-types 961 reference: RFC XXXX 963 8. Acknowledgements 965 TBD. 967 9. Contributors 969 Dieter Beller 970 Nokia 971 Email: dieter.beller@nokia.com 973 Sergio Belotti 974 Nokia 975 Email: sergio.belotti@nokia.com 977 Yanlei Zheng 978 China Unicom 979 Email: zhengyl@dimpt.com 981 Aihua Guo 982 Huawei Technologies 983 Email: aihuaguo@huawei.com 985 Young Lee 986 Huawei Technologies 987 Email: leeyoung@huawei.com 989 Lei Wang 990 China Mobile 991 Email: wangleiyj@chinamobile.com 993 Oscar Gonzalez de Dios 994 Telefonica 995 Email: oscar.gonzalezdedios@telefonica.com 997 Xufeng Liu 998 Volta Networks 999 Email: xufeng.liu.ietf@gmail.com 1000 Yunbin Xu 1001 CAICT 1002 Email: xuyunbin@ritt.com 1004 Anurag Sharma 1005 Google 1006 Email: ansha@google.com 1008 Rajan Rao 1009 Infinera 1010 Email: rrao@infinera.com 1012 Victor Lopez 1013 Telefonica 1014 Email: victor.lopezalvarez@telefonica.com 1016 Yunbo Li 1017 China Mobile 1018 Email: liyunbo@chinamobile.com 1020 10. References 1022 10.1. Normative References 1024 [I-D.ietf-teas-yang-te-types] 1025 Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, 1026 "Traffic Engineering Common YANG Types", draft-ietf-teas- 1027 yang-te-types-11 (work in progress), October 2019. 1029 [MEF63] Metro Ethernet Forum, "Subscriber Layer1 Service 1030 Attributes Technical Specification", MEF 63, August 2018. 1032 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1033 DOI 10.17487/RFC3688, January 2004, 1034 . 1036 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 1037 and A. Bierman, Ed., "Network Configuration Protocol 1038 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 1039 . 1041 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 1042 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 1043 . 1045 [RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, D., 1046 and K. Pithewan, "GMPLS Signaling Extensions for Control 1047 of Evolving G.709 Optical Transport Networks", RFC 7139, 1048 DOI 10.17487/RFC7139, March 2014, 1049 . 1051 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 1052 RFC 7950, DOI 10.17487/RFC7950, August 2016, 1053 . 1055 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 1056 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 1057 . 1059 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 1060 Access Control Model", STD 91, RFC 8341, 1061 DOI 10.17487/RFC8341, March 2018, 1062 . 1064 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 1065 and R. Wilton, "Network Management Datastore Architecture 1066 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 1067 . 1069 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 1070 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 1071 . 1073 10.2. Informative References 1075 [I-D.ietf-ccamp-l1csm-yang] 1076 Lee, Y., Lee, K., Zheng, H., Dhody, D., Dios, O., and D. 1077 Ceccarelli, "A YANG Data Model for L1 Connectivity Service 1078 Model (L1CSM)", draft-ietf-ccamp-l1csm-yang-10 (work in 1079 progress), September 2019. 1081 [I-D.ietf-ccamp-otn-topo-yang] 1082 Zheng, H., Guo, A., Busi, I., Sharma, A., Liu, X., 1083 Belotti, S., Xu, Y., Wang, L., and O. Dios, "A YANG Data 1084 Model for Optical Transport Network Topology", draft-ietf- 1085 ccamp-otn-topo-yang-08 (work in progress), September 2019. 1087 [I-D.ietf-ccamp-otn-tunnel-model] 1088 Zheng, H., Busi, I., Belotti, S., Lopezalvarez, V., and Y. 1089 Xu, "OTN Tunnel YANG Model", draft-ietf-ccamp-otn-tunnel- 1090 model-08 (work in progress), October 2019. 1092 [RFC7062] Zhang, F., Ed., Li, D., Li, H., Belotti, S., and D. 1093 Ceccarelli, "Framework for GMPLS and PCE Control of G.709 1094 Optical Transport Networks", RFC 7062, 1095 DOI 10.17487/RFC7062, November 2013, 1096 . 1098 [RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and 1099 J. Drake, "Traffic Engineering Extensions to OSPF for 1100 GMPLS Control of Evolving G.709 Optical Transport 1101 Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014, 1102 . 1104 Authors' Addresses 1106 Haomian Zheng 1107 Huawei Technologies 1108 H1-1-A043S Huawei Industrial Base, Songshanhu 1109 Dongguan, Guangdong 523808 1110 China 1112 Email: zhenghaomian@huawei.com 1114 Italo Busi 1115 Huawei Technologies 1116 Milan 1117 Italy 1119 Email: Italo.Busi@huawei.com