<?xmlversion='1.0' encoding='utf-8'?>version="1.0" encoding="UTF-8"?> <!-- draft submitted in xml v3 --> <!DOCTYPE rfc [ <!ENTITY nbsp " "> <!ENTITY zwsp "​"> <!ENTITY nbhy "‑"> <!ENTITY wj "⁠"> ]><?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?> <?rfc strict="no" ?> <?rfc toc="yes" ?> <?rfc symrefs="yes" ?> <?rfc sortrefs="yes"?> <?rfc rfcedstyle="yes" ?> <?rfc subcompact="no" ?><rfc xmlns:xi="http://www.w3.org/2001/XInclude" submissionType="IETF" category="std" consensus="true" ipr="trust200902"docName="draft-ietf-rtgwg-yang-rib-extend-22"docName="draft-ietf-rtgwg-yang-rib-extend-24" number="9403" obsoletes="" updates=""submissionType="IETF"xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true"version="3" consensus="true">version="3"> <!-- xml2rfc v2v3 conversion 3.17.1 --> <front> <title abbrev="YANGRIB-EXT">RIB ExtensionRIB-EXT">A YANG DataModel</title>Model for RIB Extensions</title> <seriesInfoname="Internet-Draft" value="draft-ietf-rtgwg-yang-rib-extend-22"/>name="RFC" value="9403"/> <author initials="A." surname="Lindem" fullname="Acee Lindem"> <organization>LabNConsulting LLC</organization>Consulting, L.L.C.</organization> <address> <postal> <street>301 Midenhall Way</street> <city>Cary</city> <region>NC</region><country>USA</country><country>United States of America</country> <code>27513</code> </postal> <email>acee.ietf@gmail.com</email> </address> </author> <author fullname="Yingzhen Qu" initials="Y" surname="Qu"><organization>Futurewei</organization><organization>Futurewei Technologies</organization> <address> <postal> <street>2330 Central Expressway</street> <city>Santa Clara</city> <region>CA</region> <code>95050</code><country>USA</country><country>United States of America</country> </postal><phone/><email>yingzhen.qu@futurewei.com</email> </address> </author><date/><date year="2023" month="November" /> <area>rtg</area> <workgroup>rtgwg</workgroup> <keyword>configuration</keyword> <keyword>IPv6 Router Advertisements</keyword> <keyword>NETCONF</keyword> <keyword>RESTCONF</keyword> <keyword>YANG</keyword> <keyword>Routing</keyword> <keyword>RIB</keyword> <abstract> <t>A Routing Information Base (RIB) is a list of routes and their corresponding administrative data and operational state.</t> <t>RFC 8349 defines the basic building blocks for the RIB data model, and this model augments it to support multiplenext-hops (aka,next hops (aka paths) for each route as well as additional attributes.</t> </abstract> </front> <middle> <section numbered="true" toc="default"> <name>Introduction</name> <t>This document defines a YANG data model <xref target="RFC7950" format="default"/>data model whichthat extends the RIB data model defined in the ietf-routing YANG module <xref target="RFC8349" format="default"/> with more route attributes.</t> <t>A RIB is a collection of routes with attributes controlled and manipulated bycontrol-planecontrol plane protocols. Each RIB contains only routes of one address family <xref target="RFC8349" format="default"/>. Within a protocol, routes are selected based on the metrics in use by that protocol, and the protocol installs the routes to the RIB. The RIB selects the preferred or active route by comparing theroute-preference (aka,route preference (aka administrative distance) of the candidate routes installed by different protocols.</t> <t>The module defined in this document extends the RIB to support more route attributes, such as multiplenext-hops,next hops, route metrics, and administrative tags.</t> <t> The YANG modules defined and discussed in this document conform to the Network Management Datastore Architecture (NMDA)[RFC8342].</t><xref target="RFC8342"/>.</t> </section> <section numbered="true" toc="default"> <name>Terminology and Notation</name> <t>The following terms are defined in <xref target="RFC8342" format="default"/>: </t> <ul spacing="normal"> <li>configuration</li> <li>system state</li> <li>operational state</li> </ul> <t>The following terms are defined in <xref target="RFC7950" format="default"/>: </t> <ul spacing="normal"> <li>action</li> <li>augment</li> <li>container</li> <li>container with presence</li> <li>data model</li> <li>data node</li> <li>leaf</li> <li>list</li> <li>mandatory node</li> <li>module</li> <li>schema tree</li><li>RPC (Remote Procedure Call) operation</li></ul> <t>The followingterms areterm is defined in <xref target="RFC8349"format="default"/> Section 5.2:sectionFormat="comma" section="5.2"/>: </t> <ul spacing="normal"> <li>RIB</li> </ul> <section numbered="true" toc="default"> <name>Tree Diagrams</name> <t>Tree diagrams used in this document follow the notation defined in <xref target="RFC8340" format="default"/>.</t> </section> <section anchor="sec.prefixes" numbered="true" toc="default"> <name>Prefixes in Data Node Names</name> <t>In this document, names of data nodes, actions, and other data model objects are often used without a prefix, as long as it is clear from the context in which YANG module each name is defined. Otherwise, names are prefixed using the standard prefix associated with the corresponding YANG module, as shown in <xref target="tab.prefixes" format="default"/>.</t> <table anchor="tab.prefixes" align="center"> <name>Prefixes and Corresponding YANG Modules</name> <thead> <tr> <th align="left">Prefix</th> <th align="left">YANGmodule</th>Module</th> <th align="left">Reference</th> </tr> </thead> <tbody> <tr> <td align="left">if</td> <td align="left">ietf-interfaces</td> <td align="left"> <xref target="RFC8343" format="default"/></td> </tr> <tr> <td align="left">rt</td> <td align="left">ietf-routing</td> <td align="left"> <xref target="RFC8349" format="default"/></td> </tr> <tr> <td align="left">v4ur</td> <td align="left">ietf-ipv4-unicast-routing</td> <td align="left"> <xref target="RFC8349" format="default"/></td> </tr> <tr> <td align="left">v6ur</td> <td align="left">ietf-ipv6-unicast-routing</td> <td align="left"> <xref target="RFC8349" format="default"/></td> </tr> <tr> <td align="left">inet</td> <td align="left">ietf-inet-types</td> <td align="left"> <xref target="RFC6991" format="default"/></td> </tr> <tr> <td align="left">ospf</td> <td align="left">ietf-ospf</td> <td align="left"> <xref target="RFC9129" format="default"/></td> </tr> <tr> <td align="left">isis</td> <td align="left">ietf-isis</td> <td align="left"> <xref target="RFC9130" format="default"/></td> </tr> </tbody> </table> </section> </section> <section numbered="true" toc="default"> <name>Design of the Model</name> <t>The YANG module defined in this document augments theietf-routingietf-routing, ietf-ipv4-unicast-routing, and ietf-ipv6-unicast-routing YANG modules defined in <xref target="RFC8349" format="default"/>, which provide a basis for routing system data model development. Together with the ietf-routing YANG module and other YANG modules defined in <xref target="RFC8349" format="default"/>, a generic RIB YANG data model is defined herein to implement and monitor aRIB.</t>RIB. </t> <t>The modules in <xref target="RFC8349" format="default"/> also define the basic configuration and operational state for both IPv4 and IPv6 static routes. This document provides augmentations for static routes to support multiplenext-hopsnext hops and more next-hop attributes. </t> <section numbered="true" toc="default"> <name>Tags andPreference</name>Preferences</name> <t>Individual route tags are supported at both the route and next-hop level. A preference pernext-hopnext hop is also supported for selection of the most preferred reachable static route.</t> <t>The following tree snapshot shows tag and preferencewhichentries that augment static IPv4 unicastroutesroute and IPv6 unicastroutes next-hop.</t> <artwork name="" type="" align="left" alt=""><![CDATA[route next hops.</t> <sourcecode type="yangtree"><![CDATA[ augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/rt:static-routes/v4ur:ipv4 /v4ur:route/v4ur:next-hop/v4ur:next-hop-options /v4ur:simple-next-hop: +--rw preference? uint32 +--rw tag? uint32 augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/rt:static-routes/v4ur:ipv4 /v4ur:route/v4ur:next-hop/v4ur:next-hop-options /v4ur:next-hop-list/v4ur:next-hop-list/v4ur:next-hop: +--rw preference? uint32 +--rw tag? uint32 augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/rt:static-routes/v6ur:ipv6 /v6ur:route/v6ur:next-hop/v6ur:next-hop-options /v6ur:simple-next-hop: +--rw preference? uint32 +--rw tag? uint32 augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/rt:static-routes/v6ur:ipv6 /v6ur:route/v6ur:next-hop/v6ur:next-hop-options /v6ur:next-hop-list/v6ur:next-hop-list/v6ur:next-hop: +--rw preference? uint32 +--rw tag? uint32]]></artwork>augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route: +--ro metric? uint32 +--ro tag* uint32 +--ro application-tag? uint32 ]]></sourcecode> </section> <section numbered="true" toc="default"> <name>Repair Path</name> <t>The IP Fast Reroute (IPFRR) calculation by routing protocolpre-computesprecomputes repair paths <xref target="RFC5714" format="default"/>, and the repair paths are installed in the RIB.</t> <t>Each routenext-hopnext hop in the RIB is augmented with a repairpath,path and is shown in the following tree snapshot.</t><artwork name="" type="" align="left" alt=""><![CDATA[<sourcecode type="yangtree"><![CDATA[ augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route /rt:next-hop/rt:next-hop-options/rt:simple-next-hop: +--ro repair-path +--ro outgoing-interface? if:interface-state-ref +--ro next-hop-address? inet:ip-address-no-zone +--ro metric? uint32 augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route /rt:next-hop/rt:next-hop-options/rt:next-hop-list /rt:next-hop-list/rt:next-hop: +--ro repair-path +--ro outgoing-interface? if:interface-state-ref +--ro next-hop-address? inet:ip-address-no-zone +--ro metric? uint32]]></artwork>]]></sourcecode> </section> </section> <section anchor="rib.tree" numbered="true" toc="default"> <name>RIB Model Tree</name> <t> The ietf-routing.yang tree with the augmentations herein is included in <xref target="full-tree" format="default"/>. Themeaningmeanings of the symbols can be found in <xref target="RFC8340" format="default"/>.</t> </section> <section numbered="true" toc="default"> <name>RIB Extension YANGModel</name>Module</name> <t>This YANG module references <xref target="RFC6991"/>, <xref target="RFC8343"/>, <xref target="RFC8349"/>, <xref target="RFC9129"/>, <xref target="RFC9130"/>, and <xref target="RFC5714"/>.</t> <sourcecodename="ietf-rib-extension@2023-06-06.yang" type=""name="ietf-rib-extension@2023-11-01.yang" type="yang" markers="true"><![CDATA[ module ietf-rib-extension { yang-version"1.1";1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-rib-extension"; prefix rib-ext; import ietf-inet-types { prefix"inet";inet; reference "RFC 6991: Common YANG Data Types"; } import ietf-interfaces { prefix"if";if; reference "RFC 8343: A YANG Data Model for InterfaceManagement (NMDA Version)";Management"; } import ietf-routing { prefix"rt";rt; reference "RFC 8349: A YANG Data Model for Routing Management (NMDA Version)"; } import ietf-ipv4-unicast-routing { prefix"v4ur";v4ur; reference "RFC 8349: A YANG Data Model for Routing Management (NMDA Version)"; } import ietf-ipv6-unicast-routing { prefix"v6ur";v6ur; reference "RFC 8349: A YANG Data Model for Routing Management (NMDA Version)"; } import ietf-ospf { prefix ospf; reference "RFC 9129: YANG Data Model for the OSPF Protocol"; } import ietf-isis { prefix isis; reference "RFC 9130: YANG Data Model for the IS-IS Protocol"; } organization "IETF RTGWG- Routing(Routing Area WorkingGroup";Group)"; contact "WG Web:<https://datatracker.ietf.org/group/rtgwg/><https://datatracker.ietf.org/wg/rtgwg/> WG List: <mailto:rtgwg@ietf.org> Author: Acee Lindem <mailto:acee.ietf@gmail.com> Author: Yingzhen Qu <mailto:yingzhen.qu@futurewei.com>"; description "This YANG module extends the RIB defined in the ietf-routing YANG module with additional route attributes. This YANG module conforms to the Network Management Datastore Architecture(NDMA)(NMDA) as described in RFC 8342. Copyright (c) 2023 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFCXXXX;9403; see the RFC itself for full legal notices."; revision2023-06-062023-11-01 { description "InitialVersion";version."; reference "RFCXXXX:9403: A YANG Data Model for RIBExtensions.";Extensions"; } /* Groupings */ grouping rib-statistics { description "Statistics grouping used for RIB augmentation."; container statistics { config false; description "Container for RIB statistics."; leaf total-routes { type uint32; description "Total number of routes in theRIB";RIB."; } leaf total-active-routes { type uint32; description "Total number of active routes in the RIB. An active route is the route that is preferred over other routes to the same destination prefix."; } leaf total-route-memory { type uint64; units "bytes"; description "Total memory for all routes in the RIB."; } list protocol-statistics { description "RIB statistics for routing protocols installing routes in the RIB."; leaf protocol { type identityref { base rt:routing-protocol; } description "Routing protocol installing routes in the RIB."; } leaf routes { type uint32; description "Total number of routes in the RIB for the routing protocol identified by the'protocol'.";'protocol' entry."; } leaf active-routes { type uint32; description "Total number of active routes in the RIB for the routing protocolfor the routing protocolidentified by the'protocol'.'protocol' entry. An active route is preferred over other routes to the same destination prefix."; } leaf route-memory { type uint64; units "bytes"; description "Total memory for all routes in the RIB for the routing protocol identified by the'protocol'.";'protocol' entry."; } } } } groupingattributes { description "Common attributes applicable to all routes."; leaf metric { type uint32; description "The metric is a numeric value indicating the cost of the route from the perspective of the routing protocol installing the route. In general, routes with a lower metric installed by the same routing protocol are lower cost to reach and are preferable to routes with a higher metric. However, metrics from different routing protocols are not comparable."; } leaf-list tag { type uint32; description "A tag is a 32-bit opaque value associated with the route that can be used for policy decisions such as advertisement and filtering of the route."; } leaf application-tag { type uint32; description "The application-specific tag is an additional tag that can be used by applications that require semantics and/or policy different from that of the tag. For example, the tag is usually automatically advertised in OSPF AS-External Link State Advertisements (LSAs) while this application-specific tag is not advertised implicitly."; } } groupingrepair-path { description "Grouping for the IP Fast Reroute (IPFRR) repair path."; container repair-path { description"IP Fast Reroute"IPFRR next-hop repair path."; leaf outgoing-interface { type if:interface-state-ref; description "Name of the outgoing interface."; } leaf next-hop-address { type inet:ip-address-no-zone; description "IP address of the next hop."; } leaf metric { type uint32; description "The metric for the repair path. While theIP Fast Reroute re-routereroute repair is local and the metric is not advertised externally, the metric for the repair path is useful for troubleshooting purposes."; } reference "RFC 5714: IP Fast RerouteFramework.";Framework"; } } augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:static-routes/v4ur:ipv4/" + "v4ur:route/v4ur:next-hop/v4ur:next-hop-options/" + "v4ur:simple-next-hop" { description "Augment 'simple-next-hop' case in IPv4 unicast route."; leaf preference { type uint32; default "1"; description "The preference is used to select among multiple static routes. Routes with a lowerpreferencenext-hop preference value arepreferredpreferred, andequal preferenceequal-preference routes result inEqual-Cost-Multi-PathEqual-Cost Multipath (ECMP) static routes."; } leaf tag { type uint32; default "0"; description "The tag is a 32-bit opaque value associated with the route that can be used for policy decisions such as advertisement and filtering of the route."; } } augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:static-routes/v4ur:ipv4/" + "v4ur:route/v4ur:next-hop/v4ur:next-hop-options/" + "v4ur:next-hop-list/v4ur:next-hop-list/v4ur:next-hop" { description "Augment static route configuration 'next-hop-list'."; leaf preference { type uint32; default "1"; description "The preference is used to select among multiple static routes. Routes with a lowerpreferencenext-hop preference value arepreferredpreferred, andequal preferenceequal-preference routes result inEqual-Cost-Multi-Path (ECMP)ECMP static routes."; } leaf tag { type uint32; default "0"; description "The tag is a 32-bit opaque value associated with the route that can be used for policy decisions such as advertisement and filtering of the route."; } } augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:static-routes/v6ur:ipv6/" + "v6ur:route/v6ur:next-hop/v6ur:next-hop-options/" + "v6ur:simple-next-hop" { description "Augment 'simple-next-hop' case in IPv6 unicast route."; leaf preference { type uint32; default "1"; description "The preference is used to select among multiple static routes. Routes with a lowerpreferencenext-hop preference value arepreferredpreferred, andequal preferenceequal-preference routes result inEqual-Cost-Multi-Path (ECMP)ECMP static routes."; } leaf tag { type uint32; default "0"; description "The tag is a 32-bit opaque value associated with the route that can be used for policy decisions such as advertisement and filtering of the route."; } } augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:static-routes/v6ur:ipv6/" + "v6ur:route/v6ur:next-hop/v6ur:next-hop-options/" + "v6ur:next-hop-list/v6ur:next-hop-list/v6ur:next-hop" { description "Augment static route configuration 'next-hop-list'."; leaf preference { type uint32; default "1"; description "The preference is used to select among multiple static routes. Routes with a lowerpreferencenext-hop preference value arepreferredpreferred, andequal preferenceequal-preference routes result inEqual-Cost-Multi-Path (ECMP)ECMP static routes."; } leaf tag { type uint32; default "0"; description "The tag is a 32-bit opaque value associated with the route that can be used for policy decisions such as advertisement and filtering of the route."; } } augment "/rt:routing/rt:ribs/rt:rib" { description "Augment a RIB with statistics."; uses rib-statistics; } augment "/rt:routing/rt:ribs/rt:rib/" + "rt:routes/rt:route" { description "Augment a route in the RIB with common attributes.";uses attributes;leaf metric { when "not(derived-from(" + "../rt:source-protocol, 'ospf:ospf')) " + "and not(derived-from( " + "../rt:source-protocol, 'isis:isis'))" { description "This augmentation is only valid for routes that don't have OSPF or IS-IS as the source protocol. The YANG data models for OSPF and IS-IS already include a 'metric' augmentation for routes."; } type uint32; description "The metric is a numeric value indicating the cost of the route from the perspective of the routing protocol installing the route. In general, routes with a lower metric installed by the same routing protocol are lower cost to reach and are preferable to routes with a higher metric. However, metrics from different routing protocols are not comparable."; } leaf-list tag { when "not(derived-from(" + "../rt:source-protocol, 'ospf:ospf')) " + "and not(derived-from( " + "../rt:source-protocol, 'isis:isis'))" { description "This augmentation is only valid for routes that don't have OSPF or IS-IS as the source protocol. The YANG data models for OSPF and IS-IS already include a 'tag' augmentation for routes."; } type uint32; description "A tag is a 32-bit opaque value associated with the route that can be used for policy decisions such as advertisement and filtering of the route."; } leaf application-tag { type uint32; description "The application-specific tag is an additional tag that can be used by applications that require semantics and/or policy different from that of the tag. For example, the tag is usually automatically advertised in OSPF AS-External Link State Advertisements (LSAs) while this application-specific tag is not advertised implicitly."; } } augment "/rt:routing/rt:ribs/rt:rib/" + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/" + "rt:simple-next-hop" { description "Augmentsimple-next-hop'simple-next-hop' withrepair-path.";'repair-path'."; uses repair-path; } augment "/rt:routing/rt:ribs/rt:rib/" + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/" + "rt:next-hop-list/rt:next-hop-list/rt:next-hop" { description "Augment thenext-hopnext hop with a repair path."; uses repair-path; } } ]]></sourcecode> </section> <section numbered="true" toc="default"> <name>Security Considerations</name> <t>The YANG module specified in this document defines a schema for data that is designed to be accessed via network management protocols such as NETCONF <xreftarget="RFC6241" format="default"/>target="RFC6241"/> or RESTCONF <xreftarget="RFC8040" format="default"/>.target="RFC8040"/>. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) <xreftarget="RFC6242" format="default"/>.target="RFC6242"/>. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS <xreftarget="RFC8446" format="default"/>.</t>target="RFC8446"/>.</t> <t>TheNETCONF access control modelNetwork Configuration Access Control Model (NACM) <xreftarget="RFC8341" format="default"/>target="RFC8341"/> provides the means to restrict access for particular NETCONF or RESTCONF users to apre-configuredpreconfigured subset of all available NETCONF or RESTCONF protocol operations and content.</t> <t>There are a number of data nodes defined inietf-rib-extensions.yangthe ietf-rib-extension.yang module that are writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. These are the subtrees and data nodes and theirsensitivity/vulnerability: </t>sensitivity/vulnerability:</t> <ulempty="true"spacing="normal"> <li>/v4ur:next-hop-options/v4ur:simple-next-hop/rib-ext:preference</li> <li>/v4ur:next-hop-options/v4ur:simple-next-hop/rib-ext:tag</li> <li>/v4ur:next-hop-options/v4ur:next-hop-list/v4ur:next-hop-list /v4ur:next-hop/rib-ext:preference</li> <li>/v4ur:next-hop-options/v4ur:next-hop-list/v4ur:next-hop-list /v4ur:next-hop/rib-ext:tag</li> <li>/v6ur:next-hop-options/v6ur:simple-next-hop/rib-ext:preference</li> <li>/v6ur:next-hop-options/v6ur:simple-next-hop/rib-ext:tag</li> <li>/v6ur:next-hop-options/v6ur:next-hop-list/v6ur:next-hop-list /v6ur:next-hop/rib-ext:preference</li> <li>/v6ur:next-hop-options/v6ur:next-hop-list/v6ur:next-hop-list /v6ur:next-hop/rib-ext:tag</li><li>For</ul> <t indent="3">For these augmentations to ietf-routing.yang, the ability to delete, add, and modify IPv4 and IPv6 static routepreferencepreferences andtagtags would allow traffic to bemisrouted.</li> </ul>misrouted.</t> <t>Some of the readable data nodes in theietf-rib-extensions.yangietf-rib-extension.yang module may be considered sensitive or vulnerable in some network environments. It is thus important to control read access (e.g., via get, get-config, or notification) to these data nodes. These are the subtrees and data nodes and theirsensitivity/vulnerability: </t>sensitivity/vulnerability:</t> <ulempty="true"spacing="normal"> <li>/rt:routing/rt:ribs/rt:rib/rib-ext:statistics</li> <li>/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/rib-ext:metric</li> <li>/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/rib-ext:tag</li><li>/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route /rib-ext:application-tag</li> <li>/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop /rib-ext:repair-path</li> <li>/rt:routes/rt:route/rt:next-hop/rt:next-hop-options /rt:next-hop-list/rt:next-hop-list/rt:next-hop/rib-ext:repair-path</li> <li>The exposure of<li>/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/rib-ext:application-tag</li> <li>/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop/rib-ext:repair-path</li> <li>/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:next-hop-list/rt:next-hop-list/rt:next-hop/rib-ext:repair-path</li> </ul> <t indent="3">Exposing theRouting Information Base (RIB)RIB will expose the routing topology of the network. This may be undesirable due to the fact that such exposure may facilitate other attacks. Additionally, network operators may consider their topologies to be sensitive confidentialdata.</li> </ul>data.</t> <t>All the security considerations for<xref target="RFC8349" format="default"/>writable and readable data nodes defined in <xref target="RFC8349" format="default"/> apply to the augmentations described herein.</t> </section> <section numbered="true" toc="default"> <name>IANA Considerations</name> <t> This document registersathe following URI in theIETF"IETF XMLregistryRegistry" <xref target="RFC3688" format="default"/>.Following the format in <xref target="RFC3688" format="default"/>, the following registration is requested to be made:</t><artwork name="" type="" align="left" alt=""><![CDATA[ URI: urn:ietf:params:xml:ns:yang:ietf-rib-extension Registrant Contact: The IESG. XML: N/A,<dl spacing="compact" newline="false"> <dt>URI:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-rib-extension</dd> <dt>Registrant Contact:</dt><dd>The IESG.</dd> <dt>XML:</dt><dd>N/A; the requested URI is an XMLnamespace. ]]></artwork> <t>This document registers anamespace.</dd> </dl> <t>IANA has registered the following YANG module in theYANG"YANG ModuleNamesNames" registry <xref target="RFC6020" format="default"/>. </t><artwork name="" type="" align="left" alt=""><![CDATA[ name: ietf-rib-extension namespace: urn:ietf:params:xml:ns:yang:ietf-rib-extension prefix: rib-ext reference: RFC XXXX ]]></artwork><dl spacing="compact" newline="false"> <dt>Name:</dt><dd>ietf-rib-extension</dd> <dt>Namespace:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-rib-extension</dd> <dt>Prefix:</dt><dd>rib-ext</dd> <dt>Reference:</dt><dd>RFC 9403</dd> </dl> </section> </middle> <back> <references> <name>References</name> <references> <name>Normative References</name> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6020.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6241.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6242.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6991.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7950.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8040.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8341.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8342.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8343.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8349.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8446.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9129.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9130.xml"/> <referenceanchor="RFC3688" target="https://www.rfc-editor.org/info/rfc3688" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml">anchor="W3C.REC-xml-20081126" target="https://www.w3.org/TR/2008/REC-xml-20081126"> <front><title>The IETF XML Registry</title> <author fullname="M. Mealling" initials="M." surname="Mealling"/> <date month="January" year="2004"/> <abstract> <t>This document describes an IANA maintained registry for IETF standards which use Extensible<title>Extensible Markup Language (XML)related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas.</t> </abstract> </front> <seriesInfo name="BCP" value="81"/> <seriesInfo name="RFC" value="3688"/> <seriesInfo name="DOI" value="10.17487/RFC3688"/> </reference> <reference anchor="RFC6020" target="https://www.rfc-editor.org/info/rfc6020" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6020.xml"> <front> <title>YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)</title> <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/> <date month="October" year="2010"/> <abstract> <t>YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="6020"/> <seriesInfo name="DOI" value="10.17487/RFC6020"/> </reference> <reference anchor="RFC6241" target="https://www.rfc-editor.org/info/rfc6241" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6241.xml"> <front> <title>Network Configuration Protocol (NETCONF)</title> <author fullname="R. Enns" initials="R." role="editor" surname="Enns"/> <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/> <author fullname="J. Schoenwaelder" initials="J." role="editor" surname="Schoenwaelder"/> <author fullname="A. Bierman" initials="A." role="editor" surname="Bierman"/> <date month="June" year="2011"/> <abstract> <t>The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="6241"/> <seriesInfo name="DOI" value="10.17487/RFC6241"/> </reference> <reference anchor="RFC6242" target="https://www.rfc-editor.org/info/rfc6242" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6242.xml"> <front> <title>Using the NETCONF Protocol over Secure Shell (SSH)</title> <author fullname="M. Wasserman" initials="M." surname="Wasserman"/> <date month="June" year="2011"/> <abstract> <t>This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="6242"/> <seriesInfo name="DOI" value="10.17487/RFC6242"/> </reference> <reference anchor="RFC6991" target="https://www.rfc-editor.org/info/rfc6991" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6991.xml"> <front> <title>Common YANG Data Types</title> <author fullname="J. Schoenwaelder" initials="J." role="editor" surname="Schoenwaelder"/> <date month="July" year="2013"/> <abstract> <t>This document introduces a collection of common data types to be used with the YANG data modeling language. This document obsoletes RFC 6021.</t> </abstract> </front> <seriesInfo name="RFC" value="6991"/> <seriesInfo name="DOI" value="10.17487/RFC6991"/> </reference> <reference anchor="RFC7950" target="https://www.rfc-editor.org/info/rfc7950" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7950.xml"> <front> <title>The YANG 1.1 Data Modeling Language</title> <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/> <date month="August" year="2016"/> <abstract> <t>YANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols. This document describes the syntax and semantics of version 1.1 of the YANG language. YANG version 1.1 is a maintenance release of the YANG language, addressing ambiguities and defects in the original specification. There are a small number of backward incompatibilities from YANG version 1. This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF).</t> </abstract> </front> <seriesInfo name="RFC" value="7950"/> <seriesInfo name="DOI" value="10.17487/RFC7950"/> </reference> <reference anchor="RFC8040" target="https://www.rfc-editor.org/info/rfc8040" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8040.xml"> <front> <title>RESTCONF Protocol</title> <author fullname="A. Bierman" initials="A." surname="Bierman"/> <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/> <author fullname="K. Watsen" initials="K." surname="Watsen"/> <date month="January" year="2017"/> <abstract> <t>This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF).</t> </abstract> </front> <seriesInfo name="RFC" value="8040"/> <seriesInfo name="DOI" value="10.17487/RFC8040"/> </reference> <reference anchor="RFC8341" target="https://www.rfc-editor.org/info/rfc8341" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8341.xml"> <front> <title>Network Configuration Access Control Model</title> <author fullname="A. Bierman" initials="A." surname="Bierman"/> <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/> <date month="March" year="2018"/> <abstract> <t>The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model.</t> <t>This document obsoletes RFC 6536.</t> </abstract> </front> <seriesInfo name="STD" value="91"/> <seriesInfo name="RFC" value="8341"/> <seriesInfo name="DOI" value="10.17487/RFC8341"/> </reference> <reference anchor="RFC8342" target="https://www.rfc-editor.org/info/rfc8342" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8342.xml"> <front> <title>Network Management Datastore Architecture (NMDA)</title> <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>1.0 (Fifth Edition)</title> <author initials="T." surname="Bray" fullname="Tim Bray"> <organization/> </author> <authorfullname="J. Schoenwaelder"initials="J."surname="Schoenwaelder"/> <author fullname="P. Shafer" initials="P." surname="Shafer"/> <author fullname="K. Watsen" initials="K." surname="Watsen"/> <author fullname="R. Wilton" initials="R." surname="Wilton"/> <date month="March" year="2018"/> <abstract> <t>Datastores are a fundamental concept binding the data models written in the YANG data modeling language to network management protocols such as the Network Configuration Protocol (NETCONF) and RESTCONF. This document defines an architectural framework for datastores based on the experience gained with the initial simpler model, addressing requirements that were not well supported in the initial model. This document updates RFC 7950.</t> </abstract> </front> <seriesInfo name="RFC" value="8342"/> <seriesInfo name="DOI" value="10.17487/RFC8342"/> </reference> <reference anchor="RFC8343" target="https://www.rfc-editor.org/info/rfc8343" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8343.xml"> <front> <title>A YANG Data Model for Interface Management</title>surname="Paoli" fullname="Jean Paoli"> <organization/> </author> <authorfullname="M. Bjorklund"initials="M."surname="Bjorklund"/> <date month="March" year="2018"/> <abstract> <t>This document defines a YANG data model for the management of network interfaces. It is expected that interface-type-specific data models augment the generic interfaces data model defined in this document. The data model includes definitions for configuration and system state (status information and counters for the collection of statistics).</t> <t>The YANG data model in this document conforms to the Network Management Datastore Architecture (NMDA) defined in RFC 8342.</t> <t>This document obsoletes RFC 7223.</t> </abstract> </front> <seriesInfo name="RFC" value="8343"/> <seriesInfo name="DOI" value="10.17487/RFC8343"/> </reference> <reference anchor="RFC8349" target="https://www.rfc-editor.org/info/rfc8349" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8349.xml"> <front> <title>A YANG Data Model for Routing Management (NMDA Version)</title> <author fullname="L. Lhotka" initials="L." surname="Lhotka"/> <author fullname="A. Lindem" initials="A." surname="Lindem"/> <author fullname="Y. Qu" initials="Y." surname="Qu"/> <date month="March" year="2018"/> <abstract> <t>This document specifies three YANG modules and one submodule. Together, they form the core routing data model that serves as a framework for configuring and managing a routing subsystem. It is expected that these modules will be augmented by additional YANG modules defining data models for control-plane protocols, route filters, and other functions. The core routing data model provides common building blocks for such extensions -- routes, Routing Information Bases (RIBs), and control-plane protocols.</t> <t>The YANG modules in this document conform to the Network Management Datastore Architecture (NMDA). This document obsoletes RFC 8022.</t> </abstract> </front> <seriesInfo name="RFC" value="8349"/> <seriesInfo name="DOI" value="10.17487/RFC8349"/> </reference> <reference anchor="RFC8446" target="https://www.rfc-editor.org/info/rfc8446" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8446.xml"> <front> <title>The Transport Layer Security (TLS) Protocol Version 1.3</title>surname="Sperberg-McQueen" fullname="Michael Sperberg-McQueen"> <organization/> </author> <authorfullname="E. Rescorla"initials="E."surname="Rescorla"/>surname="Maler" fullname="Eve Maler"> <organization/> </author> <author initials="F." surname="Yergeau" fullname="François Yergeau"> <organization/> </author> <datemonth="August" year="2018"/> <abstract> <t>This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery.</t> <t>This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations.</t> </abstract>month="November" year="2008"/> </front><seriesInfo name="RFC" value="8446"/> <seriesInfo name="DOI" value="10.17487/RFC8446"/><refcontent>World Wide Web Consortium Recommendation REC-xml-20081126</refcontent> </reference> </references> <references> <name>Informative References</name><reference anchor="RFC5714" target="https://www.rfc-editor.org/info/rfc5714" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5714.xml"> <front> <title>IP Fast Reroute Framework</title> <author fullname="M. Shand" initials="M." surname="Shand"/> <author fullname="S. Bryant" initials="S." surname="Bryant"/> <date month="January" year="2010"/> <abstract> <t>This document provides a framework for the development of IP fast- reroute mechanisms that provide protection against link or router failure by invoking locally determined repair paths. Unlike MPLS fast-reroute, the mechanisms are applicable to a network employing conventional IP routing and forwarding. This document is not an Internet Standards Track specification; it is published for informational purposes.</t> </abstract> </front> <seriesInfo name="RFC" value="5714"/> <seriesInfo name="DOI" value="10.17487/RFC5714"/> </reference> <reference anchor="RFC8340" target="https://www.rfc-editor.org/info/rfc8340" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8340.xml"> <front> <title>YANG Tree Diagrams</title> <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/> <author fullname="L. Berger" initials="L." role="editor" surname="Berger"/> <date month="March" year="2018"/> <abstract> <t>This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language.</t> </abstract> </front> <seriesInfo name="BCP" value="215"/> <seriesInfo name="RFC" value="8340"/> <seriesInfo name="DOI" value="10.17487/RFC8340"/> </reference> <reference anchor="RFC8792" target="https://www.rfc-editor.org/info/rfc8792" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8792.xml"> <front> <title>Handling Long Lines in Content of Internet-Drafts and RFCs</title> <author fullname="K. Watsen" initials="K." surname="Watsen"/> <author fullname="E. Auerswald" initials="E." surname="Auerswald"/> <author fullname="A. Farrel" initials="A." surname="Farrel"/> <author fullname="Q. Wu" initials="Q." surname="Wu"/> <date month="June" year="2020"/> <abstract> <t>This document defines two strategies for handling long lines in width-bounded text content. One strategy, called the "single backslash" strategy, is based on the historical use of a single backslash ('\') character to indicate where line-folding has occurred, with the continuation occurring with the first character that is not a space character (' ') on the next line. The second strategy, called the "double backslash" strategy, extends the first strategy by adding a second backslash character to identify where the continuation begins and is thereby able to handle cases not supported by the first strategy. Both strategies use a self-describing header enabling automated reconstitution of the original content.</t> </abstract> </front> <seriesInfo name="RFC" value="8792"/> <seriesInfo name="DOI" value="10.17487/RFC8792"/> </reference><xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5714.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7951.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8340.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8792.xml"/> </references> </references> <section anchor="full-tree" numbered="true" toc="default"> <name>Combined Tree Diagram</name> <t>This appendixincludesprovides the combined ietf-routing.yang, ietf-ipv4-unicast-routing.yang,ietf-ipv6-unicast-routing.yangietf-ipv6-unicast-routing.yang, andietf-rib-extensions.yangietf-rib-extension.yang tree diagram.</t><artwork name="" type="" align="left" alt=""><![CDATA[<sourcecode type="yangtree"><![CDATA[ module: ietf-routing +--rw routing +--rw router-id? yang:dotted-quad {router-id}? +--ro interfaces | +--ro interface* if:interface-ref +--rw control-plane-protocols | +--rw control-plane-protocol* [type name] | +--rw type identityref | +--rw name string | +--rw description? string | +--rw static-routes | +--rw v4ur:ipv4 | | +--rw v4ur:route* [destination-prefix] | | +--rw v4ur:destination-prefix inet:ipv4-prefix | | +--rw v4ur:description? string | | +--rw v4ur:next-hop | | +--rw (v4ur:next-hop-options) | | +--:(v4ur:simple-next-hop) | | | +--rw v4ur:outgoing-interface? | | | | if:interface-ref | | | +--rw v4ur:next-hop-address? | | | | inet:ipv4-address | | | +--rw rib-ext:preference? uint32 | | | +--rw rib-ext:tag? uint32 | | +--:(v4ur:special-next-hop) | | | +--rw v4ur:special-next-hop? enumeration | | +--:(v4ur:next-hop-list) | | +--rw v4ur:next-hop-list | | +--rw v4ur:next-hop* [index] | | +--rw v4ur:index string | | +--rw v4ur:outgoing-interface? | | | if:interface-ref | | +--rw v4ur:next-hop-address? | | | inet:ipv4-address | | +--rw rib-ext:preference? uint32 | | +--rw rib-ext:tag? uint32 | +--rw v6ur:ipv6 | +--rw v6ur:route* [destination-prefix] | +--rw v6ur:destination-prefix inet:ipv6-prefix | +--rw v6ur:description? string | +--rw v6ur:next-hop | +--rw (v6ur:next-hop-options) | +--:(v6ur:simple-next-hop) | | +--rw v6ur:outgoing-interface? | | | if:interface-ref | | +--rw v6ur:next-hop-address? | | | inet:ipv6-address | | +--rw rib-ext:preference? uint32 | | +--rw rib-ext:tag? uint32 | +--:(v6ur:special-next-hop) | | +--rw v6ur:special-next-hop? enumeration | +--:(v6ur:next-hop-list) | +--rw v6ur:next-hop-list | +--rw v6ur:next-hop* [index] | +--rw v6ur:index string | +--rw v6ur:outgoing-interface? | | if:interface-ref | +--rw v6ur:next-hop-address? | | inet:ipv6-address | +--rw rib-ext:preference? uint32 | +--rw rib-ext:tag? uint32 +--rw ribs +--rw rib* [name] +--rw name string +--rw address-family identityref +--ro default-rib? boolean {multiple-ribs}? +--ro routes | +--ro route* [] | +--ro route-preference? route-preference | +--ro next-hop | | +--ro (next-hop-options) | | +--:(simple-next-hop) | | | +--ro outgoing-interface? | | | | if:interface-ref | | | +--ro v4ur:next-hop-address? | | | | inet:ipv4-address | | | +--ro v6ur:next-hop-address? | | | | inet:ipv6-address | | | +--ro rib-ext:repair-path | | | +--ro rib-ext:outgoing-interface? | | | | if:interface-state-ref | | | +--ro rib-ext:next-hop-address? | | | | inet:ip-address-no-zone | | | +--ro rib-ext:metric? uint32 | | +--:(special-next-hop) | | | +--ro special-next-hop? enumeration | | +--:(next-hop-list) | | +--ro next-hop-list | | +--ro next-hop* [] | | +--ro outgoing-interface? | | | if:interface-ref | | +--ro v4ur:address? | | | inet:ipv4-address | | +--ro v6ur:address? | | | inet:ipv6-address | | +--ro rib-ext:repair-path | | +--ro rib-ext:outgoing-interface? | | | if:interface-state-ref | | +--ro rib-ext:next-hop-address? | | | inet:ip-address-no-zone | | +--ro rib-ext:metric? uint32 | +--ro source-protocol identityref | +--ro active? empty | +--ro last-updated? yang:date-and-time | +--ro v4ur:destination-prefix? inet:ipv4-prefix | +--ro v6ur:destination-prefix? inet:ipv6-prefix | +--ro rib-ext:metric? uint32 | +--ro rib-ext:tag* uint32 | +--ro rib-ext:application-tag? uint32 +---x active-route | +---w input | | +---w v4ur:destination-address? inet:ipv4-address | | +---w v6ur:destination-address? inet:ipv6-address | +--ro output | +--ro route | +--ro next-hop | | +--ro (next-hop-options) | | +--:(simple-next-hop) | | | +--ro outgoing-interface? | | | | if:interface-ref | | | +--ro v4ur:next-hop-address? | | | | inet:ipv4-address | | | +--ro v6ur:next-hop-address? | | | | inet:ipv6-address | | +--:(special-next-hop) | | | +--ro special-next-hop? enumeration | | +--:(next-hop-list) | | +--ro next-hop-list | | +--ro next-hop* [] | | +--ro outgoing-interface? | | | if:interface-ref | | +--ro v4ur:next-hop-address? | | | inet:ipv4-address | | +--ro v6ur:next-hop-address? | | | inet:ipv6-address | +--ro source-protocol identityref | +--ro active? empty | +--ro last-updated? yang:date-and-time | +--ro v4ur:destination-prefix? inet:ipv4-prefix | +--ro v6ur:destination-prefix? inet:ipv6-prefix +--rw description? string +--ro rib-ext:statistics +--ro rib-ext:total-routes? uint32 +--ro rib-ext:total-active-routes? uint32 +--ro rib-ext:total-route-memory? uint64 +--ro rib-ext:protocol-statistics* [] +--ro rib-ext:protocol? identityref +--ro rib-ext:routes? uint32 +--ro rib-ext:active-routes? uint32 +--ro rib-ext:route-memory? uint64]]></artwork>]]></sourcecode> </section> <section anchor="examples" numbered="true" toc="default"> <name>ietf-rib-extension.yang example</name> <t>The following is an XML example <xref target="W3C.REC-xml-20081126"/> using the RIB extension module and RFC 8349.</t><t>Note:<aside><t>Note: '\' line wrapping per <xref target="RFC8792"format="default"/>. </t> <artwork name="" type="" align="left" alt=""><![CDATA[format="default"/>.</t></aside> <sourcecode type="xml"><![CDATA[ <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing"> <control-plane-protocols> <control-plane-protocol> <type>static</type> <name>static-routing-protocol</name> <static-routes> <ipv4 xmlns="urn:ietf:params:xml:ns:yang:\ ietf-ipv4-unicast-routing"> <route> <destination-prefix>0.0.0.0/0</destination-prefix> <next-hop> <next-hop-address>192.0.2.2</next-hop-address> <preference xmlns="urn:ietf:params:xml:ns:yang:\ ietf-rib-extension">30</preference> <tag xmlns="urn:ietf:params:xml:ns:yang:\ ietf-rib-extension">99</tag> </next-hop> </route> </ipv4> <ipv6 xmlns="urn:ietf:params:xml:ns:yang:\ ietf-ipv6-unicast-routing"> <route> <destination-prefix>::/0</destination-prefix> <next-hop> <next-hop-address>2001:db8:aaaa::1111</next-hop-address> <preference xmlns="urn:ietf:params:xml:ns:yang:\ ietf-rib-extension">30</preference> <tag xmlns="urn:ietf:params:xml:ns:yang:\ ietf-rib-extension">66</tag> </next-hop> </route> </ipv6> </static-routes> </control-plane-protocol> </control-plane-protocols> <ribs> <rib> <name>ipv4-primary</name> <address-family xmlns:v4ur="urn:ietf:params:xml:ns:yang:\ ietf-ipv4-unicast-routing">v4ur:ipv4-unicast</address-family> <default-rib>true</default-rib> <routes> <route> <destination-prefix xmlns="urn:ietf:params:xml:ns:yang:\ ietf-ipv4-unicast-routing">0.0.0.0/0</destination-prefix> <next-hop> <next-hop-address xmlns="urn:ietf:params:xml:ns:yang:\ ietf-ipv4-unicast-routing">192.0.2.2</next-hop-address> </next-hop> <route-preference>5</route-preference> <source-protocol>static</source-protocol> <last-updated>2015-10-24T18:02:45+02:00</last-updated> </route> <route> <destination-prefix xmlns="urn:ietf:params:xml:ns:yang:\ ietf-ipv4-unicast-routing">198.51.100.0/24\ </destination-prefix> <next-hop> <next-hop-address xmlns="urn:ietf:params:xml:ns:yang:\ ietf-ipv4-unicast-routing">192.0.2.2</next-hop-address> <repair-path xmlns="urn:ietf:params:xml:ns:yang:\ ietf-rib-extension"> <next-hop-address>203.0.113.1</next-hop-address> <metric>200</metric> </repair-path> </next-hop><route-preference>110</route-preference><route-preference>120</route-preference> <source-protocolxmlns:ospf="urn:ietf:params:xml:ns:yang:\ ietf-ospf">ospf:ospf</source-protocol>xmlns:rip="urn:ietf:params:xml:ns:yang:\ ietf-rip">rip:rip</source-protocol> <last-updated>2015-10-24T18:02:45+02:00</last-updated> </route> </routes> </rib> <rib> <name>ipv6-primary</name> <address-family xmlns:v6ur="urn:ietf:params:xml:ns:yang:\ ietf-ipv6-unicast-routing">v6ur:ipv6-unicast</address-family> <default-rib>true</default-rib> <routes> <route> <destination-prefix xmlns="urn:ietf:params:xml:ns:yang:\ ietf-ipv6-unicast-routing">0::/0</destination-prefix> <next-hop> <next-hop-address xmlns="urn:ietf:params:xml:ns:yang:\ ietf-ipv6-unicast-routing">2001:db8:aaaa::1111\ </next-hop-address> </next-hop> <route-preference>5</route-preference> <source-protocol>static</source-protocol> <last-updated>2015-10-24T18:02:45+02:00</last-updated> </route> <route> <destination-prefix xmlns="urn:ietf:params:xml:ns:yang:\ ietf-ipv6-unicast-routing">2001:db8:bbbb::/64\ </destination-prefix> <next-hop> <next-hop-address xmlns="urn:ietf:params:xml:ns:yang:\ ietf-ipv6-unicast-routing">2001:db8:aaaa::1111\ </next-hop-address> <repair-path xmlns="urn:ietf:params:xml:ns:yang:\ ietf-rib-extension"> <next-hop-address>2001:db8:cccc::2222</next-hop-address> <metric>200</metric> </repair-path> </next-hop><route-preference>110</route-preference><route-preference>120</route-preference> <source-protocolxmlns:ospf="urn:ietf:params:xml:ns:yang:\ ietf-ospf">ospf:ospf</source-protocol>xmlns:rip="urn:ietf:params:xml:ns:yang:\ ietf-rip">rip:rip</source-protocol> <last-updated>2015-10-24T18:02:45+02:00</last-updated> </route> </routes> </rib> </ribs> </routing>]]></artwork>]]></sourcecode> <t>The following is the same example using JSONformat.</t> <artwork name="" type="" align="left" alt=""><![CDATA[format <xref target="RFC7951"/>.</t> <sourcecode type="json"><![CDATA[ { "ietf-routing:routing": { "control-plane-protocols": { "control-plane-protocol": [ { "type": "static", "name": "static-routing-protocol", "static-routes": { "ietf-ipv4-unicast-routing:ipv4": { "route": [ { "destination-prefix": "0.0.0.0/0", "next-hop": { "next-hop-address": "192.0.2.2", "ietf-rib-extension:preference": 30, "ietf-rib-extension:tag": 99 } } ] }, "ietf-ipv6-unicast-routing:ipv6": { "route": [ { "destination-prefix": "::/0", "next-hop": { "next-hop-address": "2001:db8:aaaa::1111", "ietf-rib-extension:preference": 30, "ietf-rib-extension:tag": 66 } } ] } } } ] }, "ribs": { "rib": [ { "name": "ipv4-primary", "address-family": "ietf-ipv4-unicast-routing:ipv4-unicast", "default-rib": true, "routes": { "route": [ { "next-hop": { "ietf-ipv4-unicast-routing:next-hop-address": \ "192.0.2.2" }, "route-preference": 5, "source-protocol": "static", "last-updated": "2015-10-24T18:02:45+02:00", "ietf-ipv4-unicast-routing:destination-prefix": \ "0.0.0.0/0" }, { "next-hop": { "ietf-rib-extension:repair-path": { "next-hop-address": "203.0.113.1", "metric": 200 }, "ietf-ipv4-unicast-routing:next-hop-address": \ "192.0.2.2" }, "route-preference":110,120, "source-protocol":"ietf-ospf:ospf","ietf-rip:rip", "last-updated": "2015-10-24T18:02:45+02:00", "ietf-ipv4-unicast-routing:destination-prefix": \ "198.51.100.0/24" } ] } }, { "name": "ipv6-primary", "address-family": "ietf-ipv6-unicast-routing:ipv6-unicast", "default-rib": true, "routes": { "route": [ { "next-hop": { "ietf-ipv6-unicast-routing:next-hop-address": \ "2001:db8:aaaa::1111" }, "route-preference": 5, "source-protocol": "static", "last-updated": "2015-10-24T18:02:45+02:00", "ietf-ipv6-unicast-routing:destination-prefix": "::/0" }, { "next-hop": { "ietf-rib-extension:repair-path": { "next-hop-address": "2001:db8:cccc::2222", "metric": 200 }, "ietf-ipv6-unicast-routing:next-hop-address": \ "2001:db8:aaaa::1111" }, "route-preference":110,120, "source-protocol":"ietf-ospf:ospf","ietf-rip:rip", "last-updated": "2015-10-24T18:02:45+02:00", "ietf-ipv6-unicast-routing:destination-prefix": \ "2001:db8:bbbb::/64" } ] } } ] } } }]]></artwork>]]></sourcecode> </section> <sectionnumbered="true"numbered="false" toc="default"> <name>Acknowledgments</name><t>The RFC text was produced using Marshall Rose's xml2rfc tool.</t><t> The authors wish to thankLes Ginsberg, Krishna Deevi, and Suyoung Yoon<contact fullname="Les Ginsberg"/>, <contact fullname="Krishna Deevi"/>, and <contact fullname="Suyoung Yoon"/> for their helpful comments and suggestions. </t> <t> The authors wish to thankTom Petch, Rob Wilton, Chris Hopps, Martin Bjorklund, Jeffrey Zhang, Eric Vyncke, Lars Eggert, and Bo Wu<contact fullname="Tom Petch"/>, <contact fullname="Rob Wilton"/>, <contact fullname="Chris Hopps"/>, <contact fullname="Martin Björklund"/>, <contact fullname="Jeffrey Zhang"/>, <contact fullname="Éric Vyncke"/>, <contact fullname="Lars Eggert"/>, and <contact fullname="Bo Wu"/> for their reviews and comments. </t> </section> </back> </rfc>