--- 1/draft-ietf-netmod-routing-cfg-11.txt 2013-11-07 17:14:30.843758786 -0800 +++ 2/draft-ietf-netmod-routing-cfg-12.txt 2013-11-07 17:14:30.991762297 -0800 @@ -1,18 +1,18 @@ NETMOD L. Lhotka Internet-Draft CZ.NIC -Intended status: Standards Track October 18, 2013 -Expires: April 21, 2014 +Intended status: Standards Track November 07, 2013 +Expires: May 11, 2014 A YANG Data Model for Routing Management - draft-ietf-netmod-routing-cfg-11 + draft-ietf-netmod-routing-cfg-12 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 individual routing protocols and other related functions. The core routing data model provides common building blocks for such extensions - routing instances, routes, @@ -26,21 +26,21 @@ 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 April 21, 2014. + This Internet-Draft will expire on May 11, 2014. Copyright Notice Copyright (c) 2013 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,62 +53,63 @@ Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology and Notation . . . . . . . . . . . . . . . . . . . 5 2.1. Glossary of New Terms . . . . . . . . . . . . . . . . . . 5 2.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 6 2.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 6 3. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4. The Design of the Core Routing Data Model . . . . . . . . . . 9 4.1. System-Controlled and User-Controlled List Entries . . . . 12 - 4.2. Simple versus Advanced Routers . . . . . . . . . . . . . . 13 - 5. Basic Building Blocks . . . . . . . . . . . . . . . . . . . . 15 - 5.1. Routing Instance . . . . . . . . . . . . . . . . . . . . . 15 - 5.1.1. Parameters of IPv6 Routing Instance Interfaces . . . . 16 - 5.2. Route . . . . . . . . . . . . . . . . . . . . . . . . . . 17 - 5.3. Routing Information Base (RIB) . . . . . . . . . . . . . . 17 - 5.3.1. Multiple RIBs per Address Family . . . . . . . . . . . 18 - 5.4. Routing Protocol . . . . . . . . . . . . . . . . . . . . . 18 - 5.4.1. Routing Pseudo-Protocols . . . . . . . . . . . . . . . 19 - 5.4.2. Defining New Routing Protocols . . . . . . . . . . . . 21 - 5.5. Route Filter . . . . . . . . . . . . . . . . . . . . . . . 22 - 5.6. RPC Operations . . . . . . . . . . . . . . . . . . . . . . 23 - 6. Interactions with Other YANG Modules . . . . . . . . . . . . . 24 - 6.1. Module "ietf-interfaces" . . . . . . . . . . . . . . . . . 24 - 6.2. Module "ietf-ip" . . . . . . . . . . . . . . . . . . . . . 24 - 7. Routing YANG Module . . . . . . . . . . . . . . . . . . . . . 26 - 8. IPv4 Unicast Routing YANG Module . . . . . . . . . . . . . . . 48 - 9. IPv6 Unicast Routing YANG Module . . . . . . . . . . . . . . . 55 - 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 70 - 11. Security Considerations . . . . . . . . . . . . . . . . . . . 72 - 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 73 - 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 74 - 13.1. Normative References . . . . . . . . . . . . . . . . . . . 74 - 13.2. Informative References . . . . . . . . . . . . . . . . . . 74 - Appendix A. The Complete Data Trees . . . . . . . . . . . . . . . 75 - A.1. Configuration Data . . . . . . . . . . . . . . . . . . . . 75 - A.2. Operational State Data . . . . . . . . . . . . . . . . . . 77 - Appendix B. Example: Adding a New Routing Protocol . . . . . . . 79 - Appendix C. Example: NETCONF Reply . . . . . . . . . . . . 82 - Appendix D. Change Log . . . . . . . . . . . . . . . . . . . . . 88 - D.1. Changes Between Versions -10 and -11 . . . . . . . . . . . 88 - D.2. Changes Between Versions -09 and -10 . . . . . . . . . . . 88 - D.3. Changes Between Versions -08 and -09 . . . . . . . . . . . 89 - D.4. Changes Between Versions -07 and -08 . . . . . . . . . . . 89 - D.5. Changes Between Versions -06 and -07 . . . . . . . . . . . 89 - D.6. Changes Between Versions -05 and -06 . . . . . . . . . . . 89 - D.7. Changes Between Versions -04 and -05 . . . . . . . . . . . 90 - D.8. Changes Between Versions -03 and -04 . . . . . . . . . . . 90 - D.9. Changes Between Versions -02 and -03 . . . . . . . . . . . 91 - D.10. Changes Between Versions -01 and -02 . . . . . . . . . . . 91 - D.11. Changes Between Versions -00 and -01 . . . . . . . . . . . 92 - Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 93 + 4.2. Features of Advanced Routers . . . . . . . . . . . . . . . 13 + 5. Basic Building Blocks . . . . . . . . . . . . . . . . . . . . 14 + 5.1. Routing Instance . . . . . . . . . . . . . . . . . . . . . 14 + 5.1.1. Parameters of IPv6 Routing Instance Interfaces . . . . 15 + 5.2. Route . . . . . . . . . . . . . . . . . . . . . . . . . . 16 + 5.3. Routing Information Base (RIB) . . . . . . . . . . . . . . 16 + 5.3.1. Multiple RIBs per Address Family . . . . . . . . . . . 17 + 5.4. Routing Protocol . . . . . . . . . . . . . . . . . . . . . 17 + 5.4.1. Routing Pseudo-Protocols . . . . . . . . . . . . . . . 18 + 5.4.2. Defining New Routing Protocols . . . . . . . . . . . . 20 + 5.5. Route Filter . . . . . . . . . . . . . . . . . . . . . . . 21 + 5.6. RPC Operations . . . . . . . . . . . . . . . . . . . . . . 22 + 6. Interactions with Other YANG Modules . . . . . . . . . . . . . 23 + 6.1. Module "ietf-interfaces" . . . . . . . . . . . . . . . . . 23 + 6.2. Module "ietf-ip" . . . . . . . . . . . . . . . . . . . . . 23 + 7. Routing YANG Module . . . . . . . . . . . . . . . . . . . . . 25 + 8. IPv4 Unicast Routing YANG Module . . . . . . . . . . . . . . . 47 + 9. IPv6 Unicast Routing YANG Module . . . . . . . . . . . . . . . 54 + 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 69 + 11. Security Considerations . . . . . . . . . . . . . . . . . . . 71 + 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 72 + 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 73 + 13.1. Normative References . . . . . . . . . . . . . . . . . . . 73 + 13.2. Informative References . . . . . . . . . . . . . . . . . . 73 + Appendix A. The Complete Data Trees . . . . . . . . . . . . . . . 74 + A.1. Configuration Data . . . . . . . . . . . . . . . . . . . . 74 + A.2. Operational State Data . . . . . . . . . . . . . . . . . . 76 + Appendix B. Example: Adding a New Routing Protocol . . . . . . . 78 + Appendix C. Example: NETCONF Reply . . . . . . . . . . . . 81 + Appendix D. Change Log . . . . . . . . . . . . . . . . . . . . . 87 + D.1. Changes Between Versions -11 and -12 . . . . . . . . . . . 87 + D.2. Changes Between Versions -10 and -11 . . . . . . . . . . . 87 + D.3. Changes Between Versions -09 and -10 . . . . . . . . . . . 87 + D.4. Changes Between Versions -08 and -09 . . . . . . . . . . . 88 + D.5. Changes Between Versions -07 and -08 . . . . . . . . . . . 88 + D.6. Changes Between Versions -06 and -07 . . . . . . . . . . . 88 + D.7. Changes Between Versions -05 and -06 . . . . . . . . . . . 88 + D.8. Changes Between Versions -04 and -05 . . . . . . . . . . . 89 + D.9. Changes Between Versions -03 and -04 . . . . . . . . . . . 90 + D.10. Changes Between Versions -02 and -03 . . . . . . . . . . . 90 + D.11. Changes Between Versions -01 and -02 . . . . . . . . . . . 91 + D.12. Changes Between Versions -00 and -01 . . . . . . . . . . . 91 + Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 92 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. @@ -162,22 +163,21 @@ o state data o RPC operation 2.1. Glossary of New Terms active route: a route that is actually used for sending packets. If there are multiple candidate routes with a matching destination prefix, then it is up to the routing algorithm to select the - active route (or several active routes in the case of multi-path - routing). + active route. core routing data model: YANG data model resulting from the combination of "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 routes together with other information. See Section 5.3 for details. @@ -274,21 +274,20 @@ 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 operational state data hierarchies. See Appendix A for the complete data trees. +--rw routing +--rw routing-instance* [name] | +--rw name - | +--rw routing-instance-id? | +--rw type? | +--rw enabled? | +--rw router-id? | +--rw description? | +--rw default-ribs | | +--rw default-rib* [address-family] | | +--rw address-family | | +--rw name | +--rw interfaces | | +--rw interface* [name] @@ -301,62 +300,61 @@ | +--rw description? | +--rw enabled? | +--rw type | +--rw connected-ribs | | ... | +--rw static-routes | ... +--rw ribs | +--rw rib* [name] | +--rw name - | +--rw id? | +--rw address-family | +--rw description? | +--rw recipient-ribs | +--rw recipient-rib* [rib-name] | ... +--rw route-filters +--rw route-filter* [name] +--rw name +--rw description? +--rw type Figure 1: Configuration data hierarchy. +--ro routing-state - +--ro routing-instance* [id] - | +--ro id - | +--ro name? + +--ro routing-instance* [name] + | +--ro name + | +--ro id? | +--ro type? | +--ro router-id? | +--ro default-ribs | | +--ro default-rib* [address-family] | | +--ro address-family | | +--ro rib-id | +--ro interfaces | | +--ro interface* [name] | | +--ro name | | +--ro v6ur:ipv6-router-advertisements | | ... | +--ro routing-protocols | +--ro routing-protocol* [name] | +--ro name | +--ro type | +--ro connected-ribs | ... +--ro ribs - | +--ro rib* [id] - | +--ro id - | +--ro name? + | +--ro rib* [name] + | +--ro name + | +--ro id? | +--ro address-family | +--ro routes - | | +--ro route* [id] + | | +--ro route* | | ... | +--ro recipient-ribs | +--ro recipient-rib* [rib-id] | ... +--ro route-filters +--ro route-filter* [name] +--ro name +--ro type Figure 2: Operational state data hierarchy. @@ -406,82 +404,72 @@ "static" and "direct" pseudo-protocols). o RIBs may also be connected to each other and exchange routes in either direction (or both). o Route exchanges along all connections may be controlled by means of route filters, denoted by "F" in Figure 3. 4.1. System-Controlled and User-Controlled List Entries - The core routing data model defines several lists, for example "rt: - routing-instance" or "rt: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, 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. In such a list, the server creates the required item as a so-called system-controlled entry in operational state data, i.e., inside the - "rt:routing-state" container. + "routing-state" container. Additional entries may be created in the configuration by the user - via the NETCONF protocol. These are the so-called user-controlled + 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 operational state version of the list. - Each version of the list (in operational state data and - configuration) uses its own set of list keys. In operational state, - the keys are unique numeric identifiers assigned by the server. In - configuration, the list keys are selected by the user. + Both versions of the list (in operational state data and + configuration) use the "name" leaf as their 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 an arbitrary key and desired configuration - contents. In order to bind this entry with the corresponding entry - in the operational state list, the user writes the operational state - key as a value of a special leaf that is defined in the data model - for this purpose. + configuration with the desired contents. In order to bind this entry + with the corresponding entry in the operational state list, the key + of the configuration entry has to be set to the same value as the key + of the state entry. An example can be seen in Appendix C: the "/routing-state/ routing-instance" list has a single system-controlled entry whose - "id" key has the value "1415926535". This entry is configured by the - "/routing/routing-instance" entry whose "name" key is "rtr0". The - binding with the operational state entry is established through the - value of the leaf "routing-instance-id". + "name" key has the value "rtr0". This entry is configured by the + "/routing/routing-instance" entry whose "name" key is also "rtr0". Deleting a user-controlled entry from the configuration list results in the removal of the corresponding entry in the operational state 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 operational state entry remains in the list. -4.2. Simple versus Advanced Routers +4.2. Features of Advanced Routers The core routing data model attempts to address devices with elementary routing functions as well as advanced routers. For simple devices, some parts and options of the data model are not needed and - represent unnecessary complications for the implementation. + would represent unnecessary complications for the implementation. Therefore, the core routing data model makes the advanced - functionality optional by means of a feature "advanced-router". - - Specifically, the following objects and options are supported only in - devices that advertise the "advanced-router" feature: - - o multiple RIBs per address family, and user-controlled RIB entries - in particular, - - o routing protocols connected to non-default RIBs, + functionality optional by means of two YANG features: - o RIBs configured as receivers of routes from other RIBs, + o "multiple-ribs" - indicates that the device supports multiple RIBs + per address family, routing protocols connected to non-default + RIBs, and RIBs configured as receivers of routes from other RIBs. - o routes with multiple nexthops. + o "multipath-routes" - indicates that the device supports routes + with multiple nexthops. See the "ietf-routing" module for details. 5. Basic Building Blocks This section describes the essential components of the core routing data model. 5.1. Routing Instance @@ -515,21 +503,21 @@ 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" module [YANG-IF]. In YANG terms, the list of routing instance interfaces is modeled as - the "list" node rather than "leaf-list" in order to allow for adding, + a "list" node rather than "leaf-list" in order to allow for adding, via augmentation, other configuration or state data related to the corresponding interface. Implementations MAY specify additional rules for the assignment of interfaces to routing instances. For example, it may be required that the sets of interfaces assigned to different routing instances be disjoint. 5.1.1. Parameters of IPv6 Routing Instance Interfaces @@ -594,22 +582,22 @@ Routes are basic elements of information in a routing system. The core routing data model defines only the following minimal set of route attributes: o destination prefix: IP prefix specifying the set of destination addresses for which the route may be used. This attribute is mandatory. o next hop or action: outgoing interface, IP address of one or more - adjacent routers to which a packet should be forwarded, or other - special action. + adjacent routers to which a packet should be forwarded, or a + special action such as discarding the packet. The above list of route attributes suffices for a simple static routing configuration. It is expected that future modules defining routing protocols will add other route attributes such as metrics or preferences. Routes and their attributes are used both in configuration data, for example as manually configured static routes, and in operational state data, for example as entries in RIBs. @@ -617,48 +605,48 @@ 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 "last-updated": the date and time when the route was last updated, or inserted into the RIB. - Each RIB MUST contain only routes of the same address family. In the - data model, address family is represented with an identity derived - from the "rt:address-family" base identity. + Each RIB MUST contain only routes of one address family. In the data + model, address family is represented with an identity derived from + the "rt:address-family" base identity. In the core routing data model, RIBs are operational 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, an implementation MAY specify rules and restrictions for sharing RIBs among routing instances. Each routing instance must have, 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. Simple router implementations that do not advertise the feature - "advanced-router" will typically create one system-controlled RIB per + "multiple-ribs" will typically create one system-controlled RIB per supported address family, and declare it as a default RIB (via a system-controlled entry of the "default-rib" list). 5.3.1. Multiple RIBs per Address Family - More complex router implementations advertising the "advanced-router" + 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. Optionally, a route filter may be configured for any or all recipient RIBs. Such a route filter then selects and/or manipulates the routes that are passed between the source and recipient RIB. A RIB MUST NOT appear among its own recipient RIBs. @@ -674,21 +662,21 @@ Each routing protocol instance is connected to exactly one RIB for each address family that the routing protocol instance supports. Routes learned from the network by a routing protocol are normally installed into the connected RIB(s) and, conversely, routes from the connected RIB(s) are normally injected into the routing protocol. However, routing protocol implementations MAY specify rules that restrict this exchange of routes in either direction (or both directions). - On devices supporting the "advanced-router" feature, any RIB (system- + 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. In addition, two independent route filters (see Section 5.5) may be configured for each connected RIB to apply user-defined policies controlling the exchange of routes in both directions between the routing protocol instance and the connected RIB: @@ -736,39 +724,39 @@ | +--rw v4ur:route* [id] | +--rw v4ur:id | +--rw v4ur:description? | +--rw v4ur:destination-prefix | +--rw (nexthop-options) | +--:(special-nexthop) | | +--rw v4ur:special-nexthop? | +--:(simple-nexthop) | | +--rw v4ur:gateway? | | +--rw v4ur:outgoing-interface? - | +--:(nexthop-list) {rt:advanced-router}? + | +--:(nexthop-list) {rt:multipath-routes}? | +--rw v4ur:nexthop* [id] | +--rw v4ur:id | +--rw v4ur:address? | +--rw v4ur:outgoing-interface? | +--rw v4ur:priority? | +--rw v4ur:weight? +--rw v6ur:ipv6 +--rw v6ur:route* [id] +--rw v6ur:id +--rw v6ur:description? +--rw v6ur:destination-prefix +--rw (nexthop-options) +--:(special-nexthop) | +--rw v6ur:special-nexthop? +--:(simple-nexthop) | +--rw v6ur:gateway? | +--rw v6ur:outgoing-interface? - +--:(nexthop-list) {rt:advanced-router}? + +--:(nexthop-list) {rt:multipath-routes}? +--rw v6ur:nexthop* [id] +--rw v6ur:id +--rw v6ur:address? +--rw v6ur:outgoing-interface? +--rw v6ur:priority? +--rw v6ur:weight? Figure 4: Structure of "static-routes" subtree. 5.4.2. Defining New Routing Protocols @@ -801,21 +789,21 @@ 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). 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 the protocol-specific data be encapsulated in + 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 B. 5.5. Route Filter The core routing data model provides a skeleton for defining route filters that can be used to restrict the set of routes being exchanged between a routing protocol instance and a connected RIB, or @@ -841,23 +829,23 @@ will be developed separately. Each route filter is identified by a unique name. Its type MUST be specified by the "type" identity reference - this opens the space for multiple route filtering framework implementations. 5.6. RPC Operations The "ietf-routing" module defines two RPC operations: - o active-route: query the routing system for the active route(s) - that are currently used for sending datagrams to a destination - host whose address is passed as an input parameter. + o active-route: query the routing system for the active 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 depend on several configuration parameters that are defined in other YANG modules. 6.1. Module "ietf-interfaces" @@ -908,21 +896,21 @@ 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 YANG Module RFC Ed.: 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@2013-10-18.yang" + file "ietf-routing@2013-11-07.yang" module ietf-routing { namespace "urn:ietf:params:xml:ns:yang:ietf-routing"; prefix "rt"; import ietf-yang-types { prefix "yang"; } @@ -959,45 +947,48 @@ 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. "; - revision 2013-10-18 { + revision 2013-11-07 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for Routing Management"; } /* Features */ - feature advanced-router { + feature multiple-ribs { description - "This feature indicates that the device supports advanced - routing functions, namely: - - - user-defined RIBs, - - - multi-path routes. + "This feature indicates that the device supports multiple RIBS + per address family, and the framework for passing routes + between RIBs, or between routing protocols and RIBs. Devices that do not support this feature MUST provide exactly one system-controlled RIB per supported address family. These RIBs then appear as entries of the list /routing-state/ribs/rib. "; } + feature multipath-routes { + description + "This feature indicates that the device supports multipath + routes that have a list of nexthops."; + } + /* Identities */ identity address-family { description "Base identity from which identities describing address families are derived."; } identity ipv4 { base address-family; @@ -1127,20 +1120,35 @@ leaf address-family { type identityref { base address-family; } mandatory "true"; description "Address family."; } } + grouping state-entry-id { + description + "This grouping defines a unique identifier of entries in + several operational state lists."; + leaf id { + type uint64 { + range "1..max"; + } + description + "Unique numerical identifier of a list entry in operational + state."; + + } + } + grouping router-id { description "This grouping provides the definition of router ID."; leaf router-id { type yang:dotted-quad; description "Router ID - 32-bit number in the form of a dotted quad."; } } @@ -1246,31 +1255,26 @@ mandatory "true"; description "Options for expressing the nexthop in routes."; case special-nexthop { uses special-nexthop; } case simple-nexthop { uses outgoing-interface; } case nexthop-list { - if-feature advanced-router; + if-feature multipath-routes; list nexthop { - key "id"; + unique "id"; description "An entry of a nexthop list."; - leaf id { - type uint64; - description - "A numeric identifier of the entry, assigned by the - server."; - } + uses state-entry-id; uses outgoing-interface; uses nexthop-classifiers; } } } } grouping route-metadata { description "Route metadata."; @@ -1284,50 +1288,45 @@ originated."; } 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."; } } + /* Operational state data */ container routing-state { config "false"; description "Operational state of the routing subsystem."; list routing-instance { - key "id"; + key "name"; + unique "id"; description "Each list entry is a container for operational state data of a routing instance. An implementation MAY create one or more system-controlled instances, other user-controlled instances MAY be created by configuration. "; - leaf id { - type uint64; - description - "Unique numeric identifier of the routing instance."; - } leaf name { - type leafref { - path "/routing/routing-instance/name"; - } + type string; description - "The name of the routing instance assigned in the - corresponding configuration entry (if any). + "The name of the routing instance. "; } + uses state-entry-id; leaf type { type identityref { base routing-instance-type; } default "rt:standard-routing-instance"; description "The routing instance type, primarily intended for discriminating among different types of logical routers, route virtualization, master-slave arrangements etc., while keeping all routing instances in the same flat list. @@ -1401,21 +1400,21 @@ } leaf type { type identityref { base routing-protocol; } mandatory "true"; description "Type of the routing protocol."; } container connected-ribs { - if-feature advanced-router; + if-feature multiple-ribs; description "Container for connected RIBs. "; list connected-rib { key "rib-id"; description "List of RIBs to which the routing protocol instance is connected (at most one RIB per address family). "; leaf rib-id { @@ -1454,66 +1453,54 @@ } } } } } } container ribs { description "Container for RIBs."; list rib { - key "id"; + key "name"; + unique "id"; description "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 create the default RIB for each address family, and MAY create other RIBs. Additional RIBs MAY be created in the configuration. "; - leaf id { - type uint64; - description - "Unique numeric identifier of the RIB instance."; - } leaf name { - type leafref { - path "/routing/ribs/rib/name"; - } + type string; description - "The name of the RIB assigned in the corresponding - configuration entry (if any)."; + "The name of the RIB."; } + uses state-entry-id; uses address-family; container routes { description "Current contents of the RIB."; list route { - key "id"; + unique "id"; description "A RIB route entry. This data node MUST be augmented with information specific for routes of each address family."; - leaf id { - type uint64 { - range "1..max"; - } - description - "Unique numeric identifier of the route."; - } + uses state-entry-id; uses nexthop-content; uses route-metadata; } } container recipient-ribs { - if-feature advanced-router; + if-feature multiple-ribs; description "Container for recipient RIBs."; list recipient-rib { key "rib-id"; description "List of RIBs that receive routes from this RIB."; leaf rib-id { type rib-state-ref; description "The name of the recipient RIB."; @@ -1559,38 +1546,34 @@ } } /* Configuration Data */ container routing { description "Configuration parameters for the routing subsystem."; list routing-instance { key "name"; - unique "routing-instance-id"; description "Configuration of a routing instance. "; leaf name { type string; description - "The name of the configured routing instance."; - } - leaf routing-instance-id { - type uint64; - description - "Reference to a system-assigned numeric identifier of the - routing instance. + "The name of the routing instance. - This leaf is essential for creating new configuration - entries that refer to existing system-controlled routing - instances. + 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-type; } default "rt:standard-routing-instance"; description "The type of the routing instance."; } @@ -1608,21 +1591,21 @@ uses router-id { description "Configuration of the global router ID."; } leaf description { type string; description "Textual description of the routing instance."; } container default-ribs { - if-feature advanced-router; + 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()/" @@ -1696,21 +1679,21 @@ leaf type { type identityref { base routing-protocol; } mandatory "true"; description "Type of the routing protocol - an identity derived from the 'routing-protocol' base identity."; } container connected-ribs { - if-feature advanced-router; + if-feature multiple-ribs; description "Configuration of connected RIBs. "; list connected-rib { must "not(/routing/ribs/rib[name=current()/" + "preceding-sibling::connected-rib/" + "name and address-family=/routing/ribs/" + "rib[name=current()/name]/address-family])" { error-message "Duplicate address family for connected RIBs."; @@ -1767,52 +1750,51 @@ "; } } } } container ribs { description "Configured RIBs."; list rib { key "name"; - unique "id"; description "Each entry represents a configured 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. "; + leaf name { type string; description - "The name of the RIB."; - } - leaf id { - type uint64; - description - "System-assigned numeric identifier of the RIB instance. + "The name of the RIB. - This leaf is essential for creating new configuration - entries that refer to existing system-controlled RIBs. + 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; leaf description { type string; description "Textual description of the RIB."; } container recipient-ribs { - if-feature advanced-router; + if-feature multiple-ribs; description "Configuration of recipient RIBs."; list recipient-rib { must "name != ../../name" { error-message "Source and recipient RIBs are identical."; description "A RIB MUST NOT appear among its recipient RIBs."; } must "/routing/ribs/rib[name=current()/name]/" @@ -1949,21 +1930,21 @@ } 8. IPv4 Unicast Routing YANG Module RFC Ed.: 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@2013-10-18.yang" + file "ietf-ipv4-unicast-routing@2013-11-07.yang" module ietf-ipv4-unicast-routing { namespace "urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing"; prefix "v4ur"; import ietf-routing { prefix "rt"; } @@ -2001,21 +1982,21 @@ 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. "; - revision 2013-10-18 { + revision 2013-11-07 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for Routing Management"; } /* Identities */ identity ipv4-unicast { base rt:ipv4; @@ -2129,21 +2110,21 @@ } description "Name of the outgoing interface. Only interfaces configured for the parent routing instance can be given. "; } } case nexthop-list { - if-feature rt:advanced-router; + if-feature rt:multipath-routes; list nexthop { key "id"; description "An entry of a nexthop list."; leaf id { type uint32; description "Unique numeric identifier of the entry. This value is unrelated to system-assigned keys of @@ -2223,42 +2204,42 @@ "IPv4 address of the gateway."; } } augment "/rt:active-route/rt:output/rt:route/rt:nexthop-options/" + "rt:nexthop-list/rt:nexthop" { when "../rt:address-family='v4ur:ipv4-unicast'" { description "This augment is valid only for IPv4 unicast."; } - if-feature rt:advanced-router; + if-feature rt:multipath-routes; description "This leaf augments the 'nexthop-list' case in the reply to the 'rt:active-route' operation."; leaf address { type inet:ipv4-address; description "IPv4 address of the nexthop."; } } } 9. IPv6 Unicast Routing YANG Module RFC Ed.: 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@2013-10-18.yang" + file "ietf-ipv6-unicast-routing@2013-11-07.yang" module ietf-ipv6-unicast-routing { namespace "urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing"; prefix "v6ur"; import ietf-routing { prefix "rt"; } @@ -2304,21 +2285,21 @@ 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. "; - revision 2013-10-18 { + revision 2013-11-07 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for Routing Management"; } /* Identities */ identity ipv6-unicast { base rt:ipv6; @@ -2855,21 +2836,21 @@ } description "Name of the outgoing interface. Only interfaces configured for the parent routing instance can be given. "; } } case nexthop-list { - if-feature rt:advanced-router; + if-feature rt:multipath-routes; list nexthop { key "id"; description "An entry of a nexthop list."; leaf id { type uint32; description "Unique numeric identifier of the entry. This value is unrelated to system-assigned keys of @@ -2948,21 +2929,21 @@ "IPv6 address of the gateway."; } } augment "/rt:active-route/rt:output/rt:route/rt:nexthop-options/" + "rt:nexthop-list/rt:nexthop" { when "../rt:address-family='v6ur:ipv6-unicast'" { description "This augment is valid only for IPv6 unicast."; } - if-feature rt:advanced-router; + if-feature rt:multipath-routes; description "This leaf augments the 'nexthop-list' case in the reply to the 'rt:active-route' operation."; leaf address { type inet:ipv6-address; description "IPv6 address of the nexthop."; } } } @@ -3059,24 +3040,24 @@ 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 author wishes to thank Nitin Bahadur, Martin Bjorklund, - Joel Halpern, Wes Hardaker, Sriganesh Kini, Andrew McGregor, - Jan Medved, Xiang Li, Thomas Morin, Tom Petch, Bruno Rijsman, - Juergen Schoenwaelder, Phil Shafer, Dave Thaler and Yi Yang for their - helpful comments and suggestions. + Joel Halpern, Wes Hardaker, Sriganesh Kini, David Lamparter, + Andrew McGregor, Jan Medved, Xiang Li, Thomas Morin, Tom Petch, + Bruno Rijsman, Juergen Schoenwaelder, Phil Shafer, Dave Thaler and + Yi Yang for their helpful comments and suggestions. 13. References 13.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. @@ -3090,26 +3071,26 @@ September 2010. [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. Bierman, "NETCONF Configuration Protocol", RFC 6241, June 2011. [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6991, July 2013. [YANG-IF] Bjorklund, M., "A YANG Data Model for Interface - Management", draft-ietf-netmod-interfaces-cfg-12 (work in - progress), July 2013. + Management", draft-ietf-netmod-interfaces-cfg-13 (work in + progress), November 2013. [YANG-IP] Bjorklund, M., "A YANG Data Model for IP Management", - draft-ietf-netmod-ip-cfg-10 (work in progress), - August 2013. + draft-ietf-netmod-ip-cfg-11 (work in progress), + October 2013. 13.2. Informative References [RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG Data Model Documents", RFC 6087, January 2011. [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, June 2011. Appendix A. The Complete Data Trees @@ -3119,26 +3100,25 @@ 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 routing-instance-id? uint64 | +--rw type? identityref | +--rw enabled? boolean | +--rw router-id? yang:dotted-quad | +--rw description? string - | +--rw default-ribs {advanced-router}? + | +--rw default-ribs {multiple-ribs}? | | +--rw default-rib* [address-family] | | +--rw address-family identityref | | +--rw 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 @@ -3159,84 +3139,83 @@ | | +--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 routing-protocol* [name] | +--rw name string | +--rw description? string | +--rw enabled? boolean | +--rw type identityref - | +--rw connected-ribs {advanced-router}? + | +--rw connected-ribs {multiple-ribs}? | | +--rw connected-rib* [rib-name] | | +--rw rib-name rib-ref | | +--rw import-filter? route-filter-ref | | +--rw export-filter? route-filter-ref | +--rw static-routes | +--rw v4ur:ipv4 | | +--rw v4ur:route* [id] | | +--rw v4ur:id uint32 | | +--rw v4ur:description? string | | +--rw v4ur:destination-prefix inet:ipv4-prefix | | +--rw (nexthop-options) | | +--:(special-nexthop) | | | +--rw v4ur:special-nexthop? enumeration | | +--:(simple-nexthop) | | | +--rw v4ur:gateway? inet:ipv4-address | | | +--rw v4ur:outgoing-interface? leafref - | | +--:(nexthop-list) {rt:advanced-router}? + | | +--:(nexthop-list) {rt:multipath-routes}? | | +--rw v4ur:nexthop* [id] | | +--rw v4ur:id uint32 | | +--rw v4ur:address? inet:ipv4-address | | +--rw v4ur:outgoing-interface? leafref | | +--rw v4ur:priority? enumeration | | +--rw v4ur:weight? uint8 | +--rw v6ur:ipv6 | +--rw v6ur:route* [id] | +--rw v6ur:id uint32 | +--rw v6ur:description? string | +--rw v6ur:destination-prefix inet:ipv6-prefix | +--rw (nexthop-options) | +--:(special-nexthop) | | +--rw v6ur:special-nexthop? enumeration | +--:(simple-nexthop) | | +--rw v6ur:gateway? inet:ipv6-address | | +--rw v6ur:outgoing-interface? leafref - | +--:(nexthop-list) {rt:advanced-router}? + | +--:(nexthop-list) {rt:multipath-routes}? | +--rw v6ur:nexthop* [id] | +--rw v6ur:id uint32 | +--rw v6ur:address? inet:ipv6-address | +--rw v6ur:outgoing-interface? leafref | +--rw v6ur:priority? enumeration | +--rw v6ur:weight? uint8 +--rw ribs | +--rw rib* [name] | +--rw name string - | +--rw id? uint64 | +--rw address-family identityref | +--rw description? string - | +--rw recipient-ribs {advanced-router}? + | +--rw recipient-ribs {multiple-ribs}? | +--rw recipient-rib* [rib-name] | +--rw rib-name rib-ref | +--rw filter? route-filter-ref +--rw route-filters +--rw route-filter* [name] +--rw name string +--rw description? string +--rw type identityref A.2. Operational State Data +--ro routing-state - +--ro routing-instance* [id] - | +--ro id uint64 - | +--ro name? leafref + +--ro routing-instance* [name] + | +--ro name string + | +--ro id? uint64 | +--ro type? identityref | +--ro router-id? yang:dotted-quad | +--ro default-ribs | | +--ro default-rib* [address-family] | | +--ro address-family identityref | | +--ro rib-id rib-state-ref | +--ro interfaces | | +--ro interface* [name] | | +--ro name if:interface-state-ref | | +--ro v6ur:ipv6-router-advertisements @@ -3254,53 +3233,53 @@ | | +--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 routing-protocol* [name] | +--ro name string | +--ro type identityref - | +--ro connected-ribs {advanced-router}? + | +--ro connected-ribs {multiple-ribs}? | +--ro connected-rib* [rib-id] | +--ro rib-id rib-state-ref | +--ro import-filter? route-filter-state-ref | +--ro export-filter? route-filter-state-ref +--ro ribs - | +--ro rib* [id] - | +--ro id uint64 - | +--ro name? leafref + | +--ro rib* [name] + | +--ro name string + | +--ro id? uint64 | +--ro address-family identityref | +--ro routes - | | +--ro route* [id] - | | +--ro id uint64 + | | +--ro route* + | | +--ro id? uint64 | | +--ro (nexthop-options) | | | +--:(special-nexthop) | | | | +--ro special-nexthop? enumeration | | | +--:(simple-nexthop) | | | | +--ro outgoing-interface? leafref | | | | +--ro v4ur:gateway? inet:ipv4-address | | | | +--ro v6ur:gateway? inet:ipv6-address - | | | +--:(nexthop-list) {advanced-router}? - | | | +--ro nexthop* [id] - | | | +--ro id uint64 + | | | +--:(nexthop-list) {multipath-routes}? + | | | +--ro nexthop* + | | | +--ro id? uint64 | | | +--ro outgoing-interface? leafref | | | +--ro priority? enumeration | | | +--ro weight? uint8 | | | +--ro v4ur:address? inet:ipv4-address | | | +--ro v6ur:address? inet:ipv6-address | | +--ro source-protocol identityref | | +--ro last-updated? yang:date-and-time | | +--ro v4ur:destination-prefix? inet:ipv4-prefix | | +--ro v6ur:destination-prefix? inet:ipv6-prefix - | +--ro recipient-ribs {advanced-router}? + | +--ro recipient-ribs {multiple-ribs}? | +--ro recipient-rib* [rib-id] | +--ro rib-id rib-state-ref | +--ro filter? route-filter-state-ref +--ro route-filters +--ro route-filter* [name] +--ro name string +--ro type identityref Appendix B. Example: Adding a New Routing Protocol @@ -3541,21 +3520,20 @@ 2013-07-02T17:11:27+00:59 rtr0 - 1415926535 Router A eth1 true 2001:db8:0:2::/64 @@ -3586,21 +3564,20 @@ 2001:db8:0:1::2 - 1415926535 rtr0 192.0.2.1 v4ur:ipv4-unicast 897932384 v6ur:ipv6-unicast 751058209 @@ -3624,28 +3601,27 @@ st0 rt:static + ipv4-main 897932384 v4ur:ipv4-unicast 626433832 - - 192.0.2.1/24 - + 192.0.2.1/24 eth0 rt:direct 2013-07-02T17:11:27+01:00 795028841 198.51.100.0/24 eth1 @@ -3652,23 +3628,25 @@ rt:direct 2013-07-02T17:11:27+01:00 971693993 0.0.0.0/0 rt:static 192.0.2.2 2013-07-02T18:02:45+01:00 + + ipv6-main 751058209 v6ur:ipv6-unicast 749445923 2001:db8:0:1::/64 eth0 rt:direct @@ -3694,21 +3672,34 @@ Appendix D. Change Log RFC Editor: remove this section upon publication as an RFC. -D.1. Changes Between Versions -10 and -11 +D.1. 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. + +D.2. 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- @@ -3718,70 +3709,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. -D.2. Changes Between Versions -09 and -10 +D.3. Changes Between Versions -09 and -10 o Added subtree for operational 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". -D.3. Changes Between Versions -08 and -09 +D.4. 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. -D.4. Changes Between Versions -07 and -08 +D.5. Changes Between Versions -07 and -08 o Changed reference from RFC6021 to RFC6021bis. -D.5. Changes Between Versions -06 and -07 +D.6. Changes Between Versions -06 and -07 o The contents of in Appendix C 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. -D.6. Changes Between Versions -05 and -06 +D.7. 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". @@ -3789,21 +3780,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. -D.7. Changes Between Versions -04 and -05 +D.8. 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 @@ -3824,35 +3815,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. -D.8. Changes Between Versions -03 and -04 +D.9. Changes Between Versions -03 and -04 o Changed "error-tag" for both RPC methods 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". -D.9. Changes Between Versions -02 and -03 +D.10. 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". @@ -3870,21 +3861,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". -D.10. Changes Between Versions -01 and -02 +D.11. Changes Between Versions -01 and -02 o Added module "ietf-ipv6-unicast-routing". o The example in Appendix C 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. @@ -3894,21 +3885,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. -D.11. Changes Between Versions -00 and -01 +D.12. 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.