idnits 2.17.1 draft-xiaobn-ccamp-flexe-yang-mod-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 22 instances of too long lines in the document, the longest one being 17 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 233 has weird spacing: '...slot-id uin...' == Line 235 has weird spacing: '...-number uin...' -- The document date (March 11, 2019) is 1872 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'G.709' is defined on line 710, but no explicit reference was found in the text == Unused Reference: 'G.798' is defined on line 714, but no explicit reference was found in the text == Unused Reference: 'G.8023' is defined on line 719, but no explicit reference was found in the text == Unused Reference: 'G.872' is defined on line 724, but no explicit reference was found in the text == Unused Reference: 'I-D.izh-ccamp-flexe-fwk' is defined on line 767, but no explicit reference was found in the text == Outdated reference: A later version (-07) exists of draft-izh-ccamp-flexe-fwk-05 Summary: 1 error (**), 0 flaws (~~), 9 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force X. Niu, Ed. 3 Internet-Draft Q. Wang, Ed. 4 Intended status: Informational ZTE 5 Expires: September 12, 2019 Y. Xu 6 CAICT 7 March 11, 2019 9 A YANG Data Model for Flex Ethernet(FlexE) 10 draft-xiaobn-ccamp-flexe-yang-mod-00 12 Abstract 14 Flex Ethernet(FlexE) implementation agreement have been published by 15 OIF. FlexE provides a generic mechanism for supporting a variety of 16 Ethernet MAC rates that may or may not correspond to any existing 17 Ethernet PHY rate. 19 This document describes a YANG data model for FlexE. It can be used 20 to manage and control devices supporting FlexE functions. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at https://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on September 12, 2019. 39 Copyright Notice 41 Copyright (c) 2019 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (https://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 59 2.2. FlexE terminology used in this document . . . . . . . . . 3 60 3. FlexE Reference Configuration Model . . . . . . . . . . . . . 4 61 4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 4 62 4.1. Requirements . . . . . . . . . . . . . . . . . . . . . . 4 63 5. YANG Data Model for FlexE (Tree Structure) . . . . . . . . . 5 64 6. FlexE types Module . . . . . . . . . . . . . . . . . . . . . 6 65 7. FlexE YANG Module . . . . . . . . . . . . . . . . . . . . . . 9 66 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 67 9. Authors (Full List) . . . . . . . . . . . . . . . . . . . . . 15 68 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15 69 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 70 12. Security Considerations . . . . . . . . . . . . . . . . . . . 16 71 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 72 13.1. Normative References . . . . . . . . . . . . . . . . . . 16 73 13.2. Informative References . . . . . . . . . . . . . . . . . 17 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 76 1. Introduction 78 Flex Ethernet (FlexE) implementation agreement version 1.0 79 [OIFFLEXE1] and 2.0 [OIFFLEXE2] have been published by OIF. FlexE 80 provides a generic mechanism for supporting a variety of Ethernet MAC 81 rates that may or may not correspond to any existing Ethernet PHY 82 rate. This includes MAC rates that are both greater than (through 83 bonding) and less than (through sub-rate and channelization) the 84 Ethernet PHY rates used to carry FlexE. 86 This document defines a date model of FlexE, using YANG[RFC7950]. 87 This model mainly deals with the data model of the FlexE Group and 88 the FlexE client. It can be used by an application to configure and 89 modify the parameters of the FlexE Group and the FlexE client, and to 90 receive notifications, e.g. mismatch errors, from devices supporting 91 FlexE functions. 93 Requirements for the FlexE YANG model are considered. And FlexE YANG 94 tree and YANG files are given. 96 2. Terminology 98 A simplified graphical representation of the data model is used in 99 this document. The meaning of the symbols in the YANG data tree 100 presented later in this document is defined in [RFC8340]. They are 101 provided below for reference. 103 o Brackets "[" and "]" enclose list keys. 105 o Abbreviations before data node names: "rw" means configuration 106 (read-write) and "ro" state data (read-only). 108 o Symbols after data node names: "?" means an optional node, "!" 109 means a presence container, and "*" denotes a list and leaf-list. 111 o Parentheses enclose choice and case nodes, and case nodes are also 112 marked with a colon (":"). 114 o Ellipsis ("...") stands for contents of subtrees that are not 115 shown. 117 o Some of the key terms used in this document are listed as follow. 119 2.1. Requirements Language 121 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 122 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 123 document are to be interpreted as described in RFC 2119 [RFC2119]. 125 2.2. FlexE terminology used in this document 127 a. CSG: Calendar Slot Granularity. It can be 5G or 25G. 129 b. FlexE Calendar: In FlexE IA v1.0, the total capacity of a FlexE 130 Group is represented as a collection of slots which have a 131 granularity of 5G. The calendar for a FlexE Group composed of n 132 100G PHYs is represented as an array of 20n slots (each 133 representing 5G of bandwidth). This calendar is partitioned into 134 sub-calendars, with 20 slots per 100G PHY. Each FlexE client is 135 mapped into one or more calendar slots (based on the bandwidth 136 the FlexE client flow will need). In FlexE IA v2.0[OIFFLEXE2], 137 the total capacity of a FlexE Group is represented as a 138 collection of slots which may have a granularity of 5G or 25G. 139 The calendar for a FlexE Group composed of n 100G FlexE instances 140 from m 100G/200G/400G PHYs is represented as an array of 20n 141 slots (each representing 5G of bandwidth) or 4n slots (25G 142 granularity). 144 c. FlexE Client: An Ethernet flow based on a MAC data rate that may 145 or may not correspond to any Ethernet PHY rate. 147 d. FlexE Group: A FlexE Group is composed of from 1 to n 100G FlexE 148 Instances that are carried by a group of from 1 to m bonded 149 Ethernet PHYs. 151 e. FlexE instance: A 100G FlexE Instance is a unit of information 152 consisting of 100G of capacity able to carry FlexE Client data, 153 together with its associated overhead. 155 Detailed description of these terms can be found in [OIFFLEXE1] and 156 [OIFFLEXE2] . 158 3. FlexE Reference Configuration Model 160 FlexE can be implemented between the FlexE mux and demux in two end 161 devices connected directly by the FlexE links. In this case, FlexE 162 is just a link connection technology. 164 FlexE can also be transported by transport networks. There are three 165 kinds of transport network mapping mechanisms for FlexE signals, that 166 is, FlexE unaware transport, FlexE termination in the transport 167 network and FlexE aware transport. 169 How to configure the ingress or egress of transport network about 170 FlexE mapping relationship may be application specific. In this 171 document, the part of YANG data model for the transport network 172 mapping for FlexE is not included at present. 174 4. Requirements 176 4.1. Requirements 178 This section summarizes the management requirements for the FlexE 179 Group and the FlexE Client. 181 Req-1 The model SHALL support the management of the FlexE Group, 182 consisting of one or more 100G FlexE instances which carried by one 183 or more 100GE, 200GE, 400GE Ethernet PHY(s). 185 The detailed management covers the CURD functions (create, update, 186 read and delete), and lock/unlock. 188 Req-2 The model SHOULD be able to verify that the collection of 189 Ethernet PHY(s) included in a FlexE Group have the same 190 characteristics (e.g. number of PHYs, rate of PHYs, etc.) at the 191 local FlexE shims. If inconsistency exists, notifications (e.g. 192 errors) SHOULD be invoked. 194 Req-3 The model SHOULD be able to verify that the collection of FlexE 195 instances included in a FlexE Group have the same characteristics 196 (e.g. calendar slot granularity, unequipped slots, etc.) at the local 197 FlexE shims. If inconsistency exists, notifications (e.g. errors) 198 SHOULD be invoked. 200 Req-4 The model SHALL allow the addition (or removal) of one or more 201 FlexE clients on a FlexE Group. The addition (or removal) of a FlexE 202 client flow SHALL NOT affect the services for the other FlexE client 203 signals whose size and calendar slot assignments are not changed. 205 Req-5 The model SHALL allow FlexE client signals to flexibly span the 206 set of FlexE instances which comprise the FlexE Group. 208 Req-6 The model SHALL support a FlexE client flow resizing without 209 affecting any existing FlexE clients within the same FlexE Group. 211 Req-7 The model SHALL support the switching of a calendar 212 configuration. There are two calendar configurations, A and B. 214 5. YANG Data Model for FlexE (Tree Structure) 215 module: ietf-flexe-yang 216 +--rw flexe-configuration 217 +--rw flexe-groups 218 | +--rw flexe-group* [group-number] 219 | +--rw group-number uint32 220 | +--rw group-attributes 221 | +--rw flexe-group-available-bandwidth? rt-types:bandwidth-ieee-float32 222 | +--rw calendar-slot-granularity? fe-types:calendar-slot-granularity 223 | +--rw flexe-phy-type? fe-types:flexe-phy-type 224 | +--rw bonded-phys 225 | | +--rw flexe-phys* [phy-number-in-group] 226 | | +--rw phy-number-in-group uint8 227 | | +--rw local-phy-interface? if:interface-ref 228 | | +--rw remote-phy-interface? if:interface-ref 229 | +--rw flexe-instances 230 | | +--rw flexe-instance* [flexe-instance-number] 231 | | | +--rw flexe-instance-number uint8 232 | | | +--rw unavailable-sub-calendar-slot-list* [sub-caldendar-slot-id] 233 | | | +--rw sub-caldendar-slot-id uint8 234 | | +--rw uneqipped-flexe-instance* [flexe-instance-number] 235 | | +--rw flexe-instance-number uint8 236 | +--rw tx-calendar? fe-types:calendar-AorB 237 | +--rw rx-calendar? fe-types:calendar-AorB 238 | +--rw tx-calendar-neg? enumeration 239 | +--rw reply-ca-mode? enumeration 240 +--rw flexe-clients 241 +--rw flexe-client* [client-number] 242 +--rw client-number uint16 243 +--rw bandwidth 244 | +--rw signal-type? flexe-client-signal-rate 245 | +--rw mac-rate? rt-types:bandwidth-ieee-float32 246 +--rw client-interface? if:interface-ref 247 +--rw group-number? uint32 249 Figure 1 251 6. FlexE types Module 253 file "ietf-flexe-types@2019-03-11.yang" 254 module ietf-flexe-types { 255 yang-version 1; 256 namespace "urn:ietf:params:xml:ns:yang:ietf-flexe-types"; 257 prefix "fe-types"; 258 import ietf-routing-types { 259 prefix rt-types; 261 } 262 organization 263 "Internet Engineering Task Force (IETF) CCAMP WG"; 264 contact 265 "WG List: 266 Editor: Xiaobing Niu (niu.xiaobing@zte.com.cn); 267 Editor: Qilei Wang (wang.qilei@zte.com.cn); "; 268 description 269 "This module defines a YANG data model for FlexE."; 270 revision 2019-03-11{ 271 description 272 "Initial version."; 273 reference 274 "draft-xiaobn-ccamp-flexe-yang-mod-00.txt"; 275 } 277 /* typedefs */ 278 typedef calendar-slot-granularity { 279 type enumeration { 280 enum csg-5G { 281 value 1; 282 description "Calendar slot with a 5G granularity"; 283 } 284 enum csg-25G { 285 value 2; 286 description "Calendar slot with a 25G granularity"; 287 } 288 } 289 description 290 "Defines a type representing the granularity of a calendar slot."; 291 } 293 typedef flexe-client-signal-rate { 294 type enumeration { 295 enum flexe-client-signal-10Gbps{ 296 value 1; 297 description 298 "FlexE Client signal rate of 10Gbps"; 299 } 300 enum flexe-client-signal-40Gbps{ 301 value 2; 302 description 303 "FlexE Client signal rate of 40Gbps"; 304 } 305 enum flexe-client-signal-25mGbps{ 306 value 3; 307 description 308 "FlexE Client signal rate of m*25Gbps"; 310 } 311 } 312 description 313 "Defines FlexE Client signal rate, including 10, 40, m*25Gbps."; 314 } 315 typedef flexe-phy-type { 316 type enumeration { 317 enum flexe-phy-100GBASE-R { 318 value 1; 319 description "100GBASE-R PHY"; 320 } 321 enum flexe-phy-200GBASE-R { 322 value 2; 323 description "200GBASE-R PHY"; 324 } 325 enum flexe-phy-400GBASE-R { 326 value 3; 327 description "400GBASE-R PHY"; 328 } 329 } 330 description 331 "Defines types of PHYs in a FlexE group"; 332 } 333 typedef calendar-AorB { 334 type enumeration { 335 enum calendar-A { 336 value 0 ; 337 description 338 "Set the A calendar configuration."; 339 } 340 enum calendar-B { 341 value 1 ; 342 description 343 "Set the B calendar configuration."; 344 } 345 } 346 description 347 "Calendar configuration A or B"; 348 } 349 /* interface states: OK, SF, SD */ 350 typedef intf-state { 351 type enumeration { 352 enum ok { 353 value 0 ; 354 description 355 "The interface state of the FlexE Group is OK."; 356 } 357 enum sf { 358 value 1 ; 359 description 360 "The interface state of the FlexE Group is SF." ; 361 } 362 enum sd { 363 value 2 ; 364 description 365 "The interface state of the FlexE Group is SD."; 366 } 367 } 368 description 369 "Interface state of port group."; 370 } 371 /* grouping */ 372 grouping flexe-client-bandwidth{ 373 leaf signal-type{ 374 type flexe-client-signal-rate; 375 description 376 "Client signal types: 10, 40, m*25 Gbps."; 377 } 378 leaf mac-rate { 379 type rt-types:bandwidth-ieee-float32; 380 description 381 "Bandwidth of clients."; 382 } 383 description 384 "The bandwidth of a FlexE client."; 385 } 386 } 388 390 7. FlexE YANG Module 392 file "ietf-flexe-yang@2019-03-11.yang" 393 module ietf-flexe-yang { 394 yang-version 1; 395 namespace "urn:ietf:params:xml:ns:yang:ietf-flexe-yang"; 396 prefix "flexe"; 397 import ietf-routing-types { 398 prefix rt-types; 399 } 400 import ietf-interfaces { 401 prefix if; 402 } 403 import ietf-flexe-types { 404 prefix fe-types; 405 } 406 organization 407 "Internet Engineering Task Force (IETF) CCAMP WG"; 408 contact 409 "WG List: 410 Editor: Xiaobing Niu (niu.xiaobing@zte.com.cn); 411 Editor: Qilei Wang (wang.qilei@zte.com.cn); "; 412 description 413 "This module defines a YANG data model for FlexE."; 414 revision 2019-03-11 { 415 description 416 "Initial version."; 417 reference 418 "draft-xiaobn-ccamp-flexe-yang-mod-00.txt"; 419 } 421 /* Configuration of FlexE */ 422 container flexe-configuration{ 423 description 424 "FlexE configuration, including configurations of FlexE groups 425 and FlexE clients."; 426 container flexe-groups { 427 description 428 "Container for the FlexE Group"; 429 list flexe-group { 430 key group-number; 431 description 432 "List of FlexE Group"; 433 leaf group-number { 434 type uint32 { 435 range 1..1048574 ; 436 } 437 description 438 "The FlexE Group number is selected from the range 1~0xFFFFE. 439 The value of 0x00000 and 0xFFFFF may not be used to designate 440 a FlexE Group."; 441 } 442 container group-attributes { 443 description 444 "The attributes of a FlexE Group"; 445 leaf flexe-group-available-bandwidth{ 446 type rt-types:bandwidth-ieee-float32; 447 description 448 "Availbale bandwidth allocated in the FlexE Group. 449 Considering the FlexE Client MAC rates supported by FlexE 450 Groups are 10, 40, m*25 Gbps, or a subset of these rates, 451 it's recommended to confine the bandwidth allocated for a 452 FlexE group into a integer compound from litmited types of 453 MAC rateds."; 455 } 456 leaf calendar-slot-granularity{ 457 type fe-types:calendar-slot-granularity; 458 description 459 "The granularity of calendar slot is 5G or 25G"; 460 reference 461 "OIF FlexE IA 2.0"; 462 } 463 leaf flexe-phy-type{ 464 type fe-types:flexe-phy-type; 465 description 466 "Types of PHYs, such as 100/200/400GBASE-R"; 467 reference 468 "OIF FlexE IA 2.0"; 469 } 470 container bonded-phys { 471 description 472 "PHYs bonded to form a FlexE Group"; 473 list flexe-phys { 474 key phy-number-in-group; 475 description 476 "One of bonded PHYs in a FlexE Group"; 477 leaf phy-number-in-group{ 478 type uint8{ 479 range "1 .. 254"; 480 } 481 description 482 "Refer to the clause 6.1 in FlexE IA 2.0. 483 For 100GBASE-R, the FlxeE PHY number and the 100G FlexE 484 instance number are the same and in the range [1-254]; 485 For 200GBASE-R, each PHY number is in the range [1-126]. 486 For 400GBASE-R, each PHY number is in the range [1-62]."; 487 } 488 leaf local-phy-interface{ 489 type if:interface-ref; 490 description 491 "Local PHY interface related to the current PHY in a FlexE group."; 492 } 493 leaf remote-phy-interface{ 494 type if:interface-ref; 495 description 496 "Remote PHY interface related to the current PHY in a FlexE group."; 497 } 498 } 499 } 501 container flexe-instances { 502 description 503 "FlexE instances in a FlexE Group"; 504 list flexe-instance { 505 key flexe-instance-number; 506 description 507 "List of a FlexE instance in a FlexE Group. 508 Not including those unequipped instances in the bonded PHYs."; 509 leaf flexe-instance-number{ 510 type uint8 ; 511 description 512 "Logical FlexE instance number"; 513 reference 514 "Clause 6.1 FlexE Group in FlexE IA 2.0. 515 For 100G, instance num=PHY num; 516 For 200G, 8-bit instance num consists of the PHY num in the upper 517 seven bits, and 0 or 1 in the lower order bit. 518 For 400G, 8-bit instance num consists of the PHY num in the upper 519 six bits, and 0,1,2, or 3 in the two lower order bits. "; 520 } 521 list unavailable-sub-calendar-slot-list { 522 key sub-caldendar-slot-id; 523 description 524 "List of sub-calendar slots unavailable in a FlexE Instance."; 525 leaf sub-caldendar-slot-id { 526 type uint8; 527 description 528 "Identification number of a sub-calendar slot in a FlexE instance. 529 For 5G granularity, the range of slot-id is [0,19]; 530 For 25G granularity, the range of slot-id is [0,3]; 531 Refer to clause 6.7 in FlexE IA 2.0. "; 532 } 533 } 534 } 535 list uneqipped-flexe-instance { 536 key flexe-instance-number; 537 description 538 "Unquipped FlexE instances in the bonded PHYs. 539 Strictly speaking, a unequipped instance does not belong 540 to any FlexE Group, because in the overhead frame, the FlexE 541 Group number is set to 0x00000. 542 Refer to Clause 6.5 Unequipped 100G FlexE Instances."; 543 leaf flexe-instance-number{ 544 type uint8 ; 545 description 546 "Clause 6.1 FlexE Group in FlexE IA 2.0"; 547 } 548 } 549 } 550 leaf tx-calendar { 551 type fe-types:calendar-AorB; 552 description 553 "Calendar configuration in the transmit direction"; 554 } 555 leaf rx-calendar { 556 type fe-types:calendar-AorB; 557 description 558 "Calendar configuration in the receive direction"; 559 } 560 leaf tx-calendar-neg { 561 type enumeration { 562 enum manual { 563 value 1 ; 564 description 565 "Manually configured"; 566 } 567 enum protocol-force { 568 value 2 ; 569 description 570 "Protocol forced"; 571 } 572 enum protocol-normal { 573 value 3 ; 574 description 575 "Protocol normal"; 576 } 577 } 578 description 579 "TX calendar negotiation methods"; 580 } 581 leaf reply-ca-mode { 582 type enumeration { 583 enum never { 584 value 1 ; 585 description 586 "never reply CA (Configuration Ack)"; 587 } 588 enum immediately { 589 value 2 ; 590 description 591 "immediately reply CA (Configuration Ack)"; 592 } 593 enum ask-controller { 594 value 3 ; 595 description 596 "Ask controller for more control"; 597 } 598 } 599 description 600 "Reply CA mode"; 601 } 602 } 603 } 604 } 605 container flexe-clients { 606 description 607 "FlexE clients information"; 608 list flexe-client { 609 key client-number ; 610 description 611 "Attributes of FlexE client" ; 612 leaf client-number { 613 type uint16 { 614 range 1..65534 ; 615 } 616 description 617 "Client number in the range of 1~0xFFFE. 618 The value 0x0000 indicates a calendar slot which is unused (but available). 619 The value 0xFFFF (all ones) indicates a calendar slot that is unavailable. 620 Refer to Clause 7.3.4 in FlexE IA 2.0."; 621 } 622 container bandwidth { 623 description "Client bandwidth"; 624 uses fe-types:flexe-client-bandwidth; 625 } 626 leaf client-interface { 627 type if:interface-ref; 628 description 629 "A FlexE Client is used as an interface."; 630 } 631 leaf group-number { 632 type uint32 { 633 range 1..1048574 ; 634 } 635 description 636 "The FlexE Group is used to transport the FlexE client."; 637 } 638 } 639 } 640 } 641 } 642 643 8. Acknowledgements 645 9. Authors (Full List) 647 Xiaobing NIU (editor) 649 ZTE 651 Beijing, China 653 Email: niu.xiaobing@zte.com.cn 655 Qilei Wang (editor) 657 ZTE 659 Nanjing, China 661 Email: wang.qilei@zte.com.cn 663 Yunbin Xu 665 CAICT 667 Beijing, China 669 Email: xuyunbin@caict.ac.cn 671 10. Contributors 673 11. IANA Considerations 675 This document registers the following namespace URIs in the IETF XML 676 registry[RFC3688]: 678 URI: urn:ietf:params:xml:ns:yang:ietf-flexe-yang 680 Registrant Contact: The IESG. 682 XML: N/A, the requested URI is an XML namespace. 684 This document registers the following YANG modules in the YANG Module 685 Names registry[RFC6020] : 687 name: ietf-flexe-yang 689 namespace: urn:ietf:params:xml:ns:yang:ietf-flexe-yang 691 reference: RFC XXXX (TDB) 693 12. Security Considerations 695 The YANG module specified in this document defines a schema for data 696 that is designed to be accessed via network management protocols such 697 as NETCONF[RFC6241]. Proper standardized security measures should be 698 implemented. 700 There are a number of data nodes defined in this YANG module that are 701 writable/creatable/deletable. These data nodes may be considered 702 sensitive or vulnerable in some network environments. Write 703 operations (e.g., edit-config) to these data nodes without proper 704 protection can have a negative effect on network operations. 706 13. References 708 13.1. Normative References 710 [G.709] ITU-T, "Interfaces for the optical transport network, 711 Amendment 2 ; 06/2018", https://www.itu.int/itu- 712 t/recommendations/rec.aspx?rec=12789, June 2018. 714 [G.798] ITU-T, "Characteristics of optical transport network 715 hierarchy equipment functional blocks ; 08/2018", 716 https://www.itu.int/itu- 717 t/recommendations/rec.aspx?rec=13335, August 2018. 719 [G.8023] ITU-T, "Characteristics of equipment functional blocks 720 supporting Ethernet physical layer and Flex Ethernet 721 interfaces ; 06/2018", https://www.itu.int/itu- 722 t/recommendations/rec.aspx?rec=13544, June 2018. 724 [G.872] ITU-T, "Architecture of optical transport networks; 725 01/2017", https://www.itu.int/itu- 726 t/recommendations/rec.aspx?rec=13086, January 2017. 728 [OIFFLEXE1] 729 OIF, "Flex Ethernet Implementation Agreement 1.0(OIF- 730 FLEXE-01.0); 03/2016", http://www.oiforum.com/wp- 731 content/uploads/OIF-FLEXE-01.0.pdf, March 2016. 733 [OIFFLEXE2] 734 OIF, "Flex Ethernet Implementation Agreement 2.0(OIF- 735 FLEXE-02.0); 06/2018", http://www.oiforum.com/wp- 736 content/uploads/OIF-FLEXE-02.0.pdf, June 2018. 738 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 739 Requirement Levels", BCP 14, RFC 2119, 740 DOI 10.17487/RFC2119, March 1997, 741 . 743 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 744 DOI 10.17487/RFC3688, January 2004, 745 . 747 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 748 the Network Configuration Protocol (NETCONF)", RFC 6020, 749 DOI 10.17487/RFC6020, October 2010, 750 . 752 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 753 and A. Bierman, Ed., "Network Configuration Protocol 754 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 755 . 757 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 758 RFC 7950, DOI 10.17487/RFC7950, August 2016, 759 . 761 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 762 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 763 . 765 13.2. Informative References 767 [I-D.izh-ccamp-flexe-fwk] 768 Hussain, I., Valiveti, R., Wang, Q., Andersson, L., Chen, 769 M., and z. zhenghaomian@huawei.com, "GMPLS Routing and 770 Signaling Framework for Flexible Ethernet (FlexE)", draft- 771 izh-ccamp-flexe-fwk-05 (work in progress), March 2018. 773 Authors' Addresses 775 Xiaobing Niu (editor) 776 ZTE 777 Beijing 778 CN 780 Email: niu.xiaobing@zte.com.cn 781 Qilei Wang (editor) 782 ZTE 783 Nanjing 784 CN 786 Email: wang.qilei@zte.com.cn 788 Yunbin Xu 789 CAICT 790 Beijing 791 CN 793 Email: xuyunbin@caict.ac.cn