draft-ietf-netmod-routing-cfg-19.txt   draft-ietf-netmod-routing-cfg-20.txt 
NETMOD Working Group L. Lhotka NETMOD Working Group L. Lhotka
Internet-Draft CZ.NIC Internet-Draft CZ.NIC
Intended status: Standards Track A. Lindem Intended status: Standards Track A. Lindem
Expires: November 26, 2015 Cisco Systems Expires: April 18, 2016 Cisco Systems
May 25, 2015 October 16, 2015
A YANG Data Model for Routing Management A YANG Data Model for Routing Management
draft-ietf-netmod-routing-cfg-19 draft-ietf-netmod-routing-cfg-20
Abstract Abstract
This document contains a specification of three YANG modules. This document contains a specification of three YANG modules.
Together they form the core routing data model which serves as a Together they form the core routing data model which serves as a
framework for configuring and managing a routing subsystem. It is framework for configuring and managing a routing subsystem. It is
expected that these modules will be augmented by additional YANG expected that these modules will be augmented by additional YANG
modules defining data models for routing protocols, route filters and modules defining data models for routing protocols, route filters and
other functions. The core routing data model provides common other functions. The core routing data model provides common
building blocks for such extensions - routing instances, routes, building blocks for such extensions - routing instances, routes,
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." 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 Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 20 skipping to change at page 2, line 20
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology and Notation . . . . . . . . . . . . . . . . . . 3 2. Terminology and Notation . . . . . . . . . . . . . . . . . . 3
2.1. Glossary of New Terms . . . . . . . . . . . . . . . . . . 4 2.1. Glossary of New Terms . . . . . . . . . . . . . . . . . . 4
2.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 5 2.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 5
2.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 5 2.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 5
3. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. The Design of the Core Routing Data Model . . . . . . . . . . 6 4. The Design of the Core Routing Data Model . . . . . . . . . . 6
4.1. System-Controlled and User-Controlled List Entries . . . 8 4.1. System-Controlled and User-Controlled List Entries . . . 8
5. Basic Building Blocks . . . . . . . . . . . . . . . . . . . . 8 5. Basic Building Blocks . . . . . . . . . . . . . . . . . . . . 8
5.1. Routing Instance . . . . . . . . . . . . . . . . . . . . 9 5.1. Routing Instance . . . . . . . . . . . . . . . . . . . . 8
5.1.1. Parameters of IPv6 Routing Instance Interfaces . . . 9 5.1.1. Parameters of IPv6 Router Interfaces . . . . . . . . 9
5.2. Route . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5.2. Route . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.3. Routing Information Base (RIB) . . . . . . . . . . . . . 11 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.1. Routing Pseudo-Protocols . . . . . . . . . . . . . . 12
5.4.2. Defining New Routing Protocols . . . . . . . . . . . 12 5.4.2. Defining New Routing Protocols . . . . . . . . . . . 12
5.5. RPC Operations . . . . . . . . . . . . . . . . . . . . . 13 5.5. RPC Operations . . . . . . . . . . . . . . . . . . . . . 13
6. Interactions with Other YANG Modules . . . . . . . . . . . . 13 6. Interactions with Other YANG Modules . . . . . . . . . . . . 13
6.1. Module "ietf-interfaces" . . . . . . . . . . . . . . . . 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 7. Routing Management YANG Module . . . . . . . . . . . . . . . 14
8. IPv4 Unicast Routing Management YANG Module . . . . . . . . . 29 8. IPv4 Unicast Routing Management YANG Module . . . . . . . . . 29
9. IPv6 Unicast Routing Management YANG Module . . . . . . . . . 33 9. IPv6 Unicast Routing Management YANG Module . . . . . . . . . 33
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46
11. Security Considerations . . . . . . . . . . . . . . . . . . . 48 11. Security Considerations . . . . . . . . . . . . . . . . . . . 47
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 48 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 48
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 49 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 48
13.1. Normative References . . . . . . . . . . . . . . . . . . 49 13.1. Normative References . . . . . . . . . . . . . . . . . . 48
13.2. Informative References . . . . . . . . . . . . . . . . . 49 13.2. Informative References . . . . . . . . . . . . . . . . . 49
Appendix A. The Complete Data Trees . . . . . . . . . . . . . . 50 Appendix A. The Complete Data Trees . . . . . . . . . . . . . . 49
A.1. Configuration Data . . . . . . . . . . . . . . . . . . . 50 A.1. Configuration Data . . . . . . . . . . . . . . . . . . . 49
A.2. State Data . . . . . . . . . . . . . . . . . . . . . . . 52 A.2. State Data . . . . . . . . . . . . . . . . . . . . . . . 50
Appendix B. Minimum Implementation . . . . . . . . . . . . . . . 52 Appendix B. Minimum Implementation . . . . . . . . . . . . . . . 51
Appendix C. Example: Adding a New Routing Protocol . . . . . . . 53 Appendix C. Example: Adding a New Routing Protocol . . . . . . . 52
Appendix D. Example: NETCONF <get> Reply . . . . . . . . . . . . 55 Appendix D. Example: NETCONF <get> Reply . . . . . . . . . . . . 54
Appendix E. Change Log . . . . . . . . . . . . . . . . . . . . . 62 Appendix E. Change Log . . . . . . . . . . . . . . . . . . . . . 61
E.1. Changes Between Versions -18 and -19 . . . . . . . . . . 62 E.1. Changes Between Versions -19 and -20 . . . . . . . . . . 61
E.2. Changes Between Versions -17 and -18 . . . . . . . . . . 62 E.2. Changes Between Versions -18 and -19 . . . . . . . . . . 61
E.3. Changes Between Versions -16 and -17 . . . . . . . . . . 63 E.3. Changes Between Versions -17 and -18 . . . . . . . . . . 61
E.4. Changes Between Versions -15 and -16 . . . . . . . . . . 63 E.4. Changes Between Versions -16 and -17 . . . . . . . . . . 62
E.5. Changes Between Versions -14 and -15 . . . . . . . . . . 64 E.5. Changes Between Versions -15 and -16 . . . . . . . . . . 62
E.6. Changes Between Versions -13 and -14 . . . . . . . . . . 64 E.6. Changes Between Versions -14 and -15 . . . . . . . . . . 63
E.7. Changes Between Versions -12 and -13 . . . . . . . . . . 64 E.7. Changes Between Versions -13 and -14 . . . . . . . . . . 63
E.8. Changes Between Versions -11 and -12 . . . . . . . . . . 65 E.8. Changes Between Versions -12 and -13 . . . . . . . . . . 63
E.9. Changes Between Versions -10 and -11 . . . . . . . . . . 65 E.9. Changes Between Versions -11 and -12 . . . . . . . . . . 64
E.10. Changes Between Versions -09 and -10 . . . . . . . . . . 66 E.10. Changes Between Versions -10 and -11 . . . . . . . . . . 64
E.11. Changes Between Versions -08 and -09 . . . . . . . . . . 66 E.11. Changes Between Versions -09 and -10 . . . . . . . . . . 65
E.12. Changes Between Versions -07 and -08 . . . . . . . . . . 66 E.12. Changes Between Versions -08 and -09 . . . . . . . . . . 65
E.13. Changes Between Versions -06 and -07 . . . . . . . . . . 66 E.13. Changes Between Versions -07 and -08 . . . . . . . . . . 65
E.14. Changes Between Versions -05 and -06 . . . . . . . . . . 67 E.14. Changes Between Versions -06 and -07 . . . . . . . . . . 65
E.15. Changes Between Versions -04 and -05 . . . . . . . . . . 67 E.15. Changes Between Versions -05 and -06 . . . . . . . . . . 66
E.16. Changes Between Versions -03 and -04 . . . . . . . . . . 68 E.16. Changes Between Versions -04 and -05 . . . . . . . . . . 66
E.17. Changes Between Versions -02 and -03 . . . . . . . . . . 68 E.17. Changes Between Versions -03 and -04 . . . . . . . . . . 67
E.18. Changes Between Versions -01 and -02 . . . . . . . . . . 69 E.18. Changes Between Versions -02 and -03 . . . . . . . . . . 67
E.19. Changes Between Versions -00 and -01 . . . . . . . . . . 69 E.19. Changes Between Versions -01 and -02 . . . . . . . . . . 68
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 70 E.20. Changes Between Versions -00 and -01 . . . . . . . . . . 68
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 69
1. Introduction 1. Introduction
This document contains a specification of the following YANG modules: This document contains a specification of the following YANG modules:
o Module "ietf-routing" provides generic components of a routing o Module "ietf-routing" provides generic components of a routing
data model. data model.
o Module "ietf-ipv4-unicast-routing" augments the "ietf-routing" o Module "ietf-ipv4-unicast-routing" augments the "ietf-routing"
module with additional data specific to IPv4 unicast. module with additional data specific to IPv4 unicast.
o Module "ietf-ipv6-unicast-routing" augments the "ietf-routing" o Module "ietf-ipv6-unicast-routing" augments the "ietf-routing"
module with additional data specific to IPv6 unicast, including module with additional data specific to IPv6 unicast. It also
the router configuration variables required by [RFC4861]. 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, These modules together define the so-called core routing data model,
which is intended as a basis for future data model development which is intended as a basis for future data model development
covering more sophisticated routing systems. While these three covering more sophisticated routing systems. While these three
modules can be directly used for simple IP devices with static modules can be directly used for simple IP devices with static
routing (see Appendix B), their main purpose is to provide essential routing (see Appendix B), their main purpose is to provide essential
building blocks for more complicated data models involving multiple building blocks for more complicated data models involving multiple
routing protocols, multicast routing, additional address families, routing protocols, multicast routing, additional address families,
and advanced functions such as route filtering or policy routing. To and advanced functions such as route filtering or policy routing. To
this end, it is expected that the core routing data model will be this end, it is expected that the core routing data model will be
skipping to change at page 4, line 19 skipping to change at page 4, line 21
o protocol operation, o protocol operation,
o server. o server.
The following terms are defined in [RFC6020]: The following terms are defined in [RFC6020]:
o augment, o augment,
o configuration data, o configuration data,
o container,
o container with presence,
o data model, o data model,
o data node, o data node,
o feature, o feature,
o leaf,
o list,
o mandatory node, o mandatory node,
o module, o module,
o schema tree, o schema tree,
o state data, o state data,
o RPC operation. o RPC operation.
skipping to change at page 5, line 15 skipping to change at page 5, line 23
user-controlled entry: An entry of a list in state data ("config user-controlled entry: An entry of a list in state data ("config
false") that is created and deleted as a direct consequence of false") that is created and deleted as a direct consequence of
certain configuration changes. See Section 4.1 for details. certain configuration changes. See Section 4.1 for details.
2.2. Tree Diagrams 2.2. Tree Diagrams
A simplified graphical representation of the complete data tree is A simplified graphical representation of the complete data tree is
presented in Appendix A, and similar diagrams of its various subtrees presented in Appendix A, and similar diagrams of its various subtrees
appear in the main text. appear in the main text.
The meaning of the symbols in these diagrams is as follows:
o Brackets "[" and "]" enclose list keys. o Brackets "[" and "]" enclose list keys.
o Curly braces "{" and "}" contain names of optional features that o Curly braces "{" and "}" contain names of optional features that
make the corresponding node conditional. make the corresponding node conditional.
o Abbreviations before data node names: "rw" means configuration o Abbreviations before data node names: "rw" means configuration
(read-write), "ro" state data (read-only), "-x" RPC operations, (read-write), "ro" state data (read-only), "-x" RPC operations,
and "-n" notifications. and "-n" notifications.
o Symbols after data node names: "?" means an optional node, "!" a o Symbols after data node names: "?" means an optional node, "!" a
skipping to change at page 7, line 12 skipping to change at page 7, line 12
configuration and state data hierarchies. See Appendix A for the configuration and state data hierarchies. See Appendix A for the
complete data trees. complete data trees.
+--rw routing +--rw routing
+--rw routing-instance* [name] +--rw routing-instance* [name]
+--rw name +--rw name
+--rw type? +--rw type?
+--rw enabled? +--rw enabled?
+--rw router-id? +--rw router-id?
+--rw description? +--rw description?
+--rw interfaces
| +--rw interface*
+--rw routing-protocols +--rw routing-protocols
| +--rw routing-protocol* [type name] | +--rw routing-protocol* [type name]
| +--rw type | +--rw type
| +--rw name | +--rw name
| +--rw description? | +--rw description?
| +--rw static-routes | +--rw static-routes
| ... | ...
+--rw ribs +--rw ribs
+--rw rib* [name] +--rw rib* [name]
+--rw name +--rw name
skipping to change at page 8, line 26 skipping to change at page 8, line 24
state" container. state" container.
Additional entries may be created in the configuration by a client, Additional entries may be created in the configuration by a client,
e.g., via the NETCONF protocol. These are so-called user-controlled e.g., via the NETCONF protocol. These are so-called user-controlled
entries. If the server accepts a configured user-controlled entry, entries. If the server accepts a configured user-controlled entry,
then this entry also appears in the state data version of the list. then this entry also appears in the state data version of the list.
Corresponding entries in both versions of the list (in state data and Corresponding entries in both versions of the list (in state data and
configuration) have the same value of the list key. configuration) have the same value of the list key.
The user may also provide supplemental configuration of system- A client may also provide supplemental configuration of system-
controlled entries. To do so, the user creates a new entry in the controlled entries. To do so, the client creates a new entry in the
configuration with the desired contents. In order to bind this entry 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 configuration entry has to be set to the same value as the key of the
state entry. state entry.
An example can be seen in Appendix D: the "/routing-state/routing- An example can be seen in Appendix D: the "/routing-state/routing-
instance" list has a single system-controlled entry whose "name" key instance" list has a single system-controlled entry whose "name" key
has the value "rtr0". This entry is configured by the "/routing/ has the value "rtr0". This entry is configured by the "/routing/
routing-instance" entry whose "name" key is also "rtr0". routing-instance" entry whose "name" key is also "rtr0".
Deleting a user-controlled entry from the configuration list results Deleting a user-controlled entry from the configuration list results
in the removal of the corresponding entry in the state data list. In in the removal of the corresponding entry in the state data list. In
skipping to change at page 9, line 19 skipping to change at page 9, line 13
instance has separate configuration and state data under instance has separate configuration and state data under
"/rt:routing/rt:routing-instance" and "/rt:routing-state/rt:routing- "/rt:routing/rt:routing-instance" and "/rt:routing-state/rt:routing-
instance", respectively. instance", respectively.
No attempt has been made to define the semantics for every type of No attempt has been made to define the semantics for every type of
routing instance. The core routing data model defines identities for routing instance. The core routing data model defines identities for
two ubiquitous routing instance types: two ubiquitous routing instance types:
o "default-routing-instance" - this routing instance type represents o "default-routing-instance" - this routing instance type represents
the default (or only) routing instance. All implementations MUST 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 o "vrf-routing-instance" - this routing instance type represents VRF
(virtual routing and forwarding) routing instances that are used (virtual routing and forwarding) routing instances that are used
for virtual private networks (VPN) including BGP/MPLS for virtual private networks (VPN) including BGP/MPLS
VPN_[RFC4364]. VPN_[RFC4364].
It is expected that future YANG modules will define other types of It is expected that future YANG modules will define other types of
routing instances. For every such type, an identity derived from routing instances. For every such type, an identity derived from
"rt:routing-instance" SHALL be defined. This identity is then "rt:routing-instance" SHALL be defined. This identity is then
referred to by the value of the "type" leaf (a child node of referred to by the value of the "type" leaf (a child node of
"routing-instance" list). "routing-instance" list).
Each network layer interface has to be assigned to one or more By default, all network layer interfaces are assigned to the routing
routing instances in order to be able to participate in packet instance of the "default-routing-instance" type. This can be changed
forwarding, routing protocols and other operations of those routing by configuring the "rt:routing-instance" leaf in the interface
instances. The assignment is accomplished by placing a corresponding configuration.
(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].
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 YANG module "ietf-ipv6-unicast-routing" (Section 9) augments the
configuration and state data of interfaces with definitions of the configuration and state data of IPv6 interfaces with definitions of
following variables as required by [RFC4861], sec. 6.2.1: the following variables as required by [RFC4861], sec. 6.2.1:
o send-advertisements, o send-advertisements,
o max-rtr-adv-interval, o max-rtr-adv-interval,
o min-rtr-adv-interval, o min-rtr-adv-interval,
o managed-flag, o managed-flag,
o other-config-flag, o other-config-flag,
o link-mtu, o link-mtu,
o reachable-time, o reachable-time,
o retrans-timer, o retrans-timer,
o cur-hop-limit, o cur-hop-limit,
o default-lifetime, o default-lifetime,
o prefix-list: a list of prefixes to be advertised. o prefix-list: a list of prefixes to be advertised.
The following parameters are associated with each prefix in the The following parameters are associated with each prefix in the
list: list:
skipping to change at page 13, line 16 skipping to change at page 13, line 9
/rt:fib-route/rt:output/rt:route, /rt:fib-route/rt:output/rt:route,
and possibly other places in the configuration, state data, and possibly other places in the configuration, state data,
notifications, and RPC input or output. notifications, and RPC input or output.
o Configuration parameters and/or state data for the new protocol o Configuration parameters and/or state data for the new protocol
can be defined by augmenting the "routing-protocol" data node can be defined by augmenting the "routing-protocol" data node
under both "/routing" and "/routing-state". under both "/routing" and "/routing-state".
o Per-interface configuration, including activation of the routing By using a "when" statement, the augmented configuration parameters
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
and state data specific to the new protocol SHOULD be made and state data specific to the new protocol SHOULD be made
conditional and valid only if the value of "rt:type" or "rt:source- 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 protocol" is equal to the new protocol's identity.
RECOMMENDED that protocol-specific data nodes be encapsulated in
appropriately named containers. 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 The above steps are implemented by the example YANG module for the
RIP routing protocol in Appendix C. RIP routing protocol in Appendix C.
5.5. RPC Operations 5.5. RPC Operations
The "ietf-routing" module defines one RPC operation: The "ietf-routing" module defines one RPC operation:
o fib-route: query a routing instance for the active route in the o fib-route: query a routing instance for the active route in the
Forwarding Information Base (FIB). It is the route that is Forwarding Information Base (FIB). It is the route that is
skipping to change at page 14, line 4 skipping to change at page 13, line 42
The semantics of the core routing data model also depends on several The semantics of the core routing data model also depends on several
configuration parameters that are defined in other YANG modules. configuration parameters that are defined in other YANG modules.
6.1. Module "ietf-interfaces" 6.1. Module "ietf-interfaces"
The following boolean switch is defined in the "ietf-interfaces" YANG The following boolean switch is defined in the "ietf-interfaces" YANG
module [RFC7223]: module [RFC7223]:
/if:interfaces/if:interface/if:enabled /if:interfaces/if:interface/if:enabled
If this switch is set to "false" for a network layer interface, If this switch is set to "false" for a network layer interface,
the device MUST behave exactly as if that interface was not then all routing and forwarding functions MUST be disabled on that
assigned to any routing instance at all. interface.
6.2. Module "ietf-ip" 6.2. Module "ietf-ip"
The following boolean switches are defined in the "ietf-ip" YANG The following boolean switches are defined in the "ietf-ip" YANG
module [RFC7277]: module [RFC7277]:
/if:interfaces/if:interface/ip:ipv4/ip:enabled /if:interfaces/if:interface/ip:ipv4/ip:enabled
If this switch is set to "false" for a network layer interface, If this switch is set to "false" for a network layer interface,
then all IPv4 routing functions related to that interface MUST be then all IPv4 routing and forwarding functions MUST be disabled on
disabled. that interface.
/if:interfaces/if:interface/ip:ipv4/ip:forwarding /if:interfaces/if:interface/ip:ipv4/ip:forwarding
If this switch is set to "false" for a network layer interface, If this switch is set to "false" for a network layer interface,
then the forwarding of IPv4 datagrams to and from this interface then the forwarding of IPv4 datagrams through this interface MUST
MUST be disabled. However, the interface may participate in other be disabled. However, the interface MAY participate in other IPv4
IPv4 routing functions, such as routing protocols. routing functions, such as routing protocols.
/if:interfaces/if:interface/ip:ipv6/ip:enabled /if:interfaces/if:interface/ip:ipv6/ip:enabled
If this switch is set to "false" for a network layer interface, If this switch is set to "false" for a network layer interface,
then all IPv6 routing functions related to that interface MUST be then all IPv6 routing and forwarding functions MUST be disabled on
disabled. that interface.
/if:interfaces/if:interface/ip:ipv6/ip:forwarding /if:interfaces/if:interface/ip:ipv6/ip:forwarding
If this switch is set to "false" for a network layer interface, If this switch is set to "false" for a network layer interface,
then the forwarding of IPv6 datagrams to and from this interface then the forwarding of IPv6 datagrams through this interface MUST
MUST be disabled. However, the interface may participate in other be disabled. However, the interface MAY participate in other IPv6
IPv6 routing functions, such as routing protocols. routing functions, such as routing protocols.
In addition, the "ietf-ip" module allows for configuring IPv4 and In addition, the "ietf-ip" module allows for configuring IPv4 and
IPv6 addresses and network prefixes or masks on network layer IPv6 addresses and network prefixes or masks on network layer
interfaces. Configuration of these parameters on an enabled interfaces. Configuration of these parameters on an enabled
interface MUST result in an immediate creation of the corresponding interface MUST result in an immediate creation of the corresponding
direct route. The destination prefix of this route is set according direct route. The destination prefix of this route is set according
to the configured IP address and network prefix/mask, and the to the configured IP address and network prefix/mask, and the
interface is set as the outgoing interface for that route. interface is set as the outgoing interface for that route.
7. Routing Management YANG Module 7. Routing Management YANG Module
RFC Editor: In this section, replace all occurrences of 'XXXX' with RFC Editor: In this section, replace all occurrences of 'XXXX' with
the actual RFC number and all occurrences of the revision date below the actual RFC number and all occurrences of the revision date below
with the date of RFC publication (and remove this note). with the date of RFC publication (and remove this note).
<CODE BEGINS> file "ietf-routing@2015-05-25.yang" <CODE BEGINS> file "ietf-routing@2015-10-16.yang"
module ietf-routing { module ietf-routing {
namespace "urn:ietf:params:xml:ns:yang:ietf-routing"; namespace "urn:ietf:params:xml:ns:yang:ietf-routing";
prefix "rt"; prefix "rt";
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix "yang";
} }
import ietf-interfaces { import ietf-interfaces {
prefix "if"; prefix "if";
} }
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group"; "IETF NETMOD (NETCONF Data Modeling Language) Working Group";
contact contact
skipping to change at page 15, line 34 skipping to change at page 15, line 24
contact contact
"WG Web: <http://tools.ietf.org/wg/netmod/> "WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:netmod@ietf.org> WG List: <mailto:netmod@ietf.org>
WG Chair: Thomas Nadeau WG Chair: Thomas Nadeau
<mailto:tnadeau@lucidvision.com> <mailto:tnadeau@lucidvision.com>
WG Chair: Juergen Schoenwaelder WG Chair: Juergen Schoenwaelder
<mailto:j.schoenwaelder@jacobs-university.de> <mailto:j.schoenwaelder@jacobs-university.de>
WG Chair: Kent Watsen
<mailto:kwatsen@juniper.net>
Editor: Ladislav Lhotka Editor: Ladislav Lhotka
<mailto:lhotka@nic.cz>"; <mailto:lhotka@nic.cz>";
description description
"This YANG module defines essential components for the management "This YANG module defines essential components for the management
of a routing subsystem. 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. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and
'OPTIONAL' in the module text are to be interpreted as described 'OPTIONAL' in the module text are to be interpreted as described
in RFC 2119 (http://tools.ietf.org/html/rfc2119). in RFC 2119 (http://tools.ietf.org/html/rfc2119).
This version of this YANG module is part of RFC XXXX This version of this YANG module is part of RFC XXXX
(http://tools.ietf.org/html/rfcXXXX); see the RFC itself for (http://tools.ietf.org/html/rfcXXXX); see the RFC itself for
full legal notices."; full legal notices.";
revision 2015-05-25 { revision 2015-10-16 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for Routing Management"; "RFC XXXX: A YANG Data Model for Routing Management";
} }
/* Features */ /* Features */
feature multiple-ribs { feature multiple-ribs {
description description
skipping to change at page 20, line 7 skipping to change at page 19, line 48
} }
grouping next-hop-content { grouping next-hop-content {
description description
"Generic parameters of next-hops in static routes."; "Generic parameters of next-hops in static routes.";
choice next-hop-options { choice next-hop-options {
mandatory "true"; mandatory "true";
description description
"Options for next-hops in static routes. "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 augments from other modules, e.g., for Equal-Cost Multipath
routing (ECMP)."; routing (ECMP).";
case simple-next-hop { leaf outgoing-interface {
type if:interface-ref;
description description
"Simple next-hop is specified as an outgoing interface, "Name of the 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";
}
description
"Name of the outgoing interface.";
}
} }
case special-next-hop { case special-next-hop {
uses special-next-hop; uses special-next-hop;
} }
} }
} }
grouping next-hop-state-content { grouping next-hop-state-content {
description description
"Generic parameters of next-hops in state data."; "Generic parameters of next-hops in state data.";
choice next-hop-options { choice next-hop-options {
mandatory "true"; mandatory "true";
description description
"Options for next-hops in state data. "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 augments from other modules, e.g., for ECMP or recursive
next-hops."; next-hops.";
case simple-next-hop { leaf outgoing-interface {
type if:interface-state-ref;
description description
"Simple next-hop is specified as an outgoing interface, "Name of the 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";
}
description
"Name of the outgoing interface.";
}
} }
case special-next-hop { case special-next-hop {
uses special-next-hop; uses special-next-hop;
} }
} }
} }
grouping route-metadata { grouping route-metadata {
description description
"Common route metadata."; "Common route metadata.";
skipping to change at page 21, line 49 skipping to change at page 21, line 28
"Time stamp of the last modification of the route. If the "Time stamp of the last modification of the route. If the
route was never modified, it is the time when the route was route was never modified, it is the time when the route was
inserted into the RIB."; inserted into the RIB.";
} }
} }
/* State data */ /* State data */
augment "/if:interfaces-state/if:interface" { augment "/if:interfaces-state/if:interface" {
description description
"This augment adds a wrapped leaf-list to interface state "This augment adds a reference to the routing-instance to which
data."; the interface is assigned.";
leaf routing-instance { leaf routing-instance {
type routing-instance-state-ref; 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 description
"The name of the routing instance to which the interface is "The name of the routing instance to which the interface is
assigned."; assigned.";
} }
} }
container routing-state { container routing-state {
config "false"; config "false";
description description
"State data of the routing subsystem."; "State data of the routing subsystem.";
list routing-instance { list routing-instance {
key "name"; key "name";
min-elements "1"; min-elements "1";
description description
"Each list entry is a container for state data of a routing "Each list entry is a container for state data of a routing
instance. instance.
An implementation MUST support routing instance(s) of the An implementation MUST provide one and only one
type 'rt:default-routing-instance', and MAY support other system-controlled routing instance(s) of the type
types. An implementation MAY restrict the number of routing 'rt:default-routing-instance', and MAY support other types.
instances of each supported type.
An implementation SHOULD create at least one An implementation MAY restrict the number of routing
system-controlled instance, and MAY allow the clients to instances of each supported type.";
create user-controlled routing instances in
configuration.";
leaf name { leaf name {
type string; type string;
description description
"The name of the routing instance. "The name of the routing instance.
For system-controlled instances the name is persistent, For system-controlled instances the name SHOULD be
i.e., it SHOULD NOT change across reboots."; persistent, i.e., it doesn't change after a reboot.";
} }
leaf type { leaf type {
type identityref { type identityref {
base routing-instance; base routing-instance;
} }
description description
"The routing instance type."; "The routing instance type.";
} }
uses router-id { uses router-id {
description description
skipping to change at page 23, line 20 skipping to change at page 22, line 35
It may be either configured or assigned algorithmically by It may be either configured or assigned algorithmically by
the implementation."; the implementation.";
} }
container interfaces { container interfaces {
description description
"Network layer interfaces belonging to the routing "Network layer interfaces belonging to the routing
instance."; instance.";
leaf-list interface { leaf-list interface {
type if:interface-state-ref; 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 description
"Each entry is a reference to the name of a configured "Each entry is a reference to the name of a configured
network layer interface."; network layer interface.";
} }
} }
container routing-protocols { container routing-protocols {
description description
"Container for the list of routing protocol instances."; "Container for the list of routing protocol instances.";
list routing-protocol { list routing-protocol {
key "type name"; key "type name";
skipping to change at page 25, line 21 skipping to change at page 24, line 44
uses route-metadata; uses route-metadata;
} }
} }
} }
} }
} }
} }
/* Configuration Data */ /* 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 { container routing {
description description
"Configuration parameters for the routing subsystem."; "Configuration parameters for the routing subsystem.";
list routing-instance { list routing-instance {
key "name"; key "name";
description description
"Configuration of a routing instance."; "Configuration of a routing instance.";
leaf name { leaf name {
type string; type string;
description description
skipping to change at page 26, line 22 skipping to change at page 26, line 12
description description
"Configuration of the global router ID. Routing protocols "Configuration of the global router ID. Routing protocols
that use router ID can use this parameter or override it that use router ID can use this parameter or override it
with another value."; with another value.";
} }
leaf description { leaf description {
type string; type string;
description description
"Textual description of the routing instance."; "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 { container routing-protocols {
description description
"Configuration of routing protocol instances."; "Configuration of routing protocol instances.";
list routing-protocol { list routing-protocol {
key "type name"; key "type name";
description description
"Each entry contains configuration of a routing protocol "Each entry contains configuration of a routing protocol
instance."; instance.";
leaf type { leaf type {
type identityref { type identityref {
skipping to change at page 29, line 36 skipping to change at page 29, line 17
} }
<CODE ENDS> <CODE ENDS>
8. IPv4 Unicast Routing Management YANG Module 8. IPv4 Unicast Routing Management YANG Module
RFC Editor: In this section, replace all occurrences of 'XXXX' with RFC Editor: In this section, replace all occurrences of 'XXXX' with
the actual RFC number and all occurrences of the revision date below the actual RFC number and all occurrences of the revision date below
with the date of RFC publication (and remove this note). with the date of RFC publication (and remove this note).
<CODE BEGINS> file "ietf-ipv4-unicast-routing@2015-05-25.yang" <CODE BEGINS> file "ietf-ipv4-unicast-routing@2015-10-16.yang"
module ietf-ipv4-unicast-routing { module ietf-ipv4-unicast-routing {
namespace "urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing"; namespace "urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing";
prefix "v4ur"; prefix "v4ur";
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
} }
skipping to change at page 30, line 17 skipping to change at page 29, line 46
contact contact
"WG Web: <http://tools.ietf.org/wg/netmod/> "WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:netmod@ietf.org> WG List: <mailto:netmod@ietf.org>
WG Chair: Thomas Nadeau WG Chair: Thomas Nadeau
<mailto:tnadeau@lucidvision.com> <mailto:tnadeau@lucidvision.com>
WG Chair: Juergen Schoenwaelder WG Chair: Juergen Schoenwaelder
<mailto:j.schoenwaelder@jacobs-university.de> <mailto:j.schoenwaelder@jacobs-university.de>
WG Chair: Kent Watsen
<mailto:kwatsen@juniper.net>
Editor: Ladislav Lhotka Editor: Ladislav Lhotka
<mailto:lhotka@nic.cz>"; <mailto:lhotka@nic.cz>";
description description
"This YANG module augments the 'ietf-routing' module with basic "This YANG module augments the 'ietf-routing' module with basic
configuration and state data for IPv4 unicast routing. 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. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and
'OPTIONAL' in the module text are to be interpreted as described 'OPTIONAL' in the module text are to be interpreted as described
in RFC 2119 (http://tools.ietf.org/html/rfc2119). in RFC 2119 (http://tools.ietf.org/html/rfc2119).
This version of this YANG module is part of RFC XXXX This version of this YANG module is part of RFC XXXX
(http://tools.ietf.org/html/rfcXXXX); see the RFC itself for (http://tools.ietf.org/html/rfcXXXX); see the RFC itself for
full legal notices."; full legal notices.";
revision 2015-05-25 { revision 2015-10-16 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for Routing Management"; "RFC XXXX: A YANG Data Model for Routing Management";
} }
/* Identities */ /* Identities */
identity ipv4-unicast { identity ipv4-unicast {
base rt:ipv4; base rt:ipv4;
description description
"This identity represents the IPv4 unicast address family."; "This identity represents the IPv4 unicast address family.";
} }
/* State data */ /* State data */
augment "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/" augment "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/"
+ "rt:routes/rt:route" { + "rt:routes/rt:route" {
skipping to change at page 31, line 28 skipping to change at page 31, line 11
description description
"This leaf augments an IPv4 unicast route."; "This leaf augments an IPv4 unicast route.";
leaf destination-prefix { leaf destination-prefix {
type inet:ipv4-prefix; type inet:ipv4-prefix;
description description
"IPv4 destination prefix."; "IPv4 destination prefix.";
} }
} }
augment "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/" augment "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/"
+ "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/" + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options" {
+ "rt:simple-next-hop" {
when "../../../rt:address-family = 'v4ur:ipv4-unicast'" { when "../../../rt:address-family = 'v4ur:ipv4-unicast'" {
description description
"This augment is valid only for IPv4 unicast."; "This augment is valid only for IPv4 unicast.";
} }
description description
"This leaf augments the 'simple-next-hop' case of IPv4 unicast "Augment 'next-hop-options' in IPv4 unicast routes.";
routes.";
leaf next-hop-address { leaf next-hop-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"IPv4 address of the next-hop."; "IPv4 address of the next-hop.";
} }
} }
/* Configuration data */ /* Configuration data */
augment "/rt:routing/rt:routing-instance/rt:routing-protocols/" augment "/rt:routing/rt:routing-instance/rt:routing-protocols/"
+ "rt:routing-protocol/rt:static-routes" { + "rt:routing-protocol/rt:static-routes" {
description description
"This augment defines the configuration of the 'static' "This augment defines the configuration of the 'static'
pseudo-protocol with data specific to IPv4 unicast."; pseudo-protocol with data specific to IPv4 unicast.";
container ipv4 { container ipv4 {
description description
"Configuration of a 'static' pseudo-protocol instance "Configuration of a 'static' pseudo-protocol instance
consists of a list of routes."; consists of a list of routes.";
list route { list route {
key "destination-prefix"; key "destination-prefix";
ordered-by "user";
description description
"A user-ordered list of static routes."; "A list of static routes.";
leaf destination-prefix { leaf destination-prefix {
type inet:ipv4-prefix; type inet:ipv4-prefix;
mandatory "true"; mandatory "true";
description description
"IPv4 destination prefix."; "IPv4 destination prefix.";
} }
leaf description { leaf description {
type string; type string;
description description
"Textual description of the route."; "Textual description of the route.";
} }
container next-hop { container next-hop {
description description
"Configuration of next-hop."; "Configuration of next-hop.";
uses rt:next-hop-content { uses rt:next-hop-content {
augment "next-hop-options" { augment "next-hop-options" {
description description
"Add next-hop address case."; "Augment 'next-hop-options' in IPv4 static routes.";
leaf next-hop-address { leaf next-hop-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"IPv4 address of the next-hop."; "IPv4 address of the next-hop.";
} }
} }
} }
} }
} }
} }
skipping to change at page 33, line 25 skipping to change at page 33, line 4
"This augment is valid only for IPv4 unicast."; "This augment is valid only for IPv4 unicast.";
} }
description description
"This leaf augments the reply to the 'rt:fib-route' "This leaf augments the reply to the 'rt:fib-route'
operation."; operation.";
leaf destination-prefix { leaf destination-prefix {
type inet:ipv4-prefix; type inet:ipv4-prefix;
description description
"IPv4 destination prefix."; "IPv4 destination prefix.";
} }
} }
augment "/rt:fib-route/rt:output/rt:route/rt:next-hop/" 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'" { when "../rt:address-family='v4ur:ipv4-unicast'" {
description description
"This augment is valid only for IPv4 unicast."; "This augment is valid only for IPv4 unicast.";
} }
description description
"This leaf augments the 'simple-next-hop' case in the reply to "Augment 'next-hop-options' in the reply to the 'rt:fib-route'
the 'rt:fib-route' operation."; operation.";
leaf next-hop-address { leaf next-hop-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"IPv4 address of the next-hop."; "IPv4 address of the next-hop.";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
9. IPv6 Unicast Routing Management YANG Module 9. IPv6 Unicast Routing Management YANG Module
RFC Editor: In this section, replace all occurrences of 'XXXX' with RFC Editor: In this section, replace all occurrences of 'XXXX' with
the actual RFC number and all occurrences of the revision date below the actual RFC number and all occurrences of the revision date below
with the date of RFC publication (and remove this note). with the date of RFC publication (and remove this note).
<CODE BEGINS> file "ietf-ipv6-unicast-routing@2015-05-25.yang" <CODE BEGINS> file "ietf-ipv6-unicast-routing@2015-10-16.yang"
module ietf-ipv6-unicast-routing { module ietf-ipv6-unicast-routing {
namespace "urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing"; namespace "urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing";
prefix "v6ur"; prefix "v6ur";
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
} }
skipping to change at page 34, line 39 skipping to change at page 34, line 20
contact contact
"WG Web: <http://tools.ietf.org/wg/netmod/> "WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:netmod@ietf.org> WG List: <mailto:netmod@ietf.org>
WG Chair: Thomas Nadeau WG Chair: Thomas Nadeau
<mailto:tnadeau@lucidvision.com> <mailto:tnadeau@lucidvision.com>
WG Chair: Juergen Schoenwaelder WG Chair: Juergen Schoenwaelder
<mailto:j.schoenwaelder@jacobs-university.de> <mailto:j.schoenwaelder@jacobs-university.de>
WG Chair: Kent Watsen
<mailto:kwatsen@juniper.net>
Editor: Ladislav Lhotka Editor: Ladislav Lhotka
<mailto:lhotka@nic.cz>"; <mailto:lhotka@nic.cz>";
description description
"This YANG module augments the 'ietf-routing' module with basic "This YANG module augments the 'ietf-routing' module with basic
configuration and state data for IPv6 unicast routing. 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. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and
'OPTIONAL' in the module text are to be interpreted as described 'OPTIONAL' in the module text are to be interpreted as described
in RFC 2119 (http://tools.ietf.org/html/rfc2119). in RFC 2119 (http://tools.ietf.org/html/rfc2119).
This version of this YANG module is part of RFC XXXX This version of this YANG module is part of RFC XXXX
(http://tools.ietf.org/html/rfcXXXX); see the RFC itself for (http://tools.ietf.org/html/rfcXXXX); see the RFC itself for
full legal notices."; full legal notices.";
revision 2015-05-25 { revision 2015-10-16 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for Routing Management"; "RFC XXXX: A YANG Data Model for Routing Management";
} }
/* Identities */ /* Identities */
identity ipv6-unicast { identity ipv6-unicast {
base rt:ipv6; base rt:ipv6;
description description
"This identity represents the IPv6 unicast address family."; "This identity represents the IPv6 unicast address family.";
skipping to change at page 39, line 4 skipping to change at page 38, line 35
"This augment is valid only for IPv6 unicast."; "This augment is valid only for IPv6 unicast.";
} }
description description
"This leaf augments an IPv6 unicast route."; "This leaf augments an IPv6 unicast route.";
leaf destination-prefix { leaf destination-prefix {
type inet:ipv6-prefix; type inet:ipv6-prefix;
description description
"IPv6 destination prefix."; "IPv6 destination prefix.";
} }
} }
augment "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/" augment "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/"
+ "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/" + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options" {
+ "rt:simple-next-hop" {
when "../../../rt:address-family = 'v6ur:ipv6-unicast'" { when "../../../rt:address-family = 'v6ur:ipv6-unicast'" {
description description
"This augment is valid only for IPv6 unicast."; "This augment is valid only for IPv6 unicast.";
} }
description description
"This leaf augments the 'simple-next-hop' case of IPv6 unicast "Augment 'next-hop-options' in IPv6 unicast routes.";
routes.";
leaf next-hop-address { leaf next-hop-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"IPv6 address of the next-hop."; "IPv6 address of the next-hop.";
} }
} }
/* Configuration data */ /* Configuration data */
augment "/if:interfaces/if:interface/ip:ipv6" { augment "/if:interfaces/if:interface/ip:ipv6" {
description description
"Augment interface configuration with IPv6-specific parameters "Augment interface configuration with IPv6-specific parameters
of router interfaces."; of router interfaces.";
container ipv6-router-advertisements { container ipv6-router-advertisements {
description description
"Configuration of IPv6 Router Advertisements."; "Configuration of IPv6 Router Advertisements.";
leaf send-advertisements { leaf send-advertisements {
type boolean; type boolean;
default "false"; default "false";
skipping to change at page 44, line 40 skipping to change at page 44, line 23
+ "rt:routing-protocol/rt:static-routes" { + "rt:routing-protocol/rt:static-routes" {
description description
"This augment defines the configuration of the 'static' "This augment defines the configuration of the 'static'
pseudo-protocol with data specific to IPv6 unicast."; pseudo-protocol with data specific to IPv6 unicast.";
container ipv6 { container ipv6 {
description description
"Configuration of a 'static' pseudo-protocol instance "Configuration of a 'static' pseudo-protocol instance
consists of a list of routes."; consists of a list of routes.";
list route { list route {
key "destination-prefix"; key "destination-prefix";
ordered-by "user";
description description
"A user-ordered list of static routes."; "A list of static routes.";
leaf destination-prefix { leaf destination-prefix {
type inet:ipv6-prefix; type inet:ipv6-prefix;
mandatory "true"; mandatory "true";
description description
"IPv6 destination prefix."; "IPv6 destination prefix.";
} }
leaf description { leaf description {
type string; type string;
description description
"Textual description of the route."; "Textual description of the route.";
} }
container next-hop { container next-hop {
description description
"Configuration of next-hop."; "Configuration of next-hop.";
uses rt:next-hop-content { uses rt:next-hop-content {
augment "next-hop-options" { augment "next-hop-options" {
description description
"Add next-hop address case."; "Augment 'next-hop-options' in IPv6 static routes.";
leaf next-hop-address { leaf next-hop-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"IPv6 address of the next-hop."; "IPv6 address of the next-hop.";
} }
} }
} }
} }
} }
} }
skipping to change at page 46, line 10 skipping to change at page 45, line 40
"This leaf augments the reply to the 'rt:fib-route' "This leaf augments the reply to the 'rt:fib-route'
operation."; operation.";
leaf destination-prefix { leaf destination-prefix {
type inet:ipv6-prefix; type inet:ipv6-prefix;
description description
"IPv6 destination prefix."; "IPv6 destination prefix.";
} }
} }
augment "/rt:fib-route/rt:output/rt:route/rt:next-hop/" 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'" { when "../rt:address-family='v6ur:ipv6-unicast'" {
description description
"This augment is valid only for IPv6 unicast."; "This augment is valid only for IPv6 unicast.";
} }
description description
"This leaf augments the 'simple-next-hop' case in the reply to "Augment 'next-hop-options' in the reply to the 'rt:fib-route'
the 'rt:fib-route' operation."; operation.";
leaf next-hop-address { leaf next-hop-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"IPv6 address of the next-hop."; "IPv6 address of the next-hop.";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
10. IANA Considerations 10. IANA Considerations
RFC Ed.: In this section, replace all occurrences of 'XXXX' with the RFC Ed.: In this section, replace all occurrences of 'XXXX' with the
actual RFC number (and remove this note). actual RFC number (and remove this note).
skipping to change at page 48, line 24 skipping to change at page 47, line 45
content. content.
A number of data nodes defined in the YANG modules belonging to the A number of data nodes defined in the YANG modules belonging to the
configuration part of the core routing data model are configuration part of the core routing data model are
writable/creatable/deletable (i.e., "config true" in YANG terms, writable/creatable/deletable (i.e., "config true" in YANG terms,
which is the default). These data nodes may be considered sensitive which is the default). These data nodes may be considered sensitive
or vulnerable in some network environments. Write operations to or vulnerable in some network environments. Write operations to
these data nodes, such as "edit-config", can have negative effects on these data nodes, such as "edit-config", can have negative effects on
the network if the protocol operations are not properly protected. 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: following:
/routing/routing-instance/interfaces/interface: This list assigns a /if:interfaces/if:interface/rt:routing-instance: This leaf assigns a
network layer interface to a routing instance and may also specify network layer interface to a routing instance.
interface parameters related to routing.
/routing/routing-instance/routing-protocols/routing-protocol: This /routing/routing-instance/routing-protocols/routing-protocol: This
list specifies the routing protocols configured on a device. list specifies the routing protocols configured on a device.
/routing/routing-instance/ribs/rib: This list specifies the RIBs /routing/routing-instance/ribs/rib: This list specifies the RIBs
configured for the device. 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 routing subsystem of both the local device and the network. This may
lead to network malfunctions, delivery of packets to inappropriate lead to network malfunctions, delivery of packets to inappropriate
destinations and other problems. destinations and other problems.
12. Acknowledgments 12. Acknowledgments
The authors wish to thank Nitin Bahadur, Martin Bjorklund, Dean The authors wish to thank Nitin Bahadur, Martin Bjorklund, Dean
Bogdanovic, Jeff Haas, Joel Halpern, Wes Hardaker, Sriganesh Kini, Bogdanovic, Jeff Haas, Joel Halpern, Wes Hardaker, Sriganesh Kini,
David Lamparter, Andrew McGregor, Jan Medved, Xiang Li, Stephane David Lamparter, Andrew McGregor, Jan Medved, Xiang Li, Stephane
Litkowski, Thomas Morin, Tom Petch, Bruno Rijsman, Litkowski, Thomas Morin, Tom Petch, Bruno Rijsman,
Juergen Schoenwaelder, Phil Shafer, Dave Thaler, Yi Yang, Derek Man- Juergen Schoenwaelder, Phil Shafer, Dave Thaler, Yi Yang, Derek Man-
Kit Yeung and Jeffrey Zhang for their helpful comments and Kit Yeung and Jeffrey Zhang for their helpful comments and
suggestions. suggestions.
13. References 13. References
13.1. Normative References 13.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [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,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>.
[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
September 2007. DOI 10.17487/RFC4861, September 2007,
<http://www.rfc-editor.org/info/rfc4861>.
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010. DOI 10.17487/RFC6020, October 2010,
<http://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
Bierman, "Network Configuration Protocol (NETCONF)", RFC and A. Bierman, Ed., "Network Configuration Protocol
6241, June 2011. (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<http://www.rfc-editor.org/info/rfc6241>.
[RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC
July 2013. 6991, DOI 10.17487/RFC6991, July 2013,
<http://www.rfc-editor.org/info/rfc6991>.
[RFC7223] Bjorklund, M., "A YANG Data Model for Interface [RFC7223] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 7223, May 2014. Management", RFC 7223, DOI 10.17487/RFC7223, May 2014,
<http://www.rfc-editor.org/info/rfc7223>.
[RFC7277] Bjorklund, M., "A YANG Data Model for IP Management", RFC [RFC7277] Bjorklund, M., "A YANG Data Model for IP Management", RFC
7277, June 2014. 7277, DOI 10.17487/RFC7277, June 2014,
<http://www.rfc-editor.org/info/rfc7277>.
13.2. Informative References 13.2. Informative References
[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private [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, <http://www.rfc-editor.org/info/rfc4364>.
[RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG [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, <http://www.rfc-editor.org/info/rfc6087>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [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,
<http://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, March Protocol (NETCONF) Access Control Model", RFC 6536, DOI
2012. 10.17487/RFC6536, March 2012,
<http://www.rfc-editor.org/info/rfc6536>.
Appendix A. The Complete Data Trees Appendix A. The Complete Data Trees
This appendix presents the complete configuration and state data This appendix presents the complete configuration and state data
trees of the core routing data model. See Section 2.2 for an 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 explanation of the symbols used. Data type of every leaf node is
shown near the right end of the corresponding line. shown near the right end of the corresponding line.
A.1. Configuration Data A.1. Configuration Data
+--rw routing +--rw routing
+--rw routing-instance* [name] +--rw routing-instance* [name]
+--rw name string +--rw name string
+--rw type? identityref +--rw type? identityref
+--rw enabled? boolean +--rw enabled? boolean
+--rw router-id? yang:dotted-quad +--rw router-id? yang:dotted-quad
+--rw description? string +--rw description? string
+--rw interfaces
| +--rw interface* if:interface-ref
+--rw routing-protocols +--rw routing-protocols
| +--rw routing-protocol* [type name] | +--rw routing-protocol* [type name]
| +--rw type identityref | +--rw type identityref
| +--rw name string | +--rw name string
| +--rw description? string | +--rw description? string
| +--rw static-routes | +--rw static-routes
| +--rw v6ur:ipv6 | +--rw v6ur:ipv6
| | +--rw v6ur:route* [destination-prefix] | | +--rw v6ur:route* [destination-prefix]
| | +--rw v6ur:destination-prefix | | +--rw v6ur:destination-prefix inet:ipv6-prefix
| | +--rw v6ur:description? string | | +--rw v6ur:description? string
| | +--rw v6ur:next-hop | | +--rw v6ur:next-hop
| | +--rw (next-hop-options) | | +--rw (next-hop-options)
| | +--:(simple-next-hop) | | +--:(outgoing-interface)
| | | +--rw v6ur:outgoing-interface? | | | +--rw v6ur:outgoing-interface?
| | +--:(special-next-hop) | | +--:(special-next-hop)
| | | +--rw v6ur:special-next-hop? | | | +--rw v6ur:special-next-hop?
| | +--:(next-hop-address) | | +--:(next-hop-address)
| | +--rw v6ur:next-hop-address? | | +--rw v6ur:next-hop-address?
| +--rw v4ur:ipv4 | +--rw v4ur:ipv4
| +--rw v4ur:route* [destination-prefix] | +--rw v4ur:route* [destination-prefix]
| +--rw v4ur:destination-prefix | +--rw v4ur:destination-prefix inet:ipv4-prefix
| +--rw v4ur:description? string | +--rw v4ur:description? string
| +--rw v4ur:next-hop | +--rw v4ur:next-hop
| +--rw (next-hop-options) | +--rw (next-hop-options)
| +--:(simple-next-hop) | +--:(outgoing-interface)
| | +--rw v4ur:outgoing-interface? | | +--rw v4ur:outgoing-interface?
| +--:(special-next-hop) | +--:(special-next-hop)
| | +--rw v4ur:special-next-hop? | | +--rw v4ur:special-next-hop?
| +--:(next-hop-address) | +--:(next-hop-address)
| +--rw v4ur:next-hop-address? | +--rw v4ur:next-hop-address?
+--rw ribs +--rw ribs
+--rw rib* [name] +--rw rib* [name]
+--rw name string +--rw name string
+--rw address-family? identityref +--rw address-family? identityref
+--rw description? string +--rw description? string
skipping to change at page 52, line 25 skipping to change at page 51, line 22
| +--ro routing-protocol* [type name] | +--ro routing-protocol* [type name]
| +--ro type identityref | +--ro type identityref
| +--ro name string | +--ro name string
+--ro ribs +--ro ribs
+--ro rib* [name] +--ro rib* [name]
+--ro name string +--ro name string
+--ro address-family identityref +--ro address-family identityref
+--ro default-rib? boolean {multiple-ribs}? +--ro default-rib? boolean {multiple-ribs}?
+--ro routes +--ro routes
+--ro route* +--ro route*
+--ro route-preference? route-preference +--ro route-preference? route-preference
+--ro next-hop +--ro next-hop
| +--ro (next-hop-options) | +--ro (next-hop-options)
| +--:(simple-next-hop) | +--:(outgoing-interface)
| | +--ro outgoing-interface? | | +--ro outgoing-interface?
| | +--ro v6ur:next-hop-address?
| | +--ro v4ur:next-hop-address?
| +--:(special-next-hop) | +--:(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 source-protocol identityref
+--ro active? empty +--ro active? empty
+--ro last-updated? yang:date-and-time +--ro last-updated? yang:date-and-time
+--ro v6ur:destination-prefix? inet:ipv6-prefix +--ro v6ur:destination-prefix? inet:ipv6-prefix
+--ro v4ur:destination-prefix? inet:ipv4-prefix +--ro v4ur:destination-prefix? inet:ipv4-prefix
Appendix B. Minimum Implementation Appendix B. Minimum Implementation
Some parts and options of the core routing model, such as user- Some parts and options of the core routing model, such as user-
defined routing tables, are intended only for advanced routers. This defined RIBs, are intended only for advanced routers. This appendix
appendix gives basic non-normative guidelines for implementing a bare gives basic non-normative guidelines for implementing a bare minimum
minimum of available functions. Such an implementation may be used of available functions. Such an implementation may be used for hosts
for hosts or very simple routers. or very simple routers.
A minimum implementation will provide a single system-controlled A minimum implementation provides a single system-controlled routing
routing instance of the type "default-routing-instance", and will not instance of the type "default-routing-instance", and will not allow
allow clients to create any user-controlled instances. clients to create any user-controlled instances.
Typically, the feature "multiple-ribs" will not be supported. This Typically, the feature "multiple-ribs" will not be supported. This
means that a single system-controlled RIB is available for each means that a single system-controlled RIB is available for each
supported address family - IPv4, IPv6 or both. These RIBs must be supported address family - IPv4, IPv6 or both. These RIBs must be
the default RIBs. No user-controlled RIBs are allowed. the default RIBs. No user-controlled RIBs are allowed.
In addition to the mandatory instance of the "direct" pseudo- In addition to the mandatory instance of the "direct" pseudo-
protocol, a minimum implementation should support configuring protocol, a minimum implementation should support configuring
instance(s) of the "static" pseudo-protocol. instance(s) of the "static" pseudo-protocol.
skipping to change at page 53, line 33 skipping to change at page 52, line 33
a real definition of a data model for the RIP routing protocol. For 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 the sake of brevity, this module does not obey all the guidelines
specified in [RFC6087]. See also Section 5.4.2. specified in [RFC6087]. See also Section 5.4.2.
module example-rip { module example-rip {
namespace "http://example.com/rip"; namespace "http://example.com/rip";
prefix "rip"; prefix "rip";
import ietf-interfaces {
prefix "if";
}
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
} }
identity rip { identity rip {
base rt:routing-protocol; base rt:routing-protocol;
description description
"Identity for the RIP routing protocol."; "Identity for the RIP routing protocol.";
} }
skipping to change at page 54, line 42 skipping to change at page 53, line 46
} }
augment "/rt:routing/rt:routing-instance/rt:routing-protocols/" augment "/rt:routing/rt:routing-instance/rt:routing-protocols/"
+ "rt:routing-protocol" { + "rt:routing-protocol" {
when "rt:type = 'rip:rip'" { when "rt:type = 'rip:rip'" {
description description
"This augment is only valid for a routing protocol instance "This augment is only valid for a routing protocol instance
of type 'rip'."; of type 'rip'.";
} }
container rip { container rip {
presence "RIP configuration";
description description
"RIP instance configuration."; "RIP instance configuration.";
container interfaces { container interfaces {
description description
"Per-interface RIP configuration."; "Per-interface RIP configuration.";
list interface { list interface {
key "name"; key "name";
description description
"RIP is enabled on interfaces that have an entry in this "RIP is enabled on interfaces that have an entry in this
list, unless 'enabled' is set to 'false' for that list, unless 'enabled' is set to 'false' for that
entry."; entry.";
leaf name { leaf name {
type leafref { type if:interface-ref;
path "../../../../../../rt:interfaces/rt:interface";
}
} }
leaf enabled { leaf enabled {
type boolean; type boolean;
default "true"; default "true";
} }
leaf metric { leaf metric {
type rip-metric; type rip-metric;
default "1"; default "1";
} }
} }
skipping to change at page 56, line 51 skipping to change at page 56, line 4
xmlns:ip="urn:ietf:params:xml:ns:yang:ietf-ip" xmlns:ip="urn:ietf:params:xml:ns:yang:ietf-ip"
xmlns:rt="urn:ietf:params:xml:ns:yang:ietf-routing"> xmlns:rt="urn:ietf:params:xml:ns:yang:ietf-routing">
<data> <data>
<if:interfaces> <if:interfaces>
<if:interface> <if:interface>
<if:name>eth0</if:name> <if:name>eth0</if:name>
<if:type>ianaift:ethernetCsmacd</if:type> <if:type>ianaift:ethernetCsmacd</if:type>
<if:description> <if:description>
Uplink to ISP. Uplink to ISP.
</if:description> </if:description>
<rt:routing-instance>rtr0</rt:routing-instance>
<ip:ipv4> <ip:ipv4>
<ip:address> <ip:address>
<ip:ip>192.0.2.1</ip:ip> <ip:ip>192.0.2.1</ip:ip>
<ip:prefix-length>24</ip:prefix-length> <ip:prefix-length>24</ip:prefix-length>
</ip:address> </ip:address>
<ip:forwarding>true</ip:forwarding> <ip:forwarding>true</ip:forwarding>
</ip:ipv4> </ip:ipv4>
<ip:ipv6> <ip:ipv6>
<ip:address> <ip:address>
<ip:ip>2001:0db8:0:1::1</ip:ip> <ip:ip>2001:0db8:0:1::1</ip:ip>
skipping to change at page 57, line 26 skipping to change at page 56, line 29
<ip:create-global-addresses>false</ip:create-global-addresses> <ip:create-global-addresses>false</ip:create-global-addresses>
</ip:autoconf> </ip:autoconf>
</ip:ipv6> </ip:ipv6>
</if:interface> </if:interface>
<if:interface> <if:interface>
<if:name>eth1</if:name> <if:name>eth1</if:name>
<if:type>ianaift:ethernetCsmacd</if:type> <if:type>ianaift:ethernetCsmacd</if:type>
<if:description> <if:description>
Interface to the internal network. Interface to the internal network.
</if:description> </if:description>
<rt:routing-instance>rtr0</rt:routing-instance>
<ip:ipv4> <ip:ipv4>
<ip:address> <ip:address>
<ip:ip>198.51.100.1</ip:ip> <ip:ip>198.51.100.1</ip:ip>
<ip:prefix-length>24</ip:prefix-length> <ip:prefix-length>24</ip:prefix-length>
</ip:address> </ip:address>
<ip:forwarding>true</ip:forwarding> <ip:forwarding>true</ip:forwarding>
</ip:ipv4> </ip:ipv4>
<ip:ipv6> <ip:ipv6>
<ip:address> <ip:address>
<ip:ip>2001:0db8:0:2::1</ip:ip> <ip:ip>2001:0db8:0:2::1</ip:ip>
skipping to change at page 58, line 6 skipping to change at page 57, line 10
</if:interfaces> </if:interfaces>
<if:interfaces-state> <if:interfaces-state>
<if:interface> <if:interface>
<if:name>eth0</if:name> <if:name>eth0</if:name>
<if:type>ianaift:ethernetCsmacd</if:type> <if:type>ianaift:ethernetCsmacd</if:type>
<if:phys-address>00:0C:42:E5:B1:E9</if:phys-address> <if:phys-address>00:0C:42:E5:B1:E9</if:phys-address>
<if:oper-status>up</if:oper-status> <if:oper-status>up</if:oper-status>
<rt:routing-instance>rtr0</rt:routing-instance> <rt:routing-instance>rtr0</rt:routing-instance>
<if:statistics> <if:statistics>
<if:discontinuity-time> <if:discontinuity-time>
2014-10-24T17:11:27+00:58 2015-10-24T17:11:27+02:00
</if:discontinuity-time> </if:discontinuity-time>
</if:statistics> </if:statistics>
<ip:ipv4> <ip:ipv4>
<ip:forwarding>true</ip:forwarding> <ip:forwarding>true</ip:forwarding>
<ip:mtu>1500</ip:mtu> <ip:mtu>1500</ip:mtu>
<ip:address> <ip:address>
<ip:ip>192.0.2.1</ip:ip> <ip:ip>192.0.2.1</ip:ip>
<ip:prefix-length>24</ip:prefix-length> <ip:prefix-length>24</ip:prefix-length>
</ip:address> </ip:address>
</ip:ipv4> </ip:ipv4>
skipping to change at page 58, line 42 skipping to change at page 57, line 46
</ip:ipv6> </ip:ipv6>
</if:interface> </if:interface>
<if:interface> <if:interface>
<if:name>eth1</if:name> <if:name>eth1</if:name>
<if:type>ianaift:ethernetCsmacd</if:type> <if:type>ianaift:ethernetCsmacd</if:type>
<if:phys-address>00:0C:42:E5:B1:EA</if:phys-address> <if:phys-address>00:0C:42:E5:B1:EA</if:phys-address>
<if:oper-status>up</if:oper-status> <if:oper-status>up</if:oper-status>
<rt:routing-instance>rtr0</rt:routing-instance> <rt:routing-instance>rtr0</rt:routing-instance>
<if:statistics> <if:statistics>
<if:discontinuity-time> <if:discontinuity-time>
2014-10-24T17:11:27+00:59 2015-10-24T17:11:29+02:00
</if:discontinuity-time> </if:discontinuity-time>
</if:statistics> </if:statistics>
<ip:ipv4> <ip:ipv4>
<ip:forwarding>true</ip:forwarding> <ip:forwarding>true</ip:forwarding>
<ip:mtu>1500</ip:mtu> <ip:mtu>1500</ip:mtu>
<ip:address> <ip:address>
<ip:ip>198.51.100.1</ip:ip> <ip:ip>198.51.100.1</ip:ip>
<ip:prefix-length>24</ip:prefix-length> <ip:prefix-length>24</ip:prefix-length>
</ip:address> </ip:address>
</ip:ipv4> </ip:ipv4>
<ip:ipv6> <ip:ipv6>
<ip:forwarding>true</ip:forwarding> <ip:forwarding>true</ip:forwarding>
<ip:mtu>1500</ip:mtu> <ip:mtu>1500</ip:mtu>
<ip:address> <ip:address>
<ip:ip>2001:0db8:0:2::1</ip:ip> <ip:ip>2001:0db8:0:2::1</ip:ip>
<ip:prefix-length>64</ip:prefix-length> <ip:prefix-length>64</ip:prefix-length>
</ip:address> </ip:address>
<v6ur:ipv6-router-advertisements> <v6ur:ipv6-router-advertisements>
<v6ur:send-advertisements>true</v6ur:send-advertisements> <v6ur:send-advertisements>true</v6ur:send-advertisements>
skipping to change at page 59, line 29 skipping to change at page 58, line 32
</v6ur:prefix-list> </v6ur:prefix-list>
</v6ur:ipv6-router-advertisements> </v6ur:ipv6-router-advertisements>
</ip:ipv6> </ip:ipv6>
</if:interface> </if:interface>
</if:interfaces-state> </if:interfaces-state>
<rt:routing> <rt:routing>
<rt:routing-instance> <rt:routing-instance>
<rt:name>rtr0</rt:name> <rt:name>rtr0</rt:name>
<rt:description>Router A</rt:description> <rt:description>Router A</rt:description>
<rt:router-id>192.0.2.1</rt:router-id> <rt:router-id>192.0.2.1</rt:router-id>
<rt:interfaces>
<rt:interface>eth0</rt:interface>
<rt:interface>eth1</rt:interface>
</rt:interfaces>
<rt:routing-protocols> <rt:routing-protocols>
<rt:routing-protocol> <rt:routing-protocol>
<rt:type>rt:static</rt:type> <rt:type>rt:static</rt:type>
<rt:name>st0</rt:name> <rt:name>st0</rt:name>
<rt:description> <rt:description>
Static routing is used for the internal network. Static routing is used for the internal network.
</rt:description> </rt:description>
<rt:static-routes> <rt:static-routes>
<v4ur:ipv4> <v4ur:ipv4>
<v4ur:route> <v4ur:route>
<v4ur:destination-prefix> <v4ur:destination-prefix>
0.0.0.0/0 0.0.0.0/0
</v4ur:destination-prefix> </v4ur:destination-prefix>
<v4ur:next-hop> <v4ur:next-hop>
<v4ur:next-hop-address>192.0.2.2</v4ur:next-hop-address> <v4ur:next-hop-address>192.0.2.2</v4ur:next-hop-address>
</v4ur:next-hop> </v4ur:next-hop>
</v4ur:route> </v4ur:route>
</v4ur:ipv4> </v4ur:ipv4>
<v6ur:ipv6> <v6ur:ipv6>
<v6ur:route> <v6ur:route>
<v6ur:destination-prefix>::/0</v6ur:destination-prefix> <v6ur:destination-prefix>::/0</v6ur:destination-prefix>
<v6ur:next-hop> <v6ur:next-hop>
<v6ur:next-hop-address> <v6ur:next-hop-address>
2001:db8:0:1::2 2001:db8:0:1::2
</v6ur:next-hop-address> </v6ur:next-hop-address>
</v6ur:next-hop> </v6ur:next-hop>
</v6ur:route> </v6ur:route>
</v6ur:ipv6> </v6ur:ipv6>
</rt:static-routes> </rt:static-routes>
</rt:routing-protocol> </rt:routing-protocol>
</rt:routing-protocols> </rt:routing-protocols>
</rt:routing-instance> </rt:routing-instance>
</rt:routing> </rt:routing>
<rt:routing-state> <rt:routing-state>
<rt:routing-instance> <rt:routing-instance>
<rt:name>rtr0</rt:name> <rt:name>rtr0</rt:name>
skipping to change at page 60, line 37 skipping to change at page 59, line 37
<rt:name>st0</rt:name> <rt:name>st0</rt:name>
</rt:routing-protocol> </rt:routing-protocol>
</rt:routing-protocols> </rt:routing-protocols>
<rt:ribs> <rt:ribs>
<rt:rib> <rt:rib>
<rt:name>ipv4-master</rt:name> <rt:name>ipv4-master</rt:name>
<rt:address-family>v4ur:ipv4-unicast</rt:address-family> <rt:address-family>v4ur:ipv4-unicast</rt:address-family>
<rt:default-rib>true</rt:default-rib> <rt:default-rib>true</rt:default-rib>
<rt:routes> <rt:routes>
<rt:route> <rt:route>
<v4ur:destination-prefix> <v4ur:destination-prefix>
192.0.2.1/24 192.0.2.1/24
</v4ur:destination-prefix> </v4ur:destination-prefix>
<rt:next-hop> <rt:next-hop>
<rt:outgoing-interface>eth0</rt:outgoing-interface> <rt:outgoing-interface>eth0</rt:outgoing-interface>
</rt:next-hop> </rt:next-hop>
<rt:route-preference>0</rt:route-preference> <rt:route-preference>0</rt:route-preference>
<rt:source-protocol>rt:direct</rt:source-protocol> <rt:source-protocol>rt:direct</rt:source-protocol>
<rt:last-updated>2014-10-24T17:11:27+01:00</rt:last-updated> <rt:last-updated>2015-10-24T17:11:27+02:00</rt:last-updated>
</rt:route> </rt:route>
<rt:route> <rt:route>
<v4ur:destination-prefix> <v4ur:destination-prefix>
198.51.100.0/24 198.51.100.0/24
</v4ur:destination-prefix> </v4ur:destination-prefix>
<rt:next-hop> <rt:next-hop>
<rt:outgoing-interface>eth1</rt:outgoing-interface> <rt:outgoing-interface>eth1</rt:outgoing-interface>
</rt:next-hop> </rt:next-hop>
<rt:source-protocol>rt:direct</rt:source-protocol> <rt:source-protocol>rt:direct</rt:source-protocol>
<rt:route-preference>0</rt:route-preference> <rt:route-preference>0</rt:route-preference>
<rt:last-updated>2014-10-24T17:11:27+01:00</rt:last-updated> <rt:last-updated>2015-10-24T17:11:27+02:00</rt:last-updated>
</rt:route> </rt:route>
<rt:route> <rt:route>
<v4ur:destination-prefix>0.0.0.0/0</v4ur:destination-prefix> <v4ur:destination-prefix>0.0.0.0/0</v4ur:destination-prefix>
<rt:source-protocol>rt:static</rt:source-protocol> <rt:source-protocol>rt:static</rt:source-protocol>
<rt:route-preference>5</rt:route-preference> <rt:route-preference>5</rt:route-preference>
<rt:next-hop> <rt:next-hop>
<v4ur:next-hop-address>192.0.2.2</v4ur:next-hop-address> <v4ur:next-hop-address>192.0.2.2</v4ur:next-hop-address>
</rt:next-hop> </rt:next-hop>
<rt:last-updated>2014-10-24T18:02:45+01:00</rt:last-updated> <rt:last-updated>2015-10-24T18:02:45+02:00</rt:last-updated>
</rt:route> </rt:route>
</rt:routes> </rt:routes>
</rt:rib> </rt:rib>
<rt:rib> <rt:rib>
<rt:name>ipv6-master</rt:name> <rt:name>ipv6-master</rt:name>
<rt:address-family>v6ur:ipv6-unicast</rt:address-family> <rt:address-family>v6ur:ipv6-unicast</rt:address-family>
<rt:default-rib>true</rt:default-rib> <rt:default-rib>true</rt:default-rib>
<rt:routes> <rt:routes>
<rt:route> <rt:route>
<v6ur:destination-prefix> <v6ur:destination-prefix>
2001:db8:0:1::/64 2001:db8:0:1::/64
</v6ur:destination-prefix> </v6ur:destination-prefix>
<rt:next-hop> <rt:next-hop>
<rt:outgoing-interface>eth0</rt:outgoing-interface> <rt:outgoing-interface>eth0</rt:outgoing-interface>
</rt:next-hop> </rt:next-hop>
<rt:source-protocol>rt:direct</rt:source-protocol> <rt:source-protocol>rt:direct</rt:source-protocol>
<rt:route-preference>0</rt:route-preference> <rt:route-preference>0</rt:route-preference>
<rt:last-updated>2014-10-24T17:11:27+01:00</rt:last-updated> <rt:last-updated>2015-10-24T17:11:27+02:00</rt:last-updated>
</rt:route> </rt:route>
<rt:route> <rt:route>
<v6ur:destination-prefix> <v6ur:destination-prefix>
2001:db8:0:2::/64 2001:db8:0:2::/64
</v6ur:destination-prefix> </v6ur:destination-prefix>
<rt:next-hop> <rt:next-hop>
<rt:outgoing-interface>eth1</rt:outgoing-interface> <rt:outgoing-interface>eth1</rt:outgoing-interface>
</rt:next-hop> </rt:next-hop>
<rt:source-protocol>rt:direct</rt:source-protocol> <rt:source-protocol>rt:direct</rt:source-protocol>
<rt:route-preference>0</rt:route-preference> <rt:route-preference>0</rt:route-preference>
<rt:last-updated>2014-10-24T17:11:27+01:00</rt:last-updated> <rt:last-updated>2015-10-24T17:11:27+02:00</rt:last-updated>
</rt:route> </rt:route>
<rt:route> <rt:route>
<v6ur:destination-prefix>::/0</v6ur:destination-prefix> <v6ur:destination-prefix>::/0</v6ur:destination-prefix>
<rt:next-hop> <rt:next-hop>
<v6ur:next-hop-address> <v6ur:next-hop-address>
2001:db8:0:1::2 2001:db8:0:1::2
</v6ur:next-hop-address> </v6ur:next-hop-address>
</rt:next-hop> </rt:next-hop>
<rt:source-protocol>rt:static</rt:source-protocol> <rt:source-protocol>rt:static</rt:source-protocol>
<rt:route-preference>5</rt:route-preference> <rt:route-preference>5</rt:route-preference>
<rt:last-updated>2014-10-24T18:02:45+01:00</rt:last-updated> <rt:last-updated>2015-10-24T18:02:45+02:00</rt:last-updated>
</rt:route> </rt:route>
</rt:routes> </rt:routes>
</rt:rib> </rt:rib>
</rt:ribs> </rt:ribs>
</rt:routing-instance> </rt:routing-instance>
</rt:routing-state> </rt:routing-state>
</data> </data>
</rpc-reply> </rpc-reply>
Appendix E. Change Log Appendix E. Change Log
RFC Editor: Remove this section upon publication as an RFC. RFC Editor: Remove this section upon publication as an RFC.
E.1. Changes Between Versions -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- o The leaf "route-preference" was removed from the "routing-
protocol" container in both "routing" and "routing-state". protocol" container in both "routing" and "routing-state".
o The "vrf-routing-instance" identity was added in support of a o The "vrf-routing-instance" identity was added in support of a
common routing-instance type in addition to the "default-routing- common routing-instance type in addition to the "default-routing-
instance". instance".
o Removed "enabled" switch from "routing-protocol". 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 o The container "ribs" was moved under "routing-instance" (in both
"routing" and "routing-state"). "routing" and "routing-state").
o Typedefs "rib-ref" and "rib-state-ref" were removed. o Typedefs "rib-ref" and "rib-state-ref" were removed.
o Removed "recipient-ribs" (both state and configuration). o Removed "recipient-ribs" (both state and configuration).
o Removed "connected-ribs" from "routing-protocol" (both state and o Removed "connected-ribs" from "routing-protocol" (both state and
configuration). configuration).
skipping to change at page 63, line 12 skipping to change at page 62, line 22
rather than list (both config and state). The opposite reference rather than list (both config and state). The opposite reference
from "if:interface" to "rt:routing-instance" was changed to a from "if:interface" to "rt:routing-instance" was changed to a
single leaf (an interface cannot belong to multiple routing single leaf (an interface cannot belong to multiple routing
instances). instances).
o Specification of a default RIB is now a simple flag under "rib" o Specification of a default RIB is now a simple flag under "rib"
(both config and state). (both config and state).
o Default RIBs are marked by a flag in state data. 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 Added Acee as a co-author.
o Removed all traces of route filters. o Removed all traces of route filters.
o Removed numeric IDs of list entries in state data. o Removed numeric IDs of list entries in state data.
o Removed all next-hop cases except "simple-next-hop" and "special- o Removed all next-hop cases except "simple-next-hop" and "special-
next-hop". next-hop".
o Removed feature "multipath-routes". o Removed feature "multipath-routes".
o Augmented "ietf-interfaces" module with a leaf-list of leafrefs o Augmented "ietf-interfaces" module with a leaf-list of leafrefs
pointing form state data of an interface entry to the routing pointing form state data of an interface entry to the routing
instance(s) to which the interface is assigned. 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', o Added 'type' as the second key component of 'routing-protocol',
both in configuration and state data. both in configuration and state data.
o The restriction of no more than one connected RIB per address o The restriction of no more than one connected RIB per address
family was removed. family was removed.
o Removed the 'id' key of routes in RIBs. This list has no keys o Removed the 'id' key of routes in RIBs. This list has no keys
anymore. anymore.
skipping to change at page 64, line 17 skipping to change at page 63, line 26
o Added next-hop lists to state data. o Added next-hop lists to state data.
o Added two cases for specifying next-hops indirectly - via a new o Added two cases for specifying next-hops indirectly - via a new
RIB or a recursive list of next-hops. RIB or a recursive list of next-hops.
o Reorganized next-hop in static routes. o Reorganized next-hop in static routes.
o Removed all 'if-feature' statements from state data. 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 all defaults from state data.
o Removed default from 'cur-hop-limit' in config. 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' o Removed dependency of 'connected-ribs' on the 'multiple-ribs'
feature. feature.
o Removed default value of 'cur-hop-limit' in state data. o Removed default value of 'cur-hop-limit' in state data.
o Moved parts of descriptions and all references on IPv6 RA o Moved parts of descriptions and all references on IPv6 RA
parameters from state data to configuration. parameters from state data to configuration.
o Added reference to RFC 6536 in the Security section. 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 Wrote appendix about minimum implementation.
o Remove "when" statement for IPv6 router interface state data - it o Remove "when" statement for IPv6 router interface state data - it
was dependent on a config value that may not be present. was dependent on a config value that may not be present.
o Extra container for the next-hop list. o Extra container for the next-hop list.
o Names rather than numeric ids are used for referring to list o Names rather than numeric ids are used for referring to list
entries in state data. entries in state data.
skipping to change at page 65, line 14 skipping to change at page 64, line 23
o o
o Removed "if-feature multiple-ribs;" from connected-ribs. o Removed "if-feature multiple-ribs;" from connected-ribs.
o "rib-name" instead of "name" is used as the name of leafref nodes. 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 o "next-hop" instead of "nexthop" or "gateway" used throughout, both
in node names and text. 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 o Removed feature "advanced-router" and introduced two features
instead: "multiple-ribs" and "multipath-routes". instead: "multiple-ribs" and "multipath-routes".
o Unified the keys of config and state versions of "routing- o Unified the keys of config and state versions of "routing-
instance" and "rib" lists. instance" and "rib" lists.
o Numerical identifiers of state list entries are not keys anymore, o Numerical identifiers of state list entries are not keys anymore,
but they are constrained using the "unique" statement. but they are constrained using the "unique" statement.
o Updated acknowledgements. 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 Migrated address families from IANA enumerations to identities.
o Terminology and node names aligned with the I2RS RIB model: router o Terminology and node names aligned with the I2RS RIB model: router
-> routing instance, routing table -> RIB. -> routing instance, routing table -> RIB.
o Introduced uint64 keys for state lists: routing-instance, rib, o Introduced uint64 keys for state lists: routing-instance, rib,
route, nexthop. route, nexthop.
o Described the relationship between system-controlled and user- o Described the relationship between system-controlled and user-
skipping to change at page 66, line 5 skipping to change at page 65, line 13
router". router".
o Made nexthop into a choice in order to allow for nexthop-list o Made nexthop into a choice in order to allow for nexthop-list
(I2RS requirement). (I2RS requirement).
o Added nexthop-list with entries having priorities (backup) and o Added nexthop-list with entries having priorities (backup) and
weights (load balancing). weights (load balancing).
o Updated bibliography references. 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 Added subtree for state data ("/routing-state").
o Terms "system-controlled entry" and "user-controlled entry" o Terms "system-controlled entry" and "user-controlled entry"
defined and used. defined and used.
o New feature "user-defined-routing-tables". Nodes that are useful o New feature "user-defined-routing-tables". Nodes that are useful
only with user-defined routing tables are now conditional. only with user-defined routing tables are now conditional.
o Added grouping "router-id". o Added grouping "router-id".
o In routing tables, "source-protocol" attribute of routes now o In routing tables, "source-protocol" attribute of routes now
reports only protocol type, and its datatype is "identityref". reports only protocol type, and its datatype is "identityref".
o Renamed "main-routing-table" to "default-routing-table". 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 Simplified "must" expression for "main-routing-table".
o Moved per-interface configuration of a new routing protocol under o Moved per-interface configuration of a new routing protocol under
'routing-protocol'. This also affects the 'example-rip' module. '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. 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 <get-reply> in Appendix D was updated: "eth[01]" o The contents of <get-reply> in Appendix D was updated: "eth[01]"
is used as the value of "location", and "forwarding" is on for is used as the value of "location", and "forwarding" is on for
both interfaces and both IPv4 and IPv6. both interfaces and both IPv4 and IPv6.
o The "must" expression for "main-routing-table" was modified to o The "must" expression for "main-routing-table" was modified to
avoid redundant error messages reporting address family mismatch avoid redundant error messages reporting address family mismatch
when "name" points to a non-existent routing table. when "name" points to a non-existent routing table.
o The default behavior for IPv6 RA prefix advertisements was o The default behavior for IPv6 RA prefix advertisements was
clarified. clarified.
o Changed type of "rt:router-id" to "ip:dotted-quad". o Changed type of "rt:router-id" to "ip:dotted-quad".
o Type of "rt:router-id" changed to "yang:dotted-quad". o Type of "rt:router-id" changed to "yang:dotted-quad".
o Fixed missing prefixes in XPath expressions. 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 o Document title changed: "Configuration" was replaced by
"Management". "Management".
o New typedefs "routing-table-ref" and "route-filter-ref". o New typedefs "routing-table-ref" and "route-filter-ref".
o Double slashes "//" were removed from XPath expressions and o Double slashes "//" were removed from XPath expressions and
replaced with the single "/". replaced with the single "/".
o Removed uniqueness requirement for "router-id". o Removed uniqueness requirement for "router-id".
skipping to change at page 67, line 27 skipping to change at page 66, line 36
o Complete data tree is now in Appendix A. o Complete data tree is now in Appendix A.
o Changed type of "source-protocol" from "leafref" to "string". o Changed type of "source-protocol" from "leafref" to "string".
o Clarified the relationship between routing protocol instances and o Clarified the relationship between routing protocol instances and
connected routing tables. connected routing tables.
o Added a must constraint saying that a routing table connected to o Added a must constraint saying that a routing table connected to
the direct pseudo-protocol must not be a main routing table. 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 o Routing tables are now global, i.e., "routing-tables" is a child
of "routing" rather than "router". of "routing" rather than "router".
o "must" statement for "static-routes" changed to "when". o "must" statement for "static-routes" changed to "when".
o Added "main-routing-tables" containing references to main routing o Added "main-routing-tables" containing references to main routing
tables for each address family. tables for each address family.
o Removed the defaults for "address-family" and "safi" and made them o Removed the defaults for "address-family" and "safi" and made them
skipping to change at page 68, line 14 skipping to change at page 67, line 24
o The "direct" pseudo-protocol is always connected to main routing o The "direct" pseudo-protocol is always connected to main routing
tables. tables.
o Entries in the list of connected routing tables renamed from o Entries in the list of connected routing tables renamed from
"routing-table" to "connected-routing-table". "routing-table" to "connected-routing-table".
o Added "must" constraint saying that a routing table must not be o Added "must" constraint saying that a routing table must not be
its own recipient. 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" o Changed "error-tag" for both RPC operations from "missing element"
to "data-missing". to "data-missing".
o Removed the decrementing behavior for advertised IPv6 prefix o Removed the decrementing behavior for advertised IPv6 prefix
parameters "valid-lifetime" and "preferred-lifetime". parameters "valid-lifetime" and "preferred-lifetime".
o Changed the key of the static route lists from "seqno" to "id" o Changed the key of the static route lists from "seqno" to "id"
because the routes needn't be sorted. because the routes needn't be sorted.
o Added 'must' constraint saying that "preferred-lifetime" must not o Added 'must' constraint saying that "preferred-lifetime" must not
be greater than "valid-lifetime". 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 Module "iana-afn-safi" moved to I-D "iana-if-type".
o Removed forwarding table. o Removed forwarding table.
o RPC "get-route" changed to "active-route". Its output is a list o RPC "get-route" changed to "active-route". Its output is a list
of routes (for multi-path routing). of routes (for multi-path routing).
o New RPC "route-count". o New RPC "route-count".
skipping to change at page 69, line 11 skipping to change at page 68, line 22
"ietf-ip". "ietf-ip".
o Added "router-id" leaf. o Added "router-id" leaf.
o Specified the names for IPv4/IPv6 unicast main routing tables. o Specified the names for IPv4/IPv6 unicast main routing tables.
o Route parameter "last-modified" changed to "age". o Route parameter "last-modified" changed to "age".
o Added container "recipient-routing-tables". 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 Added module "ietf-ipv6-unicast-routing".
o The example in Appendix D now uses IP addresses from blocks o The example in Appendix D now uses IP addresses from blocks
reserved for documentation. reserved for documentation.
o Direct routes appear by default in the forwarding table. o Direct routes appear by default in the forwarding table.
o Network layer interfaces must be assigned to a router instance. o Network layer interfaces must be assigned to a router instance.
Additional interface configuration may be present. Additional interface configuration may be present.
skipping to change at page 69, line 35 skipping to change at page 68, line 46
o Additional "must" statements were added. o Additional "must" statements were added.
o The "route-content" grouping for IPv4 and IPv6 unicast now o The "route-content" grouping for IPv4 and IPv6 unicast now
includes the material from the "ietf-routing" version via "uses includes the material from the "ietf-routing" version via "uses
rt:route-content". rt:route-content".
o Explanation of symbols in the tree representation of data model o Explanation of symbols in the tree representation of data model
hierarchy. 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 AFN/SAFI-independent stuff was moved to the "ietf-routing" module.
o Typedefs for AFN and SAFI were placed in a separate "iana-afn- o Typedefs for AFN and SAFI were placed in a separate "iana-afn-
safi" module. safi" module.
o Names of some data nodes were changed, in particular "routing- o Names of some data nodes were changed, in particular "routing-
process" is now "router". process" is now "router".
o The restriction of a single AFN/SAFI per router was lifted. o The restriction of a single AFN/SAFI per router was lifted.
 End of changes. 144 change blocks. 
306 lines changed or deleted 328 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/