--- 1/draft-ietf-netmod-routing-cfg-24.txt 2016-11-03 09:16:14.315111915 -0700 +++ 2/draft-ietf-netmod-routing-cfg-25.txt 2016-11-03 09:16:14.439114883 -0700 @@ -1,19 +1,19 @@ NETMOD Working Group L. Lhotka Internet-Draft CZ.NIC Intended status: Standards Track A. Lindem -Expires: April 23, 2017 Cisco Systems - October 20, 2016 +Expires: May 7, 2017 Cisco Systems + November 03, 2016 A YANG Data Model for Routing Management - draft-ietf-netmod-routing-cfg-24 + draft-ietf-netmod-routing-cfg-25 Abstract 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 control plane protocols, route filters and other functions. The core routing data model provides common building blocks for such extensions -- 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 April 23, 2017. + This Internet-Draft will expire on May 7, 2017. Copyright Notice 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 @@ -81,45 +81,46 @@ 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 49 13.1. Normative References . . . . . . . . . . . . . . . . . . 50 13.2. Informative References . . . . . . . . . . . . . . . . . 50 Appendix A. The Complete Data Trees . . . . . . . . . . . . . . 51 A.1. Configuration Data . . . . . . . . . . . . . . . . . . . 51 A.2. State Data . . . . . . . . . . . . . . . . . . . . . . . 53 Appendix B. Minimum Implementation . . . . . . . . . . . . . . . 54 Appendix C. Example: Adding a New Control Plane Protocol . . . . 54 Appendix D. Data Tree Example . . . . . . . . . . . . . . . . . 57 Appendix E. Change Log . . . . . . . . . . . . . . . . . . . . . 65 - E.1. Changes Between Versions -22 and -23 . . . . . . . . . . 65 - E.2. Changes Between Versions -22 and -23 . . . . . . . . . . 65 - E.3. Changes Between Versions -21 and -22 . . . . . . . . . . 65 - E.4. Changes Between Versions -20 and -21 . . . . . . . . . . 66 - E.5. Changes Between Versions -19 and -20 . . . . . . . . . . 66 - E.6. Changes Between Versions -18 and -19 . . . . . . . . . . 66 - E.7. Changes Between Versions -17 and -18 . . . . . . . . . . 66 - E.8. Changes Between Versions -16 and -17 . . . . . . . . . . 67 - E.9. Changes Between Versions -15 and -16 . . . . . . . . . . 67 - E.10. Changes Between Versions -14 and -15 . . . . . . . . . . 68 - E.11. Changes Between Versions -13 and -14 . . . . . . . . . . 68 - E.12. Changes Between Versions -12 and -13 . . . . . . . . . . 68 - E.13. Changes Between Versions -11 and -12 . . . . . . . . . . 69 - E.14. Changes Between Versions -10 and -11 . . . . . . . . . . 69 - E.15. Changes Between Versions -09 and -10 . . . . . . . . . . 69 - E.16. Changes Between Versions -08 and -09 . . . . . . . . . . 70 - E.17. Changes Between Versions -07 and -08 . . . . . . . . . . 70 - E.18. Changes Between Versions -06 and -07 . . . . . . . . . . 70 - E.19. Changes Between Versions -05 and -06 . . . . . . . . . . 70 - E.20. Changes Between Versions -04 and -05 . . . . . . . . . . 71 - E.21. Changes Between Versions -03 and -04 . . . . . . . . . . 72 - E.22. Changes Between Versions -02 and -03 . . . . . . . . . . 72 - E.23. Changes Between Versions -01 and -02 . . . . . . . . . . 73 - E.24. Changes Between Versions -00 and -01 . . . . . . . . . . 73 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 73 + E.1. Changes Between Versions -24 and -25 . . . . . . . . . . 65 + E.2. Changes Between Versions -23 and -24 . . . . . . . . . . 65 + E.3. Changes Between Versions -22 and -23 . . . . . . . . . . 65 + E.4. Changes Between Versions -21 and -22 . . . . . . . . . . 66 + E.5. Changes Between Versions -20 and -21 . . . . . . . . . . 66 + E.6. Changes Between Versions -19 and -20 . . . . . . . . . . 66 + E.7. Changes Between Versions -18 and -19 . . . . . . . . . . 66 + E.8. Changes Between Versions -17 and -18 . . . . . . . . . . 66 + E.9. Changes Between Versions -16 and -17 . . . . . . . . . . 67 + E.10. Changes Between Versions -15 and -16 . . . . . . . . . . 67 + E.11. Changes Between Versions -14 and -15 . . . . . . . . . . 68 + E.12. Changes Between Versions -13 and -14 . . . . . . . . . . 68 + E.13. Changes Between Versions -12 and -13 . . . . . . . . . . 68 + E.14. Changes Between Versions -11 and -12 . . . . . . . . . . 69 + E.15. Changes Between Versions -10 and -11 . . . . . . . . . . 69 + E.16. Changes Between Versions -09 and -10 . . . . . . . . . . 70 + E.17. Changes Between Versions -08 and -09 . . . . . . . . . . 70 + E.18. Changes Between Versions -07 and -08 . . . . . . . . . . 70 + E.19. Changes Between Versions -06 and -07 . . . . . . . . . . 70 + E.20. Changes Between Versions -05 and -06 . . . . . . . . . . 71 + E.21. Changes Between Versions -04 and -05 . . . . . . . . . . 71 + E.22. Changes Between Versions -03 and -04 . . . . . . . . . . 72 + E.23. Changes Between Versions -02 and -03 . . . . . . . . . . 72 + E.24. Changes Between Versions -01 and -02 . . . . . . . . . . 73 + E.25. Changes Between Versions -00 and -01 . . . . . . . . . . 73 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 74 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. @@ -618,21 +619,21 @@ direct route. The destination prefix of this route is set according to the configured IP address and network prefix/mask, and the interface is set as the outgoing interface for that route. 7. Routing 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@2016-10-20.yang" + file "ietf-routing@2016-11-03.yang" module ietf-routing { yang-version "1.1"; namespace "urn:ietf:params:xml:ns:yang:ietf-routing"; prefix "rt"; import ietf-yang-types { @@ -678,21 +679,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 (https://tools.ietf.org/html/rfc2119). This version of this YANG module is part of RFC XXXX (https://tools.ietf.org/html/rfcXXXX); see the RFC itself for full legal notices."; - revision 2016-10-20 { + revision 2016-11-03 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for Routing Management"; } /* Features */ feature multiple-ribs { description @@ -1205,21 +1206,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@2016-10-20.yang" + file "ietf-ipv4-unicast-routing@2016-11-03.yang" module ietf-ipv4-unicast-routing { yang-version "1.1"; namespace "urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing"; prefix "v4ur"; import ietf-routing { @@ -1264,21 +1265,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 (https://tools.ietf.org/html/rfc2119). This version of this YANG module is part of RFC XXXX (https://tools.ietf.org/html/rfcXXXX); see the RFC itself for full legal notices."; - revision 2016-10-20 { + revision 2016-11-03 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for Routing Management"; } /* Identities */ identity ipv4-unicast { base rt:ipv4; @@ -1466,40 +1467,40 @@ } } 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@2016-10-20.yang" + file "ietf-ipv6-unicast-routing@2016-11-03.yang" module ietf-ipv6-unicast-routing { yang-version "1.1"; namespace "urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing"; prefix "v6ur"; import ietf-routing { prefix "rt"; } import ietf-inet-types { prefix "inet"; } include ietf-ipv6-router-advertisements { - revision-date 2016-10-20; + revision-date 2016-11-03; } organization "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; contact "WG Web: WG List: WG Chair: Lou Berger @@ -1530,21 +1531,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 (https://tools.ietf.org/html/rfc2119). This version of this YANG module is part of RFC XXXX (https://tools.ietf.org/html/rfcXXXX); see the RFC itself for full legal notices."; - revision 2016-10-20 { + revision 2016-11-03 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for Routing Management"; } /* Identities */ identity ipv6-unicast { base rt:ipv6; @@ -1734,21 +1735,21 @@ } 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-10-20.yang" + file "ietf-ipv6-router-advertisements@2016-11-03.yang" submodule ietf-ipv6-router-advertisements { yang-version "1.1"; belongs-to ietf-ipv6-unicast-routing { prefix "v6ur"; } import ietf-inet-types { @@ -1801,21 +1802,21 @@ 'OPTIONAL' in the module text are to be interpreted as described in RFC 2119 (https://tools.ietf.org/html/rfc2119). This version of this YANG module is part of RFC XXXX (https://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-10-20 { + revision 2016-11-03 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for Routing Management"; } /* State data */ augment "/if:interfaces-state/if:interface/ip:ipv6" { description @@ -2321,76 +2322,76 @@ Litkowski, Thomas Morin, Tom Petch, Yingzhen Qu, 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, . + DOI 10.17487/RFC2119, March 1997, + . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, - DOI 10.17487/RFC3688, 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, - DOI 10.17487/RFC4861, September 2007, . + DOI 10.17487/RFC4861, September 2007, + . [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, - DOI 10.17487/RFC6020, October 2010, . + 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, - . + . [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, - . + . [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10.17487/RFC7950, August 2016, - . + . 13.2. Informative References [RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG Data Model Documents", RFC 6087, DOI 10.17487/RFC6087, - January 2011, . + January 2011, . [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration Protocol (NETCONF) Access Control Model", RFC 6536, - DOI 10.17487/RFC6536, March 2012, . + DOI 10.17487/RFC6536, March 2012, + . [RFC7895] Bierman, A., Bjorklund, M., and K. Watsen, "YANG Module Library", RFC 7895, DOI 10.17487/RFC7895, June 2016, - . + . [RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG", RFC 7951, DOI 10.17487/RFC7951, August 2016, - . + . 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 @@ -2514,20 +2515,24 @@ 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. + For hosts that are never intended to act as routers, the ability to + turn on sending IPv6 router advertisements (Section 5.4) should be + removed. + Platforms with severely constrained resources may use deviations for restricting the data model, e.g., limiting the number of "static" control plane protocol instances. Appendix C. Example: Adding a New Control Plane Protocol This appendix demonstrates how the core routing data model can be extended to support a new control plane 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 @@ -2644,78 +2650,71 @@ Appendix D. Data Tree Example This section contains an example instance data tree in the JSON encoding [RFC7951], containing both configuration and state data. The data conforms to a data model that is defined by the following YANG library specification [RFC7895]: { "ietf-yang-library:modules-state": { - "module-set-id": "3e9be92f252db56fe912cd61a6f516ecf2f46315", + "module-set-id": "c2e1f54169aa7f36e1a6e8d0865d441d3600f9c4", "module": [ { "name": "ietf-routing", - "revision": "2016-10-20", + "revision": "2016-11-03", "feature": [ "multiple-ribs", "router-id" ], "namespace": "urn:ietf:params:xml:ns:yang:ietf-routing", "conformance-type": "implement" }, { "name": "ietf-ipv4-unicast-routing", - "revision": "2016-10-20", + "revision": "2016-11-03", "namespace": "urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing", "conformance-type": "implement" }, { "name": "ietf-ipv6-unicast-routing", - "revision": "2016-10-20", + "revision": "2016-11-03", "namespace": "urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing", - "conformance-type": "implement", - "submodule": [ - { - "name": "ietf-ipv6-router-advertisements", - "revision": "2016-10-20" - } - ] - + "conformance-type": "implement" }, { "name": "ietf-interfaces", "revision": "2014-05-08", "namespace": "urn:ietf:params:xml:ns:yang:ietf-interfaces", "conformance-type": "implement" }, { - "name": "iana-if-type", - "namespace": "urn:ietf:params:xml:ns:yang:iana-if-type", - "revision": "", - "conformance-type": "implement" - }, - { "name": "ietf-inet-types", - "revision": "2013-07-15", "namespace": "urn:ietf:params:xml:ns:yang:ietf-inet-types", + "revision": "2013-07-15", "conformance-type": "import" }, { "name": "ietf-yang-types", - "revision": "2013-07-15", "namespace": "urn:ietf:params:xml:ns:yang:ietf-yang-types", + "revision": "2013-07-15", "conformance-type": "import" }, { + "name": "iana-if-type", + "namespace": "urn:ietf:params:xml:ns:yang:iana-if-type", + "revision": "", + "conformance-type": "implement" + }, + { "name": "ietf-ip", "revision": "2014-06-16", "namespace": "urn:ietf:params:xml:ns:yang:ietf-ip", "conformance-type": "implement" } ] } } A simple network set-up as shown in Figure 3 is assumed: router "A" @@ -2937,21 +2936,22 @@ { "type": "ietf-routing:static", "name": "st0" } ] }, "ribs": { "rib": [ { "name": "ipv4-master", - "address-family": "ietf-ipv4-unicast-routing:ipv4-unicast", + "address-family": + "ietf-ipv4-unicast-routing:ipv4-unicast", "default-rib": true, "routes": { "route": [ { "ietf-ipv4-unicast-routing:destination-prefix": "192.0.2.1/24", "next-hop": { "outgoing-interface": "eth0" }, "route-preference": 0, @@ -2977,21 +2978,22 @@ "ietf-ipv4-unicast-routing:next-hop-address": "192.0.2.2" }, "last-updated": "2015-10-24T18:02:45+02:00" } ] } }, { "name": "ipv6-master", - "address-family": "ietf-ipv6-unicast-routing:ipv6-unicast", + "address-family": + "ietf-ipv6-unicast-routing:ipv6-unicast", "default-rib": true, "routes": { "route": [ { "ietf-ipv6-unicast-routing:destination-prefix": "2001:db8:0:1::/64", "next-hop": { "outgoing-interface": "eth0" }, "source-protocol": "ietf-routing:direct", @@ -3024,77 +3027,81 @@ } ] } } } Appendix E. Change Log RFC Editor: Remove this section upon publication as an RFC. -E.1. Changes Between Versions -22 and -23 +E.1. Changes Between Versions -24 and -25 + + o Minor edits based on IETF Last Call reviews. + +E.2. Changes Between Versions -23 and -24 o Fix paths in "when" expressions due to errata 4749 of RFC 7950. -E.2. Changes Between Versions -22 and -23 +E.3. Changes Between Versions -22 and -23 o Removed "route-tag" feature. o Removed next-hop classifiers. o Fixed invalid when expressions in augments. o In simple-next-hop, an address, outgoing interface or both can be specified. o RPC "fib-route" changed into RIB action "active-route". o The requirement that direct routes be always placed in default RIBs. -E.3. Changes Between Versions -21 and -22 +E.4. Changes Between Versions -21 and -22 o Added "next-hop-list" as a new case of the "next-hop-options" choice. o Renamed "routing protocol" to "control plane protocol" in both the YANG modules and I-D text. -E.4. Changes Between Versions -20 and -21 +E.5. Changes Between Versions -20 and -21 o Routing instances were removed. o IPv6 RA parameters were moved to the "ietf-ipv6-router- advertisements". -E.5. Changes Between Versions -19 and -20 +E.6. 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.6. Changes Between Versions -18 and -19 +E.7. 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.7. Changes Between Versions -17 and -18 +E.8. 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). @@ -3106,38 +3113,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.8. Changes Between Versions -16 and -17 +E.9. 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.9. Changes Between Versions -15 and -16 +E.10. 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. @@ -3158,39 +3165,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.10. Changes Between Versions -14 and -15 +E.11. Changes Between Versions -14 and -15 o Removed all defaults from state data. o Removed default from 'cur-hop-limit' in config. -E.11. Changes Between Versions -13 and -14 +E.12. 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.12. Changes Between Versions -12 and -13 +E.13. 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. @@ -3203,34 +3210,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.13. Changes Between Versions -11 and -12 +E.14. 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.14. Changes Between Versions -10 and -11 +E.15. 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- @@ -3240,70 +3247,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.15. Changes Between Versions -09 and -10 +E.16. 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.16. Changes Between Versions -08 and -09 +E.17. 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.17. Changes Between Versions -07 and -08 +E.18. Changes Between Versions -07 and -08 o Changed reference from RFC6021 to RFC6021bis. -E.18. Changes Between Versions -06 and -07 +E.19. 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.19. Changes Between Versions -05 and -06 +E.20. 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". @@ -3311,21 +3318,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.20. Changes Between Versions -04 and -05 +E.21. 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 @@ -3346,35 +3353,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.21. Changes Between Versions -03 and -04 +E.22. 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.22. Changes Between Versions -02 and -03 +E.23. 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". @@ -3392,21 +3399,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.23. Changes Between Versions -01 and -02 +E.24. 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. @@ -3416,21 +3423,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.24. Changes Between Versions -00 and -01 +E.25. 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.