--- 1/draft-ietf-netmod-routing-cfg-19.txt 2015-10-16 09:15:49.042609311 -0700 +++ 2/draft-ietf-netmod-routing-cfg-20.txt 2015-10-16 09:15:49.310615835 -0700 @@ -1,19 +1,19 @@ NETMOD Working Group L. Lhotka Internet-Draft CZ.NIC Intended status: Standards Track A. Lindem -Expires: November 26, 2015 Cisco Systems - May 25, 2015 +Expires: April 18, 2016 Cisco Systems + October 16, 2015 A YANG Data Model for Routing Management - draft-ietf-netmod-routing-cfg-19 + draft-ietf-netmod-routing-cfg-20 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, @@ -27,21 +27,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on November 26, 2015. + This Internet-Draft will expire on April 18, 2016. Copyright Notice Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -55,81 +55,83 @@ 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 . . . 8 5. Basic Building Blocks . . . . . . . . . . . . . . . . . . . . 8 - 5.1. Routing Instance . . . . . . . . . . . . . . . . . . . . 9 - 5.1.1. Parameters of IPv6 Routing Instance Interfaces . . . 9 + 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 . . . . . . . . . . . . . . . . . . . . 12 + 5.4. Routing Protocol . . . . . . . . . . . . . . . . . . . . 11 5.4.1. Routing Pseudo-Protocols . . . . . . . . . . . . . . 12 5.4.2. Defining New Routing Protocols . . . . . . . . . . . 12 5.5. RPC Operations . . . . . . . . . . . . . . . . . . . . . 13 6. Interactions with Other YANG Modules . . . . . . . . . . . . 13 6.1. Module "ietf-interfaces" . . . . . . . . . . . . . . . . 13 - 6.2. Module "ietf-ip" . . . . . . . . . . . . . . . . . . . . 14 + 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 . . . . . . . . . . . . . . . . . . . 48 + 11. Security Considerations . . . . . . . . . . . . . . . . . . . 47 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 48 - 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 49 - 13.1. Normative References . . . . . . . . . . . . . . . . . . 49 + 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 48 + 13.1. Normative References . . . . . . . . . . . . . . . . . . 48 13.2. Informative References . . . . . . . . . . . . . . . . . 49 - Appendix A. The Complete Data Trees . . . . . . . . . . . . . . 50 - A.1. Configuration Data . . . . . . . . . . . . . . . . . . . 50 - A.2. State Data . . . . . . . . . . . . . . . . . . . . . . . 52 - Appendix B. Minimum Implementation . . . . . . . . . . . . . . . 52 - Appendix C. Example: Adding a New Routing Protocol . . . . . . . 53 - Appendix D. Example: NETCONF Reply . . . . . . . . . . . . 55 - Appendix E. Change Log . . . . . . . . . . . . . . . . . . . . . 62 - E.1. Changes Between Versions -18 and -19 . . . . . . . . . . 62 - E.2. Changes Between Versions -17 and -18 . . . . . . . . . . 62 - E.3. Changes Between Versions -16 and -17 . . . . . . . . . . 63 - E.4. Changes Between Versions -15 and -16 . . . . . . . . . . 63 - E.5. Changes Between Versions -14 and -15 . . . . . . . . . . 64 - E.6. Changes Between Versions -13 and -14 . . . . . . . . . . 64 - E.7. Changes Between Versions -12 and -13 . . . . . . . . . . 64 - E.8. Changes Between Versions -11 and -12 . . . . . . . . . . 65 - E.9. Changes Between Versions -10 and -11 . . . . . . . . . . 65 - E.10. Changes Between Versions -09 and -10 . . . . . . . . . . 66 - E.11. Changes Between Versions -08 and -09 . . . . . . . . . . 66 - E.12. Changes Between Versions -07 and -08 . . . . . . . . . . 66 - E.13. Changes Between Versions -06 and -07 . . . . . . . . . . 66 - E.14. Changes Between Versions -05 and -06 . . . . . . . . . . 67 - E.15. Changes Between Versions -04 and -05 . . . . . . . . . . 67 - E.16. Changes Between Versions -03 and -04 . . . . . . . . . . 68 - E.17. Changes Between Versions -02 and -03 . . . . . . . . . . 68 - E.18. Changes Between Versions -01 and -02 . . . . . . . . . . 69 - E.19. Changes Between Versions -00 and -01 . . . . . . . . . . 69 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 70 + Appendix A. The Complete Data Trees . . . . . . . . . . . . . . 49 + A.1. Configuration Data . . . . . . . . . . . . . . . . . . . 49 + 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 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]. + module with additional data specific to IPv6 unicast. It 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 @@ -150,26 +152,34 @@ o protocol operation, o server. The following terms are defined in [RFC6020]: o augment, o configuration data, + o container, + + o container with presence, + o data model, o data node, o feature, + o leaf, + + o list, + o mandatory node, o module, o schema tree, o state data, o RPC operation. @@ -192,22 +202,20 @@ 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: - 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), "ro" state data (read-only), "-x" RPC operations, and "-n" notifications. o Symbols after data node names: "?" means an optional node, "!" a @@ -276,22 +284,20 @@ 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 interfaces - | +--rw interface* +--rw routing-protocols | +--rw routing-protocol* [type name] | +--rw type | +--rw name | +--rw description? | +--rw static-routes | ... +--rw ribs +--rw rib* [name] +--rw name @@ -338,24 +344,24 @@ state" container. Additional entries may be created in the configuration by a client, e.g., via the NETCONF protocol. These are so-called user-controlled entries. If the server accepts a configured user-controlled entry, then this entry also appears in the state data version of the list. Corresponding entries in both versions of the list (in state data and configuration) have the same value of the list key. - The user may also provide supplemental configuration of system- - controlled entries. To do so, the user creates a new entry in the + 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 - with the corresponding entry in the state data list, the key of the + 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 @@ -376,61 +382,58 @@ 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 - support a single routing instance of this type. + 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). - Each network layer interface has to be assigned to one or more - routing instances in order to be able to participate in packet - forwarding, routing protocols and other operations of those routing - instances. The assignment is accomplished by placing a corresponding - (system- or user-controlled) entry in the leaf-list of routing - instance interfaces ("rt:interface"). Each entry is the name of a - configured network layer interface, see the "ietf-interfaces" - module [RFC7223]. + 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 Routing Instance Interfaces +5.1.1. Parameters of IPv6 Router Interfaces YANG module "ietf-ipv6-unicast-routing" (Section 9) augments the - configuration and state data of interfaces with definitions of the - following variables as required by [RFC4861], sec. 6.2.1: + 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: @@ -562,30 +565,29 @@ /rt:fib-route/rt:output/rt:route, and possibly other places in the configuration, state data, notifications, and RPC input or output. o Configuration parameters and/or state data for the new protocol can be defined by augmenting the "routing-protocol" data node under both "/routing" and "/routing-state". - o Per-interface configuration, including activation of the routing - protocol on individual interfaces, can use references to entries - in the leaf-list of routing instance's interfaces (rt:interface). - - By using the "when" statement, the augmented configuration parameters + By using a "when" statement, the augmented configuration parameters and state data specific to the new protocol SHOULD be made conditional and valid only if the value of "rt:type" or "rt:source- - protocol" is equal to the new protocol's identity. It is also - RECOMMENDED that protocol-specific data nodes be encapsulated in - appropriately named containers. + 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 The "ietf-routing" module defines one RPC operation: o fib-route: query a routing instance for the active route in the Forwarding Information Base (FIB). It is the route that is @@ -596,79 +598,80 @@ 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. + then all routing and forwarding functions MUST be disabled on that + interface. 6.2. Module "ietf-ip" The following boolean switches are defined in the "ietf-ip" YANG 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. + then all IPv4 routing and forwarding functions MUST be disabled on + that interface. /if:interfaces/if:interface/ip:ipv4/ip:forwarding If this switch is set to "false" for a network layer interface, - then the forwarding of IPv4 datagrams to and from this interface - MUST be disabled. However, the interface may participate in other - IPv4 routing functions, such as routing protocols. + then the forwarding of IPv4 datagrams through this interface MUST + be disabled. However, the interface MAY participate in other IPv4 + routing functions, such as routing protocols. /if:interfaces/if:interface/ip:ipv6/ip:enabled If this switch is set to "false" for a network layer interface, - then all IPv6 routing functions related to that interface MUST be - disabled. + then all IPv6 routing and forwarding functions MUST be disabled on + that interface. /if:interfaces/if:interface/ip:ipv6/ip:forwarding If this switch is set to "false" for a network layer interface, - then the forwarding of IPv6 datagrams to and from this interface - MUST be disabled. However, the interface may participate in other - IPv6 routing functions, such as routing protocols. + then the forwarding of IPv6 datagrams through this interface MUST + be disabled. However, the interface MAY participate in other IPv6 + routing functions, such as routing protocols. 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 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-05-25.yang" + file "ietf-routing@2015-10-16.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 @@ -674,47 +677,50 @@ contact "WG Web: WG List: WG Chair: Thomas Nadeau WG Chair: Juergen Schoenwaelder + WG Chair: Kent Watsen + + Editor: Ladislav Lhotka "; description "This YANG module defines essential components for the management of a routing subsystem. - Copyright (c) 2014 IETF Trust and the persons identified as + Copyright (c) 2015 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-05-25 { + revision 2015-10-16 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for Routing Management"; } /* Features */ feature multiple-ribs { description @@ -888,72 +894,58 @@ } grouping next-hop-content { description "Generic parameters of next-hops in static routes."; choice next-hop-options { mandatory "true"; description "Options for next-hops in static routes. - It is expected that other cases will be added through + Modules for address families MUST augment this choice with + the 'next-hop-address' case, which is a leaf containing a + gateway address of that address family. + + It is expected that further cases will be added through augments from other modules, e.g., for Equal-Cost Multipath routing (ECMP)."; - case simple-next-hop { - description - "Simple next-hop is specified as an outgoing interface, - next-hop address or both. - - Address-family-specific modules are expected to provide - 'next-hop-address' leaf via augmentation."; leaf outgoing-interface { - type leafref { - path "/rt:routing/rt:routing-instance/rt:interfaces/" - + "rt:interface"; - } + type if:interface-ref; description "Name of the outgoing interface."; } - } case special-next-hop { uses special-next-hop; } } } grouping next-hop-state-content { description "Generic parameters of next-hops in state data."; choice next-hop-options { mandatory "true"; description "Options for next-hops in state data. - It is expected that other cases will be added through + Modules for address families MUST augment this choice with + the 'next-hop-address' case, which is a leaf containing a + gateway address of that address family. + + It is expected that further cases will be added through augments from other modules, e.g., for ECMP or recursive next-hops."; - case simple-next-hop { - description - "Simple next-hop is specified as an outgoing interface, - next-hop address or both. - - Address-family-specific modules are expected to provide - 'next-hop-address' leaf via augmentation."; leaf outgoing-interface { - type leafref { - path "/rt:routing-state/rt:routing-instance/" - + "rt:interfaces/rt:interface"; - } + type if:interface-state-ref; description "Name of the outgoing interface."; } - } case special-next-hop { uses special-next-hop; } } } grouping route-metadata { description "Common route metadata."; leaf source-protocol { @@ -978,66 +970,54 @@ "Time stamp of the last modification of the route. If the route was never modified, it is the time when the route was inserted into the RIB."; } } /* State data */ augment "/if:interfaces-state/if:interface" { description - "This augment adds a wrapped leaf-list to interface state - data."; + "This augment adds a reference to the routing-instance to which + the interface is assigned."; leaf routing-instance { type routing-instance-state-ref; - must "../if:name=/rt:routing-state/" - + "rt:routing-instance[rt:name=current()]/rt:interfaces/" - + "rt:interface" { - error-message - "The interface is not assigned to the routing instance."; - description - "The reference must mirror a corresponding assignment under - routing-instance."; - } description "The name of the routing instance to which the interface is assigned."; } } container routing-state { config "false"; description "State data of the routing subsystem."; list routing-instance { key "name"; min-elements "1"; description "Each list entry is a container for state data of a routing instance. - An implementation MUST support routing instance(s) of the - type 'rt:default-routing-instance', and MAY support other - types. An implementation MAY restrict the number of routing - instances of each supported type. + An implementation 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 SHOULD create at least one - system-controlled instance, and MAY allow the clients to - create user-controlled routing instances in - configuration."; + 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 is persistent, - i.e., it SHOULD NOT change across reboots."; + 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 @@ -1045,20 +1025,29 @@ It may be either configured or assigned algorithmically by the implementation."; } container interfaces { description "Network layer interfaces belonging to the routing instance."; leaf-list interface { type if:interface-state-ref; + 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"; @@ -1143,20 +1131,35 @@ 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 @@ -1192,30 +1195,20 @@ description "Configuration of the global router ID. Routing protocols that use router ID can use this parameter or override it with another value."; } leaf description { type string; description "Textual description of the routing instance."; } - container interfaces { - description - "Assignment of the routing instance's interfaces."; - leaf-list interface { - type if:interface-ref; - description - "The name of a configured network layer interface to be - assigned to the routing-instance."; - } - } container routing-protocols { description "Configuration of routing protocol instances."; list routing-protocol { key "type name"; description "Each entry contains configuration of a routing protocol instance."; leaf type { type identityref { @@ -1351,21 +1344,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-05-25.yang" + file "ietf-ipv4-unicast-routing@2015-10-16.yang" module ietf-ipv4-unicast-routing { namespace "urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing"; prefix "v4ur"; import ietf-routing { prefix "rt"; } @@ -1379,54 +1373,58 @@ contact "WG Web: WG List: WG Chair: Thomas Nadeau WG Chair: Juergen Schoenwaelder + WG Chair: Kent Watsen + + Editor: Ladislav Lhotka "; description "This YANG module augments the 'ietf-routing' module with basic configuration and state data for IPv4 unicast routing. - Copyright (c) 2014 IETF Trust and the persons identified as + Copyright (c) 2015 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-05-25 { + revision 2015-10-16 { 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" { @@ -1437,70 +1435,67 @@ description "This leaf augments an IPv4 unicast route."; leaf destination-prefix { type inet:ipv4-prefix; description "IPv4 destination prefix."; } } augment "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/" - + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/" - + "rt:simple-next-hop" { + + "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 - "This leaf augments the 'simple-next-hop' case of IPv4 unicast - routes."; + "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" { description "This augment defines the configuration of the 'static' pseudo-protocol with data specific to IPv4 unicast."; container ipv4 { description "Configuration of a 'static' pseudo-protocol instance consists of a list of routes."; list route { key "destination-prefix"; - ordered-by "user"; description - "A user-ordered list of static routes."; + "A list of static routes."; leaf destination-prefix { type inet:ipv4-prefix; mandatory "true"; description "IPv4 destination prefix."; } leaf description { type string; description "Textual description of the route."; } container next-hop { description "Configuration of next-hop."; uses rt:next-hop-content { augment "next-hop-options" { description - "Add next-hop address case."; + "Augment 'next-hop-options' in IPv4 static routes."; leaf next-hop-address { type inet:ipv4-address; description "IPv4 address of the next-hop."; } } } } } } @@ -1530,48 +1524,50 @@ "This augment is valid only for IPv4 unicast."; } description "This leaf augments the reply to the 'rt:fib-route' operation."; leaf destination-prefix { type inet:ipv4-prefix; description "IPv4 destination prefix."; } + } augment "/rt:fib-route/rt:output/rt:route/rt:next-hop/" - + "rt:next-hop-options/rt:simple-next-hop" { + + "rt:next-hop-options" { when "../rt:address-family='v4ur:ipv4-unicast'" { description "This augment is valid only for IPv4 unicast."; } description - "This leaf augments the 'simple-next-hop' case in the reply to - the 'rt:fib-route' operation."; + "Augment 'next-hop-options' in the reply to 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 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-05-25.yang" + file "ietf-ipv6-unicast-routing@2015-10-16.yang" + module ietf-ipv6-unicast-routing { namespace "urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing"; prefix "v6ur"; import ietf-routing { prefix "rt"; } @@ -1593,49 +1589,53 @@ contact "WG Web: WG List: WG Chair: Thomas Nadeau WG Chair: Juergen Schoenwaelder + WG Chair: Kent Watsen + + Editor: Ladislav Lhotka "; description "This YANG module augments the 'ietf-routing' module with basic configuration and state data for IPv6 unicast routing. - Copyright (c) 2014 IETF Trust and the persons identified as + Copyright (c) 2015 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-05-25 { + revision 2015-10-16 { 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."; @@ -1797,39 +1797,37 @@ "This augment is valid only for IPv6 unicast."; } description "This leaf augments an IPv6 unicast route."; leaf destination-prefix { type inet:ipv6-prefix; description "IPv6 destination prefix."; } } + augment "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/" - + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/" - + "rt:simple-next-hop" { + + "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 - "This leaf augments the 'simple-next-hop' case of IPv6 unicast - routes."; + "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."; container ipv6-router-advertisements { description "Configuration of IPv6 Router Advertisements."; leaf send-advertisements { type boolean; default "false"; @@ -2074,41 +2074,40 @@ + "rt:routing-protocol/rt:static-routes" { description "This augment defines the configuration of the 'static' pseudo-protocol with data specific to IPv6 unicast."; container ipv6 { description "Configuration of a 'static' pseudo-protocol instance consists of a list of routes."; list route { key "destination-prefix"; - ordered-by "user"; description - "A user-ordered list of static routes."; + "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 - "Add next-hop address case."; + "Augment 'next-hop-options' in IPv6 static routes."; leaf next-hop-address { type inet:ipv6-address; description "IPv6 address of the next-hop."; } } } } } } @@ -2140,33 +2140,34 @@ "This leaf augments the reply to the 'rt:fib-route' operation."; leaf destination-prefix { type inet:ipv6-prefix; description "IPv6 destination prefix."; } } augment "/rt:fib-route/rt:output/rt:route/rt:next-hop/" - + "rt:next-hop-options/rt:simple-next-hop" { + + "rt:next-hop-options" { when "../rt:address-family='v6ur:ipv6-unicast'" { description "This augment is valid only for IPv6 unicast."; } description - "This leaf augments the 'simple-next-hop' case in the reply to - the 'rt:fib-route' operation."; + "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). @@ -2233,136 +2234,146 @@ 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. - The vulnerable "config true" subtrees and data nodes are the + The vulnerable "config true" parameters and subtrees 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. + /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-instance/ribs/rib: This list specifies the RIBs configured for the device. - Unauthorized access to any of these lists can adversely affect the + 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, David Lamparter, Andrew McGregor, Jan Medved, Xiang Li, Stephane Litkowski, Thomas Morin, Tom Petch, Bruno Rijsman, Juergen Schoenwaelder, Phil Shafer, Dave Thaler, Yi Yang, Derek Man- Kit Yeung and Jeffrey Zhang for their helpful comments and suggestions. 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. + Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ + RFC2119, March 1997, + . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, - January 2004. + 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, - September 2007. + DOI 10.17487/RFC4861, September 2007, + . - [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the - Network Configuration Protocol (NETCONF)", RFC 6020, - October 2010. + [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., Bjorklund, M., Schoenwaelder, J., and A. - Bierman, "Network Configuration Protocol (NETCONF)", RFC - 6241, June 2011. + [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., "Common YANG Data Types", RFC 6991, - 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, May 2014. + Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, + . [RFC7277] Bjorklund, M., "A YANG Data Model for IP Management", RFC - 7277, June 2014. + 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, February 2006. + 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, January 2011. + Data Model Documents", RFC 6087, DOI 10.17487/RFC6087, + January 2011, . [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure - Shell (SSH)", RFC 6242, June 2011. + 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, March - 2012. + Protocol (NETCONF) Access Control Model", RFC 6536, DOI + 10.17487/RFC6536, March 2012, + . Appendix A. The Complete Data Trees This appendix presents the complete configuration and state data trees of the core routing data model. See Section 2.2 for an explanation of the symbols used. Data type of every leaf node is shown near the right end of the corresponding line. 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 interfaces - | +--rw interface* if:interface-ref +--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 + | | +--rw v6ur:destination-prefix inet:ipv6-prefix | | +--rw v6ur:description? string | | +--rw v6ur:next-hop | | +--rw (next-hop-options) - | | +--:(simple-next-hop) + | | +--:(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 + | +--rw v4ur:destination-prefix inet:ipv4-prefix | +--rw v4ur:description? string | +--rw v4ur:next-hop | +--rw (next-hop-options) - | +--:(simple-next-hop) + | +--:(outgoing-interface) | | +--rw v4ur:outgoing-interface? | +--:(special-next-hop) | | +--rw v4ur:special-next-hop? | +--:(next-hop-address) | +--rw v4ur:next-hop-address? +--rw ribs +--rw rib* [name] +--rw name string +--rw address-family? identityref +--rw description? string @@ -2383,43 +2393,45 @@ +--ro ribs +--ro rib* [name] +--ro name string +--ro address-family identityref +--ro default-rib? boolean {multiple-ribs}? +--ro routes +--ro route* +--ro route-preference? route-preference +--ro next-hop | +--ro (next-hop-options) - | +--:(simple-next-hop) + | +--:(outgoing-interface) | | +--ro outgoing-interface? - | | +--ro v6ur:next-hop-address? - | | +--ro v4ur:next-hop-address? | +--:(special-next-hop) - | +--ro special-next-hop? enumeration + | | +--ro special-next-hop? enumeration + | +--:(next-hop-address) + | | +--ro v6ur:next-hop-address? + | +--:(next-hop-address) + | +--ro v4ur:next-hop-address? +--ro source-protocol identityref +--ro active? empty +--ro last-updated? yang:date-and-time +--ro v6ur:destination-prefix? inet:ipv6-prefix +--ro v4ur:destination-prefix? inet:ipv4-prefix Appendix B. Minimum Implementation Some parts and options of the core routing model, such as user- - defined routing tables, are intended only for advanced routers. This - appendix gives basic non-normative guidelines for implementing a bare - minimum of available functions. Such an implementation may be used - for hosts or very simple routers. + 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 will provide a single system-controlled - routing instance of the type "default-routing-instance", and will not - allow clients to create any user-controlled instances. + 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. In addition to the mandatory instance of the "direct" pseudo- protocol, a minimum implementation should support configuring instance(s) of the "static" pseudo-protocol. @@ -2435,20 +2447,24 @@ a real definition of a data model for the RIP routing protocol. For the sake of brevity, this module does not obey all the guidelines specified in [RFC6087]. See also Section 5.4.2. module example-rip { namespace "http://example.com/rip"; prefix "rip"; + import ietf-interfaces { + prefix "if"; + } + import ietf-routing { prefix "rt"; } identity rip { base rt:routing-protocol; description "Identity for the RIP routing protocol."; } @@ -2493,35 +2508,35 @@ } augment "/rt:routing/rt:routing-instance/rt:routing-protocols/" + "rt:routing-protocol" { when "rt:type = 'rip:rip'" { description "This augment is only valid for a routing protocol instance of type 'rip'."; } container rip { + presence "RIP configuration"; description "RIP instance configuration."; container interfaces { description "Per-interface RIP configuration."; + list interface { key "name"; description "RIP is enabled on interfaces that have an entry in this list, unless 'enabled' is set to 'false' for that entry."; leaf name { - type leafref { - path "../../../../../../rt:interfaces/rt:interface"; - } + type if:interface-ref; } leaf enabled { type boolean; default "true"; } leaf metric { type rip-metric; default "1"; } } @@ -2597,20 +2611,21 @@ 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 @@ -2621,20 +2636,21 @@ false eth1 ianaift:ethernetCsmacd Interface to the internal network. + rtr0 198.51.100.1 24 true 2001:0db8:0:2::1 @@ -2649,21 +2665,21 @@ eth0 ianaift:ethernetCsmacd 00:0C:42:E5:B1:E9 up rtr0 - 2014-10-24T17:11:27+00:58 + 2015-10-24T17:11:27+02:00 true 1500 192.0.2.1 24 @@ -2685,31 +2701,30 @@ eth1 ianaift:ethernetCsmacd 00:0C:42:E5:B1:EA up rtr0 - 2014-10-24T17:11:27+00:59 + 2015-10-24T17:11:29+02:00 true 1500 198.51.100.1 24 - true 1500 2001:0db8:0:2::1 64 true @@ -2720,24 +2735,20 @@ rtr0 Router A 192.0.2.1 - - eth0 - eth1 - rt:static st0 Static routing is used for the internal network. @@ -2785,106 +2796,116 @@ 192.0.2.1/24 eth0 0 rt:direct - 2014-10-24T17:11:27+01:00 + 2015-10-24T17:11:27+02:00 198.51.100.0/24 eth1 rt:direct 0 - 2014-10-24T17:11:27+01:00 + 2015-10-24T17:11:27+02:00 0.0.0.0/0 rt:static 5 192.0.2.2 - 2014-10-24T18:02:45+01:00 + 2015-10-24T18:02:45+02:00 ipv6-master v6ur:ipv6-unicast true 2001:db8:0:1::/64 eth0 rt:direct 0 - 2014-10-24T17:11:27+01:00 + 2015-10-24T17:11:27+02:00 2001:db8:0:2::/64 eth1 rt:direct 0 - 2014-10-24T17:11:27+01:00 + 2015-10-24T17:11:27+02:00 ::/0 2001:db8:0:1::2 rt:static 5 - 2014-10-24T18:02:45+01:00 + 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 -18 and -19 +E.1. 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 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.2. Changes Between Versions -17 and -18 +E.3. 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). @@ -2896,38 +2917,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.3. Changes Between Versions -16 and -17 +E.4. 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.4. Changes Between Versions -15 and -16 +E.5. 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. @@ -2948,39 +2969,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.5. Changes Between Versions -14 and -15 +E.6. Changes Between Versions -14 and -15 o Removed all defaults from state data. o Removed default from 'cur-hop-limit' in config. -E.6. Changes Between Versions -13 and -14 +E.7. 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.7. Changes Between Versions -12 and -13 +E.8. 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. @@ -2993,34 +3014,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.8. Changes Between Versions -11 and -12 +E.9. 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.9. Changes Between Versions -10 and -11 +E.10. 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- @@ -3030,70 +3051,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.10. Changes Between Versions -09 and -10 +E.11. 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.11. Changes Between Versions -08 and -09 +E.12. Changes Between Versions -08 and -09 - o Fixed "must" expresion for "connected-routing-table". + 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.12. Changes Between Versions -07 and -08 +E.13. Changes Between Versions -07 and -08 o Changed reference from RFC6021 to RFC6021bis. -E.13. Changes Between Versions -06 and -07 +E.14. 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.14. Changes Between Versions -05 and -06 +E.15. 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". @@ -3101,21 +3122,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.15. Changes Between Versions -04 and -05 +E.16. 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 @@ -3136,35 +3157,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.16. Changes Between Versions -03 and -04 +E.17. 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.17. Changes Between Versions -02 and -03 +E.18. 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". @@ -3182,21 +3203,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.18. Changes Between Versions -01 and -02 +E.19. 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. @@ -3206,21 +3227,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.19. Changes Between Versions -00 and -01 +E.20. 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.