--- 1/draft-ietf-netmod-routing-cfg-18.txt 2015-05-25 07:15:04.716535752 -0700 +++ 2/draft-ietf-netmod-routing-cfg-19.txt 2015-05-25 07:15:04.840538776 -0700 @@ -1,19 +1,19 @@ NETMOD Working Group L. Lhotka Internet-Draft CZ.NIC Intended status: Standards Track A. Lindem -Expires: October 19, 2015 Cisco Systems - April 17, 2015 +Expires: November 26, 2015 Cisco Systems + May 25, 2015 A YANG Data Model for Routing Management - draft-ietf-netmod-routing-cfg-18 + draft-ietf-netmod-routing-cfg-19 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 October 19, 2015. + This Internet-Draft will expire on November 26, 2015. Copyright Notice Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -59,62 +59,63 @@ 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.2. Route . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5.3. Routing Information Base (RIB) . . . . . . . . . . . . . 11 - 5.4. Routing Protocol . . . . . . . . . . . . . . . . . . . . 11 + 5.4. Routing Protocol . . . . . . . . . . . . . . . . . . . . 12 5.4.1. Routing Pseudo-Protocols . . . . . . . . . . . . . . 12 5.4.2. Defining New Routing Protocols . . . . . . . . . . . 12 5.5. RPC Operations . . . . . . . . . . . . . . . . . . . . . 13 6. Interactions with Other YANG Modules . . . . . . . . . . . . 13 6.1. Module "ietf-interfaces" . . . . . . . . . . . . . . . . 13 - 6.2. Module "ietf-ip" . . . . . . . . . . . . . . . . . . . . 13 + 6.2. Module "ietf-ip" . . . . . . . . . . . . . . . . . . . . 14 7. Routing Management YANG Module . . . . . . . . . . . . . . . 14 8. IPv4 Unicast Routing Management YANG Module . . . . . . . . . 29 - 9. IPv6 Unicast Routing Management YANG Module . . . . . . . . . 34 + 9. IPv6 Unicast Routing Management YANG Module . . . . . . . . . 33 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46 11. Security Considerations . . . . . . . . . . . . . . . . . . . 48 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 48 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 49 13.1. Normative References . . . . . . . . . . . . . . . . . . 49 13.2. Informative References . . . . . . . . . . . . . . . . . 49 Appendix A. The Complete Data Trees . . . . . . . . . . . . . . 50 A.1. Configuration Data . . . . . . . . . . . . . . . . . . . 50 A.2. State Data . . . . . . . . . . . . . . . . . . . . . . . 52 Appendix B. Minimum Implementation . . . . . . . . . . . . . . . 52 Appendix C. Example: Adding a New Routing Protocol . . . . . . . 53 Appendix D. Example: NETCONF Reply . . . . . . . . . . . . 55 Appendix E. Change Log . . . . . . . . . . . . . . . . . . . . . 62 - E.1. Changes Between Versions -17 and -18 . . . . . . . . . . 62 - E.2. Changes Between Versions -16 and -17 . . . . . . . . . . 63 - E.3. Changes Between Versions -15 and -16 . . . . . . . . . . 63 - E.4. Changes Between Versions -14 and -15 . . . . . . . . . . 64 - E.5. Changes Between Versions -13 and -14 . . . . . . . . . . 64 - E.6. Changes Between Versions -12 and -13 . . . . . . . . . . 64 - E.7. Changes Between Versions -11 and -12 . . . . . . . . . . 65 - E.8. Changes Between Versions -10 and -11 . . . . . . . . . . 65 - E.9. Changes Between Versions -09 and -10 . . . . . . . . . . 65 - E.10. Changes Between Versions -08 and -09 . . . . . . . . . . 66 - E.11. Changes Between Versions -07 and -08 . . . . . . . . . . 66 - E.12. Changes Between Versions -06 and -07 . . . . . . . . . . 66 - E.13. Changes Between Versions -05 and -06 . . . . . . . . . . 66 - E.14. Changes Between Versions -04 and -05 . . . . . . . . . . 67 - E.15. Changes Between Versions -03 and -04 . . . . . . . . . . 68 - E.16. Changes Between Versions -02 and -03 . . . . . . . . . . 68 - E.17. Changes Between Versions -01 and -02 . . . . . . . . . . 69 - E.18. Changes Between Versions -00 and -01 . . . . . . . . . . 69 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 69 + 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 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. @@ -282,22 +283,20 @@ +--rw enabled? +--rw router-id? +--rw description? +--rw interfaces | +--rw interface* +--rw routing-protocols | +--rw routing-protocol* [type name] | +--rw type | +--rw name | +--rw description? - | +--rw enabled? - | +--rw route-preference? | +--rw static-routes | ... +--rw ribs +--rw rib* [name] +--rw name +--rw address-family? +--rw description? Figure 1: Configuration data hierarchy. @@ -305,21 +304,20 @@ +--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 route-preference +--ro ribs +--ro rib* [name] +--ro name +--ro address-family +--ro default-rib? +--ro routes ... Figure 2: State data hierarchy. @@ -372,28 +370,38 @@ 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. - The semantics of the term "routing instance" is deliberately left - undefined. It is expected that future YANG modules will define data - models for specific types of routing instances, such as VRF (virtual - routing and forwarding) instances that are used for BGP/MPLS virtual - private networks [RFC4364]. For each type of routing instance, an - identity derived from "rt:routing-instance" SHALL be defined. This - identity is then referred to by the value of the "type" leaf (a child - node of "routing-instance" list). + 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. + + 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]. @@ -637,31 +645,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-04-17.yang" + file "ietf-routing@2015-05-25.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 @@ -693,24 +700,23 @@ 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-04-17 { + revision 2015-05-25 { 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. @@ -759,20 +766,28 @@ } 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 @@ -1064,29 +1077,21 @@ } leaf name { type string; description "The name of the routing protocol instance. For system-controlled instances this name is persistent, i.e., it SHOULD NOT change across reboots."; } - leaf route-preference { - type route-preference; - mandatory "true"; - description - "The value of route preference (administrative - distance) assigned to all routes generated by the - routing protocol instance. A lower value means a more - preferred route."; - } + } } container ribs { description "Container for RIBs."; list rib { key "name"; min-elements "1"; description "Each entry represents a RIB identified by the 'name' @@ -1218,47 +1222,28 @@ base routing-protocol; } description "Type of the routing protocol - an identity derived from the 'routing-protocol' base identity."; } leaf name { type string; description "An arbitrary name of the routing protocol instance."; + } leaf description { type string; description "Textual description of the routing protocol instance."; } - leaf enabled { - type boolean; - default "true"; - description - "Enable/disable the routing protocol instance. - - If this parameter is false, the parent routing - protocol instance is disabled and does not appear in - state data, despite any other configuration that might - be present."; - } - leaf route-preference { - type route-preference; - description - "The value of route preference (administrative - distance). - - The default value depends on the routing protocol - type, and may also be implementation-dependent."; - } container static-routes { when "../type='rt:static'" { description "This container is only valid for the 'static' routing protocol."; } description "Configuration of the 'static' pseudo-protocol. Address-family-specific modules augment this node with @@ -1366,35 +1351,35 @@ } 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-04-17.yang" + file "ietf-ipv4-unicast-routing@2015-05-25.yang" module ietf-ipv4-unicast-routing { namespace "urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing"; prefix "v4ur"; + import ietf-routing { prefix "rt"; } import ietf-inet-types { prefix "inet"; } - organization "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; contact "WG Web: WG List: WG Chair: Thomas Nadeau @@ -1420,29 +1405,28 @@ 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-04-17 { + revision 2015-05-25 { 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" { @@ -1570,22 +1557,21 @@ } 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-04-17.yang" - + file "ietf-ipv6-unicast-routing@2015-05-25.yang" module ietf-ipv6-unicast-routing { namespace "urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing"; prefix "v6ur"; import ietf-routing { prefix "rt"; } @@ -1633,21 +1619,21 @@ 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-04-17 { + revision 2015-05-25 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for Routing Management"; } /* Identities */ identity ipv6-unicast { base rt:ipv6; @@ -2346,38 +2329,36 @@ +--rw enabled? boolean +--rw router-id? yang:dotted-quad +--rw description? string +--rw interfaces | +--rw interface* if:interface-ref +--rw routing-protocols | +--rw routing-protocol* [type name] | +--rw type identityref | +--rw name string | +--rw description? string - | +--rw enabled? boolean - | +--rw route-preference? route-preference | +--rw static-routes | +--rw v6ur:ipv6 | | +--rw v6ur:route* [destination-prefix] - | | +--rw v6ur:destination-prefix inet:ipv6-prefix + | | +--rw v6ur:destination-prefix | | +--rw v6ur:description? string | | +--rw v6ur:next-hop | | +--rw (next-hop-options) | | +--:(simple-next-hop) | | | +--rw v6ur:outgoing-interface? | | +--:(special-next-hop) | | | +--rw v6ur:special-next-hop? | | +--:(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:destination-prefix | +--rw v4ur:description? string | +--rw v4ur:next-hop | +--rw (next-hop-options) | +--:(simple-next-hop) | | +--rw v4ur:outgoing-interface? | +--:(special-next-hop) | | +--rw v4ur:special-next-hop? | +--:(next-hop-address) | +--rw v4ur:next-hop-address? +--rw ribs @@ -2392,21 +2373,20 @@ +--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 route-preference route-preference +--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) @@ -2424,22 +2404,22 @@ Appendix B. Minimum Implementation Some parts and options of the core routing model, such as user- defined routing tables, are intended only for advanced routers. This appendix gives basic non-normative guidelines for implementing a bare minimum of available functions. Such an implementation may be used for hosts or very simple routers. A minimum implementation will provide a single system-controlled - routing instance, and will not allow clients to create any user- - controlled instances. + 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. @@ -2788,21 +2768,20 @@ rtr0 eth0 eth1 rt:static st0 - 5 ipv4-master v4ur:ipv4-unicast true @@ -2880,21 +2859,32 @@ Appendix E. Change Log RFC Editor: Remove this section upon publication as an RFC. -E.1. Changes Between Versions -17 and -18 +E.1. 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 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). @@ -2906,38 +2896,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.2. Changes Between Versions -16 and -17 +E.3. 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.3. Changes Between Versions -15 and -16 +E.4. 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. @@ -2958,39 +2948,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.4. Changes Between Versions -14 and -15 +E.5. Changes Between Versions -14 and -15 o Removed all defaults from state data. o Removed default from 'cur-hop-limit' in config. -E.5. Changes Between Versions -13 and -14 +E.6. 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.6. Changes Between Versions -12 and -13 +E.7. 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. @@ -3003,34 +2993,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.7. Changes Between Versions -11 and -12 +E.8. 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.8. Changes Between Versions -10 and -11 +E.9. 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- @@ -3040,70 +3030,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.9. Changes Between Versions -09 and -10 +E.10. 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.10. Changes Between Versions -08 and -09 +E.11. Changes Between Versions -08 and -09 o Fixed "must" expresion for "connected-routing-table". o Simplified "must" expression for "main-routing-table". o Moved per-interface configuration of a new routing protocol under 'routing-protocol'. This also affects the 'example-rip' module. -E.11. Changes Between Versions -07 and -08 +E.12. Changes Between Versions -07 and -08 o Changed reference from RFC6021 to RFC6021bis. -E.12. Changes Between Versions -06 and -07 +E.13. 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.13. Changes Between Versions -05 and -06 +E.14. 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". @@ -3111,21 +3101,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.14. Changes Between Versions -04 and -05 +E.15. 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 @@ -3146,35 +3136,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.15. Changes Between Versions -03 and -04 +E.16. 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.16. Changes Between Versions -02 and -03 +E.17. 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". @@ -3192,21 +3182,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.17. Changes Between Versions -01 and -02 +E.18. 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. @@ -3216,21 +3206,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.18. Changes Between Versions -00 and -01 +E.19. 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.