draft-ietf-i2rs-rib-data-model-01.txt   draft-ietf-i2rs-rib-data-model-02.txt 
Network Working Group L. Wang Network Working Group L. Wang
Internet-Draft Huawei Internet-Draft Individual
Intended status: Standards Track H. Ananthakrishnan Intended status: Standards Track H. Ananthakrishnan
Expires: April 1, 2016 Packet Design Expires: April 20, 2016 Packet Design
M. Chen M. Chen
Huawei Huawei
A. Dass A. Dass
S. Kini S. Kini
Ericsson Ericsson
N. Bahadur N. Bahadur
Bracket Computing Bracket Computing
September 29, 2015 October 18, 2015
A YANG Data Model for Routing Information Base (RIB) A YANG Data Model for Routing Information Base (RIB)
draft-ietf-i2rs-rib-data-model-01 draft-ietf-i2rs-rib-data-model-02
Abstract Abstract
This document defines a YANG data model for Routing Information Base This document defines a YANG data model for Routing Information Base
(RIB) that aligns with the I2RS RIB information model. (RIB) that aligns with the I2RS RIB information model.
Requirements Language Requirements Language
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
skipping to change at page 1, line 45 skipping to change at page 1, line 45
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 April 1, 2016. This Internet-Draft will expire on April 20, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 26 skipping to change at page 2, line 26
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Definitions and Acronyms . . . . . . . . . . . . . . . . 3 1.1. Definitions and Acronyms . . . . . . . . . . . . . . . . 3
1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3
2. Model Structure . . . . . . . . . . . . . . . . . . . . . . . 3 2. Model Structure . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. RIB Capability . . . . . . . . . . . . . . . . . . . . . 5 2.1. RIB Capability . . . . . . . . . . . . . . . . . . . . . 7
2.2. Routing Instance and Rib . . . . . . . . . . . . . . . . 6 2.2. Routing Instance and Rib . . . . . . . . . . . . . . . . 7
2.3. Route . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.3. Route . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.4. Nexthop . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.4. Nexthop . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.5. Notifications . . . . . . . . . . . . . . . . . . . . . . 12 2.5. RPC Operations . . . . . . . . . . . . . . . . . . . . . 14
3. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 14 2.6. Notifications . . . . . . . . . . . . . . . . . . . . . . 16
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 3. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 18
5. Security Considerations . . . . . . . . . . . . . . . . . . . 37 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 58
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 5. Security Considerations . . . . . . . . . . . . . . . . . . . 58
6.1. Normative References . . . . . . . . . . . . . . . . . . 37 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 58
6.2. Informative References . . . . . . . . . . . . . . . . . 37 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 59
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 38 7.1. Normative References . . . . . . . . . . . . . . . . . . 59
7.2. Informative References . . . . . . . . . . . . . . . . . 59
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 59
1. Introduction 1. Introduction
The Interface to the Routing System (I2RS) The Interface to the Routing System (I2RS)
[I-D.ietf-i2rs-architecture] provides read and write access to the [I-D.ietf-i2rs-architecture] provides read and write access to the
information and state within the routing process that exists inside information and state within the routing process that exists inside
the routing elements, this is achieved via the protocol message the routing elements, this is achieved via the protocol message
exchange between I2RS clients and I2RS agents associated with the exchange between I2RS clients and I2RS agents associated with the
routing system. One of the functions of I2RS is to read and write routing system. One of the functions of I2RS is to read and write
data of Routing Information Base (RIB). data of Routing Information Base (RIB).
[I-D.ietf-i2rs-usecase-reqs-summary] introduces a set of RIB use [I-D.ietf-i2rs-usecase-reqs-summary] introduces a set of RIB use
cases and the RIB information model is defined in cases and the RIB information model is defined in
[I-D.ietf-i2rs-rib-info-model]. [I-D.ietf-i2rs-rib-info-model].
This document defines a YANG [RFC6020][RFC6021] data model for the This document defines a YANG [RFC6020][RFC6991] data model for the
RIB that satisfies the RIB use cases and aligns with the RIB RIB that satisfies the RIB use cases and aligns with the RIB
information model. information model.
1.1. Definitions and Acronyms 1.1. Definitions and Acronyms
RIB: Routing Information Base RIB: Routing Information Base
Information Model (IM): An abstract model of a conceptual domain, Information Model (IM): An abstract model of a conceptual domain,
independent of a specific implementation or data representation. independent of a specific implementation or data representation.
skipping to change at page 3, line 43 skipping to change at page 3, line 43
o Ellipsis ("...") stands for contents of subtrees that are not o Ellipsis ("...") stands for contents of subtrees that are not
shown. shown.
2. Model Structure 2. Model Structure
The following figure shows an overview of structure tree of the i2rs- The following figure shows an overview of structure tree of the i2rs-
rib module. To give a whole view of the structure tree, some details rib module. To give a whole view of the structure tree, some details
of the tree are omitted. The detail are introduced in the following of the tree are omitted. The detail are introduced in the following
sub-sections. sub-sections.
module: i2rs-rib module: i2rs-rib
+--rw nexthop-capacity +--rw routing-instance
| ... +--rw name string
+--rw nexthop-tunnel-encap-capacity +--rw interface-list* [name]
| ... | +--rw name if:interface-ref
+--rw routing-instance +--rw router-id? yang:dotted-quad
+--rw instance-name string +--rw lookup-limit? uint8
+--rw interface-list* [name] +--rw rib-list* [name]
| +--rw name if:interface-ref +--rw name string
+--rw router-id? yang:dotted-quad +--rw rib-family rib-family-def
+--rw rib-list* [rib-name] +--rw enable-ip-rpf-check? boolean
+--rw rib-name string +--rw route-list* [route-index]
+--rw rib-family rib-family-def +--rw route-index uint64
+--rw enable-ip-rpf-check? boolean +--rw route-type route-type-def
+--rw route-list* [route-index] +--rw match
+--rw route-index uint64 | +--rw (rib-route-type)?
+--rw route-type route-type-def | +--:(ipv4)
+--rw match | | ...
| +--rw (rib-route-type)? | +--:(ipv6)
| +--:(ipv4) | | ...
| | ... | +--:(mpls-route)
| +--:(ipv6) | | ...
| | ... | +--:(mac-route)
| +--:(mpls-route) | | ...
| | ... | +--:(interface-route)
| +--:(mac-route) | ...
| | ... +--rw nexthop
| +--:(interface-route) | +--rw nexthop-id uint32
| ... | +--rw sharing-flag boolean
+--rw nexthop | +--rw (nexthop-type)?
| +--rw nexthop-id uint32 | +--:(nexthop-base)
| +--rw (nexthop-type)? | | ...
| +--:(nexthop-base) | +--:(nexthop-chain) {nexthop-chain}?
| | ... | | ...
| +--:(nexthop-protection) | +--:(nexthop-protection) {nexthop-protection}?
| | ... | | ...
| +--:(nexthop-load-balance) | +--:(nexthop-load-balance) {nexthop-load-balance}?
| | ... | | ...
| +--:(nexthop-replicate) | +--:(nexthop-replicates) {nexthop-replicates}?
| ... | ...
+--rw route-statistic +--rw route-statistic
| ... | ...
+--rw route-attributes +--rw route-attributes
| +--rw route-preference uint32 | ...
| +--rw local-only boolean +--rw route-vendor-attributes
| +--rw address-family-route-attributes rpcs:
| +--rw (route-type)? +---x rib-add
| +--:(ip-route-attributes) | +--ro input
| +--:(mpls-route-attributes) | | +--ro rib-name string
| +--:(eThernet-route-attributes) | | +--ro rib-family rib-family-def
+--rw route-vendor-attributes | | +--ro enable-ip-rpf-check? boolean
notifications: | +--ro output
+---n nexthop-resolution-status-change | +--ro result boolean
| +--ro nexthop +---x rib-delete
| | +--ro nexthop-id uint32 | +--ro input
| | +--ro (nexthop-type)? | | +--ro rib-name string
| | +--:(nexthop-base) | +--ro output
| | | ... | +--ro result boolean
+---x route-add
| | +--:(nexthop-protection) | +--ro input
| | | ... | | +--ro rib-name string
| | +--:(nexthop-load-balance) | | +--ro routes
| | | ... | | +--ro route-list* [route-index]
| | +--:(nexthop-replicate) | | ...
| | ... | +--ro output
| +--ro nexthop-state nexthop-state-def | +--ro result boolean
+---n route-change +---x route-delete
+--ro instance-name string | +--ro input
+--ro rib-name string | | +--ro rib-name string
+--ro rib-family rib-family-def | | +--ro routes
+--ro route-index uint64 | | +--ro route-list* [route-index]
+--ro route-type route-type-def | | ...
+--ro match | +--ro output
| +--ro (rib-route-type)? | +--ro result boolean
| +--:(ipv4) +---x route-update
| | ... | +--ro input
| +--:(ipv6) | | +--ro rib-name string
| | ... | | +--ro (match-conditions)?
| +--:(mpls-route) | | +--:(match-route-prefix)
| | +--ro mpls-label uint32 | | | ...
| +--:(mac-route) | | +--:(match-route-attributes)
| | +--ro mac-address uint32 | | | ...
| +--:(interface-route) | | +--:(match-nexthop)
| +--ro interface-identifier if:interface-ref | | ...
+--ro route-installed-state route-installed-state-def | +--ro output
+--ro route-state route-state-def | +--ro result boolean
+--ro route-reason route-reason-def +---x nh-add
| +--ro input
| | +--ro rib-name string
| | +--ro nexthop-id uint32
| | +--ro sharing-flag boolean
| | +--ro (nexthop-type)?
| | +--:(nexthop-base)
| | | ...
| | +--:(nexthop-chain) {nexthop-chain}?
| | | ...
| | +--:(nexthop-protection) {nexthop-protection}?
| | | ...
| | +--:(nexthop-load-balance) {nexthop-load-balance}?
| | | ...
| | +--:(nexthop-replicates) {nexthop-replicates}?
| | ...
| +--ro output
| +--ro result boolean
| +--ro nexthop-id uint32
+---x nh-delete
+--ro input
| +--ro rib-name string
| +--ro (nexthop-context-or-id)?
| +--:(nexthop-context)
| | ...
| +--:(nexthop-identifier)
| +--ro nexthop-identifer uint32
+--ro output
+--ro result boolean
notifications:
+---n nexthop-resolution-status-change
| +--ro nexthop
| | +--ro nexthop-id uint32
| | +--ro sharing-flag boolean
| | +--ro (nexthop-type)?
| | +--:(nexthop-base)
| | | ...
| | +--:(nexthop-chain) {nexthop-chain}?
| | | ...
| | +--:(nexthop-protection) {nexthop-protection}?
| | | ...
| | +--:(nexthop-load-balance) {nexthop-load-balance}?
| | | ...
| | +--:(nexthop-replicates) {nexthop-replicates}?
| | ...
| +--ro nexthop-state nexthop-state-def
+---n route-change
+--ro rib-name string
+--ro rib-family rib-family-def
+--ro route-index uint64
+--ro route-type route-type-def
+--ro match
| +--ro (rib-route-type)?
| +--:(ipv4)
| | ...
| +--:(ipv6)
| | ...
| +--:(mpls-route)
| | ...
| +--:(mac-route)
| | ...
| +--:(interface-route)
| ...
+--ro route-installed-state route-installed-state-def
+--ro route-state route-state-def
+--ro route-reason route-reason-def
Figure 1 Overview of I2RS module Figure 1: Overview of I2RS Rib Module Structure
2.1. RIB Capability 2.1. RIB Capability
RIB capability negotiation is very important because not all of the RIB capability negotiation is very important because not all of the
hardware will be able to support all kinds of nexthops and there hardware will be able to support all kinds of nexthops and there
should be a limitation on how many levels of lookup can be should be a limitation on how many levels of lookup can be
practically performed. Therefore, a RIB data model MUST specify a practically performed. Therefore, a RIB data model MUST specify a
way for an external entity to learn about the functional capabilities way for an external entity to learn about the functional capabilities
of a network device. of a network device.
At the same time, nexthop chains can be used to specify multiple At the same time, nexthop chains can be used to specify multiple
headers over a packet, before that particular packet is forwarded. headers over a packet, before that particular packet is forwarded.
Not every network device will be able to support all kinds of nexthop Not every network device will be able to support all kinds of nexthop
chains along with the arbitrary number of headers which are chained chains along with the arbitrary number of headers which are chained
together. The RIB data model MUST provide a way to expose the together. The RIB data model MUST provide a way to expose the
nexthop chaining capability supported by a given network device. nexthop chaining capability supported by a given network device.
The structure of the next-hop-capacity and the nexthop-tunnel-encap- This module uses the feature and if-feature statements to achieve
capacity is shown in the following figure: above capability negotiation.
Editor Notes: this version only includes the nexthop-hop and nexthop-
tunnel-encap capabilities, there may also need to define RIB
capabilities in future revision.
+--rw nexthop-capacity
| +--rw support-tunnel? boolean
| +--rw support-chains? boolean
| +--rw support-list-of-list? boolean
| +--rw support-replication? boolean
| +--rw support-weighted? boolean
| +--rw support-protection? boolean
| +--rw lookup-limit? uint8
+--rw nexthop-tunnel-encap-capacity
| +--rw support-ipv4? boolean
| +--rw support-ipv6? boolean
| +--rw support-mpls? boolean
| +--rw support-gre? boolean
| +--rw support-vxlan? boolean
| +--rw support-nvgre? boolean
Figure 2 RIB Capability
2.2. Routing Instance and Rib 2.2. Routing Instance and Rib
A routing instance, in the context of the RIB information model, is a A routing instance, in the context of the RIB information model, is a
collection of RIBs, interfaces, and routing protocol parameters. A collection of RIBs, interfaces, and routing protocol parameters. A
routing instance creates a logical slice of the router and can allow routing instance creates a logical slice of the router and can allow
multiple different logical slices; across a set of routers; to multiple different logical slices; across a set of routers; to
communicate with each other. And the routing protocol parameters communicate with each other. And the routing protocol parameters
control the information available in the RIBs. More detail about control the information available in the RIBs. More detail about
routing instance can be found in Section 2.2 of routing instance can be found in Section 2.2 of
[I-D.ietf-i2rs-rib-info-model]. [I-D.ietf-i2rs-rib-info-model].
As described in [I-D.ietf-i2rs-rib-info-model], there will be As described in [I-D.ietf-i2rs-rib-info-model], there will be
multiple routing instances for a router. At the same time, for a multiple routing instances for a router. At the same time, for a
routing instance, there would be multiple RIBs as well. Therefore, routing instance, there would be multiple RIBs as well. Therefore,
this model uses "list" to express the RIBs. The structure tree is this model uses "list" to express the RIBs. The structure tree is
shown as following figure. shown as following figure.
+--rw routing-instance +--rw routing-instance
+--rw instance-name string +--rw name string
+--rw interface-list* [name] +--rw interface-list* [name]
| +--rw name if:interface-ref | +--rw name if:interface-ref
+--rw router-id? yang:dotted-quad +--rw router-id? yang:dotted-quad
+--rw rib-list* [rib-name] +--rw lookup-limit? uint8
+--rw rib-name string +--rw rib-list* [name]
+--rw name string
+--rw rib-family rib-family-def +--rw rib-family rib-family-def
+--rw enable-ip-rpf-check? boolean +--rw enable-ip-rpf-check? boolean
+--rw route-list* [route-index] +--rw route-list* [route-index]
... (refer to sec.2.3) ... (refer to Sec.2.3)
Figure 3 Routing Instance Figure 2: Routing Instance Stuture
2.3. Route 2.3. Route
A route is essentially a match condition and an action following that A route is essentially a match condition and an action following that
match. The match condition specifies the kind of route (e.g., IPv4, match. The match condition specifies the kind of route (e.g., IPv4,
MPLS, MAC, Interface etc.) and the set of fields to match on. MPLS, MAC, Interface etc.) and the set of fields to match on.
According to the definition in [I-D.ietf-i2rs-rib-info-model], a According to the definition in [I-D.ietf-i2rs-rib-info-model], a
route MUST associate with the following attributes: route MUST associate with the following attributes:
skipping to change at page 8, line 5 skipping to change at page 9, line 5
candidate for selection. candidate for selection.
o INSTALLED: Indicates whether the route got installed in the FIB. o INSTALLED: Indicates whether the route got installed in the FIB.
In addition, a route can associate with one or more optional route In addition, a route can associate with one or more optional route
attributes(e.g., route-vendor-attributes). attributes(e.g., route-vendor-attributes).
For a RIB, there will have a number of routes, so the routes are For a RIB, there will have a number of routes, so the routes are
expressed as a list under the rib list. expressed as a list under the rib list.
+--rw route-list* [route-index] +--rw route-list* [route-index]
+--rw route-index uint64 +--rw route-index uint64
+--rw route-type route-type-def +--rw route-type route-type-def
+--rw match +--rw match
| +--rw (rib-route-type)? | +--rw (rib-route-type)?
| +--:(ipv4) | +--:(ipv4)
| | +--rw ipv4 | | +--rw ipv4
| | +--rw ipv4-route-type ip-route-type-def | | +--rw ipv4-route-type match-ip-route-type-def
| | +--rw (ip-route-type)? | | +--rw (match-ip-route-type)?
| | +--:(destination-ipv4-address) | | +--:(dest-ipv4-address)
| | | +--rw destination-ipv4-prefix inet:ipv4-prefix | | | ...
| | +--:(source-ipv4-address) | | +--:(src-ipv4-address)
| | | +--rw source-ipv4-prefix inet:ipv4-prefix | | | ...
| | +--:(destination-source-ipv4-address) | | +--:(dest-src-ipv4-address)
| | +--rw destination-source-ipv4-address | | ...
| | +--rw destination-ipv4-prefix inet:ipv4-prefix | +--:(ipv6)
| | +--rw source-ipv4-prefix inet:ipv4-prefix | | +--rw ipv6
| +--:(ipv6) | | +--rw ipv6-route-type match-ip-route-type-def
| | +--rw ipv6 | | +--rw (match-ip-route-type)?
| | +--rw ipv6-route-type ip-route-type-def | | +--:(dest-ipv6-address)
| | +--rw (ip-route-type)? | | | ...
| | +--:(destination-ipv6-address) | | +--:(src-ipv6-address)
| | | +--rw destination-ipv6-prefix inet:ipv6-prefix | | | ...
| | +--:(source-ipv6-address) | | +--:(dest-src-ipv6-address)
| | | +--rw source-ipv6-prefix inet:ipv6-prefix | | ...
| | +--:(destination-source-ipv6-address) | +--:(mpls-route)
| | +--rw destination-source-ipv6-address | | +--rw mpls-label uint32
| | +--rw destination-ipv6-prefix inet:ipv6-prefix | +--:(mac-route)
| | +--rw source-ipv6-prefix inet:ipv6-prefix | | +--rw mac-address uint32
| +--:(mpls-route) | +--:(interface-route)
| | +--rw mpls-label uint32 | +--rw interface-identifier if:interface-ref
| +--:(mac-route) +--rw nexthop
| | +--rw mac-address uint32 | ...(refer to Sec.2.4)
| +--:(interface-route)
| +--rw interface-identifier if:interface-ref
+--rw nexthop
... (refer to sec.2.4)
Figure 4 Route Figure 3: Routes Structure
2.4. Nexthop 2.4. Nexthop
A nexthop represents an object resulting from a route lookup. As A nexthop represents an object resulting from a route lookup. As
illustrated in Section 2.4 of [I-D.ietf-i2rs-rib-info-model], to illustrated in Section 2.4 of [I-D.ietf-i2rs-rib-info-model], to
support various of use cases (e.g., load balance, protection, support various of use cases (e.g., load balance, protection,
multicast or the combination of them), the nexthop is modelled as a multicast or the combination of them), the nexthop is modelled as a
multi-level structure and supports recursion. The first level of the multi-level structure and supports recursion. The first level of the
nexthop includes the following four types: nexthop includes the following four types:
skipping to change at page 9, line 21 skipping to change at page 10, line 17
replicate) will finally be iterated to a "base" nexthop. replicate) will finally be iterated to a "base" nexthop.
* nexthop-id * nexthop-id
* egress-interface * egress-interface
* logical-tunnel * logical-tunnel
* tunnel-encap * tunnel-encap
o Load-balance: Designed for load-balance case. o Load-balance: Designed for load-balance case where it normally
will have multiple weighted nexthops.
o Protection: Designed for protection scenario where it normally o Protection: Designed for protection scenario where it normally
will have primary and standby nexthop. will have primary and standby nexthop.
o Replicate: Designed for multiple destinations forwarding. o Replicate: Designed for multiple destinations forwarding.
The structure tree of nexthop is shown in the following figures. The structure tree of nexthop is shown in the following figures.
+--rw nexthop +--rw nexthop
| +--rw nexthop-id uint32 | +--rw nexthop-id uint32
| +--rw (nexthop-type)? | +--rw sharing-flag boolean
| +--:(nexthop-base) | +--rw (nexthop-type)?
| | +--rw nexthop-base | +--:(nexthop-base)
| | +--rw nexthop-chain* [nexthop-chain-id] | | ...(refer to Figure 5)
| | +--rw nexthop-chain-id uint32 | +--:(nexthop-chain) {nexthop-chain}?
| | +--rw (nexthop-chain-type)? | | +--rw nexthop-chain
| | ... (refer to Figure 6) | | +--rw nexthop-chain* [nexthop-chain-member-id]
| +--:(nexthop-protection) | | +--rw nexthop-chain-member-id uint32
| | +--rw nexthop-protection-list* [nexthop-protection-id] | +--:(nexthop-protection) {nexthop-protection}?
| | +--rw nexthop-protection-id uint32 | | +--rw nexthop-protection
| | +--rw nexthop-preference nexthop-preference-def | | +--rw nexthop-protection-list* [...-member-id]
| | +--rw nexthop nexthop-ref | | +--rw nexthop-protection-member-id uint32
| +--:(nexthop-load-balance) | | +--rw nexthop-preference nexthop-preference-def
| | +--rw nexthop-lb | +--:(nexthop-load-balance) {nexthop-load-balance}?
| | +--rw nexthop-lbs* [nexthop-lbs-id] | | +--rw nexthop-lb
| | +--rw nexthop-lbs-id uint32 | | +--rw nexthop-lbs* [nexthop-lbs-member-id]
| | +--rw nhop-lb-weight nhop-lb-weight-def | | +--rw nexthop-lbs-member-id uint32
| | +--rw nexthop-lb-member nexthop-ref | | +--rw nhop-lb-weight nhop-lb-weight-def
| +--:(nexthop-replicate) | +--:(nexthop-replicates) {nexthop-replicates}?
| +--rw nexthop-replicate | +--rw nexthop-replicates
| +--rw nexthop-replicates* [nexthop-replicates-id] | +--rw nexthop-replicates* [nexthop-replicates-member-id]
| +--rw nexthop-replicates-id uint32 | +--rw nexthop-replicates-member-id uint32
| +--rw nexthop-replicate? nexthop-ref
Figure 5 Nexhop Figure 4: Nexhop Structure
Figure 6 (as shown blow) is a sub-tree of nexthop, it's under the Figure 6 (as shown blow) is a sub-tree of nexthop, it's under the
nexthop chain node. nexthop base node.
+--rw (nexthop-chain-type)? +--:(nexthop-base)
+--:(nexthop-chain-member-special) | +--rw nexthop-base
| +--rw nexthop-chain-member-special | +--rw (nexthop-base-type)?
| +--rw nexthop-chain-member-special? special-nexthop-def | +--:(special-nexthop)
+--:(nexthop-chain-member-identifier) | | +--rw special? special-nexthop-def
| +--rw (nexthop-identifier-type)? | +--:(egress-interface-nexthop)
| +--:(nexthop-chain-name) | | +--rw outgoing-interface if:interface-ref
| | +--rw nexthop-chain-name string | +--:(ipv4-address-nexthop)
| +--:(nexthop-chain-id) | | +--rw ipv4-address inet:ipv4-address
| +--rw nexthop-chain-id uint32 | +--:(ipv6-address-nexthop)
+--:(egress-interface-next-hop) | | +--rw ipv6-address inet:ipv6-address
| +--rw outgoing-interface if:interface-ref | +--:(egress-interface-ipv4-nexthop)
+--:(ipv4-address-next-hop) | | +--rw egress-interface-ipv4-address
| +--rw next-hop-ipv4-address inet:ipv4-address | | +--rw outgoing-interface if:interface-ref
+--:(ipv6-address-next-hop) | | +--rw ipv4-address inet:ipv4-address
| +--rw next-hop-ipv6-address inet:ipv6-address | +--:(egress-interface-ipv6-nexthop)
+--:(egress-interface-ipv4-next-hop) | | +--rw egress-interface-ipv6-address
| +--rw next-hop-egress-interface-ipv4-address | | +--rw outgoing-interface if:interface-ref
| +--rw outgoing-interface if:interface-ref | | +--rw ipv6-address inet:ipv6-address
| +--rw next-hop-egress-ipv4-address inet:ipv4-address | +--:(egress-interface-mac-nexthop)
+--:(egress-interface-ipv6-next-hop) | | +--rw egress-interface-mac-address
| +--rw next-hop-egress-interface-ipv6-address | | +--rw outgoing-interface if:interface-ref
| +--rw outgoing-interface if:interface-ref | | +--rw ieee-mac-address uint32
| +--rw next-hop-egress-ipv6-address inet:ipv4-address | +--:(tunnel-encap-nexthop) {nexthop-tunnel}?
+--:(egress-interface-mac-next-hop) | | +--rw tunnel-encap
| +--rw next-hop-egress-interface-mac-address | | +--rw (tunnel-type)?
| +--rw outgoing-interface if:interface-ref | | +--:(ipv4) {ipv4-tunnel}?
| +--rw ieee-mac-address uint32 | | | +--rw source-ipv4-address inet:ipv4-address
+--:(tunnel-encap-next-hop) | | | +--rw destination-ipv4-address inet:ipv4-address
| +--rw tunnel-encap | | | +--rw protocol uint8
| +--rw (tunnel-type)? | | | +--rw ttl? uint8
| | +--:(ipv4) | | | +--rw dscp? uint8
| | | +--rw source-ipv4-address inet:ipv4-address | | +--:(ipv6) {ipv6-tunnel}?
| | | +--rw destination-ipv4-address inet:ipv4-address | | | +--rw source-ipv6-address inet:ipv6-address
| | | +--rw protocol uint8 | | | +--rw destination-ipv6-address inet:ipv6-address
| | | +--rw ttl? uint8 | | | +--rw next-header uint8
| | | +--rw dscp? uint8 | | | +--rw traffic-class? uint8
| | +--:(ipv6) | | | +--rw flow-label? uint16
| | | +--rw source-ipv6-address inet:ipv6-address | | | +--rw hop-limit? uint8
| | | +--rw destination-ipv6-address inet:ipv6-address | | +--:(mpls) {mpls-tunnel}?
| | | +--rw next-header uint8 | | | +--rw (mpls-action-type)?
| | | +--rw traffic-class? uint8 | | | +--:(mpls-push)
| | | +--rw flow-label? uint16 | | | | +--rw mpls-push boolean
| | | +--rw hop-limit? uint8 | | | | +--rw mpls-label uint32
| | +--:(mpls) | | | | +--rw s-bit? boolean
| | | +--rw (mpls-action-type)? | | | | +--rw tc-value? uint8
| | | +--:(mpls-push) | | | | +--rw ttl-value? uint8
| | | | +--rw mpls-push boolean | | | +--:(mpls-swap)
| | | | +--rw mpls-label uint32 | | | +--rw mpls-swap boolean
| | | | +--rw s-bit? boolean | | | +--rw mpls-in-label uint32
| | | | +--rw tos-value? uint8 | | | +--rw mpls-out-label uint32
| | | | +--rw ttl-value? uint8 | | | +--rw ttl-action? ttl-action-def
| | | +--:(mpls-pop) | | +--:(gre) {gre-tunnel}?
| | | +--rw mpls-pop boolean | | | +--rw gre-ip-destination inet:ipv4-address
| | | +--rw ttl-action? uint8 | | | +--rw gre-protocol-type inet:ipv4-address
| | +--:(gre) | | | +--rw gre-key? uint64
| | | +--rw gre-ip-destination inet:ipv4-address | | +--:(nvgre) {nvgre-tunnel}?
| | | +--rw gre-protocol-type inet:ipv4-address | | | +--rw (nvgre-type)?
| | | +--rw gre-key? uint64 | | | | +--:(ipv4)
| | +--:(nvgre) | | | | | +--rw src-ipv4-address inet:ipv4-address
| | +--rw (nvgre-type)? | | | | | +--rw dest-ipv4-address inet:ipv4-address
| | | +--:(ipv4) | | | | | +--rw protocol uint8
| | | | +--rw source-ipv4-address inet:ipv4-address | | | | | +--rw ttl? uint8
| | | | +--rw destination-ipv4-address inet:ipv4-address | | | | | +--rw dscp? uint8
| | | | +--rw protocol uint8 | | | | +--:(ipv6)
| | | | +--rw ttl? uint8 | | | | +--rw source-ipv6-address inet:ipv6-address
| | | | +--rw dscp? uint8 | | | | +--rw dest-ipv6-address inet:ipv6-address
| | | +--:(ipv6) | | | | +--rw next-header uint8
| | | +--rw source-ipv6-address inet:ipv6-address | | | | +--rw traffic-class? uint8
| | | +--rw destination-ipv6-address inet:ipv6-address | | | | +--rw flow-label? uint16
| | | +--rw next-header uint8 | | | | +--rw hop-limit? uint8
| | | +--rw traffic-class? uint8 | | | +--rw virtual-subnet-id uint32
| | | +--rw flow-label? uint16 | | | +--rw flow-id? uint16
| | | +--rw hop-limit? uint8 | | +--:(vxlan) {vxlan-tunnel}?
| | +--rw virtual-subnet-id uint32 | | +--rw (vxlan-type)?
| | +--rw flow-id? uint16 | | | +--:(ipv4)
| +--rw outgoing-interface? string | | | | +--rw src-ipv4-address inet:ipv4-address
+--:(logical-tunnel-next-hop) | | | | +--rw dest-ipv4-address inet:ipv4-address
| +--rw logical-tunnel | | | | +--rw protocol uint8
| +--rw tunnel-type tunnel-type-def | | | | +--rw ttl? uint8
| +--rw tunnel-name string | | | | +--rw dscp? uint8
+--:(rib-name) | | | +--:(ipv6)
+--rw rib-name? string | | | +--rw src-ipv6-address inet:ipv6-address
| | | +--rw dest-ipv6-address inet:ipv6-address
| | | +--rw next-header uint8
| | | +--rw traffic-class? uint8
| | | +--rw flow-label? uint16
| | | +--rw hop-limit? uint8
| | +--rw vxlan-identifier? uint32
| +--:(tunnel-decap-nexthp) {nexthop-tunnel}?
| | +--rw tunnel-decap
| | +--rw (tunnel-type)?
| | +--:(ipv4) {ipv4-tunnel}?
| | | +--rw ipv4-decap
| | | +--rw ipv4-decap boolean
| | | +--rw ttl-action? ttl-action-def
| | +--:(ipv6) {ipv6-tunnel}?
| | | +--rw ipv6-decap
| | | +--rw ipv6-decap boolean
| | | +--rw hop-limit-action? hop-limit-action-def
| | +--:(mpls) {mpls-tunnel}?
| | +--rw mpls-pop
| | +--rw mpls-pop boolean
| | +--rw ttl-action? ttl-action-def
| +--:(logical-tunnel-nexthop) {nexthop-tunnel}?
| | +--rw logical-tunnel
| | +--rw tunnel-type tunnel-type-def
| | +--rw tunnel-name string
| +--:(rib-name-nexthop)
| +--rw rib-name? string
Figure 6 Nexthop Chain Figure 5: Nexthop Base Structure
2.5. Notifications 2.5. RPC Operations
This module defines the following RPC operations:
o rib-add: It is defined to add a rib to a routing instance. A name
of the rib, address family of the rib and whether the RPF check is
enabled are passed as the input parameters. The output is the
result of the add operation: 1 means success, and 0 means failed.
o rib-delete: It is defined to delete a rib from a routing instance.
When a rib is deleted, all routes installed in the rib will be
deleted. A name of the rib is passed as the input parameter. The
output is the result of the delete operation: 1 means success, and
0 means failed.
o route-add: It is defined to add a route or a set of routes to a
rib. A rib name, the route prefix(es), route attributes, route
vendor attributes and nexthop are passed as the input parameters.
The output is the result of the add operation: 1 means success,
and 0 means failed. Before calling the route-add rpc, it is
required to call the nh-add rpc to create and/or return the
nexthop identifier.
o route-delete: It is defined to delete a route or a set of routes
from a rib. A name of the rib and the route prefix(es) are passed
as the input parameters. The output is the result of the delete
operation: 1 means success, and 0 means failed.
o route-update: It is defined to update a route or a set of routes.
A rib name, the route prefix(es), or route attributes, or route
vendor attributes, or nexthop are passed as the input parameters.
The match conditions can be either route prefix(es), or route
attributes, or route vendor attributes, or nexthop. The update
actions include: update the nexthop, update the route attributes,
update the route vendor attributes. The output is the result of
the update operation: 1 means success, and 0 means failed.
o nh-add: It is defined to add a nexthop to a rib. A name of the
rib and a nexthop are passed as the input parameters. The network
node is required to allocate a nexhop identifier to the nexthop.
The outputs include the result of the update operation (1 means
success, and 0 means failed ) and the nexthop identifier that is
allocated to the nexthop.
o nh-delete: It is defined to delete a nexthop from a rib. A name
of a rib and a nexthop or nexthop identifier are passed as the
input parameters. The output is the result of the delete
operation: 1 means success, 0 means failed.
The structure tree of rpcs is showing in following figure.
rpcs:
+---x rib-add
| +--ro input
| | +--ro rib-name string
| | +--ro rib-family rib-family-def
| | +--ro enable-ip-rpf-check? boolean
| +--ro output
| +--ro result boolean
+---x rib-delete
| +--ro input
| | +--ro rib-name string
| +--ro output
| +--ro result boolean
+---x route-add
| +--ro input
| | +--ro rib-name string
| | +--ro routes
| | ...
| +--ro output
| +--ro result boolean
+---x route-delete
| +--ro input
| | +--ro rib-name string
| | +--ro routes
| | ...
| +--ro output
| +--ro result boolean
+---x route-update
| +--ro input
| | +--ro rib-name string
| | +--ro (match-conditions)?
| | +--:(match-route-prefix)
| | | ...
| | +--:(match-route-attributes)
| | | ...
| | +--:(match-vendor-route-attributes)
| | | ...
| | +--:(match-nexthop)
| | ...
| +--ro output
| +--ro result boolean
+---x nh-add
| +--ro input
| | +--ro rib-name string
| | +--ro nexthop-id uint32
| | +--ro sharing-flag boolean
| | +--ro (nexthop-type)?
| | ...
| +--ro output
| +--ro result boolean
| +--ro nexthop-id uint32
+---x nh-delete
+--ro input
| +--ro rib-name string
| +--ro (nexthop-context-or-id)?
| +--:(nexthop-context)
| | ...
| +--:(nexthop-identifier)
| ...
+--ro output
+--ro result boolean
Figure 6: RPCs Structure
2.6. Notifications
Asynchronous notifications are sent by the RIB manager of a network Asynchronous notifications are sent by the RIB manager of a network
device to an external entity when some event triggers on the network device to an external entity when some event triggers on the network
device. A RIB data-model MUST support sending 2 kind of asynchronous device. A RIB data-model MUST support sending 2 kind of asynchronous
notifications. notifications.
1. Route change notification: 1. Route change notification:
o Installed (Indicates whether the route got installed in the FIB) ; o Installed (Indicates whether the route got installed in the FIB) ;
skipping to change at page 13, line 12 skipping to change at page 17, line 9
determine the final resolved nexthop. For example, in a case when a determine the final resolved nexthop. For example, in a case when a
nexthop could be an IP address. The RIB manager would resolve how to nexthop could be an IP address. The RIB manager would resolve how to
reach that IP address, e.g. by checking if that particular IP is reach that IP address, e.g. by checking if that particular IP is
address reachable by regular IP forwarding or by a MPLS tunnel or by address reachable by regular IP forwarding or by a MPLS tunnel or by
both. If the RIB manager cannot resolve the nexthop, then the both. If the RIB manager cannot resolve the nexthop, then the
nexthop remains in an unresolved state and is NOT a suitable nexthop remains in an unresolved state and is NOT a suitable
candidate for installation in the FIB. candidate for installation in the FIB.
The structure tree of notifications is shown in the following figure. The structure tree of notifications is shown in the following figure.
notifications: notifications:
+---n nexthop-resolution-status-change +---n nexthop-resolution-status-change
| +--ro nexthop | +--ro nexthop
| | +--ro nexthop-id uint32 | | +--ro nexthop-id uint32
| | +--ro (nexthop-type)? | | +--ro sharing-flag boolean
| | +--:(nexthop-base) | | +--ro (nexthop-type)?
| | | +--ro nexthop-base | | +--:(nexthop-base)
| | | +--ro nexthop-chain* [nexthop-chain-id] | | | ...
| | | +--ro nexthop-chain-id uint32 | | +--:(nexthop-chain) {nexthop-chain}?
| | | +--ro (nexthop-chain-type)? | | | ...
| | | ... | | +--:(nexthop-protection) {nexthop-protection}?
| | +--:(nexthop-protection) | | | ...
| | | +--ro nexthop-protection-list* [nexthop-protection-id] | | +--:(nexthop-load-balance) {nexthop-load-balance}?
| | | +--ro nexthop-protection-id uint32 | | | ...
| | | +--ro nexthop-preference nexthop-preference-def | | +--:(nexthop-replicates) {nexthop-replicates}?
| | | +--ro rw nexthop nexthop-ref | | ...
| | +--:(nexthop-load-balance) | +--ro nexthop-state nexthop-state-def
| | | +--ro nexthop-lb +---n route-change
| | | +--ro nexthop-lbs* [nexthop-lbs-id] +--ro rib-name string
| | | +--ro nexthop-lbs-id uint32 +--ro rib-family rib-family-def
| | | +--ro nhop-lb-weight nhop-lb-weight-def +--ro route-index uint64
| | | +--ro nexthop-lb-member nexthop-ref +--ro route-type route-type-def
| | +--:(nexthop-replicate) +--ro match
| | +--ro nexthop-replicate | +--ro (rib-route-type)?
| | +--ro nexthop-replicates* [nexthop-replicates-id] | +--:(ipv4)
| | +--ro nexthop-replicates-id uint32 | | ...
| | +--ro nexthop-replicate? nexthop-ref | +--:(ipv6)
| +--ro nexthop-state nexthop-state-def | | ...
+---n route-change | +--:(mpls-route)
+--ro instance-name string | | ...
+--ro rib-name string | +--:(mac-route)
+--ro rib-family rib-family-def | | ...
+--ro route-index uint64 | +--:(interface-route)
+--ro route-type route-type-def | ...
+--ro match +--ro route-installed-state route-installed-state-def
| +--ro (rib-route-type)? +--ro route-state route-state-def
| +--:(ipv4) +--ro route-reason route-reason-def
| | +--ro ipv4
| | ...
| +--:(ipv6)
| | +--ro ipv6
| | ...
| +--:(mpls-route)
| | +--ro mpls-label uint32
| +--:(mac-route)
| | +--ro mac-address uint32
| +--:(interface-route)
| +--ro interface-identifier if:interface-ref
+--ro route-installed-state route-installed-state-def
+--ro route-state route-state-def
+--ro route-reason route-reason-def
Figure 7 Notifications Figure 7: Notifications Structure
3. YANG Modules 3. YANG Modules
<CODE BEGINS> file "i2rs rib@2015-04-03.yang" //<CODE BEGINS> file "i2rs rib@2015-10-17.yang"
module i2rs-rib { module i2rs-rib {
namespace "urn:TBD1:params:xml:ns:yang:rt:i2rs:rib"; namespace "urn:ietf:params:xml:ns:yang:i2rs-rib";
// replace with iana namespace when assigned // replace with iana namespace when assigned
prefix "i2rs-rib"; prefix "i2rs-rib";
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
//rfc6991 //rfc6991
} }
import ietf-interfaces { import ietf-interfaces {
prefix "if"; prefix "if";
} }
import ietf-routing { import ietf-yang-types {
prefix "rt"; prefix yang;
} }
organization organization
"TBD2"; "IETF I2RS WG";
contact contact
"email: wang_little_star@sina.com "email: wang_little_star@sina.com
email: hari@packetdesign.com email: hari@packetdesign.com
email: mach.chen@huawei.com email: mach.chen@huawei.com
email: amit.dass@ericsson.com email: amit.dass@ericsson.com
email: sriganesh.kini@ericsson.com email: sriganesh.kini@ericsson.com
email: nitin_bahadur@yahoo.com"; email: nitin_bahadur@yahoo.com";
description description
"This module defines a YANG data model for "This module defines a YANG data model for
Routing Information Base (RIB) that aligns Routing Information Base (RIB) that aligns
with the I2RS RIB information model. with the I2RS RIB information model.";
";
revision "2015-04-03" { revision "2015-10-17" {
description "initial revision"; description "initial revision";
reference "draft-ietf-i2rs-rib-info-model-06"; reference "draft-ietf-i2rs-rib-info-model-07";
} }
container nexthop-capacity{ //Nexthhop related features
leaf support-tunnel{ feature nexthop-tunnel {
type boolean; description
} "This feature means that a node support
leaf support-chains{ tunnel nexhtop capability. The i2rs client
type boolean; can specify a tunnel nexthop to a route.";
}
leaf support-list-of-list{
type boolean;
}
leaf support-replication{
type boolean;
}
leaf support-weighted{
type boolean;
}
leaf support-protection{
type boolean;
}
leaf lookup-limit{
type uint8;
}
}
container nexthop-tunnel-encap-capacity{ }
leaf support-ipv4{
type boolean;
}
leaf support-ipv6{
type boolean;
}
leaf support-mpls{
type boolean;
}
leaf support-gre{
type boolean;
}
leaf support-vxlan{
type boolean;
} feature nexthop-chain {
leaf support-nvgre{ description
type boolean; "This feature means that a node support
} chain nexhtop capability.";
} }
// Identities and Type Definitions feature nexthop-protection {
identity mpls-action { description
description "This feature means that a node support
"The mpls-action. "; protection nexhtop capability.";
} }
identity push { feature nexthop-replicates {
base "mpls-action"; description
} "This feature means that a node support
relicates nexhtop capability.";
}
identity pop { feature nexthop-load-balance {
base "mpls-action"; description
} "This feature means that a node support
load balance nexhtop capability.";
}
identity swap { //Tunnel encap related features
base "mpls-action"; feature ipv4-tunnel {
} description
"This feature means that a node support
IPv4 tunnel encapsulation capability.";
}
feature ipv6-tunnel {
description
"This feature means that a node support
IPv6 tunnel encapsulation capability.";
}
feature mpls-tunnel {
description
"This feature means that a node support
MPLS tunnel encapsulation capability.";
}
feature vxlan-tunnel {
description
"This feature means that a node support
VxLAN tunnel encapsulation capability.";
}
feature gre-tunnel {
description
"This feature means that a node support
GRE tunnel encapsulation capability.";
}
feature nvgre-tunnel {
description
"This feature means that a node support
NvGRE tunnel encapsulation capability.";
}
typedef mpls-action-def { //Identities and Type Definitions
type identityref { identity mpls-action {
base "mpls-action"; description
} "Base identify from which all mpls label
} operations are derived.
The MPLS label stack operations include:
push - to add a new label to a label stack,
pop - to pop the top label from a label stack,
swap - to change the top label of a label
stack with new label.";
}
identity special-nexthop { identity label-push {
description base "mpls-action";
"special-nexthop. "; description
} "MPLS label stack operation: push.";
}
identity discard { identity label-pop {
base "special-nexthop"; base "mpls-action";
} description
"MPLS label stack operation: pop.";
}
identity discard-with-error { identity label-swap {
base "special-nexthop"; base "mpls-action";
} description
"MPLS label stack operation: swap.";
}
identity receive { typedef mpls-action-def {
base "special-nexthop"; type identityref {
} base "mpls-action";
}
description
"MPLS action def.";
}
identity ttl-action {
description
"Base identify from which all TTL
actions are derived.
The tll actions include:
- ttl-no-action: do nothing regarding the TTL, or
- ttl-copy-to-inner: copy the TTL of the outer
header to inner header, or
- ttl-decrease-and-copy-to-inner: Decrease the TTL
by one and copy it to inner header.
";
}
identity cos-value { identity ttl-no-action {
base "special-nexthop"; base "ttl-action";
} description
"Do nothing regarding the TTL.";
}
typedef special-nexthop-def { identity ttl-copy-to-inner {
type identityref { base "ttl-action";
base "special-nexthop"; description
} "Copy the TTL of the outer header
} to inner header.";
}
identity ip-route-type { identity ttl-decrease-and-copy-to-inner {
description base "ttl-action";
"The ip route type. "; description
} "Decrease TTL by one and copy the TTL
to inner header.";
}
identity src { typedef ttl-action-def {
base "ip-route-type"; type identityref {
} base "ttl-action";
}
description
"TTL action def.";
}
identity dest { identity hop-limit-action {
base "ip-route-type"; description
} "Base identify from which all hop limit
actions are derived.";
}
identity dest-src { identity hop-limit-no-action {
base "ip-route-type"; base "hop-limit-action";
} description
"Do nothing regarding the hop limit.";
}
typedef ip-route-type-def { identity hop-limit-copy-to-inner {
type identityref { base "hop-limit-action";
base "ip-route-type"; description
} "Copy the hop limit of the outer header
} to inner header.";
}
identity rib-family { typedef hop-limit-action-def {
description type identityref {
"The rib-family."; base "hop-limit-action";
} }
description
"IPv6 hop limit action def.";
}
identity ipv4-rib-family { identity special-nexthop {
base "rib-family"; description
} "Base identify from which all special
nexthops are derived.";
}
identity ipv6-rib-family { identity discard {
base "rib-family"; base "special-nexthop";
} description
"This indicates that the network
device should drop the packet and
increment a drop counter.";
}
identity mpls-rib-family { identity discard-with-error {
base "rib-family"; base "special-nexthop";
} description
identity ieee-mac-rib-family { "This indicates that the network
base "rib-family"; device should drop the packet,
} increment a drop counter and send
back an appropriate error message
(like ICMP error).";
}
typedef rib-family-def { identity receive {
type identityref { base "special-nexthop";
base "rib-family"; description
} "This indicates that that the traffic is
} destined for the network device. For
example, protocol packets or OAM packets.
All locally destined traffic SHOULD be
throttled to avoid a denial of service
attack on the router's control plane. An
optional rate-limiter can be specified
to indicate how to throttle traffic
destined for the control plane.";
}
identity route-type { identity cos-value {
description "The route type. "; base "special-nexthop";
} description
"Cos-value special nexthop.";
}
identity ipv4-route { typedef special-nexthop-def {
base "route-type"; type identityref {
} base "special-nexthop";
}
description
"Special nexthop def.";
}
identity ipv6-route { identity match-ip-route-type {
base "route-type"; description
} "Base identify from which all route
match types are derived.
Route match type could be:
match source, or
match destination, or
match source and destination.";
}
identity mpls-route { identity match-ip-src {
base "route-type"; base "match-ip-route-type";
} description
"Source route match type.";
}
identity match-ip-dest {
base "match-ip-route-type";
description
"Destination route match type";
}
identity match-ip-src-dest {
base "match-ip-route-type";
description
"Src and Dest route match type";
identity ieee-mac { }
base "route-type";
}
identity interface { typedef match-ip-route-type-def {
base "route-type"; type identityref {
} base "match-ip-route-type";
}
description
"Route match type def.";
}
typedef route-type-def { identity rib-family {
type identityref { description
base "route-type"; "Base identify from which all rib
} address families are derived.";
} }
identity tunnel-type { identity ipv4-rib-family {
description base "rib-family";
"The tunnel type."; description
} "IPv4 rib address family.";
}
identity ipv4-tunnel { identity ipv6-rib-family {
base "tunnel-type"; base "rib-family";
description description
"IPv4 tunnel type"; "IPv6 rib address family.";
} }
identity ipv6-tunnel { identity mpls-rib-family {
base "tunnel-type"; base "rib-family";
description description
"IPv6 Tunnel type"; "MPLS rib address family.";
} }
identity mpls-tunnel { identity ieee-mac-rib-family {
base "tunnel-type"; base "rib-family";
description description
"MPLS tunnel type"; "MAC rib address family.";
} }
identity gre-tunnel { typedef rib-family-def {
base "tunnel-type"; type identityref {
description base "rib-family";
"GRE tunnel type"; }
} description
"Rib address family def.";
}
identity route-type {
description
"Base identify from which all route types
are derived.";
}
identity vxlan-tunnel { identity ipv4-route {
base "tunnel-type"; base "route-type";
description description
"VxLAN tunnel type"; "IPv4 route type.";
} }
identity nvgre-tunnel { identity ipv6-route {
base "tunnel-type"; base "route-type";
description description
"NVGRE tunnel type"; "IPv6 route type.";
} }
typedef tunnel-type-def { identity mpls-route {
type identityref { base "route-type";
base "tunnel-type"; description
} "MPLS route type.";
} }
identity route-state { identity ieee-mac {
description base "route-type";
"The route state."; description
} "MAC route type.";
}
identity active { identity interface {
base "route-state"; base "route-type";
} description
identity inactive { "Interface route type.";
base "route-state"; }
}
typedef route-state-def { typedef route-type-def {
type identityref { type identityref {
base "route-state"; base "route-type";
} }
} description
"Route type def.";
}
identity nexthop-state { identity tunnel-type {
description description
"The nexthop state."; "Base identify from which all tunnel
} types are derived.";
identity resolved { }
base "nexthop-state";
}
identity unresolved { identity ipv4-tunnel {
base "nexthop-state"; base "tunnel-type";
} description
"IPv4 tunnel type";
}
typedef nexthop-state-def { identity ipv6-tunnel {
type identityref { base "tunnel-type";
base "nexthop-state"; description
} "IPv6 Tunnel type";
} }
identity route-installed-state { identity mpls-tunnel {
description base "tunnel-type";
"The route installed state. "; description
} "MPLS tunnel type";
}
identity uninstalled { identity gre-tunnel {
base "route-installed-state"; base "tunnel-type";
} description
"GRE tunnel type";
}
identity Installed { identity vxlan-tunnel {
base "route-installed-state"; base "tunnel-type";
} description
"VxLAN tunnel type";
}
typedef route-installed-state-def { identity nvgre-tunnel {
type identityref { base "tunnel-type";
base "route-installed-state"; description
} "NVGRE tunnel type";
} }
identity route-reason {
description
"The reason of invalid route. ";
}
identity low-preference { typedef tunnel-type-def {
base "route-reason"; type identityref {
description base "tunnel-type";
"Low preference"; }
} description
"Tunnel type def.";
}
identity unresolved-nexthop { identity route-state {
base "route-reason"; description
description "Base identify from which all route
"Unresolved nexthop"; states are derived.";
} }
identity higher-metric { identity active {
base "route-reason"; base "route-state";
description description
"Higher metric"; "Active state.";
} }
typedef route-reason-def { identity inactive {
type identityref { base "route-state";
base "route-reason"; description
} "Inactive state.";
} }
typedef nexthop-preference-def { typedef route-state-def {
description type identityref {
"Nexthop-preference is used for protection schemes. base "route-state";
It is an integer value between 1 and 99. A lower }
value indicates higher preference. To download a description
primary/standby/tertiary group to the FIB, the "Route state def.";
nexthops that are resolved and have two highest }
preferences are selected.";
type uint8 {
range "1..99";
}
}
typedef nhop-lb-weight-def {
description
"Nhop-lb-weight is a number between 1 and 99.";
type uint8 {
range "1..99";
}
}
typedef nexthop-ref {
type leafref {
path "/i2rs-rib:routing-instance/i2rs-rib:rib-list" +
"/i2rs-rib:route-list/i2rs-rib:nexthop/i2rs-rib:nexthop-id";
}
}
//Groupings identity nexthop-state {
description
"Base identify from which all nexthop
states are derived.";
}
grouping route-prefix{ identity resolved {
description base "nexthop-state";
"The common attributes used for all routes"; description
leaf route-index { "Reolved nexthop state.";
type uint64 ; }
mandatory true;
}
leaf route-type {
type route-type-def ;
mandatory true;
}
container match {
choice rib-route-type {
case ipv4 {
description
"Match on destination IP address in the IPv4 header";
container ipv4{
leaf ipv4-route-type {
type ip-route-type-def ;
mandatory true;
}
choice ip-route-type {
case destination-ipv4-address {
leaf destination-ipv4-prefix {
type inet:ipv4-prefix;
mandatory true;
}
}
case source-ipv4-address {
leaf source-ipv4-prefix {
type inet:ipv4-prefix;
mandatory true;
}
}
case destination-source-ipv4-address {
container destination-source-ipv4-address {
leaf destination-ipv4-prefix {
type inet:ipv4-prefix;
mandatory true;
} identity unresolved {
leaf source-ipv4-prefix { base "nexthop-state";
type inet:ipv4-prefix; description
mandatory true; "Unresolved nexthop state.";
} }
}
}
}
}
}
case ipv6 {
description
"Match on destination IP address in the IPv6 header";
container ipv6 {
leaf ipv6-route-type {
type ip-route-type-def ;
mandatory true;
}
choice ip-route-type {
case destination-ipv6-address {
leaf destination-ipv6-prefix {
type inet:ipv6-prefix;
mandatory true;
}
}
case source-ipv6-address {
leaf source-ipv6-prefix {
type inet:ipv6-prefix;
mandatory true;
}
}
case destination-source-ipv6-address {
container destination-source-ipv6-address {
leaf destination-ipv6-prefix {
type inet:ipv6-prefix;
mandatory true;
}
leaf source-ipv6-prefix {
type inet:ipv6-prefix;
mandatory true;
}
}
}
}
}
}
case mpls-route {
description
"Match on a MPLS label at the top of the MPLS label stack";
leaf mpls-label {
type uint32 ;
mandatory true;
}
}
case mac-route {
description
"Match on MAC destination addresses in the ethernet header";
leaf mac-address {
type uint32 ;
mandatory true;
}
}
case interface-route {
description
"Match on incoming interface of the packet";
leaf interface-identifier {
type if:interface-ref;
mandatory true;
}
}
}
}
}
grouping route{ typedef nexthop-state-def {
description type identityref {
"The common attributes usesd for all routes"; base "nexthop-state";
uses route-prefix; }
container nexthop{ description
uses nexthop; "Nexthop state def.";
}
container route-statistic{
leaf route-state {
type route-state-def ;
config false;
}
leaf route-installed-state {
type route-installed-state-def ;
config false;
}
leaf route-reason {
type route-reason-def ;
config false;
}
}
container route-attributes{
uses route-attributes;
}
container route-vendor-attributes{
uses route-vendor-attributes;
}
}
grouping nexthop { }
leaf nexthop-id {
mandatory true;
type uint32;
}
choice nexthop-type {
case nexthop-base {
container nexthop-base {
list nexthop-chain {
key "nexthop-chain-id";
uses nexthop-chain-member;
}
}
}
case nexthop-protection { identity route-installed-state {
list nexthop-protection-list { description
key "nexthop-protection-id"; "Base identify from which all route
leaf nexthop-protection-id { installed states are derived.";
}
identity uninstalled {
base "route-installed-state";
description
"Uninstalled state.";
}
identity installed {
base "route-installed-state";
description
"Installed state.";
}
typedef route-installed-state-def {
type identityref {
base "route-installed-state";
}
description
"Route installed state def.";
}
identity route-reason {
description
"Base identify from which all route
reasons are derived.";
}
identity low-preference {
base "route-reason";
description
"Low preference";
}
identity unresolved-nexthop {
base "route-reason";
description
"Unresolved nexthop";
}
identity higher-metric {
base "route-reason";
description
"Higher metric";
}
typedef route-reason-def {
type identityref {
base "route-reason";
}
description
"Route reason def.";
}
typedef nexthop-preference-def {
type uint8 {
range "1..99";
}
description
"Nexthop-preference is used for protection schemes.
It is an integer value between 1 and 99. A lower
value indicates higher preference. To download a
primary/standby/tertiary group to the FIB, the
nexthops that are resolved and have two highest
preferences are selected.";
}
typedef nhop-lb-weight-def {
type uint8 {
range "1..99";
}
description
"Nhop-lb-weight is a number between 1 and 99.";
}
//Groupings
grouping route-prefix {
description
"The common attributes used for all types of route prefix.";
leaf route-index {
type uint64 ;
mandatory true;
description
"Route index.";
}
leaf route-type {
type route-type-def;
mandatory true;
description
"Route types, e.g., IPv4, IPv6, MPLS, MAC etc. route types.";
}
container match {
description
"The match condition specifies the
kind of route (IPv4, MPLS, etc.)
and the set of fields to match on.";
choice rib-route-type {
description
"To match a route according to rib route type.";
case ipv4 {
description
"IPv4 rib case.";
container ipv4 {
description
"IPv4 route match type.";
leaf ipv4-route-type {
type match-ip-route-type-def;
mandatory true;
description
"Route match type, it could be:
match source, or
match destination, or
match source and destination.
";
}
choice match-ip-route-type {
description
"To match a route according to match type.";
case dest-ipv4-address {
leaf dest-ipv4-prefix {
type inet:ipv4-prefix;
mandatory true;
description
"To match an IPv4 destination address.";
}
}
case src-ipv4-address {
leaf src-ipv4-prefix {
type inet:ipv4-prefix;
mandatory true;
description
"To match an IPv4 source address.";
}
}
case dest-src-ipv4-address {
container dest-src-ipv4-address {
description
"To match IPv4 source and destination addreses.";
leaf dest-ipv4-prefix {
type inet:ipv4-prefix;
mandatory true;
description
"The IPv4 destination address of
the match condition.";
}
leaf src-ipv4-prefix {
type inet:ipv4-prefix;
mandatory true;
description
"The IPv4 source address of
the match condition.";
}
}
}
}
}
}
case ipv6 {
description
"IPv6 rib case.";
container ipv6 {
description
"IPv6 route match type.";
leaf ipv6-route-type {
type match-ip-route-type-def;
mandatory true;
description
"Route match type, it could be:
match source, or
match destination, or
match source and destination.
";
}
choice match-ip-route-type {
description
"To match a route according to match type.";
case dest-ipv6-address {
leaf dest-ipv6-prefix {
type inet:ipv6-prefix;
mandatory true;
description
"To match an IPv6 destination address.";
}
}
case src-ipv6-address {
leaf src-ipv6-prefix {
type inet:ipv6-prefix;
mandatory true;
description
"To match an IPv6 source address.";
}
}
case dest-src-ipv6-address {
container dest-src-ipv6-address {
description
"To match the source and destination addreses.";
leaf dest-ipv6-prefix {
type inet:ipv6-prefix;
mandatory true;
description
"The IPv6 destination address of
the match condition.";
}
leaf src-ipv6-prefix {
type inet:ipv6-prefix;
mandatory true;
description
"The IPv6 source address of
the match condition.";
}
}
}
}
}
}
case mpls-route {
description
"MPLS rib case.";
leaf mpls-label {
type uint32 ;
mandatory true;
description
"The label used for matching.";
}
}
case mac-route {
description
"MAC rib case.";
leaf mac-address {
type uint32 ;
mandatory true;
description
"The MAC address used for matching.";
}
}
case interface-route {
description
"Interface rib case.";
leaf interface-identifier {
type if:interface-ref;
mandatory true;
description
"The interface used for matching.";
}
}
}
}
}
grouping route {
description
"The common attributes usesd for all types of route.";
uses route-prefix;
container nexthop {
description
"The nexthop of the route.";
uses nexthop;
}
container route-statistic {
description
"The statistic information of the route.";
leaf route-state {
type route-state-def;
config false;
description
"Indicate a route's state: Active or Inactive.";
}
leaf route-installed-state {
type route-installed-state-def;
config false;
description
"Indicate that a route's installed states:
Installed or uninstalled.";
}
leaf route-reason {
type route-reason-def;
config false;
description
"Indicate the route reason.";
}
}
container route-attributes {
description
"Route attributes.";
uses route-attributes;
}
container route-vendor-attributes {
description
"Route vendor attributes.";
uses route-vendor-attributes;
}
}
grouping nexthop {
description
"The nexthop structure.";
leaf nexthop-id {
type uint32;
mandatory true;
description
"The nexthop identifier of a nexthop.";
}
leaf sharing-flag {
type boolean;
mandatory true;
description
"To indicate whether a nexthop is sharable
or non-sharable.
1 - means sharable
0 - means non-sharable.";
}
choice nexthop-type {
description
"Based on nexthop type to derive the nexthop.";
case nexthop-base {
container nexthop-base {
description
"A nexthop base container.";
uses nexthop-base;
}
}
case nexthop-chain {
if-feature nexthop-chain;
container nexthop-chain {
description
"A nexthop chain container.";
list nexthop-chain {
key "nexthop-chain-member-id";
description
"A list of nexthop members of
a load nexthop chain.";
leaf nexthop-chain-member-id {
type uint32;
mandatory true;
description
"A nexthop identifier that points
to a nexthop chain member.
A nexthop chain member is a nexthop.";
}
}
}
}
case nexthop-protection {
if-feature nexthop-protection;
container nexthop-protection {
description
"A protection nexthop container.";
list nexthop-protection-list {
key "nexthop-protection-member-id";
description
"A list of nexthop protection
members of a load balance nexthop.";
leaf nexthop-protection-member-id {
type uint32;
mandatory true;
description
"A nexthop identifier that points
to a protection nexthop member.
A protection nexthop member is
a nexthop.";
}
leaf nexthop-preference {
type nexthop-preference-def;
mandatory true;
description
"Nexthop-preference is used for protection schemes.
It is an integer value between 1 and 99. A lower
value indicates higher preference. To download a
primary/standby/tertiary group to the FIB, the
nexthops that are resolved and have two highest
preferences are selected.";
}
}
}
}
case nexthop-load-balance {
if-feature nexthop-load-balance;
container nexthop-lb {
description
"A load balance nexthop container.";
list nexthop-lbs {
key "nexthop-lbs-member-id";
description
"A list of nexthop load balance
members of a load balance nexthop.";
leaf nexthop-lbs-member-id {
type uint32;
mandatory true;
description
"A nexthop identifier that points
to a load balance nexthop member.
A load balance nexthop member is
a nexthop.";
}
leaf nhop-lb-weight {
type nhop-lb-weight-def;
mandatory true;
description
"The weight of a nexthop of
the load balance nexthops.";
}
}
}
}
case nexthop-replicates {
if-feature nexthop-replicates;
container nexthop-replicates {
description
"A nexthop replicates container.";
list nexthop-replicates {
key "nexthop-replicates-member-id";
description
"A list of replicate nexthop members
that belong to the nexthop-replicates.";
leaf nexthop-replicates-member-id {
type uint32;
description
"A nexthop identifier that points
to a replicates nexthop member.
A replicates nexthop member is a nexthop.";
}
}
}
}
}
}
grouping nexthop-base {
description
"The base nexthop content for a route.";
choice nexthop-base-type {
description
"Based on nexthop chain type to select
relevant nexthop chain member.";
case special-nexthop {
leaf special {
type special-nexthop-def;
description
"A special nexthop.";
}
}
case egress-interface-nexthop {
leaf outgoing-interface {
type if:interface-ref;
mandatory true; mandatory true;
type uint32; description
"The nexthop is an outgoing interface.";
} }
leaf nexthop-preference { }
description case ipv4-address-nexthop {
"Nexthop-preference is used for protection schemes. leaf ipv4-address {
It is an integer value between 1 and 99. A lower type inet:ipv4-address;
value indicates higher preference. To download a
primary/standby/tertiary group to the FIB, the
nexthops that are resolved and have two highest
preferences are selected.";
mandatory true; mandatory true;
type nexthop-preference-def; description
"The nexthop is an IPv4 address.";
} }
leaf nexthop { }
case ipv6-address-nexthop {
leaf ipv6-address {
type inet:ipv6-address;
mandatory true; mandatory true;
type nexthop-ref; description
"The nexthop is an IPv6 address.";
} }
} }
} case egress-interface-ipv4-nexthop {
container egress-interface-ipv4-address{
leaf outgoing-interface {
type if:interface-ref;
mandatory true;
description
"Name of the outgoing interface.";
}
leaf ipv4-address {
type inet:ipv4-address;
mandatory true;
description
"The nexthop points to an interface with
an IPv4 address.";
}
description
"Egress-interface and ip address: This can be usesd
in cases e.g.where the ip address is a link-local
address.";
}
}
case egress-interface-ipv6-nexthop {
container egress-interface-ipv6-address {
leaf outgoing-interface {
type if:interface-ref;
mandatory true;
description
"Name of the outgoing interface.";
}
leaf ipv6-address {
type inet:ipv6-address;
mandatory true;
description
"The nexthop points to an interface with
an IPv6 address.";
}
description
"Egress-interface and ip address: This can be usesd
in cases e.g.where the ip address is a link-local
address.";
}
}
case egress-interface-mac-nexthop {
container egress-interface-mac-address {
leaf outgoing-interface {
type if:interface-ref;
mandatory true;
description
"Name of the outgoing interface.";
}
leaf ieee-mac-address {
type uint32;
mandatory true;
description
"The nexthop points to an interface with
a specific mac-address.";
}
description
"The egress interface must be an ethernet
interface. Address resolution is not required
for this nexthop.";
}
}
case tunnel-encap-nexthop {
if-feature nexthop-tunnel;
container tunnel-encap {
uses tunnel-encap;
description
"This can be an encap representing an IP tunnel or
MPLS tunnel or others as defined in info model.
An optional egress interface can be chained to the
tunnel encap to indicate which interface to send
the packet out on. The egress interface is useful
when the network device contains Ethernet interfaces
and one needs to perform address resolution for the
IP packet.";
}
}
case tunnel-decap-nexthp {
if-feature nexthop-tunnel;
container tunnel-decap {
uses tunnel-decap;
description
"This is to specify decapsulating a tunnel header.";
}
}
case logical-tunnel-nexthop {
if-feature nexthop-tunnel;
container logical-tunnel {
uses logical-tunnel;
description
"This can be a MPLS LSP or a GRE tunnel (or others
as defined in This document), that is represented
by a unique identifier (e.g. name).";
}
}
case rib-name-nexthop {
leaf rib-name {
type string;
description
"A nexthop pointing to a rib indicates that the
route lookup needs to continue in The specified
rib. This is a way to perform chained lookups.";
}
}
}
case nexthop-load-balance { }
container nexthop-lb {
list nexthop-lbs {
key "nexthop-lbs-id";
leaf nexthop-lbs-id {
mandatory true;
type uint32;
}
leaf nhop-lb-weight {
mandatory true;
type nhop-lb-weight-def;
}
leaf nexthop-lb-member {
mandatory true;
type nexthop-ref;
}
}
}
}
case nexthop-replicate { grouping route-vendor-attributes {
container nexthop-replicate { description
list nexthop-replicates{ "Route vendor attributes.";
key "nexthop-replicates-id"; }
leaf nexthop-replicates-id {
mandatory true;
type uint32;
}
leaf nexthop-replicate {
type nexthop-ref;
}
}
}
}
}
}
grouping nexthop-chain-member { grouping logical-tunnel {
description description
"One nexthop content for a route."; "A logical tunnel that is identified
leaf nexthop-chain-id{ by a type and a tunnel name.";
type uint32; leaf tunnel-type {
mandatory true; type tunnel-type-def;
} mandatory true;
choice nexthop-chain-type { description
case nexthop-chain-member-special { "A tunnel type.";
container nexthop-chain-member-special { }
leaf nexthop-chain-member-special{ leaf tunnel-name {
type special-nexthop-def; type string;
mandatory true;
description
"A tunnel name that points to a logical tunnel.";
}
}
} grouping ipv4-header {
} description
} "The IPv4 header encapsulation information.";
leaf source-ipv4-address {
type inet:ipv4-address;
mandatory true;
description
"The source ip address of the header.";
}
leaf destination-ipv4-address {
type inet:ipv4-address;
mandatory true;
description
"The destination ip address of the header.";
}
leaf protocol {
type uint8;
mandatory true;
description
"The protocol id of the header.";
}
leaf ttl {
type uint8;
description
"The TTL of the header.";
}
leaf dscp {
type uint8;
description
"The DSCP field of the header.";
}
}
case nexthop-chain-member-identifier{ grouping ipv6-header {
uses nexthop-chain-member-identifier; description
} "The IPv6 header encapsulation information.";
leaf source-ipv6-address {
type inet:ipv6-address;
mandatory true;
description
"The source ip address of the header.";
}
leaf destination-ipv6-address {
type inet:ipv6-address;
mandatory true;
description
"The destination ip address of the header.";
}
leaf next-header {
type uint8;
mandatory true;
description
"The next header of the IPv6 header.";
}
leaf traffic-class {
type uint8;
description
"The traffic class value of the header.";
}
leaf flow-label {
type uint16;
description
"The flow label of the header.";
}
leaf hop-limit {
type uint8;
description
"The hop limit the header.";
}
}
grouping nvgre-header {
description
"The NvGRE header encapsulation information.";
choice nvgre-type {
description
"NvGRE can use eigher IPv4
or IPv6 header for encapsulation.";
case ipv4 {
uses ipv4-header;
}
case ipv6 {
uses ipv6-header;
}
}
leaf virtual-subnet-id {
type uint32;
mandatory true;
description
"The subnet identifier of the NvGRE header.";
}
leaf flow-id {
type uint16;
description
"The flow identifier of the NvGRE header.";
}
}
case egress-interface-next-hop { grouping vxlan-header {
description
"The VxLAN encapsulation header information.";
choice vxlan-type {
description description
"Simple next-hop is specified as an outgoing interface, "NvGRE can use eigher IPv4
next-hop address or both."; or IPv6 header for encapsulation.";
leaf outgoing-interface { case ipv4 {
uses ipv4-header;
}
case ipv6 {
uses ipv6-header;
}
}
leaf vxlan-identifier {
type uint32;
description
"The VxLAN identifier of the VxLAN header.";
}
}
grouping gre-header {
description
"The GRE encapsulation header information.";
leaf gre-ip-destination {
type inet:ipv4-address;
mandatory true;
description
"The destination ip address of the GRE header.";
}
leaf gre-protocol-type {
type inet:ipv4-address;
mandatory true;
description
"The protocol type of the GRE header.";
}
leaf gre-key {
type uint64;
description
"The GRE key of the GRE header.";
}
}
grouping mpls-header {
description
"The MPLS encapsulation header information.";
choice mpls-action-type {
description
"Based on action type to perform different operation.";
case mpls-push {
leaf mpls-push {
type boolean;
mandatory true;
description
"Push a MPLS label to the label stack.";
}
leaf mpls-label {
type uint32;
mandatory true;
description
"The MPLS label to be pushed.";
}
leaf s-bit {
type boolean;
description
"The s-bit of the label to be pushed. ";
}
leaf tc-value {
type uint8;
description
"The traffic class value of the label to be pushed.";
}
leaf ttl-value {
type uint8;
description
"The TTL value of the label to to be pushed.";
}
}
case mpls-swap {
leaf mpls-swap {
type boolean;
mandatory true;
description
"Swap a MPLS label with another label.";
}
leaf mpls-in-label {
type uint32;
mandatory true;
description
"The in MPLS label.";
}
leaf mpls-out-label {
type uint32;
mandatory true;
description
"The out MPLS label.";
}
leaf ttl-action {
type ttl-action-def;
description
"The label ttl actions:
- No-action, or
- Copy to inner label,or
- Decrease (the in label) by 1 and
copy to the out label.";
}
}
}
}
grouping tunnel-encap{
description
"Tunnel encapsulation inforamtion.";
choice tunnel-type {
description
"Tunnel options for next-hops.";
case ipv4 {
if-feature ipv4-tunnel;
uses ipv4-header;
}
case ipv6 {
if-feature ipv6-tunnel;
uses ipv6-header;
}
case mpls {
if-feature mpls-tunnel;
uses mpls-header;
}
case gre {
if-feature gre-tunnel;
uses gre-header;
}
case nvgre {
if-feature nvgre-tunnel;
uses nvgre-header;
}
case vxlan {
if-feature vxlan-tunnel;
uses vxlan-header;
}
}
}
grouping tunnel-decap {
description
"Tunnel decapsulation inforamtion.";
choice tunnel-type {
description
"Tunnel options for next-hops.";
case ipv4 {
if-feature ipv4-tunnel;
container ipv4-decap {
leaf ipv4-decap {
type boolean;
mandatory true;
description
"IPv4 decap operations.";
}
leaf ttl-action {
type ttl-action-def;
description
"The ttl actions:
no-action or copy to inner header.";
}
description
"IPv4 decap.";
}
}
case ipv6 {
if-feature ipv6-tunnel;
container ipv6-decap {
leaf ipv6-decap {
type boolean;
mandatory true;
description
"IPv6 decap operations.";
}
leaf hop-limit-action {
type hop-limit-action-def;
description
"The hop limit actions:
no-action or copy to inner header.";
}
description
"IPv6 decap.";
}
}
case mpls {
if-feature mpls-tunnel;
container mpls-pop {
leaf mpls-pop {
type boolean;
mandatory true;
description
"Pop a MPLS label from the label stack.";
}
leaf ttl-action {
type ttl-action-def;
description
"The label ttl actions:
no-action or copy to inner label";
}
description
"MPLS decap.";
}
}
}
}
grouping route-attributes {
description
"Route attributes.";
leaf route-preference {
type uint32 ;
mandatory true;
description
"ROUTE_PREFERENCE: This is a numerical value that
allows for comparing routes from different
protocols. Static configuration is also
considered a protocol for the purpose of this
field. It iss also known as administrative-distance.
The lower the value, the higher the preference.";
}
leaf local-only {
type boolean ;
mandatory true;
description
"Indicate whether the attributes is local only.";
}
container address-family-route-attributes{
description
"Address family related route attributes.";
choice route-type {
description
"Address family related route attributes.";
case ip-route-attributes {
}
case mpls-route-attributes {
}
case ethernet-route-attributes {
}
}
}
}
container routing-instance {
description
"Configuration of an 'i2rs' pseudo-protocol
instance consists of a list of ribs.";
leaf name {
type string;
mandatory true;
description
"A routing instance is identified by its name,
INSTANCE_name. This MUST be unique across all
routing instances in a given network device.";
}
list interface-list {
key "name";
description
"This represents the list of interfaces associated
with this routing instance. The interface list helps
constrain the boundaries of packet forwarding.
Packets coming on these interfaces are directly
associated with the given routing instance. The
interface list contains a list of identifiers, with
each identifier uniquely identifying an interface.";
leaf name {
type if:interface-ref; type if:interface-ref;
description
"A reference to the name of a configured
network layer interface.";
}
}
leaf router-id {
type yang:dotted-quad;
description
"Router ID - 32-bit number in the form of a dotted quad.";
}
leaf lookup-limit {
type uint8;
description
"A limit on how many levels of a lookup can be performed.";
}
list rib-list {
key "name";
description
"This is the list of RIBs associated with this routing
instance. Each routing instance can have multiple RIBs
to represent routes of different types.";
leaf name {
type string;
mandatory true; mandatory true;
description description
"Name of the outgoing interface."; "A reference to the name of a rib.";
} }
} leaf rib-family {
type rib-family-def;
mandatory true;
description
"The address family of the rib.";
}
leaf enable-ip-rpf-check {
type boolean;
description
"Each RIB can be optionally associated with a
ENABLE_IP_RPF_CHECK attribute that enables Reverse
path forwarding (RPF) checks on all IP routes in that
RIB. Reverse path forwarding (RPF) check is used to
prevent spoofing and limit malicious traffic.";
}
list route-list {
key "route-index";
description
"A routes of a rib.";
uses route;
}
}
}
case ipv4-address-next-hop { /*RPC Operations*/
leaf next-hop-ipv4-address {
type inet:ipv4-address;
mandatory true;
description
"The nexthop is an IPv4 address.";
}
}
case ipv6-address-next-hop { rpc rib-add {
leaf next-hop-ipv6-address { description
type inet:ipv6-address; "To add a rib to a instance";
mandatory true; input {
description leaf rib-name {
"The nexthop is an IPv6 address."; type string;
} mandatory true;
} description
"A reference to the name of the rib
that is to be added.";
}
leaf rib-family {
type rib-family-def;
mandatory true;
description
"The address family of the rib.";
}
leaf enable-ip-rpf-check {
type boolean;
description
"Each RIB can be optionally associated with a
ENABLE_IP_RPF_CHECK attribute that enables Reverse
path forwarding (RPF) checks on all IP routes in that
RIB. Reverse path forwarding (RPF) check is used to
prevent spoofing and limit malicious traffic.";
}
}
case egress-interface-ipv4-next-hop { output {
container next-hop-egress-interface-ipv4-address{ leaf result {
leaf outgoing-interface { type boolean ;
type if:interface-ref; mandatory true;
mandatory true; description
description "Return the result of the rib-add operation.
"Name of the outgoing interface."; 1 - means success;
} 0 - means falied.";
leaf next-hop-egress-ipv4-address { }
type inet:ipv4-address; }
mandatory true; }
description
"The nexthop points to an interface with
an IPv4 address.";
}
description
"Egress-interface and ip address: This can be usesd
in cases e.g.where the ip address is a link-local
address.";
}
}
case egress-interface-ipv6-next-hop { rpc rib-delete {
container next-hop-egress-interface-ipv6-address{ description
leaf outgoing-interface { "To delete a rib from a routing instance,
type if:interface-ref; by deleting the rib, all routes installed
mandatory true; in the rib will be deleted as well.";
description input {
"Name of the outgoing interface."; leaf rib-name {
} type string;
leaf next-hop-egress-ipv6-address { mandatory true;
type inet:ipv6-address; description
mandatory true; "A reference to the name of the rib
description that is to be deleted.";
"The nexthop points to an interface with }
an IPv6 address."; }
} output {
description leaf result {
"Egress-interface and ip address: This can be usesd type boolean ;
in cases e.g.where the ip address is a link-local mandatory true;
address."; description
} "Return the result of the rib-delete operation.
} 1 - means success;
0 - means falied.";
}
}
}
case egress-interface-mac-next-hop { rpc route-add {
container next-hop-egress-interface-mac-address{ description
leaf outgoing-interface { "To add a route or a list of route to a rib";
type if:interface-ref; input {
mandatory true; leaf rib-name {
description type string;
"Name of the outgoing interface."; mandatory true;
} description
leaf ieee-mac-address { "A reference to the name of a rib.";
type uint32; }
mandatory true; container routes {
description description
"The nexthop points to an interface with "The routes to be added to the rib.";
a specific mac-address."; list route-list {
key "route-index";
description
"Use a list to include all routes to be added.";
} uses route-prefix;
description uses route-attributes;
"The egress interface must be an ethernet uses route-vendor-attributes;
interface.Address resolution is not required uses nexthop;
for this nexthop." }
}
}
} output {
} leaf result {
type boolean ;
mandatory true;
description
"Return the result of the route-add operation.
1 - means success;
0 - means falied.";
}
}
}
case tunnel-encap-next-hop { rpc route-delete {
container tunnel-encap { description
uses tunnel-encap; "To delete a route or a list of route from a rib";
leaf outgoing-interface { input {
type string; leaf rib-name {
} type string;
description mandatory true;
"This can be an encap representing an ip tunnel or description
mpls tunnel or others as defined in this document. "A reference to the name of a rib.";
An optional egress interface can be specified to }
indicate which interface to send The packet out on. container routes {
The egress interface is usesful when the network description
device contains eThernet interfaces and one needs "The routes to be added to the rib.";
to perform address resolution for The ip packet."; list route-list{
} key "route-index";
} description
"The list of routes to be deleted.";
uses route-prefix;
}
}
}
case logical-tunnel-next-hop { output {
container logical-tunnel { leaf result {
uses logical-tunnel; type boolean ;
description mandatory true;
"This can be a MPLS LSP or a GRE tunnel (or others description
as defined in This document), that is represented "Return the result of the route-delete operation.
by a unique identifier (e.g. name).";
}
}
case rib-name { 1 - means success;
leaf rib-name { 0 - means falied.";
type string; }
description }
"A nexthop pointing to a rib indicates that the }
route lookup needs to continue in The specified
rib. This is a way to perform chained lookups.";
}
}
}
}
grouping nexthop-chain-member-identifier{
choice nexthop-identifier-type{
case nexthop-chain-name {
leaf nexthop-chain-name {
type string;
mandatory true;
}
}
case nexthop-chain-id {
leaf nexthop-chain-id {
type uint32;
mandatory true;
}
}
}
}
grouping route-vendor-attributes{ rpc route-update {
} description
"To update a route or a list of route of a rib.
The inputs:
1. The match conditions, could be:
a. route prefix, or
b. route attribtes, or
c. nexthop;
2. The update parameters to be used:
a. new nexhop;
b. new route attributes;
Actions:
1. update the nexthop
2. update the route attributes
The outputs:
1 - success;
0 - failed.
";
grouping logical-tunnel{ input {
leaf tunnel-type { leaf rib-name {
type tunnel-type-def ; type string;
mandatory true; mandatory true;
} description
leaf tunnel-name { "A reference to the name of a rib.";
type string ; }
mandatory true; choice match-conditions {
} description
} "When conditions matched, update the routes.";
//Update routes that have the matched route prefixes
case match-route-prefix {
container input-routes {
description
"The matched routes to be updated.";
list route-list {
key "route-index";
description
"The list of routes to be updated.";
uses route-prefix;
choice update-actions-prefix {
description
"Update actions include:
grouping ipv4-header{ 1. update nexthop
leaf source-ipv4-address { 2. update route attributes
type inet:ipv4-address; 3. update route-vendor-attributes.
mandatory true; ";
} case update-nexthop {
leaf destination-ipv4-address { uses nexthop;
type inet:ipv4-address; }
mandatory true; case update-route-attributes {
} uses route-attributes;
leaf protocol { }
type uint8; case update-route-vendor-attributes {
mandatory true; uses route-vendor-attributes;
} }
leaf ttl { }
type uint8; }
} }
leaf dscp { }
type uint8; //Update the routes that have the matched attributes
} case match-route-attributes {
} container input-route-attributes {
description
"The route attributes are used for matching.";
uses route-attributes;
}
choice update-actions-attributes {
description
"Update actions include:
1. update nexthop
2. update route attributes
3. update route-vendor-attributes.
";
case update-nexthop {
uses nexthop;
}
case update-route-attributes {
uses route-attributes;
}
case update-route-vendor-attributes {
uses route-vendor-attributes;
}
}
}
//Update the routes that have the matched vendor attributes
case match-vendor-route-attributes {
container input-vendor-route-attributes {
description
"The vendor route attributes are used for matching.";
uses route-vendor-attributes;
grouping ipv6-header{ }
leaf source-ipv6-address { choice update-actions-vendor-attributes {
type inet:ipv6-address; description
mandatory true; "Update actions include:
} 1. update nexthop
leaf destination-ipv6-address { 2. update route attributes
type inet:ipv6-address; 3. update route-vendor-attributes.
mandatory true; ";
} case update-nexthop {
leaf next-header { uses nexthop;
type uint8; }
mandatory true; case update-route-attributes {
} uses route-attributes;
leaf traffic-class { }
type uint8; case update-route-vendor-attributes {
} uses route-vendor-attributes;
leaf flow-label { }
type uint16; }
} }
leaf hop-limit { //Update the routes that have the matched nexthop
type uint8; case match-nexthop {
} container input-nexthop {
} description
"The nexthop used for matching.";
uses nexthop;
}
grouping nvgre-header{ choice update-actions-nexthop {
choice nvgre-type { description
description "Update actions include:
"nvgre-header."; 1. update nexthop
case ipv4 { 2. update route attributes
uses ipv4-header; 3. update route-vendor-attributes.
} ";
case ipv6 { case update-nexthop {
uses ipv6-header; uses nexthop;
} }
} case update-route-attributes {
leaf virtual-subnet-id { uses route-attributes;
type uint32; }
mandatory true; case update-route-vendor-attributes {
} uses route-vendor-attributes;
leaf flow-id { }
type uint16; }
} }
} }
grouping vxlan-header{ }
choice vxlan-type { output {
description leaf result {
"vxlan-header."; type boolean ;
case ipv4 { mandatory true;
uses ipv4-header; description
} "Return the result of the route-update operation.
case ipv6 { 1 - means success;
uses ipv6-header; 0 - means falied.";
} }
} }
leaf vxlan-identifier { }
type uint32;
}
}
grouping gre-header{ rpc nh-add {
leaf gre-ip-destination { description
type inet:ipv4-address; "To add a nexthop to a rib.
mandatory true; Inputs parameters:
} 1. rib name
leaf gre-protocol-type { 2. nexthop;
type inet:ipv4-address; Actions:
mandatory true; Add the nexthop to the rib
} Outputs:
leaf gre-key { 1.Operation result:
type uint64; 1 - means success
} 0 - means faled;
} 2. nexthop identifier.";
input {
leaf rib-name {
type string;
mandatory true;
description
"A reference to the name of a rib.";
}
uses nexthop;
}
grouping mpls-header{ output {
choice mpls-action-type { leaf result {
description type boolean ;
"mpls-header."; mandatory true;
case mpls-push { description
leaf mpls-push { "Return the result of the nh-add operation.
type boolean; 1 - means success;
mandatory true; 0 - means falied.";
} }
leaf mpls-label { leaf nexthop-id {
type uint32; type uint32;
mandatory true; mandatory true;
} description
leaf s-bit { "A nexthop identifer that is allocated to the nexthop.";
type boolean; }
} }
leaf tos-value { }
type uint8;
} rpc nh-delete {
leaf ttl-value { description
type uint8; "To delete a nexthop from a rib";
} input {
} leaf rib-name {
case mpls-pop { type string;
leaf mpls-pop { mandatory true;
type boolean; description
mandatory true; "A reference to the name of a rib.";
} }
leaf ttl-action { choice nexthop-context-or-id {
type uint8; description
} "Delete a nexthop by inputing
} the nexthop itself or its nexthop id.";
} case nexthop-context {
} uses nexthop;
}
case nexthop-identifier {
leaf nexthop-identifer {
type uint32;
mandatory true;
description
"A reference to the nexthop to be deleted.";
}
}
}
}
grouping tunnel-encap{ output {
choice tunnel-type { leaf result {
description type boolean ;
"options for next-hops."; mandatory true;
case ipv4 { description
uses ipv4-header; "Return the result of the nh-delete operation.
} 1 - means success;
case ipv6 { 0 - means falied.";
uses ipv6-header; }
} }
case mpls { }
uses mpls-header;
}
case gre {
uses gre-header;
}
case nvgre {
uses nvgre-header;
}
}
}
grouping route-attributes{ /*Notifications*/
leaf route-preference { notification nexthop-resolution-status-change {
description description
"ROUTE_PREFERENCE: This is a numerical value that "Nexthop resolution status (resolved/unresolved)
allows for comparing routes from different notification.";
protocols. Static configuration is also container nexthop{
considered a protocol for the purpose of this description
field. It iss also known as administrative-distance. "The nexthop.";
The lower the value, the higher the preference."; uses nexthop;
}
leaf nexthop-state {
type nexthop-state-def;
mandatory true;
description
"Nexthop resolution status (resolved/unresolved)
notification.";
}
}
type uint32 ; notification route-change {
mandatory true; description
} "Route change notification.";
leaf local-only { leaf rib-name {
type boolean ; type string;
mandatory true; mandatory true;
} description
container address-family-route-attributes{ "A reference to the name of a rib.";
choice route-type { }
case ip-route-attributes { leaf rib-family {
} type rib-family-def;
case mpls-route-attributes { mandatory true;
} description
case ethernet-route-attributes { "A reference to address family of a rib.";
} }
} uses route-prefix;
} leaf route-installed-state {
} type route-installed-state-def;
mandatory true;
description
"Indicates whether the route got installed in the FIB.";
}
leaf route-state {
type route-state-def;
mandatory true;
description
"Indicates whether a route is fully resolved and
is a candidate for selection.";
}
leaf route-change-reason {
type route-reason-def;
mandatory true;
description
"Return the reason that causes the route change.";
}
}
}
container routing-instance { //<CODE ENDS>
description
"Configuration of an 'i2rs' pseudo-protocol instance
consists of a list of ribs.";
leaf name { 4. IANA Considerations
description
"A routing instance is identified by its name,
INSTANCE_name. This MUST be unique across all routing
instances in a given network device.";
type string ;
mandatory true;
}
list interface-list {
description
"This represents the list of interfaces associated
with this routing instance. The interface list helps
constrain the boundaries of packet forwarding.
Packets coming on these interfaces are directly
associated with the given routing instance. The
interface list contains a list of identifiers, with
each identifier uniquely identifying an interface.";
key "name";
leaf name {
type if:interface-ref;
description
"A reference to the name of a configured network layer
interface.";
}
} This document requests to register a URI in the "IETF XML registry"
uses rt:router-id ; [RFC3688]:
list rib-list {
description
"This is the list of RIBs associated with this routing
instance. Each routing instance can have multiple RIBs
to represent routes of different types.";
key "name";
leaf name {
description
"A reference to the name of a rib.";
type string;
mandatory true;
}
leaf rib-family {
type rib-family-def;
mandatory true;
}
leaf enable-ip-rpf-check {
description
"Each RIB can be optionally associated with a
ENABLE_IP_RPF_CHECK attribute that enables Reverse
path forwarding (RPF) checks on all IP routes in that
RIB. Reverse path forwarding (RPF) check is used to
prevent spoofing and limit malicious traffic.";
type boolean;
}
list route-list{
key "route-index";
uses route;
}
}
}
notification nexthop-resolution-status-change { --------------------------------------------------------------------
description URI: urn:ietf:params:xml:ns:yang:ietf-i2rs-rib
"Nexthop resolution status (resolved/unresolved) Registrant Contact: The IESG.XML:
notification."; N/A, the requested URI is an XML namespace.
container nexthop{ --------------------------------------------------------------------
uses nexthop;
}
leaf nexthop-state {
description
"Nexthop resolution status (resolved/unresolved)
notification.";
type nexthop-state-def;
mandatory true;
}
} This document requests to register a YANG module in the "YANG Module
Names registry" [RFC6020]:
notification route-change { --------------------------------------------------------------------
description name: ietf-i2rs-rib
"Route change notification."; namespace: urn:ietf:params:xml:ns:yang:ietf-i2rs-rib
leaf instance-name { prefix: iir
description reference: RFC XXXX
"A routing instance is identified by its name, --------------------------------------------------------------------
INSTANCE_name. This MUST be unique across all
routing instances in a given network device.";
type string ;
mandatory true;
}
leaf rib-name {
description
"A reference to the name of a rib.";
type string;
mandatory true;
}
leaf rib-family {
type rib-family-def;
mandatory true;
}
uses route-prefix;
leaf route-installed-state {
description
"Indicates whether the route got installed in the FIB.";
type route-installed-state-def;
mandatory true;
}
leaf route-state {
description
"Indicates whether a route is fully resolved and
is a candidate for selection.";
type route-state-def;
mandatory true;
}
leaf route-reason {
description
"Need to be added.";
type route-reason-def;
mandatory true;
}
}
}
<CODE ENDS> 5. Security Considerations
4. IANA Considerations
TBD. This document introduces no extra new security threat and SHOULD
follow the security requirements as stated in
[I-D.ietf-i2rs-architecture].
5. Security Considerations 6. Contributors
This document introduces no new security threat and SHOULD follow the The following individuals also contribute to this document.
security requirements as stated in [I-D.ietf-i2rs-architecture].
6. References o Zekun He, Tencent Holdings Ltd
6.1. Normative References o Sujian Lu, Tencent Holdings Ltd
o Jeffery Zhang, Juniper Networks
7. References
7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
6.2. Informative References [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<http://www.rfc-editor.org/info/rfc6020>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6991, DOI 10.17487/RFC6991, July 2013,
<http://www.rfc-editor.org/info/rfc6991>.
7.2. Informative References
[I-D.ietf-i2rs-architecture] [I-D.ietf-i2rs-architecture]
Atlas, A., Halpern, J., Hares, S., Ward, D., and T. Atlas, A., Halpern, J., Hares, S., Ward, D., and T.
Nadeau, "An Architecture for the Interface to the Routing Nadeau, "An Architecture for the Interface to the Routing
System", draft-ietf-i2rs-architecture-09 (work in System", draft-ietf-i2rs-architecture-09 (work in
progress), March 2015. progress), March 2015.
[I-D.ietf-i2rs-rib-info-model] [I-D.ietf-i2rs-rib-info-model]
Bahadur, N., Folkes, R., Kini, S., and J. Medved, "Routing Bahadur, N., Kini, S., and J. Medved, "Routing Information
Information Base Info Model", draft-ietf-i2rs-rib-info- Base Info Model", draft-ietf-i2rs-rib-info-model-07 (work
model-06 (work in progress), March 2015. in progress), September 2015.
[I-D.ietf-i2rs-usecase-reqs-summary] [I-D.ietf-i2rs-usecase-reqs-summary]
Hares, S. and M. Chen, "Summary of I2RS Use Case Hares, S. and M. Chen, "Summary of I2RS Use Case
Requirements", draft-ietf-i2rs-usecase-reqs-summary-01 Requirements", draft-ietf-i2rs-usecase-reqs-summary-01
(work in progress), May 2015. (work in progress), May 2015.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<http://www.rfc-editor.org/info/rfc6020>.
[RFC6021] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6021, DOI 10.17487/RFC6021, October 2010,
<http://www.rfc-editor.org/info/rfc6021>.
Authors' Addresses Authors' Addresses
Lixing Wang Lixing Wang
Huawei Individual
Email: wang_little_star@sina.com Email: wang_little_star@sina.com
Hariharan Ananthakrishnan Hariharan Ananthakrishnan
Packet Design Packet Design
Email: hari@packetdesign.com Email: hari@packetdesign.com
Mach(Guoyi) Chen Mach(Guoyi) Chen
Huawei Huawei
Email: mach.chen@huawei.com Email: mach.chen@huawei.com
 End of changes. 149 change blocks. 
1339 lines changed or deleted 2382 lines changed or added

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