draft-wang-i2rs-rib-data-model-01.txt   draft-wang-i2rs-rib-data-model-02.txt 
skipping to change at page 1, line 17 skipping to change at page 1, line 17
M. Chen M. Chen
Huawei Huawei
A. Dass A. Dass
S. Kini S. Kini
Ericsson Ericsson
N. Bahadur N. Bahadur
Bracket Computing Bracket Computing
March 09, 2015 March 09, 2015
Data Model for RIB I2RS protocol Data Model for RIB I2RS protocol
draft-wang-i2rs-rib-data-model-01 draft-wang-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 2, line 30 skipping to change at page 2, line 30
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 . . . . . . . . . . . . . . . . . . . . . 5
2.2. Routing Instance and Rib . . . . . . . . . . . . . . . . 6 2.2. Routing Instance and Rib . . . . . . . . . . . . . . . . 6
2.3. Route . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.3. Route . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.4. Nexthop . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.4. Nexthop . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.5. Notifications . . . . . . . . . . . . . . . . . . . . . . 11 2.5. Notifications . . . . . . . . . . . . . . . . . . . . . . 12
3. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 13 3. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 14
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37
5. Security Considerations . . . . . . . . . . . . . . . . . . . 36 5. Security Considerations . . . . . . . . . . . . . . . . . . . 37
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 36 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.1. Normative References . . . . . . . . . . . . . . . . . . 36 6.1. Normative References . . . . . . . . . . . . . . . . . . 37
6.2. Informative References . . . . . . . . . . . . . . . . . 36 6.2. Informative References . . . . . . . . . . . . . . . . . 37
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 38
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).
skipping to change at page 8, line 47 skipping to change at page 8, line 47
| | +--rw mac-address uint32 | | +--rw mac-address uint32
| +--:(interface-route) | +--:(interface-route)
| +--rw interface-identifier if:interface-ref | +--rw interface-identifier if:interface-ref
+--rw nexthop +--rw nexthop
... (refer to sec.2.4) ... (refer to sec.2.4)
Figure 4 Route Figure 4 Route
2.4. Nexthop 2.4. Nexthop
A nexthop represents an object resulting from a route lookup. The A nexthop represents an object resulting from a route lookup. As
detail information of nexthop is defined in Section 2.4 of illustrated in Section 2.4 of [I-D.ietf-i2rs-rib-info-model], to
[I-D.ietf-i2rs-rib-info-model]. Currently, four types of nexthop are support various of use cases (e.g., load balance, protection,
defined. multicast or the combination of them), the nexthop is modelled as a
multi-level structure and supports recursion. The first level of the
nexthop includes the following four types:
o base o Base: The "base" nexthop itself is a hierarchical structure, it is
o load-balance: design for load-balance case. the base of all other nexthop types. The first level of the base
nexthop includes special-nexthop and nexthop-chain. The nexthop-
chain can have one or more nexthop chain members, each member is
one of the four types (as listed below) of specific nexthop.
Other first level nexthop (e.g., load-balance, protection and
replicate) will finally be iterated to a "base" nexthop.
o primary-standby: designed for protection scenario where it * nexthop-id
normally will have primary and standby nexthop.
o replicate: designed for multiple destinations forwarding. * egress-interface
To support some complex use cases (e.g., multicast with load-balance * logical-tunnel
and/or protection), the nexthop is defined in the way of recursion.
* tunnel-encap
o Load-balance: Designed for load-balance case.
o Protection: Designed for protection scenario where it normally
will have primary and standby nexthop.
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 (nexthop-type)?
| +--:(nexthop-base) | +--:(nexthop-base)
| | +--rw nexthop-base | | +--rw nexthop-base
| | +--rw nexthop-chain* [nexthop-chain-id] | | +--rw nexthop-chain* [nexthop-chain-id]
| | +--rw nexthop-chain-id uint32 | | +--rw nexthop-chain-id uint32
 End of changes. 7 change blocks. 
20 lines changed or deleted 34 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/