--- 1/draft-ietf-netmod-routing-cfg-17.txt 2015-04-17 07:15:04.189064002 -0700 +++ 2/draft-ietf-netmod-routing-cfg-18.txt 2015-04-17 07:15:04.317067082 -0700 @@ -1,47 +1,47 @@ NETMOD Working Group L. Lhotka Internet-Draft CZ.NIC Intended status: Standards Track A. Lindem -Expires: September 5, 2015 Cisco Systems - March 04, 2015 +Expires: October 19, 2015 Cisco Systems + April 17, 2015 A YANG Data Model for Routing Management - draft-ietf-netmod-routing-cfg-17 + draft-ietf-netmod-routing-cfg-18 Abstract 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 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. + 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. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on September 5, 2015. + This Internet-Draft will expire on October 19, 2015. Copyright Notice Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -53,68 +53,68 @@ Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology and Notation . . . . . . . . . . . . . . . . . . 3 2.1. Glossary of New Terms . . . . . . . . . . . . . . . . . . 4 2.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 5 2.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 5 3. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. The Design of the Core Routing Data Model . . . . . . . . . . 6 - 4.1. System-Controlled and User-Controlled List Entries . . . 9 - 5. Basic Building Blocks . . . . . . . . . . . . . . . . . . . . 10 - 5.1. Routing Instance . . . . . . . . . . . . . . . . . . . . 10 - 5.1.1. Parameters of IPv6 Routing Instance Interfaces . . . 11 - 5.2. Route . . . . . . . . . . . . . . . . . . . . . . . . . . 12 - 5.3. Routing Information Base (RIB) . . . . . . . . . . . . . 13 - 5.3.1. Multiple RIBs per Address Family . . . . . . . . . . 14 - 5.4. Routing Protocol . . . . . . . . . . . . . . . . . . . . 14 - 5.4.1. Routing Pseudo-Protocols . . . . . . . . . . . . . . 15 - 5.4.2. Defining New Routing Protocols . . . . . . . . . . . 15 - 5.5. RPC Operations . . . . . . . . . . . . . . . . . . . . . 16 - 6. Interactions with Other YANG Modules . . . . . . . . . . . . 17 - 6.1. Module "ietf-interfaces" . . . . . . . . . . . . . . . . 17 - 6.2. Module "ietf-ip" . . . . . . . . . . . . . . . . . . . . 17 - 7. Routing Management YANG Module . . . . . . . . . . . . . . . 18 - 8. IPv4 Unicast Routing Management YANG Module . . . . . . . . . 36 - 9. IPv6 Unicast Routing Management YANG Module . . . . . . . . . 40 - 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 53 - 11. Security Considerations . . . . . . . . . . . . . . . . . . . 54 - 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 55 - 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 55 - 13.1. Normative References . . . . . . . . . . . . . . . . . . 55 - 13.2. Informative References . . . . . . . . . . . . . . . . . 56 - Appendix A. The Complete Data Trees . . . . . . . . . . . . . . 56 - A.1. Configuration Data . . . . . . . . . . . . . . . . . . . 56 - A.2. State Data . . . . . . . . . . . . . . . . . . . . . . . 58 - Appendix B. Minimum Implementation . . . . . . . . . . . . . . . 59 - Appendix C. Example: Adding a New Routing Protocol . . . . . . . 60 - Appendix D. Example: NETCONF Reply . . . . . . . . . . . . 62 - Appendix E. Change Log . . . . . . . . . . . . . . . . . . . . . 69 - E.1. Changes Between Versions -16 and -17 . . . . . . . . . . 69 - E.2. Changes Between Versions -15 and -16 . . . . . . . . . . 69 - E.3. Changes Between Versions -14 and -15 . . . . . . . . . . 70 - E.4. Changes Between Versions -13 and -14 . . . . . . . . . . 70 - E.5. Changes Between Versions -12 and -13 . . . . . . . . . . 70 - E.6. Changes Between Versions -11 and -12 . . . . . . . . . . 71 - E.7. Changes Between Versions -10 and -11 . . . . . . . . . . 71 - E.8. Changes Between Versions -09 and -10 . . . . . . . . . . 72 - E.9. Changes Between Versions -08 and -09 . . . . . . . . . . 72 - E.10. Changes Between Versions -07 and -08 . . . . . . . . . . 72 - E.11. Changes Between Versions -06 and -07 . . . . . . . . . . 72 - E.12. Changes Between Versions -05 and -06 . . . . . . . . . . 73 - E.13. Changes Between Versions -04 and -05 . . . . . . . . . . 73 - E.14. Changes Between Versions -03 and -04 . . . . . . . . . . 74 - E.15. Changes Between Versions -02 and -03 . . . . . . . . . . 74 - E.16. Changes Between Versions -01 and -02 . . . . . . . . . . 75 - E.17. Changes Between Versions -00 and -01 . . . . . . . . . . 75 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 76 + 4.1. System-Controlled and User-Controlled List Entries . . . 8 + 5. Basic Building Blocks . . . . . . . . . . . . . . . . . . . . 8 + 5.1. Routing Instance . . . . . . . . . . . . . . . . . . . . 9 + 5.1.1. Parameters of IPv6 Routing Instance Interfaces . . . 9 + 5.2. Route . . . . . . . . . . . . . . . . . . . . . . . . . . 10 + 5.3. Routing Information Base (RIB) . . . . . . . . . . . . . 11 + 5.4. Routing Protocol . . . . . . . . . . . . . . . . . . . . 11 + 5.4.1. Routing Pseudo-Protocols . . . . . . . . . . . . . . 12 + 5.4.2. Defining New Routing Protocols . . . . . . . . . . . 12 + 5.5. RPC Operations . . . . . . . . . . . . . . . . . . . . . 13 + 6. Interactions with Other YANG Modules . . . . . . . . . . . . 13 + 6.1. Module "ietf-interfaces" . . . . . . . . . . . . . . . . 13 + 6.2. Module "ietf-ip" . . . . . . . . . . . . . . . . . . . . 13 + 7. Routing Management YANG Module . . . . . . . . . . . . . . . 14 + 8. IPv4 Unicast Routing Management YANG Module . . . . . . . . . 29 + 9. IPv6 Unicast Routing Management YANG Module . . . . . . . . . 34 + 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46 + 11. Security Considerations . . . . . . . . . . . . . . . . . . . 48 + 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 48 + 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 49 + 13.1. Normative References . . . . . . . . . . . . . . . . . . 49 + 13.2. Informative References . . . . . . . . . . . . . . . . . 49 + Appendix A. The Complete Data Trees . . . . . . . . . . . . . . 50 + A.1. Configuration Data . . . . . . . . . . . . . . . . . . . 50 + A.2. State Data . . . . . . . . . . . . . . . . . . . . . . . 52 + Appendix B. Minimum Implementation . . . . . . . . . . . . . . . 52 + Appendix C. Example: Adding a New Routing Protocol . . . . . . . 53 + Appendix D. Example: NETCONF Reply . . . . . . . . . . . . 55 + Appendix E. Change Log . . . . . . . . . . . . . . . . . . . . . 62 + E.1. Changes Between Versions -17 and -18 . . . . . . . . . . 62 + E.2. Changes Between Versions -16 and -17 . . . . . . . . . . 63 + E.3. Changes Between Versions -15 and -16 . . . . . . . . . . 63 + E.4. Changes Between Versions -14 and -15 . . . . . . . . . . 64 + E.5. Changes Between Versions -13 and -14 . . . . . . . . . . 64 + E.6. Changes Between Versions -12 and -13 . . . . . . . . . . 64 + E.7. Changes Between Versions -11 and -12 . . . . . . . . . . 65 + E.8. Changes Between Versions -10 and -11 . . . . . . . . . . 65 + E.9. Changes Between Versions -09 and -10 . . . . . . . . . . 65 + E.10. Changes Between Versions -08 and -09 . . . . . . . . . . 66 + E.11. Changes Between Versions -07 and -08 . . . . . . . . . . 66 + E.12. Changes Between Versions -06 and -07 . . . . . . . . . . 66 + E.13. Changes Between Versions -05 and -06 . . . . . . . . . . 66 + E.14. Changes Between Versions -04 and -05 . . . . . . . . . . 67 + E.15. Changes Between Versions -03 and -04 . . . . . . . . . . 68 + E.16. Changes Between Versions -02 and -03 . . . . . . . . . . 68 + E.17. Changes Between Versions -01 and -02 . . . . . . . . . . 69 + E.18. Changes Between Versions -00 and -01 . . . . . . . . . . 69 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 69 1. Introduction This document contains a specification of the following YANG modules: o Module "ietf-routing" provides generic components of a routing data model. o Module "ietf-ipv4-unicast-routing" augments the "ietf-routing" module with additional data specific to IPv4 unicast. @@ -135,47 +135,49 @@ augmented by numerous modules developed by other IETF working groups. 2. Terminology and Notation 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 [RFC2119]. The following terms are defined in [RFC6241]: - o client + o client, - o message + o message, - o protocol operation + o protocol operation, - o server + o server. The following terms are defined in [RFC6020]: - o augment + o augment, - o configuration data + o configuration data, - o data model + o data model, - o data node + o data node, - o feature + o feature, - o mandatory node + o mandatory node, - o module + o module, - o state data + o schema tree, - o RPC operation + o state data, + + o RPC operation. 2.1. Glossary of New Terms core routing data model: YANG data model comprising "ietf-routing", "ietf-ipv4-unicast-routing" and "ietf-ipv6-unicast-routing" modules. direct route: a route to a directly connected network. routing information base (RIB): An object containing a list of @@ -240,27 +242,27 @@ 3. Objectives The initial design of the core routing data model was driven by the following objectives: o 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). - o Simple routing set-ups, such as static routing, should be - configurable in a simple way, ideally without any need to develop - additional YANG modules. + o 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. o On the other hand, the core routing framework must allow for - complicated set-ups involving multiple routing information bases - (RIB) and multiple routing protocols, as well as controlled + complicated implementations involving multiple routing information + bases (RIB) and multiple routing protocols, as well as controlled redistributions of routing information. o 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. 4. The Design of the Core Routing Data Model @@ -268,143 +270,83 @@ 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 1 and 2 show abridged views of the configuration and state data hierarchies. See Appendix A for the complete data trees. +--rw routing +--rw routing-instance* [name] - | +--rw name - | +--rw type? - | +--rw enabled? - | +--rw router-id? - | +--rw description? - | +--rw default-ribs - | | +--rw default-rib* [address-family] - | | +--rw address-family - | | +--rw rib-name - | +--rw interfaces - | | +--rw interface* [name] - | | +--rw name - | | +--rw v6ur:ipv6-router-advertisements - | | ... - | +--rw routing-protocols + +--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 connected-ribs - | | ... | +--rw static-routes | ... +--rw ribs +--rw rib* [name] +--rw name - +--rw address-family + +--rw address-family? +--rw description? - +--rw recipient-ribs - +--rw recipient-rib* [rib-name] - ... Figure 1: Configuration data hierarchy. +--ro routing-state +--ro routing-instance* [name] - | +--ro name - | +--ro type? - | +--ro default-ribs - | | +--ro default-rib* [address-family] - | | +--ro address-family - | | +--ro rib-name - | +--ro interfaces - | | +--ro interface* [name] - | | +--ro name - | | +--ro v6ur:ipv6-router-advertisements - | | ... - | +--ro routing-protocols + +--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 connected-ribs - | ... +--ro ribs +--ro rib* [name] +--ro name +--ro address-family + +--ro default-rib? +--ro routes - | +--ro route* - | ... - +--ro recipient-ribs - +--ro recipient-rib* [rib-name] ... Figure 2: State data hierarchy. As can be seen from Figures 1 and 2, the core routing data model introduces several generic components of a routing framework: routing instances, RIBs containing lists of routes, and routing protocols. - The following subsections describe these components in more detail. - - By combining the components in various ways, and possibly augmenting - them with appropriate contents defined in other modules, various - routing systems can be realized. - - +--------+ - | direct | +--------------+ +--------------+ - | routes |------>| |<------| | - +--------+ | default | | additional | - | RIB | | RIB | - +--------+ | | | | - | static |------>| |------>| | - | routes | +--------------+ +--------------+ - +--------+ ^ | ^ | - | | | | - | v | v - +----------+ +----------+ - | routing | | routing | - | protocol | | protocol | - +----------+ +----------+ - - Figure 3: Example set-up of a routing system - - The example in Figure 3 shows a typical (though certainly not the - only possible) organization of a more complex routing subsystem for a - single address family. Several of its features are worth mentioning: - - o Along with the default RIB, which is always present, an additional - RIB is configured. - - o Each routing protocol instance, including the "static" and - "direct" pseudo-protocols, is connected to one or more RIBs with - which it can exchange routes (in both directions, except for the - "static" and "direct" pseudo-protocols). - - o RIBs may also be connected to each other and exchange routes in - either direction (or both). + Section 5 describes these components in more detail. 4.1. System-Controlled and User-Controlled List Entries - The core routing data model defines several lists, 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 the user. + 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. 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. - Additional entries may be created in the configuration by the user, + 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. Corresponding entries in both versions of the list (in state data and configuration) have the same value of the list key. 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 @@ -435,52 +377,38 @@ 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. 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 [RFC4364]. For each type of routing instance, an - identity derived from "rt:routing-instance" MUST be defined. This + 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). - An implementation MAY create one or more system-controlled routing - instances, and MAY also impose restrictions on types of routing - instances that can be configured, and on the maximum number of - supported instances for each type. For example, a simple router - implementation may support only one system-controlled routing - instance of the default type "rt:default-routing-instance" and may - not allow creation of any user-controlled instances. - 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 list of routing instance - interfaces ("rt:interface"). The key of the list entry is the name - of a configured network layer interface, see the "ietf-interfaces" + (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 [RFC7223]. - A data model for a routing instance type MAY state additional rules - for the assignment of interfaces to routing instances of that type. - For example, it may be required that the sets of interfaces assigned - to different routing instances of a certain type be disjoint. - 5.1.1. Parameters of IPv6 Routing Instance Interfaces - The module "ietf-ipv6-unicast-routing" augments the definition of the - data node "rt:interface", in both configuration and state data, with - definitions of the following variables as required by [RFC4861], sec. - 6.2.1: + YANG module "ietf-ipv6-unicast-routing" (Section 9) augments the + configuration and state data of interfaces with definitions of the + following variables as required by [RFC4861], sec. 6.2.1: o send-advertisements, o max-rtr-adv-interval, o min-rtr-adv-interval, o managed-flag, o other-config-flag, @@ -501,23 +428,20 @@ list: * valid-lifetime, * on-link-flag, * preferred-lifetime, * autonomous-flag. - The definitions and descriptions of the above parameters can be found - in the module "ietf-ipv6-unicast-routing" (Section 9). - NOTES: 1. The "IsRouter" flag, which is also required by [RFC4861], is implemented in the "ietf-ip" module [RFC7277] (leaf "ip:forwarding"). 2. The original specification [RFC4861] 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 @@ -536,151 +460,80 @@ o "destination-prefix": IP prefix specifying the set of destination addresses for which the route may be used. This attribute is mandatory. o "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. o "next-hop": determines the action to be performed with a packet. - See below for details. - - The choice of next-hops comprises the following cases: - - o simple next-hop - IP address of the next-hop router, outgoing - interface, or both. - - o special next-hop - a keyword indicating special packet handling, - one of: - - * "blackhole" - silently discard the packet; - - * "unreachable" - discard the packet and notify the sender with a - "destination unreachable" error message; - - * "prohibit" - discard the packet notify the sender with an - "administratively prohibited" error message. - - It is expected that future YANG modules defining will augment routes - with more complex next-hop types, or additional attributes such as - metrics. Routes are primarily state data that appear as entries of RIBs (Section 5.3) 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. 5.3. Routing Information Base (RIB) - A routing information base (RIB) is a list of routes complemented - with administrative data, namely: - - o "source-protocol": type of the routing protocol from which the - route was originally obtained. - - o "active": an implementation can use this empty leaf to indicate - that the route is preferred among all routes in the same RIB that - have the same destination prefix. - - o "last-updated": the date and time when the route was last updated, - or inserted into the RIB. - - Each RIB MUST contain only routes of one address family. An address - family is represented by an identity derived from the "rt:address- - family" base identity. + 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. In the core routing data model, RIBs are state data represented as - entries of the list "/routing-state/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 Section 5.4.1. - - RIBs are global, which means that a RIB may be used by any or all - routing instances. However, a data model for a routing instance type - MAY state rules and restrictions for sharing RIBs among routing - instances of that type. + 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 Section 5.4.1. Each routing instance has, for every supported address family, one - RIB selected as the so-called default RIB. This selection is - recorded in the list "default-rib". The role of default RIBs is - explained in Section 5.4. + RIB marked as the so-called default RIB. Its role is explained in + Section 5.4. Simple router implementations that do not advertise the feature "multiple-ribs" will typically create one system-controlled RIB per - supported address family, and declare it as the default RIB (via a - system-controlled entry of the "default-rib" list). - -5.3.1. Multiple RIBs per Address Family + routing instance and supported address family, and mark it as the + default RIB. 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. Every RIB can then serve as a - source of routes for other RIBs of the same address family. To - achieve this, one or more recipient RIBs may be specified in the - configuration of the source RIB. - - A RIB MUST NOT appear among its own recipient RIBs. + policy routing and other purposes. 5.4. Routing Protocol 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 (Section 5.4.1). Multiple routing protocol instances of the same type MAY be configured within the same routing instance. - Each routing protocol instance can be connected to one or more RIBs - for each address family that the routing protocol instance supports. - By default, the interaction of a routing protocol instance with its - connected RIBs is governed by the following rules: - - o Routes learned from the network are installed in all connected - RIBs with a matching address family. - - o Conversely, routes from all connected RIBs are injected into the - routing protocol instance. - - However, a data model for a routing protocol MAY impose specific - rules for exchanging routes between routing protocol instances and - connected RIBs. - - On devices supporting the "multiple-ribs" feature, any RIB (system- - controlled or user-controlled) may be connected to a routing protocol - instance by configuring a corresponding entry in the "connected-rib" - list. If such an entry is not configured for an address family, then - the default RIB MUST be used as the connected RIB for this address - family. - 5.4.1. Routing Pseudo-Protocols 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. Routes from both - "direct" and "static" protocol instances are passed to the connected - RIBs, but an exchange in the opposite direction is not allowed. + any routing information with adjacent routers. 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 Section 6.2. The "direct" pseudo-protocol - MUST always be connected to the default RIBs of all supported address - families. Unlike other routing protocol types, this connection - cannot be changed in the configuration. + interface addresses, see Section 6.2. Direct routes MUST be + installed in default RIBs of all supported address families. 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. 5.4.2. Defining New Routing Protocols It is expected that future YANG modules will create data models for additional routing protocol types. Such a new module has to define @@ -703,43 +556,41 @@ and possibly other places in the configuration, state data, notifications, and RPC input or output. o 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". o Per-interface configuration, including activation of the routing protocol on individual interfaces, can use references to entries - in the list of routing instance interfaces (rt:interface). + in the leaf-list of routing instance's interfaces (rt:interface). 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. The above steps are implemented by the example YANG module for the RIP routing protocol in Appendix C. 5.5. RPC Operations - The "ietf-routing" module defines two RPC operations: + The "ietf-routing" module defines one RPC operation: o 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. - o route-count: retrieve the total number of entries in a RIB. - 6. Interactions with Other YANG Modules The semantics of the core routing data model also depends on several configuration parameters that are defined in other YANG modules. 6.1. Module "ietf-interfaces" The following boolean switch is defined in the "ietf-interfaces" YANG module [RFC7223]: @@ -787,30 +637,31 @@ 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. 7. Routing Management YANG Module 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). - file "ietf-routing@2015-03-04.yang" + 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 @@ -833,41 +684,49 @@ 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). - This version of this YANG module is part of RFC XXXX; see the - RFC itself for full legal notices."; + 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). - revision 2015-03-04 { + 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 and the framework for passing routes between RIBs. + RIBs. - Servers that do not advertise this feature MUST provide - exactly one system-controlled RIB per supported address family - and make them also the default RIBs. These RIBs then appear as - entries of the list /routing-state/ribs/rib."; + 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. @@ -939,45 +798,28 @@ 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 rib-ref { - type leafref { - path "/rt:routing/rt:ribs/rt:rib/rt:name"; - } - description - "This type is used for leafs that reference a RIB - configuration."; - } - - typedef rib-state-ref { - type leafref { - path "/rt:routing-state/rt:ribs/rt:rib/rt:name"; - } - description - "This type is used for leafs that reference a RIB in state - data."; - } - 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 @@ -1033,32 +874,33 @@ 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 ECMP."; + 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/rt:name"; + + "rt:interface"; } description "Name of the outgoing interface."; } } case special-next-hop { uses special-next-hop; } } } @@ -1077,21 +919,21 @@ 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/rt:name"; + + "rt:interfaces/rt:interface"; } description "Name of the outgoing interface."; } } case special-next-hop { uses special-next-hop; } } } @@ -1123,113 +966,89 @@ inserted into the RIB."; } } /* State data */ augment "/if:interfaces-state/if:interface" { description "This augment adds a wrapped leaf-list to interface state data."; - container routing-instances { - description - "The enclosed leaf-list provides references to all routing - instances to which the parent interface is assigned. - - The assignments are configured as a part of routing-instance - configuration (module ietf-routing)."; - leaf-list routing-instance { + leaf routing-instance { type routing-instance-state-ref; - must "../../if:name=/rt:routing-state/" + must "../if:name=/rt:routing-state/" + "rt:routing-instance[rt:name=current()]/rt:interfaces/" - + "rt:interface/rt:name" { - error-message "The interface is not assigned to the " - + "routing instance."; + + "rt:interface" { + error-message + "The interface is not assigned to the routing instance."; description - "The reference must mirror a corresponding assignment - under routing-instance."; + "The reference must mirror a corresponding assignment under + routing-instance."; } description - "Reference to a routing instance."; - } + "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 MAY create one or more system-controlled - instances, other user-controlled instances MAY be created by + 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."; } - container default-ribs { - description - "Default RIBs used by the routing instance."; - list default-rib { - key "address-family"; + uses router-id { description - "Each list entry specifies the default RIB for one - address family. - - The default RIB is operationally connected to all - routing protocols for which a connected RIB has not been - explicitly configured. + "Global router ID. - The 'direct' pseudo-protocol is always connected to the - default RIBs."; - uses address-family; - leaf rib-name { - type rib-state-ref; - mandatory "true"; - description - "Name of an existing RIB to be used as the default RIB - for the given routing instance and address family."; - } - } + It may be either configured or assigned algorithmically by + the implementation."; } container interfaces { description "Network layer interfaces belonging to the routing instance."; - list interface { - key "name"; - description - "List of network layer interfaces assigned to the routing - instance."; - leaf name { + leaf-list interface { type if:interface-state-ref; description - "A reference to the name of a configured network layer - interface."; - } + "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. @@ -1254,69 +1073,57 @@ } 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 connected-ribs { - description - "Container for connected RIBs."; - list connected-rib { - key "rib-name"; - description - "List of RIBs to which the routing protocol instance - is connected. - - By default, routes learned by the routing protocol - instance are installed in all connected RIBs of the - matching address family, and, conversely, all routes - from connected RIBs are installed in the routing - protocol instance. However, routing protocols may - specify other rules."; - leaf rib-name { - type rib-state-ref; - description - "Name of an existing RIB."; - } - } - } - } } } 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 + "Each entry represents a RIB identified by the 'name' + key. All routes in a RIB MUST belong to the same address family. - The server MUST provide a system-controlled default RIB - for each supported address family, and MAY provide other - system-controlled RIBs. Additional RIBs MAY be created in - the configuration."; + 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 @@ -1324,33 +1131,21 @@ smaller value means a more preferred route."; } container next-hop { description "Route's next-hop attribute."; uses next-hop-state-content; } uses route-metadata; } } - container recipient-ribs { - description - "Container for recipient RIBs."; - list recipient-rib { - key "rib-name"; - description - "List of RIBs that receive routes from this RIB."; - leaf rib-name { - type rib-state-ref; - description - "The name of the recipient RIB."; - } - } + } } } } /* Configuration Data */ container routing { description "Configuration parameters for the routing subsystem."; @@ -1394,65 +1188,28 @@ 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 default-ribs { - if-feature multiple-ribs; - description - "Configuration of the default RIBs used by the routing - instance. - - The default RIB for an addressed family if by default - connected to all routing protocol instances supporting - that address family, and always receives direct routes."; - list default-rib { - must "address-family=/routing/ribs/rib[name=current()/" - + "rib-name]/address-family" { - error-message "Address family mismatch."; - description - "The entry's address family MUST match that of the - referenced RIB."; - } - key "address-family"; - description - "Each list entry configures the default RIB for one - address family."; - uses address-family; - leaf rib-name { - type string; - mandatory "true"; - description - "Name of an existing RIB to be used as the default RIB - for the given routing instance and address family."; - } - } - } container interfaces { description - "Configuration of the routing instance's interfaces."; - list interface { - key "name"; - description - "List of network layer interfaces assigned to the routing - instance."; - leaf name { + "Assignment of the routing instance's interfaces."; + leaf-list interface { type if:interface-ref; description - "A reference to the name of a configured network layer - interface."; - } + "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."; @@ -1488,125 +1245,81 @@ } 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 connected-ribs { - description - "Configuration of connected RIBs."; - list connected-rib { - key "rib-name"; - description - "Each entry configures a RIB to which the routing - protocol instance is connected. - - If no connected RIB is configured for an address - family, the routing protocol is connected to the - default RIB for that address family."; - leaf rib-name { - type rib-ref; - must "../../../type != 'rt:direct' or " - + "../../../../../default-ribs/ " - + "default-rib/rib-name=." { - error-message "The 'direct' protocol can be " - + "connected only to a default RIB."; - description - "For the 'direct' pseudo-protocol, the connected - RIB must always be a default RIB."; - } - description - "Name of an existing RIB."; - } - } - } 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 represents a configured RIB identified by the - 'name' key. + "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/ribs/rib are used for - configuring parameters of that entry. Other entries define - additional user-controlled RIBs."; + 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. + 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; - leaf description { - type string; - description - "Textual description of the RIB."; - } - container recipient-ribs { - if-feature multiple-ribs; - description - "Configuration of recipient RIBs."; - list recipient-rib { - must "rib-name != ../../name" { - error-message - "Source and recipient RIBs are identical."; + uses address-family { description - "A RIB MUST NOT appear among its recipient RIBs."; + "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"; } - must "/routing/ribs/rib[name=current()/rib-name]/" - + "address-family=../../address-family" { - error-message "Address family mismatch."; - description - "Address family of the recipient RIB MUST match that - of the source RIB."; } - key "rib-name"; - description - "Each entry configures a recipient RIB."; - leaf rib-name { - type rib-ref; + leaf description { + type string; description - "The name of the recipient RIB."; - } + "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"; @@ -1641,70 +1354,41 @@ 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; } - - } - } - - rpc route-count { - description - "Return the current number of routes in a RIB."; - input { - leaf rib-name { - type rib-state-ref; - mandatory "true"; - description - "Name of the RIB. - - If the RIB 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 - 'rib-not-found'."; - } - } - output { - leaf number-of-routes { - type uint64; - mandatory "true"; - description - "Number of routes in the RIB."; - } } } } 8. IPv4 Unicast Routing Management YANG Module 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). - file "ietf-ipv4-unicast-routing@2015-02-10.yang" + 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 @@ -1727,55 +1411,64 @@ 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). - This version of this YANG module is part of RFC XXXX; see the - RFC itself for full legal notices."; + 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). - revision 2015-02-10 { + 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:ribs/rt:rib/rt:routes/rt:route" { + 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:ribs/rt:rib/rt:routes/rt:route/" - + "rt:next-hop/rt:next-hop-options/rt:simple-next-hop" { + 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 @@ -1879,23 +1570,24 @@ } 9. IPv6 Unicast Routing Management YANG Module 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). - file "ietf-ipv6-unicast-routing@2015-02-10.yang" + 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"; @@ -1932,44 +1624,50 @@ 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). - This version of this YANG module is part of RFC XXXX; see the - RFC itself for full legal notices."; + 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). - revision 2015-02-10 { + 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 "/rt:routing-state/rt:routing-instance/rt:interfaces/" - + "rt:interface" { + augment "/if:interfaces-state/if:interface/ip:ipv6" { description - "IPv6-specific parameters of router interfaces."; + "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."; } @@ -2064,90 +1761,94 @@ 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."; + 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."; + 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:ribs/rt:rib/rt:routes/rt:route" { + 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:ribs/rt:rib/rt:routes/rt:route/" - + "rt:next-hop/rt:next-hop-options/rt:simple-next-hop" { + 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 - "/rt:routing/rt:routing-instance/rt:interfaces/rt:interface" { - when "/if:interfaces/if:interface[if:name=current()/rt:name]/" - + "ip:ipv6/ip:enabled='true'" { - description - "This augment is only valid for router interfaces with - enabled IPv6."; - } + + augment "/if:interfaces/if:interface/ip:ipv6" { description - "Configuration of IPv6-specific parameters of router - interfaces."; + "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."; @@ -2482,67 +2183,67 @@ 10. IANA Considerations RFC Ed.: In this section, replace all occurrences of 'XXXX' with the actual RFC number (and remove this note). This document registers the following namespace URIs in the IETF XML registry [RFC3688]: - ---------------------------------------------------------- + -------------------------------------------------------------------- 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. - ---------------------------------------------------------- + -------------------------------------------------------------------- This document registers the following YANG modules in the YANG Module Names registry [RFC6020]: - ------------------------------------------------------------------- + -------------------------------------------------------------------- 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 - ------------------------------------------------------------------- + -------------------------------------------------------------------- 11. Security Considerations Configuration and state data conforming to the core routing data model (defined in this document) are designed to be accessed via the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the secure transport layer and the mandatory-to-implement secure transport is SSH [RFC6242]. The NETCONF access control model [RFC6536] provides the means to restrict access for particular NETCONF users to a pre- configured subset of all available NETCONF protocol operations and @@ -2559,22 +2260,22 @@ The vulnerable "config true" subtrees and data nodes are the following: /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. /routing/routing-instance/routing-protocols/routing-protocol: This list specifies the routing protocols configured on a device. - /routing/ribs/rib: This list specifies the RIBs configured for the - device. + /routing/routing-instance/ribs/rib: This list specifies the RIBs + configured for the device. 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. 12. Acknowledgments The authors wish to thank Nitin Bahadur, Martin Bjorklund, Dean Bogdanovic, Jeff Haas, Joel Halpern, Wes Hardaker, Sriganesh Kini, @@ -2626,210 +2327,140 @@ [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, June 2011. [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration Protocol (NETCONF) Access Control Model", RFC 6536, March 2012. Appendix A. The Complete Data Trees This appendix presents the complete configuration and state data - trees of the core routing data model. - - See Section 2.2 for an explanation of the symbols used. Data type of - every leaf node is shown near the right end of the corresponding - line. + trees of the core routing data model. See Section 2.2 for an + explanation of the symbols used. Data type of every leaf node is + shown near the right end of the corresponding line. A.1. Configuration Data - +--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 default-ribs {multiple-ribs}? - | | +--rw default-rib* [address-family] - | | +--rw address-family identityref - | | +--rw rib-name string - | +--rw interfaces - | | +--rw interface* [name] - | | +--rw name if:interface-ref - | | +--rw v6ur:ipv6-router-advertisements - | | +--rw v6ur:send-advertisements? boolean - | | +--rw v6ur:max-rtr-adv-interval? uint16 - | | +--rw v6ur:min-rtr-adv-interval? uint16 - | | +--rw v6ur:managed-flag? boolean - | | +--rw v6ur:other-config-flag? boolean - | | +--rw v6ur:link-mtu? uint32 - | | +--rw v6ur:reachable-time? uint32 - | | +--rw v6ur:retrans-timer? uint32 - | | +--rw v6ur:cur-hop-limit? uint8 - | | +--rw v6ur:default-lifetime? uint16 - | | +--rw v6ur:prefix-list - | | +--rw v6ur:prefix* [prefix-spec] - | | +--rw v6ur:prefix-spec inet:ipv6-prefix - | | +--rw (control-adv-prefixes)? - | | +--:(no-advertise) - | | | +--rw v6ur:no-advertise? empty - | | +--:(advertise) - | | +--rw v6ur:valid-lifetime? uint32 - | | +--rw v6ur:on-link-flag? boolean - | | +--rw v6ur:preferred-lifetime? uint32 - | | +--rw v6ur:autonomous-flag? boolean - | +--rw routing-protocols + +--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 connected-ribs - | | +--rw connected-rib* [rib-name] - | | +--rw rib-name rib-ref | +--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? enumeration + | | | +--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? enumeration + | | +--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 address-family? identityref +--rw description? string - +--rw recipient-ribs {multiple-ribs}? - +--rw recipient-rib* [rib-name] - +--rw rib-name rib-ref A.2. State Data +--ro routing-state +--ro routing-instance* [name] - | +--ro name string - | +--ro type? identityref - | +--ro default-ribs - | | +--ro default-rib* [address-family] - | | +--ro address-family identityref - | | +--ro rib-name rib-state-ref - | +--ro interfaces - | | +--ro interface* [name] - | | +--ro name if:interface-state-ref - | | +--ro v6ur:ipv6-router-advertisements - | | +--ro v6ur:send-advertisements? boolean - | | +--ro v6ur:max-rtr-adv-interval? uint16 - | | +--ro v6ur:min-rtr-adv-interval? uint16 - | | +--ro v6ur:managed-flag? boolean - | | +--ro v6ur:other-config-flag? boolean - | | +--ro v6ur:link-mtu? uint32 - | | +--ro v6ur:reachable-time? uint32 - | | +--ro v6ur:retrans-timer? uint32 - | | +--ro v6ur:cur-hop-limit? uint8 - | | +--ro v6ur:default-lifetime? uint16 - | | +--ro v6ur:prefix-list - | | +--ro v6ur:prefix* [prefix-spec] - | | +--ro v6ur:prefix-spec inet:ipv6-prefix - | | +--ro v6ur:valid-lifetime? uint32 - | | +--ro v6ur:on-link-flag? boolean - | | +--ro v6ur:preferred-lifetime? uint32 - | | +--ro v6ur:autonomous-flag? boolean - | +--ro routing-protocols + +--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 connected-ribs - | +--ro connected-rib* [rib-name] - | +--ro rib-name rib-state-ref +--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? inet:ipv6-address - | | | +--ro v4ur:next-hop-address? inet:ipv4-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 - +--ro recipient-ribs - +--ro recipient-rib* [rib-name] - +--ro rib-name rib-state-ref + +--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 Appendix B. Minimum Implementation 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. A minimum implementation will provide a single system-controlled routing instance, and will not allow clients to create any user- controlled instances. 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, so references to them will also appear as system- - controlled entries of the "default-rib" list in state data. No user- - controlled RIBs are allowed. + the default RIBs. No user-controlled RIBs are allowed. In addition to the mandatory instance of the "direct" pseudo- - protocol, a minimum implementation should support configured - instance(s) of the "static" pseudo-protocol. Even with a single RIB - per address family, it may be occasionally useful to be able to - configure multiple "static" instances. For example, a client may - want to configure alternative sets of static routes and activate or - deactivate them by means of connnecting the default RIB to the - corresponding "static" instance. + protocol, a minimum implementation should support configuring + instance(s) of the "static" pseudo-protocol. Platforms with severely constrained resources may use deviations for restricting the data model, e.g., limiting the number of "static" routing protocol instances. Appendix C. Example: Adding a New Routing Protocol 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 only 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 + "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 [RFC6087]. See also Section 5.4.2. module example-rip { namespace "http://example.com/rip"; prefix "rip"; import ietf-routing { prefix "rt"; @@ -2855,32 +2486,33 @@ } 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:ribs/rt:rib/rt:routes/rt:route" { + 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:active-route/rt:output/rt:route" { + 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 @@ -2892,25 +2524,23 @@ "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/" - + "rt:name"; + path "../../../../../../rt:interfaces/rt:interface"; } } leaf enabled { type boolean; default "true"; } leaf metric { type rip-metric; default "1"; } @@ -2938,21 +2568,21 @@ o ietf-interfaces [RFC7223], o ietf-ip [RFC7277], o ietf-routing (Section 7), o ietf-ipv4-unicast-routing (Section 8), o ietf-ipv6-unicast-routing (Section 9). - We assume a simple network set-up as shown in Figure 4: router "A" + We assume a simple network set-up as shown in Figure 3: 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. +-----------------+ | | | Router ISP | | | +--------+--------+ @@ -2964,21 +2594,21 @@ eth0|192.0.2.1 +--------+--------+ | | | Router A | | | +--------+--------+ eth1|198.51.100.1 |2001:db8:0:2::1 | - Figure 4: Example network configuration + Figure 3: Example network configuration A reply to the NETCONF message sent by router "A" would then be as follows: eth0 ianaift:ethernetCsmacd 00:0C:42:E5:B1:E9 up + rtr0 2014-10-24T17:11:27+00:58 true 1500 192.0.2.1 24 true 1500 2001:0db8:0:1::1 64 + + true + + + 2001:db8:0:2::/64 + + + eth1 ianaift:ethernetCsmacd - up 00:0C:42:E5:B1:EA + up + rtr0 2014-10-24T17:11:27+00:59 true 1500 198.51.100.1 @@ -3075,131 +2715,117 @@ 2014-10-24T17:11:27+00:59 true 1500 198.51.100.1 24 + true 1500 2001:0db8:0:2::1 64 - - - - - - - rtr0 - Router A - - - eth1 true 2001:db8:0:2::/64 - + + + + + + rtr0 + Router A + 192.0.2.1 + + eth0 + eth1 rt:static st0 Static routing is used for the internal network. - 0.0.0.0/0 + + 0.0.0.0/0 + 192.0.2.2 ::/0 - 2001:db8:0:1::2 + + 2001:db8:0:1::2 + rtr0 - - - v4ur:ipv4-unicast - ipv4-master - - - v6ur:ipv6-unicast - ipv6-master - - - - eth0 - - - eth1 - - true - - - 2001:db8:0:2::/64 - - - - + eth0 + eth1 rt:static st0 5 - ipv4-master v4ur:ipv4-unicast + true - 192.0.2.1/24 + + 192.0.2.1/24 + eth0 0 rt:direct 2014-10-24T17:11:27+01:00 - 198.51.100.0/24 + + 198.51.100.0/24 + eth1 rt:direct 0 2014-10-24T17:11:27+01:00 0.0.0.0/0 rt:static @@ -3207,20 +2833,21 @@ 192.0.2.2 2014-10-24T18:02:45+01:00 ipv6-master v6ur:ipv6-unicast + true 2001:db8:0:1::/64 eth0 rt:direct 0 @@ -3233,55 +2860,84 @@ eth1 rt:direct 0 2014-10-24T17:11:27+01:00 ::/0 - 2001:db8:0:1::2 + + 2001:db8:0:1::2 + rt:static 5 2014-10-24T18:02:45+01:00 + Appendix E. Change Log RFC Editor: Remove this section upon publication as an RFC. -E.1. Changes Between Versions -16 and -17 +E.1. Changes Between Versions -17 and -18 + + o The container "ribs" was moved under "routing-instance" (in both + "routing" and "routing-state"). + + o Typedefs "rib-ref" and "rib-state-ref" were removed. + + o Removed "recipient-ribs" (both state and configuration). + + o Removed "connected-ribs" from "routing-protocol" (both state and + configuration). + + o Configuration and state data for IPv6 RA were moved under + "if:interface" and "if:interface-state". + + o 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). + + o Specification of a default RIB is now a simple flag under "rib" + (both config and state). + + o Default RIBs are marked by a flag in state data. + +E.2. Changes Between Versions -16 and -17 o Added Acee as a co-author. o Removed all traces of route filters. o Removed numeric IDs of list entries in state data. o Removed all next-hop cases except "simple-next-hop" and "special- next-hop". o Removed feature "multipath-routes". o 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. -E.2. Changes Between Versions -15 and -16 +E.3. Changes Between Versions -15 and -16 o Added 'type' as the second key component of 'routing-protocol', both in configuration and state data. o The restriction of no more than one connected RIB per address family was removed. o Removed the 'id' key of routes in RIBs. This list has no keys anymore. @@ -3302,39 +2958,39 @@ o Added next-hop lists to state data. o Added two cases for specifying next-hops indirectly - via a new RIB or a recursive list of next-hops. o Reorganized next-hop in static routes. o Removed all 'if-feature' statements from state data. -E.3. Changes Between Versions -14 and -15 +E.4. Changes Between Versions -14 and -15 o Removed all defaults from state data. o Removed default from 'cur-hop-limit' in config. -E.4. Changes Between Versions -13 and -14 +E.5. Changes Between Versions -13 and -14 o Removed dependency of 'connected-ribs' on the 'multiple-ribs' feature. o Removed default value of 'cur-hop-limit' in state data. o Moved parts of descriptions and all references on IPv6 RA parameters from state data to configuration. o Added reference to RFC 6536 in the Security section. -E.5. Changes Between Versions -12 and -13 +E.6. Changes Between Versions -12 and -13 o Wrote appendix about minimum implementation. o Remove "when" statement for IPv6 router interface state data - it was dependent on a config value that may not be present. o Extra container for the next-hop list. o Names rather than numeric ids are used for referring to list entries in state data. @@ -3347,34 +3003,34 @@ o o Removed "if-feature multiple-ribs;" from connected-ribs. o "rib-name" instead of "name" is used as the name of leafref nodes. o "next-hop" instead of "nexthop" or "gateway" used throughout, both in node names and text. -E.6. Changes Between Versions -11 and -12 +E.7. Changes Between Versions -11 and -12 o Removed feature "advanced-router" and introduced two features instead: "multiple-ribs" and "multipath-routes". o Unified the keys of config and state versions of "routing- instance" and "rib" lists. o Numerical identifiers of state list entries are not keys anymore, but they are constrained using the "unique" statement. o Updated acknowledgements. -E.7. Changes Between Versions -10 and -11 +E.8. Changes Between Versions -10 and -11 o Migrated address families from IANA enumerations to identities. o Terminology and node names aligned with the I2RS RIB model: router -> routing instance, routing table -> RIB. o Introduced uint64 keys for state lists: routing-instance, rib, route, nexthop. o Described the relationship between system-controlled and user- @@ -3384,70 +3040,70 @@ router". o Made nexthop into a choice in order to allow for nexthop-list (I2RS requirement). o Added nexthop-list with entries having priorities (backup) and weights (load balancing). o Updated bibliography references. -E.8. Changes Between Versions -09 and -10 +E.9. Changes Between Versions -09 and -10 o Added subtree for state data ("/routing-state"). o Terms "system-controlled entry" and "user-controlled entry" defined and used. o New feature "user-defined-routing-tables". Nodes that are useful only with user-defined routing tables are now conditional. o Added grouping "router-id". o In routing tables, "source-protocol" attribute of routes now reports only protocol type, and its datatype is "identityref". o Renamed "main-routing-table" to "default-routing-table". -E.9. Changes Between Versions -08 and -09 +E.10. Changes Between Versions -08 and -09 o Fixed "must" expresion for "connected-routing-table". o Simplified "must" expression for "main-routing-table". o Moved per-interface configuration of a new routing protocol under 'routing-protocol'. This also affects the 'example-rip' module. -E.10. Changes Between Versions -07 and -08 +E.11. Changes Between Versions -07 and -08 o Changed reference from RFC6021 to RFC6021bis. -E.11. Changes Between Versions -06 and -07 +E.12. Changes Between Versions -06 and -07 o The contents of in Appendix D was updated: "eth[01]" is used as the value of "location", and "forwarding" is on for both interfaces and both IPv4 and IPv6. o 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. o The default behavior for IPv6 RA prefix advertisements was clarified. o Changed type of "rt:router-id" to "ip:dotted-quad". o Type of "rt:router-id" changed to "yang:dotted-quad". o Fixed missing prefixes in XPath expressions. -E.12. Changes Between Versions -05 and -06 +E.13. Changes Between Versions -05 and -06 o Document title changed: "Configuration" was replaced by "Management". o New typedefs "routing-table-ref" and "route-filter-ref". o Double slashes "//" were removed from XPath expressions and replaced with the single "/". o Removed uniqueness requirement for "router-id". @@ -3455,21 +3111,21 @@ o Complete data tree is now in Appendix A. o Changed type of "source-protocol" from "leafref" to "string". o Clarified the relationship between routing protocol instances and connected routing tables. o Added a must constraint saying that a routing table connected to the direct pseudo-protocol must not be a main routing table. -E.13. Changes Between Versions -04 and -05 +E.14. Changes Between Versions -04 and -05 o Routing tables are now global, i.e., "routing-tables" is a child of "routing" rather than "router". o "must" statement for "static-routes" changed to "when". o Added "main-routing-tables" containing references to main routing tables for each address family. o Removed the defaults for "address-family" and "safi" and made them @@ -3490,35 +3146,35 @@ o The "direct" pseudo-protocol is always connected to main routing tables. o Entries in the list of connected routing tables renamed from "routing-table" to "connected-routing-table". o Added "must" constraint saying that a routing table must not be its own recipient. -E.14. Changes Between Versions -03 and -04 +E.15. Changes Between Versions -03 and -04 o Changed "error-tag" for both RPC operations from "missing element" to "data-missing". o Removed the decrementing behavior for advertised IPv6 prefix parameters "valid-lifetime" and "preferred-lifetime". o Changed the key of the static route lists from "seqno" to "id" because the routes needn't be sorted. o Added 'must' constraint saying that "preferred-lifetime" must not be greater than "valid-lifetime". -E.15. Changes Between Versions -02 and -03 +E.16. Changes Between Versions -02 and -03 o Module "iana-afn-safi" moved to I-D "iana-if-type". o Removed forwarding table. o RPC "get-route" changed to "active-route". Its output is a list of routes (for multi-path routing). o New RPC "route-count". @@ -3536,21 +3192,21 @@ "ietf-ip". o Added "router-id" leaf. o Specified the names for IPv4/IPv6 unicast main routing tables. o Route parameter "last-modified" changed to "age". o Added container "recipient-routing-tables". -E.16. Changes Between Versions -01 and -02 +E.17. Changes Between Versions -01 and -02 o Added module "ietf-ipv6-unicast-routing". o The example in Appendix D now uses IP addresses from blocks reserved for documentation. o Direct routes appear by default in the forwarding table. o Network layer interfaces must be assigned to a router instance. Additional interface configuration may be present. @@ -3560,21 +3216,21 @@ o Additional "must" statements were added. o The "route-content" grouping for IPv4 and IPv6 unicast now includes the material from the "ietf-routing" version via "uses rt:route-content". o Explanation of symbols in the tree representation of data model hierarchy. -E.17. Changes Between Versions -00 and -01 +E.18. Changes Between Versions -00 and -01 o AFN/SAFI-independent stuff was moved to the "ietf-routing" module. o Typedefs for AFN and SAFI were placed in a separate "iana-afn- safi" module. o Names of some data nodes were changed, in particular "routing- process" is now "router". o The restriction of a single AFN/SAFI per router was lifted.