draft-ietf-netmod-routing-cfg-21.txt   draft-ietf-netmod-routing-cfg-22.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: September 10, 2016 Cisco Systems Expires: January 6, 2017 Cisco Systems
March 17, 2016 July 05, 2016
A YANG Data Model for Routing Management A YANG Data Model for Routing Management
draft-ietf-netmod-routing-cfg-21 draft-ietf-netmod-routing-cfg-22
Abstract Abstract
This document contains a specification of three YANG modules and one This document contains a specification of three YANG modules and one
submodule. Together they form the core routing data model which submodule. Together they form the core routing data model which
serves as a framework for configuring and managing a routing serves as a framework for configuring and managing a routing
subsystem. It is expected that these modules will be augmented by subsystem. It is expected that these modules will be augmented by
additional YANG modules defining data models for routing protocols, additional YANG modules defining data models for control plane
route filters and other functions. The core routing data model protocols, route filters and other functions. The core routing data
provides common building blocks for such extensions - routes, routing model provides common building blocks for such extensions - routes,
information bases (RIB), and routing protocols. routing information bases (RIB), and control plane protocols.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 September 10, 2016. This Internet-Draft will expire on January 6, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 22 skipping to change at page 2, line 22
2. Terminology and Notation . . . . . . . . . . . . . . . . . . 4 2. Terminology and Notation . . . . . . . . . . . . . . . . . . 4
2.1. Glossary of New Terms . . . . . . . . . . . . . . . . . . 5 2.1. Glossary of New Terms . . . . . . . . . . . . . . . . . . 5
2.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 5 2.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 5
2.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 6 2.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 6
3. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. The Design of the Core Routing Data Model . . . . . . . . . . 7 4. The Design of the Core Routing Data Model . . . . . . . . . . 7
4.1. System-Controlled and User-Controlled List Entries . . . 8 4.1. System-Controlled and User-Controlled List Entries . . . 8
5. Basic Building Blocks . . . . . . . . . . . . . . . . . . . . 9 5. Basic Building Blocks . . . . . . . . . . . . . . . . . . . . 9
5.1. Route . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5.1. Route . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.2. Routing Information Base (RIB) . . . . . . . . . . . . . 9 5.2. Routing Information Base (RIB) . . . . . . . . . . . . . 9
5.3. Routing Protocol . . . . . . . . . . . . . . . . . . . . 10 5.3. Control Plane Protocol . . . . . . . . . . . . . . . . . 10
5.3.1. Routing Pseudo-Protocols . . . . . . . . . . . . . . 10 5.3.1. Routing Pseudo-Protocols . . . . . . . . . . . . . . 10
5.3.2. Defining New Routing Protocols . . . . . . . . . . . 11 5.3.2. Defining New Control Plane Protocols . . . . . . . . 11
5.4. RPC Operations . . . . . . . . . . . . . . . . . . . . . 12 5.4. RPC Operations . . . . . . . . . . . . . . . . . . . . . 12
5.5. Parameters of IPv6 Router Advertisements . . . . . . . . 12 5.5. Parameters of IPv6 Router Advertisements . . . . . . . . 12
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" . . . . . . . . . . . . . . . . . . . . 13 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 . . . . . . . . . 25 8. IPv4 Unicast Routing Management YANG Module . . . . . . . . . 27
9. IPv6 Unicast Routing Management YANG Module . . . . . . . . . 30 9. IPv6 Unicast Routing Management YANG Module . . . . . . . . . 33
9.1. IPv6 Router Advertisements Submodule . . . . . . . . . . 34 9.1. IPv6 Router Advertisements Submodule . . . . . . . . . . 38
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 44 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48
11. Security Considerations . . . . . . . . . . . . . . . . . . . 45 11. Security Considerations . . . . . . . . . . . . . . . . . . . 49
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 46 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 50
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 46 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 50
13.1. Normative References . . . . . . . . . . . . . . . . . . 46 13.1. Normative References . . . . . . . . . . . . . . . . . . 50
13.2. Informative References . . . . . . . . . . . . . . . . . 47 13.2. Informative References . . . . . . . . . . . . . . . . . 51
Appendix A. The Complete Data Trees . . . . . . . . . . . . . . 48 Appendix A. The Complete Data Trees . . . . . . . . . . . . . . 51
A.1. Configuration Data . . . . . . . . . . . . . . . . . . . 48 A.1. Configuration Data . . . . . . . . . . . . . . . . . . . 51
A.2. State Data . . . . . . . . . . . . . . . . . . . . . . . 50 A.2. State Data . . . . . . . . . . . . . . . . . . . . . . . 53
Appendix B. Minimum Implementation . . . . . . . . . . . . . . . 50 Appendix B. Minimum Implementation . . . . . . . . . . . . . . . 55
Appendix C. Example: Adding a New Routing Protocol . . . . . . . 51 Appendix C. Example: Adding a New Control Plane Protocol . . . . 55
Appendix D. Example: NETCONF <get> Reply . . . . . . . . . . . . 53 Appendix D. Example: NETCONF <get> Reply . . . . . . . . . . . . 57
Appendix E. Change Log . . . . . . . . . . . . . . . . . . . . . 59 Appendix E. Change Log . . . . . . . . . . . . . . . . . . . . . 64
E.1. Changes Between Versions -20 and -21 . . . . . . . . . . 59 E.1. Changes Between Versions -21 and -22 . . . . . . . . . . 64
E.2. Changes Between Versions -19 and -20 . . . . . . . . . . 60 E.2. Changes Between Versions -20 and -21 . . . . . . . . . . 64
E.3. Changes Between Versions -18 and -19 . . . . . . . . . . 60 E.3. Changes Between Versions -19 and -20 . . . . . . . . . . 64
E.4. Changes Between Versions -17 and -18 . . . . . . . . . . 60 E.4. Changes Between Versions -18 and -19 . . . . . . . . . . 64
E.5. Changes Between Versions -16 and -17 . . . . . . . . . . 61 E.5. Changes Between Versions -17 and -18 . . . . . . . . . . 65
E.6. Changes Between Versions -15 and -16 . . . . . . . . . . 61 E.6. Changes Between Versions -16 and -17 . . . . . . . . . . 65
E.7. Changes Between Versions -14 and -15 . . . . . . . . . . 62 E.7. Changes Between Versions -15 and -16 . . . . . . . . . . 66
E.8. Changes Between Versions -13 and -14 . . . . . . . . . . 62 E.8. Changes Between Versions -14 and -15 . . . . . . . . . . 66
E.9. Changes Between Versions -12 and -13 . . . . . . . . . . 62 E.9. Changes Between Versions -13 and -14 . . . . . . . . . . 66
E.10. Changes Between Versions -11 and -12 . . . . . . . . . . 63 E.10. Changes Between Versions -12 and -13 . . . . . . . . . . 67
E.11. Changes Between Versions -10 and -11 . . . . . . . . . . 63 E.11. Changes Between Versions -11 and -12 . . . . . . . . . . 67
E.12. Changes Between Versions -09 and -10 . . . . . . . . . . 63 E.12. Changes Between Versions -10 and -11 . . . . . . . . . . 68
E.13. Changes Between Versions -08 and -09 . . . . . . . . . . 64 E.13. Changes Between Versions -09 and -10 . . . . . . . . . . 68
E.14. Changes Between Versions -07 and -08 . . . . . . . . . . 64 E.14. Changes Between Versions -08 and -09 . . . . . . . . . . 68
E.15. Changes Between Versions -06 and -07 . . . . . . . . . . 64 E.15. Changes Between Versions -07 and -08 . . . . . . . . . . 69
E.16. Changes Between Versions -05 and -06 . . . . . . . . . . 64 E.16. Changes Between Versions -06 and -07 . . . . . . . . . . 69
E.17. Changes Between Versions -04 and -05 . . . . . . . . . . 65 E.17. Changes Between Versions -05 and -06 . . . . . . . . . . 69
E.18. Changes Between Versions -03 and -04 . . . . . . . . . . 66 E.18. Changes Between Versions -04 and -05 . . . . . . . . . . 70
E.19. Changes Between Versions -02 and -03 . . . . . . . . . . 66 E.19. Changes Between Versions -03 and -04 . . . . . . . . . . 70
E.20. Changes Between Versions -01 and -02 . . . . . . . . . . 67 E.20. Changes Between Versions -02 and -03 . . . . . . . . . . 71
E.21. Changes Between Versions -00 and -01 . . . . . . . . . . 67 E.21. Changes Between Versions -01 and -02 . . . . . . . . . . 71
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 67 E.22. Changes Between Versions -00 and -01 . . . . . . . . . . 72
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 72
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.
skipping to change at page 3, line 44 skipping to change at page 3, line 45
submodule "ietf-ipv6-router-advertisements" also augments the submodule "ietf-ipv6-router-advertisements" also augments the
"ietf-interfaces" module [RFC7223] with IPv6 router configuration "ietf-interfaces" module [RFC7223] with IPv6 router configuration
variables required by [RFC4861]. 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, control plane protocols, multicast routing, additional address
and advanced functions such as route filtering or policy routing. To families, and advanced functions such as route filtering or policy
this end, it is expected that the core routing data model will be routing. To this end, it is expected that the core routing data
augmented by numerous modules developed by other IETF working groups. model will be augmented by numerous modules developed by other IETF
working groups.
2. Terminology and Notation 2. Terminology and Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
The following terms are defined in [RFC6241]: The following terms are defined in [RFC6241]:
o client, o client,
skipping to change at page 6, line 42 skipping to change at page 6, line 42
o The data model should be suitable for the common address families, o The data model should be suitable for the common address families,
in particular IPv4 and IPv6, and for unicast and multicast in particular IPv4 and IPv6, and for unicast and multicast
routing, as well as Multiprotocol Label Switching (MPLS). routing, as well as Multiprotocol Label Switching (MPLS).
o A simple IP routing system, such as one that uses only static o A simple IP routing system, such as one that uses only static
routing, should be configurable in a simple way, ideally without routing, should be configurable in a simple way, ideally without
any need to develop additional YANG modules. any need to develop additional YANG modules.
o On the other hand, the core routing framework must allow for o On the other hand, the core routing framework must allow for
complicated implementations involving multiple routing information complicated implementations involving multiple routing information
bases (RIB) and multiple routing protocols, as well as controlled bases (RIB) and multiple control plane protocols, as well as
redistributions of routing information. controlled redistributions of routing information.
o Device vendors will want to map the data models built on this o Device vendors will want to map the data models built on this
generic framework to their proprietary data models and generic framework to their proprietary data models and
configuration interfaces. Therefore, the framework should be configuration interfaces. Therefore, the framework should be
flexible enough to facilitate such a mapping and accommodate data flexible enough to facilitate such a mapping and accommodate data
models with different logic. models with different logic.
4. The Design of the Core Routing Data Model 4. The Design of the Core Routing Data Model
The core routing data model consists of three YANG modules and one The core routing data model consists of three YANG modules and one
skipping to change at page 7, line 21 skipping to change at page 7, line 21
routing" module with additional data nodes that are needed for IPv4 routing" module with additional data nodes that are needed for IPv4
and IPv6 unicast routing, respectively. Module "ietf-ipv6-unicast- and IPv6 unicast routing, respectively. Module "ietf-ipv6-unicast-
routing" has a submodule, "ietf-ipv6-router-advertisements", that routing" has a submodule, "ietf-ipv6-router-advertisements", that
defines configuration variables for IPv6 router advertisements as defines configuration variables for IPv6 router advertisements as
required by [RFC4861]. Figures 1 and 2 show abridged views of the required by [RFC4861]. Figures 1 and 2 show abridged views of the
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 router-id? +--rw router-id?
+--rw routing-protocols +--rw control-plane-protocols
| +--rw routing-protocol* [type name] | +--rw control-plane-protocol* [type name]
| +--rw type | +--rw type
| +--rw name | +--rw name
| +--rw description? | +--rw description?
| +--rw static-routes | +--rw static-routes
| | +--rw v6ur:ipv6 | +--rw v6ur:ipv6
| | | ...
| | +--rw v4ur:ipv4
| | ...
| +--rw rip:rip!
| +--rw rip:interfaces
| | ... | | ...
| +--rw rip:update-interval? | +--rw v4ur:ipv4
| ...
+--rw ribs +--rw ribs
+--rw rib* [name] +--rw rib* [name]
+--rw name +--rw name
+--rw address-family? +--rw address-family?
+--rw description? +--rw description?
Figure 1: Configuration data hierarchy. Figure 1: Configuration data hierarchy.
+--ro routing-state +--ro routing-state
+--ro router-id? +--ro router-id?
+--ro interfaces +--ro interfaces
| +--ro interface* | +--ro interface*
+--ro routing-protocols +--ro control-plane-protocols
| +--ro routing-protocol* [type name] | +--ro control-plane-protocol* [type name]
| +--ro type | +--ro type
| +--ro name | +--ro name
+--ro ribs +--ro ribs
+--ro rib* [name] +--ro rib* [name]
+--ro name +--ro name
+--ro address-family +--ro address-family
+--ro default-rib? +--ro default-rib?
+--ro routes +--ro routes
+--ro route* +--ro route*
... ...
Figure 2: State data hierarchy. Figure 2: State data hierarchy.
As can be seen from Figures 1 and 2, the core routing data model As can be seen from Figures 1 and 2, the core routing data model
introduces several generic components of a routing framework: routes, introduces several generic components of a routing framework: routes,
RIBs containing lists of routes, and routing protocols. Section 5 RIBs containing lists of routes, and control plane protocols.
describes these components in more detail. Section 5 describes these components in more detail.
4.1. System-Controlled and User-Controlled List Entries 4.1. System-Controlled and User-Controlled List Entries
The core routing data model defines several lists in the schema tree, The core routing data model defines several lists in the schema tree,
such as "rib", that have to be populated with at least one entry in such as "rib", that have to be populated with at least one entry in
any properly functioning device, and additional entries may be any properly functioning device, and additional entries may be
configured by a client. configured by a client.
In such a list, the server creates the required item as a so-called In such a list, the server creates the required item as a so-called
system-controlled entry in state data, i.e., inside the "routing- system-controlled entry in state data, i.e., inside the "routing-
skipping to change at page 10, line 9 skipping to change at page 10, line 9
5.2. Routing Information Base (RIB) 5.2. Routing Information Base (RIB)
Every implementation of the core routing data model manages one or Every implementation of the core routing data model manages one or
more routing information bases (RIB). A RIB is a list of routes more routing information bases (RIB). A RIB is a list of routes
complemented with administrative data. Each RIB contains only routes complemented with administrative data. Each RIB contains only routes
of one address family. An address family is represented by an of one address family. An address family is represented by an
identity derived from the "rt:address-family" base identity. identity derived from the "rt:address-family" base identity.
In the core routing data model, RIBs are state data represented as In the core routing data model, RIBs are state data represented as
entries of the list "/routing-state/ribs/rib". The contents of RIBs entries of the list "/routing-state/ribs/rib". The contents of RIBs
are controlled and manipulated by routing protocol operations which are controlled and manipulated by control plane protocol operations
may result in route additions, removals and modifications. This also which may result in route additions, removals and modifications.
includes manipulations via the "static" and/or "direct" pseudo- This also includes manipulations via the "static" and/or "direct"
protocols, see Section 5.3.1. pseudo-protocols, see Section 5.3.1.
For every supported address family, exactly one RIB MUST be marked as For every supported address family, exactly one RIB MUST be marked as
the so-called default RIB. Its role is explained in Section 5.3. the so-called default RIB. Its role is explained in Section 5.3.
Simple router implementations that do not advertise the feature Simple router implementations that do not advertise the feature
"multiple-ribs" will typically create one system-controlled RIB per "multiple-ribs" will typically create one system-controlled RIB per
supported address family, and mark it as the default RIB. supported address family, and mark it as the default RIB.
More complex router implementations advertising the "multiple-ribs" More complex router implementations advertising the "multiple-ribs"
feature support multiple RIBs per address family that can be used for feature support multiple RIBs per address family that can be used for
policy routing and other purposes. policy routing and other purposes.
5.3. Routing Protocol 5.3. Control Plane Protocol
The core routing data model provides an open-ended framework for The core routing data model provides an open-ended framework for
defining multiple routing protocol instances. Each routing protocol defining multiple control plane protocol instances, e.g., for Layer 3
instance MUST be assigned a type, which is an identity derived from routing protocols. Each routing protocol instance MUST be assigned a
the "rt:routing-protocol" base identity. The core routing data model type, which is an identity derived from the "rt:control-plane-
defines two identities for the direct and static pseudo-protocols protocol" base identity. The core routing data model defines two
identities for the direct and static pseudo-protocols
(Section 5.3.1). (Section 5.3.1).
Multiple routing protocol instances of the same type MAY be Multiple control plane protocol instances of the same type MAY be
configured. configured.
5.3.1. Routing Pseudo-Protocols 5.3.1. Routing Pseudo-Protocols
The core routing data model defines two special routing protocol The core routing data model defines two special routing protocol
types - "direct" and "static". Both are in fact pseudo-protocols, types - "direct" and "static". Both are in fact pseudo-protocols,
which means they are confined to the local device and do not exchange which means they are confined to the local device and do not exchange
any routing information with adjacent routers. any routing information with adjacent routers.
Every implementation of the core routing data model MUST provide Every implementation of the core routing data model MUST provide
skipping to change at page 11, line 9 skipping to change at page 11, line 9
source of direct routes for all configured address families. Direct source of direct routes for all configured address families. Direct
routes are normally supplied by the operating system kernel, based on routes are normally supplied by the operating system kernel, based on
the configuration of network interface addresses, see Section 6.2. the configuration of network interface addresses, see Section 6.2.
Direct routes MUST be installed in default RIBs of all supported Direct routes MUST be installed in default RIBs of all supported
address families. address families.
A pseudo-protocol of the type "static" allows for specifying routes A pseudo-protocol of the type "static" allows for specifying routes
manually. It MAY be configured in zero or multiple instances, manually. It MAY be configured in zero or multiple instances,
although a typical configuration will have exactly one instance. although a typical configuration will have exactly one instance.
5.3.2. Defining New Routing Protocols 5.3.2. Defining New Control Plane Protocols
It is expected that future YANG modules will create data models for It is expected that future YANG modules will create data models for
additional routing protocol types. Such a new module has to define additional control plane protocol types. Such a new module has to
the protocol-specific configuration and state data, and it has to define the protocol-specific configuration and state data, and it has
integrate it into the core routing framework in the following way: to integrate it into the core routing framework in the following way:
o A new identity MUST be defined for the routing protocol and its o A new identity MUST be defined for the control plane protocol and
base identity MUST be set to "rt:routing-protocol", or to an its base identity MUST be set to "rt:control-plane-protocol", or
identity derived from "rt:routing-protocol". to an identity derived from "rt:control-plane-protocol".
o Additional route attributes MAY be defined, preferably in one o Additional route attributes MAY be defined, preferably in one
place by means of defining a YANG grouping. The new attributes place by means of defining a YANG grouping. The new attributes
have to be inserted by augmenting the definitions of the nodes have to be inserted by augmenting the definitions of the nodes
/rt:routing-state/rt:ribs/rt:rib/rt:routes/rt:route /rt:routing-state/rt:ribs/rt:rib/rt:routes/rt:route
and and
/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 "control-plane-protocol" data
under both "/routing" and "/routing-state". node under both "/routing" and "/routing-state".
By using a "when" statement, the augmented configuration parameters By using a "when" statement, the augmented configuration parameters
and state data specific to the new protocol SHOULD be made 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. protocol" is equal to the new protocol's identity.
It is also RECOMMENDED that protocol-specific data nodes be It is also RECOMMENDED that protocol-specific data nodes be
encapsulated in an appropriately named container with presence. Such encapsulated in an appropriately named container with presence. Such
a container may contain mandatory data nodes that are otherwise a container may contain mandatory data nodes that are otherwise
forbidden at the top level of an augment. forbidden at the top level of an augment.
skipping to change at page 14, line 34 skipping to change at page 14, line 34
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@2016-03-09.yang" <CODE BEGINS> file "ietf-routing@2016-07-01.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";
} }
skipping to change at page 15, line 12 skipping to change at page 15, line 12
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group"; "IETF NETMOD (NETCONF Data Modeling Language) Working Group";
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: Lou Berger WG Chair: Lou Berger
<mailto:lberger@labn.net> <mailto:lberger@labn.net>
WG Chair: Juergen Schoenwaelder
<mailto:j.schoenwaelder@jacobs-university.de>
WG Chair: Kent Watsen WG Chair: Kent Watsen
<mailto:kwatsen@juniper.net> <mailto:kwatsen@juniper.net>
Editor: Ladislav Lhotka Editor: Ladislav Lhotka
<mailto:lhotka@nic.cz> <mailto:lhotka@nic.cz>
Editor: Acee Lindem Editor: Acee Lindem
<mailto:acee@cisco.com>"; <mailto:acee@cisco.com>";
description description
skipping to change at page 15, line 47 skipping to change at page 15, line 44
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 2016-03-09 { revision 2016-07-01 {
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
"This feature indicates that the server supports user-defined "This feature indicates that the server supports user-defined
RIBs. RIBs.
Servers that do not advertise this feature SHOULD provide Servers that do not advertise this feature SHOULD provide
exactly one system-controlled RIB per supported address family exactly one system-controlled RIB per supported address family
and make them also the default RIBs. These RIBs then appear as and make them also the default RIBs. These RIBs then appear as
entries of the list /routing-state/ribs/rib."; entries of the list /routing-state/ribs/rib.";
} }
skipping to change at page 16, line 48 skipping to change at page 16, line 46
description description
"This identity represents IPv4 address family."; "This identity represents IPv4 address family.";
} }
identity ipv6 { identity ipv6 {
base address-family; base address-family;
description description
"This identity represents IPv6 address family."; "This identity represents IPv6 address family.";
} }
identity control-plane-protocol {
description
"Base identity from which control plane protocol identities are
derived.";
}
identity routing-protocol { identity routing-protocol {
base control-plane-protocol;
description description
"Base identity from which routing protocol identities are "Identity from which Layer 3 routing protocol identities are
derived."; derived.";
} }
identity direct { identity direct {
base routing-protocol; base routing-protocol;
description description
"Routing pseudo-protocol that provides routes to directly "Routing pseudo-protocol that provides routes to directly
connected networks."; connected networks.";
} }
identity static { identity static {
skipping to change at page 18, line 40 skipping to change at page 18, line 45
enum receive { enum receive {
description description
"The packet will be received by the local system."; "The packet will be received by the local system.";
} }
} }
description description
"Special next-hop options."; "Special next-hop options.";
} }
} }
grouping next-hop-classifiers {
description
"This grouping provides two next-hop classifiers.";
leaf priority {
type enumeration {
enum primary {
value "1";
description
"Primary next-hop.";
}
enum backup {
value "2";
description
"Backup next-hop.";
}
}
description
"Simple priority for distinguishing between primary and
backup next-hops.
Backup next-hops are used if and only if no primary
next-hops are reachable.";
}
leaf weight {
type uint8;
must ". = 0 or not(../../next-hop/weight = 0)" {
error-message "Illegal combination of zero and non-zero "
+ "next-hop weights.";
description
"Next-hop weights must be either all zero (equal
load-balancing) or all non-zero.";
}
description
"This parameter specifies the weight of the next-hop for load
balancing. The number specifies the relative fraction of the
traffic that will use the corresponding next-hop.
A value of 0 represents equal load-balancing.
If both primary and backup next-hops are present, then the
weights for each priority level are used separately.";
}
}
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.
Modules for address families MUST augment this choice with Modules for address families MUST augment this choice with
the 'next-hop-address' case, which is a leaf containing a the 'next-hop-address' case, which is a leaf containing a
gateway address of that address family. gateway address of that address family.
It is expected that further cases will be added through It is expected that further cases will be added through
augments from other modules, e.g., for Equal-Cost Multipath augments from other modules.";
routing (ECMP).";
leaf outgoing-interface { leaf outgoing-interface {
type if:interface-ref; type if:interface-ref;
description description
"Name of the outgoing interface."; "Name of the outgoing interface.";
} }
case special-next-hop { case special-next-hop {
uses special-next-hop; uses special-next-hop;
} }
case next-hop-list {
container next-hop-list {
description
"Container for multiple next-hops.";
list next-hop {
key "index";
description
"An entry of a next-hop list.";
leaf index {
type string;
description
"An user-specified identifier utilised to uniquely
reference the next-hop entry in the next-hop list.
The value of this index has no semantic meaning
other than for referencing the entry.";
}
choice address-or-interface {
mandatory "true";
description
"Choice between outgoing interface and next-hop
address in next-hop list entries.
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.";
leaf outgoing-interface {
type if:interface-ref;
description
"Name of the outgoing interface.";
}
}
uses next-hop-classifiers;
}
}
}
} }
} }
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.
Modules for address families MUST augment this choice with Modules for address families MUST augment this choice with
the 'next-hop-address' case, which is a leaf containing a the 'next-hop-address' case, which is a leaf containing a
skipping to change at page 19, line 32 skipping to change at page 21, line 17
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.
Modules for address families MUST augment this choice with Modules for address families MUST augment this choice with
the 'next-hop-address' case, which is a leaf containing a the 'next-hop-address' case, which is a leaf containing a
gateway address of that address family. gateway address of that address family.
It is expected that further cases will be added through 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 recursive
next-hops."; next-hops.";
leaf outgoing-interface { leaf outgoing-interface {
type if:interface-state-ref; type if:interface-state-ref;
description description
"Name of the outgoing interface."; "Name of the outgoing interface.";
} }
case special-next-hop { case special-next-hop {
uses special-next-hop; uses special-next-hop;
} }
case next-hop-list {
container next-hop-list {
description
"Container for multiple next-hops.";
list next-hop {
description
"An entry of a next-hop list.";
choice address-or-interface {
mandatory "true";
description
"Choice between outgoing interface and next-hop
address in next-hop list entries.
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.";
leaf outgoing-interface {
type if:interface-state-ref;
description
"Name of the outgoing interface.";
}
}
uses next-hop-classifiers;
}
}
}
} }
} }
grouping route-metadata { grouping route-metadata {
description description
"Common route metadata."; "Common route metadata.";
leaf source-protocol { leaf source-protocol {
type identityref { type identityref {
base routing-protocol; base routing-protocol;
} }
skipping to change at page 20, line 47 skipping to change at page 23, line 12
container interfaces { container interfaces {
description description
"Network layer interfaces used for routing."; "Network layer interfaces used for routing.";
leaf-list interface { leaf-list interface {
type if:interface-state-ref; type if:interface-state-ref;
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 control-plane-protocols {
description description
"Container for the list of routing protocol instances."; "Container for the list of routing protocol instances.";
list routing-protocol { list control-plane-protocol {
key "type name"; key "type name";
description description
"State data of a routing protocol instance. "State data of a control plane protocol instance.
An implementation MUST provide exactly one An implementation MUST provide exactly one
system-controlled instance of the type 'direct'. Other system-controlled instance of the 'direct'
instances MAY be created by configuration."; pseudo-protocol. Instances of other control plane
protocols MAY be created by configuration.";
leaf type { leaf type {
type identityref { type identityref {
base routing-protocol; base control-plane-protocol;
} }
description description
"Type of the routing protocol."; "Type of the control plane protocol.";
} }
leaf name { leaf name {
type string; type string;
description description
"The name of the routing protocol instance. "The name of the control plane protocol instance.
For system-controlled instances this name is persistent, For system-controlled instances this name is persistent,
i.e., it SHOULD NOT change across reboots."; i.e., it SHOULD NOT change across reboots.";
} }
} }
} }
container ribs { container ribs {
description description
"Container for RIBs."; "Container for RIBs.";
list rib { list rib {
skipping to change at page 21, line 47 skipping to change at page 24, line 14
An implementation SHOULD provide one system-controlled An implementation SHOULD provide one system-controlled
default RIB for each supported address family."; default RIB for each supported address family.";
leaf name { leaf name {
type string; type string;
description description
"The name of the RIB."; "The name of the RIB.";
} }
uses address-family; uses address-family;
leaf default-rib { leaf default-rib {
if-feature multiple-ribs; if-feature "multiple-ribs";
type boolean; type boolean;
default "true"; default "true";
description description
"This flag has the value of 'true' if and only if the RIB "This flag has the value of 'true' if and only if the RIB
is the default RIB for the given address family. is the default RIB for the given address family.
A default RIB always receives direct routes. By default A default RIB always receives direct routes. By default
it also receives routes from all routing protocols."; it also receives routes from all routing protocols.";
} }
container routes { container routes {
skipping to change at page 22, line 38 skipping to change at page 25, line 4
uses next-hop-state-content; uses next-hop-state-content;
} }
uses route-metadata; uses route-metadata;
} }
} }
} }
} }
} }
/* Configuration Data */ /* Configuration Data */
container routing { container routing {
description description
"Configuration parameters for the routing subsystem."; "Configuration parameters for the routing subsystem.";
uses router-id { uses router-id {
if-feature router-id; if-feature "router-id";
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.";
} }
container routing-protocols { container control-plane-protocols {
description description
"Configuration of routing protocol instances."; "Configuration of control plane protocol instances.";
list control-plane-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 control plane
instance."; protocol instance.";
leaf type { leaf type {
type identityref { type identityref {
base routing-protocol; base control-plane-protocol;
} }
description description
"Type of the routing protocol - an identity derived from "Type of the control plane protocol - an identity derived
the 'routing-protocol' base identity."; from the 'control-plane-protocol' base identity.";
} }
leaf name { leaf name {
type string; type string;
description description
"An arbitrary name of the routing protocol instance."; "An arbitrary name of the control plane protocol
instance.";
} }
leaf description { leaf description {
type string; type string;
description description
"Textual description of the routing protocol instance."; "Textual description of the control plane protocol
instance.";
} }
container static-routes { container static-routes {
when "../type='rt:static'" { when "../type='rt:static'" {
description description
"This container is only valid for the 'static' routing "This container is only valid for the 'static' routing
protocol."; protocol.";
} }
description description
"Configuration of the 'static' pseudo-protocol. "Configuration of the 'static' pseudo-protocol.
skipping to change at page 25, line 39 skipping to change at page 28, line 5
} }
<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@2016-03-09.yang" <CODE BEGINS> file "ietf-ipv4-unicast-routing@2016-07-01.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 26, line 17 skipping to change at page 28, line 31
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group"; "IETF NETMOD (NETCONF Data Modeling Language) Working Group";
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: Lou Berger WG Chair: Lou Berger
<mailto:lberger@labn.net> <mailto:lberger@labn.net>
WG Chair: Juergen Schoenwaelder
<mailto:j.schoenwaelder@jacobs-university.de>
WG Chair: Kent Watsen WG Chair: Kent Watsen
<mailto:kwatsen@juniper.net> <mailto:kwatsen@juniper.net>
Editor: Ladislav Lhotka Editor: Ladislav Lhotka
<mailto:lhotka@nic.cz> <mailto:lhotka@nic.cz>
Editor: Acee Lindem Editor: Acee Lindem
<mailto:acee@cisco.com>"; <mailto:acee@cisco.com>";
description description
skipping to change at page 26, line 42 skipping to change at page 29, line 4
Copyright (c) 2016 IETF Trust and the persons identified as Copyright (c) 2016 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 2016-03-09 { revision 2016-07-01 {
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;
skipping to change at page 27, line 42 skipping to change at page 30, line 4
} }
augment "/rt:routing-state/rt:ribs/rt:rib/rt:routes/rt:route/" augment "/rt:routing-state/rt:ribs/rt:rib/rt:routes/rt:route/"
+ "rt:next-hop/rt:next-hop-options" { + "rt: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
"Augment 'next-hop-options' in IPv4 unicast routes."; "Augment 'next-hop-options' in IPv4 unicast 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.";
} }
} }
augment "/rt:routing-state/rt:ribs/rt:rib/rt:routes/rt:route/"
+ "rt:next-hop/rt:next-hop-options/rt:next-hop-list/"
+ "rt:next-hop-list/rt:next-hop/rt:address-or-interface" {
when "../../../../../rt:address-family = 'v4ur:ipv4-unicast'" {
description
"This augment is valid only for IPv4 unicast.";
}
description
"This leaf augments the 'next-hop-list' case of IPv4 unicast
routes.";
leaf address {
type inet:ipv4-address;
description
"IPv4 address of the next-hop.";
}
}
/* Configuration data */ /* Configuration data */
augment "/rt:routing/rt:routing-protocols/rt:routing-protocol/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:static-routes" { + "rt:control-plane-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";
description description
skipping to change at page 28, line 40 skipping to change at page 31, line 19
uses rt:next-hop-content { uses rt:next-hop-content {
augment "next-hop-options" { augment "next-hop-options" {
description description
"Augment 'next-hop-options' in IPv4 static routes."; "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.";
} }
} }
augment "next-hop-options/next-hop-list/next-hop-list/"
+ "next-hop/address-or-interface" {
description
"Augment 'next-hop-options' in IPv4 static routes.";
leaf next-hop-address {
type inet:ipv4-address;
description
"IPv4 address of the next-hop.";
}
}
} }
} }
} }
} }
} }
/* RPC operations */ /* RPC operations */
augment "/rt:fib-route/rt:input/rt:destination-address" { augment "/rt:fib-route/rt:input/rt:destination-address" {
when "rt:address-family='v4ur:ipv4-unicast'" { when "rt:address-family='v4ur:ipv4-unicast'" {
skipping to change at page 29, line 46 skipping to change at page 32, line 34
} }
description description
"Augment 'next-hop-options' in the reply to the 'rt:fib-route' "Augment 'next-hop-options' in the reply to 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.";
} }
} }
}
augment "/rt:fib-route/rt:output/rt:route/rt:next-hop/"
+ "rt:next-hop-options/rt:next-hop-list/rt:next-hop-list/"
+ "rt:next-hop/rt:address-or-interface" {
when "../rt:address-family='v4ur:ipv4-unicast'" {
description
"This augment is valid only for IPv4 unicast.";
}
description
"Augment 'next-hop' list entry in the reply to the
'rt:fib-route' operation.";
leaf next-hop-address {
type inet:ipv4-address;
description
"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@2016-03-09.yang" <CODE BEGINS> file "ietf-ipv6-unicast-routing@2016-07-01.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";
} }
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
} }
include ietf-ipv6-router-advertisements { include ietf-ipv6-router-advertisements {
revision-date 2016-03-09; revision-date 2016-07-01;
} }
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group"; "IETF NETMOD (NETCONF Data Modeling Language) Working Group";
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: Lou Berger WG Chair: Lou Berger
<mailto:lberger@labn.net> <mailto:lberger@labn.net>
WG Chair: Juergen Schoenwaelder
<mailto:j.schoenwaelder@jacobs-university.de>
WG Chair: Kent Watsen WG Chair: Kent Watsen
<mailto:kwatsen@juniper.net> <mailto:kwatsen@juniper.net>
Editor: Ladislav Lhotka Editor: Ladislav Lhotka
<mailto:lhotka@nic.cz> <mailto:lhotka@nic.cz>
Editor: Acee Lindem Editor: Acee Lindem
<mailto:acee@cisco.com>"; <mailto:acee@cisco.com>";
description description
skipping to change at page 31, line 28 skipping to change at page 34, line 26
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 2016-03-09 { revision 2016-07-01 {
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;
skipping to change at page 32, line 25 skipping to change at page 35, line 24
} }
description description
"Augment 'next-hop-options' in IPv6 unicast routes."; "Augment 'next-hop-options' in IPv6 unicast 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.";
} }
} }
augment "/rt:routing-state/rt:ribs/rt:rib/rt:routes/rt:route/"
+ "rt:next-hop/rt:next-hop-options/rt:next-hop-list/"
+ "rt:next-hop-list/rt:next-hop/rt:address-or-interface" {
when "../../../../../rt:address-family = 'v6ur:ipv6-unicast'" {
description
"This augment is valid only for IPv6 unicast.";
}
description
"This leaf augments the 'next-hop-list' case of IPv6 unicast
routes.";
leaf address {
type inet:ipv6-address;
description
"IPv6 address of the next-hop.";
}
}
/* Configuration data */ /* Configuration data */
augment "/rt:routing/rt:routing-protocols/rt:routing-protocol/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:static-routes" { + "rt:control-plane-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";
description description
"A 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.";
} }
skipping to change at page 33, line 16 skipping to change at page 36, line 33
uses rt:next-hop-content { uses rt:next-hop-content {
augment "next-hop-options" { augment "next-hop-options" {
description description
"Augment 'next-hop-options' in IPv6 static routes."; "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.";
} }
} }
augment "next-hop-options/next-hop-list/next-hop-list/"
+ "next-hop/address-or-interface" {
description
"Augment 'next-hop-options' in IPv6 static routes.";
leaf next-hop-address {
type inet:ipv6-address;
description
"IPv6 address of the next-hop.";
}
}
} }
} }
} }
} }
} }
/* RPC operations */ /* RPC operations */
augment "/rt:fib-route/rt:input/rt:destination-address" { augment "/rt:fib-route/rt:input/rt:destination-address" {
when "rt:address-family='v6ur:ipv6-unicast'" { when "rt:address-family='v6ur:ipv6-unicast'" {
skipping to change at page 34, line 22 skipping to change at page 37, line 47
} }
description description
"Augment 'next-hop-options' in the reply to the 'rt:fib-route' "Augment 'next-hop-options' in the reply to 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.";
} }
} }
augment "/rt:fib-route/rt:output/rt:route/rt:next-hop/"
+ "rt:next-hop-options/rt:next-hop-list/rt:next-hop-list/"
+ "rt:next-hop/rt:address-or-interface" {
when "../rt:address-family='v6ur:ipv6-unicast'" {
description
"This augment is valid only for IPv6 unicast.";
}
description
"Augment 'next-hop' list entry in the reply to the
'rt:fib-route' operation.";
leaf next-hop-address {
type inet:ipv6-address;
description
"IPv6 address of the next-hop.";
}
}
} }
<CODE ENDS> <CODE ENDS>
9.1. IPv6 Router Advertisements Submodule 9.1. IPv6 Router Advertisements Submodule
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-router-advertisements@2016-03-09.yang" <CODE BEGINS> file "ietf-ipv6-router-advertisements@2016-07-01.yang"
submodule ietf-ipv6-router-advertisements { submodule ietf-ipv6-router-advertisements {
belongs-to ietf-ipv6-unicast-routing { belongs-to ietf-ipv6-unicast-routing {
prefix "v6ur"; prefix "v6ur";
} }
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
} }
skipping to change at page 35, line 9 skipping to change at page 39, line 4
import ietf-ip { import ietf-ip {
prefix "ip"; prefix "ip";
} }
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group"; "IETF NETMOD (NETCONF Data Modeling Language) Working Group";
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: Lou Berger WG Chair: Lou Berger
<mailto:lberger@labn.net> <mailto:lberger@labn.net>
WG Chair: Juergen Schoenwaelder
<mailto:j.schoenwaelder@jacobs-university.de>
WG Chair: Kent Watsen WG Chair: Kent Watsen
<mailto:kwatsen@juniper.net> <mailto:kwatsen@juniper.net>
Editor: Ladislav Lhotka Editor: Ladislav Lhotka
<mailto:lhotka@nic.cz> <mailto:lhotka@nic.cz>
Editor: Acee Lindem Editor: Acee Lindem
<mailto:acee@cisco.com>"; <mailto:acee@cisco.com>";
description description
skipping to change at page 35, line 51 skipping to change at page 39, line 42
'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.";
reference reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6)."; "RFC 4861: Neighbor Discovery for IP version 6 (IPv6).";
revision 2016-03-09 { revision 2016-07-01 {
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";
} }
/* State data */ /* State data */
augment "/if:interfaces-state/if:interface/ip:ipv6" { augment "/if:interfaces-state/if:interface/ip:ipv6" {
description description
skipping to change at page 46, line 19 skipping to change at page 50, line 8
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" parameters and subtrees are the The vulnerable "config true" parameters and subtrees are the
following: following:
/routing/routing-protocols/routing-protocol: This list specifies the /routing/control-plane-protocols/control-plane-protocol: This list
routing protocols configured on a device. specifies the control plane protocols configured on a device.
/routing/ribs/rib: This list specifies the RIBs configured for the /routing/ribs/rib: This list specifies the RIBs configured for the
device. device.
Unauthorised 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
skipping to change at page 49, line 4 skipping to change at page 51, line 49
<http://www.rfc-editor.org/info/rfc7224>. <http://www.rfc-editor.org/info/rfc7224>.
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 router-id? yang:dotted-quad
+--rw routing-protocols
| +--rw routing-protocol* [type name]
| +--rw type identityref
| +--rw name string
| +--rw description? string
| +--rw static-routes
| | +--rw v6ur:ipv6
| | | +--rw v6ur:route* [destination-prefix]
| | | +--rw v6ur:destination-prefix inet:ipv6-prefix
| | | +--rw v6ur:description? string
| | | +--rw v6ur:next-hop
| | | +--rw (v6ur:next-hop-options)
| | | +--:(v6ur:outgoing-interface)
| | | | +--rw v6ur:outgoing-interface? if:interface-ref
| | | +--:(v6ur:special-next-hop)
| | | | +--rw v6ur:special-next-hop? enumeration
| | | +--:(v6ur:next-hop-address)
| | | +--rw v6ur:next-hop-address? inet:ipv6-address
| | +--rw v4ur:ipv4
| | +--rw v4ur:route* [destination-prefix]
| | +--rw v4ur:destination-prefix inet:ipv4-prefix
| | +--rw v4ur:description? string
| | +--rw v4ur:next-hop
| | +--rw (v4ur:next-hop-options)
| | +--:(v4ur:outgoing-interface)
| | | +--rw v4ur:outgoing-interface? if:interface-ref
| | +--:(v4ur:special-next-hop)
| | | +--rw v4ur:special-next-hop? enumeration
| | +--:(v4ur:next-hop-address)
| | +--rw v4ur:next-hop-address? inet:ipv4-address
| +--rw rip:rip!
| +--rw rip:interfaces
| | +--rw rip:interface* [name]
| | +--rw rip:name if:interface-ref
| | +--rw rip:enabled? boolean
| | +--rw rip:metric? rip-metric
| +--rw rip:update-interval? uint8
+--rw ribs
+--rw rib* [name]
+--rw name string
+--rw address-family? identityref
+--rw description? string
A.2. State Data +--rw routing
+--rw router-id? yang:dotted-quad
+--rw control-plane-protocols
| +--rw control-plane-protocol* [type name]
| +--rw type identityref
| +--rw name string
| +--rw description? string
| +--rw static-routes
| +--rw v6ur:ipv6
| | +--rw v6ur:route* [destination-prefix]
| | +--rw v6ur:destination-prefix inet:ipv6-prefix
| | +--rw v6ur:description? string
| | +--rw v6ur:next-hop
| | +--rw (v6ur:next-hop-options)
| | +--:(v6ur:outgoing-interface)
| | | +--rw v6ur:outgoing-interface?
| | +--:(v6ur:special-next-hop)
| | | +--rw v6ur:special-next-hop?
| | +--:(v6ur:next-hop-list)
| | | +--rw v6ur:next-hop-list
| | | +--rw v6ur:next-hop* [index]
| | | +--rw v6ur:index string
| | | +--rw (v6ur:address-or-interface)
| | | | +--:(v6ur:outgoing-interface)
| | | | | +--rw v6ur:outgoing-interface?
| | | | +--:(v6ur:next-hop-address)
| | | | +--rw v6ur:next-hop-address?
| | | +--rw v6ur:priority? enumeration
| | | +--rw v6ur:weight? uint8
| | +--:(v6ur:next-hop-address)
| | +--rw v6ur:next-hop-address?
| +--rw v4ur:ipv4
| +--rw v4ur:route* [destination-prefix]
| +--rw v4ur:destination-prefix inet:ipv4-prefix
| +--rw v4ur:description? string
| +--rw v4ur:next-hop
| +--rw (v4ur:next-hop-options)
| +--:(v4ur:outgoing-interface)
| | +--rw v4ur:outgoing-interface?
| +--:(v4ur:special-next-hop)
| | +--rw v4ur:special-next-hop?
| +--:(v4ur:next-hop-list)
| | +--rw v4ur:next-hop-list
| | +--rw v4ur:next-hop* [index]
| | +--rw v4ur:index string
| | +--rw (v4ur:address-or-interface)
| | | +--:(v4ur:outgoing-interface)
| | | | +--rw v4ur:outgoing-interface?
| | | +--:(v4ur:next-hop-address)
| | | +--rw v4ur:next-hop-address?
| | +--rw v4ur:priority? enumeration
| | +--rw v4ur:weight? uint8
| +--:(v4ur:next-hop-address)
| +--rw v4ur:next-hop-address?
+--rw ribs
+--rw rib* [name]
+--rw name string
+--rw address-family? identityref
+--rw description? string
+--ro routing-state A.2. State Data
+--ro router-id? yang:dotted-quad +--ro routing-state
+--ro interfaces +--ro router-id? yang:dotted-quad
| +--ro interface* if:interface-state-ref +--ro interfaces
+--ro routing-protocols | +--ro interface* if:interface-state-ref
| +--ro routing-protocol* [type name] +--ro control-plane-protocols
| +--ro type identityref | +--ro control-plane-protocol* [type name]
| +--ro name string | +--ro type identityref
+--ro ribs | +--ro name string
+--ro rib* [name] +--ro ribs
+--ro name string +--ro rib* [name]
+--ro address-family identityref +--ro name string
+--ro default-rib? boolean {multiple-ribs}? +--ro address-family identityref
+--ro routes +--ro default-rib? boolean {multiple-ribs}?
+--ro route* +--ro routes
+--ro route-preference? route-preference +--ro route*
+--ro next-hop +--ro route-preference? route-preference
| +--ro (next-hop-options) +--ro next-hop
| +--:(outgoing-interface) | +--ro (next-hop-options)
| | +--ro outgoing-interface? if:interface-state-ref | +--:(outgoing-interface)
| +--:(special-next-hop) | | +--ro outgoing-interface?
| | +--ro special-next-hop? enumeration | +--:(special-next-hop)
| +--:(v6ur:next-hop-address) | | +--ro special-next-hop? enumeration
| | +--ro v6ur:next-hop-address? inet:ipv6-address | +--:(next-hop-list)
| +--:(v4ur:next-hop-address) | | +--ro next-hop-list
| +--ro v4ur:next-hop-address? inet:ipv4-address | | +--ro next-hop*
+--ro source-protocol identityref | | +--ro (address-or-interface)
+--ro active? empty | | | +--:(outgoing-interface)
+--ro last-updated? yang:date-and-time | | | | +--ro outgoing-interface?
+--ro v6ur:destination-prefix? inet:ipv6-prefix | | | +--:(v6ur:address)
+--ro rip:metric? rip-metric | | | | +--ro v6ur:address?
+--ro rip:tag? uint16 | | | +--:(v4ur:address)
+--ro v4ur:destination-prefix? inet:ipv4-prefix | | | +--ro v4ur:address?
| | +--ro priority? enumeration
| | +--ro weight? uint8
| +--:(v6ur:next-hop-address)
| | +--ro v6ur:next-hop-address?
| +--:(v4ur:next-hop-address)
| +--ro v4ur:next-hop-address?
+--ro source-protocol identityref
+--ro active? empty
+--ro last-updated? yang:date-and-time
+--ro v6ur:destination-prefix? inet:ipv6-prefix
+--ro v4ur:destination-prefix? inet:ipv4-prefix
Appendix B. Minimum Implementation 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 RIBs, are intended only for advanced routers. This appendix defined RIBs, are intended only for advanced routers. This appendix
gives basic non-normative guidelines for implementing a bare minimum gives basic non-normative guidelines for implementing a bare minimum
of available functions. Such an implementation may be used for hosts of available functions. Such an implementation may be used for hosts
or very simple routers. or very simple routers.
A minimum implementation does not support the feature "multiple- A minimum implementation does not support the feature "multiple-
ribs". This means that a single system-controlled RIB is available ribs". This means that a single system-controlled RIB is available
for each supported address family - IPv4, IPv6 or both. These RIBs for each supported address family - IPv4, IPv6 or both. These RIBs
are also the default RIBs. No user-controlled RIBs are allowed. are also 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.
Platforms with severely constrained resources may use deviations for Platforms with severely constrained resources may use deviations for
restricting the data model, e.g., limiting the number of "static" restricting the data model, e.g., limiting the number of "static"
routing protocol instances. control plane protocol instances.
Appendix C. Example: Adding a New Routing Protocol Appendix C. Example: Adding a New Control Plane Protocol
This appendix demonstrates how the core routing data model can be This appendix demonstrates how the core routing data model can be
extended to support a new routing protocol. The YANG module extended to support a new control plane protocol. The YANG module
"example-rip" shown below is intended as an illustration rather than "example-rip" shown below is intended as an illustration rather than
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.3.2. specified in [RFC6087]. See also Section 5.3.2.
module example-rip { module example-rip {
namespace "http://example.com/rip"; namespace "http://example.com/rip";
prefix "rip"; prefix "rip";
skipping to change at page 52, line 33 skipping to change at page 56, line 46
uses route-content; uses route-content;
} }
augment "/rt:fib-route/rt:output/rt:route" { augment "/rt:fib-route/rt:output/rt:route" {
description description
"RIP-specific route attributes in the output of 'active-route' "RIP-specific route attributes in the output of 'active-route'
RPC."; RPC.";
uses route-content; uses route-content;
} }
augment "/rt:routing/rt:routing-protocols/rt:routing-protocol" { augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-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"; presence "RIP configuration";
description description
"RIP instance configuration."; "RIP instance configuration.";
container interfaces { container interfaces {
skipping to change at page 54, line 30 skipping to change at page 58, line 42
+--------+--------+ +--------+--------+
eth1|198.51.100.1 eth1|198.51.100.1
|2001:db8:0:2::1 |2001:db8:0:2::1
| |
Figure 3: Example network configuration Figure 3: Example network configuration
A reply to the NETCONF <get> message sent by router "A" would then be A reply to the NETCONF <get> message sent by router "A" would then be
as follows: as follows:
<?xml version="1.0"?> <?xml version="1.0"?>
<rpc-reply <rpc-reply
message-id="101" message-id="101"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
xmlns:v4ur="urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing" xmlns:v4ur="urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing"
xmlns:v6ur="urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing" xmlns:v6ur="urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing"
xmlns:if="urn:ietf:params:xml:ns:yang:ietf-interfaces" xmlns:if="urn:ietf:params:xml:ns:yang:ietf-interfaces"
xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type" xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type"
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>
<if:interfaces> <data>
<if:interface> <if:interfaces>
<if:name>eth0</if:name> <if:interface>
<if:type>ianaift:ethernetCsmacd</if:type> <if:name>eth0</if:name>
<if:description> <if:type>ianaift:ethernetCsmacd</if:type>
Uplink to ISP. <if:description>
</if:description> Uplink to ISP.
<ip:ipv4> </if:description>
<ip:address> <ip:ipv4>
<ip:ip>192.0.2.1</ip:ip> <ip:address>
<ip:prefix-length>24</ip:prefix-length> <ip:ip>192.0.2.1</ip:ip>
</ip:address> <ip:prefix-length>24</ip:prefix-length>
<ip:forwarding>true</ip:forwarding> </ip:address>
</ip:ipv4> <ip:forwarding>true</ip:forwarding>
<ip:ipv6> </ip:ipv4>
<ip:address> <ip:ipv6>
<ip:ip>2001:0db8:0:1::1</ip:ip> <ip:address>
<ip:prefix-length>64</ip:prefix-length> <ip:ip>2001:0db8:0:1::1</ip:ip>
</ip:address> <ip:prefix-length>64</ip:prefix-length>
<ip:forwarding>true</ip:forwarding> </ip:address>
<ip:autoconf> <ip:forwarding>true</ip:forwarding>
<ip:create-global-addresses>false</ip:create-global-addresses> <ip:autoconf>
</ip:autoconf> <ip:create-global-addresses>false</ip:create-global-addresses>
</ip:ipv6> </ip:autoconf>
</if:interface> </ip:ipv6>
<if:interface> </if:interface>
<if:name>eth1</if:name> <if:interface>
<if:type>ianaift:ethernetCsmacd</if:type> <if:name>eth1</if:name>
<if:description> <if:type>ianaift:ethernetCsmacd</if:type>
Interface to the internal network. <if:description>
</if:description> Interface to the internal network.
<ip:ipv4> </if:description>
<ip:address> <ip:ipv4>
<ip:ip>198.51.100.1</ip:ip> <ip:address>
<ip:prefix-length>24</ip:prefix-length> <ip:ip>198.51.100.1</ip:ip>
</ip:address> <ip:prefix-length>24</ip:prefix-length>
<ip:forwarding>true</ip:forwarding> </ip:address>
</ip:ipv4> <ip:forwarding>true</ip:forwarding>
<ip:ipv6> </ip:ipv4>
<ip:address> <ip:ipv6>
<ip:ip>2001:0db8:0:2::1</ip:ip> <ip:address>
<ip:prefix-length>64</ip:prefix-length> <ip:ip>2001:0db8:0:2::1</ip:ip>
</ip:address> <ip:prefix-length>64</ip:prefix-length>
<ip:forwarding>true</ip:forwarding> </ip:address>
<ip:autoconf> <ip:forwarding>true</ip:forwarding>
<ip:create-global-addresses>false</ip:create-global-addresses> <ip:autoconf>
</ip:autoconf> <ip:create-global-addresses>false</ip:create-global-addresses>
<v6ur:ipv6-router-advertisements> </ip:autoconf>
<v6ur:send-advertisements>true</v6ur:send-advertisements> <v6ur:ipv6-router-advertisements>
</v6ur:ipv6-router-advertisements> <v6ur:send-advertisements>true</v6ur:send-advertisements>
</ip:ipv6> </v6ur:ipv6-router-advertisements>
</if:interface> </ip:ipv6>
</if:interfaces> </if:interface>
<if:interfaces-state> </if:interfaces>
<if:interface> <if:interfaces-state>
<if:name>eth0</if:name> <if:interface>
<if:type>ianaift:ethernetCsmacd</if:type> <if:name>eth0</if:name>
<if:phys-address>00:0C:42:E5:B1:E9</if:phys-address> <if:type>ianaift:ethernetCsmacd</if:type>
<if:oper-status>up</if:oper-status> <if:phys-address>00:0C:42:E5:B1:E9</if:phys-address>
<if:statistics> <if:oper-status>up</if:oper-status>
<if:discontinuity-time>2015-10-24T17:11:27+02:00</if:discontinuity-time> <if:statistics>
</if:statistics> <if:discontinuity-time>
<ip:ipv4> 2015-10-24T17:11:27+02:00
<ip:forwarding>true</ip:forwarding> </if:discontinuity-time>
<ip:mtu>1500</ip:mtu> </if:statistics>
<ip:address> <ip:ipv4>
<ip:ip>192.0.2.1</ip:ip> <ip:forwarding>true</ip:forwarding>
<ip:prefix-length>24</ip:prefix-length> <ip:mtu>1500</ip:mtu>
</ip:address> <ip:address>
</ip:ipv4> <ip:ip>192.0.2.1</ip:ip>
<ip:ipv6> <ip:prefix-length>24</ip:prefix-length>
<ip:forwarding>true</ip:forwarding> </ip:address>
<ip:mtu>1500</ip:mtu> </ip:ipv4>
<ip:address> <ip:ipv6>
<ip:ip>2001:0db8:0:1::1</ip:ip> <ip:forwarding>true</ip:forwarding>
<ip:prefix-length>64</ip:prefix-length> <ip:mtu>1500</ip:mtu>
</ip:address> <ip:address>
<v6ur:ipv6-router-advertisements> <ip:ip>2001:0db8:0:1::1</ip:ip>
<v6ur:send-advertisements>true</v6ur:send-advertisements> <ip:prefix-length>64</ip:prefix-length>
<v6ur:prefix-list> </ip:address>
<v6ur:prefix> <v6ur:ipv6-router-advertisements>
<v6ur:prefix-spec>2001:db8:0:2::/64</v6ur:prefix-spec> <v6ur:send-advertisements>true</v6ur:send-advertisements>
</v6ur:prefix> <v6ur:prefix-list>
</v6ur:prefix-list> <v6ur:prefix>
</v6ur:ipv6-router-advertisements> <v6ur:prefix-spec>2001:db8:0:2::/64</v6ur:prefix-spec>
</ip:ipv6> </v6ur:prefix>
</if:interface> </v6ur:prefix-list>
<if:interface> </v6ur:ipv6-router-advertisements>
<if:name>eth1</if:name> </ip:ipv6>
<if:type>ianaift:ethernetCsmacd</if:type> </if:interface>
<if:phys-address>00:0C:42:E5:B1:EA</if:phys-address> <if:interface>
<if:oper-status>up</if:oper-status> <if:name>eth1</if:name>
<if:statistics> <if:type>ianaift:ethernetCsmacd</if:type>
<if:discontinuity-time>2015-10-24T17:11:29+02:00</if:discontinuity-time> <if:phys-address>00:0C:42:E5:B1:EA</if:phys-address>
</if:statistics> <if:oper-status>up</if:oper-status>
<ip:ipv4> <if:statistics>
<ip:forwarding>true</ip:forwarding> <if:discontinuity-time>
<ip:mtu>1500</ip:mtu> 2015-10-24T17:11:29+02:00
<ip:address> </if:discontinuity-time>
<ip:ip>198.51.100.1</ip:ip> </if:statistics>
<ip:prefix-length>24</ip:prefix-length> <ip:ipv4>
</ip:address> <ip:forwarding>true</ip:forwarding>
</ip:ipv4> <ip:mtu>1500</ip:mtu>
<ip:ipv6> <ip:address>
<ip:forwarding>true</ip:forwarding> <ip:ip>198.51.100.1</ip:ip>
<ip:mtu>1500</ip:mtu> <ip:prefix-length>24</ip:prefix-length>
<ip:address> </ip:address>
<ip:ip>2001:0db8:0:2::1</ip:ip> </ip:ipv4>
<ip:prefix-length>64</ip:prefix-length> <ip:ipv6>
</ip:address> <ip:forwarding>true</ip:forwarding>
<v6ur:ipv6-router-advertisements> <ip:mtu>1500</ip:mtu>
<v6ur:send-advertisements>true</v6ur:send-advertisements> <ip:address>
<v6ur:prefix-list> <ip:ip>2001:0db8:0:2::1</ip:ip>
<v6ur:prefix> <ip:prefix-length>64</ip:prefix-length>
<v6ur:prefix-spec>2001:db8:0:2::/64</v6ur:prefix-spec> </ip:address>
</v6ur:prefix> <v6ur:ipv6-router-advertisements>
</v6ur:prefix-list> <v6ur:send-advertisements>true</v6ur:send-advertisements>
</v6ur:ipv6-router-advertisements> <v6ur:prefix-list>
</ip:ipv6> <v6ur:prefix>
</if:interface> <v6ur:prefix-spec>2001:db8:0:2::/64</v6ur:prefix-spec>
</if:interfaces-state> </v6ur:prefix>
<rt:routing> </v6ur:prefix-list>
<rt:router-id>192.0.2.1</rt:router-id> </v6ur:ipv6-router-advertisements>
<rt:routing-protocols> </ip:ipv6>
<rt:routing-protocol> </if:interface>
<rt:type>rt:static</rt:type> </if:interfaces-state>
<rt:name>st0</rt:name> <rt:routing>
<rt:description> <rt:router-id>192.0.2.1</rt:router-id>
Static routing is used for the internal network. <rt:control-plane-protocols>
</rt:description> <rt:control-plane-protocol>
<rt:static-routes> <rt:type>rt:static</rt:type>
<v4ur:ipv4> <rt:name>st0</rt:name>
<v4ur:route> <rt:description>
Static routing is used for the internal network.
</rt:description>
<rt:static-routes>
<v4ur:ipv4>
<v4ur:route>
<v4ur:destination-prefix>0.0.0.0/0</v4ur:destination-prefix>
<v4ur:next-hop>
<v4ur:next-hop-address>192.0.2.2</v4ur:next-hop-address>
</v4ur:next-hop>
</v4ur:route>
</v4ur:ipv4>
<v6ur:ipv6>
<v6ur:route>
<v6ur:destination-prefix>::/0</v6ur:destination-prefix>
<v6ur:next-hop>
<v6ur:next-hop-address>2001:db8:0:1::2</v6ur:next-hop-address>
</v6ur:next-hop>
</v6ur:route>
</v6ur:ipv6>
</rt:static-routes>
</rt:control-plane-protocol>
</rt:control-plane-protocols>
</rt:routing>
<rt:routing-state>
<rt:interfaces>
<rt:interface>eth0</rt:interface>
<rt:interface>eth1</rt:interface>
</rt:interfaces>
<rt:control-plane-protocols>
<rt:control-plane-protocol>
<rt:type>rt:static</rt:type>
<rt:name>st0</rt:name>
</rt:control-plane-protocol>
</rt:control-plane-protocols>
<rt:ribs>
<rt:rib>
<rt:name>ipv4-master</rt:name>
<rt:address-family>v4ur:ipv4-unicast</rt:address-family>
<rt:default-rib>true</rt:default-rib>
<rt:routes>
<rt:route>
<v4ur:destination-prefix>192.0.2.1/24</v4ur:destination-prefix>
<rt:next-hop>
<rt:outgoing-interface>eth0</rt:outgoing-interface>
</rt:next-hop>
<rt:route-preference>0</rt:route-preference>
<rt:source-protocol>rt:direct</rt:source-protocol>
<rt:last-updated>2015-10-24T17:11:27+02:00</rt:last-updated>
</rt:route>
<rt:route>
<v4ur:destination-prefix>
198.51.100.0/24
</v4ur:destination-prefix>
<rt:next-hop>
<rt:outgoing-interface>eth1</rt:outgoing-interface>
</rt:next-hop>
<rt:source-protocol>rt:direct</rt:source-protocol>
<rt:route-preference>0</rt:route-preference>
<rt:last-updated>2015-10-24T17:11:27+02:00</rt:last-updated>
</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>
<v4ur:next-hop> <rt:source-protocol>rt:static</rt:source-protocol>
<rt:route-preference>5</rt:route-preference>
<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>
</v4ur:next-hop> </rt:next-hop>
</v4ur:route> <rt:last-updated>2015-10-24T18:02:45+02:00</rt:last-updated>
</v4ur:ipv4> </rt:route>
<v6ur:ipv6> </rt:routes>
<v6ur:route> </rt:rib>
<rt:rib>
<rt:name>ipv6-master</rt:name>
<rt:address-family>v6ur:ipv6-unicast</rt:address-family>
<rt:default-rib>true</rt:default-rib>
<rt:routes>
<rt:route>
<v6ur:destination-prefix>
2001:db8:0:1::/64
</v6ur:destination-prefix>
<rt:next-hop>
<rt:outgoing-interface>eth0</rt:outgoing-interface>
</rt:next-hop>
<rt:source-protocol>rt:direct</rt:source-protocol>
<rt:route-preference>0</rt:route-preference>
<rt:last-updated>2015-10-24T17:11:27+02:00</rt:last-updated>
</rt:route>
<rt:route>
<v6ur:destination-prefix>
2001:db8:0:2::/64
</v6ur:destination-prefix>
<rt:next-hop>
<rt:outgoing-interface>eth1</rt:outgoing-interface>
</rt:next-hop>
<rt:source-protocol>rt:direct</rt:source-protocol>
<rt:route-preference>0</rt:route-preference>
<rt:last-updated>2015-10-24T17:11:27+02:00</rt:last-updated>
</rt:route>
<rt:route>
<v6ur:destination-prefix>::/0</v6ur:destination-prefix> <v6ur:destination-prefix>::/0</v6ur:destination-prefix>
<v6ur:next-hop> <rt:next-hop>
<v6ur:next-hop-address>2001:db8:0:1::2</v6ur:next-hop-address> <v6ur:next-hop-address>
</v6ur:next-hop> 2001:db8:0:1::2
</v6ur:route> </v6ur:next-hop-address>
</v6ur:ipv6> </rt:next-hop>
</rt:static-routes> <rt:source-protocol>rt:static</rt:source-protocol>
</rt:routing-protocol> <rt:route-preference>5</rt:route-preference>
</rt:routing-protocols> <rt:last-updated>2015-10-24T18:02:45+02:00</rt:last-updated>
</rt:routing> </rt:route>
<rt:routing-state> </rt:routes>
<rt:interfaces> </rt:rib>
<rt:interface>eth0</rt:interface> </rt:ribs>
<rt:interface>eth1</rt:interface> </rt:routing-state>
</rt:interfaces> </data>
<rt:routing-protocols> </rpc-reply>
<rt:routing-protocol>
<rt:type>rt:static</rt:type>
<rt:name>st0</rt:name>
</rt:routing-protocol>
</rt:routing-protocols>
<rt:ribs>
<rt:rib>
<rt:name>ipv4-master</rt:name>
<rt:address-family>v4ur:ipv4-unicast</rt:address-family>
<rt:default-rib>true</rt:default-rib>
<rt:routes>
<rt:route>
<v4ur:destination-prefix>192.0.2.1/24</v4ur:destination-prefix>
<rt:next-hop>
<rt:outgoing-interface>eth0</rt:outgoing-interface>
</rt:next-hop>
<rt:route-preference>0</rt:route-preference>
<rt:source-protocol>rt:direct</rt:source-protocol>
<rt:last-updated>2015-10-24T17:11:27+02:00</rt:last-updated>
</rt:route>
<rt:route>
<v4ur:destination-prefix>198.51.100.0/24</v4ur:destination-prefix>
<rt:next-hop>
<rt:outgoing-interface>eth1</rt:outgoing-interface>
</rt:next-hop>
<rt:source-protocol>rt:direct</rt:source-protocol>
<rt:route-preference>0</rt:route-preference>
<rt:last-updated>2015-10-24T17:11:27+02:00</rt:last-updated>
</rt:route>
<rt:route>
<v4ur:destination-prefix>0.0.0.0/0</v4ur:destination-prefix>
<rt:source-protocol>rt:static</rt:source-protocol>
<rt:route-preference>5</rt:route-preference>
<rt:next-hop>
<v4ur:next-hop-address>192.0.2.2</v4ur:next-hop-address>
</rt:next-hop>
<rt:last-updated>2015-10-24T18:02:45+02:00</rt:last-updated>
</rt:route>
</rt:routes>
</rt:rib>
<rt:rib>
<rt:name>ipv6-master</rt:name>
<rt:address-family>v6ur:ipv6-unicast</rt:address-family>
<rt:default-rib>true</rt:default-rib>
<rt:routes>
<rt:route>
<v6ur:destination-prefix>2001:db8:0:1::/64</v6ur:destination-prefix>
<rt:next-hop>
<rt:outgoing-interface>eth0</rt:outgoing-interface>
</rt:next-hop>
<rt:source-protocol>rt:direct</rt:source-protocol>
<rt:route-preference>0</rt:route-preference>
<rt:last-updated>2015-10-24T17:11:27+02:00</rt:last-updated>
</rt:route>
<rt:route>
<v6ur:destination-prefix>2001:db8:0:2::/64</v6ur:destination-prefix>
<rt:next-hop>
<rt:outgoing-interface>eth1</rt:outgoing-interface>
</rt:next-hop>
<rt:source-protocol>rt:direct</rt:source-protocol>
<rt:route-preference>0</rt:route-preference>
<rt:last-updated>2015-10-24T17:11:27+02:00</rt:last-updated>
</rt:route>
<rt:route>
<v6ur:destination-prefix>::/0</v6ur:destination-prefix>
<rt:next-hop>
<v6ur:next-hop-address>2001:db8:0:1::2</v6ur:next-hop-address>
</rt:next-hop>
<rt:source-protocol>rt:static</rt:source-protocol>
<rt:route-preference>5</rt:route-preference>
<rt:last-updated>2015-10-24T18:02:45+02:00</rt:last-updated>
</rt:route>
</rt:routes>
</rt:rib>
</rt:ribs>
</rt:routing-state>
</data>
</rpc-reply>
<!-- Local Variables: --> <!-- Local Variables: -->
<!-- nxml-child-indent: 1 --> <!-- nxml-child-indent: 1 -->
<!-- End: --> <!-- End: -->
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 -20 and -21 E.1. Changes Between Versions -21 and -22
o Added "next-hop-list" as a new case of the "next-hop-options"
choice.
o Renamed "routing protocol" to "control plane protocol" in both the
YANG modules and I-D text.
E.2. Changes Between Versions -20 and -21
o Routing instances were removed. o Routing instances were removed.
o IPv6 RA parameters were moved to the "ietf-ipv6-router- o IPv6 RA parameters were moved to the "ietf-ipv6-router-
advertisements". advertisements".
E.2. Changes Between Versions -19 and -20 E.3. Changes Between Versions -19 and -20
o Assignment of L3 interfaces to routing instances is now part of o Assignment of L3 interfaces to routing instances is now part of
interface configuration. interface configuration.
o Next-hop options in configuration were aligned with state data. o Next-hop options in configuration were aligned with state data.
o It is recommended to enclose protocol-specific configuration in a o It is recommended to enclose protocol-specific configuration in a
presence container. presence container.
E.3. Changes Between Versions -18 and -19 E.4. 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.4. Changes Between Versions -17 and -18 E.5. 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 61, line 5 skipping to change at page 65, line 37
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.5. Changes Between Versions -16 and -17 E.6. 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.6. Changes Between Versions -15 and -16 E.7. 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 62, line 9 skipping to change at page 66, line 40
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.7. Changes Between Versions -14 and -15 E.8. 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.8. Changes Between Versions -13 and -14 E.9. 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.9. Changes Between Versions -12 and -13 E.10. 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 63, line 5 skipping to change at page 67, line 37
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.10. Changes Between Versions -11 and -12 E.11. 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.11. Changes Between Versions -10 and -11 E.12. 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 63, line 42 skipping to change at page 68, line 29
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.12. Changes Between Versions -09 and -10 E.13. 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.13. Changes Between Versions -08 and -09 E.14. Changes Between Versions -08 and -09
o Fixed "must" expression 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.14. Changes Between Versions -07 and -08 E.15. Changes Between Versions -07 and -08
o Changed reference from RFC6021 to RFC6021bis. o Changed reference from RFC6021 to RFC6021bis.
E.15. Changes Between Versions -06 and -07 E.16. 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.16. Changes Between Versions -05 and -06 E.17. 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 65, line 15 skipping to change at page 70, line 5
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.17. Changes Between Versions -04 and -05 E.18. 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 66, line 5 skipping to change at page 70, line 40
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.18. Changes Between Versions -03 and -04 E.19. 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.19. Changes Between Versions -02 and -03 E.20. 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 67, line 5 skipping to change at page 71, line 37
"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.20. Changes Between Versions -01 and -02 E.21. 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 67, line 29 skipping to change at page 72, line 12
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.21. Changes Between Versions -00 and -01 E.22. 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. 111 change blocks. 
494 lines changed or deleted 728 lines changed or added

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