idnits 2.17.1 draft-ietf-ccamp-layer1-types-00.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 2 instances of too long lines in the document, the longest one being 1 character 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 (June 6, 2019) is 1786 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-09 -- 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 (-18) exists of draft-ietf-ccamp-otn-topo-yang-06 == Outdated reference: A later version (-20) exists of draft-ietf-ccamp-otn-tunnel-model-06 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: December 8, 2019 June 6, 2019 7 A YANG Data Model for Layer 1 Types 8 draft-ietf-ccamp-layer1-types-00 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 December 8, 2019. 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 . . . . . . . . . . . . . . . . . . . . . 19 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-06-06.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-06-06" { 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)"; 253 } 255 identity ODU1 { 256 base odu-type; 257 description 258 "ODU1 protocol (2.49G)"; 259 } 260 /* 261 identity ODU1e { 262 base odu-type; 263 description 264 "ODU1e protocol (10.35G)."; 265 } 267 identity ODU1f { 268 base odu-type; 269 description 270 "ODU1f protocol (10.56G)."; 271 } 272 */ 273 identity ODU2 { 274 base odu-type; 275 description 276 "ODU2 protocol (10.03G)"; 277 } 279 identity ODU2e { 280 base odu-type; 281 description 282 "ODU2e protocol (10.39G)"; 283 } 284 /* 285 identity ODU2f { 286 base odu-type; 287 description 288 "ODU2f protocol (10.60G)."; 289 } 290 */ 291 identity ODU3 { 292 base odu-type; 293 description 294 "ODU3 protocol (40.31G)"; 295 } 296 /* 297 identity ODU3e1 { 298 base odu-type; 299 description 300 "ODU3e1 protocol (41.77G)."; 301 } 303 identity ODU3e2 { 304 base odu-type; 305 description 306 "ODU3e2 protocol (41.78G)."; 307 } 308 */ 309 identity ODU4 { 310 base odu-type; 311 description 312 "ODU4 protocol (104.79G)"; 313 } 315 identity ODUFlex-cbr { 316 base odu-type; 317 description 318 "ODU Flex CBR protocol for transporting constant bit rate 319 signal"; 320 } 322 identity ODUFlex-gfp { 323 base odu-type; 324 description 325 "ODU Flex GFP protocol for transporting stream of packets 326 using Generic Framing Procedure"; 327 } 329 identity ODUCn { 330 base odu-type; 331 description 332 "ODUCn protocol (beyond 100G)"; 333 } 335 identity client-signal { 336 description 337 "Base identity from which specific client signals for the 338 tunnel are derived"; 339 } 341 // Editor Notes: may consider add the OTUk as client signal; 343 identity ETH-1Gb { 344 base client-signal; 345 description 346 "Client signal type of 1GbE"; 347 } 349 identity ETH-10Gb-LAN { 350 base client-signal; 351 description 352 "Client signal type of 10GbE LAN"; 353 } 355 identity ETH-10Gb-WAN { 356 base client-signal; 357 description 358 "Client signal type of 10GbE WAN"; 359 } 361 identity ETH-40Gb { 362 base client-signal; 363 description 364 "Client signal type of 40GbE"; 365 } 367 identity ETH-100Gb { 368 base client-signal; 369 description 370 "Client signal type of 100GbE"; 371 } 373 identity STM-1 { 374 base client-signal; 375 description 376 "Client signal type of STM-1"; 377 } 378 identity STM-4 { 379 base client-signal; 380 description 381 "Client signal type of STM-4"; 382 } 384 identity STM-16 { 385 base client-signal; 386 description 387 "Client signal type of STM-16"; 388 } 390 identity STM-64 { 391 base client-signal; 392 description 393 "Client signal type of STM-64"; 394 } 396 identity STM-256 { 397 base client-signal; 398 description 399 "Client signal type of STM-256"; 400 } 401 identity OC-3 { 402 base client-signal; 403 description 404 "Client signal type of OC3"; 405 } 407 identity OC-12 { 408 base client-signal; 409 description 410 "Client signal type of OC12"; 411 } 413 identity OC-48 { 414 base client-signal; 415 description 416 "Client signal type of OC48"; 417 } 419 identity OC-192 { 420 base client-signal; 421 description 422 "Client signal type of OC192"; 423 } 425 identity OC-768 { 426 base client-signal; 427 description 428 "Client signal type of OC768"; 429 } 431 identity FC-100 { 432 base client-signal; 433 description 434 "Client signal type of Fibre Channel FC-100"; 435 } 437 identity FC-200 { 438 base client-signal; 439 description 440 "Client signal type of Fibre Channel FC-200"; 441 } 443 identity FC-400 { 444 base client-signal; 445 description 446 "Client signal type of Fibre Channel FC-400"; 447 } 449 identity FC-800 { 450 base client-signal; 451 description 452 "Client signal type of Fibre Channel FC-800"; 453 } 455 identity FC-1200 { 456 base client-signal; 457 description 458 "Client signal type of Fibre Channel FC-1200"; 459 } 461 identity FC-1600 { 462 base client-signal; 463 description 464 "Client signal type of Fibre Channel FC-1600"; 465 } 467 identity FC-3200 { 468 base client-signal; 469 description 470 "Client signal type of Fibre Channel FC-3200"; 471 } 473 identity FICON-4G { 474 base client-signal; 475 description 476 "Client signal type of Fibre Connection 4G"; 477 } 479 identity FICON-8G { 480 base client-signal; 481 description 482 "Client signal type of Fibre Connection 8G"; 483 } 485 identity otn-label-range-type { 486 description 487 "Base identity from which specific OTN label 488 range types derived"; 489 } 491 identity label-range-trib-slot { 492 base otn-label-range-type; 493 description 494 "Defines a range of OTN tributary slots"; 495 } 497 identity label-range-trib-port { 498 base otn-label-range-type; 499 description 500 "Defines a range of OTN tributary ports"; 501 } 503 // Editor Notes: following grouping only used in otn topology model, 504 // so suggest to move to ietf-otn-topology and remove from types. 505 grouping otn-link-bandwidth { 506 description "link bandwidth attributes for OTN"; 507 list odulist { 508 key "odu-type"; 509 description 510 "OTN bandwidth definition"; 511 leaf odu-type { 512 type identityref { 513 base layer1-types:odu-type; 514 } 515 description "ODU type"; 516 } 517 leaf number { 518 type uint16; 519 description "Number of ODUs"; 520 } 521 } 523 } 525 // Editor Notes: following groupings are used in both otn topology 526 // and tunnel model, so suggest to be kept in the types. 527 grouping otn-path-bandwidth { 528 description "path bandwidth attributes for OTN"; 529 leaf odu-type { 530 type identityref { 531 base layer1-types:odu-type; 532 } 533 description "ODU type"; 534 } 535 } 536 // Editor Notes: following groupings are used in both otn topology 537 // and tunnel model, so suggest to be kept in the types. 538 grouping otn-label-restriction { 539 description "label restriction information for OTN"; 540 leaf range-type { 541 type identityref { 542 base layer1-types:otn-label-range-type; 543 } 544 description "type for range"; 545 } 546 leaf tsg { 547 type identityref { 548 base layer1-types:tributary-slot-granularity; 549 } 550 description "Tributary slot granularity."; 551 reference 552 "G.709/Y.1331, February 2016: Interfaces for the 553 Optical Transport Network (OTN)"; 554 } 555 leaf priority { 556 type uint8; 557 description "priority."; 558 } 559 } 561 // Editor Notes: following groupings are used in both otn topology 562 // and tunnel model, so suggest to be kept in the types. 563 grouping otn-link-label { 564 description "link label information for OTN, for label-start/end"; 565 choice otn-label-type { 566 description 567 "OTN label range type, either TPN range or TS range"; 568 case tributary-port { 569 leaf tpn { 570 type uint16 { 571 range "1..4095"; 572 } 573 description 574 "Tributary Port Number. Applicable in case of mux services."; 575 reference 576 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 577 G.709 Optical Transport Networks."; 578 } 579 } 580 case tributary-slot { 581 leaf ts { 582 type uint16 { 583 range "1..4095"; 584 } 585 description 586 "Tributary Slot Number. Applicable in case of mux services."; 587 reference 588 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 589 G.709 Optical Transport Networks."; 590 } 591 } 592 } 593 } 595 // Editor Notes: following groupings are used in both otn topology 596 // and tunnel model, so suggest to be kept in the types. 597 grouping otn-path-label { 598 description "label information for OTN, for label-hop"; 599 leaf tpn { 600 type uint16 { 601 range "1..4095"; 602 } 603 description 604 "Tributary Port Number. Applicable in case of mux services."; 605 reference 606 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 607 G.709 Optical Transport Networks."; 608 } 609 leaf tsg { 610 type identityref { 611 base layer1-types:tributary-slot-granularity; 612 } 613 description "Tributary slot granularity."; 614 reference 615 "G.709/Y.1331, February 2016: Interfaces for the 616 Optical Transport Network (OTN)"; 617 } 618 leaf ts-list { 619 type string { 620 pattern "([1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?" 621 + "(,[1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?)*)"; 622 } 623 description 624 "A list of available tributary slots ranging 625 between 1 and 9999. 626 For example 1-20,25,50-1000"; 627 reference "RFC 7139: GMPLS Signaling Extensions for Control 628 of Evolving G.709 Optical Transport Networks"; 629 } 630 } 632 // Editor Notes: following grouping only used in otn topology model, 633 // so suggest to move to ietf-otn-topology and remove from types. 634 grouping otn-label-step { 635 description "Label step for OTN"; 636 choice otn-label-type { 637 description 638 "OTN label range type, either TPN range or TS range"; 639 case tributary-port { 640 leaf tpn-step { 641 type uint16 { 642 range "1..80"; 643 } 644 default 1; 645 description 646 "Label step which represents possible increments for 647 Tributary Port Number."; 648 reference 649 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 650 G.709 Optical Transport Networks."; 651 } 652 } 653 case tributary-slot { 654 leaf ts { 655 type uint16 { 656 range "1..80"; 657 } 658 default 1; 659 description 660 "Label step which represents possible increments for 661 Tributary Slot Number."; 662 reference 663 "RFC7139: GMPLS Signaling Extensions for Control of Evolving 664 G.709 Optical Transport Networks."; 665 } 666 } 668 } 669 } 671 // Editor Notes: to be reviewed for the following coding functions. 672 identity optical-interface-func { 673 description 674 "base identity from which optical-interface-function is 675 derived."; 676 } 678 identity SX-PMD-clause-38 { 679 base "optical-interface-func"; 680 description 681 "SX-PMD-clause-38 Optical Interface function for 682 1000BASE-X PCS-36"; 683 reference "MEF63 & IEEE802.3"; 684 } 686 identity LX-PMD-clause-38 { 687 base "optical-interface-func"; 688 description 689 "LX-PMD-clause-38 Optical Interface function for 690 1000BASE-X PCS-36"; 691 reference "MEF63 & IEEE802.3"; 692 } 694 identity LX10-PMD-clause-59 { 695 base "optical-interface-func"; 696 description 697 "LX10-PMD-clause-59 Optical Interface function for 698 1000BASE-X PCS-36"; 699 reference "MEF63 & IEEE802.3"; 700 } 702 identity BX10-PMD-clause-59 { 703 base "optical-interface-func"; 704 description 705 "BX10-PMD-clause-59 Optical Interface function for 706 1000BASE-X PCS-36"; 707 reference "MEF63 & IEEE802.3"; 708 } 710 identity LW-PMD-clause-52 { 711 base "optical-interface-func"; 712 description 713 "LW-PMD-clause-52 Optical Interface function for 714 10GBASE-W PCS-49-WIS-50"; 715 reference "MEF63 & IEEE802.3"; 717 } 719 identity EW-PMD-clause-52 { 720 base "optical-interface-func"; 721 description 722 "EW-PMD-clause-52 Optical Interface function for 723 10GBASE-W PCS-49-WIS-50"; 724 reference "MEF63 & IEEE802.3"; 725 } 727 identity LR-PMD-clause-52 { 728 base "optical-interface-func"; 729 description 730 "LR-PMD-clause-52 Optical Interface function for 731 10GBASE-R PCS-49"; 732 reference "MEF63 & IEEE802.3"; 733 } 735 identity ER-PMD-clause-52 { 736 base "optical-interface-func"; 737 description 738 "ER-PMD-clause-52 Optical Interface function for 739 10GBASE-R PCS-49"; 740 reference "MEF63 & IEEE802.3"; 741 } 743 identity LR4-PMD-clause-87 { 744 base "optical-interface-func"; 745 description 746 "LR4-PMD-clause-87 Optical Interface function for 747 40GBASE-R PCS-82"; 748 reference "MEF63 & IEEE802.3"; 749 } 751 identity ER4-PMD-clause-87 { 752 base "optical-interface-func"; 753 description 754 "ER4-PMD-clause-87 Optical Interface function for 755 40GBASE-R PCS-82"; 756 reference "MEF63 & IEEE802.3"; 757 } 759 identity FR-PMD-clause-89 { 760 base "optical-interface-func"; 761 description 762 "FR-PMD-clause-89 Optical Interface function for 763 40GBASE-R PCS-82"; 764 reference "MEF63 & IEEE802.3"; 766 } 768 identity LR4-PMD-clause-88 { 769 base "optical-interface-func"; 770 description 771 "LR4-PMD-clause-88 Optical Interface function for 772 100GBASE-R PCS-82"; 773 reference "MEF63 & IEEE802.3"; 774 } 776 identity ER4-PMD-clause-88 { 777 base "optical-interface-func"; 778 description 779 "ER4-PMD-clause-88 Optical Interface function for 780 100GBASE-R PCS-82"; 781 reference "MEF63 & IEEE802.3"; 782 } 784 // Editor Notes: To add the performance monitor parameters per L1CSM; 785 identity service-performance-metric { 786 description "list of service-specific performance metric"; 787 } 789 identity One-way-Delay { 790 base "service-performance-metric"; 791 description "one-way-delay"; 792 } 794 identity One-way-Errored-Second { 795 base "service-performance-metric"; 796 description "one-way-errored-second"; 797 } 799 identity One-way-Severely-Errored-Second { 800 base "service-performance-metric"; 801 description "one-way-severely-errored-second"; 802 } 804 identity One-way-Unavailable-Second { 805 base "service-performance-metric"; 806 description "one-way-unavailable-second"; 807 } 809 identity One-way-Availability { 810 base "service-performance-metric"; 811 description "one-way-availability"; 812 } 814 //Editor Notes: it's useful to separate network specific performance 815 //monitoring with service-specific 816 identity network-performance-metric { 817 description "list of network-specific performance metric"; 818 } 820 identity pm-placeholder { 821 base "network-performance-metric"; 822 description "A placeholder for potential performance monitoring 823 on L1 networks"; 824 } 825 } 826 828 6. Security Considerations 830 The YANG module specified in this document defines a schema for data 831 that is designed to be accessed via network management protocols such 832 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 833 is the secure transport layer, and the mandatory-to-implement secure 834 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 835 is HTTPS, and the mandatory-to-implement secure transport is TLS 836 [RFC8446]. 838 The NETCONF access control model [RFC8341] provides the means to 839 restrict access for particular NETCONF or RESTCONF users to a 840 preconfigured subset of all available NETCONF or RESTCONF protocol 841 operations and content. 843 The YANG module in this document defines layer 1 type definitions 844 (i.e., typedef, identity and grouping statements) in YANG data 845 modeling language to be imported and used by other layer 1 846 technology-specific modules. When imported and used, the resultant 847 schema will have data nodes that can be writable, or readable. The 848 access to such data nodes may be onsidered sensitive or vulnerable in 849 some network environments. Write operations (e.g., edit-config) to 850 these data nodes without proper protection can have a negative effect 851 on network operations. 853 The security considerations spelled out in the YANG 1.1 specification 854 [RFC7950] apply for this document as well. 856 7. IANA Considerations 858 It is proposed that IANA should assign new URIs from the "IETF XML 859 Registry" [RFC3688] as follows: 861 URI: urn:ietf:params:xml:ns:yang:ietf-layer1-types 862 Registrant Contact: The IESG 863 XML: N/A; the requested URI is an XML namespace. 865 This document registers following YANG modules in the YANG Module 866 Names registry [RFC7950]. 868 name: ietf-layer1-types 869 namespace: urn:ietf:params:xml:ns:yang:ietf-otn-types 870 prefix: layer1-types 871 reference: RFC XXXX 873 8. Acknowledgements 875 TBD. 877 9. Contributors 879 Dieter Beller 880 Nokia 881 Email: dieter.beller@nokia.com 883 Sergio Belotti 884 Nokia 885 Email: sergio.belotti@nokia.com 887 Yanlei Zheng 888 China Unicom 889 Email: zhengyl@dimpt.com 891 Aihua Guo 892 Huawei Technologies 893 Email: aihuaguo@huawei.com 895 Young Lee 896 Huawei Technologies 897 Email: leeyoung@huawei.com 899 Lei Wang 900 China Mobile 901 Email: wangleiyj@chinamobile.com 903 Oscar Gonzalez de Dios 904 Telefonica 905 Email: oscar.gonzalezdedios@telefonica.com 907 Xufeng Liu 908 Volta Networks 909 Email: xufeng.liu.ietf@gmail.com 911 Yunbin Xu 912 CAICT 913 Email: xuyunbin@ritt.com 915 Anurag Sharma 916 Google 917 Email: ansha@google.com 919 Rajan Rao 920 Infinera 921 Email: rrao@infinera.com 923 Victor Lopez 924 Telefonica 925 Email: victor.lopezalvarez@telefonica.com 927 Yunbo Li 928 China Mobile 929 Email: liyunbo@chinamobile.com 931 10. References 933 10.1. Normative References 935 [I-D.ietf-teas-yang-te-types] 936 Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, 937 "Traffic Engineering Common YANG Types", draft-ietf-teas- 938 yang-te-types-09 (work in progress), May 2019. 940 [MEF63] M, EF., "Subscriber Layer1 Service Attributes Technical 941 Specification", MEF63 , August 2018. 943 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 944 DOI 10.17487/RFC3688, January 2004, 945 . 947 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 948 and A. Bierman, Ed., "Network Configuration Protocol 949 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 950 . 952 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 953 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 954 . 956 [RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, D., 957 and K. Pithewan, "GMPLS Signaling Extensions for Control 958 of Evolving G.709 Optical Transport Networks", RFC 7139, 959 DOI 10.17487/RFC7139, March 2014, 960 . 962 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 963 RFC 7950, DOI 10.17487/RFC7950, August 2016, 964 . 966 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 967 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 968 . 970 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 971 Access Control Model", STD 91, RFC 8341, 972 DOI 10.17487/RFC8341, March 2018, 973 . 975 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 976 and R. Wilton, "Network Management Datastore Architecture 977 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 978 . 980 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 981 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 982 . 984 10.2. Informative References 986 [I-D.ietf-ccamp-l1csm-yang] 987 Fioccola, G., Lee, K., Lee, Y., Dhody, D., and D. 988 Ceccarelli, "A YANG Data Model for L1 Connectivity Service 989 Model (L1CSM)", draft-ietf-ccamp-l1csm-yang-09 (work in 990 progress), March 2019. 992 [I-D.ietf-ccamp-otn-topo-yang] 993 Zheng, H., Guo, A., Busi, I., Sharma, A., Liu, X., 994 Belotti, S., Xu, Y., Wang, L., and O. Dios, "A YANG Data 995 Model for Optical Transport Network Topology", draft-ietf- 996 ccamp-otn-topo-yang-06 (work in progress), February 2019. 998 [I-D.ietf-ccamp-otn-tunnel-model] 999 Zheng, H., Guo, A., Busi, I., Sharma, A., Rao, R., 1000 Belotti, S., Lopezalvarez, V., Li, Y., and Y. Xu, "OTN 1001 Tunnel YANG Model", draft-ietf-ccamp-otn-tunnel-model-06 1002 (work in progress), February 2019. 1004 [RFC7062] Zhang, F., Ed., Li, D., Li, H., Belotti, S., and D. 1005 Ceccarelli, "Framework for GMPLS and PCE Control of G.709 1006 Optical Transport Networks", RFC 7062, 1007 DOI 10.17487/RFC7062, November 2013, 1008 . 1010 [RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and 1011 J. Drake, "Traffic Engineering Extensions to OSPF for 1012 GMPLS Control of Evolving G.709 Optical Transport 1013 Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014, 1014 . 1016 Authors' Addresses 1018 Haomian Zheng 1019 Huawei Technologies 1020 H1-1-A043S Huawei Industrial Base, Songshanhu 1021 Dongguan, Guangdong 523808 1022 China 1024 Email: zhenghaomian@huawei.com 1026 Italo Busi 1027 Huawei Technologies 1028 Milan 1029 Italy 1031 Email: Italo.Busi@huawei.com