idnits 2.17.1 draft-acee-rtgwg-yang-rib-extend-10.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 == Line 788 has weird spacing: '...-family ide...' == Line 822 has weird spacing: '...rotocol ide...' == Line 832 has weird spacing: '...ro type ide...' == Line 833 has weird spacing: '...ro name str...' == Line 837 has weird spacing: '...-family ide...' == (1 more instance...) == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (March 4, 2019) is 1873 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) ** Obsolete normative reference: RFC 5246 (Obsoleted by RFC 8446) Summary: 1 error (**), 0 flaws (~~), 8 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Lindem 3 Internet-Draft Cisco Systems 4 Intended status: Standards Track Y. Qu 5 Expires: September 5, 2019 Huawei 6 March 4, 2019 8 RIB YANG Data Model 9 draft-acee-rtgwg-yang-rib-extend-10.txt 11 Abstract 13 The Routing Information Base (RIB) is a list of routes and their 14 corresponding administrative data and operational state. 16 RFC 8349 defines the basic building blocks for RIB, and this model 17 augments it to support multiple next-hops (aka, paths) for each route 18 as well as additional attributes. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at https://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on September 5, 2019. 37 Copyright Notice 39 Copyright (c) 2019 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (https://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. Terminology and Notation . . . . . . . . . . . . . . . . . . 3 56 2.1. Glossary of New Terms . . . . . . . . . . . . . . . . . . 4 57 2.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 4 58 2.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4 59 3. Design of the Model . . . . . . . . . . . . . . . . . . . . . 4 60 3.1. RIB Tags and Preference . . . . . . . . . . . . . . . . . 5 61 3.2. Multiple next-hops . . . . . . . . . . . . . . . . . . . 5 62 3.3. Repair path . . . . . . . . . . . . . . . . . . . . . . . 5 63 4. RIB Model Tree . . . . . . . . . . . . . . . . . . . . . . . 5 64 5. RIB YANG Model . . . . . . . . . . . . . . . . . . . . . . . 7 65 6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 66 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 67 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 68 8.1. Normative References . . . . . . . . . . . . . . . . . . 15 69 8.2. Informative References . . . . . . . . . . . . . . . . . 16 70 Appendix A. Combined Tree Diagram . . . . . . . . . . . . . . . 17 71 Appendix B. ietf-rib-extension.yang examples . . . . . . . . . . 20 72 Appendix C. Acknowledgments . . . . . . . . . . . . . . . . . . 20 73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 75 1. Introduction 77 This document defines a YANG, [RFC6020][RFC7950], data model which 78 extends the generic data model for RIB by augmenting the ietf-routing 79 model as defined in [RFC8349]. 81 RIB is a collection of best routes from all routing protocols. 82 Within a protocol routes are selected based on the metrics in use by 83 that protocol, and the protocol install its best routes to RIB. RIB 84 selects the best route by comparing the route preference (aka, 85 administrative distance) of the associated protocol. 87 The augmentations described herein extend the RIB to support multiple 88 paths per route, route metrics, and administrative tags. 90 The YANG modules in this document conform to the Network Management 91 Datastore Architecture (NMDA) [RFC8342]. 93 2. Terminology and Notation 95 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 96 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 97 "OPTIONAL" in this document are to be interpreted as described in BCP 98 14 [RFC2119] [RFC8174] when, and only when, they appear in all 99 capitals, as shown here. 101 The following terms are defined in [RFC8342]: 103 o client 105 o server 107 o configuration 109 o system state 111 o operational state 113 o intended configuration 115 The following terms are defined in [RFC7950]: 117 o action 119 o augment 121 o container 123 o container with presence 125 o data model 127 o data node 129 o feature 131 o leaf 133 o list 135 o mandatory node 137 o module 139 o schema tree 140 o RPC (Remote Procedure Call) operation 142 2.1. Glossary of New Terms 144 Routing Information Base (RIB): An object containing a list of 145 routes, together with other information. See [RFC8349] 146 Section 5.2 for details. 148 2.2. Tree Diagrams 150 Tree diagrams used in this document follow the notation defined in 151 [RFC8340]. 153 2.3. Prefixes in Data Node Names 155 In this document, names of data nodes, actions, and other data model 156 objects are often used without a prefix, as long as it is clear from 157 the context in which YANG module each name is defined. Otherwise, 158 names are prefixed using the standard prefix associated with the 159 corresponding YANG module, as shown in Table 1. 161 +--------+---------------------------+-----------+ 162 | Prefix | YANG module | Reference | 163 +--------+---------------------------+-----------+ 164 | if | ietf-interfaces | [RFC8343] | 165 | | | | 166 | rt | ietf-routing | [RFC8349] | 167 | | | | 168 | v4ur | ietf-ipv4-unicast-routing | [RFC8349] | 169 | | | | 170 | v6ur | ietf-ipv6-unicast-routing | [RFC8349] | 171 | | | | 172 | inet | ietf-inet-types | [RFC6991] | 173 +--------+---------------------------+-----------+ 175 Table 1: Prefixes and Corresponding YANG Modules 177 3. Design of the Model 179 The YANG definitions in this document augment the ietf-routing model 180 defined in [RFC8349], which provides a basis for routing system data 181 model development. Together with modules defined in [RFC8349], a 182 generic RIB Yang model is defined to implement and monitor RIB. 184 The models in [RFC8349] also define the basic configuration and 185 operational state for both IPv4 and IPv6 static routes and this 186 document also provides augmentations for static routes to support 187 multiple next-hop and more next-hop attributes. 189 3.1. RIB Tags and Preference 191 Individual routes tags will be supported at both the route and next- 192 hop level. A preference per next-hop is also supported for selection 193 of the most preferred reachable static route. 195 3.2. Multiple next-hops 197 Both Ipv4 and IPv6 static route configuration defined in [RFC8349] 198 have been augmented with a multi-next-hop option. 200 A static route/prefix can be configured to have multiple next-hops, 201 each with their own tag and route preference. 203 In RIB, a route may have multiple next-hops. They can be either 204 equal cost multiple paths (ECMP), or they may have different metrics. 206 3.3. Repair path 208 The loop-free alternate (LFA) Fast Reroute (FRR) pre-computes repair 209 paths by routing protocols, and RIB stores the best repair path. 211 A repair path is augmented in RIB operation state for each path. 213 4. RIB Model Tree 215 The tree associated with the "ietf-rib-extension" module follows. 216 The meaning of the symbols can be found in [RFC8340]. The ietf- 217 routing.yang tree with the augmentations herein is included in 218 Appendix A. 220 augment /rt:routing/rt:control-plane-protocols 221 /rt:control-plane-protocol/rt:static-routes/v4ur:ipv4 222 /v4ur:route/v4ur:next-hop/v4ur:next-hop-options 223 /v4ur:simple-next-hop: 224 +--rw preference? uint32 225 +--rw tag? uint32 226 +--rw application-tag? uint32 227 augment /rt:routing/rt:control-plane-protocols 228 /rt:control-plane-protocol/rt:static-routes/v4ur:ipv4 229 /v4ur:route/v4ur:next-hop/v4ur:next-hop-options 230 /v4ur:next-hop-list/v4ur:next-hop-list/v4ur:next-hop: 231 +--rw preference? uint32 232 +--rw tag? uint32 233 +--rw application-tag? uint32 234 augment /rt:routing/rt:control-plane-protocols 235 /rt:control-plane-protocol/rt:static-routes/v6ur:ipv6 236 /v6ur:route/v6ur:next-hop/v6ur:next-hop-options 237 /v6ur:simple-next-hop: 238 +--rw preference? uint32 239 +--rw tag? uint32 240 +--rw application-tag? uint32 241 augment /rt:routing/rt:control-plane-protocols 242 /rt:control-plane-protocol/rt:static-routes/v6ur:ipv6 243 /v6ur:route/v6ur:next-hop/v6ur:next-hop-options 244 /v6ur:next-hop-list/v6ur:next-hop-list/v6ur:next-hop: 245 +--rw preference? uint32 246 +--rw tag? uint32 247 +--rw application-tag? uint32 248 augment /rt:routing/rt:ribs/rt:rib: 249 +--ro rib-summary-statistics 250 +--ro total-routes? uint32 251 +--ro total-active-routes? uint32 252 +--ro total-route-memory? uint64 253 +--ro protocol-rib-statistics* [] 254 +--ro rib-protocol? identityref 255 +--ro protocol-total-routes? uint32 256 +--ro protocol-active-routes? uint32 257 +--ro protocol-route-memory? uint64 258 augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route: 259 +--ro metric? uint32 260 +--ro tag? uint32 261 +--ro application-tag? uint32 262 augment /rt:routing/rt:ribs/rt:rib/rt:routes: 263 +--ro repair-route* [id] 264 +--ro id string 265 +--ro next-hop 266 | +--ro outgoing-interface? if:interface-state-ref 267 | +--ro next-hop-address? inet:ip-address 268 +--ro metric? uint32 269 augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route 270 /rt:next-hop/rt:next-hop-options/rt:simple-next-hop: 271 +--ro repair-path? 272 -> /rt:routing/ribs/rib/routes/repair-route/id 273 augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route 274 /rt:next-hop/rt:next-hop-options/rt:special-next-hop: 275 +--ro repair-path? 276 -> /rt:routing/ribs/rib/routes/repair-route/id 277 augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route 278 /rt:next-hop/rt:next-hop-options/rt:next-hop-list 279 /rt:next-hop-list/rt:next-hop: 280 +--ro repair-path? 281 -> /rt:routing/ribs/rib/routes/repair-route/id 283 5. RIB YANG Model 285 file "ietf-rib-extension@2019-03-01.yang" 286 module ietf-rib-extension { 287 yang-version "1.1"; 288 namespace "urn:ietf:params:xml:ns:yang:ietf-rib-extension"; 290 prefix rib-ext; 292 import ietf-inet-types { 293 prefix "inet"; 294 } 296 import ietf-interfaces { 297 prefix "if"; 298 } 300 import ietf-routing { 301 prefix "rt"; 302 } 304 import ietf-ipv4-unicast-routing { 305 prefix "v4ur"; 306 } 308 import ietf-ipv6-unicast-routing { 309 prefix "v6ur"; 310 } 312 organization 313 "IETF RTGWG - Routing Working Group"; 315 contact 316 "WG Web: 317 WG List: 319 Author: Acee Lindem 320 321 Author: Yingzhen Qu 322 "; 324 description 325 "This YANG module extends the generic data model for 326 RIB by augmenting the ietf-netmod-routing-cfg 327 model. It is intended that the module will be extended 328 by vendors to define vendor-specific RIB parameters. 330 This YANG model conforms to the Network Management 331 Datastore Architecture (NDMA) as described in RFC 8342. 333 Copyright (c) 2018 IETF Trust and the persons identified as 334 authors of the code. All rights reserved. 336 Redistribution and use in source and binary forms, with or 337 without modification, is permitted pursuant to, and subject 338 to the license terms contained in, the Simplified BSD License 339 set forth in Section 4.c of the IETF Trust's Legal Provisions 340 Relating to IETF Documents 341 (http://trustee.ietf.org/license-info). 343 This version of this YANG module is part of RFC XXXX; 344 see the RFC itself for full legal notices."; 346 revision 2019-03-01 { 347 description 348 "Initial RFC Version"; 349 reference 350 "RFC XXXX: A YANG Data Model for RIB Extensions."; 351 } 353 /* Groupings */ 354 grouping rib-statistics { 355 description "Statistics grouping used for RIB augmentation"; 356 container rib-summary-statistics { 357 config false; 358 description "Container for RIB statistics"; 359 leaf total-routes { 360 type uint32; 361 description 362 "Total routes in the RIB from all protocols"; 363 } 364 leaf total-active-routes { 365 type uint32; 366 description 367 "Total active routes in the RIB"; 368 } 369 leaf total-route-memory { 370 type uint64; 371 description 372 "Total memory for all routes in the RIB from all 373 protocol clients"; 374 } 375 list protocol-rib-statistics { 376 description "List protocol statistics"; 377 leaf rib-protocol { 378 type identityref { 379 base rt:routing-protocol; 380 } 381 description "Routing protocol for statistics"; 382 } 383 leaf protocol-total-routes { 384 type uint32; 385 description 386 "Total number routes for protocol in the RIB"; 387 } 388 leaf protocol-active-routes { 389 type uint32; 390 description 391 "Number active routes for protocol in the RIB"; 392 } 393 leaf protocol-route-memory { 394 type uint64; 395 description 396 "Total memory for all routes in the RIB for protocol"; 397 } 398 } 399 } 400 } 402 grouping next-hop { 403 description 404 "Next-hop grouping"; 405 leaf interface { 406 type if:interface-ref; 407 description 408 "Outgoing interface"; 409 } 410 leaf address { 411 type inet:ip-address; 412 description 413 "IPv4 or IPv6 Address of the next-hop"; 414 } 415 } 417 grouping attributes { 418 description 419 "Common attributes applicable to all paths"; 420 leaf metric { 421 type uint32; 422 description "Route metric"; 423 } 424 leaf tag { 425 type uint32; 426 description "Route tag"; 428 } 429 leaf application-tag { 430 type uint32; 431 description "Additional Application-Specific Route tag"; 432 } 433 } 434 grouping path-attribute { 435 description 436 "Path attribute grouping"; 437 leaf repair-path { 438 type leafref { 439 path "/rt:routing/rt:ribs/rt:rib/" 440 + "rt:routes/repair-route/id"; 441 } 442 description 443 "IP Fast ReRoute (IPFRR) repair path, use a path 444 from repair-route list"; 445 } 446 } 448 augment "/rt:routing/rt:control-plane-protocols/" 449 + "rt:control-plane-protocol/rt:static-routes/v4ur:ipv4/" 450 + "v4ur:route/v4ur:next-hop/v4ur:next-hop-options/" 451 + "v4ur:simple-next-hop" 452 { 453 description 454 "Augment 'simple-next-hop' case in IPv4 unicast route."; 455 leaf preference { 456 type uint32; 457 default "1"; 458 description "Route preference - Used to select among multiple 459 static routes with a lower preference next-hop 460 preferred and equal preference paths yielding 461 Equal Cost Multi-Path (ECMP)."; 462 } 463 leaf tag { 464 type uint32; 465 default "0"; 466 description "Route tag"; 467 } 468 leaf application-tag { 469 type uint32; 470 description "Additional Application-Specific Route tag"; 471 } 472 } 474 augment "/rt:routing/rt:control-plane-protocols/" 475 + "rt:control-plane-protocol/rt:static-routes/v4ur:ipv4/" 476 + "v4ur:route/v4ur:next-hop/v4ur:next-hop-options/" 477 + "v4ur:next-hop-list/v4ur:next-hop-list/v4ur:next-hop" 478 { 479 description 480 "Augment static route configuration 'next-hop-list'."; 482 leaf preference { 483 type uint32; 484 default "1"; 485 description "Route preference - Used to select among multiple 486 static routes with a lower preference next-hop 487 preferred and equal preference paths yielding 488 Equal Cost Multi-Path (ECMP)."; 489 } 490 leaf tag { 491 type uint32; 492 default "0"; 493 description "Route tag"; 494 } 495 leaf application-tag { 496 type uint32; 497 description "Additional Application-Specific Route tag"; 498 } 499 } 501 augment "/rt:routing/rt:control-plane-protocols/" 502 + "rt:control-plane-protocol/rt:static-routes/v6ur:ipv6/" 503 + "v6ur:route/v6ur:next-hop/v6ur:next-hop-options/" 504 + "v6ur:simple-next-hop" 505 { 506 description 507 "Augment 'simple-next-hop' case in IPv6 unicast route."; 508 leaf preference { 509 type uint32; 510 default "1"; 511 description "Route preference - Used to select among multiple 512 static routes with a lower preference next-hop 513 preferred and equal preference paths yielding 514 Equal Cost Multi-Path (ECMP)."; 515 } 516 leaf tag { 517 type uint32; 518 default "0"; 519 description "Route tag"; 520 } 521 leaf application-tag { 522 type uint32; 523 description "Additional Application-Specific Route tag"; 525 } 526 } 528 augment "/rt:routing/rt:control-plane-protocols/" 529 + "rt:control-plane-protocol/rt:static-routes/v6ur:ipv6/" 530 + "v6ur:route/v6ur:next-hop/v6ur:next-hop-options/" 531 + "v6ur:next-hop-list/v6ur:next-hop-list/v6ur:next-hop" 532 { 533 description 534 "Augment static route configuration 'next-hop-list'."; 536 leaf preference { 537 type uint32; 538 default "1"; 539 description "Route preference - Used to select among multiple 540 static routes with a lower preference next-hop 541 preferred and equal preference paths yielding 542 Equal Cost Multi-Path (ECMP)."; 543 } 544 leaf tag { 545 type uint32; 546 default "0"; 547 description "Route tag"; 548 } 549 leaf application-tag { 550 type uint32; 551 description "Additional Application-Specific Route tag"; 552 } 553 } 555 augment "/rt:routing/rt:ribs/rt:rib" 556 { 557 description "Augment a RIB with statistics"; 558 uses rib-statistics; 559 } 561 augment "/rt:routing/rt:ribs/rt:rib/" 562 + "rt:routes/rt:route" 563 { 564 description 565 "Augment a route in RIB with tag."; 566 uses attributes; 567 } 569 augment "/rt:routing/rt:ribs/rt:rib/" 570 + "rt:routes" 571 { 572 description 573 "Augment a route with a list of repair-paths."; 574 list repair-route { 575 key "id"; 576 description 577 "A repair-path entry, which can be referenced 578 by a repair-path."; 579 leaf id { 580 type string; 581 description 582 "A unique identifier."; 583 } 585 container next-hop { 586 description 587 "Route's next-hop attribute."; 588 leaf outgoing-interface { 589 type if:interface-state-ref; 590 description 591 "Name of the outgoing interface."; 592 } 593 leaf next-hop-address { 594 type inet:ip-address; 595 description 596 "IP address of the next hop."; 597 } 598 } 599 leaf metric { 600 type uint32; 601 description "Route metric"; 602 } 603 } 604 } 606 augment "/rt:routing/rt:ribs/rt:rib/" 607 + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/" 608 + "rt:simple-next-hop" 609 { 610 description 611 "Add more parameters to a path."; 612 uses path-attribute; 613 } 615 augment "/rt:routing/rt:ribs/rt:rib/" 616 + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/" 617 + "rt:special-next-hop" 618 { 619 description 620 "Add more parameters to a path."; 622 uses path-attribute; 623 } 625 augment "/rt:routing/rt:ribs/rt:rib/" 626 + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/" 627 + "rt:next-hop-list/rt:next-hop-list/rt:next-hop" 628 { 629 description 630 "This case augments the 'next-hop-options' in the routing 631 model."; 632 uses path-attribute; 633 } 634 } 635 637 6. Security Considerations 639 The YANG modules specified in this document define a schema for data 640 that is designed to be accessed via network management protocols such 641 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 642 is the secure transport layer, and the mandatory-to-implement secure 643 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 644 is HTTPS, and the mandatory-to-implement secure transport is TLS 645 [RFC5246]. 647 The NETCONF access control model [RFC8341] provides the means to 648 restrict access for particular NETCONF or RESTCONF users to a pre- 649 configured subset of all available NETCONF or RESTCONF protocol 650 operations and content. 652 There are a number of data nodes defined in ietf-rib-extensions.yang 653 module that are writable/creatable/deletable (i.e., config true, 654 which is the default). These data nodes may be considered sensitive 655 or vulnerable in some network environments. Write operations (e.g., 656 edit-config) to these data nodes without proper protection can have a 657 negative effect on network operations. For these augmentations to 658 ietf-routing.yang, the abiliy to delete, add, and modify IPv4 and 659 IPv6 static routes would allow traffic to be misrouted. 661 Some of the readable data nodes in the ietf-rib-extensions.yang 662 module may be considered sensitive or vulnerable in some network 663 environments. It is thus important to control read access (e.g., via 664 get, get-config, or notification) to these data nodes. The exposure 665 of the Routing Information Base (RIB) will expose the routing 666 topology of the network. This may be undesirable since both due to 667 the fact that exposure may facilitate other attacks. Additionally, 668 network operators may consider their topologies to be sensitive 669 confidential data. 671 All the security considerations for [RFC8349] writable and readable 672 data nodes apply to the augmentations described herein. 674 7. IANA Considerations 676 This document registers a URI in the IETF XML registry 677 [XML-REGISTRY]. Following the format in [RFC3688], the following 678 registration is requested to be made: 680 URI: urn:ietf:params:xml:ns:yang:ietf-rib-extension 682 Registrant Contact: The IESG. 684 XML: N/A, the requested URI is an XML namespace. 686 This document registers a YANG module in the YANG Module Names 687 registry [RFC6020]. 689 name: ietf-acl namespace: urn:ietf:params:xml:ns:yang:ietf-rib- 690 extension prefix: ietf-rib-ext reference: RFC XXXX 692 8. References 694 8.1. Normative References 696 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 697 Requirement Levels", BCP 14, RFC 2119, 698 DOI 10.17487/RFC2119, March 1997, 699 . 701 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 702 DOI 10.17487/RFC3688, January 2004, 703 . 705 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 706 (TLS) Protocol Version 1.2", RFC 5246, 707 DOI 10.17487/RFC5246, August 2008, 708 . 710 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 711 the Network Configuration Protocol (NETCONF)", RFC 6020, 712 DOI 10.17487/RFC6020, October 2010, 713 . 715 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 716 and A. Bierman, Ed., "Network Configuration Protocol 717 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 718 . 720 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 721 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 722 . 724 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 725 RFC 6991, DOI 10.17487/RFC6991, July 2013, 726 . 728 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 729 RFC 7950, DOI 10.17487/RFC7950, August 2016, 730 . 732 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 733 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 734 . 736 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 737 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 738 May 2017, . 740 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 741 Access Control Model", STD 91, RFC 8341, 742 DOI 10.17487/RFC8341, March 2018, 743 . 745 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 746 and R. Wilton, "Network Management Datastore Architecture 747 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 748 . 750 [RFC8343] Bjorklund, M., "A YANG Data Model for Interface 751 Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, 752 . 754 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 755 Routing Management (NMDA Version)", RFC 8349, 756 DOI 10.17487/RFC8349, March 2018, 757 . 759 8.2. Informative References 761 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 762 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 763 . 765 [XML-REGISTRY] 766 Mealling, M., "The IETF XML Registry", BCP 81, January 767 2004. 769 Appendix A. Combined Tree Diagram 771 This appendix includes the combined ietf-routing.yang and ietf-rib- 772 extensions.yang tree diagram. 774 module: ietf-routing 775 +--rw routing 776 | +--rw router-id? yang:dotted-quad 777 | +--ro interfaces 778 | | +--ro interface* if:interface-ref 779 | +--rw control-plane-protocols 780 | | +--rw control-plane-protocol* [type name] 781 | | +--rw type identityref 782 | | +--rw name string 783 | | +--rw description? string 784 | | +--rw static-routes 785 | +--rw ribs 786 | +--rw rib* [name] 787 | +--rw name string 788 | +--rw address-family identityref 789 | +--ro default-rib? boolean {multiple-ribs}? 790 | +--ro routes 791 | | +--ro route* [] 792 | | +--ro route-preference? route-preference 793 | | +--ro next-hop 794 | | | +--ro (next-hop-options) 795 | | | +--:(simple-next-hop) 796 | | | | +--ro outgoing-interface? if:interface-ref 797 | | | +--:(special-next-hop) 798 | | | | +--ro special-next-hop? enumeration 799 | | | +--:(next-hop-list) 800 | | | +--ro next-hop-list 801 | | | +--ro next-hop* [] 802 | | | +--ro outgoing-interface? 803 | | | if:interface-ref 804 | | +--ro source-protocol identityref 805 | | +--ro active? empty 806 | | +--ro last-updated? yang:date-and-time 807 | +---x active-route 808 | | +--ro output 809 | | +--ro route 810 | | +--ro next-hop 811 | | | +--ro (next-hop-options) 812 | | | +--:(simple-next-hop) 813 | | | | +--ro outgoing-interface? 814 | | | | if:interface-ref 815 | | | +--:(special-next-hop) 816 | | | | +--ro special-next-hop? enumeration 817 | | | +--:(next-hop-list) 818 | | | +--ro next-hop-list 819 | | | +--ro next-hop* [] 820 | | | +--ro outgoing-interface? 821 | | | if:interface-ref 822 | | +--ro source-protocol identityref 823 | | +--ro active? empty 824 | | +--ro last-updated? yang:date-and-time 825 | +--rw description? string 826 o--ro routing-state 827 +--ro router-id? yang:dotted-quad 828 o--ro interfaces 829 | o--ro interface* if:interface-state-ref 830 o--ro control-plane-protocols 831 | o--ro control-plane-protocol* [type name] 832 | o--ro type identityref 833 | o--ro name string 834 o--ro ribs 835 o--ro rib* [name] 836 o--ro name string 837 +--ro address-family identityref 838 o--ro default-rib? boolean {multiple-ribs}? 839 o--ro routes 840 | o--ro route* [] 841 | o--ro route-preference? route-preference 842 | o--ro next-hop 843 | | +--ro (next-hop-options) 844 | | +--:(simple-next-hop) 845 | | | +--ro outgoing-interface? if:interface-ref 846 | | +--:(special-next-hop) 847 | | | +--ro special-next-hop? enumeration 848 | | +--:(next-hop-list) 849 | | +--ro next-hop-list 850 | | +--ro next-hop* [] 851 | | +--ro outgoing-interface? 852 | | if:interface-ref 853 | +--ro source-protocol identityref 854 | +--ro active? empty 855 | +--ro last-updated? yang:date-and-time 856 o---x active-route 857 +--ro output 858 o--ro route 859 o--ro next-hop 860 | +--ro (next-hop-options) 861 | +--:(simple-next-hop) 862 | | +--ro outgoing-interface? 863 | | if:interface-ref 864 | +--:(special-next-hop) 865 | | +--ro special-next-hop? enumeration 866 | +--:(next-hop-list) 867 | +--ro next-hop-list 868 | +--ro next-hop* [] 869 | +--ro outgoing-interface? 870 | if:interface-ref 871 +--ro source-protocol identityref 872 +--ro active? empty 873 +--ro last-updated? yang:date-and-time 875 module: ietf-rib-extension 876 augment /rt:routing/rt:control-plane-protocols 877 /rt:control-plane-protocol/rt:static-routes/v4ur:ipv4 878 /v4ur:route/v4ur:next-hop/v4ur:next-hop-options 879 /v4ur:simple-next-hop: 880 +--rw preference? uint32 881 +--rw tag? uint32 882 +--rw application-tag? uint32 883 augment /rt:routing/rt:control-plane-protocols 884 /rt:control-plane-protocol/rt:static-routes/v4ur:ipv4 885 /v4ur:route/v4ur:next-hop/v4ur:next-hop-options 886 /v4ur:next-hop-list/v4ur:next-hop-list/v4ur:next-hop: 887 +--rw preference? uint32 888 +--rw tag? uint32 889 +--rw application-tag? uint32 890 augment /rt:routing/rt:control-plane-protocols 891 /rt:control-plane-protocol/rt:static-routes/v6ur:ipv6 892 /v6ur:route/v6ur:next-hop/v6ur:next-hop-options 893 /v6ur:simple-next-hop: 894 +--rw preference? uint32 895 +--rw tag? uint32 896 +--rw application-tag? uint32 897 augment /rt:routing/rt:control-plane-protocols 898 /rt:control-plane-protocol/rt:static-routes/v6ur:ipv6 899 /v6ur:route/v6ur:next-hop/v6ur:next-hop-options 900 /v6ur:next-hop-list/v6ur:next-hop-list/v6ur:next-hop: 901 +--rw preference? uint32 902 +--rw tag? uint32 903 +--rw application-tag? uint32 904 augment /rt:routing/rt:ribs/rt:rib: 905 +--ro rib-summary-statistics 906 +--ro total-routes? uint32 907 +--ro total-active-routes? uint32 908 +--ro total-route-memory? uint64 909 +--ro protocol-rib-statistics* [] 910 +--ro rib-protocol? identityref 911 +--ro protocol-total-routes? uint32 912 +--ro protocol-active-routes? uint32 913 +--ro protocol-route-memory? uint64 914 augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route: 915 +--ro metric? uint32 916 +--ro tag? uint32 917 +--ro application-tag? uint32 918 augment /rt:routing/rt:ribs/rt:rib/rt:routes: 919 +--ro repair-route* [id] 920 +--ro id string 921 +--ro next-hop 922 | +--ro outgoing-interface? if:interface-state-ref 923 | +--ro next-hop-address? inet:ip-address 924 +--ro metric? uint32 925 augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop 926 /rt:next-hop-options/rt:simple-next-hop: 927 +--ro repair-path? -> /rt:routing/ribs/rib/routes/repair-route/id 928 augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop 929 /rt:next-hop-options/rt:special-next-hop: 930 +--ro repair-path? -> /rt:routing/ribs/rib/routes/repair-route/id 931 augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop 932 /rt:next-hop-options/rt:next-hop-list/rt:next-hop-list 933 /rt:next-hop: 934 +--ro repair-path? -> /rt:routing/ribs/rib/routes/repair-route/id 936 Appendix B. ietf-rib-extension.yang examples 938 Examples will be added in a future version of this document. 940 Appendix C. Acknowledgments 942 The RFC text was produced using Marshall Rose's xml2rfc tool. 944 The authors wish to thank Les Ginsberg, Krishna Deevi, and Suyoung 945 Yoon for their helpful comments and suggestions. 947 The authors wish to thank Tom Petch and Rob Wilton for review and 948 comments. 950 Authors' Addresses 952 Acee Lindem 953 Cisco Systems 954 301 Midenhall Way 955 Cary, NC 27513 956 USA 958 EMail: acee@cisco.com 959 Yingzhen Qu 960 Huawei 961 2330 Central Expressway 962 Santa Clara, CA 95050 963 USA 965 EMail: yingzhen.qu@huawei.com