idnits 2.17.1 draft-jiang-ccamp-flexe-yang-02.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 (November 4, 2019) is 1628 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Y. Jiang 2 Internet Draft X. He 3 Intended status: Standards Track Huawei 4 W. Cheng 5 China Mobile 6 J. Wang 7 Y. Han 8 Fiberhome 9 Expires: May 2020 November 4, 2019 11 YANG Data Model for FlexE Interface Management 12 draft-jiang-ccamp-flexe-yang-02 14 Abstract 16 This document defines YANG data models for the configuration of Flex 17 Ethernet (FlexE) interfaces, including a FlexE group and its FlexE 18 clients. The YANG modules in this document conforms to the Network 19 Management Datastore Architecture (NMDA). 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six 32 months and may be updated, replaced, or obsoleted by other documents 33 at any time. It is inappropriate to use Internet-Drafts as 34 reference material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on May 4, 2020. 38 Copyright Notice 40 Copyright (c) 2019 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with 48 respect to this document. Code Components extracted from this 49 document must include Simplified BSD License text as described in 50 Section 4.e of the Trust Legal Provisions and are provided without 51 warranty as described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction ................................... 2 56 1.1. Conventions used in this document ........... 3 57 1.2. Terminology ................................. 3 58 2. YANG model hierarchy for FlexE interfaces ...... 4 59 3. YANG Module for FlexE group interface .......... 7 60 4. YANG Module for FlexE client interface ........ 14 61 5. Security Considerations ....................... 16 62 6. IANA Considerations ........................... 18 63 7. References .................................... 18 64 7.1. Normative References ....................... 18 65 7.2. Informative References ..................... 19 66 8. Acknowledgments ............................... 20 68 1. Introduction 70 The Flex Ethernet (FlexE) 2.0 Implementation Agreement [FLEXE] 71 defined by the OIF provides the support of a variety of Ethernet MAC 72 rates that may or may not correspond to any existing Ethernet PHY 73 rate. This includes MAC rates that are both greater than (through 74 bonding) and less than (through sub-rate and channelization) the 75 Ethernet PHY rates used to carry FlexE. Besides 100GBASE-R PHYs, 76 FlexE 2.0 further supports the bonding of 200GBASE-R PHYs or 77 400GBASE-R PHYs respectively. 79 In the FlexE, multiple Ethernet PHYs (each PHY can further consist 80 of one or more FlexE Instances) are bonded into a FlexE Group, and 81 the total capacity of the FlexE Group is represented as a collection 82 of slots (e.g., each slot has a granularity of 5Gbps or 25Gbps). 83 Based on their bandwidth needs, FlexE Clients are each mapped into 84 one or more slots in a FlexE group. The FlexE mechanism operates 85 using a calendar consisting of these slots. 87 This calendar is partitioned into sub-calendars for each PHY 88 (earlier than FlexE 2.0) or sub-calendars for each FlexE instance 89 (FlexE 2.0 and above). For example, the calendar for a FlexE Group 90 composed of n 100G PHYs is partitioned into 20n slots (each slot 91 representing 5Gbps of bandwidth when the slot granularity is 5Gbps). 93 [FLEXE-PS] discusses the problem statements and requirements for 94 FlexE interface management. 96 This document defines a YANG data model for the configuration of a 97 Flex Ethernet interface (i.e., FlexE Group). The data model is 98 augmented based on the generic interfaces data model as defined in 99 [RFC8343], the FlexE attributes are based on the FlexE 2.0 100 Implementation Agreement as specified in [FLEXE]. With the help of 101 this YANG data module, the FlexE Groups can be managed conveniently 102 as ordinary network interfaces on a network device (e.g., a router 103 or bridge). 105 This document also defines a YANG data model for the configuration 106 of a Flex Ethernet client interface (i.e., FlexE Client). The data 107 model is augmented based on the generic interfaces data model as 108 defined in [RFC8343], currently it only includes mac-address and 109 group-number attributes for a FlexE client. 111 The YANG modules in this document conforms to the Network Management 112 Datastore Architecture (NMDA) [RFC8342]. 114 1.1. Conventions used in this document 116 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 117 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", 118 "MAY", and "OPTIONAL" in this document are to be interpreted as 119 described in BCP 14 [RFC2119] [RFC8174] when, and only when, they 120 appear in all capitals, as shown here. 122 1.2. Terminology 124 Most terminologies used in this document are extracted from [FLEXE]. 126 FlexE: Flex Ethernet. 128 FlexE Client: An Ethernet flow based on a MAC data rate that may or 129 may not correspond to any Ethernet PHY rate. 131 FlexE Group: A FlexE Group is composed of from 1 to n Ethernet PHYs. 133 FlexE Instance: A FlexE Instance is a unit of information consisting 134 of 100G of capacity able to carry FlexE Client data, together with 135 its associated overhead. 137 Ethernet PHY: an entity representing Ethernet Physical Coding 138 Sublayer (PCS), Physical Media Attachment (PMA), and Physical Media 139 Dependent (PMD) layers. Each PHY is consisted of one or more FlexE 140 Instance (e.g., a 400GBASE-R PHY has four FlexE Instances). 142 FlexE Calendar: The total capacity of a FlexE Group is represented 143 as a collection of slots. The calendar for a FlexE Group composed 144 of n PHYs is represented in each PHY as an array of slots (e.g., 145 each representing 5Gbps of bandwidth), i.e., calendar-slot-list. 147 2. YANG model hierarchy for FlexE 149 This section describes the hierarchy of the YANG modules for the 150 FlexE interface management and the FlexE client interface. 152 Configuration and status of FlexE group interface information 153 include: 155 - flexe-group specifies a management interface for configuration of 156 a FlexE group. 158 - flexe-phy-list specifies a list of PHYs in a Flex Group. 160 - flexe-client-list specifies a list of FlexE client, each client is 161 mapped to some slots in this FlexE group. flexe-client-if references 162 to a FlexE client interface. flexe-client-status indicates whether 163 there is any fault in local or remote for this client. 165 Configuration and status of FlexE client interface information 166 include: 168 - flexe-group specifies the FlexE Group number of the FlexE group to 169 which this FlexE client belongs. 171 - mac-address specifies the MAC address for a FlexE client. 173 A flag calendar-protocol-enable is added to indicate that whether 174 FlexE calendar negotiation protocol as described in Section 7.3 of 175 [FLEXE] is enabled or not. 177 The readers are assumed to be familiar with FlexE 2.0, as all FlexE 178 terminologies are described in details in [FLEXE]. 180 In order to simplify the YANG module of the FlexE interface and to 181 follow the YANG style of terminology, the full calendar in FlexE is 182 not modelled explicitly. However, a calendar-slot-list per PHY is 183 modeled which represents all the slots in a PHY (i.e., slots in all 184 sub-calendars of the FlexE instances in this PHY), and the calendar 185 is actually a conglomerate of all the slots in calendar-slot-lists 186 for all FlexE PHYs of this FlexE Group. 188 From FlexE 2.0 on, concept of "FlexE Instance" is introduced, which 189 is equivalent to 100GBASE-R PHY, and slots for each instance is used 190 and carried in the overhead. However, we decide not to model the 191 instance, for the following reasons: 193 - instance numbers can be inferred from the FlexE PHY, and any slot 194 in an instance is corresponding to a slot in a PHY; 196 - instance is an internal logical construct, there is no benefit in 197 exposing it for management; 199 - instance is only introduced after FlexE 2.0, its construct will 200 not be compatible with the early versions of FlexE.A simplified YANG 201 tree diagram [RFC8340] representing the data model is typically used 202 by YANG modules. This document uses the same tree diagram syntax as 203 described in [RFC8340]. 205 A tree diagram of the module for FlexE group interface is depicted 206 as the following: 208 module: ietf-flexe 209 augment /if:interfaces/if:interface: 210 +--rw flexe-group 211 +--rw group-number? uint32 212 +--rw slot-granularity? slot-granularity-enumeration 213 +--rw flexe-phy-type? flexe-phy-enumeration 214 +--rw calendar-protocol-enable? boolean 215 +--rw flexe-phy-list* [flexe-phy-if] 216 | +--rw flexe-phy-if? if:interface-ref 217 | +--rw phy-number uint8 218 | +--ro flexe-phy-status? phy-status-enumeration 219 | +--rw calendar-slot-list* [slot-id] 220 | +--rw slot-id uint8 221 | +--rw flexe-slot-status? slot-status-enumeration 222 +--rw flexe-client-list* [client-id] 223 | +--rw client-id uint16 224 | +--rw flexe-client-if? if:interface-ref 225 | +--rw client-slot-list* [client-slot-id] 226 | | +--rw client-slot-id uint8 227 | | +--rw mapped-phy-if? if:interface-ref 228 | | +--rw mapped-slot-id uint8 229 | +--ro flexe-client-status? client-status-enumeration 230 +--ro flexe-group-status? uint8 232 A tree diagram of the module for FlexE client interface is depicted 233 as the following: 234 module: ietf-interfaces-flexe-client 235 augment /if:interfaces/if:interface: 236 +--rw flexe-client 237 +--ro mac-address 238 +--rw group-number? uint32 240 3. YANG Module for FlexE group interface 242 The following YANG data module augments the interface container 243 defined in RFC 8343 for a FlexE group interface. It imports iana-if- 244 type [RFC7224] and ietf-interfaces [RFC8343]. 246 file "ietf-flexe@2019-10-30.yang" 247 module ietf-flexe { 248 yang-version 1.1; 249 namespace "urn:ietf:params:xml:ns:yang:ietf-flexe"; 250 prefix "flexe"; 252 import iana-if-type { 253 prefix ianaift; 254 } 255 import ietf-interfaces { 256 prefix if; 257 reference 258 "RFC8343: A YANG Data Model for Interface Management"; 259 } 261 organization "IETF CCAMP Working Group"; 262 contact 263 "WG Web: http://tools.ietf.org/wg/ccamp/ 264 WG List: 265 Author: Yuanlong Jiang 266 267 Author: Xiang He 268 269 Author: Weiqiang Cheng 270 271 Author: Junfang Wang 272 273 Author: Yalei Han 274 "; 275 description 276 "This YANG module defines a data model for the configuration 277 of FlexE interface."; 279 revision "2019-10-30" { 280 description "Initial version"; 281 reference 282 "draft-jiang-ccamp-flexe-yang-02: YANG Data Model for FlexE 283 Interface Management "; 284 } 285 identity flexEthernet { 286 base ianaift:iana-interface-type; 287 description 288 "Flex Ethernet."; 289 } 291 typedef slot-granularity-enumeration { 292 type enumeration { 293 enum slot-5g { 294 value 1; 295 description 296 "5Gbps per slot."; 297 } 298 enum slot-25g { 299 value 2; 300 description 301 "25Gbps per slot."; 302 } 303 enum slot-others { 304 value 254; 305 description 306 "Other type of granularities per slot."; 307 } 308 } 309 description 310 "The bandwidth granularity of a slot. Options for this 311 enumeration are specified by the OIF standard, currently only 312 5G and 25G are defined."; 313 reference 314 "OIF Flex 2.0: Section 6.7"; 315 } 317 typedef slot-status-enumeration { 318 type enumeration { 319 enum unavailable { 320 value 1; 321 description 322 "slot is unavailable for a FlexE client."; 323 } 324 enum unused { 325 value 2; 326 description 327 "slot is unused."; 328 } 329 enum used { 330 value 3; 331 description 332 "slot is used."; 333 } 334 } 335 description 336 "The status of a slot in a PHY. Options for this enumeration 337 are specified by the OIF standard, 'used' is implicit."; 338 reference 339 "OIF Flex 2.0: Section 7.3.4 and Section 7.6"; 340 } 342 typedef flexe-phy-enumeration { 343 type enumeration { 344 enum 'PHY-100GBASE-R' { 345 value 1; 346 description 347 "100GBASE-R PHY, as defined in FlexE 1.0."; 348 } 349 enum 'PHY-200GBASE-R' { 350 value 2; 351 description 352 "200GBASE-R PHY, as defined in FlexE 2.0."; 353 } 354 enum 'PHY-400GBASE-R' { 355 value 3; 356 description 357 "400GBASE-R PHY, as defined in FlexE 2.0."; 358 } 359 enum 'PHY-50GBASE-R' { 360 value 4; 361 description 362 "50GBASE-R PHY, as defined in FlexE 2.1."; 363 } 364 } 366 description 367 "The current type of PHYs bonded in a FlexE Group. Values for 368 this enumeration are specified by the OIF standard."; 369 reference 370 "OIF Flex 2.0 and 2.1: Section 5.2.1.5"; 371 } 373 typedef phy-status-enumeration { 374 type enumeration { 375 enum phy-status-OK { 376 value 0; 377 description 378 "The FlexE PHY status is ok"; 380 } 381 enum phy-status-LOF { 382 value 1; 383 description 384 "The FlexE PHY status is Loss of Frame"; 385 } 386 enum phy-status-RPF { 387 value 2; 388 description 389 "The FlexE PHY status is Remote PHY Fault"; 390 } 391 enum phy-status-LPF { 392 value 3; 393 description 394 "The FlexE PHY status is Local PHY Fault"; 395 } 396 } 397 description 398 "The current PHY status. RPF, LPF, LOF and OK are defined."; 399 reference 400 "OIF Flex 2.0: Section 7.3.8"; 401 } 403 typedef client-status-enumeration { 405 type enumeration { 406 enum flexe-client-status-OK { 407 value 0; 408 description 409 "The FlexE client status is OK"; 410 } 411 enum flexe-client-status-LF { 412 value 1; 413 description 414 "The FlexE client status is Local Fault"; 415 } 416 enum flexe-client-status-RF { 417 value 2; 418 description 419 "The FlexE client status is Remote Fault"; 420 } 421 } 422 description 423 "The client status. RPF, LPF and OK are defined."; 424 reference 425 "OIF Flex 2.0: Section 7.3.8"; 427 } 429 augment "/if:interfaces/if:interface" { 431 when "if:type = 'ianaift:flexEthernet'" { 432 description "Applies to Flex bonded Ethernet interfaces"; 433 } 435 description 436 "Augment interface model with OIF Flex Ethernet interface 437 specific configuration nodes. Each flexEthernet interface 438 represents a FlexE Group configured in a device."; 440 container flexe-group { 441 description 442 "The struct containing all FlexE related configuration 443 (see OIF FlexE 2.0 Section 6.1). 444 Note that max number of FlexE groups in a network is 63."; 446 leaf group-number { 447 type uint32 { 448 range "1..1048574"; 449 } 450 description 451 "FlexE Group Number as defined in Section 7.3.6 of FlexE 452 2.0."; 453 } 455 leaf slot-granularity { 456 type slot-granularity-enumeration; 457 default "slot-5g"; 458 description 459 "The granularity of a slot in a FlexE group."; 460 } 461 leaf flexe-phy-type { 462 type flexe-phy-enumeration; 463 default "PHY-100GBASE-R"; 464 description 465 "The type of PHYs bonded in a FlexE Group."; 466 } 468 leaf calendar-protocol-enable { 469 type boolean; 470 default true; 471 description 472 "Whether calendar negotiation protocol is enabled or 473 not."; 474 reference 475 "OIF Flex 2.0: Section 7.3.4"; 476 } 478 list flexe-phy-list { 480 key "flexe-phy-if"; 481 description 482 "List of PHYs bonded in a FlexE group."; 484 leaf flexe-phy-if { 485 type if:interface-ref; 486 description 487 "Reference to a Flexe PHY interface."; 488 } 490 leaf phy-number { 491 type uint8 { 492 range "1 .. 254"; 493 } 494 description 495 "PHY number of a FlexE PHY. 496 If PHY type is 100GBASE-R, phy-number is [1,254]. 497 If PHY type is 200GBASE-R, phy-number is [1,126]. 498 If PHY type is 400GBASE-R, phy-number is [1, 62]."; 499 } 501 leaf flexe-phy-status { 502 type phy-status-enumeration; 503 default "phy-status-OK"; 504 config false; 505 description 506 "The FlexE PHY status."; 507 } 509 list calendar-slot-list { 510 key "slot-id"; 511 leaf slot-id { 512 type uint8; 513 description 514 "slot id of a slot in a PHY."; 515 } 516 description 517 "List of slots in a FlexE PHY. Max elements of 518 slot-list for a FlexE PHY is dependent on the PHY 519 bandwidth (X)G and the slot granularity (Y)G, i.e., 520 X/Y. For example, for a 400GBASE-R PHY: 521 If slot-granularity=slot-5g, max-elements is 80. 522 If slot-granularity=slot-25g, max-elements is 16."; 524 leaf flexe-slot-status { 525 type slot-status-enumeration; 526 default unused; 527 config false; 528 description 529 "Slot status of a FlexE slot."; 530 } 531 } //calendar-slot-list 532 } //flexe-phy-list 534 list flexe-client-list { 536 key "client-id"; 537 description 538 "List of FlexE clients in a FlexE Group."; 539 leaf client-id { 540 type uint16 { 541 range "1..65534"; 542 } 543 description 544 "FlexE Client field as defined in FlexE 2.0 Section 545 7.3.4."; 546 } 548 leaf flexe-client-if { 549 type if:interface-ref; 550 description 551 "The type of a flexe client interface must be 552 'flexeClient'."; 553 } 555 list client-slot-list { 556 key "client-slot-id"; 557 min-elements 1; 558 description 559 "List of slots for a FlexE client."; 560 leaf client-slot-id { 561 type uint8; 562 description 563 "Client slot id of a client slot in sequence for a 564 client."; 566 } 568 leaf mapped-phy-if { 569 type if:interface-ref; 570 description 571 "Mapped PHY interface of a client slot."; 572 } 573 leaf mapped-slot-id { 574 type uint8; 575 description 576 "Mapped Slot id of a client slot in the mapped PHY. 577 If a slot [i] is mapped, flexe-slot-status[i] in the 578 Mapped PHY MUST be set to 'used' "; 579 } 580 } // client-slot-list 582 leaf flexe-client-status { 583 type client-status-enumeration; 584 default flexe-client-status-OK; 585 config false; 586 description 587 "The FlexE client status."; 588 } 590 } //flexe-client-list 592 leaf flexe-group-status { 593 type uint8; 594 config false; 595 description 596 "Status for a FlexE Group. If any PHY is in fault, 597 or any FlexE configuration is mismatched, the FlexE 598 Group status is indicated in fault. Status includes: 599 OK, Local Fault, Remote Fault, mismatch and etc."; 600 } 601 } //flexe-group 602 } //augment 603 } 605 606 4. YANG Module for FlexE client interface 608 The following YANG data module augments the interface container 609 defined in RFC 8343 for a FlexE client interface. 611 file "ietf-interfaces-flexe-client@2019-10-30.yang" 612 module ietf-interfaces-flexe-client { 613 yang-version 1.1; 615 namespace 616 "urn:ietf:params:xml:ns:yang:ietf-interfaces-flexe-client"; 618 prefix flexcl; 620 import ietf-interfaces { 621 prefix if; 622 } 624 import ietf-yang-types { 625 prefix yang; 626 } 628 import iana-if-type { 629 prefix ianaift; 630 } 632 organization "IETF CCAMP Working Group"; 633 contact 634 "WG Web: http://tools.ietf.org/wg/ccamp/ 635 WG List: 636 Author: Yuanlong Jiang 637 638 Author: Xiang He 639 640 Author: Weiqiang Cheng 641 642 Author: Junfang Wang 643 644 Author: Yalei Han 645 "; 647 description 648 "This module contains YANG definitions for configuration of 649 'FlexE client' interfaces. FlexE Client is defined in 650 OIF Flexible Ethernet 2.0 Implementation Agreement."; 652 revision 2019-10-30 { 653 description "Initial revision"; 655 reference 656 "Internet draft: draft-jiang-ccamp-flexe-yang-02"; 657 } 658 identity flexeClient { 659 base ianaift:iana-interface-type; 660 description 661 "FlexE Client."; 662 } 664 /* 665 * Configuration parameters for FlexE client interfaces. 666 */ 667 augment "/if:interfaces/if:interface" { 668 when "derived-from-or-self(if:type, 'ianaift:flexeClient')" { 669 description "Applies to FlexE client interfaces"; 670 } 671 description 672 "Augment the interface model with parameters for 673 FlexE client interfaces"; 675 container flexe-client { 676 description 677 "Contains parameters for FlexE client interfaces 678 which expose an Ethernet MAC layer."; 679 leaf mac-address { 680 type yang:mac-address; 681 config false; 682 description 683 "The MAC address of the FlexE client."; 684 } 685 leaf group-number { 686 type uint32 { 687 range "1..1048574"; 688 } 689 description 690 "FlexE Group Number of the FlexE group to which this 691 Client belongs."; 692 } 693 // statistics can further be defined for the MAC layer 694 } 695 } 696 } 697 698 5. Security Considerations 700 The YANG module specified in this document defines a schema for data 701 that is designed to be accessed via network management protocols 702 such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF 703 layer is the secure transport layer, and the mandatory-to-implement 704 secure transport is Secure Shell (SSH) [RFC6242]. The lowest 705 RESTCONF layer is HTTPS, and the mandatory-to-implement secure 706 transport is TLS [RFC8446]. 708 The NETCONF access control model [RFC8341] provides the means to 709 restrict access for particular NETCONF or RESTCONF users to a 710 preconfigured subset of all available NETCONF or RESTCONF protocol 711 operations and content. 713 There are a number of data nodes defined in the YANG data modules in 714 this document are writable, and the involved subtrees that are 715 sensitive include: 717 /flexe/flexe-group/flexe-phy-list specifies a list of FlexE PHYs. 719 /flexe/flexe-group/flexe-client-list specifies a list of FlexE 720 Client, and each client is mapped to some slots in a FlexE PHY. 722 /flexcl/mac-address specifies a MAC address for a FlexE client. 724 /flexcl/group-number specifies the group number of a FlexE Group to 725 which a FlexE client belongs. 727 Write operations (e.g., edit-config) to these data nodes without 728 proper protection can have a negative effect on network operations. 729 Specifically, an inappropriate configuration of them may cause an 730 interrupt of a FlexE client flow, drop of all Ethernet frames of a 731 FlexE client, or even break down of a whole FlexE group interface. 733 6. IANA Considerations 735 It is proposed that IANA register the following URI in the "IETF XML 736 registry" [RFC3688]: 737 URI: urn:ietf:params:xml:ns:yang:ietf-flexe 738 Registrant Contact: The IESG 739 XML: N/A; the requested URI is an XML namespace 741 It is proposed that IANA register the following URI in the "IETF XML 742 registry" [RFC3688]: 743 URI: urn:ietf:params:xml:ns:yang:ietf-interfaces-flexe-client 744 Registrant Contact: The IESG 745 XML: N/A; the requested URI is an XML namespace 747 It is proposed that IANA register the following YANG module in the 748 "YANG Module Names" registry: 749 Name: ietf-flexe 750 Namespace: urn:ietf:params:xml:ns:yang:ietf-flexe 751 Prefix: flexe 752 Reference: this document 754 It is proposed that IANA register the following YANG module in the 755 "YANG Module Names" registry: 756 Name: ietf-interfaces-flexe-client 757 Namespace: urn:ietf:params:xml:ns:yang:ietf-interfaces-flexe- 758 client 759 Prefix: flexcl 760 Reference: this document 762 It is proposed that IANA register a new IANAifType TBD for 763 the interface type of Flex Ethernet group in the "IANA Interface 764 Type YANG Module" [RFC7224]. 766 It is proposed that IANA register a new IANAifType TBD for 767 the interface type of Flex Ethernet client in the "IANA Interface 768 TypeYANG Module" [RFC7224]. 770 7. References 772 7.1. Normative References 774 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 775 Requirement Levels", BCP 14, RFC 2119, March 1997 777 [RFC3688] Mealling, M., "The IETF XML Registry", RFC 3688, 778 January 2004 780 [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and Bierman, 781 A., "Network Configuration Protocol (NETCONF)", RFC 6241, 782 June 2011 784 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 785 Shell (SSH)", RFC 6242, June 2011 787 [RFC7224] Bjorklund, M., "IANA Interface Type YANG Module", RFC 7224, 788 May 2014 790 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 791 Protocol", RFC 8040, January 2017 793 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 794 2119 Key Words", BCP 14, RFC 8174, May 2017 796 [RFC8341] Bierman, A. and Bjorklund, M., "Network Configuration 797 Protocol (NETCONF) Access Control Model", RFC 8341, 798 March 2018 800 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 801 and R. Wilton, "Network Management Datastore 802 Architecture (NMDA)", RFC 8342, March 2018 804 [RFC8343] Bjorklund, M., "A YANG Data Model for Interface 805 Management", RFC 8343, March 2018 807 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 808 Version 1.3", RFC 8446, August 2018 810 7.2. Informative References 812 [FLEXE] OIF, "Flex Ethernet 2.0 Implementation Agreement", FlexE 813 2.0, June 2018 815 [FLEXE2.1]OIF, "Flex Ethernet 2.1 Implementation Agreement", FlexE 816 2.1, July 2019 818 [RFC8340] Bjorklund, M., and Berger, L., "YANG Tree Diagrams", RFC 819 8340, March 2018 821 [FLEXE-PS] Jiang, Y., Yang, F., Busi, I., Cheng., W, Wang, J., 822 "Problem Statements of FlexE Interface Management", 823 draft-jiang-ccamp-flexe-ifmps-00, Work in Progress 825 8. Acknowledgments 827 The authors would like to thank Yongjian Hu, Zitao Wang and 828 Zhongjian Zhang for discussions on YANG. 830 Authors' Addresses 832 Yuanlong Jiang 833 Huawei Technologies Co., Ltd. 834 Bantian, Longgang district 835 Shenzhen 518129, China 836 Email: jiangyuanlong@huawei.com 838 Xiang He 839 Huawei Technologies Co., Ltd. 840 Huawei Campus, No. 156 Beiqing Rd. 841 Beijing 100095 842 Email: hexiang9@huawei.com 844 Weiqiang Cheng 845 China Mobile 846 No.32 Xuanwumen West Street 847 Beijing 100053, China 848 Email: chengweiqiang@chinamobile.com 850 Junfang Wang 851 Fiberhome 852 Email: wjf@fiberhome.com 854 Yalei Han 855 Fiberhome 856 Email: ylhan@fiberhome.com