--- 1/draft-ietf-netmod-routing-cfg-15.txt 2014-10-26 09:14:54.913280838 -0700 +++ 2/draft-ietf-netmod-routing-cfg-16.txt 2014-10-26 09:14:55.061284514 -0700 @@ -1,145 +1,145 @@ -NETMOD L. Lhotka +NETMOD Working Group L. Lhotka Internet-Draft CZ.NIC -Intended status: Standards Track May 25, 2014 -Expires: November 26, 2014 +Intended status: Standards Track October 26, 2014 +Expires: April 29, 2015 A YANG Data Model for Routing Management - draft-ietf-netmod-routing-cfg-15 + draft-ietf-netmod-routing-cfg-16 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, - routing information bases (RIB), routing protocols and route filters. + 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), routing protocols and route filters. -Status of this Memo +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 November 26, 2014. + This Internet-Draft will expire on April 29, 2015. Copyright Notice Copyright (c) 2014 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 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. 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. 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 Management YANG Module . . . . . . . . . . . . . . . . 25 - 8. IPv4 Unicast Routing Management YANG Module . . . . . . . . . 47 - 9. IPv6 Unicast Routing Management 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. Minimum Implementation . . . . . . . . . . . . . . . 78 - Appendix C. Example: Adding a New Routing Protocol . . . . . . . 79 - Appendix D. Example: NETCONF Reply . . . . . . . . . . . . 82 - Appendix E. Change Log . . . . . . . . . . . . . . . . . . . . . 89 - E.1. Changes Between Versions -14 and -15 . . . . . . . . . . . 89 - E.2. Changes Between Versions -13 and -14 . . . . . . . . . . . 89 - E.3. Changes Between Versions -12 and -13 . . . . . . . . . . . 89 - E.4. Changes Between Versions -11 and -12 . . . . . . . . . . . 90 - E.5. Changes Between Versions -10 and -11 . . . . . . . . . . . 90 - E.6. Changes Between Versions -09 and -10 . . . . . . . . . . . 90 - E.7. Changes Between Versions -08 and -09 . . . . . . . . . . . 91 - E.8. Changes Between Versions -07 and -08 . . . . . . . . . . . 91 - E.9. Changes Between Versions -06 and -07 . . . . . . . . . . . 91 - E.10. Changes Between Versions -05 and -06 . . . . . . . . . . . 91 - E.11. Changes Between Versions -04 and -05 . . . . . . . . . . . 92 - E.12. Changes Between Versions -03 and -04 . . . . . . . . . . . 93 - E.13. Changes Between Versions -02 and -03 . . . . . . . . . . . 93 - E.14. Changes Between Versions -01 and -02 . . . . . . . . . . . 94 - E.15. Changes Between Versions -00 and -01 . . . . . . . . . . . 94 - Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 95 + 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 . . . 10 + 4.2. Features of Advanced Routers . . . . . . . . . . . . . . 10 + 5. Basic Building Blocks . . . . . . . . . . . . . . . . . . . . 11 + 5.1. Routing Instance . . . . . . . . . . . . . . . . . . . . 11 + 5.1.1. Parameters of IPv6 Routing Instance Interfaces . . . 12 + 5.2. Route . . . . . . . . . . . . . . . . . . . . . . . . . . 13 + 5.3. Routing Information Base (RIB) . . . . . . . . . . . . . 14 + 5.3.1. Multiple RIBs per Address Family . . . . . . . . . . 15 + 5.4. Routing Protocol . . . . . . . . . . . . . . . . . . . . 15 + 5.4.1. Routing Pseudo-Protocols . . . . . . . . . . . . . . 16 + 5.4.2. Defining New Routing Protocols . . . . . . . . . . . 18 + 5.5. Route Filter . . . . . . . . . . . . . . . . . . . . . . 19 + 5.6. RPC Operations . . . . . . . . . . . . . . . . . . . . . 20 + 6. Interactions with Other YANG Modules . . . . . . . . . . . . 20 + 6.1. Module "ietf-interfaces" . . . . . . . . . . . . . . . . 20 + 6.2. Module "ietf-ip" . . . . . . . . . . . . . . . . . . . . 20 + 7. Routing Management YANG Module . . . . . . . . . . . . . . . 21 + 8. IPv4 Unicast Routing Management YANG Module . . . . . . . . . 44 + 9. IPv6 Unicast Routing Management YANG Module . . . . . . . . . 49 + 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 63 + 11. Security Considerations . . . . . . . . . . . . . . . . . . . 64 + 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 65 + 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 65 + 13.1. Normative References . . . . . . . . . . . . . . . . . . 65 + 13.2. Informative References . . . . . . . . . . . . . . . . . 66 + Appendix A. The Complete Data Trees . . . . . . . . . . . . . . 66 + A.1. Configuration Data . . . . . . . . . . . . . . . . . . . 66 + A.2. State Data . . . . . . . . . . . . . . . . . . . . . . . 69 + Appendix B. Minimum Implementation . . . . . . . . . . . . . . . 71 + Appendix C. Example: Adding a New Routing Protocol . . . . . . . 72 + Appendix D. Example: NETCONF Reply . . . . . . . . . . . . 74 + Appendix E. Change Log . . . . . . . . . . . . . . . . . . . . . 81 + E.1. Changes Between Versions -15 and -16 . . . . . . . . . . 81 + E.2. Changes Between Versions -14 and -15 . . . . . . . . . . 82 + E.3. Changes Between Versions -13 and -14 . . . . . . . . . . 82 + E.4. Changes Between Versions -12 and -13 . . . . . . . . . . 82 + E.5. Changes Between Versions -11 and -12 . . . . . . . . . . 83 + E.6. Changes Between Versions -10 and -11 . . . . . . . . . . 83 + E.7. Changes Between Versions -09 and -10 . . . . . . . . . . 84 + E.8. Changes Between Versions -08 and -09 . . . . . . . . . . 84 + E.9. Changes Between Versions -07 and -08 . . . . . . . . . . 84 + E.10. Changes Between Versions -06 and -07 . . . . . . . . . . 84 + E.11. Changes Between Versions -05 and -06 . . . . . . . . . . 85 + E.12. Changes Between Versions -04 and -05 . . . . . . . . . . 85 + E.13. Changes Between Versions -03 and -04 . . . . . . . . . . 86 + E.14. Changes Between Versions -02 and -03 . . . . . . . . . . 86 + E.15. Changes Between Versions -01 and -02 . . . . . . . . . . 87 + E.16. Changes Between Versions -00 and -01 . . . . . . . . . . 87 + Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 88 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. o Module "ietf-ipv6-unicast-routing" augments the "ietf-routing" module with additional data specific to IPv6 unicast, including the router configuration variables required by [RFC4861]. These modules together define the so-called core routing data model, - which is proposed as a basis for the development of data models for - configuration and management of more sophisticated routing systems. - While these three modules can be directly used for simple IP devices - with static routing (see Appendix B), their main purpose is to - provide essential building blocks for more complicated setups - involving multiple routing protocols, multicast routing, additional - address families, and advanced functions such as route filtering or - policy routing. To this end, it is expected that the core routing - data model will be augmented by numerous modules developed by other - IETF working groups. + which is intended as a basis for future data model development + covering more sophisticated routing systems. While these three + modules can be directly used for simple IP devices with static + routing (see Appendix B), their main purpose is to provide essential + building blocks for more complicated data models involving multiple + routing protocols, multicast routing, additional address families, + and advanced functions such as route filtering or policy routing. To + this end, it is expected that the core routing data model will be + augmented by numerous modules developed by other IETF working groups. 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 @@ -180,36 +180,35 @@ 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 routes together with other information. See Section 5.3 for details. - system-controlled entry: An entry of a list in operational state - data ("config false") that is created by the system independently - of what has been explicitly configured. See Section 4.1 for - details. + system-controlled entry: An entry of a list in state data ("config + false") that is created by the system independently of what has + been explicitly configured. See Section 4.1 for details. - user-controlled entry: An entry of a list in operational state data - ("config false") that is created and deleted as a direct - consequence of certain configuration changes. See Section 4.1 for - details. + user-controlled entry: An entry of a list in state data ("config + false") that is created and deleted as a direct consequence of + certain configuration changes. See Section 4.1 for details. 2.2. Tree Diagrams A simplified graphical representation of the complete data tree is presented in Appendix A, and similar diagrams of its various subtrees - appear in the main text. The meaning of the symbols in these - diagrams is as follows: + appear in the main text. + + The meaning of the symbols in these diagrams is as follows: o Brackets "[" and "]" enclose list keys. o Curly braces "{" and "}" contain names of optional features that make the corresponding node conditional. o Abbreviations before data node names: "rw" means configuration (read-write), and "ro" state data (read-only). o Symbols after data node names: "?" means an optional node and "*" @@ -226,93 +225,88 @@ In this document, names of data nodes, RPC methods and other data model objects are often used without a prefix, as long as it is clear from the context in which YANG module each name is defined. Otherwise, names are prefixed using the standard prefix associated with the corresponding YANG module, as shown in Table 1. +--------+---------------------------+-----------+ | Prefix | YANG module | Reference | +--------+---------------------------+-----------+ | if | ietf-interfaces | [RFC7223] | - | | | | - | ip | ietf-ip | [YANG-IP] | - | | | | + | ip | ietf-ip | [RFC7277] | | rt | ietf-routing | Section 7 | - | | | | | v4ur | ietf-ipv4-unicast-routing | Section 8 | - | | | | | v6ur | ietf-ipv6-unicast-routing | Section 9 | - | | | | | yang | ietf-yang-types | [RFC6991] | - | | | | | inet | ietf-inet-types | [RFC6991] | +--------+---------------------------+-----------+ Table 1: Prefixes and corresponding YANG modules 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 setups, such as static routing, should be + 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 On the other hand, the core routing framework must allow for - complicated setups involving multiple routing information bases + complicated set-ups 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 The core routing data model consists of three YANG modules. The first module, "ietf-routing", defines the generic components of a routing system. The other two modules, "ietf-ipv4-unicast-routing" and "ietf-ipv6-unicast-routing", augment the "ietf-routing" module with additional data nodes that are needed for IPv4 and IPv6 unicast routing, respectively. Figures 1 and 2 show abridged views of the - configuration and operational state data hierarchies. See Appendix A - for the complete data trees. + 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 routing-protocol* [name] + | +--rw routing-protocol* [type name] + | +--rw type | +--rw name | +--rw description? | +--rw enabled? - | +--rw type + | +--rw route-preference? | +--rw connected-ribs | | ... | +--rw static-routes | ... +--rw ribs | +--rw rib* [name] | +--rw name | +--rw address-family | +--rw description? | +--rw recipient-ribs @@ -324,53 +318,62 @@ +--rw description? +--rw type Figure 1: Configuration data hierarchy. +--ro routing-state +--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-name | +--ro interfaces | | +--ro interface* [name] | | +--ro name | | +--ro v6ur:ipv6-router-advertisements | | ... | +--ro routing-protocols - | +--ro routing-protocol* [name] - | +--ro name + | +--ro routing-protocol* [type name] | +--ro type + | +--ro name + | +--ro route-preference | +--ro connected-ribs | ... + +--ro next-hop-lists + | +--ro next-hop-list* [id] + | +--ro id + | +--ro address-family + | +--ro next-hop* + | +--ro (next-hop-options) + | | ... + | +--ro priority? + | +--ro weight? +--ro ribs | +--ro rib* [name] | +--ro name | +--ro id | +--ro address-family | +--ro routes - | | +--ro route* [id] + | | +--ro route* | | ... | +--ro recipient-ribs | +--ro recipient-rib* [rib-name] | ... +--ro route-filters +--ro route-filter* [name] +--ro name +--ro type - Figure 2: Operational state data hierarchy. + 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, routing protocols and route filters. 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. @@ -388,21 +391,21 @@ +---+ +---+ +---+ +---+ | F | | F | | F | | F | +---+ +---+ +---+ +---+ ^ | ^ | | v | v +----------+ +----------+ | routing | | routing | | protocol | | protocol | +----------+ +----------+ - Figure 3: Example setup of a routing system + 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 exactly one RIB with @@ -416,126 +419,119 @@ 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 "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 - "routing-state" container. + system-controlled entry in state data, i.e., inside the "routing- + state" container. - Additional entries may be created in the configuration by the user - via the NETCONF protocol. These are so-called user-controlled + Additional entries may be created in the configuration by the user, + 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 operational state version of the - list. + then this entry also appears in the state data version of the list. - Corresponding entries in both versions of the list (in operational - state data and configuration) have the same value of the list key. + 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 - 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. + with the corresponding entry in the state data list, the key of the + configuration entry has to be set to the same value as the key of the + state entry. - An example can be seen in Appendix D: the "/routing-state/ - routing-instance" list has a single system-controlled entry whose - "name" key has the value "rtr0". This entry is configured by the - "/routing/routing-instance" entry whose "name" key is also "rtr0". + An example can be seen in Appendix D: the "/routing-state/routing- + instance" list has a single system-controlled entry whose "name" key + has the value "rtr0". This entry is configured by the "/routing/ + routing-instance" entry whose "name" key is also "rtr0". 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 + in the removal of the corresponding entry in the state data list. In + contrast, if a system-controlled entry is deleted from the configuration list, only the extra configuration specified in that - entry is removed but the corresponding operational state entry - remains in the list. + entry is removed but the corresponding state data entry remains in + the list. 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 would represent unnecessary complications for the implementation. - Therefore, the core routing data model makes the advanced - functionality optional by means of two YANG features: + Therefore, the core routing data model makes the configuration of + some advanced functions optional to implement by means of two YANG + features: - o "multiple-ribs" - indicates that the device supports multiple RIBs - per address family, routing protocols connected to non-default + o "multiple-ribs" - indicates that the device supports configuration + of user-defined RIBs, routing protocols connected to non-default RIBs, and RIBs configured as receivers of routes from other RIBs. - o "multipath-routes" - indicates that the device supports routes - with multiple next-hops. + o "multipath-routes" - indicates that the device supports + configuration of routes with multiple next-hops. 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 - Each routing instance in the core routing data model represents a - logical router. The exact semantics of this term are left to - implementations. For example, routing instances may be completely - isolated virtual routers or, alternatively, they may internally share - certain information. - - A routing instance together with its operational state is represented - as an entry of the list "/routing-state/routing-instance", and - identified by a unique name. Configuration of that router instance - appears as an entry of the list "/routing/routing-instance". + The core routing data model supports one or more routing instances + appearing as entries of the "routing-instance" list. Each routing + instance has separate configuration and state data under + "/rt:routing/rt:routing-instance" and "/rt:routing-state/rt:routing- + instance", respectively. - An implementation MAY support multiple types of logical routers - simultaneously. Instances of all routing instance types are - organized as entries of the same flat "routing-instance" list. In - order to discriminate routing instances belonging to different types, - the "type" leaf is defined as a child of the "routing-instance" node. + 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 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 pose restrictions on allowed routing instance - types and on the 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:standard-routing- - instance" and may not allow creation of any user-controlled - instances. + 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" module [RFC7223]. - In YANG terms, the list of routing instance interfaces is modeled as - 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. + 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 operational state - data, with definitions of the following variables as required by - [RFC4861], sec. 6.2.1: + data node "rt:interface", in both configuration and state data, 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, @@ -562,81 +558,111 @@ * 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 [YANG-IP] (leaf "ip: - forwarding"). + 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 problematic because the values might be reset again to the (higher) configured values after a configuration is reloaded. Moreover, no implementation is known to use the decrementing behavior. The "ietf-ipv6-unicast-routing" module therefore assumes the former behavior with constant values. 5.2. Route 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 + 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 a - special action such as discarding the packet. + 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. - 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. + o "next-hop": determines the action to be performed with a packet. + See below for details. - 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. + 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. + + o next-hop list reference - each next-hop list is a set of next-hops + that may also contain a reference to another next-hop list. + + o RIB reference - a new look-up is to be performed in the specified + RIB. + + It is expected that future modules defining routing protocols will + add other route attributes such as metrics or preferences. + + Routes are primarily state data that appear as entries of RIBs + (Section 5.3) but they may be also 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 "preferred": 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. 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. + 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, an implementation MAY specify rules and - restrictions for sharing RIBs among routing instances. + 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. 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. 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). @@ -657,28 +683,36 @@ 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). - 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). + Multiple routing protocol instances of the same type are permitted. + + 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. In addition, two independent route filters (see Section 5.5) may be configured for each connected RIB to apply user-defined policies @@ -691,25 +725,25 @@ o export filter controls which routes the routing protocol instance receives from the connected RIB. Note that the terms import and export are used from the viewpoint of a RIB. 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 that they are confined to the local device and do not - exchange any routing information with neighboring routers. Routes - from both "direct" and "static" protocol instances are passed to the - connected RIB (subject to route filters, if any), but an exchange in - the opposite direction is not allowed. + 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 (subject to route filters, if any), but an exchange in the + opposite direction is not allowed. 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. Direct routes MAY be filtered before they appear in the default RIB. @@ -717,80 +751,103 @@ 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. Static routes are configured within the "static-routes" container, see Figure 4. +--rw static-routes +--rw v4ur:ipv4 - | +--rw v4ur:route* [id] - | +--rw v4ur:id - | +--rw v4ur:description? + | +--rw v4ur:route* [destination-prefix] | +--rw v4ur:destination-prefix + | +--rw v4ur:description? + | +--rw v4ur:next-hop + | +--rw (simple-or-list)? + | +--:(multipath-entry) + | | +--rw v4ur:multipath-entry* [name] + | | +--rw v4ur:name + | | +--rw (next-hop-options) + | | | +--:(simple-next-hop) + | | | | +--rw v4ur:outgoing-interface? + | | | +--:(special-next-hop) + | | | | +--rw v4ur:special-next-hop? + | | | +--:(next-hop-address) + | | | +--rw v4ur:next-hop-address? + | | +--rw v4ur:priority? + | | +--rw v4ur:weight? + | +--:(simple-next-hop) | +--rw (next-hop-options) - | +--:(special-next-hop) - | | +--rw v4ur:special-next-hop? | +--:(simple-next-hop) - | | +--rw v4ur:next-hop? | | +--rw v4ur:outgoing-interface? - | +--:(next-hop-list) {rt:multipath-routes}? - | +--rw v4ur:next-hop-list - | +--rw v4ur:next-hop* [id] - | +--rw v4ur:id - | +--rw v4ur:address? - | +--rw v4ur:outgoing-interface? - | +--rw v4ur:priority? - | +--rw v4ur:weight? + | +--:(special-next-hop) + | | +--rw v4ur:special-next-hop? + | +--:(next-hop-address) + | +--rw v4ur:next-hop-address? +--rw v6ur:ipv6 - +--rw v6ur:route* [id] - +--rw v6ur:id - +--rw v6ur:description? + +--rw v6ur:route* [destination-prefix] +--rw v6ur:destination-prefix + +--rw v6ur:description? + +--rw v6ur:next-hop + +--rw (simple-or-list)? + +--:(multipath-entry) + | +--rw v6ur:multipath-entry* [name] + | +--rw v6ur:name + | +--rw (next-hop-options) + | | +--:(simple-next-hop) + | | | +--rw v6ur:outgoing-interface? + | | +--:(special-next-hop) + | | | +--rw v6ur:special-next-hop? + | | +--:(next-hop-address) + | | +--rw v6ur:next-hop-address? + | +--rw v6ur:priority? + | +--rw v6ur:weight? + +--:(simple-next-hop) +--rw (next-hop-options) - +--:(special-next-hop) - | +--rw v6ur:special-next-hop? +--:(simple-next-hop) - | +--rw v6ur:next-hop? | +--rw v6ur:outgoing-interface? - +--:(next-hop-list) {rt:multipath-routes}? - +--rw v6ur:next-hop-list - +--rw v6ur:next-hop* [id] - +--rw v6ur:id - +--rw v6ur:address? - +--rw v6ur:outgoing-interface? - +--rw v6ur:priority? - +--rw v6ur:weight? + +--:(special-next-hop) + | +--rw v6ur:special-next-hop? + +--:(next-hop-address) + +--rw v6ur:next-hop-address? Figure 4: Structure of "static-routes" subtree. + A next-hop in static routes may be configured as a simple next-hop + (IP address, outgoing interface or both), special next-hop or a list + of multi-path next-hop entries that is used either for backup routes + of for equal-cost multi-path (ECMP) routing. The last option is + available only on devices that advertise the feature "rt:multipath- + routes". Moreover, unlike next-hop lists in state data, a list of + next-hop entries in a static route cannot be recursive, i.e., each + entry of that list can only be a simple or special next-hop. + 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 the protocol-specific configuration and state data, and it has to fit it into the core routing framework in the following way: o A new identity MUST be defined for the routing protocol and its base identity MUST be set to "rt:routing-protocol", or to an identity derived from "rt:routing-protocol". o Additional route attributes MAY be defined, preferably in one place by means of defining a YANG grouping. The new attributes have to be inserted by augmenting the definitions of the nodes /rt:routing-state/rt:ribs/rt:rib/rt:routes/rt:route and - /rt:active-route/rt:output/rt:route, + /rt:fib-route/rt:output/rt:route, and possibly other places in the configuration, state data 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 @@ -808,71 +865,71 @@ 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 between a source and a recipient RIB. Route filters may also manipulate routes, i.e., add, delete, or modify their attributes. Route filters are global, which means that a configured route filter - may be used by any or all routing instances. However, an - implementation MAY specify rules and restrictions for sharing route - filters among routing instances. + may be used by any or all routing instances. However, a data model + for a routing instance type MAY specify rules and restrictions for + sharing route filters among routing instances of that type. - By itself, the route filtering framework defined in this document - allows for applying only two extreme routing policies which are - represented by the following pre-defined route filter types: + The core routing data model defines only two extreme route filtering + policies which are represented by the following pre-defined route + filter types: o "deny-all-route-filter": all routes are blocked, o "allow-all-route-filter": all routes are permitted. The latter type is equivalent to no route filter. It is expected that more comprehensive route filtering frameworks 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. + Each route filter entry is identified by a unique name. Its type + MUST be specified by the "type" identity reference. 5.6. RPC Operations The "ietf-routing" module defines two RPC operations: - o active-route: query a routing instance for the active route that - is currently used for sending datagrams to a destination host - whose address is passed as an input parameter. + 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 depend on several + 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]: /if:interfaces/if:interface/if:enabled If this switch is set to "false" for a network layer interface, the device MUST behave exactly as if that interface was not assigned to any routing instance at all. 6.2. Module "ietf-ip" The following boolean switches are defined in the "ietf-ip" YANG - module [YANG-IP]: + module [RFC7277]: /if:interfaces/if:interface/ip:ipv4/ip:enabled If this switch is set to "false" for a network layer interface, then all IPv4 routing functions related to that interface MUST be disabled. /if:interfaces/if:interface/ip:ipv4/ip:forwarding If this switch is set to "false" for a network layer interface, @@ -896,25 +952,25 @@ In addition, the "ietf-ip" module allows for configuring IPv4 and IPv6 addresses and network prefixes or masks on network layer interfaces. Configuration of these parameters on an enabled interface MUST result in an immediate creation of the corresponding direct route. The destination prefix of this route is set according to the configured IP address and network prefix/mask, and the interface is set as the outgoing interface for that route. 7. Routing Management 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). + 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@2014-05-24.yang" + file "routing@2014-10-26.yang" module ietf-routing { namespace "urn:ietf:params:xml:ns:yang:ietf-routing"; prefix "rt"; import ietf-yang-types { prefix "yang"; } @@ -949,47 +1004,57 @@ 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."; - revision 2014-05-24 { + revision 2014-10-26 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for Routing Management"; } /* Features */ feature multiple-ribs { description - "This feature indicates that the device supports multiple RIBS - per address family, and the framework for passing routes - between RIBs. + "This feature indicates that the server supports user-defined + RIBS and the framework for passing routes between 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."; + Servers that do not advertize 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."; } feature multipath-routes { description - "This feature indicates that the device supports multipath + "This feature indicates that the server supports multipath routes that have a list of next-hops."; } + 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 advertize this feature set a router ID + algorithmically, usually to one of configured IPv4 addresses. + However, this algorithm is implementation-specific."; + } + /* Identities */ identity address-family { description "Base identity from which identities describing address families are derived."; } identity ipv4 { base address-family; @@ -989,41 +1054,40 @@ description "Base identity from which identities describing address families are derived."; } identity ipv4 { base address-family; description "This identity represents IPv4 address family."; } + identity ipv6 { base address-family; description "This identity represents IPv6 address family."; } - identity routing-instance-type { + identity routing-instance { description "Base identity from which identities describing routing - instance types are derived. - - It is primarily intended for discriminating among different - types of logical routers or router virtualization."; + instance types are derived."; } - identity standard-routing-instance { - base routing-instance-type; + identity default-routing-instance { + base routing-instance; description - "This identity represents a default routing instance."; + "This identity represents either a default routing instance, or + the only routing instance on systems that do not support + multiple instances."; } - identity routing-protocol { description "Base identity from which routing protocol identities are derived."; } identity direct { base routing-protocol; description "Routing pseudo-protocol which provides routes to directly @@ -1084,58 +1148,74 @@ 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 next-hop-list-ref { + type leafref { + path "/rt:routing-state/rt:next-hop-lists/rt:next-hop-list/" + + "rt:id"; + } + description + "This type is used for leafs that reference a next-hop list (in + state data)."; + } + typedef route-filter-ref { type leafref { path "/rt:routing/rt:route-filters/rt:route-filter/rt:name"; } description "This type is used for leafs that reference a route filter configuration."; } typedef route-filter-state-ref { type leafref { path "/rt:routing-state/rt:route-filters/rt:route-filter/" + "rt:name"; } description - "This type is used for leafs that reference a route filter in - state data."; + "This type is used for leafs that reference state data of a + route filter."; + } + + typedef route-preference { + type uint32; + description + "This type is used for route preferences."; } /* Groupings */ grouping address-family { description "This grouping provides a leaf identifying an address family."; leaf address-family { type identityref { base address-family; } mandatory "true"; description "Address family."; } } grouping state-entry-id { description - "This grouping defines a unique identifier for entries in + "This grouping provides a unique identifier for entries in several operational state lists."; leaf id { type uint64; description "Unique numerical identifier of a list entry in operational state. It may be used by protocols or tools that inspect and/or manipulate operational state data and prefer fixed-size integers as list entry handles. These identifiers are always ephemeral, i.e., they may @@ -1133,80 +1213,33 @@ leaf id { type uint64; description "Unique numerical identifier of a list entry in operational state. It may be used by protocols or tools that inspect and/or manipulate operational state data and prefer fixed-size integers as list entry handles. These identifiers are always ephemeral, i.e., they may change after a reboot."; - } } grouping router-id { description - "This grouping provides the definition of router ID."; + "This grouping provides router ID."; leaf router-id { type yang:dotted-quad; description - "Router ID - 32-bit number in the form of a dotted quad. Some - protocols use this parameter for identifying a router to its - neighbors."; - } - } - - grouping outgoing-interface { - description - "This grouping defines the outgoing interface for use in - next-hops."; - leaf outgoing-interface { - type leafref { - path "/rt:routing-state/rt:routing-instance/rt:interfaces/" - + "rt:interface/rt:name"; - } - description - "Name of the outgoing interface."; - } - } - - grouping special-next-hop { - description - "This grouping provides the leaf for specifying special - next-hop options."; - leaf special-next-hop { - type enumeration { - enum blackhole { - description - "Silently discard the packet."; - } - enum unreachable { - description - "Discard the packet and notify the sender with an error - message indicating that the destination host is - unreachable."; - } - enum prohibit { - description - "Discard the packet and notify the sender with an error - message indicating that the communication is - administratively prohibited."; - } - enum receive { - description - "The packet will be received by the local network - device."; - } - } - description - "Special next-hop options."; + "A 32-bit number in the form of a dotted quad that is used by + some routing protocols identifying a router."; + reference + "RFC 2328: OSPF Version 2."; } } grouping next-hop-classifiers { description "This grouping provides two next-hop classifiers."; leaf priority { type enumeration { enum primary { value "1"; @@ -1240,81 +1273,159 @@ balancing. The number specifies the relative fraction of the traffic that will use the corresponding next-hop. A value of 0 represents equal load-balancing. If both primary and backup next-hops are present, then the weights for each priority level are used separately."; } } + grouping special-next-hop { + description + "This grouping provides a leaf with enumeration of special + next-hops."; + leaf special-next-hop { + type enumeration { + enum blackhole { + description + "Silently discard the packet."; + } + enum unreachable { + description + "Discard the packet and notify the sender with an error + message indicating that the destination host is + unreachable."; + } + enum prohibit { + description + "Discard the packet and notify the sender with an error + message indicating that the communication is + administratively prohibited."; + } + enum receive { + description + "The packet will be received by the local system."; + } + } + description + "Special next-hop options."; + } + } + grouping next-hop-content { description - "Generic parameters of next-hops in routes."; + "Generic parameters of next-hops in static routes."; choice next-hop-options { mandatory "true"; description - "Options for expressing the next-hop in routes."; + "Options for next-hops in static routes."; + 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"; + } + description + "Name of the outgoing interface."; + } + } case special-next-hop { uses special-next-hop; } - case simple-next-hop { - uses outgoing-interface; } - case next-hop-list { - if-feature multipath-routes; - container next-hop-list { + } + + grouping next-hop-state-content { description - "Container for multiple next-hops."; - list next-hop { - key "id"; + "Generic parameters of next-hops in state data."; + choice next-hop-options { + mandatory "true"; description - "An entry of a next-hop list."; - uses state-entry-id; - uses outgoing-interface; - uses next-hop-classifiers; + "Options for next-hops in state data."; + leaf next-hop-list { + type next-hop-list-ref; + description + "Reference to a next-hop list."; } + leaf use-rib { + type rib-state-ref; + description + "Reference to a RIB in which a new look-up is to be + performed."; } + 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"; + } + description + "Name of the outgoing interface."; + } + } + case special-next-hop { + uses special-next-hop; } } } grouping route-metadata { description "Route metadata."; leaf source-protocol { type identityref { base routing-protocol; } mandatory "true"; description "Type of the routing protocol from which the route originated."; } + leaf active { + type empty; + description + "Presence of this leaf indicates that the route is preferred + among all routes in the same RIB that have the same + destination prefix."; + } leaf last-updated { type yang:date-and-time; description "Time stamp of the last modification of the route. If the route was never modified, it is the time when the route was inserted into the RIB."; } } /* Operational state data */ container routing-state { config "false"; description "Operational state of the routing subsystem."; list routing-instance { key "name"; unique "id"; + min-elements "1"; 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 name { type string; description @@ -1323,38 +1434,24 @@ For system-controlled instances the name is persistent, i.e., it SHOULD NOT change across reboots."; } uses state-entry-id { refine "id" { mandatory "true"; } } leaf type { type identityref { - base routing-instance-type; - } - 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."; + base routing-instance; } - uses router-id { description - "Global router ID. - - An implementation may choose a value if none is - configured. - - Routing protocols that use router ID MAY override this - global parameter."; + "The routing instance type."; } container default-ribs { description "Default RIBs used by the routing instance."; list default-rib { key "address-family"; description "Each list entry specifies the default RIB for one address family. @@ -1388,53 +1485,67 @@ description "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 "name"; + key "type name"; description "Operational state of a routing protocol instance. An implementation MUST provide exactly one system-controlled instance of the type 'direct'. Other instances MAY be created by configuration."; + leaf type { + type identityref { + base routing-protocol; + } + description + "Type of the routing protocol."; + } leaf name { type string; description "The name of the routing protocol instance. For system-controlled instances this name is persistent, i.e., it SHOULD NOT change across reboots."; } - leaf type { - type identityref { - base routing-protocol; - } + leaf route-preference { + type route-preference; mandatory "true"; description - "Type of the routing protocol."; + "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 (at most one RIB per address - family)."; + 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."; } leaf import-filter { type route-filter-state-ref; description "Reference to a route filter that is used for filtering routes passed from this routing protocol @@ -1458,20 +1569,37 @@ routes are accepted. The 'direct' and 'static' pseudo-protocols accept no routes from any RIB."; } } } } } } + container next-hop-lists { + description + "Container for next-hop lists."; + list next-hop-list { + key "id"; + description + "Next-hop list."; + uses state-entry-id; + uses address-family; + list next-hop { + description + "Entry in a next-hop list."; + uses next-hop-state-content; + uses next-hop-classifiers; + } + } + } container ribs { description "Container for RIBs."; list rib { 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. @@ -1486,34 +1614,43 @@ "The name of the RIB."; } uses state-entry-id { refine "id" { mandatory "true"; } } uses address-family; container routes { description - "Current contents of the RIB."; + "Current content of the RIB."; list route { - key "id"; description "A RIB route entry. This data node MUST be augmented with information specific for routes of each address family."; - uses state-entry-id; - uses next-hop-content; + leaf route-preference { + type route-preference; + description + "This route attribute, also known as administrative + distance, allows for selecting the preferred route + among routes with the same destination prefix. A + smaller value means a more preferred route."; + } + container next-hop { + description + "Route's next-hop attribute."; + uses next-hop-state-content; + } uses route-metadata; } } container recipient-ribs { - if-feature multiple-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."; @@ -1575,39 +1711,42 @@ 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; + base routing-instance; } - default "rt:standard-routing-instance"; + default "rt:default-routing-instance"; description "The type of the routing instance."; } leaf enabled { type boolean; default "true"; description "Enable/disable the routing instance. If this parameter is false, the parent routing instance is disabled and does not appear in operational state data, despite any other configuration that might be present."; } uses router-id { + if-feature router-id; description - "Configuration of the global router ID."; + "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 @@ -1651,24 +1790,33 @@ description "A reference to the name of a configured network layer interface."; } } } container routing-protocols { description "Configuration of routing protocol instances."; list routing-protocol { - key "name"; + key "type name"; description "Each entry contains configuration of a routing protocol instance."; + + leaf type { + type identityref { + base routing-protocol; + } + description + "Type of the routing protocol - an identity derived + from the 'routing-protocol' base identity."; + } leaf name { type string; description "An arbitrary name of the routing protocol instance."; } leaf description { type string; description "Textual description of the routing protocol instance."; @@ -1677,47 +1825,37 @@ type boolean; default "true"; description "Enable/disable the routing protocol instance. If this parameter is false, the parent routing protocol instance is disabled and does not appear in operational state data, despite any other configuration that might be present."; } - leaf type { - type identityref { - base routing-protocol; - } - mandatory "true"; + leaf route-preference { + type route-preference; description - "Type of the routing protocol - an identity derived - from the 'routing-protocol' base identity."; + "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 { - must "not(/routing/ribs/rib[name=current()/" - + "preceding-sibling::connected-rib/" - + "rib-name and address-family=/routing/ribs/" - + "rib[name=current()/rib-name]/address-family])" { - error-message - "Duplicate address family for connected RIBs."; - description - "For each address family, there MUST NOT be more - than one connected RIB."; - } key "rib-name"; description - "List of RIBs to which the routing protocol instance - is connected (at most one RIB per address family). + "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 " @@ -1743,29 +1881,29 @@ } 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 + Address-family-specific modules augment this node with their lists of routes."; } } } } container ribs { description - "Configured RIBs."; + "Configuration of RIBs."; list rib { key "name"; 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."; @@ -1847,23 +1986,23 @@ mandatory "true"; description "Type of the route filter.."; } } } } /* RPC methods */ - rpc active-route { + rpc fib-route { description - "Return the active route that a routing-instance uses for + "Return the active FIB route that a routing-instance uses for sending packets to a destination address."; input { leaf routing-instance-name { type routing-instance-state-ref; mandatory "true"; description "Name of the routing instance whose forwarding information base is being queried. If the routing instance with name equal to the value of @@ -1886,21 +2025,25 @@ "The active route for the specified destination. If the routing instance has no active route for the destination address, no output is returned - the server SHALL send an containing a single element . Address family specific modules MUST augment this list with appropriate route contents."; uses address-family; - uses next-hop-content; + 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 { @@ -1923,25 +2066,25 @@ "Number of routes in the RIB."; } } } } 8. IPv4 Unicast Routing Management 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). + 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@2014-05-24.yang" + file "ipv4-unicast-routing@2014-10-26.yang" module ietf-ipv4-unicast-routing { namespace "urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing"; prefix "v4ur"; import ietf-routing { prefix "rt"; } @@ -1977,21 +2121,21 @@ 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."; - revision 2014-05-24 { + revision 2014-10-26 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for Routing Management"; } /* Identities */ identity ipv4-unicast { base rt:ipv4; @@ -2009,51 +2153,49 @@ 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-options/rt:simple-next-hop" { - when "../../rt:address-family = 'v4ur:ipv4-unicast'" { + + "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 { + leaf next-hop-address { type inet:ipv4-address; description "IPv4 address of the next-hop."; } } - augment "/rt:routing-state/rt:ribs/rt:rib/rt:routes/rt:route/" - + "rt:next-hop-options/rt:next-hop-list/rt:next-hop-list/" - + "rt:next-hop" { - when "../../../../rt:address-family = 'v4ur:ipv4-unicast'" { + augment "/rt:routing-state/rt:next-hop-lists/rt:next-hop-list/" + + "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."; } - if-feature rt:multipath-routes; description - "This leaf augments the 'next-hop-list' case of IPv4 unicast + "This leaf augments next-hop list with IPv4 next-hop address. routes."; - leaf address { + leaf next-hop-address { type inet:ipv4-address; description "IPv4 address of the next-hop."; + } } /* Configuration data */ augment "/rt:routing/rt:routing-instance/rt:routing-protocols/" + "rt:routing-protocol/rt:static-routes" { description "This augment defines the configuration of the 'static' pseudo-protocol with data specific to IPv4 unicast."; @@ -2055,195 +2197,136 @@ augment "/rt:routing/rt:routing-instance/rt:routing-protocols/" + "rt:routing-protocol/rt:static-routes" { description "This augment defines the configuration of the 'static' pseudo-protocol with data specific to IPv4 unicast."; container ipv4 { description "Configuration of a 'static' pseudo-protocol instance consists of a list of routes."; list route { - key "id"; + key "destination-prefix"; ordered-by "user"; description "A user-ordered list of static routes."; - leaf id { - type uint32 { - range "1..max"; - } + leaf destination-prefix { + type inet:ipv4-prefix; + mandatory "true"; description - "Unique numeric identifier of the route. - - This value is unrelated to system-assigned 'id' - parameters of routes in RIBs."; + "IPv4 destination prefix."; } leaf description { type string; description "Textual description of the route."; } - leaf destination-prefix { - type inet:ipv4-prefix; - mandatory "true"; + container next-hop { description - "IPv4 destination prefix."; - } - choice next-hop-options { - mandatory "true"; + "Configuration of next-hop."; + grouping next-hop-content { description - "Options for expressing the next-hop in static routes."; - case special-next-hop { - uses rt:special-next-hop; - } - case simple-next-hop { - leaf next-hop { + "Next-hop content for IPv4 unicast static routes."; + uses rt:next-hop-content { + augment "next-hop-options" { + description + "Add next-hop address case."; + leaf next-hop-address { type inet:ipv4-address; description "IPv4 address of the next-hop."; } - leaf outgoing-interface { - type leafref { - path "../../../../../../rt:interfaces/rt:interface/" - + "rt:name"; } - description - "Name of the outgoing interface. - - Only interfaces configured for the ancestor routing - instance can be given."; } } - case next-hop-list { - if-feature rt:multipath-routes; - container next-hop-list { - description - "Configuration of multiple next-hops."; - list next-hop { - key "id"; - description - "An entry of a next-hop list."; - - leaf id { - type uint32; + choice simple-or-list { description - "Unique numeric identifier of the entry. - - This value is unrelated to system-assigned 'id' - parameters of next-hops in RIBs."; - } - leaf address { - type inet:ipv4-address; + "Options for next-hops."; + list multipath-entry { + if-feature rt:multipath-routes; + key "name"; description - "IPv4 address of the next-hop."; - } - leaf outgoing-interface { - type leafref { - path "../../../../../../../../rt:interfaces/" - + "rt:interface/rt:name"; - } + "List of alternative next-hops."; + leaf name { + type string; description - "Name of the outgoing interface. - - Only interfaces configured for the ancestor - routing instance can be given."; - } - uses rt:next-hop-classifiers { - refine "priority" { - default "primary"; - } - refine "weight" { - default "0"; - } + "A unique identifier of the next-hop entry."; } + uses next-hop-content; + uses rt:next-hop-classifiers; } + case simple-next-hop { + uses next-hop-content; } } } } } } /* RPC methods */ - augment "/rt:active-route/rt:input/rt:destination-address" { + augment "/rt:fib-route/rt:input/rt:destination-address" { when "rt:address-family='v4ur:ipv4-unicast'" { description "This augment is valid only for IPv4 unicast."; } description "This leaf augments the 'rt:destination-address' parameter of - the 'rt:active-route' operation."; + the 'rt:fib-route' operation."; leaf address { type inet:ipv4-address; description "IPv4 destination address."; } } - augment "/rt:active-route/rt:output/rt:route" { + augment "/rt:fib-route/rt:output/rt:route" { when "rt:address-family='v4ur:ipv4-unicast'" { description "This augment is valid only for IPv4 unicast."; } description - "This leaf augments the reply to the 'rt:active-route' + "This leaf augments the reply to the 'rt:fib-route' operation."; leaf destination-prefix { type inet:ipv4-prefix; description "IPv4 destination prefix."; } } - augment "/rt:active-route/rt:output/rt:route/rt:next-hop-options/" - + "rt:simple-next-hop" { - when "rt:address-family='v4ur:ipv4-unicast'" { + augment "/rt:fib-route/rt:output/rt:route/rt:next-hop/" + + "rt:next-hop-options/rt:simple-next-hop" { + when "../rt:address-family='v4ur:ipv4-unicast'" { description "This augment is valid only for IPv4 unicast."; } description "This leaf augments the 'simple-next-hop' case in the reply to - the 'rt:active-route' operation."; - leaf next-hop { - type inet:ipv4-address; - description - "IPv4 address of the next-hop."; - } - } - - augment "/rt:active-route/rt:output/rt:route/rt:next-hop-options/" - + "rt:next-hop-list/rt:next-hop-list/rt:next-hop" { - when "../../rt:address-family='v4ur:ipv4-unicast'" { - description - "This augment is valid only for IPv4 unicast."; - } - if-feature rt:multipath-routes; - description - "This leaf augments the 'next-hop-list' case in the reply to - the 'rt:active-route' operation."; - leaf address { + the 'rt:fib-route' operation."; + leaf next-hop-address { type inet:ipv4-address; description "IPv4 address of the next-hop."; } } } 9. IPv6 Unicast Routing Management 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). + 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@2014-05-25.yang" + file "ipv6-unicast-routing@2014-10-26.yang" module ietf-ipv6-unicast-routing { namespace "urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing"; prefix "v6ur"; import ietf-routing { prefix "rt"; } @@ -2287,21 +2371,21 @@ 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."; - revision 2014-05-25 { + revision 2014-10-26 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for Routing Management"; } /* Identities */ identity ipv6-unicast { base rt:ipv6; @@ -2458,47 +2542,45 @@ 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-options/rt:simple-next-hop" { - when "../../rt:address-family = 'v6ur:ipv6-unicast'" { + + "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 { type inet:ipv6-address; description "IPv6 address of the next-hop."; } } - augment "/rt:routing-state/rt:ribs/rt:rib/rt:routes/rt:route/" - + "rt:next-hop-options/rt:next-hop-list/rt:next-hop-list/" - + "rt:next-hop" { - when "../../../../rt:address-family = 'v6ur:ipv6-unicast'" { + augment "/rt:routing-state/rt:next-hop-lists/rt:next-hop-list/" + + "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."; } - if-feature rt:multipath-routes; description - "This leaf augments the 'next-hop-list' case of IPv6 unicast + "This leaf augments next-hop list with IPv6 next-hop address. routes."; - leaf address { + 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" { @@ -2757,180 +2840,121 @@ augment "/rt:routing/rt:routing-instance/rt:routing-protocols/" + "rt:routing-protocol/rt:static-routes" { description "This augment defines the configuration of the 'static' pseudo-protocol with data specific to IPv6 unicast."; container ipv6 { description "Configuration of a 'static' pseudo-protocol instance consists of a list of routes."; list route { - key "id"; + key "destination-prefix"; ordered-by "user"; description "A user-ordered list of static routes."; - leaf id { - type uint32 { - range "1..max"; - } + leaf destination-prefix { + type inet:ipv6-prefix; + mandatory "true"; description - "Unique numeric identifier of the route. - - This value is unrelated to system-assigned 'id' - parameters of routes in RIBs."; + "IPv6 destination prefix."; } leaf description { type string; description "Textual description of the route."; } - leaf destination-prefix { - type inet:ipv6-prefix; - mandatory "true"; + container next-hop { description - "IPv6 destination prefix."; - } - choice next-hop-options { - mandatory "true"; + "Configuration of next-hop."; + grouping next-hop-content { description - "Options for expressing the next-hop in static routes."; - case special-next-hop { - uses rt:special-next-hop; - } - case simple-next-hop { - leaf next-hop { + "Next-hop content for IPv6 unicast static routes."; + uses rt:next-hop-content { + augment "next-hop-options" { + description + "Add next-hop address case."; + leaf next-hop-address { type inet:ipv6-address; description "IPv6 address of the next-hop."; } - leaf outgoing-interface { - type leafref { - path "../../../../../../rt:interfaces/rt:interface/" - + "rt:name"; - } - description - "Name of the outgoing interface. - - Only interfaces configured for the ancestor routing - instance can be given."; } } - case next-hop-list { - if-feature rt:multipath-routes; - container next-hop-list { - description - "Configuration of multiple next-hops."; - list next-hop { - key "id"; - description - "An entry of a next-hop list."; - leaf id { - type uint32; + choice simple-or-list { description - "Unique numeric identifier of the entry. - - This value is unrelated to system-assigned 'id' - parameters of next-hops in RIBs."; - } - leaf address { - type inet:ipv6-address; + "Options for next-hops."; + list multipath-entry { + if-feature rt:multipath-routes; + key "name"; description - "IPv6 address of the next-hop."; - } - leaf outgoing-interface { - type leafref { - path "../../../../../../../../rt:interfaces/" - + "rt:interface/rt:name"; - } + "List of alternative next-hops."; + leaf name { + type string; description - "Name of the outgoing interface. - - Only interfaces configured for the ancestor - routing instance can be given."; - } - uses rt:next-hop-classifiers { - refine "priority" { - default "primary"; - } - refine "weight" { - default "0"; - } - + "A unique identifier of the next-hop entry."; } + uses next-hop-content; + uses rt:next-hop-classifiers; } + case simple-next-hop { + uses next-hop-content; } } } } } } /* RPC methods */ - augment "/rt:active-route/rt:input/rt:destination-address" { + augment "/rt:fib-route/rt:input/rt:destination-address" { when "rt:address-family='v6ur:ipv6-unicast'" { description "This augment is valid only for IPv6 unicast."; + } description "This leaf augments the 'rt:destination-address' parameter of - the 'rt:active-route' operation."; + the 'rt:fib-route' operation."; leaf address { type inet:ipv6-address; description "IPv6 destination address."; } } - augment "/rt:active-route/rt:output/rt:route" { + augment "/rt:fib-route/rt:output/rt:route" { when "rt:address-family='v6ur:ipv6-unicast'" { description "This augment is valid only for IPv6 unicast."; } description - "This leaf augments the reply to the 'rt:active-route' + "This leaf augments the reply to the 'rt:fib-route' operation."; leaf destination-prefix { type inet:ipv6-prefix; description "IPv6 destination prefix."; } } - augment "/rt:active-route/rt:output/rt:route/rt:next-hop-options/" - + "rt:simple-next-hop" { - when "rt:address-family='v6ur:ipv6-unicast'" { + augment "/rt:fib-route/rt:output/rt:route/rt:next-hop/" + + "rt:next-hop-options/rt:simple-next-hop" { + when "../rt:address-family='v4ur:ipv6-unicast'" { description "This augment is valid only for IPv6 unicast."; } description "This leaf augments the 'simple-next-hop' case in the reply to - the 'rt:active-route' operation."; - leaf next-hop { - type inet:ipv6-address; - description - "IPv6 address of the next-hop."; - } - } - - augment "/rt:active-route/rt:output/rt:route/rt:next-hop-options/" - + "rt:next-hop-list/rt:next-hop-list/rt:next-hop" { - when "../../rt:address-family='v6ur:ipv6-unicast'" { - description - "This augment is valid only for IPv6 unicast."; - } - if-feature rt:multipath-routes; - description - "This leaf augments the 'next-hop-list' case in the reply to - the 'rt:active-route' operation."; - leaf address { + the 'rt:fib-route' operation."; + leaf next-hop-address { type inet:ipv6-address; description "IPv6 address of the next-hop."; } } } 10. IANA Considerations @@ -2994,26 +3018,26 @@ 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 content. A number of data nodes defined in the YANG modules belonging to the - configuration part of the core routing data model are writable/ - creatable/deletable (i.e., "config true" in YANG terms, which is the - default). These data nodes may be considered sensitive or vulnerable - in some network environments. Write operations to these data nodes, - such as "edit-config", can have negative effects on the network if - the protocol operations are not properly protected. + configuration part of the core routing data model are + writable/creatable/deletable (i.e., "config true" in YANG terms, + which is the default). These data nodes may be considered sensitive + or vulnerable in some network environments. Write operations to + these data nodes, such as "edit-config", can have negative effects on + the network if the protocol operations are not properly protected. 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. @@ -3025,74 +3049,78 @@ /routing/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 author wishes to thank Nitin Bahadur, Martin Bjorklund, - 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. + The author wishes to thank Nitin Bahadur, Martin Bjorklund, Dean + Bogdanovic, Joel Halpern, Wes Hardaker, Sriganesh Kini, + David Lamparter, Andrew McGregor, Jan Medved, Xiang Li, Acee Lindem, + Stephane Litkowski, Thomas Morin, Tom Petch, Bruno Rijsman, + Juergen Schoenwaelder, Phil Shafer, Dave Thaler, Yi Yang, Derek Man- + Kit Yeung and Jeffrey Zhang for their helpful comments and + suggestions. 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. [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, September 2007. - [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for + [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, - September 2010. + October 2010. [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. - Bierman, "NETCONF Configuration Protocol", RFC 6241, - June 2011. + Bierman, "Network Configuration Protocol (NETCONF)", RFC + 6241, June 2011. - [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", - RFC 6991, July 2013. + [RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, + July 2013. [RFC7223] Bjorklund, M., "A YANG Data Model for Interface Management", RFC 7223, May 2014. - [YANG-IP] Bjorklund, M., "A YANG Data Model for IP Management", - draft-ietf-netmod-ip-cfg-14 (work in progress), - March 2014. + [RFC7277] Bjorklund, M., "A YANG Data Model for IP Management", RFC + 7277, June 2014. 13.2. Informative References + [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private + Networks (VPNs)", RFC 4364, February 2006. + [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. [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration - Protocol (NETCONF) Access Control Model", RFC 6536, - March 2012. + Protocol (NETCONF) Access Control Model", RFC 6536, March + 2012. Appendix A. The Complete Data Trees - This appendix presents the complete configuration and operational - state data trees of the core routing data model. + 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. A.1. Configuration Data +--rw routing +--rw routing-instance* [name] | +--rw name string @@ -3123,92 +3151,106 @@ | | +--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 routing-protocol* [name] + | +--rw routing-protocol* [type name] + | +--rw type identityref | +--rw name string | +--rw description? string | +--rw enabled? boolean - | +--rw type identityref + | +--rw route-preference? route-preference | +--rw connected-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:route* [destination-prefix] | | +--rw v4ur:destination-prefix inet:ipv4-prefix + | | +--rw v4ur:description? string + | | +--rw v4ur:next-hop + | | +--rw (simple-or-list)? + | | +--:(multipath-entry) + | | | +--rw v4ur:multipath-entry* [name] + | | | +--rw v4ur:name string + | | | +--rw (next-hop-options) + | | | | +--:(simple-next-hop) + | | | | | +--rw v4ur:outgoing-interface? + | | | | +--:(special-next-hop) + | | | | | +--rw v4ur:special-next-hop? + | | | | +--:(next-hop-address) + | | | | +--rw v4ur:next-hop-address? + | | | +--rw v4ur:priority? + | | | +--rw v4ur:weight? uint8 + | | +--:(simple-next-hop) | | +--rw (next-hop-options) - | | +--:(special-next-hop) - | | | +--rw v4ur:special-next-hop? enumeration | | +--:(simple-next-hop) - | | | +--rw v4ur:next-hop? inet:ipv4-address - | | | +--rw v4ur:outgoing-interface? leafref - | | +--:(next-hop-list) {rt:multipath-routes}? - | | +--rw v4ur:next-hop-list - | | +--rw v4ur:next-hop* [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 v4ur:outgoing-interface? + | | +--:(special-next-hop) + | | | +--rw v4ur:special-next-hop? + | | +--:(next-hop-address) + | | +--rw v4ur:next-hop-address? | +--rw v6ur:ipv6 - | +--rw v6ur:route* [id] - | +--rw v6ur:id uint32 - | +--rw v6ur:description? string + | +--rw v6ur:route* [destination-prefix] | +--rw v6ur:destination-prefix inet:ipv6-prefix + | +--rw v6ur:description? string + | +--rw v6ur:next-hop + | +--rw (simple-or-list)? + | +--:(multipath-entry) + | | +--rw v6ur:multipath-entry* [name] + | | +--rw v6ur:name string + | | +--rw (next-hop-options) + | | | +--:(simple-next-hop) + | | | | +--rw v6ur:outgoing-interface? + | | | +--:(special-next-hop) + | | | | +--rw v6ur:special-next-hop? + | | | +--:(next-hop-address) + | | | +--rw v6ur:next-hop-address? + | | +--rw v6ur:priority? + | | +--rw v6ur:weight? uint8 + | +--:(simple-next-hop) | +--rw (next-hop-options) - | +--:(special-next-hop) - | | +--rw v6ur:special-next-hop? enumeration | +--:(simple-next-hop) - | | +--rw v6ur:next-hop? inet:ipv6-address - | | +--rw v6ur:outgoing-interface? leafref - | +--:(next-hop-list) {rt:multipath-routes}? - | +--rw v6ur:next-hop-list - | +--rw v6ur:next-hop* [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 v6ur:outgoing-interface? + | +--:(special-next-hop) + | | +--rw v6ur:special-next-hop? + | +--:(next-hop-address) + | +--rw v6ur:next-hop-address? +--rw ribs | +--rw rib* [name] | +--rw name string | +--rw address-family identityref | +--rw description? string | +--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 +A.2. State Data +--ro routing-state +--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-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 @@ -3221,57 +3263,73 @@ | | +--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 routing-protocol* [name] - | +--ro name string + | +--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 import-filter? route-filter-state-ref | +--ro export-filter? route-filter-state-ref + +--ro next-hop-lists + | +--ro next-hop-list* [id] + | +--ro id uint64 + | +--ro address-family identityref + | +--ro next-hop* + | +--ro (next-hop-options) + | | +--:(next-hop-list) + | | | +--ro next-hop-list? next-hop-list-ref + | | +--:(use-rib) + | | | +--ro use-rib? rib-state-ref + | | +--:(simple-next-hop) + | | | +--ro outgoing-interface? + | | | +--ro v4ur:next-hop-address? inet:ipv4-address + | | | +--ro v6ur:next-hop-address? inet:ipv6-address + | | +--:(special-next-hop) + | | +--ro special-next-hop? enumeration + | +--ro priority? enumeration + | +--ro weight? uint8 +--ro ribs | +--ro rib* [name] | +--ro name string | +--ro id uint64 | +--ro address-family identityref | +--ro routes - | | +--ro route* [id] - | | +--ro id uint64 - | | +--ro (next-hop-options) - | | | +--:(special-next-hop) - | | | | +--ro special-next-hop? enumeration + | | +--ro route* + | | +--ro route-preference? route-preference + | | +--ro next-hop + | | | +--ro (next-hop-options) + | | | +--:(next-hop-list) + | | | | +--ro next-hop-list? next-hop-list-ref + | | | +--:(use-rib) + | | | | +--ro use-rib? rib-state-ref | | | +--:(simple-next-hop) - | | | | +--ro outgoing-interface? leafref - | | | | +--ro v4ur:next-hop? inet:ipv4-address - | | | | +--ro v6ur:next-hop? inet:ipv6-address - | | | +--:(next-hop-list) {multipath-routes}? - | | | +--ro next-hop-list - | | | +--ro next-hop* [id] - | | | +--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 outgoing-interface? + | | | | +--ro v4ur:next-hop-address? + | | | | +--ro v6ur:next-hop? + | | | +--:(special-next-hop) + | | | +--ro special-next-hop? enumeration | | +--ro source-protocol identityref + | | +--ro active? empty | | +--ro last-updated? yang:date-and-time | | +--ro v4ur:destination-prefix? inet:ipv4-prefix | | +--ro v6ur:destination-prefix? inet:ipv6-prefix - | +--ro recipient-ribs {multiple-ribs}? + | +--ro recipient-ribs | +--ro recipient-rib* [rib-name] | +--ro rib-name rib-state-ref | +--ro filter? route-filter-state-ref +--ro route-filters +--ro route-filter* [name] +--ro name string +--ro type identityref Appendix B. Minimum Implementation @@ -3284,23 +3342,23 @@ A minimum implementation will provide a single system-controlled routing instance, and will not allow clients to create any user- controlled instances. Typically, neither of the features defined in the "ietf-routing" module ("multiple-ribs" and "multipath-routes") will be supported. This means that: o A single system-controlled RIB (routing table) is available for each supported address family - IPv4, IPv6 or both. These RIBs - are the default RIBs, so they will also appear as system- - controlled entries of the "default-rib" list in operational state - data. No user-controlled RIBs are allowed. + are 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. o Each route has no more than one "next-hop", "outgoing-interface" or "special-next-hop". 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 @@ -3311,21 +3369,21 @@ restricting the data model, e.g., limiting the number of "static" routing protocol instances, preventing any route filters to be configured etc. 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, we do not follow all the guidelines + 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"; @@ -3426,29 +3484,29 @@ } Appendix D. Example: NETCONF Reply This section contains a sample reply to the NETCONF message, which could be sent by a server supporting (i.e., advertising them in the NETCONF message) the following YANG modules: o ietf-interfaces [RFC7223], - o ietf-ip [YANG-IP], + 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 setup as shown in Figure 5: router "A" + We assume a simple network set-up as shown in Figure 5: 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 | | | +--------+--------+ |2001:db8:0:1::2 @@ -3533,21 +3591,23 @@ eth0 ianaift:ethernetCsmacd 00:0C:42:E5:B1:E9 up - 2013-07-02T17:11:27+00:58 + 2014-10-24T17:11:27+00:58 + + true 1500 192.0.2.1 24 @@ -3559,21 +3619,22 @@ eth1 ianaift:ethernetCsmacd up 00:0C:42:E5:B1:EA - 2013-07-02T17:11:27+00:59 + 2014-10-24T17:11:27+00:59 + true 1500 198.51.100.1 24 @@ -3598,51 +3659,51 @@ 2001:db8:0:2::/64 + rt:static st0 Static routing is used for the internal network. - rt:static - 1 0.0.0.0/0 - 192.0.2.2 + + 192.0.2.2 + - - 1 ::/0 - 2001:db8:0:1::2 + + 2001:db8:0:1::2 + rtr0 2718281828 - 192.0.2.1 v4ur:ipv4-unicast ipv4-master v6ur:ipv6-unicast ipv6-master @@ -3657,156 +3718,218 @@ 2001:db8:0:2::/64 - st0 rt:static - + st0 + 5 ipv4-master 897932384 v4ur:ipv4-unicast - 626433832 - - 192.0.2.1/24 + 192.0.2.1/24 + eth0 + + 0 rt:direct - 2013-07-02T17:11:27+01:00 + + + 2014-10-24T17:11:27+01:00 + - 795028841 - 198.51.100.0/24 + 198.51.100.0/24 + + eth1 + rt:direct - 2013-07-02T17:11:27+01:00 + 0 + + 2014-10-24T17:11:27+01:00 + - 971693993 0.0.0.0/0 rt:static - 192.0.2.2 - 2013-07-02T18:02:45+01:00 + 5 + + 192.0.2.2 + + + 2014-10-24T18:02:45+01:00 + ipv6-master 751058209 v6ur:ipv6-unicast - 749445923 - 2001:db8:0:1::/64 + 2001:db8:0:1::/64 + + eth0 + rt:direct - 2013-07-02T17:11:27+01:00 + 0 + + 2014-10-24T17:11:27+01:00 + - 78164062 + - 2001:db8:0:2::/64 + 2001:db8:0:2::/64 + + eth1 + rt:direct - 2013-07-02T17:11:27+01:00 + 0 + + 2014-10-24T17:11:27+01:00 + - 862089986 ::/0 + 2001:db8:0:1::2 + rt:static - 2013-07-02T18:02:45+01:00 + 5 + + 2014-10-24T18:02:45+01:00 + Appendix E. Change Log - RFC Editor: remove this section upon publication as an RFC. + RFC Editor: Remove this section upon publication as an RFC. -E.1. Changes Between Versions -14 and -15 +E.1. 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. + + o Remove the 'id' key from static routes and make 'destination- + prefix' the only key. + + o Added 'route-preference' as a new attribute of routes in RIB. + + o Added 'active' as a new attribute of routes in RIBs. + + o Renamed RPC operation 'active-route' to 'fib-route. + + o Added 'route-preference' as a new parameter of routing protocol + instances, both in configuration and state data. + + o Renamed identity 'rt:standard-routing-instance' to 'rt:default- + routing-instance'. + + 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.2. Changes Between Versions -14 and -15 o Removed all defaults from state data. o Removed default from 'cur-hop-limit' in config. -E.2. Changes Between Versions -13 and -14 +E.3. 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.3. Changes Between Versions -12 and -13 +E.4. Changes Between Versions -12 and -13 o Wrote appendix about minimum implementation. - o Remove "when" statement for IPv6 router interface operational - state - it was dependent on a config value that may not be - present. + 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 operational state. + entries in state data. o Numeric ids are always declared as mandatory and unique. Their description states that they are ephemeral. - o Descriptions of "name" keys in operational state lists are - required to be persistent. + o Descriptions of "name" keys in state data lists are required to be + persistent. 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.4. Changes Between Versions -11 and -12 +E.5. 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.5. Changes Between Versions -10 and -11 +E.6. 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- @@ -3816,70 +3939,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.6. Changes Between Versions -09 and -10 +E.7. Changes Between Versions -09 and -10 - o Added subtree for operational state data ("/routing-state"). + 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.7. Changes Between Versions -08 and -09 +E.8. 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.8. Changes Between Versions -07 and -08 +E.9. Changes Between Versions -07 and -08 o Changed reference from RFC6021 to RFC6021bis. -E.9. Changes Between Versions -06 and -07 +E.10. 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.10. Changes Between Versions -05 and -06 +E.11. 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". @@ -3887,21 +4010,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.11. Changes Between Versions -04 and -05 +E.12. 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 @@ -3922,35 +4045,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.12. Changes Between Versions -03 and -04 +E.13. 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". -E.13. Changes Between Versions -02 and -03 +E.14. 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". @@ -3968,21 +4091,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.14. Changes Between Versions -01 and -02 +E.15. 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. @@ -3992,21 +4115,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.15. Changes Between Versions -00 and -01 +E.16. 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.