--- 1/draft-ietf-netmod-routing-cfg-20.txt 2016-03-17 08:23:01.274905674 -0700 +++ 2/draft-ietf-netmod-routing-cfg-21.txt 2016-03-17 08:23:01.770918078 -0700 @@ -1,137 +1,139 @@ NETMOD Working Group L. Lhotka Internet-Draft CZ.NIC Intended status: Standards Track A. Lindem -Expires: April 18, 2016 Cisco Systems - October 16, 2015 +Expires: September 10, 2016 Cisco Systems + March 17, 2016 A YANG Data Model for Routing Management - draft-ietf-netmod-routing-cfg-20 + draft-ietf-netmod-routing-cfg-21 Abstract - This document contains a specification of three YANG modules. - Together they form the core routing data model which serves as a - framework for configuring and managing a routing subsystem. It is - expected that these modules will be augmented by additional YANG - modules defining data models for routing protocols, route filters and - other functions. The core routing data model provides common - building blocks for such extensions - routing instances, routes, - routing information bases (RIB), and routing protocols. + This document contains a specification of three YANG modules and one + submodule. Together they form the core routing data model which + serves as a framework for configuring and managing a routing + subsystem. It is expected that these modules will be augmented by + additional YANG modules defining data models for routing protocols, + route filters and other functions. The core routing data model + provides common building blocks for such extensions - routes, routing + information bases (RIB), and routing protocols. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on April 18, 2016. + This Internet-Draft will expire on September 10, 2016. Copyright Notice - Copyright (c) 2015 IETF Trust and the persons identified as the + Copyright (c) 2016 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 . . . . . . . . . . . . . . . . . . . . . . . . 3 - 2. Terminology and Notation . . . . . . . . . . . . . . . . . . 3 - 2.1. Glossary of New Terms . . . . . . . . . . . . . . . . . . 4 + 2. Terminology and Notation . . . . . . . . . . . . . . . . . . 4 + 2.1. Glossary of New Terms . . . . . . . . . . . . . . . . . . 5 2.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 5 - 2.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 5 + 2.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 6 3. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 4. The Design of the Core Routing Data Model . . . . . . . . . . 6 + 4. The Design of the Core Routing Data Model . . . . . . . . . . 7 4.1. System-Controlled and User-Controlled List Entries . . . 8 - 5. Basic Building Blocks . . . . . . . . . . . . . . . . . . . . 8 - 5.1. Routing Instance . . . . . . . . . . . . . . . . . . . . 8 - 5.1.1. Parameters of IPv6 Router Interfaces . . . . . . . . 9 - 5.2. Route . . . . . . . . . . . . . . . . . . . . . . . . . . 10 - 5.3. Routing Information Base (RIB) . . . . . . . . . . . . . 11 - 5.4. Routing Protocol . . . . . . . . . . . . . . . . . . . . 11 - 5.4.1. Routing Pseudo-Protocols . . . . . . . . . . . . . . 12 - 5.4.2. Defining New Routing Protocols . . . . . . . . . . . 12 - 5.5. RPC Operations . . . . . . . . . . . . . . . . . . . . . 13 + 5. Basic Building Blocks . . . . . . . . . . . . . . . . . . . . 9 + 5.1. Route . . . . . . . . . . . . . . . . . . . . . . . . . . 9 + 5.2. Routing Information Base (RIB) . . . . . . . . . . . . . 9 + 5.3. Routing Protocol . . . . . . . . . . . . . . . . . . . . 10 + 5.3.1. Routing Pseudo-Protocols . . . . . . . . . . . . . . 10 + 5.3.2. Defining New Routing Protocols . . . . . . . . . . . 11 + 5.4. RPC Operations . . . . . . . . . . . . . . . . . . . . . 12 + 5.5. Parameters of IPv6 Router Advertisements . . . . . . . . 12 6. Interactions with Other YANG Modules . . . . . . . . . . . . 13 6.1. Module "ietf-interfaces" . . . . . . . . . . . . . . . . 13 6.2. Module "ietf-ip" . . . . . . . . . . . . . . . . . . . . 13 7. Routing Management YANG Module . . . . . . . . . . . . . . . 14 - 8. IPv4 Unicast Routing Management YANG Module . . . . . . . . . 29 - 9. IPv6 Unicast Routing Management YANG Module . . . . . . . . . 33 - 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46 - 11. Security Considerations . . . . . . . . . . . . . . . . . . . 47 - 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 48 - 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 48 - 13.1. Normative References . . . . . . . . . . . . . . . . . . 48 - 13.2. Informative References . . . . . . . . . . . . . . . . . 49 - Appendix A. The Complete Data Trees . . . . . . . . . . . . . . 49 - A.1. Configuration Data . . . . . . . . . . . . . . . . . . . 49 + 8. IPv4 Unicast Routing Management YANG Module . . . . . . . . . 25 + 9. IPv6 Unicast Routing Management YANG Module . . . . . . . . . 30 + 9.1. IPv6 Router Advertisements Submodule . . . . . . . . . . 34 + 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 44 + 11. Security Considerations . . . . . . . . . . . . . . . . . . . 45 + 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 46 + 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 46 + 13.1. Normative References . . . . . . . . . . . . . . . . . . 46 + 13.2. Informative References . . . . . . . . . . . . . . . . . 47 + Appendix A. The Complete Data Trees . . . . . . . . . . . . . . 48 + A.1. Configuration Data . . . . . . . . . . . . . . . . . . . 48 A.2. State Data . . . . . . . . . . . . . . . . . . . . . . . 50 - Appendix B. Minimum Implementation . . . . . . . . . . . . . . . 51 - Appendix C. Example: Adding a New Routing Protocol . . . . . . . 52 - Appendix D. Example: NETCONF Reply . . . . . . . . . . . . 54 - Appendix E. Change Log . . . . . . . . . . . . . . . . . . . . . 61 - E.1. Changes Between Versions -19 and -20 . . . . . . . . . . 61 - E.2. Changes Between Versions -18 and -19 . . . . . . . . . . 61 - E.3. Changes Between Versions -17 and -18 . . . . . . . . . . 61 - E.4. Changes Between Versions -16 and -17 . . . . . . . . . . 62 - E.5. Changes Between Versions -15 and -16 . . . . . . . . . . 62 - E.6. Changes Between Versions -14 and -15 . . . . . . . . . . 63 - E.7. Changes Between Versions -13 and -14 . . . . . . . . . . 63 - E.8. Changes Between Versions -12 and -13 . . . . . . . . . . 63 - E.9. Changes Between Versions -11 and -12 . . . . . . . . . . 64 - E.10. Changes Between Versions -10 and -11 . . . . . . . . . . 64 - E.11. Changes Between Versions -09 and -10 . . . . . . . . . . 65 - E.12. Changes Between Versions -08 and -09 . . . . . . . . . . 65 - E.13. Changes Between Versions -07 and -08 . . . . . . . . . . 65 - E.14. Changes Between Versions -06 and -07 . . . . . . . . . . 65 - E.15. Changes Between Versions -05 and -06 . . . . . . . . . . 66 - E.16. Changes Between Versions -04 and -05 . . . . . . . . . . 66 - E.17. Changes Between Versions -03 and -04 . . . . . . . . . . 67 - E.18. Changes Between Versions -02 and -03 . . . . . . . . . . 67 - E.19. Changes Between Versions -01 and -02 . . . . . . . . . . 68 - E.20. Changes Between Versions -00 and -01 . . . . . . . . . . 68 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 69 + Appendix B. Minimum Implementation . . . . . . . . . . . . . . . 50 + Appendix C. Example: Adding a New Routing Protocol . . . . . . . 51 + Appendix D. Example: NETCONF Reply . . . . . . . . . . . . 53 + Appendix E. Change Log . . . . . . . . . . . . . . . . . . . . . 59 + E.1. Changes Between Versions -20 and -21 . . . . . . . . . . 59 + E.2. Changes Between Versions -19 and -20 . . . . . . . . . . 60 + E.3. Changes Between Versions -18 and -19 . . . . . . . . . . 60 + E.4. Changes Between Versions -17 and -18 . . . . . . . . . . 60 + E.5. Changes Between Versions -16 and -17 . . . . . . . . . . 61 + E.6. Changes Between Versions -15 and -16 . . . . . . . . . . 61 + E.7. Changes Between Versions -14 and -15 . . . . . . . . . . 62 + E.8. Changes Between Versions -13 and -14 . . . . . . . . . . 62 + E.9. Changes Between Versions -12 and -13 . . . . . . . . . . 62 + E.10. Changes Between Versions -11 and -12 . . . . . . . . . . 63 + E.11. Changes Between Versions -10 and -11 . . . . . . . . . . 63 + E.12. Changes Between Versions -09 and -10 . . . . . . . . . . 63 + E.13. Changes Between Versions -08 and -09 . . . . . . . . . . 64 + E.14. Changes Between Versions -07 and -08 . . . . . . . . . . 64 + E.15. Changes Between Versions -06 and -07 . . . . . . . . . . 64 + E.16. Changes Between Versions -05 and -06 . . . . . . . . . . 64 + E.17. Changes Between Versions -04 and -05 . . . . . . . . . . 65 + E.18. Changes Between Versions -03 and -04 . . . . . . . . . . 66 + E.19. Changes Between Versions -02 and -03 . . . . . . . . . . 66 + E.20. Changes Between Versions -01 and -02 . . . . . . . . . . 67 + E.21. Changes Between Versions -00 and -01 . . . . . . . . . . 67 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 67 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. It also - augments the "ietf-interfaces" module [RFC7223] with IPv6 router - configuration variables required by [RFC4861]. + module with additional data specific to IPv6 unicast. Its + submodule "ietf-ipv6-router-advertisements" also augments the + "ietf-interfaces" module [RFC7223] with IPv6 router configuration + variables required by [RFC4861]. These modules together define the so-called core routing data model, which is intended as a basis for future data model development covering more sophisticated routing systems. While these three modules can be directly used for simple IP devices with static routing (see 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 @@ -185,21 +187,21 @@ 2.1. Glossary of New Terms core routing data model: YANG data model comprising "ietf-routing", "ietf-ipv4-unicast-routing" and "ietf-ipv6-unicast-routing" modules. direct route: a route to a directly connected network. routing information base (RIB): An object containing a list of - routes together with other information. See Section 5.3 for + routes together with other information. See Section 5.2 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 state data ("config false") that is created and deleted as a direct consequence of certain configuration changes. See Section 4.1 for details. @@ -268,295 +270,208 @@ 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 + The core routing data model consists of three YANG modules and one + submodule. 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. Module "ietf-ipv6-unicast- + routing" has a submodule, "ietf-ipv6-router-advertisements", that + defines configuration variables for IPv6 router advertisements as + required by [RFC4861]. Figures 1 and 2 show abridged views of the configuration and state data hierarchies. See Appendix A for the complete data trees. +--rw routing - +--rw routing-instance* [name] - +--rw name - +--rw type? - +--rw enabled? +--rw router-id? - +--rw description? +--rw routing-protocols | +--rw routing-protocol* [type name] | +--rw type | +--rw name | +--rw description? | +--rw static-routes - | ... + | | +--rw v6ur:ipv6 + | | | ... + | | +--rw v4ur:ipv4 + | | ... + | +--rw rip:rip! + | +--rw rip:interfaces + | | ... + | +--rw rip:update-interval? +--rw ribs +--rw rib* [name] +--rw name +--rw address-family? +--rw description? Figure 1: Configuration data hierarchy. +--ro routing-state - +--ro routing-instance* [name] - +--ro name - +--ro type? +--ro router-id? +--ro interfaces | +--ro interface* +--ro routing-protocols | +--ro routing-protocol* [type name] | +--ro type | +--ro name +--ro ribs +--ro rib* [name] +--ro name +--ro address-family +--ro default-rib? +--ro routes + +--ro route* ... Figure 2: State data hierarchy. As can be seen from Figures 1 and 2, the core routing data model - introduces several generic components of a routing framework: routing - instances, RIBs containing lists of routes, and routing protocols. - Section 5 describes these components in more detail. + introduces several generic components of a routing framework: routes, + RIBs containing lists of routes, and routing protocols. Section 5 + describes these components in more detail. 4.1. System-Controlled and User-Controlled List Entries The core routing data model defines several lists in the schema tree, - for example "routing-instance" or "rib", that have to be populated - with at least one entry in any properly functioning device, and - additional entries may be configured by a client. + such as "rib", that have to be populated with at least one entry in + any properly functioning device, and additional entries may be + configured by a client. In such a list, the server creates the required item as a so-called system-controlled entry in state data, i.e., inside the "routing- state" container. + An example can be seen in Appendix D: the "/routing-state/ribs/rib" + list has two system-controlled entries named "ipv4-master" and + "ipv6-master". + Additional entries may be created in the configuration by a client, e.g., via the NETCONF protocol. These are so-called user-controlled entries. If the server accepts a configured user-controlled entry, then this entry also appears in the state data version of the list. Corresponding entries in both versions of the list (in state data and configuration) have the same value of the list key. A client may also provide supplemental configuration of system- controlled entries. To do so, the client creates a new entry in the configuration with the desired contents. In order to bind this entry to 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". - Deleting a user-controlled entry from the configuration list results in the removal of the corresponding entry in the state data list. In contrast, if a system-controlled entry is deleted from the configuration list, only the extra configuration specified in that entry is removed but the corresponding state data entry remains in the list. 5. Basic Building Blocks This section describes the essential components of the core routing data model. -5.1. 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. - - No attempt has been made to define the semantics for every type of - routing instance. The core routing data model defines identities for - two ubiquitous routing instance types: - - o "default-routing-instance" - this routing instance type represents - the default (or only) routing instance. All implementations MUST - provide one and only one system-controlled routing instance of - this type. - - o "vrf-routing-instance" - this routing instance type represents VRF - (virtual routing and forwarding) routing instances that are used - for virtual private networks (VPN) including BGP/MPLS - VPN_[RFC4364]. - - It is expected that future YANG modules will define other types of - routing instances. For every such type, an identity derived from - "rt:routing-instance" SHALL be defined. This identity is then - referred to by the value of the "type" leaf (a child node of - "routing-instance" list). - - By default, all network layer interfaces are assigned to the routing - instance of the "default-routing-instance" type. This can be changed - by configuring the "rt:routing-instance" leaf in the interface - configuration. - -5.1.1. Parameters of IPv6 Router Interfaces - - YANG module "ietf-ipv6-unicast-routing" (Section 9) augments the - configuration and state data of IPv6 interfaces with definitions of - the following variables as required by [RFC4861], sec. 6.2.1: - - o send-advertisements, - - o max-rtr-adv-interval, - - o min-rtr-adv-interval, - - o managed-flag, - - o other-config-flag, - - o link-mtu, - - o reachable-time, - o retrans-timer, - - o cur-hop-limit, - - o default-lifetime, - - o prefix-list: a list of prefixes to be advertised. - - The following parameters are associated with each prefix in the - list: - - * valid-lifetime, - - * on-link-flag, - - * preferred-lifetime, - - * autonomous-flag. - - NOTES: - - 1. The "IsRouter" flag, which is also required by [RFC4861], is - implemented in the "ietf-ip" module [RFC7277] (leaf - "ip:forwarding"). - - 2. The original specification [RFC4861] allows the implementations - to decide whether the "valid-lifetime" and "preferred-lifetime" - parameters remain the same in consecutive advertisements, or - decrement in real time. However, the latter behavior seems - 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 +5.1. 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 addresses for which the route may be used. This attribute is mandatory. o "route-preference": an integer value (also known as administrative distance) that is used for selecting a preferred route among routes with the same destination prefix. A lower value means a more preferred route. o "next-hop": determines the action to be performed with a packet. Routes are primarily state data that appear as entries of RIBs - (Section 5.3) but they may also be found in configuration data, for + (Section 5.2) but they may also be found in configuration data, for example as manually configured static routes. In the latter case, configurable route attributes are generally a subset of route attributes described above. -5.3. Routing Information Base (RIB) +5.2. Routing Information Base (RIB) - Every routing instance manages one or more routing information bases - (RIB). A RIB is a list of routes complemented with administrative - data. Each RIB contains only routes of one address family. An - address family is represented by an identity derived from the - "rt:address-family" base identity. + Every implementation of the core routing data model manages one or + more routing information bases (RIB). A RIB is a list of routes + complemented with administrative data. Each RIB contains only routes + of one address family. An address family is represented by an + identity derived from the "rt:address-family" base identity. In the core routing data model, RIBs are state data represented as - entries of the list "/routing-state/routing-instance/ribs/rib". The - contents of RIBs are controlled and manipulated by routing protocol - operations which may result in route additions, removals and - modifications. This also includes manipulations via the "static" - and/or "direct" pseudo-protocols, see Section 5.4.1. + 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.3.1. - Each routing instance has, for every supported address family, one - RIB marked as the so-called default RIB. Its role is explained in - Section 5.4. + For every supported address family, exactly one RIB MUST be marked as + the so-called default RIB. Its role is explained in Section 5.3. Simple router implementations that do not advertise the feature "multiple-ribs" will typically create one system-controlled RIB per - routing instance and supported address family, and mark it as the - default RIB. + supported address family, and mark it as the default RIB. More complex router implementations advertising the "multiple-ribs" feature support multiple RIBs per address family that can be used for policy routing and other purposes. -5.4. Routing Protocol +5.3. 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). + defining multiple routing protocol instances. 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.3.1). Multiple routing protocol instances of the same type MAY be - configured within the same routing instance. + configured. -5.4.1. Routing Pseudo-Protocols +5.3.1. Routing Pseudo-Protocols The core routing data model defines two special routing protocol types - "direct" and "static". Both are in fact pseudo-protocols, which means they are confined to the local device and do not exchange any routing information with adjacent routers. - 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. Direct routes MUST be - installed in default RIBs of all supported address families. + Every implementation of the core routing data model MUST provide + 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. + Direct routes MUST be installed in default RIBs of all supported + address families. A pseudo-protocol of the type "static" allows for specifying routes manually. It MAY be configured in zero or multiple instances, - although a typical configuration will have exactly one instance per - routing instance. + although a typical configuration will have exactly one instance. -5.4.2. Defining New Routing Protocols +5.3.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: + the protocol-specific configuration and state data, and it has to + integrate 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 @@ -578,28 +493,84 @@ protocol" is equal to the new protocol's identity. It is also RECOMMENDED that protocol-specific data nodes be encapsulated in an appropriately named container with presence. Such a container may contain mandatory data nodes that are otherwise forbidden at the top level of an augment. The above steps are implemented by the example YANG module for the RIP routing protocol in Appendix C. -5.5. RPC Operations +5.4. RPC Operations The "ietf-routing" module defines one RPC operation: - o fib-route: query a routing instance for the active route in the + o fib-route: query the routing system 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. + address is passed as the input parameter. + +5.5. Parameters of IPv6 Router Advertisements + + YANG module "ietf-ipv6-router-advertisements" (Section 9.1), which is + a submodule of the "ietf-ipv6-unicast-routing" module, augments the + configuration and state data of IPv6 interfaces with definitions of + the following variables as required by [RFC4861], sec. 6.2.1: + + o send-advertisements, + + o max-rtr-adv-interval, + + o min-rtr-adv-interval, + + o managed-flag, + + o other-config-flag, + + o link-mtu, + + o reachable-time, + + o retrans-timer, + + o cur-hop-limit, + + o default-lifetime, + + o prefix-list: a list of prefixes to be advertised. + + The following parameters are associated with each prefix in the + list: + + * valid-lifetime, + + * on-link-flag, + + * preferred-lifetime, + + * autonomous-flag. + + NOTES: + + 1. The "IsRouter" flag, which is also required by [RFC4861], is + implemented in the "ietf-ip" module [RFC7277] (leaf + "ip:forwarding"). + + 2. The original specification [RFC4861] allows the implementations + to decide whether the "valid-lifetime" and "preferred-lifetime" + parameters remain the same in consecutive advertisements, or + decrement in real time. However, the latter behavior seems + 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. 6. Interactions with Other YANG Modules The semantics of the core routing data model also depends on several configuration parameters that are defined in other YANG modules. 6.1. Module "ietf-interfaces" The following boolean switch is defined in the "ietf-interfaces" YANG module [RFC7223]: @@ -647,31 +619,30 @@ direct route. The destination prefix of this route is set according to the configured IP address and network prefix/mask, and the interface is set as the outgoing interface for that route. 7. Routing Management YANG Module RFC Editor: In this section, replace all occurrences of 'XXXX' with the actual RFC number and all occurrences of the revision date below with the date of RFC publication (and remove this note). - file "ietf-routing@2015-10-16.yang" + file "ietf-routing@2016-03-09.yang" module ietf-routing { namespace "urn:ietf:params:xml:ns:yang:ietf-routing"; prefix "rt"; import ietf-yang-types { prefix "yang"; - } import ietf-interfaces { prefix "if"; } organization "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; contact @@ -671,74 +642,75 @@ prefix "if"; } organization "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; contact "WG Web: WG List: - WG Chair: Thomas Nadeau - + WG Chair: Lou Berger + WG Chair: Juergen Schoenwaelder WG Chair: Kent Watsen Editor: Ladislav Lhotka - "; + + + Editor: Acee Lindem + "; description "This YANG module defines essential components for the management of a routing subsystem. - Copyright (c) 2015 IETF Trust and the persons identified as + Copyright (c) 2016 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and 'OPTIONAL' in the module text are to be interpreted as described in RFC 2119 (http://tools.ietf.org/html/rfc2119). This version of this YANG module is part of RFC XXXX (http://tools.ietf.org/html/rfcXXXX); see the RFC itself for full legal notices."; - revision 2015-10-16 { + revision 2016-03-09 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for Routing Management"; } - /* Features */ feature multiple-ribs { description "This feature indicates that the server supports user-defined RIBs. Servers that do not advertise this feature SHOULD provide - exactly one system-controlled RIB per routing-instance and - supported address family and make them also the default RIBs. - These RIBs then appear as entries of the list - /routing-state/routing-instance/ribs/rib."; + 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 router-id { description "This feature indicates that the server supports configuration of an explicit 32-bit router ID that is used by some routing protocols. Servers that do not advertise this feature set a router ID algorithmically, usually to one of configured IPv4 addresses. @@ -758,46 +730,25 @@ description "This identity represents IPv4 address family."; } identity ipv6 { base address-family; description "This identity represents IPv6 address family."; } - identity routing-instance { - description - "Base identity from which identities describing routing - instance types are derived."; - } - - identity default-routing-instance { - base routing-instance; - description - "This identity represents either a default routing instance, or - the only routing instance on systems that do not support - multiple instances."; - } - - identity vrf-routing-instance { - base routing-instance; - description - "This identity represents a VRF routing instance. The type is - distinct from the default-routing-instance. There may be - multiple vrf-routing-interfaces."; - } - identity routing-protocol { description "Base identity from which routing protocol identities are derived."; + } identity direct { base routing-protocol; description "Routing pseudo-protocol that provides routes to directly connected networks."; } identity static { @@ -801,38 +752,20 @@ } identity static { base routing-protocol; description "Static routing pseudo-protocol."; } /* Type Definitions */ - typedef routing-instance-ref { - type leafref { - path "/rt:routing/rt:routing-instance/rt:name"; - } - description - "This type is used for leafs that reference a routing instance - configuration."; - } - - typedef routing-instance-state-ref { - type leafref { - path "/rt:routing-state/rt:routing-instance/rt:name"; - } - description - "This type is used for leafs that reference state data of a - routing instance."; - } - typedef route-preference { type uint32; description "This type is used for route preferences."; } /* Groupings */ grouping address-family { description @@ -968,86 +901,36 @@ type yang:date-and-time; description "Time stamp of the last modification of the route. If the route was never modified, it is the time when the route was inserted into the RIB."; } } /* State data */ - augment "/if:interfaces-state/if:interface" { - description - "This augment adds a reference to the routing-instance to which - the interface is assigned."; - leaf routing-instance { - type routing-instance-state-ref; - description - "The name of the routing instance to which the interface is - assigned."; - } - } - container routing-state { config "false"; description "State data of the routing subsystem."; - list routing-instance { - key "name"; - min-elements "1"; - description - "Each list entry is a container for state data of a routing - instance. - - An implementation MUST provide one and only one - system-controlled routing instance(s) of the type - 'rt:default-routing-instance', and MAY support other types. - - An implementation MAY restrict the number of routing - instances of each supported type."; - leaf name { - type string; - description - "The name of the routing instance. - - For system-controlled instances the name SHOULD be - persistent, i.e., it doesn't change after a reboot."; - } - leaf type { - type identityref { - base routing-instance; - } - description - "The routing instance type."; - } uses router-id { description "Global router ID. It may be either configured or assigned algorithmically by the implementation."; } container interfaces { description - "Network layer interfaces belonging to the routing - instance."; + "Network layer interfaces used for routing."; leaf-list interface { type if:interface-state-ref; - must "../../name = /if:interfaces-state/" - + "if:interface[if:name=current()]/" - + "rt:routing-instance" { - error-message - "Routing instance is not assigned to the interface."; - description - "This reference must mirror a corresponding assignment - of the ancestor routing-instance to the interface."; - } description "Each entry is a reference to the name of a configured network layer interface."; } } container routing-protocols { description "Container for the list of routing protocol instances."; list routing-protocol { key "type name"; @@ -1062,57 +945,54 @@ 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."; + For system-controlled instances this name is persistent, + i.e., it SHOULD NOT change across reboots."; } } } container ribs { description "Container for RIBs."; list rib { key "name"; min-elements "1"; description - "Each entry represents a RIB identified by the 'name' - key. All routes in a RIB MUST belong to the same address + "Each entry represents a RIB identified by the 'name' key. + All routes in a RIB MUST belong to the same address family. - For each routing instance, an implementation SHOULD - provide one system-controlled default RIB for each - supported address family."; + An implementation SHOULD provide one system-controlled + default RIB for each supported address family."; leaf name { type string; description "The name of the RIB."; } uses address-family; leaf default-rib { if-feature multiple-ribs; type boolean; default "true"; description - "This flag has the value of 'true' if and only if the - RIB is the default RIB for the given address family. + "This flag has the value of 'true' if and only if the RIB + is the default RIB for the given address family. - A default RIB always receives direct routes. By - default it also receives routes from all routing - protocols."; + A default RIB always receives direct routes. By default + it also receives routes from all routing protocols."; } container routes { description "Current content of the RIB."; list route { description "A RIB route entry. This data node MUST be augmented with information specific for routes of each address family."; leaf route-preference { @@ -1127,91 +1007,37 @@ description "Route's next-hop attribute."; uses next-hop-state-content; } uses route-metadata; } } } } } - } /* Configuration Data */ - augment "/if:interfaces/if:interface" { - description - "This augment adds a routing-instance reference to interface - configuration."; - leaf routing-instance { - type routing-instance-ref; - description - "The name of the routing instance to which the interface is - to be assigned. - - By default, all network layer interfaces belong to the - routing-instance of the 'default-routing-instance' type."; - } - } - container routing { description "Configuration parameters for the routing subsystem."; - list routing-instance { - key "name"; - description - "Configuration of a routing instance."; - leaf name { - type string; - description - "The name of the routing instance. - - For system-controlled entries, the value of this leaf must - be the same as the name of the corresponding entry in - state data. - - For user-controlled entries, an arbitrary name can be - used."; - } - leaf type { - type identityref { - base routing-instance; - } - default "rt:default-routing-instance"; - description - "The type of the routing instance."; - } - leaf enabled { - type boolean; - default "true"; - description - "Enable/disable the routing instance. - - If this parameter is false, the parent routing instance is - disabled and does not appear in state data, despite any - other configuration that might be present."; - } uses router-id { if-feature router-id; description "Configuration of the global router ID. Routing protocols that use router ID can use this parameter or override it with another value."; } - leaf description { - type string; - description - "Textual description of the routing instance."; - } container routing-protocols { description "Configuration of routing protocol instances."; + list routing-protocol { key "type name"; description "Each entry contains configuration of a routing protocol instance."; leaf type { type identityref { base routing-protocol; } description @@ -1208,132 +1034,118 @@ list routing-protocol { key "type name"; description "Each entry contains configuration of a routing protocol instance."; leaf type { type identityref { base routing-protocol; } description - "Type of the routing protocol - an identity derived - from the 'routing-protocol' base identity."; + "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."; + "Textual description of the routing protocol instance."; } container static-routes { when "../type='rt:static'" { description - "This container is only valid for the 'static' - routing protocol."; + "This container is only valid for the 'static' routing + protocol."; } description "Configuration of the 'static' pseudo-protocol. Address-family-specific modules augment this node with their lists of routes."; } } - } container ribs { description "Configuration of RIBs."; list rib { key "name"; description - "Each entry contains configuration for a RIB identified - by the 'name' key. + "Each entry contains configuration for a RIB identified by + the 'name' key. Entries having the same key as a system-controlled entry - of the list /routing-state/routing-instance/ribs/rib are - used for configuring parameters of that entry. Other - entries define additional user-controlled RIBs."; + of the list /routing-state/ribs/rib are used for + configuring parameters of that entry. Other entries define + additional user-controlled RIBs."; leaf name { type string; description "The name of the RIB. For system-controlled entries, the value of this leaf - must be the same as the name of the corresponding - entry in state data. + must be the same as the name of the corresponding entry + in state data. For user-controlled entries, an arbitrary name can be used."; } uses address-family { description "Address family of the RIB. It is mandatory for user-controlled RIBs. For system-controlled RIBs it can be omitted, otherwise it - must match the address family of the corresponding - state entry."; + must match the address family of the corresponding state + entry."; refine "address-family" { mandatory "false"; } } leaf description { type string; description "Textual description of the RIB."; } } } } - } + /* RPC operations */ rpc fib-route { description - "Return the active FIB route that a routing-instance uses for - sending packets to a destination address."; + "Return the active FIB route that is used for sending packets + to a destination address."; input { - leaf routing-instance-name { - type routing-instance-state-ref; - mandatory "true"; - description - "Name of the routing instance whose forwarding information - base is being queried. - - If the routing instance with name equal to the value of - this parameter doesn't exist, then this operation SHALL - fail with error-tag 'data-missing' and error-app-tag - 'routing-instance-not-found'."; - } container destination-address { description "Network layer destination address. Address family specific modules MUST augment this container with a leaf named 'address'."; + uses address-family; } } output { container route { description "The active FIB route for the specified destination. - If the routing instance has no active FIB route for the - destination address, no output is returned - the server - SHALL send an containing a single element - . + If no active FIB route exists 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; container next-hop { description "Route's next-hop attribute."; uses next-hop-state-content; } uses route-metadata; @@ -1344,21 +1155,21 @@ } 8. IPv4 Unicast Routing Management YANG Module RFC Editor: In this section, replace all occurrences of 'XXXX' with the actual RFC number and all occurrences of the revision date below with the date of RFC publication (and remove this note). - file "ietf-ipv4-unicast-routing@2015-10-16.yang" + file "ietf-ipv4-unicast-routing@2016-03-09.yang" module ietf-ipv4-unicast-routing { namespace "urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing"; prefix "v4ur"; import ietf-routing { prefix "rt"; } @@ -1358,115 +1169,118 @@ namespace "urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing"; prefix "v4ur"; import ietf-routing { prefix "rt"; } import ietf-inet-types { prefix "inet"; + } organization "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; contact "WG Web: WG List: - WG Chair: Thomas Nadeau - + WG Chair: Lou Berger + WG Chair: Juergen Schoenwaelder WG Chair: Kent Watsen Editor: Ladislav Lhotka - "; + + + Editor: Acee Lindem + "; description "This YANG module augments the 'ietf-routing' module with basic configuration and state data for IPv4 unicast routing. - Copyright (c) 2015 IETF Trust and the persons identified as + Copyright (c) 2016 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and 'OPTIONAL' in the module text are to be interpreted as described in RFC 2119 (http://tools.ietf.org/html/rfc2119). This version of this YANG module is part of RFC XXXX (http://tools.ietf.org/html/rfcXXXX); see the RFC itself for full legal notices."; - revision 2015-10-16 { + revision 2016-03-09 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for Routing Management"; } /* Identities */ identity ipv4-unicast { base rt:ipv4; description "This identity represents the IPv4 unicast address family."; } /* State data */ - augment "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/" - + "rt:routes/rt:route" { + augment "/rt:routing-state/rt:ribs/rt:rib/rt:routes/rt:route" { when "../../rt:address-family = 'v4ur:ipv4-unicast'" { description "This augment is valid only for IPv4 unicast."; } description "This leaf augments an IPv4 unicast route."; leaf destination-prefix { type inet:ipv4-prefix; description "IPv4 destination prefix."; } } - augment "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/" - + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options" { + augment "/rt:routing-state/rt:ribs/rt:rib/rt:routes/rt:route/" + + "rt:next-hop/rt:next-hop-options" { when "../../../rt:address-family = 'v4ur:ipv4-unicast'" { description "This augment is valid only for IPv4 unicast."; } description "Augment 'next-hop-options' in IPv4 unicast routes."; leaf next-hop-address { type inet:ipv4-address; description "IPv4 address of the next-hop."; } } /* Configuration data */ - augment "/rt:routing/rt:routing-instance/rt:routing-protocols/" - + "rt:routing-protocol/rt:static-routes" { + augment "/rt:routing/rt:routing-protocols/rt:routing-protocol/" + + "rt:static-routes" { description "This augment defines the configuration of the 'static' pseudo-protocol with data specific to IPv4 unicast."; container ipv4 { description "Configuration of a 'static' pseudo-protocol instance consists of a list of routes."; list route { key "destination-prefix"; description @@ -1552,90 +1366,88 @@ } 9. IPv6 Unicast Routing Management YANG Module RFC Editor: In this section, replace all occurrences of 'XXXX' with the actual RFC number and all occurrences of the revision date below with the date of RFC publication (and remove this note). - file "ietf-ipv6-unicast-routing@2015-10-16.yang" + file "ietf-ipv6-unicast-routing@2016-03-09.yang" module ietf-ipv6-unicast-routing { namespace "urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing"; prefix "v6ur"; import ietf-routing { prefix "rt"; } import ietf-inet-types { prefix "inet"; } - import ietf-interfaces { - prefix "if"; - } - - import ietf-ip { - prefix "ip"; + include ietf-ipv6-router-advertisements { + revision-date 2016-03-09; } organization "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; contact "WG Web: WG List: - WG Chair: Thomas Nadeau - + WG Chair: Lou Berger + WG Chair: Juergen Schoenwaelder WG Chair: Kent Watsen Editor: Ladislav Lhotka - "; + + + Editor: Acee Lindem + "; description "This YANG module augments the 'ietf-routing' module with basic configuration and state data for IPv6 unicast routing. - Copyright (c) 2015 IETF Trust and the persons identified as + Copyright (c) 2016 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and 'OPTIONAL' in the module text are to be interpreted as described in RFC 2119 (http://tools.ietf.org/html/rfc2119). This version of this YANG module is part of RFC XXXX (http://tools.ietf.org/html/rfcXXXX); see the RFC itself for full legal notices."; - revision 2015-10-16 { + revision 2016-03-09 { description "Initial revision."; - reference "RFC XXXX: A YANG Data Model for Routing Management"; } /* Identities */ identity ipv6-unicast { base rt:ipv6; description "This identity represents the IPv6 unicast address family."; @@ -1636,24 +1448,233 @@ /* Identities */ identity ipv6-unicast { base rt:ipv6; description "This identity represents the IPv6 unicast address family."; } /* State data */ + augment "/rt:routing-state/rt:ribs/rt:rib/rt:routes/rt:route" { + when "../../rt:address-family = 'v6ur:ipv6-unicast'" { + description + "This augment is valid only for IPv6 unicast."; + } + description + "This leaf augments an IPv6 unicast route."; + leaf destination-prefix { + type inet:ipv6-prefix; + description + "IPv6 destination prefix."; + } + } + + augment "/rt:routing-state/rt:ribs/rt:rib/rt:routes/rt:route/" + + "rt:next-hop/rt:next-hop-options" { + when "../../../rt:address-family = 'v6ur:ipv6-unicast'" { + description + "This augment is valid only for IPv6 unicast."; + } + description + "Augment 'next-hop-options' in IPv6 unicast routes."; + leaf next-hop-address { + type inet:ipv6-address; + description + "IPv6 address of the next-hop."; + } + } + + /* Configuration data */ + + augment "/rt:routing/rt:routing-protocols/rt:routing-protocol/" + + "rt:static-routes" { + description + "This augment defines the configuration of the 'static' + pseudo-protocol with data specific to IPv6 unicast."; + container ipv6 { + description + "Configuration of a 'static' pseudo-protocol instance + consists of a list of routes."; + list route { + key "destination-prefix"; + description + "A list of static routes."; + leaf destination-prefix { + type inet:ipv6-prefix; + mandatory "true"; + description + "IPv6 destination prefix."; + } + leaf description { + type string; + description + "Textual description of the route."; + } + container next-hop { + description + "Configuration of next-hop."; + uses rt:next-hop-content { + augment "next-hop-options" { + description + "Augment 'next-hop-options' in IPv6 static routes."; + leaf next-hop-address { + type inet:ipv6-address; + description + "IPv6 address of the next-hop."; + } + } + } + } + } + } + } + + /* RPC operations */ + + augment "/rt:fib-route/rt:input/rt:destination-address" { + when "rt:address-family='v6ur:ipv6-unicast'" { + description + "This augment is valid only for IPv6 unicast."; + } + description + "This leaf augments the 'rt:destination-address' parameter of + the 'rt:fib-route' operation."; + leaf address { + type inet:ipv6-address; + description + "IPv6 destination address."; + } + } + + augment "/rt:fib-route/rt:output/rt:route" { + when "rt:address-family='v6ur:ipv6-unicast'" { + description + "This augment is valid only for IPv6 unicast."; + } + description + "This leaf augments the reply to the 'rt:fib-route' + operation."; + leaf destination-prefix { + type inet:ipv6-prefix; + description + "IPv6 destination prefix."; + } + + } + + augment "/rt:fib-route/rt:output/rt:route/rt:next-hop/" + + "rt:next-hop-options" { + when "../rt:address-family='v6ur:ipv6-unicast'" { + description + "This augment is valid only for IPv6 unicast."; + } + description + "Augment 'next-hop-options' in the reply to the 'rt:fib-route' + operation."; + leaf next-hop-address { + type inet:ipv6-address; + description + "IPv6 address of the next-hop."; + } + } + } + + + +9.1. IPv6 Router Advertisements Submodule + + 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-router-advertisements@2016-03-09.yang" + + submodule ietf-ipv6-router-advertisements { + + belongs-to ietf-ipv6-unicast-routing { + prefix "v6ur"; + } + + import ietf-inet-types { + prefix "inet"; + } + + import ietf-interfaces { + prefix "if"; + } + + import ietf-ip { + prefix "ip"; + } + + organization + "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; + + contact + "WG Web: + WG List: + + WG Chair: Lou Berger + + + WG Chair: Juergen Schoenwaelder + + + WG Chair: Kent Watsen + + + Editor: Ladislav Lhotka + + + Editor: Acee Lindem + "; + + description + "This YANG module augments the 'ietf-ip' module with + configuration and state data of IPv6 router advertisements. + + Copyright (c) 2016 IETF Trust and the persons identified as + authors of the code. All rights reserved. + + Redistribution and use in source and binary forms, with or + without modification, is permitted pursuant to, and subject to + the license terms contained in, the Simplified BSD License set + forth in Section 4.c of the IETF Trust's Legal Provisions + Relating to IETF Documents + (http://trustee.ietf.org/license-info). + + The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL + NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and + 'OPTIONAL' in the module text are to be interpreted as described + in RFC 2119 (http://tools.ietf.org/html/rfc2119). + + This version of this YANG module is part of RFC XXXX + (http://tools.ietf.org/html/rfcXXXX); see the RFC itself for + full legal notices."; + + reference + "RFC 4861: Neighbor Discovery for IP version 6 (IPv6)."; + + revision 2016-03-09 { + description + "Initial revision."; + reference + "RFC XXXX: A YANG Data Model for Routing Management"; + } + + /* State data */ + augment "/if:interfaces-state/if:interface/ip:ipv6" { description - "Augment interface state data with IPv6-specific parameters of - router interfaces."; + "Augment interface state data with parameters of IPv6 router + advertisements."; container ipv6-router-advertisements { description "Parameters of IPv6 Router Advertisements."; leaf send-advertisements { type boolean; description "A flag indicating whether or not the router sends periodic Router Advertisements and responds to Router Solicitations."; } @@ -1783,55 +1804,26 @@ type boolean; description "The value that is placed in the Autonomous Flag field in the Prefix Information option."; } } } } } - augment "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/" - + "rt:routes/rt:route" { - when "../../rt:address-family = 'v6ur:ipv6-unicast'" { - description - "This augment is valid only for IPv6 unicast."; - } - description - "This leaf augments an IPv6 unicast route."; - leaf destination-prefix { - type inet:ipv6-prefix; - description - "IPv6 destination prefix."; - } - } - - augment "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/" - + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options" { - when "../../../rt:address-family = 'v6ur:ipv6-unicast'" { - description - "This augment is valid only for IPv6 unicast."; - } - description - "Augment 'next-hop-options' in IPv6 unicast routes."; - leaf next-hop-address { - type inet:ipv6-address; - description - "IPv6 address of the next-hop."; - } - } - /* Configuration data */ + augment "/if:interfaces/if:interface/ip:ipv6" { description - "Augment interface configuration with IPv6-specific parameters - of router interfaces."; + "Augment interface configuration with parameters of IPv6 router + advertisements."; container ipv6-router-advertisements { description "Configuration of IPv6 Router Advertisements."; leaf send-advertisements { type boolean; default "false"; description "A flag indicating whether or not the router sends periodic Router Advertisements and responds to Router Solicitations."; @@ -2055,120 +2047,26 @@ leaf autonomous-flag { type boolean; default "true"; description "The value to be placed in the Autonomous Flag field in the Prefix Information option."; reference "RFC 4861: Neighbor Discovery for IP version 6 (IPv6) - AdvAutonomousFlag."; } - } } } } } } - - augment "/rt:routing/rt:routing-instance/rt:routing-protocols/" - + "rt:routing-protocol/rt:static-routes" { - description - "This augment defines the configuration of the 'static' - pseudo-protocol with data specific to IPv6 unicast."; - container ipv6 { - description - "Configuration of a 'static' pseudo-protocol instance - consists of a list of routes."; - list route { - key "destination-prefix"; - description - "A list of static routes."; - leaf destination-prefix { - type inet:ipv6-prefix; - mandatory "true"; - description - "IPv6 destination prefix."; - } - leaf description { - type string; - description - "Textual description of the route."; - } - container next-hop { - description - "Configuration of next-hop."; - uses rt:next-hop-content { - augment "next-hop-options" { - description - "Augment 'next-hop-options' in IPv6 static routes."; - leaf next-hop-address { - type inet:ipv6-address; - description - "IPv6 address of the next-hop."; - } - } - } - } - } - } - - } - - /* RPC operations */ - - augment "/rt:fib-route/rt:input/rt:destination-address" { - when "rt:address-family='v6ur:ipv6-unicast'" { - description - "This augment is valid only for IPv6 unicast."; - } - description - "This leaf augments the 'rt:destination-address' parameter of - the 'rt:fib-route' operation."; - leaf address { - type inet:ipv6-address; - description - "IPv6 destination address."; - } - } - - augment "/rt:fib-route/rt:output/rt:route" { - when "rt:address-family='v6ur:ipv6-unicast'" { - description - "This augment is valid only for IPv6 unicast."; - } - description - "This leaf augments the reply to the 'rt:fib-route' - operation."; - leaf destination-prefix { - type inet:ipv6-prefix; - description - "IPv6 destination prefix."; - } - } - - augment "/rt:fib-route/rt:output/rt:route/rt:next-hop/" - + "rt:next-hop-options" { - when "../rt:address-family='v6ur:ipv6-unicast'" { - description - "This augment is valid only for IPv6 unicast."; - } - description - "Augment 'next-hop-options' in the reply to the 'rt:fib-route' - operation."; - leaf next-hop-address { - type inet:ipv6-address; - description - "IPv6 address of the next-hop."; - } - - } } 10. IANA Considerations RFC Ed.: In this section, replace all occurrences of 'XXXX' with the actual RFC number (and remove this note). This document registers the following namespace URIs in the IETF XML @@ -2215,20 +2112,29 @@ reference: RFC XXXX -------------------------------------------------------------------- -------------------------------------------------------------------- name: ietf-ipv6-unicast-routing namespace: urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing prefix: v6ur reference: RFC XXXX -------------------------------------------------------------------- + This document registers the following YANG submodule in the YANG + Module Names registry [RFC6020]: + + -------------------------------------------------------------------- + name: ietf-ipv6-router-advertisements + parent: ietf-ipv6-unicast-routing + reference: RFC XXXX + -------------------------------------------------------------------- + 11. Security Considerations Configuration and state data conforming to the core routing data model (defined in this document) are designed to be accessed via the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the secure transport layer and the mandatory-to-implement secure transport is SSH [RFC6242]. The NETCONF access control model [RFC6536] provides the means to restrict access for particular NETCONF users to a pre- configured subset of all available NETCONF protocol operations and content. @@ -2237,28 +2143,25 @@ 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" parameters and subtrees are the following: - /if:interfaces/if:interface/rt:routing-instance: This leaf assigns a - network layer interface to a routing instance. - - /routing/routing-instance/routing-protocols/routing-protocol: This - list specifies the routing protocols configured on a device. + /routing/routing-protocols/routing-protocol: This list specifies the + routing protocols configured on a device. - /routing/routing-instance/ribs/rib: This list specifies the RIBs - configured for the device. + /routing/ribs/rib: This list specifies the RIBs configured for the + device. Unauthorised access to any of these lists can adversely affect the routing subsystem of both the local device and the network. This may lead to network malfunctions, delivery of packets to inappropriate destinations and other problems. 12. Acknowledgments The authors wish to thank Nitin Bahadur, Martin Bjorklund, Dean Bogdanovic, Jeff Haas, Joel Halpern, Wes Hardaker, Sriganesh Kini, @@ -2266,22 +2169,22 @@ 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, DOI 10.17487/ - RFC2119, March 1997, + Requirement Levels", BCP 14, RFC 2119, + DOI 10.17487/RFC2119, March 1997, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, DOI 10.17487/RFC4861, September 2007, . @@ -2289,171 +2192,169 @@ [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, October 2010, . [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, . - [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC - 6991, DOI 10.17487/RFC6991, July 2013, + [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", + RFC 6991, DOI 10.17487/RFC6991, July 2013, . [RFC7223] Bjorklund, M., "A YANG Data Model for Interface Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, . - [RFC7277] Bjorklund, M., "A YANG Data Model for IP Management", RFC - 7277, DOI 10.17487/RFC7277, June 2014, + [RFC7277] Bjorklund, M., "A YANG Data Model for IP Management", + RFC 7277, DOI 10.17487/RFC7277, June 2014, . 13.2. Informative References - [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private - Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February - 2006, . - [RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG Data Model Documents", RFC 6087, DOI 10.17487/RFC6087, January 2011, . [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, . [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration - Protocol (NETCONF) Access Control Model", RFC 6536, DOI - 10.17487/RFC6536, March 2012, + Protocol (NETCONF) Access Control Model", RFC 6536, + DOI 10.17487/RFC6536, March 2012, . + [RFC7224] Bjorklund, M., "IANA Interface Type YANG Module", + RFC 7224, DOI 10.17487/RFC7224, May 2014, + . + Appendix A. The Complete Data Trees This appendix presents the complete configuration and state data trees of the core routing data model. See Section 2.2 for an explanation of the symbols used. Data type of every leaf node is shown near the right end of the corresponding line. A.1. Configuration Data +--rw routing - +--rw routing-instance* [name] - +--rw name string - +--rw type? identityref - +--rw enabled? boolean +--rw router-id? yang:dotted-quad - +--rw description? string +--rw routing-protocols | +--rw routing-protocol* [type name] | +--rw type identityref | +--rw name string | +--rw description? string | +--rw static-routes - | +--rw v6ur:ipv6 - | | +--rw v6ur:route* [destination-prefix] - | | +--rw v6ur:destination-prefix inet:ipv6-prefix - | | +--rw v6ur:description? string - | | +--rw v6ur:next-hop - | | +--rw (next-hop-options) - | | +--:(outgoing-interface) - | | | +--rw v6ur:outgoing-interface? - | | +--:(special-next-hop) - | | | +--rw v6ur:special-next-hop? - | | +--:(next-hop-address) - | | +--rw v6ur:next-hop-address? - | +--rw v4ur:ipv4 - | +--rw v4ur:route* [destination-prefix] - | +--rw v4ur:destination-prefix inet:ipv4-prefix - | +--rw v4ur:description? string - | +--rw v4ur:next-hop - | +--rw (next-hop-options) - | +--:(outgoing-interface) - | | +--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* [destination-prefix] + | | | +--rw v6ur:destination-prefix inet:ipv6-prefix + | | | +--rw v6ur:description? string + | | | +--rw v6ur:next-hop + | | | +--rw (v6ur:next-hop-options) + | | | +--:(v6ur:outgoing-interface) + | | | | +--rw v6ur:outgoing-interface? if:interface-ref + | | | +--:(v6ur:special-next-hop) + | | | | +--rw v6ur:special-next-hop? enumeration + | | | +--:(v6ur:next-hop-address) + | | | +--rw v6ur:next-hop-address? inet:ipv6-address + | | +--rw v4ur:ipv4 + | | +--rw v4ur:route* [destination-prefix] + | | +--rw v4ur:destination-prefix inet:ipv4-prefix + | | +--rw v4ur:description? string + | | +--rw v4ur:next-hop + | | +--rw (v4ur:next-hop-options) + | | +--:(v4ur:outgoing-interface) + | | | +--rw v4ur:outgoing-interface? if:interface-ref + | | +--:(v4ur:special-next-hop) + | | | +--rw v4ur:special-next-hop? enumeration + | | +--:(v4ur:next-hop-address) + | | +--rw v4ur:next-hop-address? inet:ipv4-address + | +--rw rip:rip! + | +--rw rip:interfaces + | | +--rw rip:interface* [name] + | | +--rw rip:name if:interface-ref + | | +--rw rip:enabled? boolean + | | +--rw rip:metric? rip-metric + | +--rw rip:update-interval? uint8 +--rw ribs +--rw rib* [name] +--rw name string +--rw address-family? identityref +--rw description? string A.2. State Data + +--ro routing-state - +--ro routing-instance* [name] - +--ro name string - +--ro type? identityref +--ro router-id? yang:dotted-quad +--ro interfaces | +--ro interface* if:interface-state-ref +--ro routing-protocols | +--ro routing-protocol* [type name] | +--ro type identityref | +--ro name string +--ro ribs +--ro rib* [name] +--ro name string +--ro address-family identityref +--ro default-rib? boolean {multiple-ribs}? +--ro routes +--ro route* +--ro route-preference? route-preference +--ro next-hop | +--ro (next-hop-options) | +--:(outgoing-interface) - | | +--ro outgoing-interface? + | | +--ro outgoing-interface? if:interface-state-ref | +--:(special-next-hop) | | +--ro special-next-hop? enumeration - | +--:(next-hop-address) - | | +--ro v6ur:next-hop-address? - | +--:(next-hop-address) - | +--ro v4ur:next-hop-address? + | +--:(v6ur:next-hop-address) + | | +--ro v6ur:next-hop-address? inet:ipv6-address + | +--:(v4ur:next-hop-address) + | +--ro v4ur:next-hop-address? inet:ipv4-address +--ro source-protocol identityref +--ro active? empty +--ro last-updated? yang:date-and-time +--ro v6ur:destination-prefix? inet:ipv6-prefix + +--ro rip:metric? rip-metric + +--ro rip:tag? uint16 +--ro v4ur:destination-prefix? inet:ipv4-prefix Appendix B. Minimum Implementation Some parts and options of the core routing model, such as user- defined RIBs, are intended only for advanced routers. This appendix gives basic non-normative guidelines for implementing a bare minimum of available functions. Such an implementation may be used for hosts or very simple routers. - A minimum implementation provides a single system-controlled routing - instance of the type "default-routing-instance", and will not allow - clients to create any user-controlled instances. - - Typically, the feature "multiple-ribs" will not be supported. This - means that a single system-controlled RIB is available for each - supported address family - IPv4, IPv6 or both. These RIBs must be - the default RIBs. No user-controlled RIBs are allowed. + A minimum implementation does not support the feature "multiple- + ribs". This means that a single system-controlled RIB is available + for each supported address family - IPv4, IPv6 or both. These RIBs + are also the default RIBs. No user-controlled RIBs are allowed. In addition to the mandatory instance of the "direct" pseudo- protocol, a minimum implementation should support configuring instance(s) of the "static" pseudo-protocol. Platforms with severely constrained resources may use deviations for restricting the data model, e.g., limiting the number of "static" routing protocol instances. Appendix C. Example: Adding a New Routing Protocol This appendix demonstrates how the core routing data model can be extended to support a new routing protocol. The YANG module "example-rip" shown below is intended as an illustration rather than a real definition of a data model for the RIP routing protocol. For the sake of brevity, this module does not obey all the guidelines - specified in [RFC6087]. See also Section 5.4.2. + specified in [RFC6087]. See also Section 5.3.2. module example-rip { namespace "http://example.com/rip"; prefix "rip"; import ietf-interfaces { prefix "if"; } @@ -2481,41 +2384,39 @@ } leaf tag { type uint16; default "0"; description "This leaf may be used to carry additional info, e.g. AS number."; } } - augment "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/" - + "rt:routes/rt:route" { + augment "/rt:routing-state/rt:ribs/rt:rib/rt:routes/rt:route" { when "rt:source-protocol = 'rip:rip'" { description "This augment is only valid for a routes whose source protocol is RIP."; } description "RIP-specific route attributes."; uses route-content; } augment "/rt:fib-route/rt:output/rt:route" { description "RIP-specific route attributes in the output of 'active-route' RPC."; uses route-content; } - augment "/rt:routing/rt:routing-instance/rt:routing-protocols/" - + "rt:routing-protocol" { + augment "/rt:routing/rt:routing-protocols/rt:routing-protocol" { when "rt:type = 'rip:rip'" { description "This augment is only valid for a routing protocol instance of type 'rip'."; } container rip { presence "RIP configuration"; description "RIP instance configuration."; container interfaces { @@ -2555,20 +2455,22 @@ } 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 iana-if-type [RFC7224], + o ietf-ip [RFC7277], o ietf-routing (Section 7), o ietf-ipv4-unicast-routing (Section 8), o ietf-ipv6-unicast-routing (Section 9). We assume a simple network set-up as shown in Figure 3: router "A" uses static default routes with the "ISP" router as the next-hop. @@ -2611,21 +2513,20 @@ xmlns:ip="urn:ietf:params:xml:ns:yang:ietf-ip" xmlns:rt="urn:ietf:params:xml:ns:yang:ietf-routing"> eth0 ianaift:ethernetCsmacd Uplink to ISP. - rtr0 192.0.2.1 24 true 2001:0db8:0:1::1 @@ -2636,51 +2537,50 @@ false eth1 ianaift:ethernetCsmacd Interface to the internal network. - rtr0 198.51.100.1 24 true 2001:0db8:0:2::1 64 true false + + true + eth0 ianaift:ethernetCsmacd 00:0C:42:E5:B1:E9 up - rtr0 - - 2015-10-24T17:11:27+02:00 - + 2015-10-24T17:11:27+02:00 true 1500 192.0.2.1 24 @@ -2698,25 +2598,22 @@ eth1 ianaift:ethernetCsmacd 00:0C:42:E5:B1:EA up - rtr0 - - 2015-10-24T17:11:29+02:00 - + 2015-10-24T17:11:29+02:00 true 1500 198.51.100.1 24 @@ -2731,91 +2628,77 @@ 2001:db8:0:2::/64 - - rtr0 - Router A 192.0.2.1 rt:static st0 Static routing is used for the internal network. - - 0.0.0.0/0 - + 0.0.0.0/0 192.0.2.2 ::/0 - - 2001:db8:0:1::2 - + 2001:db8:0:1::2 - - - rtr0 eth0 eth1 rt:static st0 ipv4-master v4ur:ipv4-unicast true - - 192.0.2.1/24 - + 192.0.2.1/24 eth0 0 rt:direct 2015-10-24T17:11:27+02:00 - - 198.51.100.0/24 - + 198.51.100.0/24 eth1 rt:direct 0 2015-10-24T17:11:27+02:00 0.0.0.0/0 rt:static @@ -2826,86 +2709,90 @@ 2015-10-24T18:02:45+02:00 ipv6-master v6ur:ipv6-unicast true - - 2001:db8:0:1::/64 - + 2001:db8:0:1::/64 eth0 rt:direct 0 2015-10-24T17:11:27+02:00 - - 2001:db8:0:2::/64 - + 2001:db8:0:2::/64 eth1 rt:direct 0 2015-10-24T17:11:27+02:00 ::/0 - - 2001:db8:0:1::2 - + 2001:db8:0:1::2 rt:static 5 2015-10-24T18:02:45+02:00 - + + + + Appendix E. Change Log RFC Editor: Remove this section upon publication as an RFC. -E.1. Changes Between Versions -19 and -20 +E.1. Changes Between Versions -20 and -21 + + o Routing instances were removed. + + o IPv6 RA parameters were moved to the "ietf-ipv6-router- + advertisements". + +E.2. Changes Between Versions -19 and -20 o Assignment of L3 interfaces to routing instances is now part of interface configuration. o Next-hop options in configuration were aligned with state data. o It is recommended to enclose protocol-specific configuration in a presence container. -E.2. Changes Between Versions -18 and -19 +E.3. Changes Between Versions -18 and -19 o The leaf "route-preference" was removed from the "routing- protocol" container in both "routing" and "routing-state". o The "vrf-routing-instance" identity was added in support of a common routing-instance type in addition to the "default-routing- instance". o Removed "enabled" switch from "routing-protocol". -E.3. Changes Between Versions -17 and -18 +E.4. Changes Between Versions -17 and -18 o The container "ribs" was moved under "routing-instance" (in both "routing" and "routing-state"). o Typedefs "rib-ref" and "rib-state-ref" were removed. o Removed "recipient-ribs" (both state and configuration). o Removed "connected-ribs" from "routing-protocol" (both state and configuration). @@ -2917,38 +2804,38 @@ rather than list (both config and state). The opposite reference from "if:interface" to "rt:routing-instance" was changed to a single leaf (an interface cannot belong to multiple routing instances). o Specification of a default RIB is now a simple flag under "rib" (both config and state). o Default RIBs are marked by a flag in state data. -E.4. Changes Between Versions -16 and -17 +E.5. Changes Between Versions -16 and -17 o Added Acee as a co-author. o Removed all traces of route filters. o Removed numeric IDs of list entries in state data. o Removed all next-hop cases except "simple-next-hop" and "special- next-hop". o Removed feature "multipath-routes". o Augmented "ietf-interfaces" module with a leaf-list of leafrefs pointing form state data of an interface entry to the routing instance(s) to which the interface is assigned. -E.5. Changes Between Versions -15 and -16 +E.6. 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. @@ -2969,39 +2856,39 @@ o Added next-hop lists to state data. o Added two cases for specifying next-hops indirectly - via a new RIB or a recursive list of next-hops. o Reorganized next-hop in static routes. o Removed all 'if-feature' statements from state data. -E.6. Changes Between Versions -14 and -15 +E.7. Changes Between Versions -14 and -15 o Removed all defaults from state data. o Removed default from 'cur-hop-limit' in config. -E.7. Changes Between Versions -13 and -14 +E.8. 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.8. Changes Between Versions -12 and -13 +E.9. Changes Between Versions -12 and -13 o Wrote appendix about minimum implementation. o Remove "when" statement for IPv6 router interface state data - it was dependent on a config value that may not be present. o Extra container for the next-hop list. o Names rather than numeric ids are used for referring to list entries in state data. @@ -3014,34 +2901,34 @@ o o Removed "if-feature multiple-ribs;" from connected-ribs. o "rib-name" instead of "name" is used as the name of leafref nodes. o "next-hop" instead of "nexthop" or "gateway" used throughout, both in node names and text. -E.9. Changes Between Versions -11 and -12 +E.10. 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.10. Changes Between Versions -10 and -11 +E.11. 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- @@ -3051,70 +2938,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.11. Changes Between Versions -09 and -10 +E.12. Changes Between Versions -09 and -10 o Added subtree for state data ("/routing-state"). o Terms "system-controlled entry" and "user-controlled entry" defined and used. o New feature "user-defined-routing-tables". Nodes that are useful only with user-defined routing tables are now conditional. o Added grouping "router-id". o In routing tables, "source-protocol" attribute of routes now reports only protocol type, and its datatype is "identityref". o Renamed "main-routing-table" to "default-routing-table". -E.12. Changes Between Versions -08 and -09 +E.13. Changes Between Versions -08 and -09 o Fixed "must" expression 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.13. Changes Between Versions -07 and -08 +E.14. Changes Between Versions -07 and -08 o Changed reference from RFC6021 to RFC6021bis. -E.14. Changes Between Versions -06 and -07 +E.15. 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.15. Changes Between Versions -05 and -06 +E.16. 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". @@ -3122,21 +3009,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.16. Changes Between Versions -04 and -05 +E.17. 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 @@ -3157,35 +3044,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.17. Changes Between Versions -03 and -04 +E.18. Changes Between Versions -03 and -04 o Changed "error-tag" for both RPC operations from "missing element" to "data-missing". o Removed the decrementing behavior for advertised IPv6 prefix parameters "valid-lifetime" and "preferred-lifetime". o Changed the key of the static route lists from "seqno" to "id" because the routes needn't be sorted. o Added 'must' constraint saying that "preferred-lifetime" must not be greater than "valid-lifetime". -E.18. Changes Between Versions -02 and -03 +E.19. 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". @@ -3203,21 +3090,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.19. Changes Between Versions -01 and -02 +E.20. 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. @@ -3227,21 +3114,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.20. Changes Between Versions -00 and -01 +E.21. 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.