One document matched: draft-ietf-netmod-routing-cfg-18.xml
<?xml version="1.0"?>
<?rfc strict="yes"?>
<?rfc toc="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc docName="draft-ietf-netmod-routing-cfg-18" ipr="trust200902" category="std" obsoletes="" updates="" submissionType="IETF" xml:lang="en">
<front>
<title abbrev="YANG Routing Management">A YANG Data Model for
Routing Management</title>
<author initials="L." surname="Lhotka" fullname="Ladislav Lhotka">
<organization>CZ.NIC</organization>
<address>
<email>lhotka@nic.cz</email>
</address>
</author>
<author initials="A." surname="Lindem" fullname="Acee Lindem">
<organization>Cisco Systems</organization>
<address>
<email>acee@cisco.com</email>
</address>
</author>
<date day="17" month="April" year="2015"/>
<area>Operations and Management</area>
<workgroup>NETMOD Working Group</workgroup>
<abstract>
<t>This document contains a specification of three YANG modules.
Together they form the core routing data model which 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 routing protocols, route
filters and other functions. The core routing data model
provides common building blocks for such extensions - routing
instances, routes, routing information bases (RIB), and routing
protocols.</t>
</abstract>
</front>
<middle>
<section anchor="sec.introduction" title="Introduction" toc="default">
<t>This document contains a specification of the following YANG
modules:
<list style="symbols">
<t>Module "ietf-routing" provides generic components of a
routing data model.</t>
<t>Module "ietf-ipv4-unicast-routing" augments the
"ietf-routing" module with additional data specific to IPv4
unicast.</t>
<t>Module "ietf-ipv6-unicast-routing" augments the
"ietf-routing" module with additional data specific to IPv6
unicast, including the router configuration variables required
by <xref target="RFC4861" pageno="false" format="default"/>.</t>
</list></t>
<t>These modules together define the so-called core routing data
model, which is intended as a basis for future data model
development covering more sophisticated routing systems. While
these three modules can be directly used for simple IP devices
with static routing (see <xref target="app.minimum" pageno="false" format="default"/>), their
main purpose is to provide essential building blocks for more
complicated data models involving multiple routing protocols,
multicast routing, additional address families, and advanced
functions such as route filtering or policy routing. To this
end, it is expected that the core routing data model will be
augmented by numerous modules developed by other IETF working
groups.</t>
</section>
<section anchor="sec.term-not" title="Terminology and Notation" toc="default">
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
in this document are to be interpreted as described in <xref target="RFC2119" pageno="false" format="default"/>.</t>
<t>The following terms are defined in <xref target="RFC6241" pageno="false" format="default"/>:
<list style="symbols">
<t>client,</t>
<t>message,</t>
<t>protocol operation,</t>
<t>server.</t>
</list></t>
<t>The following terms are defined in <xref target="RFC6020" pageno="false" format="default"/>:
<list style="symbols">
<t>augment,</t>
<t>configuration data,</t>
<t>data model,</t>
<t>data node,</t>
<t>feature,</t>
<t>mandatory node,</t>
<t>module,</t>
<t>schema tree,</t>
<t>state data,</t>
<t>RPC operation.</t>
</list></t>
<section anchor="sec.new-terms" title="Glossary of New Terms" toc="default">
<t><list style="hanging">
<t hangText="core routing data model:"> YANG data model
comprising "ietf-routing", "ietf-ipv4-unicast-routing" and
"ietf-ipv6-unicast-routing" modules.</t>
<t hangText="direct route:">a route to a directly connected
network.</t>
<t hangText="routing information base (RIB):">An object
containing a list of routes together with other
information. See <xref target="sec.rib" pageno="false" format="default"/> for details.</t>
<t hangText="system-controlled entry:">An entry of a list in
state data ("config false") that is created by the system
independently of what has been explicitly configured. See
<xref target="sec.system-user" pageno="false" format="default"/> for details.</t>
<t hangText="user-controlled entry:">An entry of a list in
state data ("config false") that is created and deleted as a
direct consequence of certain configuration changes. See
<xref target="sec.system-user" pageno="false" format="default"/> for details.</t>
</list></t>
</section>
<section anchor="sec.tree-symbols" title="Tree Diagrams" toc="default">
<t>A simplified graphical representation of the complete data
tree is presented in <xref target="app.data-tree" pageno="false" format="default"/>, and similar
diagrams of its various subtrees appear in the main text.</t>
<t>The meaning of the symbols in these diagrams is as follows:
<list style="symbols">
<t>Brackets "[" and "]" enclose list keys.</t>
<t>Curly braces "{" and "}" contain names of optional features that
make the corresponding node conditional.</t>
<t>Abbreviations before data node names: "rw" means configuration
(read-write), "ro" state data (read-only), "-x" RPC operations, and
"-n" notifications.</t>
<t>Symbols after data node names: "?" means an optional node, "!" a
container with presence, and "*" denotes a "list" or "leaf-list".</t>
<t>Parentheses enclose choice and case nodes, and case nodes are
also marked with a colon (":").</t>
<t>Ellipsis ("...") stands for contents of subtrees that are not
shown.</t>
</list></t>
</section>
<section anchor="sec.prefixes" title="Prefixes in Data Node Names" toc="default">
<t>In this document, names of data nodes, RPC operations 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" pageno="false" format="default"/>.</t>
<texttable anchor="tab.prefixes" title="Prefixes and corresponding YANG modules" suppress-title="false" align="center" style="full">
<ttcol align="left">Prefix</ttcol>
<ttcol align="left">YANG module</ttcol>
<ttcol align="left">Reference</ttcol>
<c>if</c><c>ietf-interfaces</c><c><xref target="RFC7223" pageno="false" format="default"/></c>
<c>ip</c><c>ietf-ip</c><c><xref target="RFC7277" pageno="false" format="default"/></c>
<c>rt</c><c>ietf-routing</c><c><xref target="sec.mod-rt" pageno="false" format="default"/></c>
<c>v4ur</c><c>ietf-ipv4-unicast-routing</c>
<c><xref target="sec.mod-v4ur" pageno="false" format="default"/></c>
<c>v6ur</c><c>ietf-ipv6-unicast-routing</c>
<c><xref target="sec.mod-v6ur" pageno="false" format="default"/></c>
<c>yang</c><c>ietf-yang-types</c><c><xref target="RFC6991" pageno="false" format="default"/></c>
<c>inet</c><c>ietf-inet-types</c><c><xref target="RFC6991" pageno="false" format="default"/></c>
</texttable>
</section>
</section>
<section anchor="sec.objectives" title="Objectives" toc="default">
<t>The initial design of the core routing data model was driven by
the following objectives:
<list style="symbols">
<t>The data model should be suitable for the common address
families, in particular IPv4 and IPv6, and for unicast and
multicast routing, as well as Multiprotocol Label Switching
(MPLS).</t>
<t>A simple IP routing system, such as one that uses only
static routing, should be configurable in a simple way,
ideally without any need to develop additional YANG
modules.</t>
<t>On the other hand, the core routing framework must allow
for complicated implementations involving multiple routing
information bases (RIB) and multiple routing protocols, as
well as controlled redistributions of routing information.</t>
<t>Device vendors will want to map the data models built on this
generic framework to their proprietary data models and
configuration interfaces. Therefore, the framework should be
flexible enough to facilitate such a mapping and accommodate
data models with different logic.</t>
</list>
</t>
</section>
<section anchor="sec.design" title="The Design of the Core Routing Data Model" toc="default">
<t>The core routing data model consists of three YANG
modules. The first module, "ietf-routing", defines the generic
components of a routing system. The other two modules,
"ietf-ipv4-unicast-routing" and "ietf-ipv6-unicast-routing",
augment the "ietf-routing" module with additional data nodes
that are needed for IPv4 and IPv6 unicast routing,
respectively. Figures <xref target="fig.confdata" format="counter" pageno="false"/> and <xref target="fig.statedata" format="counter" pageno="false"/> show abridged views of the configuration and
state data hierarchies. See <xref target="app.data-tree" pageno="false" format="default"/> for
the complete data trees.</t>
<figure anchor="fig.confdata" title="Configuration data hierarchy." suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height="">
+--rw routing
+--rw routing-instance* [name]
+--rw name
+--rw type?
+--rw enabled?
+--rw router-id?
+--rw description?
+--rw interfaces
| +--rw interface*
+--rw routing-protocols
| +--rw routing-protocol* [type name]
| +--rw type
| +--rw name
| +--rw description?
| +--rw enabled?
| +--rw route-preference?
| +--rw static-routes
| ...
+--rw ribs
+--rw rib* [name]
+--rw name
+--rw address-family?
+--rw description?
</artwork>
</figure>
<figure anchor="fig.statedata" title="State data hierarchy." suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height="">
+--ro routing-state
+--ro routing-instance* [name]
+--ro name
+--ro type?
+--ro router-id?
+--ro interfaces
| +--ro interface*
+--ro routing-protocols
| +--ro routing-protocol* [type name]
| +--ro type
| +--ro name
| +--ro route-preference
+--ro ribs
+--ro rib* [name]
+--ro name
+--ro address-family
+--ro default-rib?
+--ro routes
...
</artwork>
</figure>
<t>As can be seen from Figures <xref target="fig.confdata" format="counter" pageno="false"/> and <xref target="fig.statedata" format="counter" pageno="false"/>, the core routing data model introduces
several generic components of a routing framework: routing
instances, RIBs containing lists of routes, and routing
protocols. <xref target="sec.building-blocks" pageno="false" format="default"/> describes these
components in more detail.</t>
<section anchor="sec.system-user" title="System-Controlled and User-Controlled List Entries" toc="default">
<t>The core routing data model defines several lists in the
schema tree, for example "routing-instance" or "rib", that
have to be populated with at least one entry in any properly
functioning device, and additional entries may be configured
by a client.</t>
<t>In such a list, the server creates the required item as a
so-called system-controlled entry in state data, i.e., inside
the "routing-state" container.</t>
<t>Additional entries may be created in the configuration by
a client, e.g., via the NETCONF protocol. These are so-called
user-controlled entries. If the server accepts a configured
user-controlled entry, then this entry also appears in the
state data version of the list.</t>
<t>Corresponding entries in both versions of the list (in
state data and configuration) have the same value of the list
key.</t>
<t>The user may also provide supplemental configuration of
system-controlled entries. To do so, the user creates a new
entry in the configuration with the desired contents. In order
to bind this entry with the corresponding entry in the
state data list, the key of the configuration entry has
to be set to the same value as the key of the state entry.</t>
<t>An example can be seen in <xref target="app.get-reply" pageno="false" format="default"/>: the
"/routing-state/routing-instance" list has a single
system-controlled entry whose "name" key has the value
"rtr0". This entry is configured by the
"/routing/routing-instance" entry whose "name" key is
also "rtr0".</t>
<t>Deleting a user-controlled entry from the configuration list
results in the removal of the corresponding entry in the
state data list. In contrast, if a system-controlled
entry is deleted from the configuration list, only the extra
configuration specified in that entry is removed but the
corresponding state data entry remains in the list.</t>
</section>
</section>
<section anchor="sec.building-blocks" title="Basic Building Blocks" toc="default">
<t>This section describes the essential components of the core
routing data model.</t>
<section anchor="sec.routing-instance" title="Routing Instance" toc="default">
<t>The core routing data model supports one or more routing
instances appearing as entries of the "routing-instance"
list. Each routing instance has separate configuration and
state data under "/rt:routing/rt:routing-instance" and
"/rt:routing-state/rt:routing-instance", respectively.</t>
<t>The semantics of the term "routing instance" is
deliberately left undefined. It is expected that future YANG
modules will define data models for specific types of routing
instances, such as VRF (virtual routing and forwarding)
instances that are used for BGP/MPLS virtual private
networks <xref target="RFC4364" pageno="false" format="default"/>. For each type of routing
instance, an identity derived from "rt:routing-instance" SHALL
be defined. This identity is then referred to by the value of
the "type" leaf (a child node of "routing-instance" list).</t>
<t>Each network layer interface has to be assigned to one or
more routing instances in order to be able to participate in
packet forwarding, routing protocols and other operations of
those routing instances. The assignment is accomplished by
placing a corresponding (system- or user-controlled) entry in
the leaf-list of routing instance interfaces
("rt:interface"). Each entry is the name of a configured
network layer interface, see the "ietf-interfaces"
module <xref target="RFC7223" pageno="false" format="default"/>.</t>
<section anchor="sec.4861" title="Parameters of IPv6 Routing Instance Interfaces" toc="default">
<t>YANG module "ietf-ipv6-unicast-routing" (<xref target="sec.mod-v6ur" pageno="false" format="default"/>) augments the configuration and
state data of interfaces with definitions of the following
variables as required by <xref target="RFC4861" pageno="false" format="default"/>,
sec. 6.2.1:
<list style="symbols">
<t>send-advertisements,</t>
<t>max-rtr-adv-interval,</t>
<t>min-rtr-adv-interval,</t>
<t>managed-flag,</t>
<t>other-config-flag,</t>
<t>link-mtu,</t>
<t>reachable-time,</t>
<t>retrans-timer,</t>
<t>cur-hop-limit,</t>
<t>default-lifetime,</t>
<t>prefix-list: a list of prefixes to be advertised.<vspace blankLines="1"/>The
following parameters are associated with each prefix in the
list:
<list style="symbols">
<t>valid-lifetime,</t>
<t>on-link-flag,</t>
<t>preferred-lifetime,</t>
<t>autonomous-flag.</t>
</list></t>
</list></t>
<t>NOTES:</t>
<t><list style="numbers">
<t>The "IsRouter" flag, which is also required by <xref target="RFC4861" pageno="false" format="default"/>, is implemented in the "ietf-ip" module
<xref target="RFC7277" pageno="false" format="default"/> (leaf "ip:forwarding").</t>
<t>The original specification <xref target="RFC4861" pageno="false" format="default"/>
allows the implementations to decide whether the
"valid-lifetime" and "preferred-lifetime" parameters remain
the same in consecutive advertisements, or decrement in real
time. However, the latter behavior seems problematic because
the values might be reset again to the (higher) configured
values after a configuration is reloaded. Moreover, no
implementation is known to use the decrementing
behavior. The "ietf-ipv6-unicast-routing" module therefore
assumes the former behavior with constant values.</t>
</list></t>
</section>
</section>
<section anchor="sec.route" title="Route" toc="default">
<t>Routes are basic elements of information in a routing
system. The core routing data model defines only the following
minimal set of route attributes:
<list style="symbols">
<t>"destination-prefix": IP prefix specifying the set of
destination addresses for which the route may be used. This
attribute is mandatory.</t>
<t>"route-preference": an integer value (also known as
administrative distance) that is used for selecting a
preferred route among routes with the same destination
prefix. A lower value means a more preferred route.</t>
<t>"next-hop": determines the action to be performed with a
packet.</t>
</list>
</t>
<t>Routes are primarily state data that appear as entries of
RIBs (<xref target="sec.rib" pageno="false" format="default"/>) but they may also be found in
configuration data, for example as manually configured static
routes. In the latter case, configurable route attributes are
generally a subset of route attributes described above.</t>
</section>
<section anchor="sec.rib" title="Routing Information Base (RIB)" toc="default">
<t>Every routing instance manages one or more routing
information bases (RIB). A RIB is a list of routes
complemented with administrative data. Each RIB contains only
routes of one address family. An address family is represented
by an identity derived from the "rt:address-family" base
identity.</t>
<t>In the core routing data model, RIBs are state data
represented as entries of the list
"/routing-state/routing-instance/ribs/rib". The contents of
RIBs are controlled and manipulated by routing protocol
operations which may result in route additions, removals and
modifications. This also includes manipulations via the
"static" and/or "direct" pseudo-protocols, see <xref target="sec.pseudoproto" pageno="false" format="default"/>.</t>
<t>Each routing instance has, for every supported address
family, one RIB marked as the so-called default RIB. Its role
is explained in <xref target="sec.proto" pageno="false" format="default"/>.</t>
<t>Simple router implementations that do not advertise the
feature "multiple-ribs" will typically create one
system-controlled RIB per routing instance and supported
address family, and mark it as the default RIB.</t>
<t>More complex router implementations advertising the
"multiple-ribs" feature support multiple RIBs per address
family that can be used for policy routing and other
purposes.</t>
</section>
<section anchor="sec.proto" title="Routing Protocol" toc="default">
<t>The core routing data model provides an open-ended framework
for defining multiple routing protocol instances within a routing
instance. Each routing protocol instance MUST be assigned a
type, which is an identity derived from the
"rt:routing-protocol" base identity. The core routing data model
defines two identities for the direct and static
pseudo-protocols (<xref target="sec.pseudoproto" pageno="false" format="default"/>).</t>
<t>Multiple routing protocol instances of the same type MAY be
configured within the same routing instance.</t>
<section anchor="sec.pseudoproto" title="Routing Pseudo-Protocols" toc="default">
<t>The core routing data model defines two special routing
protocol types - "direct" and "static". Both are in fact
pseudo-protocols, which means they are confined to the local
device and do not exchange any routing information with
adjacent routers.</t>
<t>Every routing instance MUST implement exactly one
instance of the "direct" pseudo-protocol type. It is the
source of direct routes for all configured address
families. Direct routes are normally supplied by the
operating system kernel, based on the configuration of
network interface addresses, see <xref target="sec.ietf-ip" pageno="false" format="default"/>. Direct routes MUST be installed in
default RIBs of all supported address families.</t>
<t>A pseudo-protocol of the type "static" allows for specifying
routes manually. It MAY be configured in zero or multiple
instances, although a typical configuration will have exactly
one instance per routing instance.</t>
</section>
<section anchor="sec.newproto" title="Defining New Routing Protocols" toc="default">
<t>It is expected that future YANG modules will create data
models for additional routing protocol types. Such a new
module has to define the protocol-specific configuration and
state data, and it has to fit it into the core routing
framework in the following way:
<list style="symbols">
<t>A new identity MUST be defined for the routing protocol
and its base identity MUST be set to "rt:routing-protocol",
or to an identity derived from "rt:routing-protocol".</t>
<t>Additional route attributes MAY be defined, preferably in
one place by means of defining a YANG grouping. The new
attributes have to be inserted by augmenting the definitions
of the nodes
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height="">
/rt:routing-state/rt:ribs/rt:rib/rt:routes/rt:route
</artwork>
</figure>
and
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height="">
/rt:fib-route/rt:output/rt:route,
</artwork>
</figure>
and possibly other places in the configuration, state
data, notifications, and RPC input or output.</t>
<t>Configuration parameters and/or state data for the new
protocol can be defined by augmenting the
"routing-protocol" data node under both "/routing" and "/routing-state".</t>
<t>Per-interface configuration, including activation of
the routing protocol on individual interfaces, can use
references to entries in the leaf-list of routing
instance's interfaces (rt:interface).</t>
</list></t>
<t>By using the "when" statement, the augmented configuration
parameters and state data specific to the new protocol SHOULD
be made conditional and valid only if the value of "rt:type"
or "rt:source-protocol" is equal to the new protocol's
identity. It is also RECOMMENDED that protocol-specific data
nodes be encapsulated in appropriately named containers.</t>
<t>The above steps are implemented by the example YANG module
for the RIP routing protocol in <xref target="app.rip" pageno="false" format="default"/>.</t>
</section>
</section>
<section anchor="sec.rpcs" title="RPC Operations" toc="default">
<t>The "ietf-routing" module defines one RPC operation:
<list style="symbols">
<t>fib-route: query a routing instance for the active route
in the Forwarding Information Base (FIB). It is the route
that is currently used for sending datagrams to a
destination host whose address is passed as an input
parameter.</t>
</list></t>
</section>
</section>
<section anchor="sec.interactions" title="Interactions with Other YANG Modules" toc="default">
<t>The semantics of the core routing data model also depends on
several configuration parameters that are defined in other YANG
modules.</t>
<section anchor="sec.ietf-if" title="Module "ietf-interfaces"" toc="default">
<t>The following boolean switch is defined in the
"ietf-interfaces" YANG module <xref target="RFC7223" pageno="false" format="default"/>:
<list style="hanging">
<t hangText="/if:interfaces/if:interface/if:enabled">
<vspace blankLines="1"/>
If this switch is set to "false" for a network layer
interface, the device MUST behave exactly as if that
interface was not assigned to any routing instance at all.
</t>
</list>
</t>
</section>
<section anchor="sec.ietf-ip" title="Module "ietf-ip"" toc="default">
<t>The following boolean switches are defined in the "ietf-ip"
YANG module <xref target="RFC7277" pageno="false" format="default"/>:
<list style="hanging">
<t hangText="/if:interfaces/if:interface/ip:ipv4/ip:enabled">
<vspace blankLines="1"/>
If this switch is set to "false" for a network layer
interface, then all IPv4 routing functions related to that
interface MUST be disabled.
</t>
<t hangText="/if:interfaces/if:interface/ip:ipv4/ip:forwarding">
<vspace blankLines="1"/>
If this switch is set to "false" for a network layer
interface, then the forwarding of IPv4 datagrams to and from
this interface MUST be disabled. However, the interface may
participate in other IPv4 routing functions, such as routing
protocols.
</t>
<t hangText="/if:interfaces/if:interface/ip:ipv6/ip:enabled">
<vspace blankLines="1"/>
If this switch is set to "false" for a network layer
interface, then all IPv6 routing functions related to that
interface MUST be disabled.
</t>
<t hangText="/if:interfaces/if:interface/ip:ipv6/ip:forwarding">
<vspace blankLines="1"/>
If this switch is set to "false" for a network layer
interface, then the forwarding of IPv6 datagrams to and from
this interface MUST be disabled. However, the interface may
participate in other IPv6 routing functions, such as routing
protocols.
</t>
</list>
</t>
<t>In addition, the "ietf-ip" module allows for configuring IPv4
and IPv6 addresses and network prefixes or masks on network
layer interfaces. Configuration of these parameters on an
enabled interface MUST result in an immediate creation of the
corresponding direct route. The destination prefix of this route
is set according to the configured IP address and network
prefix/mask, and the interface is set as the outgoing interface
for that route.</t>
</section>
</section>
<section anchor="sec.mod-rt" title="Routing Management YANG Module" toc="default">
<t>RFC Editor: In this section, replace all occurrences of 'XXXX'
with the actual RFC number and all occurrences of the revision date
below with the date of RFC publication (and remove this note).</t>
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height="">
<CODE BEGINS> file "ietf-routing@2015-04-17.yang"
module ietf-routing {
namespace "urn:ietf:params:xml:ns:yang:ietf-routing";
prefix "rt";
import ietf-yang-types {
prefix "yang";
}
import ietf-interfaces {
prefix "if";
}
organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group";
contact
"WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:netmod@ietf.org>
WG Chair: Thomas Nadeau
<mailto:tnadeau@lucidvision.com>
WG Chair: Juergen Schoenwaelder
<mailto:j.schoenwaelder@jacobs-university.de>
Editor: Ladislav Lhotka
<mailto:lhotka@nic.cz>";
description
"This YANG module defines essential components for the management
of a routing subsystem.
Copyright (c) 2014 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 Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and
'OPTIONAL' in the module text are to be interpreted as described
in RFC 2119 (http://tools.ietf.org/html/rfc2119).
This version of this YANG module is part of RFC XXXX
(http://tools.ietf.org/html/rfcXXXX); see the RFC itself for
full legal notices.";
revision 2015-04-17 {
description
"Initial revision.";
reference
"RFC XXXX: A YANG Data Model for Routing Management";
}
/* Features */
feature multiple-ribs {
description
"This feature indicates that the server supports user-defined
RIBs.
Servers that do not advertise this feature SHOULD provide
exactly one system-controlled RIB per routing-instance and
supported address family and make them also the default RIBs.
These RIBs then appear as entries of the list
/routing-state/routing-instance/ribs/rib.";
}
feature router-id {
description
"This feature indicates that the server supports configuration
of an explicit 32-bit router ID that is used by some routing
protocols.
Servers that do not advertise this feature set a router ID
algorithmically, usually to one of configured IPv4 addresses.
However, this algorithm is implementation-specific.";
}
/* Identities */
identity address-family {
description
"Base identity from which identities describing address
families are derived.";
}
identity ipv4 {
base address-family;
description
"This identity represents IPv4 address family.";
}
identity ipv6 {
base address-family;
description
"This identity represents IPv6 address family.";
}
identity routing-instance {
description
"Base identity from which identities describing routing
instance types are derived.";
}
identity default-routing-instance {
base routing-instance;
description
"This identity represents either a default routing instance, or
the only routing instance on systems that do not support
multiple instances.";
}
identity routing-protocol {
description
"Base identity from which routing protocol identities are
derived.";
}
identity direct {
base routing-protocol;
description
"Routing pseudo-protocol that provides routes to directly
connected networks.";
}
identity static {
base routing-protocol;
description
"Static routing pseudo-protocol.";
}
/* Type Definitions */
typedef routing-instance-ref {
type leafref {
path "/rt:routing/rt:routing-instance/rt:name";
}
description
"This type is used for leafs that reference a routing instance
configuration.";
}
typedef routing-instance-state-ref {
type leafref {
path "/rt:routing-state/rt:routing-instance/rt:name";
}
description
"This type is used for leafs that reference state data of a
routing instance.";
}
typedef route-preference {
type uint32;
description
"This type is used for route preferences.";
}
/* Groupings */
grouping address-family {
description
"This grouping provides a leaf identifying an address
family.";
leaf address-family {
type identityref {
base address-family;
}
mandatory "true";
description
"Address family.";
}
}
grouping router-id {
description
"This grouping provides router ID.";
leaf router-id {
type yang:dotted-quad;
description
"A 32-bit number in the form of a dotted quad that is used by
some routing protocols identifying a router.";
reference
"RFC 2328: OSPF Version 2.";
}
}
grouping special-next-hop {
description
"This grouping provides a leaf with an enumeration of special
next-hops.";
leaf special-next-hop {
type enumeration {
enum blackhole {
description
"Silently discard the packet.";
}
enum unreachable {
description
"Discard the packet and notify the sender with an error
message indicating that the destination host is
unreachable.";
}
enum prohibit {
description
"Discard the packet and notify the sender with an error
message indicating that the communication is
administratively prohibited.";
}
enum receive {
description
"The packet will be received by the local system.";
}
}
description
"Special next-hop options.";
}
}
grouping next-hop-content {
description
"Generic parameters of next-hops in static routes.";
choice next-hop-options {
mandatory "true";
description
"Options for next-hops in static routes.
It is expected that other cases will be added through
augments from other modules, e.g., for Equal-Cost Multipath
routing (ECMP).";
case simple-next-hop {
description
"Simple next-hop is specified as an outgoing interface,
next-hop address or both.
Address-family-specific modules are expected to provide
'next-hop-address' leaf via augmentation.";
leaf outgoing-interface {
type leafref {
path "/rt:routing/rt:routing-instance/rt:interfaces/"
+ "rt:interface";
}
description
"Name of the outgoing interface.";
}
}
case special-next-hop {
uses special-next-hop;
}
}
}
grouping next-hop-state-content {
description
"Generic parameters of next-hops in state data.";
choice next-hop-options {
mandatory "true";
description
"Options for next-hops in state data.
It is expected that other cases will be added through
augments from other modules, e.g., for ECMP or recursive
next-hops.";
case simple-next-hop {
description
"Simple next-hop is specified as an outgoing interface,
next-hop address or both.
Address-family-specific modules are expected to provide
'next-hop-address' leaf via augmentation.";
leaf outgoing-interface {
type leafref {
path "/rt:routing-state/rt:routing-instance/"
+ "rt:interfaces/rt:interface";
}
description
"Name of the outgoing interface.";
}
}
case special-next-hop {
uses special-next-hop;
}
}
}
grouping route-metadata {
description
"Common route metadata.";
leaf source-protocol {
type identityref {
base routing-protocol;
}
mandatory "true";
description
"Type of the routing protocol from which the route
originated.";
}
leaf active {
type empty;
description
"Presence of this leaf indicates that the route is preferred
among all routes in the same RIB that have the same
destination prefix.";
}
leaf last-updated {
type yang:date-and-time;
description
"Time stamp of the last modification of the route. If the
route was never modified, it is the time when the route was
inserted into the RIB.";
}
}
/* State data */
augment "/if:interfaces-state/if:interface" {
description
"This augment adds a wrapped leaf-list to interface state
data.";
leaf routing-instance {
type routing-instance-state-ref;
must "../if:name=/rt:routing-state/"
+ "rt:routing-instance[rt:name=current()]/rt:interfaces/"
+ "rt:interface" {
error-message
"The interface is not assigned to the routing instance.";
description
"The reference must mirror a corresponding assignment under
routing-instance.";
}
description
"The name of the routing instance to which the interface is
assigned.";
}
}
container routing-state {
config "false";
description
"State data of the routing subsystem.";
list routing-instance {
key "name";
min-elements "1";
description
"Each list entry is a container for state data of a routing
instance.
An implementation MUST support routing instance(s) of the
type 'rt:default-routing-instance', and MAY support other
types. An implementation MAY restrict the number of routing
instances of each supported type.
An implementation SHOULD create at least one
system-controlled instance, and MAY allow the clients to
create user-controlled routing instances in
configuration.";
leaf name {
type string;
description
"The name of the routing instance.
For system-controlled instances the name is persistent,
i.e., it SHOULD NOT change across reboots.";
}
leaf type {
type identityref {
base routing-instance;
}
description
"The routing instance type.";
}
uses router-id {
description
"Global router ID.
It may be either configured or assigned algorithmically by
the implementation.";
}
container interfaces {
description
"Network layer interfaces belonging to the routing
instance.";
leaf-list interface {
type if:interface-state-ref;
description
"Each entry is a reference to the name of a configured
network layer interface.";
}
}
container routing-protocols {
description
"Container for the list of routing protocol instances.";
list routing-protocol {
key "type name";
description
"State data of a routing protocol instance.
An implementation MUST provide exactly one
system-controlled instance of the type 'direct'. Other
instances MAY be created by configuration.";
leaf type {
type identityref {
base routing-protocol;
}
description
"Type of the routing protocol.";
}
leaf name {
type string;
description
"The name of the routing protocol instance.
For system-controlled instances this name is
persistent, i.e., it SHOULD NOT change across
reboots.";
}
leaf route-preference {
type route-preference;
mandatory "true";
description
"The value of route preference (administrative
distance) assigned to all routes generated by the
routing protocol instance. A lower value means a more
preferred route.";
}
}
}
container ribs {
description
"Container for RIBs.";
list rib {
key "name";
min-elements "1";
description
"Each entry represents a RIB identified by the 'name'
key. All routes in a RIB MUST belong to the same address
family.
For each routing instance, an implementation SHOULD
provide one system-controlled default RIB for each
supported address family.";
leaf name {
type string;
description
"The name of the RIB.";
}
uses address-family;
leaf default-rib {
if-feature multiple-ribs;
type boolean;
default "true";
description
"This flag has the value of 'true' if and only if the
RIB is the default RIB for the given address family.
A default RIB always receives direct routes. By
default it also receives routes from all routing
protocols.";
}
container routes {
description
"Current content of the RIB.";
list route {
description
"A RIB route entry. This data node MUST be augmented
with information specific for routes of each address
family.";
leaf route-preference {
type route-preference;
description
"This route attribute, also known as administrative
distance, allows for selecting the preferred route
among routes with the same destination prefix. A
smaller value means a more preferred route.";
}
container next-hop {
description
"Route's next-hop attribute.";
uses next-hop-state-content;
}
uses route-metadata;
}
}
}
}
}
}
/* Configuration Data */
container routing {
description
"Configuration parameters for the routing subsystem.";
list routing-instance {
key "name";
description
"Configuration of a routing instance.";
leaf name {
type string;
description
"The name of the routing instance.
For system-controlled entries, the value of this leaf must
be the same as the name of the corresponding entry in
state data.
For user-controlled entries, an arbitrary name can be
used.";
}
leaf type {
type identityref {
base routing-instance;
}
default "rt:default-routing-instance";
description
"The type of the routing instance.";
}
leaf enabled {
type boolean;
default "true";
description
"Enable/disable the routing instance.
If this parameter is false, the parent routing instance is
disabled and does not appear in state data, despite any
other configuration that might be present.";
}
uses router-id {
if-feature router-id;
description
"Configuration of the global router ID. Routing protocols
that use router ID can use this parameter or override it
with another value.";
}
leaf description {
type string;
description
"Textual description of the routing instance.";
}
container interfaces {
description
"Assignment of the routing instance's interfaces.";
leaf-list interface {
type if:interface-ref;
description
"The name of a configured network layer interface to be
assigned to the routing-instance.";
}
}
container routing-protocols {
description
"Configuration of routing protocol instances.";
list routing-protocol {
key "type name";
description
"Each entry contains configuration of a routing protocol
instance.";
leaf type {
type identityref {
base routing-protocol;
}
description
"Type of the routing protocol - an identity derived
from the 'routing-protocol' base identity.";
}
leaf name {
type string;
description
"An arbitrary name of the routing protocol instance.";
}
leaf description {
type string;
description
"Textual description of the routing protocol
instance.";
}
leaf enabled {
type boolean;
default "true";
description
"Enable/disable the routing protocol instance.
If this parameter is false, the parent routing
protocol instance is disabled and does not appear in
state data, despite any other configuration that might
be present.";
}
leaf route-preference {
type route-preference;
description
"The value of route preference (administrative
distance).
The default value depends on the routing protocol
type, and may also be implementation-dependent.";
}
container static-routes {
when "../type='rt:static'" {
description
"This container is only valid for the 'static'
routing protocol.";
}
description
"Configuration of the 'static' pseudo-protocol.
Address-family-specific modules augment this node with
their lists of routes.";
}
}
}
container ribs {
description
"Configuration of RIBs.";
list rib {
key "name";
description
"Each entry contains configuration for a RIB identified
by the 'name' key.
Entries having the same key as a system-controlled entry
of the list /routing-state/routing-instance/ribs/rib are
used for configuring parameters of that entry. Other
entries define additional user-controlled RIBs.";
leaf name {
type string;
description
"The name of the RIB.
For system-controlled entries, the value of this leaf
must be the same as the name of the corresponding
entry in state data.
For user-controlled entries, an arbitrary name can be
used.";
}
uses address-family {
description
"Address family of the RIB.
It is mandatory for user-controlled RIBs. For
system-controlled RIBs it can be omitted, otherwise it
must match the address family of the corresponding
state entry.";
refine "address-family" {
mandatory "false";
}
}
leaf description {
type string;
description
"Textual description of the RIB.";
}
}
}
}
}
/* RPC operations */
rpc fib-route {
description
"Return the active FIB route that a routing-instance uses for
sending packets to a destination address.";
input {
leaf routing-instance-name {
type routing-instance-state-ref;
mandatory "true";
description
"Name of the routing instance whose forwarding information
base is being queried.
If the routing instance with name equal to the value of
this parameter doesn't exist, then this operation SHALL
fail with error-tag 'data-missing' and error-app-tag
'routing-instance-not-found'.";
}
container destination-address {
description
"Network layer destination address.
Address family specific modules MUST augment this
container with a leaf named 'address'.";
uses address-family;
}
}
output {
container route {
description
"The active FIB route for the specified destination.
If the routing instance has no active FIB route for the
destination address, no output is returned - the server
SHALL send an <rpc-reply> containing a single element
<ok>.
Address family specific modules MUST augment this list
with appropriate route contents.";
uses address-family;
container next-hop {
description
"Route's next-hop attribute.";
uses next-hop-state-content;
}
uses route-metadata;
}
}
}
}
<CODE ENDS></artwork>
</figure>
</section>
<section anchor="sec.mod-v4ur" title="IPv4 Unicast Routing Management YANG Module" toc="default">
<t>RFC Editor: In this section, replace all occurrences of 'XXXX'
with the actual RFC number and all occurrences of the revision date
below with the date of RFC publication (and remove this note).</t>
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height="">
<CODE BEGINS> file "ietf-ipv4-unicast-routing@2015-04-17.yang"
module ietf-ipv4-unicast-routing {
namespace "urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing";
prefix "v4ur";
import ietf-routing {
prefix "rt";
}
import ietf-inet-types {
prefix "inet";
}
organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group";
contact
"WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:netmod@ietf.org>
WG Chair: Thomas Nadeau
<mailto:tnadeau@lucidvision.com>
WG Chair: Juergen Schoenwaelder
<mailto:j.schoenwaelder@jacobs-university.de>
Editor: Ladislav Lhotka
<mailto:lhotka@nic.cz>";
description
"This YANG module augments the 'ietf-routing' module with basic
configuration and state data for IPv4 unicast routing.
Copyright (c) 2014 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 Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and
'OPTIONAL' in the module text are to be interpreted as described
in RFC 2119 (http://tools.ietf.org/html/rfc2119).
This version of this YANG module is part of RFC XXXX
(http://tools.ietf.org/html/rfcXXXX); see the RFC itself for
full legal notices.";
revision 2015-04-17 {
description
"Initial revision.";
reference
"RFC XXXX: A YANG Data Model for Routing Management";
}
/* Identities */
identity ipv4-unicast {
base rt:ipv4;
description
"This identity represents the IPv4 unicast address family.";
}
/* State data */
augment "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/"
+ "rt:routes/rt:route" {
when "../../rt:address-family = 'v4ur:ipv4-unicast'" {
description
"This augment is valid only for IPv4 unicast.";
}
description
"This leaf augments an IPv4 unicast route.";
leaf destination-prefix {
type inet:ipv4-prefix;
description
"IPv4 destination prefix.";
}
}
augment "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/"
+ "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/"
+ "rt:simple-next-hop" {
when "../../../rt:address-family = 'v4ur:ipv4-unicast'" {
description
"This augment is valid only for IPv4 unicast.";
}
description
"This leaf augments the 'simple-next-hop' case of IPv4 unicast
routes.";
leaf next-hop-address {
type inet:ipv4-address;
description
"IPv4 address of the next-hop.";
}
}
/* Configuration data */
augment "/rt:routing/rt:routing-instance/rt:routing-protocols/"
+ "rt:routing-protocol/rt:static-routes" {
description
"This augment defines the configuration of the 'static'
pseudo-protocol with data specific to IPv4 unicast.";
container ipv4 {
description
"Configuration of a 'static' pseudo-protocol instance
consists of a list of routes.";
list route {
key "destination-prefix";
ordered-by "user";
description
"A user-ordered list of static routes.";
leaf destination-prefix {
type inet:ipv4-prefix;
mandatory "true";
description
"IPv4 destination prefix.";
}
leaf description {
type string;
description
"Textual description of the route.";
}
container next-hop {
description
"Configuration of next-hop.";
uses rt:next-hop-content {
augment "next-hop-options" {
description
"Add next-hop address case.";
leaf next-hop-address {
type inet:ipv4-address;
description
"IPv4 address of the next-hop.";
}
}
}
}
}
}
}
/* RPC operations */
augment "/rt:fib-route/rt:input/rt:destination-address" {
when "rt:address-family='v4ur:ipv4-unicast'" {
description
"This augment is valid only for IPv4 unicast.";
}
description
"This leaf augments the 'rt:destination-address' parameter of
the 'rt:fib-route' operation.";
leaf address {
type inet:ipv4-address;
description
"IPv4 destination address.";
}
}
augment "/rt:fib-route/rt:output/rt:route" {
when "rt:address-family='v4ur:ipv4-unicast'" {
description
"This augment is valid only for IPv4 unicast.";
}
description
"This leaf augments the reply to the 'rt:fib-route'
operation.";
leaf destination-prefix {
type inet:ipv4-prefix;
description
"IPv4 destination prefix.";
}
}
augment "/rt:fib-route/rt:output/rt:route/rt:next-hop/"
+ "rt:next-hop-options/rt:simple-next-hop" {
when "../rt:address-family='v4ur:ipv4-unicast'" {
description
"This augment is valid only for IPv4 unicast.";
}
description
"This leaf augments the 'simple-next-hop' case in the reply to
the 'rt:fib-route' operation.";
leaf next-hop-address {
type inet:ipv4-address;
description
"IPv4 address of the next-hop.";
}
}
}
<CODE ENDS></artwork>
</figure>
</section>
<section anchor="sec.mod-v6ur" title="IPv6 Unicast Routing Management YANG Module" toc="default">
<t>RFC Editor: In this section, replace all occurrences of 'XXXX'
with the actual RFC number and all occurrences of the revision date
below with the date of RFC publication (and remove this note).</t>
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height="">
<CODE BEGINS> file "ietf-ipv6-unicast-routing@2015-04-17.yang"
module ietf-ipv6-unicast-routing {
namespace "urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing";
prefix "v6ur";
import ietf-routing {
prefix "rt";
}
import ietf-inet-types {
prefix "inet";
}
import ietf-interfaces {
prefix "if";
}
import ietf-ip {
prefix "ip";
}
organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group";
contact
"WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:netmod@ietf.org>
WG Chair: Thomas Nadeau
<mailto:tnadeau@lucidvision.com>
WG Chair: Juergen Schoenwaelder
<mailto:j.schoenwaelder@jacobs-university.de>
Editor: Ladislav Lhotka
<mailto:lhotka@nic.cz>";
description
"This YANG module augments the 'ietf-routing' module with basic
configuration and state data for IPv6 unicast routing.
Copyright (c) 2014 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 Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and
'OPTIONAL' in the module text are to be interpreted as described
in RFC 2119 (http://tools.ietf.org/html/rfc2119).
This version of this YANG module is part of RFC XXXX
(http://tools.ietf.org/html/rfcXXXX); see the RFC itself for
full legal notices.";
revision 2015-04-17 {
description
"Initial revision.";
reference
"RFC XXXX: A YANG Data Model for Routing Management";
}
/* Identities */
identity ipv6-unicast {
base rt:ipv6;
description
"This identity represents the IPv6 unicast address family.";
}
/* State data */
augment "/if:interfaces-state/if:interface/ip:ipv6" {
description
"Augment interface state data with IPv6-specific parameters of
router interfaces.";
container ipv6-router-advertisements {
description
"Parameters of IPv6 Router Advertisements.";
leaf send-advertisements {
type boolean;
description
"A flag indicating whether or not the router sends periodic
Router Advertisements and responds to Router
Solicitations.";
}
leaf max-rtr-adv-interval {
type uint16 {
range "4..1800";
}
units "seconds";
description
"The maximum time allowed between sending unsolicited
multicast Router Advertisements from the interface.";
}
leaf min-rtr-adv-interval {
type uint16 {
range "3..1350";
}
units "seconds";
description
"The minimum time allowed between sending unsolicited
multicast Router Advertisements from the interface.";
}
leaf managed-flag {
type boolean;
description
"The value that is placed in the 'Managed address
configuration' flag field in the Router Advertisement.";
}
leaf other-config-flag {
type boolean;
description
"The value that is placed in the 'Other configuration' flag
field in the Router Advertisement.";
}
leaf link-mtu {
type uint32;
description
"The value that is placed in MTU options sent by the
router. A value of zero indicates that no MTU options are
sent.";
}
leaf reachable-time {
type uint32 {
range "0..3600000";
}
units "milliseconds";
description
"The value that is placed in the Reachable Time field in
the Router Advertisement messages sent by the router. A
value of zero means unspecified (by this router).";
}
leaf retrans-timer {
type uint32;
units "milliseconds";
description
"The value that is placed in the Retrans Timer field in the
Router Advertisement messages sent by the router. A value
of zero means unspecified (by this router).";
}
leaf cur-hop-limit {
type uint8;
description
"The value that is placed in the Cur Hop Limit field in the
Router Advertisement messages sent by the router. A value
of zero means unspecified (by this router).";
}
leaf default-lifetime {
type uint16 {
range "0..9000";
}
units "seconds";
description
"The value that is placed in the Router Lifetime field of
Router Advertisements sent from the interface, in seconds.
A value of zero indicates that the router is not to be
used as a default router.";
}
container prefix-list {
description
"A list of prefixes that are placed in Prefix Information
options in Router Advertisement messages sent from the
interface.
By default, these are all prefixes that the router
advertises via routing protocols as being on-link for the
interface from which the advertisement is sent.";
list prefix {
key "prefix-spec";
description
"Advertised prefix entry and its parameters.";
leaf prefix-spec {
type inet:ipv6-prefix;
description
"IPv6 address prefix.";
}
leaf valid-lifetime {
type uint32;
units "seconds";
description
"The value that is placed in the Valid Lifetime in the
Prefix Information option. The designated value of all
1's (0xffffffff) represents infinity.
An implementation SHOULD keep this value constant in
consecutive advertisements except when it is
explicitly changed in configuration.";
}
leaf on-link-flag {
type boolean;
description
"The value that is placed in the on-link flag ('L-bit')
field in the Prefix Information option.";
}
leaf preferred-lifetime {
type uint32;
units "seconds";
description
"The value that is placed in the Preferred Lifetime in
the Prefix Information option, in seconds. The
designated value of all 1's (0xffffffff) represents
infinity.
An implementation SHOULD keep this value constant in
consecutive advertisements except when it is
explicitly changed in configuration.";
}
leaf autonomous-flag {
type boolean;
description
"The value that is placed in the Autonomous Flag field
in the Prefix Information option.";
}
}
}
}
}
augment "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/"
+ "rt:routes/rt:route" {
when "../../rt:address-family = 'v6ur:ipv6-unicast'" {
description
"This augment is valid only for IPv6 unicast.";
}
description
"This leaf augments an IPv6 unicast route.";
leaf destination-prefix {
type inet:ipv6-prefix;
description
"IPv6 destination prefix.";
}
}
augment "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/"
+ "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/"
+ "rt:simple-next-hop" {
when "../../../rt:address-family = 'v6ur:ipv6-unicast'" {
description
"This augment is valid only for IPv6 unicast.";
}
description
"This leaf augments the 'simple-next-hop' case of IPv6 unicast
routes.";
leaf next-hop-address {
type inet:ipv6-address;
description
"IPv6 address of the next-hop.";
}
}
/* Configuration data */
augment "/if:interfaces/if:interface/ip:ipv6" {
description
"Augment interface configuration with IPv6-specific parameters
of router interfaces.";
container ipv6-router-advertisements {
description
"Configuration of IPv6 Router Advertisements.";
leaf send-advertisements {
type boolean;
default "false";
description
"A flag indicating whether or not the router sends periodic
Router Advertisements and responds to Router
Solicitations.";
reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6) -
AdvSendAdvertisements.";
}
leaf max-rtr-adv-interval {
type uint16 {
range "4..1800";
}
units "seconds";
default "600";
description
"The maximum time allowed between sending unsolicited
multicast Router Advertisements from the interface.";
reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6) -
MaxRtrAdvInterval.";
}
leaf min-rtr-adv-interval {
type uint16 {
range "3..1350";
}
units "seconds";
must ". <= 0.75 * ../max-rtr-adv-interval" {
description
"The value MUST NOT be greater than 75 % of
'max-rtr-adv-interval'.";
}
description
"The minimum time allowed between sending unsolicited
multicast Router Advertisements from the interface.
The default value to be used operationally if this leaf is
not configured is determined as follows:
- if max-rtr-adv-interval >= 9 seconds, the default value
is 0.33 * max-rtr-adv-interval;
- otherwise it is 0.75 * max-rtr-adv-interval.";
reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6) -
MinRtrAdvInterval.";
}
leaf managed-flag {
type boolean;
default "false";
description
"The value to be placed in the 'Managed address
configuration' flag field in the Router Advertisement.";
reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6) -
AdvManagedFlag.";
}
leaf other-config-flag {
type boolean;
default "false";
description
"The value to be placed in the 'Other configuration' flag
field in the Router Advertisement.";
reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6) -
AdvOtherConfigFlag.";
}
leaf link-mtu {
type uint32;
default "0";
description
"The value to be placed in MTU options sent by the router.
A value of zero indicates that no MTU options are sent.";
reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6) -
AdvLinkMTU.";
}
leaf reachable-time {
type uint32 {
range "0..3600000";
}
units "milliseconds";
default "0";
description
"The value to be placed in the Reachable Time field in the
Router Advertisement messages sent by the router. A value
of zero means unspecified (by this router).";
reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6) -
AdvReachableTime.";
}
leaf retrans-timer {
type uint32;
units "milliseconds";
default "0";
description
"The value to be placed in the Retrans Timer field in the
Router Advertisement messages sent by the router. A value
of zero means unspecified (by this router).";
reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6) -
AdvRetransTimer.";
}
leaf cur-hop-limit {
type uint8;
description
"The value to be placed in the Cur Hop Limit field in the
Router Advertisement messages sent by the router. A value
of zero means unspecified (by this router).
If this parameter is not configured, the device SHOULD use
the value specified in IANA Assigned Numbers that was in
effect at the time of implementation.";
reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6) -
AdvCurHopLimit.
IANA: IP Parameters,
http://www.iana.org/assignments/ip-parameters";
}
leaf default-lifetime {
type uint16 {
range "0..9000";
}
units "seconds";
description
"The value to be placed in the Router Lifetime field of
Router Advertisements sent from the interface, in seconds.
It MUST be either zero or between max-rtr-adv-interval and
9000 seconds. A value of zero indicates that the router is
not to be used as a default router. These limits may be
overridden by specific documents that describe how IPv6
operates over different link layers.
If this parameter is not configured, the device SHOULD use
a value of 3 * max-rtr-adv-interval.";
reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6) -
AdvDefaultLifeTime.";
}
container prefix-list {
description
"Configuration of prefixes to be placed in Prefix
Information options in Router Advertisement messages sent
from the interface.
Prefixes that are advertised by default but do not have
their entries in the child 'prefix' list are advertised
with the default values of all parameters.
The link-local prefix SHOULD NOT be included in the list
of advertised prefixes.";
reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6) -
AdvPrefixList.";
list prefix {
key "prefix-spec";
description
"Configuration of an advertised prefix entry.";
leaf prefix-spec {
type inet:ipv6-prefix;
description
"IPv6 address prefix.";
}
choice control-adv-prefixes {
default "advertise";
description
"The prefix either may be explicitly removed from the
set of advertised prefixes, or parameters with which
it is advertised may be specified (default case).";
leaf no-advertise {
type empty;
description
"The prefix will not be advertised.
This can be used for removing the prefix from the
default set of advertised prefixes.";
}
case advertise {
leaf valid-lifetime {
type uint32;
units "seconds";
default "2592000";
description
"The value to be placed in the Valid Lifetime in
the Prefix Information option. The designated
value of all 1's (0xffffffff) represents
infinity.";
reference
"RFC 4861: Neighbor Discovery for IP version 6
(IPv6) - AdvValidLifetime.";
}
leaf on-link-flag {
type boolean;
default "true";
description
"The value to be placed in the on-link flag
('L-bit') field in the Prefix Information
option.";
reference
"RFC 4861: Neighbor Discovery for IP version 6
(IPv6) - AdvOnLinkFlag.";
}
leaf preferred-lifetime {
type uint32;
units "seconds";
must ". <= ../valid-lifetime" {
description
"This value MUST NOT be greater than
valid-lifetime.";
}
default "604800";
description
"The value to be placed in the Preferred Lifetime
in the Prefix Information option. The designated
value of all 1's (0xffffffff) represents
infinity.";
reference
"RFC 4861: Neighbor Discovery for IP version 6
(IPv6) - AdvPreferredLifetime.";
}
leaf autonomous-flag {
type boolean;
default "true";
description
"The value to be placed in the Autonomous Flag
field in the Prefix Information option.";
reference
"RFC 4861: Neighbor Discovery for IP version 6
(IPv6) - AdvAutonomousFlag.";
}
}
}
}
}
}
}
augment "/rt:routing/rt:routing-instance/rt:routing-protocols/"
+ "rt:routing-protocol/rt:static-routes" {
description
"This augment defines the configuration of the 'static'
pseudo-protocol with data specific to IPv6 unicast.";
container ipv6 {
description
"Configuration of a 'static' pseudo-protocol instance
consists of a list of routes.";
list route {
key "destination-prefix";
ordered-by "user";
description
"A user-ordered list of static routes.";
leaf destination-prefix {
type inet:ipv6-prefix;
mandatory "true";
description
"IPv6 destination prefix.";
}
leaf description {
type string;
description
"Textual description of the route.";
}
container next-hop {
description
"Configuration of next-hop.";
uses rt:next-hop-content {
augment "next-hop-options" {
description
"Add next-hop address case.";
leaf next-hop-address {
type inet:ipv6-address;
description
"IPv6 address of the next-hop.";
}
}
}
}
}
}
}
/* RPC operations */
augment "/rt:fib-route/rt:input/rt:destination-address" {
when "rt:address-family='v6ur:ipv6-unicast'" {
description
"This augment is valid only for IPv6 unicast.";
}
description
"This leaf augments the 'rt:destination-address' parameter of
the 'rt:fib-route' operation.";
leaf address {
type inet:ipv6-address;
description
"IPv6 destination address.";
}
}
augment "/rt:fib-route/rt:output/rt:route" {
when "rt:address-family='v6ur:ipv6-unicast'" {
description
"This augment is valid only for IPv6 unicast.";
}
description
"This leaf augments the reply to the 'rt:fib-route'
operation.";
leaf destination-prefix {
type inet:ipv6-prefix;
description
"IPv6 destination prefix.";
}
}
augment "/rt:fib-route/rt:output/rt:route/rt:next-hop/"
+ "rt:next-hop-options/rt:simple-next-hop" {
when "../rt:address-family='v6ur:ipv6-unicast'" {
description
"This augment is valid only for IPv6 unicast.";
}
description
"This leaf augments the 'simple-next-hop' case in the reply to
the 'rt:fib-route' operation.";
leaf next-hop-address {
type inet:ipv6-address;
description
"IPv6 address of the next-hop.";
}
}
}
<CODE ENDS></artwork>
</figure>
</section>
<section anchor="sec.iana" title="IANA Considerations" toc="default">
<t>RFC Ed.: In this section, replace all occurrences of 'XXXX' with
the actual RFC number (and remove this note).</t>
<t>This document registers the following namespace URIs in the
IETF XML registry <xref target="RFC3688" pageno="false" format="default"/>:</t>
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height="">
--------------------------------------------------------------------
URI: urn:ietf:params:xml:ns:yang:ietf-routing
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
--------------------------------------------------------------------
--------------------------------------------------------------------
URI: urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
--------------------------------------------------------------------
--------------------------------------------------------------------
URI: urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
--------------------------------------------------------------------
</artwork>
</figure>
<t>This document registers the following YANG modules in the YANG
Module Names registry <xref target="RFC6020" pageno="false" format="default"/>:</t>
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height="">
--------------------------------------------------------------------
name: ietf-routing
namespace: urn:ietf:params:xml:ns:yang:ietf-routing
prefix: rt
reference: RFC XXXX
--------------------------------------------------------------------
--------------------------------------------------------------------
name: ietf-ipv4-unicast-routing
namespace: urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing
prefix: v4ur
reference: RFC XXXX
--------------------------------------------------------------------
--------------------------------------------------------------------
name: ietf-ipv6-unicast-routing
namespace: urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing
prefix: v6ur
reference: RFC XXXX
--------------------------------------------------------------------
</artwork>
</figure>
</section>
<section anchor="sec-cons" title="Security Considerations" toc="default">
<t>Configuration and state data conforming to the core routing
data model (defined in this document) are designed to be accessed
via the NETCONF protocol <xref target="RFC6241" pageno="false" format="default"/>. The lowest
NETCONF layer is the secure transport layer and the
mandatory-to-implement secure transport is SSH <xref target="RFC6242" pageno="false" format="default"/>. The NETCONF access control model <xref target="RFC6536" pageno="false" format="default"/> provides the means to restrict access for
particular NETCONF users to a pre-configured subset of all
available NETCONF protocol operations and content.</t>
<t>A number of data nodes defined in the YANG modules belonging to
the configuration part of the core routing data model are
writable/creatable/deletable (i.e., "config true" in YANG terms,
which is the default). These data nodes may be considered
sensitive or vulnerable in some network environments. Write
operations to these data nodes, such as "edit-config", can have
negative effects on the network if the protocol operations are not
properly protected.</t>
<t>The vulnerable "config true" subtrees and data nodes are the
following:
<list style="hanging">
<t hangText="/routing/routing-instance/interfaces/interface:">This
list assigns a network layer interface to a routing instance and
may also specify interface parameters related to routing.</t>
<t hangText="/routing/routing-instance/routing-protocols/routing-protocol:">This
list specifies the routing protocols configured on a device.</t>
<t hangText="/routing/routing-instance/ribs/rib:">This list
specifies the RIBs configured for the device.</t>
</list>
Unauthorized access to any of these lists can adversely affect the
routing subsystem of both the local device and the network. This
may lead to network malfunctions, delivery of packets to
inappropriate destinations and other problems.</t>
</section>
<section anchor="acknowledgments" title="Acknowledgments" toc="default">
<t>The authors wish to thank Nitin Bahadur, Martin Bjorklund,
Dean Bogdanovic, Jeff Haas, Joel Halpern, Wes Hardaker,
Sriganesh Kini, David Lamparter, Andrew McGregor, Jan Medved,
Xiang Li, Stephane Litkowski, Thomas Morin, Tom Petch,
Bruno Rijsman, Juergen Schoenwaelder, Phil Shafer, Dave Thaler,
Yi Yang, Derek Man-Kit Yeung and Jeffrey Zhang for their helpful
comments and suggestions.</t>
</section>
</middle>
<back>
<references title="Normative References">
<reference anchor="RFC2119">
<front>
<title abbrev="RFC Key Words">Key words for use in RFCs to Indicate Requirement Levels</title>
<author initials="S." surname="Bradner" fullname="Scott Bradner">
<organization>Harvard University</organization>
<address>
<postal>
<street>1350 Mass. Ave.</street>
<street>Cambridge</street>
<street>MA 02138</street></postal>
<phone>- +1 617 495 3864</phone>
<email>sob@harvard.edu</email></address></author>
<date year="1997" month="March"/>
<area>General</area>
<keyword>keyword</keyword>
<abstract>
<t>
In many standards track documents several words are used to signify
the requirements in the specification. These words are often
capitalized. This document defines these words as they should be
interpreted in IETF documents. Authors who follow these guidelines
should incorporate this phrase near the beginning of their document:
<list>
<t>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
RFC 2119.
</t></list></t>
<t>
Note that the force of these words is modified by the requirement
level of the document in which they are used.
</t></abstract></front>
<seriesInfo name="BCP" value="14"/>
<seriesInfo name="RFC" value="2119"/>
<format type="TXT" octets="4723" target="http://www.rfc-editor.org/rfc/rfc2119.txt"/>
<format type="HTML" octets="17970" target="http://xml.resource.org/public/rfc/html/rfc2119.html"/>
<format type="XML" octets="5777" target="http://xml.resource.org/public/rfc/xml/rfc2119.xml"/>
</reference>
<reference anchor="RFC3688">
<front>
<title>The IETF XML Registry</title>
<author initials="M." surname="Mealling" fullname="M. Mealling">
<organization/></author>
<date year="2004" month="January"/>
<abstract>
<t>This document describes an IANA maintained registry for IETF standards which use 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"/>
<format type="TXT" octets="17325" target="http://www.rfc-editor.org/rfc/rfc3688.txt"/>
</reference>
<reference anchor="RFC4861">
<front>
<title>Neighbor Discovery for IP version 6 (IPv6)</title>
<author initials="T." surname="Narten" fullname="T. Narten">
<organization/></author>
<author initials="E." surname="Nordmark" fullname="E. Nordmark">
<organization/></author>
<author initials="W." surname="Simpson" fullname="W. Simpson">
<organization/></author>
<author initials="H." surname="Soliman" fullname="H. Soliman">
<organization/></author>
<date year="2007" month="September"/>
<abstract>
<t>This document specifies the Neighbor Discovery protocol for IP Version 6. IPv6 nodes on the same link use Neighbor Discovery to discover each other's presence, to determine each other's link-layer addresses, to find routers, and to maintain reachability information about the paths to active neighbors. [STANDARDS-TRACK]</t></abstract></front>
<seriesInfo name="RFC" value="4861"/>
<format type="TXT" octets="235106" target="http://www.rfc-editor.org/rfc/rfc4861.txt"/>
</reference>
<reference anchor="RFC6020">
<front>
<title>YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)</title>
<author initials="M." surname="Bjorklund" fullname="M. Bjorklund">
<organization/></author>
<date year="2010" month="October"/>
<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"/>
<format type="TXT" octets="324178" target="http://www.rfc-editor.org/rfc/rfc6020.txt"/>
</reference>
<reference anchor="RFC6991">
<front>
<title>Common YANG Data Types</title>
<author initials="J." surname="Schoenwaelder" fullname="J. Schoenwaelder">
<organization/></author>
<date year="2013" month="July"/>
<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"/>
<format type="TXT" octets="60242" target="http://www.rfc-editor.org/rfc/rfc6991.txt"/>
</reference>
<reference anchor="RFC6241">
<front>
<title>Network Configuration Protocol (NETCONF)</title>
<author initials="R." surname="Enns" fullname="R. Enns">
<organization/></author>
<author initials="M." surname="Bjorklund" fullname="M. Bjorklund">
<organization/></author>
<author initials="J." surname="Schoenwaelder" fullname="J. Schoenwaelder">
<organization/></author>
<author initials="A." surname="Bierman" fullname="A. Bierman">
<organization/></author>
<date year="2011" month="June"/>
<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"/>
<format type="TXT" octets="209465" target="http://www.rfc-editor.org/rfc/rfc6241.txt"/>
</reference>
<reference anchor="RFC7223">
<front>
<title>A YANG Data Model for Interface Management</title>
<author initials="M." surname="Bjorklund" fullname="M. Bjorklund">
<organization/></author>
<date year="2014" month="May"/>
<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 configuration data and state data (status information and counters for the collection of statistics).</t></abstract></front>
<seriesInfo name="RFC" value="7223"/>
<format type="TXT" octets="70537" target="http://www.rfc-editor.org/rfc/rfc7223.txt"/>
</reference>
<reference anchor="RFC7277">
<front>
<title>A YANG Data Model for IP Management</title>
<author initials="M." surname="Bjorklund" fullname="M. Bjorklund">
<organization/></author>
<date year="2014" month="June"/>
<abstract>
<t>This document defines a YANG data model for management of IP implementations. The data model includes configuration data and state data.</t></abstract></front>
<seriesInfo name="RFC" value="7277"/>
<format type="TXT" octets="50043" target="http://www.rfc-editor.org/rfc/rfc7277.txt"/>
</reference>
</references>
<references title="Informative References">
<reference anchor="RFC6087">
<front>
<title>Guidelines for Authors and Reviewers of YANG Data Model Documents</title>
<author initials="A." surname="Bierman" fullname="A. Bierman">
<organization/></author>
<date year="2011" month="January"/>
<abstract>
<t>This memo provides guidelines for authors and reviewers of Standards Track specifications containing YANG data model modules. Applicable portions may be used as a basis for reviews of other YANG data model documents. Recommendations and procedures are defined, which are intended to increase interoperability and usability of Network Configuration Protocol (NETCONF) implementations that utilize YANG data model modules. This document is not an Internet Standards Track specification; it is published for informational purposes.</t></abstract></front>
<seriesInfo name="RFC" value="6087"/>
<format type="TXT" octets="49969" target="http://www.rfc-editor.org/rfc/rfc6087.txt"/>
</reference>
<reference anchor="RFC6242">
<front>
<title>Using the NETCONF Protocol over Secure Shell (SSH)</title>
<author initials="M." surname="Wasserman" fullname="M. Wasserman">
<organization/></author>
<date year="2011" month="June"/>
<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"/>
<format type="TXT" octets="22704" target="http://www.rfc-editor.org/rfc/rfc6242.txt"/>
</reference>
<reference anchor="RFC6536">
<front>
<title>Network Configuration Protocol (NETCONF) Access Control Model</title>
<author initials="A." surname="Bierman" fullname="A. Bierman">
<organization/></author>
<author initials="M." surname="Bjorklund" fullname="M. Bjorklund">
<organization/></author>
<date year="2012" month="March"/>
<abstract>
<t>The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) 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 protocol access for particular users to a pre-configured subset of all available NETCONF protocol operations and content. This document defines such an access control model. [STANDARDS-TRACK]</t></abstract></front>
<seriesInfo name="RFC" value="6536"/>
<format type="TXT" octets="90803" target="http://www.rfc-editor.org/rfc/rfc6536.txt"/>
</reference>
<reference anchor="RFC4364">
<front>
<title>BGP/MPLS IP Virtual Private Networks (VPNs)</title>
<author initials="E." surname="Rosen" fullname="E. Rosen">
<organization/></author>
<author initials="Y." surname="Rekhter" fullname="Y. Rekhter">
<organization/></author>
<date year="2006" month="February"/>
<abstract>
<t>This document describes a method by which a Service Provider may use an IP backbone to provide IP Virtual Private Networks (VPNs) for its customers. This method uses a "peer model", in which the customers' edge routers (CE routers) send their routes to the Service Provider's edge routers (PE routers); there is no "overlay" visible to the customer's routing algorithm, and CE routers at different sites do not peer with each other. Data packets are tunneled through the backbone, so that the core routers do not need to know the VPN routes. [STANDARDS-TRACK]</t></abstract></front>
<seriesInfo name="RFC" value="4364"/>
<format type="TXT" octets="116446" target="http://www.rfc-editor.org/rfc/rfc4364.txt"/>
</reference>
</references>
<section anchor="app.data-tree" title="The Complete Data Trees" toc="default">
<t>This appendix presents the complete configuration and
state data trees of the core routing data model.
See <xref target="sec.tree-symbols" pageno="false" format="default"/> for an explanation of the
symbols used. Data type of every leaf node is shown near the right
end of the corresponding line.</t>
<section anchor="app.config-tree" title="Configuration Data" toc="default">
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height="">
+--rw routing
+--rw routing-instance* [name]
+--rw name string
+--rw type? identityref
+--rw enabled? boolean
+--rw router-id? yang:dotted-quad
+--rw description? string
+--rw interfaces
| +--rw interface* if:interface-ref
+--rw routing-protocols
| +--rw routing-protocol* [type name]
| +--rw type identityref
| +--rw name string
| +--rw description? string
| +--rw enabled? boolean
| +--rw route-preference? route-preference
| +--rw static-routes
| +--rw v6ur:ipv6
| | +--rw v6ur:route* [destination-prefix]
| | +--rw v6ur:destination-prefix inet:ipv6-prefix
| | +--rw v6ur:description? string
| | +--rw v6ur:next-hop
| | +--rw (next-hop-options)
| | +--:(simple-next-hop)
| | | +--rw v6ur:outgoing-interface?
| | +--:(special-next-hop)
| | | +--rw v6ur:special-next-hop?
| | +--:(next-hop-address)
| | +--rw v6ur:next-hop-address?
| +--rw v4ur:ipv4
| +--rw v4ur:route* [destination-prefix]
| +--rw v4ur:destination-prefix inet:ipv4-prefix
| +--rw v4ur:description? string
| +--rw v4ur:next-hop
| +--rw (next-hop-options)
| +--:(simple-next-hop)
| | +--rw v4ur:outgoing-interface?
| +--:(special-next-hop)
| | +--rw v4ur:special-next-hop?
| +--:(next-hop-address)
| +--rw v4ur:next-hop-address?
+--rw ribs
+--rw rib* [name]
+--rw name string
+--rw address-family? identityref
+--rw description? string
</artwork>
</figure>
</section>
<section anchor="app.state-tree" title="State Data" toc="default">
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height="">
+--ro routing-state
+--ro routing-instance* [name]
+--ro name string
+--ro type? identityref
+--ro router-id? yang:dotted-quad
+--ro interfaces
| +--ro interface* if:interface-state-ref
+--ro routing-protocols
| +--ro routing-protocol* [type name]
| +--ro type identityref
| +--ro name string
| +--ro route-preference route-preference
+--ro ribs
+--ro rib* [name]
+--ro name string
+--ro 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?
| | +--ro v6ur:next-hop-address?
| | +--ro v4ur:next-hop-address?
| +--:(special-next-hop)
| +--ro special-next-hop? enumeration
+--ro source-protocol identityref
+--ro active? empty
+--ro last-updated? yang:date-and-time
+--ro v6ur:destination-prefix? inet:ipv6-prefix
+--ro v4ur:destination-prefix? inet:ipv4-prefix
</artwork>
</figure>
</section>
</section>
<section anchor="app.minimum" title="Minimum Implementation" toc="default">
<t>Some parts and options of the core routing model, such as
user-defined routing tables, are intended only for advanced
routers. This appendix gives basic non-normative guidelines for
implementing a bare minimum of available functions. Such an
implementation may be used for hosts or very simple routers.</t>
<t>A minimum implementation will provide a single
system-controlled routing instance, and will not allow clients to
create any user-controlled instances.</t>
<t>Typically, the feature "multiple-ribs" will not be
supported. This means that a single system-controlled RIB is
available for each supported address family - IPv4, IPv6 or
both. These RIBs must be the default RIBs. No user-controlled
RIBs are allowed.</t>
<t>In addition to the mandatory instance of the "direct"
pseudo-protocol, a minimum implementation should support
configuring instance(s) of the "static" pseudo-protocol.</t>
<t>Platforms with severely constrained resources may use
deviations for restricting the data model, e.g., limiting the
number of "static" routing protocol instances.</t>
</section>
<section anchor="app.rip" title="Example: Adding a New Routing Protocol" toc="default">
<t>This appendix demonstrates how the core routing data model
can be extended to support a new routing protocol. The YANG
module "example-rip" shown below is intended as an illustration
rather than a real definition of a data model for the RIP
routing protocol. For the sake of brevity, this module does not
obey all the guidelines specified in <xref target="RFC6087" pageno="false" format="default"/>. See also <xref target="sec.newproto" pageno="false" format="default"/>.</t>
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height="">
module example-rip {
namespace "http://example.com/rip";
prefix "rip";
import ietf-routing {
prefix "rt";
}
identity rip {
base rt:routing-protocol;
description
"Identity for the RIP routing protocol.";
}
typedef rip-metric {
type uint8 {
range "0..16";
}
}
grouping route-content {
description
"This grouping defines RIP-specific route attributes.";
leaf metric {
type rip-metric;
}
leaf tag {
type uint16;
default "0";
description
"This leaf may be used to carry additional info, e.g. AS
number.";
}
}
augment "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/"
+ "rt:routes/rt:route" {
when "rt:source-protocol = 'rip:rip'" {
description
"This augment is only valid for a routes whose source
protocol is RIP.";
}
description
"RIP-specific route attributes.";
uses route-content;
}
augment "/rt:fib-route/rt:output/rt:route" {
description
"RIP-specific route attributes in the output of 'active-route'
RPC.";
uses route-content;
}
augment "/rt:routing/rt:routing-instance/rt:routing-protocols/"
+ "rt:routing-protocol" {
when "rt:type = 'rip:rip'" {
description
"This augment is only valid for a routing protocol instance
of type 'rip'.";
}
container rip {
description
"RIP instance configuration.";
container interfaces {
description
"Per-interface RIP configuration.";
list interface {
key "name";
description
"RIP is enabled on interfaces that have an entry in this
list, unless 'enabled' is set to 'false' for that
entry.";
leaf name {
type leafref {
path "../../../../../../rt:interfaces/rt:interface";
}
}
leaf enabled {
type boolean;
default "true";
}
leaf metric {
type rip-metric;
default "1";
}
}
}
leaf update-interval {
type uint8 {
range "10..60";
}
units "seconds";
default "30";
description
"Time interval between periodic updates.";
}
}
}
}
</artwork>
</figure>
</section>
<section anchor="app.get-reply" title="Example: NETCONF <get> Reply" toc="default">
<t>This section contains a sample reply to the NETCONF <get>
message, which could be sent by a server supporting (i.e.,
advertising them in the NETCONF <hello> message) the
following YANG modules:
<list style="symbols">
<t>ietf-interfaces <xref target="RFC7223" pageno="false" format="default"/>,</t>
<t>ietf-ip <xref target="RFC7277" pageno="false" format="default"/>,</t>
<t>ietf-routing (<xref target="sec.mod-rt" pageno="false" format="default"/>),</t>
<t>ietf-ipv4-unicast-routing (<xref target="sec.mod-v4ur" pageno="false" format="default"/>),</t>
<t>ietf-ipv6-unicast-routing (<xref target="sec.mod-v6ur" pageno="false" format="default"/>).</t>
</list></t>
<t>We assume a simple network set-up as shown in <xref target="fig.exnet" pageno="false" format="default"/>: router "A" uses static default routes with
the "ISP" router as the next-hop. IPv6 router advertisements are
configured only on the "eth1" interface and disabled on the
upstream "eth0" interface.</t>
<figure anchor="fig.exnet" title="Example network configuration" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height="">
+-----------------+
| |
| Router ISP |
| |
+--------+--------+
|2001:db8:0:1::2
|192.0.2.2
|
|
|2001:db8:0:1::1
eth0|192.0.2.1
+--------+--------+
| |
| Router A |
| |
+--------+--------+
eth1|198.51.100.1
|2001:db8:0:2::1
|
</artwork>
</figure>
<t>A reply to the NETCONF <get> message sent by router "A"
would then be as follows:</t>
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height="">
<?xml version="1.0"?>
<rpc-reply
message-id="101"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
xmlns:v4ur="urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing"
xmlns:v6ur="urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing"
xmlns:if="urn:ietf:params:xml:ns:yang:ietf-interfaces"
xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type"
xmlns:ip="urn:ietf:params:xml:ns:yang:ietf-ip"
xmlns:rt="urn:ietf:params:xml:ns:yang:ietf-routing">
<data>
<if:interfaces>
<if:interface>
<if:name>eth0</if:name>
<if:type>ianaift:ethernetCsmacd</if:type>
<if:description>
Uplink to ISP.
</if:description>
<ip:ipv4>
<ip:address>
<ip:ip>192.0.2.1</ip:ip>
<ip:prefix-length>24</ip:prefix-length>
</ip:address>
<ip:forwarding>true</ip:forwarding>
</ip:ipv4>
<ip:ipv6>
<ip:address>
<ip:ip>2001:0db8:0:1::1</ip:ip>
<ip:prefix-length>64</ip:prefix-length>
</ip:address>
<ip:forwarding>true</ip:forwarding>
<ip:autoconf>
<ip:create-global-addresses>false</ip:create-global-addresses>
</ip:autoconf>
</ip:ipv6>
</if:interface>
<if:interface>
<if:name>eth1</if:name>
<if:type>ianaift:ethernetCsmacd</if:type>
<if:description>
Interface to the internal network.
</if:description>
<ip:ipv4>
<ip:address>
<ip:ip>198.51.100.1</ip:ip>
<ip:prefix-length>24</ip:prefix-length>
</ip:address>
<ip:forwarding>true</ip:forwarding>
</ip:ipv4>
<ip:ipv6>
<ip:address>
<ip:ip>2001:0db8:0:2::1</ip:ip>
<ip:prefix-length>64</ip:prefix-length>
</ip:address>
<ip:forwarding>true</ip:forwarding>
<ip:autoconf>
<ip:create-global-addresses>false</ip:create-global-addresses>
</ip:autoconf>
</ip:ipv6>
</if:interface>
</if:interfaces>
<if:interfaces-state>
<if:interface>
<if:name>eth0</if:name>
<if:type>ianaift:ethernetCsmacd</if:type>
<if:phys-address>00:0C:42:E5:B1:E9</if:phys-address>
<if:oper-status>up</if:oper-status>
<rt:routing-instance>rtr0</rt:routing-instance>
<if:statistics>
<if:discontinuity-time>
2014-10-24T17:11:27+00:58
</if:discontinuity-time>
</if:statistics>
<ip:ipv4>
<ip:forwarding>true</ip:forwarding>
<ip:mtu>1500</ip:mtu>
<ip:address>
<ip:ip>192.0.2.1</ip:ip>
<ip:prefix-length>24</ip:prefix-length>
</ip:address>
</ip:ipv4>
<ip:ipv6>
<ip:forwarding>true</ip:forwarding>
<ip:mtu>1500</ip:mtu>
<ip:address>
<ip:ip>2001:0db8:0:1::1</ip:ip>
<ip:prefix-length>64</ip:prefix-length>
</ip:address>
<v6ur:ipv6-router-advertisements>
<v6ur:send-advertisements>true</v6ur:send-advertisements>
<v6ur:prefix-list>
<v6ur:prefix>
<v6ur:prefix-spec>2001:db8:0:2::/64</v6ur:prefix-spec>
</v6ur:prefix>
</v6ur:prefix-list>
</v6ur:ipv6-router-advertisements>
</ip:ipv6>
</if:interface>
<if:interface>
<if:name>eth1</if:name>
<if:type>ianaift:ethernetCsmacd</if:type>
<if:phys-address>00:0C:42:E5:B1:EA</if:phys-address>
<if:oper-status>up</if:oper-status>
<rt:routing-instance>rtr0</rt:routing-instance>
<if:statistics>
<if:discontinuity-time>
2014-10-24T17:11:27+00:59
</if:discontinuity-time>
</if:statistics>
<ip:ipv4>
<ip:forwarding>true</ip:forwarding>
<ip:mtu>1500</ip:mtu>
<ip:address>
<ip:ip>198.51.100.1</ip:ip>
<ip:prefix-length>24</ip:prefix-length>
</ip:address>
</ip:ipv4>
<ip:ipv6>
<ip:forwarding>true</ip:forwarding>
<ip:mtu>1500</ip:mtu>
<ip:address>
<ip:ip>2001:0db8:0:2::1</ip:ip>
<ip:prefix-length>64</ip:prefix-length>
</ip:address>
<v6ur:ipv6-router-advertisements>
<v6ur:send-advertisements>true</v6ur:send-advertisements>
<v6ur:prefix-list>
<v6ur:prefix>
<v6ur:prefix-spec>2001:db8:0:2::/64</v6ur:prefix-spec>
</v6ur:prefix>
</v6ur:prefix-list>
</v6ur:ipv6-router-advertisements>
</ip:ipv6>
</if:interface>
</if:interfaces-state>
<rt:routing>
<rt:routing-instance>
<rt:name>rtr0</rt:name>
<rt:description>Router A</rt:description>
<rt:router-id>192.0.2.1</rt:router-id>
<rt:interfaces>
<rt:interface>eth0</rt:interface>
<rt:interface>eth1</rt:interface>
</rt:interfaces>
<rt:routing-protocols>
<rt:routing-protocol>
<rt:type>rt:static</rt:type>
<rt:name>st0</rt:name>
<rt:description>
Static routing is used for the internal network.
</rt:description>
<rt:static-routes>
<v4ur:ipv4>
<v4ur:route>
<v4ur:destination-prefix>
0.0.0.0/0
</v4ur:destination-prefix>
<v4ur:next-hop>
<v4ur:next-hop-address>192.0.2.2</v4ur:next-hop-address>
</v4ur:next-hop>
</v4ur:route>
</v4ur:ipv4>
<v6ur:ipv6>
<v6ur:route>
<v6ur:destination-prefix>::/0</v6ur:destination-prefix>
<v6ur:next-hop>
<v6ur:next-hop-address>
2001:db8:0:1::2
</v6ur:next-hop-address>
</v6ur:next-hop>
</v6ur:route>
</v6ur:ipv6>
</rt:static-routes>
</rt:routing-protocol>
</rt:routing-protocols>
</rt:routing-instance>
</rt:routing>
<rt:routing-state>
<rt:routing-instance>
<rt:name>rtr0</rt:name>
<rt:interfaces>
<rt:interface>eth0</rt:interface>
<rt:interface>eth1</rt:interface>
</rt:interfaces>
<rt:routing-protocols>
<rt:routing-protocol>
<rt:type>rt:static</rt:type>
<rt:name>st0</rt:name>
<rt:route-preference>5</rt:route-preference>
</rt:routing-protocol>
</rt:routing-protocols>
<rt:ribs>
<rt:rib>
<rt:name>ipv4-master</rt:name>
<rt:address-family>v4ur:ipv4-unicast</rt:address-family>
<rt:default-rib>true</rt:default-rib>
<rt:routes>
<rt:route>
<v4ur:destination-prefix>
192.0.2.1/24
</v4ur:destination-prefix>
<rt:next-hop>
<rt:outgoing-interface>eth0</rt:outgoing-interface>
</rt:next-hop>
<rt:route-preference>0</rt:route-preference>
<rt:source-protocol>rt:direct</rt:source-protocol>
<rt:last-updated>2014-10-24T17:11:27+01:00</rt:last-updated>
</rt:route>
<rt:route>
<v4ur:destination-prefix>
198.51.100.0/24
</v4ur:destination-prefix>
<rt:next-hop>
<rt:outgoing-interface>eth1</rt:outgoing-interface>
</rt:next-hop>
<rt:source-protocol>rt:direct</rt:source-protocol>
<rt:route-preference>0</rt:route-preference>
<rt:last-updated>2014-10-24T17:11:27+01:00</rt:last-updated>
</rt:route>
<rt:route>
<v4ur:destination-prefix>0.0.0.0/0</v4ur:destination-prefix>
<rt:source-protocol>rt:static</rt:source-protocol>
<rt:route-preference>5</rt:route-preference>
<rt:next-hop>
<v4ur:next-hop-address>192.0.2.2</v4ur:next-hop-address>
</rt:next-hop>
<rt:last-updated>2014-10-24T18:02:45+01:00</rt:last-updated>
</rt:route>
</rt:routes>
</rt:rib>
<rt:rib>
<rt:name>ipv6-master</rt:name>
<rt:address-family>v6ur:ipv6-unicast</rt:address-family>
<rt:default-rib>true</rt:default-rib>
<rt:routes>
<rt:route>
<v6ur:destination-prefix>
2001:db8:0:1::/64
</v6ur:destination-prefix>
<rt:next-hop>
<rt:outgoing-interface>eth0</rt:outgoing-interface>
</rt:next-hop>
<rt:source-protocol>rt:direct</rt:source-protocol>
<rt:route-preference>0</rt:route-preference>
<rt:last-updated>2014-10-24T17:11:27+01:00</rt:last-updated>
</rt:route>
<rt:route>
<v6ur:destination-prefix>
2001:db8:0:2::/64
</v6ur:destination-prefix>
<rt:next-hop>
<rt:outgoing-interface>eth1</rt:outgoing-interface>
</rt:next-hop>
<rt:source-protocol>rt:direct</rt:source-protocol>
<rt:route-preference>0</rt:route-preference>
<rt:last-updated>2014-10-24T17:11:27+01:00</rt:last-updated>
</rt:route>
<rt:route>
<v6ur:destination-prefix>::/0</v6ur:destination-prefix>
<rt:next-hop>
<v6ur:next-hop-address>
2001:db8:0:1::2
</v6ur:next-hop-address>
</rt:next-hop>
<rt:source-protocol>rt:static</rt:source-protocol>
<rt:route-preference>5</rt:route-preference>
<rt:last-updated>2014-10-24T18:02:45+01:00</rt:last-updated>
</rt:route>
</rt:routes>
</rt:rib>
</rt:ribs>
</rt:routing-instance>
</rt:routing-state>
</data>
</rpc-reply>
</artwork>
</figure>
</section>
<section anchor="change-log" title="Change Log" toc="default">
<t>RFC Editor: Remove this section upon publication as an RFC.</t>
<section title="Changes Between Versions -17 and -18" toc="default">
<t>
<list style="symbols">
<t>The container "ribs" was moved under "routing-instance"
(in both "routing" and "routing-state").</t>
<t>Typedefs "rib-ref" and "rib-state-ref" were removed.</t>
<t>Removed "recipient-ribs" (both state and configuration).</t>
<t>Removed "connected-ribs" from "routing-protocol" (both
state and configuration).</t>
<t>Configuration and state data for IPv6 RA were moved
under "if:interface" and "if:interface-state".</t>
<t>Assignment of interfaces to routing instances now use
leaf-list rather than list (both config and state). The
opposite reference from "if:interface" to
"rt:routing-instance" was changed to a single leaf (an
interface cannot belong to multiple routing instances).</t>
<t>Specification of a default RIB is now a simple flag
under "rib" (both config and state).</t>
<t>Default RIBs are marked by a flag in state data.</t>
</list>
</t>
</section>
<section title="Changes Between Versions -16 and -17" toc="default">
<t>
<list style="symbols">
<t>Added Acee as a co-author.</t>
<t>Removed all traces of route filters.</t>
<t>Removed numeric IDs of list entries in state data.</t>
<t>Removed all next-hop cases except "simple-next-hop" and
"special-next-hop".</t>
<t>Removed feature "multipath-routes".</t>
<t>Augmented "ietf-interfaces" module with a leaf-list of
leafrefs pointing form state data of an interface entry to
the routing instance(s) to which the interface is
assigned.</t>
</list>
</t>
</section>
<section title="Changes Between Versions -15 and -16" toc="default">
<t>
<list style="symbols">
<t>Added 'type' as the second key component of
'routing-protocol', both in configuration and state
data.</t>
<t>The restriction of no more than one connected RIB per
address family was removed.</t>
<t>Removed the 'id' key of routes in RIBs. This list has
no keys anymore.</t>
<t>Remove the 'id' key from static routes and make
'destination-prefix' the only key.</t>
<t>Added 'route-preference' as a new attribute of routes
in RIB.</t>
<t>Added 'active' as a new attribute of routes in
RIBs.</t>
<t>Renamed RPC operation 'active-route' to 'fib-route'.</t>
<t>Added 'route-preference' as a new parameter of routing
protocol instances, both in configuration and state data.</t>
<t>Renamed identity 'rt:standard-routing-instance' to
'rt:default-routing-instance'.</t>
<t>Added next-hop lists to state data.</t>
<t>Added two cases for specifying next-hops indirectly -
via a new RIB or a recursive list of next-hops.</t>
<t>Reorganized next-hop in static routes.</t>
<t>Removed all 'if-feature' statements from state data.</t>
</list>
</t>
</section>
<section title="Changes Between Versions -14 and -15" toc="default">
<t>
<list style="symbols">
<t>Removed all defaults from state data.</t>
<t>Removed default from 'cur-hop-limit' in config.</t>
</list>
</t>
</section>
<section title="Changes Between Versions -13 and -14" toc="default">
<t>
<list style="symbols">
<t>Removed dependency of 'connected-ribs' on the
'multiple-ribs' feature.</t>
<t>Removed default value of 'cur-hop-limit' in state data.</t>
<t>Moved parts of descriptions and all references on IPv6 RA
parameters from state data to configuration.</t>
<t>Added reference to RFC 6536 in the Security section.</t>
</list>
</t>
</section>
<section title="Changes Between Versions -12 and -13" toc="default">
<t>
<list style="symbols">
<t>Wrote appendix about minimum implementation.</t>
<t>Remove "when" statement for IPv6 router interface
state data - it was dependent on a config value that
may not be present.</t>
<t>Extra container for the next-hop list.</t>
<t>Names rather than numeric ids are used for referring to
list entries in state data.</t>
<t>Numeric ids are always declared as mandatory and
unique. Their description states that they are ephemeral.</t>
<t>Descriptions of "name" keys in state data lists
are required to be persistent.</t>
<t/>
<t>Removed "if-feature multiple-ribs;" from connected-ribs.</t>
<t>"rib-name" instead of "name" is used as the name of
leafref nodes.</t>
<t>"next-hop" instead of "nexthop" or "gateway" used
throughout, both in node names and text.</t>
</list>
</t>
</section>
<section title="Changes Between Versions -11 and -12" toc="default">
<t>
<list style="symbols">
<t>Removed feature "advanced-router" and introduced two
features instead: "multiple-ribs" and "multipath-routes".</t>
<t>Unified the keys of config and state versions of
"routing-instance" and "rib" lists.</t>
<t>Numerical identifiers of state list entries are not keys
anymore, but they are constrained using the "unique" statement.</t>
<t>Updated acknowledgements.</t>
</list>
</t>
</section>
<section title="Changes Between Versions -10 and -11" toc="default">
<t>
<list style="symbols">
<t>Migrated address families from IANA enumerations to
identities.</t> <t>Terminology and node names aligned with
the I2RS RIB model: router -> routing instance, routing
table -> RIB.</t>
<t>Introduced uint64 keys for state lists: routing-instance,
rib, route, nexthop.</t>
<t>Described the relationship between system-controlled and
user-controlled list entries.</t>
<t>Feature "user-defined-routing-tables" changed into "advanced-router".</t>
<t>Made nexthop into a choice in order to allow for
nexthop-list (I2RS requirement).</t>
<t>Added nexthop-list with entries having priorities
(backup) and weights (load balancing).</t>
<t>Updated bibliography references.</t>
</list>
</t>
</section>
<section title="Changes Between Versions -09 and -10" toc="default">
<t>
<list style="symbols">
<t>Added subtree for state data ("/routing-state").</t>
<t>Terms "system-controlled entry" and "user-controlled
entry" defined and used.</t>
<t>New feature "user-defined-routing-tables". Nodes that are
useful only with user-defined routing tables are now conditional.</t>
<t>Added grouping "router-id".</t>
<t>In routing tables, "source-protocol" attribute of routes
now reports only protocol type, and its datatype is
"identityref".</t>
<t>Renamed "main-routing-table" to "default-routing-table".</t>
</list>
</t>
</section>
<section title="Changes Between Versions -08 and -09" toc="default">
<t>
<list style="symbols">
<t>Fixed "must" expresion for "connected-routing-table".</t>
<t>Simplified "must" expression for "main-routing-table".</t>
<t>Moved per-interface configuration of a new routing
protocol under 'routing-protocol'. This also affects the
'example-rip' module.</t>
</list>
</t>
</section>
<section title="Changes Between Versions -07 and -08" toc="default">
<t>
<list style="symbols">
<t>Changed reference from RFC6021 to RFC6021bis.</t>
</list>
</t>
</section>
<section title="Changes Between Versions -06 and -07" toc="default">
<t>
<list style="symbols">
<t>The contents of <get-reply> in <xref target="app.get-reply" pageno="false" format="default"/> was updated: "eth[01]" is used as
the value of "location", and "forwarding" is on for both
interfaces and both IPv4 and IPv6.</t>
<t>The "must" expression for "main-routing-table" was
modified to avoid redundant error messages reporting address
family mismatch when "name" points to a non-existent routing
table.</t>
<t>The default behavior for IPv6 RA prefix advertisements
was clarified.</t>
<t>Changed type of "rt:router-id" to "ip:dotted-quad".</t>
<t>Type of "rt:router-id" changed to "yang:dotted-quad".</t>
<t>Fixed missing prefixes in XPath expressions.</t>
</list>
</t>
</section>
<section title="Changes Between Versions -05 and -06" toc="default">
<t>
<list style="symbols">
<t>Document title changed: "Configuration" was replaced by
"Management".</t>
<t>New typedefs "routing-table-ref" and "route-filter-ref".</t>
<t>Double slashes "//" were removed from XPath expressions
and replaced with the single "/".</t>
<t>Removed uniqueness requirement for "router-id".</t>
<t>Complete data tree is now in <xref target="app.data-tree" pageno="false" format="default"/>.</t>
<t>Changed type of "source-protocol" from "leafref" to "string".</t>
<t>Clarified the relationship between routing protocol
instances and connected routing tables.</t>
<t>Added a must constraint saying that a routing table
connected to the direct pseudo-protocol must not be a main
routing table.</t>
</list>
</t>
</section>
<section title="Changes Between Versions -04 and -05" toc="default">
<t>
<list style="symbols">
<t>Routing tables are now global, i.e., "routing-tables" is
a child of "routing" rather than "router".</t>
<t>"must" statement for "static-routes" changed to "when".</t>
<t>Added "main-routing-tables" containing references to main
routing tables for each address family.</t>
<t>Removed the defaults for "address-family" and "safi" and
made them mandatory.</t>
<t>Removed the default for route-filter/type and made this
leaf mandatory.</t>
<t>If there is no active route for a given destination, the
"active-route" RPC returns no output.</t>
<t>Added "enabled" switch under "routing-protocol".</t>
<t>Added "router-type" identity and "type" leaf under
"router".</t>
<t>Route attribute "age" changed to "last-updated", its type
is "yang:date-and-time".</t>
<t>The "direct" pseudo-protocol is always connected to main
routing tables.</t>
<t>Entries in the list of connected routing tables renamed
from "routing-table" to "connected-routing-table".</t>
<t>Added "must" constraint saying that a routing table must
not be its own recipient.</t>
</list>
</t>
</section>
<section title="Changes Between Versions -03 and -04" toc="default">
<t>
<list style="symbols">
<t>Changed "error-tag" for both RPC operations from "missing
element" to "data-missing".</t>
<t>Removed the decrementing behavior for advertised IPv6
prefix parameters "valid-lifetime" and
"preferred-lifetime".</t>
<t>Changed the key of the static route lists from "seqno" to
"id" because the routes needn't be sorted.</t>
<t>Added 'must' constraint saying that "preferred-lifetime"
must not be greater than "valid-lifetime".</t>
</list>
</t>
</section>
<section title="Changes Between Versions -02 and -03" toc="default">
<t>
<list style="symbols">
<t>Module "iana-afn-safi" moved to I-D "iana-if-type".</t>
<t>Removed forwarding table.</t>
<t>RPC "get-route" changed to "active-route". Its output is
a list of routes (for multi-path routing).</t>
<t>New RPC "route-count".</t>
<t>For both RPCs, specification of negative responses was
added.</t>
<t>Relaxed separation of router instances.</t>
<t>Assignment of interfaces to router instances needn't be
disjoint.</t>
<t>Route filters are now global.</t>
<t>Added "allow-all-route-filter" for symmetry.</t>
<t>Added <xref target="sec.interactions" pageno="false" format="default"/> about
interactions with "ietf-interfaces" and "ietf-ip".</t>
<t>Added "router-id" leaf.</t>
<t>Specified the names for IPv4/IPv6 unicast main routing
tables.</t>
<t>Route parameter "last-modified" changed to "age".</t>
<t>Added container "recipient-routing-tables".</t>
</list>
</t>
</section>
<section title="Changes Between Versions -01 and -02" toc="default">
<t><list style="symbols">
<t>Added module "ietf-ipv6-unicast-routing".</t>
<t>The example in <xref target="app.get-reply" pageno="false" format="default"/> now uses
IP addresses from blocks reserved for documentation.</t>
<t>Direct routes appear by default in the forwarding
table.</t>
<t>Network layer interfaces must be assigned to a router
instance. Additional interface configuration may be present.</t>
<t>The "when" statement is only used with "augment", "must" is
used elsewhere.</t>
<t>Additional "must" statements were added.</t>
<t>The "route-content" grouping for IPv4 and IPv6 unicast now
includes the material from the "ietf-routing" version via
"uses rt:route-content".</t>
<t>Explanation of symbols in the tree representation of data
model hierarchy.</t>
</list></t>
</section>
<section title="Changes Between Versions -00 and -01" toc="default">
<t><list style="symbols">
<t>AFN/SAFI-independent stuff was moved to the "ietf-routing"
module.</t>
<t>Typedefs for AFN and SAFI were placed in a separate
"iana-afn-safi" module.</t>
<t>Names of some data nodes were changed, in particular
"routing-process" is now "router".</t>
<t>The restriction of a single AFN/SAFI per router was
lifted.</t>
<t>RPC operation "delete-route" was removed.</t>
<t>Illegal XPath references from "get-route" to the datastore
were fixed.</t>
<t>Section "Security Considerations" was written.</t>
</list></t>
</section>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 10:56:46 |