idnits 2.17.1 draft-ietf-rtgwg-yang-rib-extend-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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 783 has weird spacing: '...-family ide...' == Line 817 has weird spacing: '...rotocol ide...' == Line 827 has weird spacing: '...ro type ide...' == Line 828 has weird spacing: '...ro name str...' == Line 832 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 9, 2020) is 1506 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) ** Downref: Normative reference to an Informational RFC: RFC 5714 Summary: 2 errors (**), 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 10, 2020 Futurewei 6 March 9, 2020 8 RIB YANG Data Model 9 draft-ietf-rtgwg-yang-rib-extend-03 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 10, 2020. 37 Copyright Notice 39 Copyright (c) 2020 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 . . . . . . . . . . . . . . . . . 17 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 IP Fast Reroute (IPFRR) pre-computes repair paths by routing 209 protocols [RFC5714], and the best repair path is installed in RIB. 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@2020-03-07.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 8242. 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 2020-03-07 { 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. This 432 additional tag can be used by applications that 433 require semantics and policy different from that 434 of the tag. For example, the tag is usually 435 automatically advertised in OSPF AS-External 436 Link State Advertisements (LSAs) while this 437 application specific tag is not unless done so 438 explicitly."; 439 } 440 } 441 grouping path-attribute { 442 description 443 "Path attribute grouping"; 444 leaf repair-path { 445 type leafref { 446 path "/rt:routing/rt:ribs/rt:rib/" 447 + "rt:routes/repair-route/id"; 448 } 449 description 450 "IP Fast ReRoute (IPFRR) repair path, use a path 451 from repair-route list"; 452 reference 453 "RFC 5714: IP Fast Reroute Framework."; 454 } 455 } 457 augment "/rt:routing/rt:control-plane-protocols/" 458 + "rt:control-plane-protocol/rt:static-routes/v4ur:ipv4/" 459 + "v4ur:route/v4ur:next-hop/v4ur:next-hop-options/" 460 + "v4ur:simple-next-hop" 461 { 462 description 463 "Augment 'simple-next-hop' case in IPv4 unicast route."; 464 leaf preference { 465 type uint32; 466 default "1"; 467 description "Route preference - Used to select among multiple 468 static routes with a lower preference next-hop 469 preferred and equal preference paths yielding 470 Equal Cost Multi-Path (ECMP)."; 471 } 472 leaf tag { 473 type uint32; 474 default "0"; 475 description "Route tag"; 477 } 478 } 480 augment "/rt:routing/rt:control-plane-protocols/" 481 + "rt:control-plane-protocol/rt:static-routes/v4ur:ipv4/" 482 + "v4ur:route/v4ur:next-hop/v4ur:next-hop-options/" 483 + "v4ur:next-hop-list/v4ur:next-hop-list/v4ur:next-hop" 484 { 485 description 486 "Augment static route configuration 'next-hop-list'."; 488 leaf preference { 489 type uint32; 490 default "1"; 491 description "Route preference - Used to select among multiple 492 static routes with a lower preference next-hop 493 preferred and equal preference paths yielding 494 Equal Cost Multi-Path (ECMP)."; 495 } 496 leaf tag { 497 type uint32; 498 default "0"; 499 description "Route tag"; 500 } 501 } 503 augment "/rt:routing/rt:control-plane-protocols/" 504 + "rt:control-plane-protocol/rt:static-routes/v6ur:ipv6/" 505 + "v6ur:route/v6ur:next-hop/v6ur:next-hop-options/" 506 + "v6ur:simple-next-hop" 507 { 508 description 509 "Augment 'simple-next-hop' case in IPv6 unicast route."; 510 leaf preference { 511 type uint32; 512 default "1"; 513 description "Route preference - Used to select among multiple 514 static routes with a lower preference next-hop 515 preferred and equal preference paths yielding 516 Equal Cost Multi-Path (ECMP)."; 517 } 518 leaf tag { 519 type uint32; 520 default "0"; 521 description "Route tag"; 522 } 523 } 524 augment "/rt:routing/rt:control-plane-protocols/" 525 + "rt:control-plane-protocol/rt:static-routes/v6ur:ipv6/" 526 + "v6ur:route/v6ur:next-hop/v6ur:next-hop-options/" 527 + "v6ur:next-hop-list/v6ur:next-hop-list/v6ur:next-hop" 528 { 529 description 530 "Augment static route configuration 'next-hop-list'."; 532 leaf preference { 533 type uint32; 534 default "1"; 535 description "Route preference - Used to select among multiple 536 static routes with a lower preference next-hop 537 preferred and equal preference paths yielding 538 Equal Cost Multi-Path (ECMP)."; 539 } 540 leaf tag { 541 type uint32; 542 default "0"; 543 description "Route tag"; 544 } 545 } 547 augment "/rt:routing/rt:ribs/rt:rib" 548 { 549 description "Augment a RIB with statistics"; 550 uses rib-statistics; 551 } 553 augment "/rt:routing/rt:ribs/rt:rib/" 554 + "rt:routes/rt:route" 555 { 556 description 557 "Augment a route in RIB with tag."; 558 uses attributes; 559 } 561 augment "/rt:routing/rt:ribs/rt:rib/" 562 + "rt:routes" 563 { 564 description 565 "Augment a route with a list of repair-paths."; 566 list repair-route { 567 key "id"; 568 description 569 "A repair-path entry, which can be referenced 570 by a repair-path."; 571 leaf id { 572 type string; 573 description 574 "A unique identifier."; 575 } 577 container next-hop { 578 description 579 "Route's next-hop attribute."; 580 leaf outgoing-interface { 581 type if:interface-state-ref; 582 description 583 "Name of the outgoing interface."; 584 } 585 leaf next-hop-address { 586 type inet:ip-address; 587 description 588 "IP address of the next hop."; 589 } 590 } 591 leaf metric { 592 type uint32; 593 description "Route metric"; 594 } 595 } 596 } 598 augment "/rt:routing/rt:ribs/rt:rib/" 599 + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/" 600 + "rt:simple-next-hop" 601 { 602 description 603 "Add more parameters to a path."; 604 uses path-attribute; 605 } 607 augment "/rt:routing/rt:ribs/rt:rib/" 608 + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/" 609 + "rt:special-next-hop" 610 { 611 description 612 "Add more parameters to a path."; 613 uses path-attribute; 614 } 616 augment "/rt:routing/rt:ribs/rt:rib/" 617 + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/" 618 + "rt:next-hop-list/rt:next-hop-list/rt:next-hop" 619 { 620 description 621 "This case augments the 'next-hop-options' in the routing 622 model."; 623 uses path-attribute; 624 } 625 } 626 628 6. Security Considerations 630 The YANG modules specified in this document define a schema for data 631 that is designed to be accessed via network management protocols such 632 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 633 is the secure transport layer, and the mandatory-to-implement secure 634 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 635 is HTTPS, and the mandatory-to-implement secure transport is TLS 636 [RFC5246]. 638 The NETCONF access control model [RFC8341] provides the means to 639 restrict access for particular NETCONF or RESTCONF users to a pre- 640 configured subset of all available NETCONF or RESTCONF protocol 641 operations and content. 643 There are a number of data nodes defined in ietf-rib-extensions.yang 644 module that are writable/creatable/deletable (i.e., config true, 645 which is the default). These data nodes may be considered sensitive 646 or vulnerable in some network environments. Write operations (e.g., 647 edit-config) to these data nodes without proper protection can have a 648 negative effect on network operations. For these augmentations to 649 ietf-routing.yang, the ability to delete, add, and modify IPv4 and 650 IPv6 static routes would allow traffic to be misrouted. 652 Some of the readable data nodes in the ietf-rib-extensions.yang 653 module may be considered sensitive or vulnerable in some network 654 environments. It is thus important to control read access (e.g., via 655 get, get-config, or notification) to these data nodes. The exposure 656 of the Routing Information Base (RIB) will expose the routing 657 topology of the network. This may be undesirable since both due to 658 the fact that exposure may facilitate other attacks. Additionally, 659 network operators may consider their topologies to be sensitive 660 confidential data. 662 All the security considerations for [RFC8349] writable and readable 663 data nodes apply to the augmentations described herein. 665 7. IANA Considerations 667 This document registers a URI in the IETF XML registry 668 [XML-REGISTRY]. Following the format in [RFC3688], the following 669 registration is requested to be made: 671 URI: urn:ietf:params:xml:ns:yang:ietf-rib-extension 673 Registrant Contact: The IESG. 675 XML: N/A, the requested URI is an XML namespace. 677 This document registers a YANG module in the YANG Module Names 678 registry [RFC6020]. 680 name: ietf-acl namespace: urn:ietf:params:xml:ns:yang:ietf-rib- 681 extension prefix: ietf-rib-ext reference: RFC XXXX 683 8. References 685 8.1. Normative References 687 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 688 Requirement Levels", BCP 14, RFC 2119, 689 DOI 10.17487/RFC2119, March 1997, 690 . 692 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 693 DOI 10.17487/RFC3688, January 2004, 694 . 696 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 697 (TLS) Protocol Version 1.2", RFC 5246, 698 DOI 10.17487/RFC5246, August 2008, 699 . 701 [RFC5714] Shand, M. and S. Bryant, "IP Fast Reroute Framework", 702 RFC 5714, DOI 10.17487/RFC5714, January 2010, 703 . 705 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 706 the Network Configuration Protocol (NETCONF)", RFC 6020, 707 DOI 10.17487/RFC6020, October 2010, 708 . 710 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 711 and A. Bierman, Ed., "Network Configuration Protocol 712 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 713 . 715 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 716 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 717 . 719 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 720 RFC 6991, DOI 10.17487/RFC6991, July 2013, 721 . 723 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 724 RFC 7950, DOI 10.17487/RFC7950, August 2016, 725 . 727 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 728 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 729 . 731 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 732 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 733 May 2017, . 735 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 736 Access Control Model", STD 91, RFC 8341, 737 DOI 10.17487/RFC8341, March 2018, 738 . 740 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 741 and R. Wilton, "Network Management Datastore Architecture 742 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 743 . 745 [RFC8343] Bjorklund, M., "A YANG Data Model for Interface 746 Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, 747 . 749 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 750 Routing Management (NMDA Version)", RFC 8349, 751 DOI 10.17487/RFC8349, March 2018, 752 . 754 8.2. Informative References 756 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 757 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 758 . 760 [XML-REGISTRY] 761 Mealling, M., "The IETF XML Registry", BCP 81, January 762 2004. 764 Appendix A. Combined Tree Diagram 766 This appendix includes the combined ietf-routing.yang and ietf-rib- 767 extensions.yang tree diagram. 769 module: ietf-routing 770 +--rw routing 771 | +--rw router-id? yang:dotted-quad 772 | +--ro interfaces 773 | | +--ro interface* if:interface-ref 774 | +--rw control-plane-protocols 775 | | +--rw control-plane-protocol* [type name] 776 | | +--rw type identityref 777 | | +--rw name string 778 | | +--rw description? string 779 | | +--rw static-routes 780 | +--rw ribs 781 | +--rw rib* [name] 782 | +--rw name string 783 | +--rw address-family identityref 784 | +--ro default-rib? boolean {multiple-ribs}? 785 | +--ro routes 786 | | +--ro route* [] 787 | | +--ro route-preference? route-preference 788 | | +--ro next-hop 789 | | | +--ro (next-hop-options) 790 | | | +--:(simple-next-hop) 791 | | | | +--ro outgoing-interface? if:interface-ref 792 | | | +--:(special-next-hop) 793 | | | | +--ro special-next-hop? enumeration 794 | | | +--:(next-hop-list) 795 | | | +--ro next-hop-list 796 | | | +--ro next-hop* [] 797 | | | +--ro outgoing-interface? 798 | | | if:interface-ref 799 | | +--ro source-protocol identityref 800 | | +--ro active? empty 801 | | +--ro last-updated? yang:date-and-time 802 | +---x active-route 803 | | +--ro output 804 | | +--ro route 805 | | +--ro next-hop 806 | | | +--ro (next-hop-options) 807 | | | +--:(simple-next-hop) 808 | | | | +--ro outgoing-interface? 809 | | | | if:interface-ref 810 | | | +--:(special-next-hop) 811 | | | | +--ro special-next-hop? enumeration 812 | | | +--:(next-hop-list) 813 | | | +--ro next-hop-list 814 | | | +--ro next-hop* [] 815 | | | +--ro outgoing-interface? 816 | | | if:interface-ref 817 | | +--ro source-protocol identityref 818 | | +--ro active? empty 819 | | +--ro last-updated? yang:date-and-time 820 | +--rw description? string 821 o--ro routing-state 822 +--ro router-id? yang:dotted-quad 823 o--ro interfaces 824 | o--ro interface* if:interface-state-ref 825 o--ro control-plane-protocols 826 | o--ro control-plane-protocol* [type name] 827 | o--ro type identityref 828 | o--ro name string 829 o--ro ribs 830 o--ro rib* [name] 831 o--ro name string 832 +--ro address-family identityref 833 o--ro default-rib? boolean {multiple-ribs}? 834 o--ro routes 835 | o--ro route* [] 836 | o--ro route-preference? route-preference 837 | o--ro next-hop 838 | | +--ro (next-hop-options) 839 | | +--:(simple-next-hop) 840 | | | +--ro outgoing-interface? if:interface-ref 841 | | +--:(special-next-hop) 842 | | | +--ro special-next-hop? enumeration 843 | | +--:(next-hop-list) 844 | | +--ro next-hop-list 845 | | +--ro next-hop* [] 846 | | +--ro outgoing-interface? 847 | | if:interface-ref 848 | +--ro source-protocol identityref 849 | +--ro active? empty 850 | +--ro last-updated? yang:date-and-time 851 o---x active-route 852 +--ro output 853 o--ro route 854 o--ro next-hop 855 | +--ro (next-hop-options) 856 | +--:(simple-next-hop) 857 | | +--ro outgoing-interface? 858 | | if:interface-ref 859 | +--:(special-next-hop) 860 | | +--ro special-next-hop? enumeration 861 | +--:(next-hop-list) 862 | +--ro next-hop-list 863 | +--ro next-hop* [] 864 | +--ro outgoing-interface? 865 | if:interface-ref 866 +--ro source-protocol identityref 867 +--ro active? empty 868 +--ro last-updated? yang:date-and-time 870 module: ietf-rib-extension 871 augment /rt:routing/rt:control-plane-protocols 872 /rt:control-plane-protocol/rt:static-routes/v4ur:ipv4 873 /v4ur:route/v4ur:next-hop/v4ur:next-hop-options 874 /v4ur:simple-next-hop: 875 +--rw preference? uint32 876 +--rw tag? uint32 877 +--rw application-tag? uint32 878 augment /rt:routing/rt:control-plane-protocols 879 /rt:control-plane-protocol/rt:static-routes/v4ur:ipv4 880 /v4ur:route/v4ur:next-hop/v4ur:next-hop-options 881 /v4ur:next-hop-list/v4ur:next-hop-list/v4ur:next-hop: 882 +--rw preference? uint32 883 +--rw tag? uint32 884 +--rw application-tag? uint32 885 augment /rt:routing/rt:control-plane-protocols 886 /rt:control-plane-protocol/rt:static-routes/v6ur:ipv6 887 /v6ur:route/v6ur:next-hop/v6ur:next-hop-options 888 /v6ur:simple-next-hop: 889 +--rw preference? uint32 890 +--rw tag? uint32 891 +--rw application-tag? uint32 892 augment /rt:routing/rt:control-plane-protocols 893 /rt:control-plane-protocol/rt:static-routes/v6ur:ipv6 894 /v6ur:route/v6ur:next-hop/v6ur:next-hop-options 895 /v6ur:next-hop-list/v6ur:next-hop-list/v6ur:next-hop: 896 +--rw preference? uint32 897 +--rw tag? uint32 898 +--rw application-tag? uint32 899 augment /rt:routing/rt:ribs/rt:rib: 900 +--ro rib-summary-statistics 901 +--ro total-routes? uint32 902 +--ro total-active-routes? uint32 903 +--ro total-route-memory? uint64 904 +--ro protocol-rib-statistics* [] 905 +--ro rib-protocol? identityref 906 +--ro protocol-total-routes? uint32 907 +--ro protocol-active-routes? uint32 908 +--ro protocol-route-memory? uint64 909 augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route: 910 +--ro metric? uint32 911 +--ro tag? uint32 912 +--ro application-tag? uint32 913 augment /rt:routing/rt:ribs/rt:rib/rt:routes: 914 +--ro repair-route* [id] 915 +--ro id string 916 +--ro next-hop 917 | +--ro outgoing-interface? if:interface-state-ref 918 | +--ro next-hop-address? inet:ip-address 919 +--ro metric? uint32 920 augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop 921 /rt:next-hop-options/rt:simple-next-hop: 922 +--ro repair-path? -> /rt:routing/ribs/rib/routes/repair-route/id 923 augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop 924 /rt:next-hop-options/rt:special-next-hop: 925 +--ro repair-path? -> /rt:routing/ribs/rib/routes/repair-route/id 926 augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop 927 /rt:next-hop-options/rt:next-hop-list/rt:next-hop-list 928 /rt:next-hop: 929 +--ro repair-path? -> /rt:routing/ribs/rib/routes/repair-route/id 931 Appendix B. ietf-rib-extension.yang examples 933 Examples will be added in a future version of this document. 935 Appendix C. Acknowledgments 937 The RFC text was produced using Marshall Rose's xml2rfc tool. 939 The authors wish to thank Les Ginsberg, Krishna Deevi, and Suyoung 940 Yoon for their helpful comments and suggestions. 942 The authors wish to thank Tom Petch and Rob Wilton for review and 943 comments. 945 Authors' Addresses 946 Acee Lindem 947 Cisco Systems 948 301 Midenhall Way 949 Cary, NC 27513 950 USA 952 EMail: acee@cisco.com 954 Yingzhen Qu 955 Futurewei 956 2330 Central Expressway 957 Santa Clara, CA 95050 958 USA 960 EMail: yingzhen.qu@futurewei.com