idnits 2.17.1 draft-ietf-i2rs-yang-l2-network-topology-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 5 instances of too long lines in the document, the longest one being 108 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 08, 2016) is 2848 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) == Unused Reference: 'I-D.amante-i2rs-topology-use-cases' is defined on line 897, but no explicit reference was found in the text == Unused Reference: 'I-D.medved-i2rs-topology-requirements' is defined on line 902, but no explicit reference was found in the text == Outdated reference: A later version (-20) exists of draft-ietf-i2rs-yang-network-topo-03 Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Dong 3 Internet-Draft X. Wei 4 Intended status: Standards Track Huawei Technologies 5 Expires: January 9, 2017 July 08, 2016 7 A YANG Data Model for Layer-2 Network Topologies 8 draft-ietf-i2rs-yang-l2-network-topology-03 10 Abstract 12 This document defines a YANG data model for Layer 2 network 13 topologies. 15 Requirements Language 17 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 18 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 19 document are to be interpreted as described in RFC 2119 [RFC2119]. 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 http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on January 9, 2017. 38 Copyright Notice 40 Copyright (c) 2016 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 respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 2. Layer 2 Topology Model . . . . . . . . . . . . . . . . . . . 2 57 3. Layer-2 Topology Yang Module . . . . . . . . . . . . . . . . 6 58 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 59 5. Security Considerations . . . . . . . . . . . . . . . . . . . 19 60 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19 61 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 62 7.1. Normative References . . . . . . . . . . . . . . . . . . 19 63 7.2. Informative References . . . . . . . . . . . . . . . . . 19 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 66 1. Introduction 68 [I-D.ietf-i2rs-yang-network-topo] defines the YANG [RFC6020] 69 [RFC6991] [I-D.ietf-netmod-rfc6020bis] data models of the abstract 70 (generic) network and network topology. Such models can be augmented 71 with technology-specific details to build more specific topology 72 models. 74 This document defines the YANG data model for Layer 2 network 75 topologies by augmenting the generic network and network topology 76 data models with L2 specific topology attributes. 78 2. Layer 2 Topology Model 80 The Layer 2 network topology model is designed to be generic and 81 applicable to Layer 2 networks built with different L2 technologies. 82 It can be used to describe both the physical and the logical 83 (virtual) L2 network topologies. 85 The Layer 2 topology model applies the generic network and network 86 topology models to Layer 2 network topologies, and augments the 87 generic models with information specific in Layer 2 networks. The 88 relationship between the Layer 2 topology model and the generic 89 network and network topology model is shown in the figure below: 91 +---------------------+ 92 | ietf-network | 93 +----------^----------+ 94 | 95 | 96 +---------------------+ 97 |ietf-network-topology| 98 +----------^----------+ 99 | 100 | 101 +----------^----------+ 102 | ietf-l2-topology | 103 +---------------------+ 104 Figure 1. L2-topology model structure 106 In order to represent a Layer 2 network topology, the generic network 107 and topology models are augmented with Layer-2 specific information, 108 such as the identifiers, descriptions, attributes and states of the 109 Layer-2 networks, nodes, links and termination points. Some of the 110 information may be collected via Link Layer Discovery Protocol (LLDP) 111 or other Layer-2 protocols, and some of them may be locally 112 configured. 114 The structure of "ietf-l2-topology" data model is depicted in the 115 following diagram. Brackets enclose list keys, "rw" means 116 configuration data, "ro" means operational state data, "?" designates 117 optional nodes, "*" designates nodes that can have multiple 118 instances. 120 module: ietf-l2-topology 121 augment /nw:networks/nw:network/nw:network-types: 122 +--rw l2-network! 123 augment /nw:networks/nw:network: 124 +--rw l2-network-attributes 125 +--rw name? string 126 +--rw flag* flag-type 127 augment /nw:networks/nw:network/nw:node: 128 +--rw l2-node-attributes 129 +--rw name? string 130 +--rw description? string 131 +--rw management-address* inet:ip-address 132 +--rw sys-mac-address? yang:mac-address 133 +--rw management-vid? vlan {VLAN}? 134 +--rw nick-name* trill-nickname {TRILL}? 135 +--rw vn-id* vni {VXLAN}? 136 +--rw flag* flag-type 137 augment /nw:networks/nw:network/nt:link: 138 +--rw l2-link-attributes 139 +--rw name? string 140 +--rw flag* flag-type 141 +--rw rate? decimal64 142 +--rw delay? uint32 143 +--rw srlg* uint32 144 augment /nw:networks/nw:network/nw:node/nt:termination-point: 145 +--rw l2-termination-point-attributes 146 +--rw description? string 147 +--rw maximum-frame-size? uint32 148 +--rw (l2-termination-point-type)? 149 | +--:(ethernet) 150 | | +--rw mac-address? yang:mac-address 151 | | +--rw eth-encapsulation? identityref 152 | | +--rw port-vlan-id? vlan {VLAN}? 153 | | +--rw vlan-id-name* [vlan-id] {VLAN}? 154 | | +--rw vlan-id vlan 155 | | +--rw vlan-name? string 156 | +--:(legacy) 157 | +--rw layer-2-address? yang:phys-address 158 | +--rw encapsulation? identityref 159 +--ro tp-state? enumeration 160 notifications: 161 +---n l2-node-event 162 | +--ro event-type? l2-network-event-type 163 | +--ro network-ref? -> /nw:networks/network/network-id 164 | +--ro node-ref? -> /nw:networks/network[nw:network-id = current()/../network-ref]/node/node-id 165 | +--ro l2-network! 166 | +--ro l2-node-attributes 167 | +--ro name? string 168 | +--ro description? string 169 | +--ro management-address* inet:ip-address 170 | +--ro sys-mac-address? yang:mac-address 171 | +--ro management-vid? vlan {VLAN}? 172 | +--ro nick-name* trill-nickname {TRILL}? 173 | +--ro vn-id* vni {VXLAN}? 174 | +--ro flag* flag-type 175 +---n l2-link-event 176 | +--ro event-type? l2-network-event-type 177 | +--ro network-ref? -> /nw:networks/network/network-id 178 | +--ro link-ref? -> /nw:networks/network[nw:network-id = current()/../network-ref]/nt:link/link-id 179 | +--ro l2-network! 180 | +--ro l2-link-attributes 181 | +--ro name? string 182 | +--ro flag* flag-type 183 | +--ro rate? decimal64 184 | +--ro delay? uint32 185 | +--ro srlg* uint32 186 +---n l2-termination-point-event 187 +--ro event-type? l2-network-event-type 188 +--ro network-ref? -> /nw:networks/network/network-id 189 +--ro node-ref? -> /nw:networks/network[nw:network-id = current()/../network-ref]/node/node-id 190 +--ro tp-ref? -> /nw:networks/network[nw:network-id = current()/../network-ref]/node[nw:node-id = current()/../node-ref]/nt:termination-point/tp-id 191 +--ro l2-network! 192 +--ro l2-termination-point-attributes 193 +--ro description? string 194 +--ro maximum-frame-size? uint32 195 +--ro (l2-termination-point-type)? 196 | +--:(ethernet) 197 | | +--ro mac-address? yang:mac-address 198 | | +--ro eth-encapsulation? identityref 199 | | +--ro port-vlan-id? vlan {VLAN}? 200 | | +--ro vlan-id-name* [vlan-id] {VLAN}? 201 | | +--ro vlan-id vlan 202 | | +--ro vlan-name? string 203 | +--:(legacy) 204 | +--ro layer-2-address? yang:phys-address 205 | +--ro encapsulation? identityref 206 +--ro tp-state? enumeration 208 The L2-topology module augments the generic ietf-network and ietf- 209 network-topology modules as follows: 211 o A new network type "l2-network-type" is introduced. This is 212 represented by a container object, and is inserted under the 213 "network-types" container of the generic ietf-network module in 214 [I-D.ietf-i2rs-yang-network-topo]. 216 o Additional network attributes are introduced in a grouping "l2- 217 network-attributes", which augments the "network" list of the 218 ietf-network module. The attributes include Layer-2 network name 219 and a set of flags. Each type of flag is represented by a 220 separate identity. 222 o Additional data objects for Layer-2 nodes are introduced by 223 augmenting the "node" list of the generic ietf-network module. 224 New objects include Layer-2 node identifier, description, 225 management address, and a set of flags. 227 o Additional data objects for Layer-2 termination points are 228 introduced by augmenting the "termination-point" list of the ietf- 229 network-topology module defined in 230 [I-D.ietf-i2rs-yang-network-topo]. New objects include Layer-2 231 termination point descriptions, Layer-2 termination point type 232 specific attributes and Layer-2 termination point states. 234 o Links in the ietf-network-topology module are augmented as well 235 with a set of Layer-2 parameters, allowing to associate a link 236 with a name, a set of Layer-2 link attributes and flags. 238 o The optional L2 technology specific attributes are introduced in 239 this module as Layer-2 features. 241 3. Layer-2 Topology Yang Module 243 file "ietf-l2-topology@2016-07-07.yang" 244 module ietf-l2-topology { 245 yang-version 1.1; 246 namespace "urn:ietf:params:xml:ns:yang:ietf-l2-topology"; 247 prefix "l2t"; 249 import ietf-network { 250 prefix "nw"; 251 } 253 import ietf-network-topology { 254 prefix "nt"; 255 } 257 import ietf-inet-types { 258 prefix "inet"; 259 } 261 import ietf-yang-types { 262 prefix "yang"; 263 } 265 organization 266 "IETF I2RS (Interface to the Routing System) Working Group"; 267 contact 268 "WG Web: 269 WG List: 270 WG Chair: Susan Hares 271 273 WG Chair: Russ White 274 276 Editor: Jie Dong 277 279 Editor: Xiugang Wei 280 "; 282 description 283 "This module defines a basic model for 284 the layer-2 topology of a network"; 286 revision "2016-07-07" { 287 description "Initial revision"; 288 reference "draft-ietf-i2rs-l2-network-topology-03"; 289 } 291 /* 292 * Typedefs 293 */ 295 typedef vlan { 296 type uint16 { 297 range "0..4095"; 298 } 299 description "VLAN ID"; 300 } 302 typedef trill-nickname { 303 type uint16; 304 description "TRILL Nickname"; 305 } 307 typedef vni { 308 type uint32 { 309 range "1..16777215"; 310 } 311 description "VxLAN Network Identifier"; 312 } 314 typedef flag-type { 315 type identityref { 316 base "flag-identity"; 317 } 318 description "Base type for flags"; 319 } 321 typedef l2-network-event-type { 322 type enumeration { 323 enum "add" { 324 value 0; 325 description "An L2 node or link or termination-point 326 has been added"; 327 } 328 enum "remove" { 329 value 1; 330 description "An L2 node or link or termination-point 331 has been removed"; 332 } 333 enum "update" { 334 value 2; 335 description "An L2 node or link or termination-point 336 has been updated"; 337 } 338 } 339 description "l2 network event type for notifications"; 340 } // l2-topology-event-type 342 /* 343 * Features 344 */ 346 feature VLAN { 347 description 348 "Indicates that the system supports the 349 vlan functions"; 350 } 352 feature QinQ { 353 description 354 "Indicates that the system supports the 355 qinq functions"; 356 } 358 feature PBB { 359 description 360 "Indicates that the device supports the 361 provider-backbone-bridging functions"; 362 } 364 feature VPLS { 365 description 366 "Indicates that the device supports the 367 VPLS functions"; 368 reference "RFC 4761, RFC 4762"; 369 } 371 feature TRILL { 372 description 373 "Indicates that the device supports the 374 TRILL functions"; 375 reference "RFC 6325"; 377 } 379 feature VXLAN { 380 description 381 "Indicates that the device supports the 382 VXLAN functions"; 383 reference "RFC 7348"; 384 } 386 /* 387 * Identities 388 */ 390 identity flag-identity { 391 description "Base type for flags"; 392 } 394 identity encapsulation-type { 395 description 396 "Base identity from which specific encapsulation 397 types are derived."; 398 } 400 identity eth-encapsulation-type { 401 base encapsulation-type; 402 description 403 "Base identity from which specific ethernet 404 encapsulation types are derived."; 406 } 408 identity ethernet { 409 base eth-encapsulation-type; 410 description 411 "native ethernet encapsulation"; 412 } 414 identity vlan { 415 base eth-encapsulation-type; 416 description 417 "vlan encapsulation"; 418 } 420 identity qinq { 421 base eth-encapsulation-type; 422 description 423 "qinq encapsulation"; 425 } 427 identity pbb { 428 base eth-encapsulation-type; 429 description 430 "pbb encapsulation"; 431 } 433 identity trill { 434 base eth-encapsulation-type; 435 description 436 "trill encapsulation"; 437 } 439 identity vpls { 440 base eth-encapsulation-type; 441 description 442 "vpls encapsulation"; 443 } 445 identity vxlan { 446 base eth-encapsulation-type; 447 description 448 "vxlan encapsulation"; 449 } 451 identity frame-relay { 452 base encapsulation-type; 453 description 454 "Frame Relay encapsulation"; 455 } 457 identity ppp { 458 base encapsulation-type; 459 description 460 "PPP encapsulation"; 461 } 463 identity hdlc { 464 base encapsulation-type; 465 description 466 "HDLC encapsulation"; 467 } 469 identity atm { 470 base encapsulation-type; 471 description 472 "Base identity from which specific ATM 473 encapsulation types are derived."; 475 } 477 identity pwe3 { 478 base encapsulation-type; 479 description 480 "Base identity from which specific pw 481 encapsulation types are derived."; 482 } 484 /* 485 * Groupings 486 */ 488 grouping l2-network-type { 489 description "Identify the topology type to be L2."; 490 container l2-network { 491 presence "indicates L2 Network"; 492 description 493 "The presence of the container node indicates 494 L2 Topology"; 495 } 496 } 498 grouping l2-network-attributes { 499 description "L2 Topology scope attributes"; 500 container l2-network-attributes { 501 description "Containing L2 network attributes"; 502 leaf name { 503 type string; 504 description "Name of the L2 network"; 505 } 507 leaf-list flag { 508 type flag-type; 509 description "L2 network flags"; 510 } 511 } 512 } 514 grouping l2-node-attributes { 515 description "L2 node attributes"; 516 container l2-node-attributes { 517 description "Containing L2 node attributes"; 518 leaf name { 519 type string; 520 description "Node name"; 521 } 522 leaf description { 523 type string; 524 description "Node description"; 525 } 526 leaf-list management-address { 527 type inet:ip-address; 528 description "System management address"; 529 } 530 leaf sys-mac-address { 531 type yang:mac-address; 532 description "System MAC-address"; 533 } 534 leaf management-vid { 535 if-feature VLAN; 536 type vlan; 537 description "System management VID"; 538 } 539 leaf-list nick-name { 540 if-feature TRILL; 541 type trill-nickname; 542 description "Nickname of the RBridge"; 543 } 544 leaf-list vn-id { 545 if-feature VXLAN; 546 type vni; 547 description "VNI of the VxLAN"; 548 } 549 leaf-list flag { 550 type flag-type; 551 description "Node operational flags"; 552 } 553 } 554 } // grouping l2-node-attributes 556 grouping l2-link-attributes { 557 description "L2 link attributes"; 558 container l2-link-attributes { 559 description "Containing L2 link attributes"; 560 leaf name { 561 type string; 562 description "Link name"; 563 } 564 leaf-list flag { 565 type flag-type; 566 description "Link flags"; 568 } 569 leaf rate { 570 type decimal64 { 571 fraction-digits 2; 572 } 573 description "Link rate"; 575 } 576 leaf delay { 577 type uint32; 578 description "Link delay in microseconds"; 579 } 580 leaf-list srlg { 581 type uint32; 582 description 583 "List of Shared Risk Link Groups 584 this link belongs to."; 585 } 586 } 587 } // grouping l2-link-attributes 589 grouping l2-termination-point-attributes { 590 description "L2 termination point attributes"; 591 container l2-termination-point-attributes { 592 description "Containing L2 TP attributes"; 593 leaf description { 594 type string; 595 description "Port description"; 596 } 598 leaf maximum-frame-size { 599 type uint32; 600 description "Maximum frame size"; 601 } 603 choice l2-termination-point-type { 604 description 605 "Indicates termination-point type 606 specific attributes"; 607 case ethernet { 608 leaf mac-address { 609 type yang:mac-address; 610 description "Interface MAC address"; 611 } 613 leaf eth-encapsulation { 614 type identityref { 615 base eth-encapsulation-type; 617 } 618 description 619 "Encapsulation type of this 620 ternimation point."; 621 } 623 leaf port-vlan-id { 624 if-feature VLAN; 625 type vlan; 626 description "Port VLAN ID"; 627 } 629 list vlan-id-name { 630 if-feature VLAN; 631 key "vlan-id"; 632 description "Interface configured VLANs"; 633 leaf vlan-id { 634 type vlan; 635 description "VLAN ID"; 636 } 637 leaf vlan-name { 638 type string; 639 description "VLAN Name"; 640 } 641 } 642 } //case ethernet 644 case legacy { 645 leaf layer-2-address { 646 type yang:phys-address; 647 description "Interface Layer 2 address"; 648 } 650 leaf encapsulation { 651 type identityref { 652 base encapsulation-type; 653 } 654 description 655 "Encapsulation type of this termination point."; 656 } 657 } //case legacy 659 } //choice termination-point-type 661 leaf tp-state { 662 type enumeration { 663 enum in-use { 664 value 0; 665 description 666 "the termination point is in forwarding state"; 667 } 668 enum blocking { 669 value 1; 670 description 671 "the termination point is in blocking state"; 672 } 673 enum down { 674 value 2; 675 description 676 "the termination point is in down state"; 677 } 678 enum others { 679 value 3; 680 description 681 "the termination point is in other state"; 682 } 683 } 684 config false; 685 description "State of the termination point"; 686 } 687 } 688 } // grouping l2-termination-point-attributes 690 /*** grouping of network/node/link/tp leaf-refs ***/ 692 grouping network-ref { 693 description 694 "Grouping for an absolute reference to a network topology 695 instance."; 696 leaf network-ref { 697 type leafref { 698 path "/nw:networks/nw:network/nw:network-id"; 699 } 700 description 701 "An absolute reference to a network topology instance."; 702 } 703 } 705 grouping link-ref { 706 description 707 "Grouping for an absolute reference to a link instance."; 708 uses network-ref; 709 leaf link-ref { 710 type leafref { 711 path "/nw:networks/nw:network" 712 +"[nw:network-id = current()/../network-ref]" 713 +"/nt:link/nt:link-id"; 714 } 715 description 716 "An absolute reference to a link instance."; 717 } 718 } 720 grouping node-ref { 721 description 722 "Grouping for an absolute reference to a node instance."; 723 uses network-ref; 724 leaf node-ref { 725 type leafref { 726 path "/nw:networks/nw:network" 727 +"[nw:network-id = current()/../network-ref]" 728 +"/nw:node/nw:node-id"; 729 } 730 description 731 "An absolute reference to a node instance."; 732 } 733 } 735 grouping tp-ref { 736 description 737 "Grouping for an absolute reference to a termination point."; 738 uses node-ref; 739 leaf tp-ref { 740 type leafref { 741 path "/nw:networks/nw:network" 742 +"[nw:network-id = current()/../network-ref]" 743 +"/nw:node[nw:node-id = current()/../node-ref]" 744 +"/nt:termination-point/nt:tp-id"; 745 } 746 description 747 "Grouping for an absolute reference to a TP."; 748 } 749 } 751 /* 752 * Data nodes 753 */ 755 augment "/nw:networks/nw:network/nw:network-types" { 756 description 757 "Introduce new network type for L2 topology"; 758 uses l2-network-type; 760 } 762 augment "/nw:networks/nw:network" { 763 when "/nw:networks/nw:network/nw:network-types/l2-network" { 764 description 765 "Augmentation parameters apply only for networks 766 with L2 topology"; 767 } 768 description 769 "Configuration parameters for the L2 network 770 as a whole"; 771 uses l2-network-attributes; 772 } 774 augment "/nw:networks/nw:network/nw:node" { 775 when "/nw:networks/nw:network/nw:network-types/l2-network" { 776 description 777 "Augmentation parameters apply only for networks 778 with L2 topology"; 779 } 780 description 781 "Configuration parameters for L2 at the node 782 level"; 783 uses l2-node-attributes; 784 } 786 augment "/nw:networks/nw:network/nt:link" { 787 when "/nw:networks/nw:network/nw:network-types/l2-network" { 788 description 789 "Augmentation parameters apply only for networks 790 with L2 topology"; 791 } 792 description "Augment L2 topology link information"; 793 uses l2-link-attributes; 794 } 796 augment "/nw:networks/nw:network/nw:node/nt:termination-point" { 797 when "/nw:networks/nw:network/nw:network-types/l2-network" { 798 description 799 "Augmentation parameters apply only for networks 800 with L2 topology"; 801 } 802 description 803 "Augment L2 topology termination point information"; 804 uses l2-termination-point-attributes; 805 } 807 /* 808 * Notifications 809 */ 811 notification l2-node-event { 812 description "Notification event for L2 node"; 813 leaf event-type { 814 type l2-network-event-type; 815 description "Event type"; 816 } 817 uses node-ref; 818 uses l2-network-type; 819 uses l2-node-attributes; 820 } 822 notification l2-link-event { 823 description "Notification event for L2 link"; 824 leaf event-type { 825 type l2-network-event-type; 826 description "Event type"; 827 } 828 uses link-ref; 829 uses l2-network-type; 830 uses l2-link-attributes; 831 } 833 notification l2-termination-point-event { 834 description "Notification event for L2 termination point"; 835 leaf event-type { 836 type l2-network-event-type; 837 description "Event type"; 838 } 839 uses tp-ref; 840 uses l2-network-type; 841 uses l2-termination-point-attributes; 842 } 844 } // module l2-topology 845 847 4. IANA Considerations 849 This document makes no request of IANA. 851 Note to RFC Editor: this section may be removed on publication as an 852 RFC. 854 5. Security Considerations 856 The transport protocol used for sending the topology data MUST 857 support authentication and SHOULD support encryption. The data-model 858 by itself does not create any security implications. 860 6. Acknowledgements 862 The authors would like to acknowledge the comments and suggestions 863 received from Susan Hares, Alia Atlas, Juergen Schoenwaelder, Mach 864 Chen, Alexander Clemm and Sriganesh Kini. 866 7. References 868 7.1. Normative References 870 [I-D.ietf-i2rs-yang-network-topo] 871 Clemm, A., Medved, J., Varga, R., Tkacik, T., Bahadur, N., 872 Ananthakrishnan, H., and X. Liu, "A Data Model for Network 873 Topologies", draft-ietf-i2rs-yang-network-topo-03 (work in 874 progress), June 2016. 876 [I-D.ietf-netmod-rfc6020bis] 877 Bjorklund, M., "The YANG 1.1 Data Modeling Language", 878 draft-ietf-netmod-rfc6020bis-14 (work in progress), June 879 2016. 881 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 882 Requirement Levels", BCP 14, RFC 2119, 883 DOI 10.17487/RFC2119, March 1997, 884 . 886 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 887 the Network Configuration Protocol (NETCONF)", RFC 6020, 888 DOI 10.17487/RFC6020, October 2010, 889 . 891 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 892 RFC 6991, DOI 10.17487/RFC6991, July 2013, 893 . 895 7.2. Informative References 897 [I-D.amante-i2rs-topology-use-cases] 898 Medved, J., Previdi, S., Lopez, V., and S. Amante, 899 "Topology API Use Cases", draft-amante-i2rs-topology-use- 900 cases-01 (work in progress), October 2013. 902 [I-D.medved-i2rs-topology-requirements] 903 Medved, J., Previdi, S., Gredler, H., Nadeau, T., and S. 904 Amante, "Topology API Requirements", draft-medved-i2rs- 905 topology-requirements-00 (work in progress), February 906 2013. 908 Authors' Addresses 910 Jie Dong 911 Huawei Technologies 912 Huawei Campus, No. 156 Beiqing Rd. 913 Beijing 100095 914 China 916 Email: jie.dong@huawei.com 918 Xiugang Wei 919 Huawei Technologies 920 Huawei Campus, No. 156 Beiqing Rd. 921 Beijing 100095 922 China 924 Email: weixiugang@huawei.com