idnits 2.17.1 draft-ietf-ccamp-layer1-types-01.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 -- The document date (July 8, 2019) is 1747 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-10 -- Possible downref: Non-RFC (?) normative reference: ref. 'MEF63' == Outdated reference: A later version (-26) exists of draft-ietf-ccamp-l1csm-yang-09 == Outdated reference: A later version (-17) exists of draft-ietf-ccamp-otn-topo-yang-07 == Outdated reference: A later version (-20) exists of draft-ietf-ccamp-otn-tunnel-model-06 Summary: 0 errors (**), 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: January 9, 2020 July 8, 2019 7 A YANG Data Model for Layer 1 Types 8 draft-ietf-ccamp-layer1-types-01 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 January 9, 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 5. OTN Tunnel YANG Code . . . . . . . . . . . . . . . . . . . . 5 59 6. Security Considerations . . . . . . . . . . . . . . . . . . . 18 60 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 61 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19 62 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 19 63 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 64 10.1. Normative References . . . . . . . . . . . . . . . . . . 20 65 10.2. Informative References . . . . . . . . . . . . . . . . . 21 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 68 1. Introduction 70 This document introduces a collection of common data types which 71 would be used in Layer 1 networks. The derived types and groupings 72 are designed to be the common types applicable for modeling Traffic 73 Engineering (TE) features for Layer 1 optical networks. 75 Typical L1 network, the Optical Transport Networking, was specified 76 in [RFC7062]. Corresponding routing and signaling protocol have been 77 specified in [RFC7138] and [RFC7139]. The types and groupings 78 defined in this document is consistent to these document, and will be 79 imported in other Layer 1 data models, including but not restrictive 80 to, [I-D.ietf-ccamp-otn-topo-yang], [I-D.ietf-ccamp-otn-tunnel-model] 81 and [I-D.ietf-ccamp-l1csm-yang]. 83 The data model in this draft has only types defined including 84 groupings, typedef and identities. There is no need to include 85 configuration and state data according to the new Network Management 86 Datastore Architecture [RFC8342]. The content in this draft is in 87 consistent with [MEF63]. 89 2. Terminology and Notations 91 Refer to [RFC7062] for the key terms used in this document, and the 92 terminology for describing YANG data models can be found in 93 [RFC7950]. 95 3. Prefix in Data Node Names 97 In this document, names of data nodes and other data model objects 98 are prefixed using the standard prefix associated with the 99 corresponding YANG imported modules. 101 +-------------+---------------------------+----------------------+ 102 | Prefix | YANG module | Reference | 103 +-------------+---------------------------+----------------------+ 104 | layer1-types| ietf-layer1-types | This Document | 105 +-------------+---------------------------+----------------------+ 107 4. Layer 1 Types Overview 109 4.1. Relationship with other Modules 111 This document defines one YANG module for common Layer 1 types: ietf- 112 layer1-types for OTN specific types. The objective is to specifies 113 common Layer 1 TE types that can be imported by layer 1 specific 114 technology, for example OTN, in its technology-specific modules such 115 as topology and tunnels. It is worth noting that the generic 116 traffic-engineering (TE) types module is specified in 117 [I-D.ietf-teas-yang-te-types] as ietf-te-types, and both the module 118 ietf-te-types and ietf-layer1-types are needed to be imported when 119 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 for ODUk or ODUCn. Three 129 granularities, 1.25G/2.5G/5G, have been specified. 131 odu-type: 133 This is to specify the type of ODUk. 135 client-signal: 137 This is to specify the client signal types of OTN networks. The 138 initial input was the G-PID specified in [RFC7139]. Identities about 139 a few categories of client signal types, including ETH, STM-n, OC and 140 Fiber Channel have been specified. 142 otn-label-range-type: 144 The label range type of OTN has two different representations, 145 tributary slots (TS) and tributary port number (TPN), according to 146 [RFC7139]. Respective representation is specified under this same 147 base type. 149 otn-link-bandwidth: 151 This grouping defines the link bandwidth information and could be 152 used in OTN topology model for bandwidth representation. All the 153 bandwidth related sections in generic topology module, ietf-te- 154 topology, need to be augmented with this grouping for the usage of 155 Layer 1. 157 otn-path-bandwidth: 159 This grouping defines the path bandwidth information and could be 160 used in OTN topology model for bandwidth representation. All the 161 bandwidth related sections in generic topology module, ietf-te- 162 topology, need to be augmented with this grouping for the usage of 163 Layer 1. This grouping is also applicable to set up the OTN tunnel. 165 otn-label-restriction and otn-label-step: 167 These groupings are used for the augmentation of OTN label in a 168 specific way. 170 otn-link-label and otn-path-label: 172 These groupings are used for the augmentation of label for OTN link 173 and path respectively. 175 optical-interface-func: 177 The optical interface function is specified in [MEF63]. This 178 grouping describes the functionality which encodes bits for 179 transmission and the corresponding decode upon reception. 181 service-performance-metric: 183 The service performance metric is a quantitative characterization of 184 Layer 1 characteristic information delivery quality experienced by 185 the Layer 1 subscriber. 187 5. OTN Tunnel YANG Code 189 file "ietf-layer1-types@2019-07-08.yang" 190 module ietf-layer1-types { 191 namespace "urn:ietf:params:xml:ns:yang:ietf-layer1-types"; 192 prefix "layer1-types"; 194 organization 195 "IETF CCAMP Working Group"; 196 contact 197 "WG Web: 198 WG List: 200 Editor: Haomian Zheng 201 203 Editor: Italo Busi 204 "; 206 description 207 "This module defines Layer 1 types."; 209 revision "2019-07-07" { 210 description 211 "Initial Version"; 212 reference 213 "RFC XXXX: A YANG Data Model for Layer 1 Types"; 214 // RFC Ed.: replace XXXX with actual RFC number, update date 215 // information and remove this note 216 } 218 identity tributary-slot-granularity { 219 description 220 "Tributary slot granularity"; 221 reference 222 "G.709/Y.1331, February 2016: Interfaces for the Optical 223 Transport Network (OTN)"; 224 } 226 identity tsg-1.25G { 227 base tributary-slot-granularity; 228 description 229 "1.25G tributary slot granularity"; 230 } 232 identity tsg-2.5G { 233 base tributary-slot-granularity; 234 description 235 "2.5G tributary slot granularity"; 236 } 238 identity tsg-5G { 239 base tributary-slot-granularity; 240 description 241 "5G tributary slot granularity"; 242 } 244 identity odu-type { 245 description 246 "Base identity for protocol framing used by tributary signals."; 247 } 249 identity ODU0 { 250 base odu-type; 251 description 252 "ODU0 protocol (1.24G), RFC7139/ITU-T G.709, standard track."; 253 } 255 identity ODU1 { 256 base odu-type; 257 description 258 "ODU1 protocol (2.49G), RFC7139/ITU-T G.709, standard track."; 259 } 261 identity ODU1e { 262 base odu-type; 263 description 264 "ODU1e protocol (10.35G), RFC7963/ITU-T G.sup43, informational."; 265 } 267 identity ODU2 { 268 base odu-type; 269 description 270 "ODU2 protocol (10.03G), RFC7139/ITU-T G.709, standard track."; 271 } 273 identity ODU2e { 274 base odu-type; 275 description 276 "ODU2e protocol (10.39G), RFC7139/ITU-T G.709, standard track."; 277 } 279 identity ODU3 { 280 base odu-type; 281 description 282 "ODU3 protocol (40.31G), RFC7139/ITU-T G.709, standard track."; 283 } 285 identity ODU3e1 { 286 base odu-type; 287 description 288 "ODU3e1 protocol (41.77G), RFC7963/ITU-T G.sup43, informational."; 289 } 291 identity ODU3e2 { 292 base odu-type; 293 description 294 "ODU3e2 protocol (41.78G), RFC7963/ITU-T G.sup43, informational."; 295 } 297 identity ODU4 { 298 base odu-type; 299 description 300 "ODU4 protocol (104.79G), RFC7139/ITU-T G.709, standard track."; 301 } 303 identity ODUFlex-cbr { 304 base odu-type; 305 description 306 "ODU Flex CBR protocol for transporting constant bit rate 307 signal"; 308 } 310 identity ODUFlex-gfp { 311 base odu-type; 312 description 313 "ODU Flex GFP protocol for transporting stream of packets 314 using Generic Framing Procedure"; 315 } 317 identity ODUCn { 318 base odu-type; 319 description 320 "ODUCn protocol (beyond 100G)"; 321 } 323 identity client-signal { 324 description 325 "Base identity from which specific client signals for the 326 tunnel are derived"; 327 } 329 // Editor Notes: may consider add the OTUk as client signal; 330 identity ETH-1Gb { 331 base client-signal; 332 description 333 "Client signal type of 1GbE"; 334 } 336 identity ETH-10Gb-LAN { 337 base client-signal; 338 description 339 "Client signal type of 10GbE LAN"; 340 } 342 identity ETH-10Gb-WAN { 343 base client-signal; 344 description 345 "Client signal type of 10GbE WAN"; 346 } 348 identity ETH-40Gb { 349 base client-signal; 350 description 351 "Client signal type of 40GbE"; 352 } 354 identity ETH-100Gb { 355 base client-signal; 356 description 357 "Client signal type of 100GbE"; 358 } 360 identity STM-1 { 361 base client-signal; 362 description 363 "Client signal type of STM-1"; 364 } 366 identity STM-4 { 367 base client-signal; 368 description 369 "Client signal type of STM-4"; 370 } 372 identity STM-16 { 373 base client-signal; 374 description 375 "Client signal type of STM-16"; 376 } 377 identity STM-64 { 378 base client-signal; 379 description 380 "Client signal type of STM-64"; 381 } 383 identity STM-256 { 384 base client-signal; 385 description 386 "Client signal type of STM-256"; 387 } 388 identity OC-3 { 389 base client-signal; 390 description 391 "Client signal type of OC3"; 392 } 394 identity OC-12 { 395 base client-signal; 396 description 397 "Client signal type of OC12"; 398 } 400 identity OC-48 { 401 base client-signal; 402 description 403 "Client signal type of OC48"; 404 } 406 identity OC-192 { 407 base client-signal; 408 description 409 "Client signal type of OC192"; 410 } 412 identity OC-768 { 413 base client-signal; 414 description 415 "Client signal type of OC768"; 416 } 418 identity FC-100 { 419 base client-signal; 420 description 421 "Client signal type of Fibre Channel FC-100"; 422 } 424 identity FC-200 { 425 base client-signal; 426 description 427 "Client signal type of Fibre Channel FC-200"; 428 } 430 identity FC-400 { 431 base client-signal; 432 description 433 "Client signal type of Fibre Channel FC-400"; 434 } 436 identity FC-800 { 437 base client-signal; 438 description 439 "Client signal type of Fibre Channel FC-800"; 440 } 442 identity FC-1200 { 443 base client-signal; 444 description 445 "Client signal type of Fibre Channel FC-1200"; 446 } 448 identity FC-1600 { 449 base client-signal; 450 description 451 "Client signal type of Fibre Channel FC-1600"; 452 } 454 identity FC-3200 { 455 base client-signal; 456 description 457 "Client signal type of Fibre Channel FC-3200"; 458 } 460 identity FICON-4G { 461 base client-signal; 462 description 463 "Client signal type of Fibre Connection 4G"; 464 } 466 identity FICON-8G { 467 base client-signal; 468 description 469 "Client signal type of Fibre Connection 8G"; 470 } 472 identity otn-label-range-type { 473 description 474 "Base identity from which specific OTN label 475 range types derived"; 476 } 478 identity label-range-trib-slot { 479 base otn-label-range-type; 480 description 481 "Defines a range of OTN tributary slots"; 482 } 484 identity label-range-trib-port { 485 base otn-label-range-type; 486 description 487 "Defines a range of OTN tributary ports"; 488 } 490 // Editor Notes: following grouping only used in otn topology model, 491 // so suggest to move to ietf-otn-topology and remove from types. 492 grouping otn-link-bandwidth { 493 description "link bandwidth attributes for OTN"; 494 list odulist { 495 key "odu-type"; 496 description 497 "OTN bandwidth definition"; 498 leaf odu-type { 499 type identityref { 500 base layer1-types:odu-type; 501 } 502 description "ODU type"; 503 } 504 leaf number { 505 type uint16; 506 description "Number of ODUs"; 507 } 508 } 509 } 511 // Editor Notes: following groupings are used in both otn topology 512 // and tunnel model, so suggest to be kept in the types. 513 grouping otn-path-bandwidth { 514 description "path bandwidth attributes for OTN"; 515 leaf odu-type { 516 type identityref { 517 base layer1-types:odu-type; 518 } 519 description "ODU type"; 520 } 522 } 523 // Editor Notes: following groupings are used in both otn topology 524 // and tunnel model, so suggest to be kept in the types. 525 grouping otn-label-restriction { 526 description "label restriction information for OTN"; 527 leaf range-type { 528 type identityref { 529 base layer1-types:otn-label-range-type; 530 } 531 description "type for range"; 532 } 533 leaf tsg { 534 type identityref { 535 base layer1-types:tributary-slot-granularity; 536 } 537 description "Tributary slot granularity."; 538 reference 539 "G.709/Y.1331, February 2016: Interfaces for the 540 Optical Transport Network (OTN)"; 541 } 542 leaf priority { 543 type uint8; 544 description "priority."; 545 } 546 } 548 // Editor Notes: following groupings are used in both otn topology 549 // and tunnel model, so suggest to be kept in the types. 550 grouping otn-link-label { 551 description "link label information for OTN, for label-start/end"; 552 choice otn-label-type { 553 description 554 "OTN label range type, either TPN range or TS range"; 555 case tributary-port { 556 leaf tpn { 557 type uint16 { 558 range "1..4095"; 559 } 560 description 561 "Tributary Port Number. Applicable for mux services."; 562 reference 563 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 564 G.709 Optical Transport Networks."; 565 } 566 } 567 case tributary-slot { 568 leaf ts { 569 type uint16 { 570 range "1..4095"; 571 } 572 description 573 "Tributary Slot Number. Applicable for mux services."; 574 reference 575 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 576 G.709 Optical Transport Networks."; 577 } 578 } 579 } 580 } 582 // Editor Notes: following groupings are used in both otn topology 583 // and tunnel model, so suggest to be kept in the types. 584 grouping otn-path-label { 585 description "label information for OTN, for label-hop"; 586 leaf tpn { 587 type uint16 { 588 range "1..4095"; 589 } 590 description 591 "Tributary Port Number. Applicable in case of mux services."; 592 reference 593 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 594 G.709 Optical Transport Networks."; 595 } 596 leaf tsg { 597 type identityref { 598 base layer1-types:tributary-slot-granularity; 599 } 600 description "Tributary slot granularity."; 601 reference 602 "G.709/Y.1331, February 2016: Interfaces for the 603 Optical Transport Network (OTN)"; 604 } 605 leaf ts-list { 606 type string { 607 pattern "([1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?" 608 + "(,[1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?)*)"; 609 } 610 description 611 "A list of available tributary slots ranging 612 between 1 and 9999. 613 For example 1-20,25,50-1000"; 614 reference "RFC 7139: GMPLS Signaling Extensions for Control 615 of Evolving G.709 Optical Transport Networks"; 616 } 617 } 618 // Editor Notes: following grouping only used in otn topology model, 619 // so suggest to move to ietf-otn-topology and remove from types. 620 grouping otn-label-step { 621 description "Label step for OTN"; 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-step { 627 type uint16 { 628 range "1..80"; 629 } 630 default 1; 631 description 632 "Label step which represents possible increments for 633 Tributary Port Number."; 634 reference 635 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 636 G.709 Optical Transport Networks."; 637 } 638 } 639 case tributary-slot { 640 leaf ts { 641 type uint16 { 642 range "1..80"; 643 } 644 default 1; 645 description 646 "Label step which represents possible increments for 647 Tributary Slot Number."; 648 reference 649 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 650 G.709 Optical Transport Networks."; 651 } 652 } 653 } 654 } 656 // Editor Notes: to be reviewed for the following coding functions. 657 identity optical-interface-func { 658 description 659 "base identity from which optical-interface-function is 660 derived."; 661 } 663 identity SX-PMD-clause-38 { 664 base "optical-interface-func"; 665 description 666 "SX-PMD-clause-38 Optical Interface function for 667 1000BASE-X PCS-36"; 668 reference "MEF63 & IEEE802.3"; 669 } 671 identity LX-PMD-clause-38 { 672 base "optical-interface-func"; 673 description 674 "LX-PMD-clause-38 Optical Interface function for 675 1000BASE-X PCS-36"; 676 reference "MEF63 & IEEE802.3"; 677 } 679 identity LX10-PMD-clause-59 { 680 base "optical-interface-func"; 681 description 682 "LX10-PMD-clause-59 Optical Interface function for 683 1000BASE-X PCS-36"; 684 reference "MEF63 & IEEE802.3"; 685 } 687 identity BX10-PMD-clause-59 { 688 base "optical-interface-func"; 689 description 690 "BX10-PMD-clause-59 Optical Interface function for 691 1000BASE-X PCS-36"; 692 reference "MEF63 & IEEE802.3"; 693 } 695 identity LW-PMD-clause-52 { 696 base "optical-interface-func"; 697 description 698 "LW-PMD-clause-52 Optical Interface function for 699 10GBASE-W PCS-49-WIS-50"; 700 reference "MEF63 & IEEE802.3"; 701 } 703 identity EW-PMD-clause-52 { 704 base "optical-interface-func"; 705 description 706 "EW-PMD-clause-52 Optical Interface function for 707 10GBASE-W PCS-49-WIS-50"; 708 reference "MEF63 & IEEE802.3"; 709 } 711 identity LR-PMD-clause-52 { 712 base "optical-interface-func"; 713 description 714 "LR-PMD-clause-52 Optical Interface function for 715 10GBASE-R PCS-49"; 716 reference "MEF63 & IEEE802.3"; 717 } 719 identity ER-PMD-clause-52 { 720 base "optical-interface-func"; 721 description 722 "ER-PMD-clause-52 Optical Interface function for 723 10GBASE-R PCS-49"; 724 reference "MEF63 & IEEE802.3"; 725 } 727 identity LR4-PMD-clause-87 { 728 base "optical-interface-func"; 729 description 730 "LR4-PMD-clause-87 Optical Interface function for 731 40GBASE-R PCS-82"; 732 reference "MEF63 & IEEE802.3"; 733 } 735 identity ER4-PMD-clause-87 { 736 base "optical-interface-func"; 737 description 738 "ER4-PMD-clause-87 Optical Interface function for 739 40GBASE-R PCS-82"; 740 reference "MEF63 & IEEE802.3"; 741 } 743 identity FR-PMD-clause-89 { 744 base "optical-interface-func"; 745 description 746 "FR-PMD-clause-89 Optical Interface function for 747 40GBASE-R PCS-82"; 748 reference "MEF63 & IEEE802.3"; 749 } 751 identity LR4-PMD-clause-88 { 752 base "optical-interface-func"; 753 description 754 "LR4-PMD-clause-88 Optical Interface function for 755 100GBASE-R PCS-82"; 756 reference "MEF63 & IEEE802.3"; 757 } 759 identity ER4-PMD-clause-88 { 760 base "optical-interface-func"; 761 description 762 "ER4-PMD-clause-88 Optical Interface function for 763 100GBASE-R PCS-82"; 764 reference "MEF63 & IEEE802.3"; 765 } 767 // Editor Notes: To add the performance monitor parameters per L1CSM; 768 identity service-performance-metric { 769 description "list of service-specific performance metric"; 770 } 772 identity One-way-Delay { 773 base "service-performance-metric"; 774 description "one-way-delay"; 775 } 777 identity One-way-Errored-Second { 778 base "service-performance-metric"; 779 description "one-way-errored-second"; 780 } 782 identity One-way-Severely-Errored-Second { 783 base "service-performance-metric"; 784 description "one-way-severely-errored-second"; 785 } 787 identity One-way-Unavailable-Second { 788 base "service-performance-metric"; 789 description "one-way-unavailable-second"; 790 } 792 identity One-way-Availability { 793 base "service-performance-metric"; 794 description "one-way-availability"; 795 } 797 //Editor Notes: it's useful to separate network specific performance 798 //monitoring with service-specific 799 identity network-performance-metric { 800 description "list of network-specific performance metric"; 801 } 803 identity pm-placeholder { 804 base "network-performance-metric"; 805 description "A placeholder for potential performance monitoring 806 on L1 networks"; 807 } 808 } 809 810 6. Security Considerations 812 The YANG module specified in this document defines a schema for data 813 that is designed to be accessed via network management protocols such 814 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 815 is the secure transport layer, and the mandatory-to-implement secure 816 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 817 is HTTPS, and the mandatory-to-implement secure transport is TLS 818 [RFC8446]. 820 The NETCONF access control model [RFC8341] provides the means to 821 restrict access for particular NETCONF or RESTCONF users to a 822 preconfigured subset of all available NETCONF or RESTCONF protocol 823 operations and content. 825 The YANG module in this document defines layer 1 type definitions 826 (i.e., typedef, identity and grouping statements) in YANG data 827 modeling language to be imported and used by other layer 1 828 technology-specific modules. When imported and used, the resultant 829 schema will have data nodes that can be writable, or readable. The 830 access to such data nodes may be onsidered sensitive or vulnerable in 831 some network environments. Write operations (e.g., edit-config) to 832 these data nodes without proper protection can have a negative effect 833 on network operations. 835 The security considerations spelled out in the YANG 1.1 specification 836 [RFC7950] apply for this document as well. 838 7. IANA Considerations 840 It is proposed that IANA should assign new URIs from the "IETF XML 841 Registry" [RFC3688] as follows: 843 URI: urn:ietf:params:xml:ns:yang:ietf-layer1-types 844 Registrant Contact: The IESG 845 XML: N/A; the requested URI is an XML namespace. 847 This document registers following YANG modules in the YANG Module 848 Names registry [RFC7950]. 850 name: ietf-layer1-types 851 namespace: urn:ietf:params:xml:ns:yang:ietf-otn-types 852 prefix: layer1-types 853 reference: RFC XXXX 855 8. Acknowledgements 857 TBD. 859 9. Contributors 861 Dieter Beller 862 Nokia 863 Email: dieter.beller@nokia.com 865 Sergio Belotti 866 Nokia 867 Email: sergio.belotti@nokia.com 869 Yanlei Zheng 870 China Unicom 871 Email: zhengyl@dimpt.com 873 Aihua Guo 874 Huawei Technologies 875 Email: aihuaguo@huawei.com 877 Young Lee 878 Huawei Technologies 879 Email: leeyoung@huawei.com 881 Lei Wang 882 China Mobile 883 Email: wangleiyj@chinamobile.com 885 Oscar Gonzalez de Dios 886 Telefonica 887 Email: oscar.gonzalezdedios@telefonica.com 889 Xufeng Liu 890 Volta Networks 891 Email: xufeng.liu.ietf@gmail.com 893 Yunbin Xu 894 CAICT 895 Email: xuyunbin@ritt.com 897 Anurag Sharma 898 Google 899 Email: ansha@google.com 901 Rajan Rao 902 Infinera 903 Email: rrao@infinera.com 905 Victor Lopez 906 Telefonica 907 Email: victor.lopezalvarez@telefonica.com 909 Yunbo Li 910 China Mobile 911 Email: liyunbo@chinamobile.com 913 10. References 915 10.1. Normative References 917 [I-D.ietf-teas-yang-te-types] 918 Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, 919 "Traffic Engineering Common YANG Types", draft-ietf-teas- 920 yang-te-types-10 (work in progress), July 2019. 922 [MEF63] M, EF., "Subscriber Layer1 Service Attributes Technical 923 Specification", MEF63 , August 2018. 925 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 926 DOI 10.17487/RFC3688, January 2004, 927 . 929 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 930 and A. Bierman, Ed., "Network Configuration Protocol 931 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 932 . 934 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 935 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 936 . 938 [RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, D., 939 and K. Pithewan, "GMPLS Signaling Extensions for Control 940 of Evolving G.709 Optical Transport Networks", RFC 7139, 941 DOI 10.17487/RFC7139, March 2014, 942 . 944 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 945 RFC 7950, DOI 10.17487/RFC7950, August 2016, 946 . 948 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 949 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 950 . 952 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 953 Access Control Model", STD 91, RFC 8341, 954 DOI 10.17487/RFC8341, March 2018, 955 . 957 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 958 and R. Wilton, "Network Management Datastore Architecture 959 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 960 . 962 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 963 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 964 . 966 10.2. Informative References 968 [I-D.ietf-ccamp-l1csm-yang] 969 Fioccola, G., Lee, K., Lee, Y., Dhody, D., and D. 970 Ceccarelli, "A YANG Data Model for L1 Connectivity Service 971 Model (L1CSM)", draft-ietf-ccamp-l1csm-yang-09 (work in 972 progress), March 2019. 974 [I-D.ietf-ccamp-otn-topo-yang] 975 Zheng, H., Guo, A., Busi, I., Sharma, A., Liu, X., 976 Belotti, S., Xu, Y., Wang, L., and O. Dios, "A YANG Data 977 Model for Optical Transport Network Topology", draft-ietf- 978 ccamp-otn-topo-yang-07 (work in progress), July 2019. 980 [I-D.ietf-ccamp-otn-tunnel-model] 981 Zheng, H., Guo, A., Busi, I., Sharma, A., Rao, R., 982 Belotti, S., Lopezalvarez, V., Li, Y., and Y. Xu, "OTN 983 Tunnel YANG Model", draft-ietf-ccamp-otn-tunnel-model-06 984 (work in progress), February 2019. 986 [RFC7062] Zhang, F., Ed., Li, D., Li, H., Belotti, S., and D. 987 Ceccarelli, "Framework for GMPLS and PCE Control of G.709 988 Optical Transport Networks", RFC 7062, 989 DOI 10.17487/RFC7062, November 2013, 990 . 992 [RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and 993 J. Drake, "Traffic Engineering Extensions to OSPF for 994 GMPLS Control of Evolving G.709 Optical Transport 995 Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014, 996 . 998 Authors' Addresses 1000 Haomian Zheng 1001 Huawei Technologies 1002 H1-1-A043S Huawei Industrial Base, Songshanhu 1003 Dongguan, Guangdong 523808 1004 China 1006 Email: zhenghaomian@huawei.com 1008 Italo Busi 1009 Huawei Technologies 1010 Milan 1011 Italy 1013 Email: Italo.Busi@huawei.com