draft-ietf-i2rs-fb-rib-data-model-00.txt   draft-ietf-i2rs-fb-rib-data-model-01.txt 
I2RS working group S. Hares I2RS working group S. Hares
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Standards Track S. Kini Intended status: Standards Track S. Kini
Expires: December 25, 2016 Ericsson Expires: September 14, 2017 Ericsson
L. Dunbar L. Dunbar
Huawei Huawei
R. Krishnan R. Krishnan
Dell Dell
D. Bogdanovic D. Bogdanovic
Juniper Networks Juniper Networks
R. White R. White
Linkedin Linkedin
June 23, 2016 March 13, 2017
Filter-Based RIB Data Model Filter-Based RIB Data Model
draft-ietf-i2rs-fb-rib-data-model-00 draft-ietf-i2rs-fb-rib-data-model-01
Abstract Abstract
This document defines a data model to support the Filter-based This document defines a data model to support the Filter-based
Routing Information Base (RIB) Yang data models for I2RS. A routing Routing Information Base (RIB) Yang data models. A routing system
system uses the Filter-based RIB to program FIB entries that process uses the Filter-based RIB to program FIB entries that process
incoming packets by matching on multiple fields within the packet and incoming packets by matching on multiple fields within the packet and
then performing a specified action on it. The FB-RIB can also then performing a specified action on it. The FB-RIB can also
specify an action to forward the packet according to the FIB entries specify an action to forward the packet according to the FIB entries
programmed using the RIBs of its routing instance. programmed using the RIBs of its routing instance.
The Filter based RIB is a protocol independent data structure which
can be deployed in a configuration datastore, an ephemeral control
plane data stroe.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 25, 2016. This Internet-Draft will expire on September 14, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
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. Definition of I2RS Filter Based RIB . . . . . . . . . . . 3 1.1. Definition of Filter Based RIB . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4
3. Definitions and Acronyms . . . . . . . . . . . . . . . . . . 4 3. Definitions and Acronyms . . . . . . . . . . . . . . . . . . 4
4. High level Yang structure for the FB-RIB . . . . . . . . . . 5 4. High level Yang structure for the FB-RIB . . . . . . . . . . 5
4.1. Top Level Yang Structure for ietf-fb-rib . . . . . . . . 7 4.1. Top Level Yang Structure for ietf-fb-rib . . . . . . . . 7
4.2. Filter-Based RIB structures . . . . . . . . . . . . . . . 8 4.2. Filter-Based RIB structures . . . . . . . . . . . . . . . 8
5. yang models . . . . . . . . . . . . . . . . . . . . . . . . . 9 5. yang models . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.1. Filter-Based RIB types . . . . . . . . . . . . . . . . . 9 5.1. Filter-Based RIB types . . . . . . . . . . . . . . . . . 9
5.2. FB-RIB . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.2. FB-RIB . . . . . . . . . . . . . . . . . . . . . . . . . 16
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
7. Security Considerations . . . . . . . . . . . . . . . . . . . 18 7. Security Considerations . . . . . . . . . . . . . . . . . . . 19
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.1. Normative References: . . . . . . . . . . . . . . . . . . 18 8.1. Normative References: . . . . . . . . . . . . . . . . . . 19
8.2. Informative References . . . . . . . . . . . . . . . . . 19 8.2. Informative References . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
The Interface to the Routing System (I2RS) This document provides a protocol-independent yang module for Filter
[I-D.ietf-i2rs-architecture] architecture provides dynamic read and Based Routing (FB-RIB) routing filters within a routing element. The
write access to the information and state within the routing informational model for this FB-RIB is in
elements. The I2RS client interacts with the I2RS agent in one or [I-D.ietf-i2rs-fb-rib-info-model].
more network routing systems.
This document provides a yang module for the I2RS filter Based
Routing Information Base (FB-RIB) and describes the I2RS interaction
with routing filters within a routing element. The informational
model for the FB-RIB is in [I-D.kini-i2rs-fb-rib-info-model]
1.1. Definition of I2RS Filter Based RIB 1.1. Definition of Filter Based RIB
Filter-based routing is a technique used to make packet forwarding Filter-based routing is a technique used to make packet forwarding
decisions based on a filter that is matched to the incoming packets decisions based on a filter that is matched to the incoming packets
and the specified action. It should be noted that that this is and the specified action. It should be noted that that this is
distinct from the static routes in the RIB distinct from the static routes in the RIB where the routing is
[I-D.ietf-i2rs-rib-info-model] where the routing is destination destination ddress based.
ddress based.
A Filter-Based RIB (Routing Information Base) is contained in a A Filter-Based RIB (Routing Information Base) is contained in a
routing instance (defined in [I-D.ietf-i2rs-rib-info-model]). It routing instance. It contains a list of filters (match-action
contains a list of filters (match-action conditions) and a list of conditions) and a list of interfaces the filter-based forwarding
interfaces the filter-based forwarding operates on, and default operates on, and default RIB(s).
RIB(s).
A Filter Based RIB uses packet forwarding policy. If packet A Filter Based RIB uses packet forwarding policy. If packet
reception is considered an event, then the I2RS Filter-based RIB uses reception is considered an event, then the Filter-based RIB uses a
a minimalistic Event-matchCondition-Action policy with the following minimalistic Event-matchCondition-Action policy with the following
characteristics: characteristics:
event = packet/frame received, event = packet/frame received,
match condition - match on field in frame/packet or circumstances match condition - match on field in frame/packet or circumstances
relating to packet reception (e.g. time received), relating to packet reception (e.g. time received),
action - modify packet and forward/drop packet. action - modify packet and forward/drop packet.
A Filter-based RIB entry specifies match filters for the fields in a A Filter-based RIB entry specifies match filters for the fields in a
skipping to change at page 3, line 48 skipping to change at page 3, line 38
If all matches fail, default action is to forward the packet using If all matches fail, default action is to forward the packet using
Destination Based forward from the default RIB(s). The default RIBs Destination Based forward from the default RIB(s). The default RIBs
can be: can be:
o created by the I2RS Routing Informational Base (RIB) manager using o created by the I2RS Routing Informational Base (RIB) manager using
the yang model described in: in [I-D.ietf-i2rs-rib-info-model], or the yang model described in: in [I-D.ietf-i2rs-rib-info-model], or
o configured RIB created using static routes or o configured RIB created using static routes or
[I-D.ietf-netmod-routing-cfg]. [I-D.ietf-netmod-routing-cfg].
o or static RIB created via static route yang model
Actions in the condition-action pair may impact forwarding or set Actions in the condition-action pair may impact forwarding or set
something in the packet that will impact forwarding. Policy actions something in the packet that will impact forwarding. Policy actions
are typically applied before applying QoS constraints since policy are typically applied before applying QoS constraints since policy
actions may override QoS constraint. actions may override QoS constraint.
The Filter-Based RIB resides in ephemeral state as does the I2RS RIB The Filter-Based RIB can reside in the configuration datastore, a
and I2RS topology models. control plane datastore, or an ephemeral control plane data store
(e.g. I2RS ephemeral control plane datastore).
The Interface to the Routing System (I2RS) [RFC7921] architecture
provides dynamic read and write access to the information and state
within the routing elements. The I2RS client interacts with the I2RS
agent in one or more network routing systems. The I2RS architecture
defines the I2RS control plane datastore as ephemeral - which means
it does not persist across a reboot.
2. Requirements Language 2. 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
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
In this document, these words will appear with that interpretation In this document, these words will appear with that interpretation
only when in ALL CAPS. Lower case uses of these words are not to be only when in ALL CAPS. Lower case uses of these words are not to be
interpreted as carrying RFC-2119 significance. interpreted as carrying RFC-2119 significance.
skipping to change at page 4, line 39 skipping to change at page 4, line 34
FB-Route FB-Route
The policy rules in the filter-based RIB are prescriptive of the The policy rules in the filter-based RIB are prescriptive of the
Event-Condition-Action form which is often represented by if Event-Condition-Action form which is often represented by if
Condition then action". Condition then action".
Policy Group Policy Group
Policy Groups are groups of policy rules. The groups of policy in Policy Groups are groups of policy rules. The groups of policy in
the basic network policy [I-D.hares-i2rs-pkt-eca-data-model] allow the basic network policy [I-D.ietf-i2rs-pkt-eca-data-model] allow
grouping of policy by name. This structure allow easier grouping of policy by name. This structure allow easier
management of customer-based or provider based filters, but does management of customer-based or provider based filters, but does
not change the policy-rules list. not change the policy-rules list.
RIB IM RIB IM
RIB Informational Model (RIB IM) [I-D.ietf-i2rs-rib-info-model] RIB Informational Model (RIB IM) [I-D.ietf-i2rs-rib-info-model]
Routing instance Routing instance
skipping to change at page 5, line 20 skipping to change at page 5, line 18
o a global FB-RIB structures, o a global FB-RIB structures,
o the common structure of the FB-RIB, and o the common structure of the FB-RIB, and
o the groupings that make up the FB-RIB o the groupings that make up the FB-RIB
All structures have two types: configuration/ephemeral state and All structures have two types: configuration/ephemeral state and
operational state. operational state.
This yang model describes three types of FB-RIBS: configuration, This yang model allows for three types of FB-RIB installations in
I2RS, and BGP Flow Specification. The configuration FB-RIB yang three types of datastores:
module is config state ("config true" and "ephemeral false") and
survives a reboot. The I2RS FB-RB yang model is reboot ephemeral configuration (Config=TRUE, ephemeral=false, opstate definitions)
("config true" and "ephemeral true;"). The BGP Flow Specification
Filter-Based RIB stores policy which is received by the BGP peers. ephemeral control plane (E.g. I2RS Agent, config=TRUE,
The BGP configuration contains a flow-specification as part of its ephemeral=TRUE, opstate definitions), and
configuration, and the ability to export this flow specification to
other BGP peers. The BGP local configuration with the flow non-ephemeral control plane datastore (e.g. dBGP FB-FIB with
specification is consider ("config true"), and it is possible to be config=TRUE; ephemeral=false, opstate which stores BGP Flow
ephemeral ("ephemeral true") or local configuration ("ephemeral Specification received by bgp speaker from BGP peers).
false" ). The BGP flow specifications received from peers are
derived state, just like other BGP dervised state. Each of these cases is differentiated by using an "if-feature" to
provide unique RIB under the routing instance.
Configuration RIBS Configuration RIBS
+-----------------------------------------+ +-----------------------------------------+
| routing instance | | routing instance |
+-------|-------------|----------------|--+ +-------|-------------|----------------|--+
| | | | | |
| | | | | |
+---------|----+ +-----|-----+ +--------|-----+ +---------|----+ +-----|-----+ +--------|-----+
|config-fb-rib | |i2rs-fb-rib| |bgp-fs-fb-rib | |config-fb-rib | |i2rs-fb-rib| |bgp-fs-fb-rib |
| | | | |config only | | | | | | |
+------|-------+ +-----|-----+ +------|-------+ +------|-------+ +-----|-----+ +------|-------+
|............:....|...............| |............:....|...............|
: (uses common structures : (uses common structures
: in separate lists of FB-RIBs) : in separate lists of FB-RIBs)
+--------|----+ +--------|----+
|fb-ribs* | |fb-ribs* |
| | | |
+--|----------+ +--|----------+
| |
skipping to change at page 6, line 44 skipping to change at page 6, line 44
o fb-rib - that contains the structures for the filter-based o fb-rib - that contains the structures for the filter-based
grouping grouping
o fb-rib-types - that contains the structures for groupings within o fb-rib-types - that contains the structures for groupings within
the filter-based RIBS the filter-based RIBS
These structures are contained within the yang section in this draft. These structures are contained within the yang section in this draft.
The packet-reception ECA policy yang module is contained in the draft The packet-reception ECA policy yang module is contained in the draft
[I-D.hares-i2rs-pkt-eca-data-model]. [I-D.ietf-i2rs-pkt-eca-data-model].
For those who desire more information regarding the logic behind the For those who desire more information regarding the logic behind the
I2RS Filter-Based RIB, please see the Informational Model at: I2RS Filter-Based RIB, please see the Informational Model at:
[I-D.kini-i2rs-fb-rib-info-model]. [I-D.ietf-i2rs-fb-rib-info-model].
4.1. Top Level Yang Structure for ietf-fb-rib 4.1. Top Level Yang Structure for ietf-fb-rib
The Top-level Yang structure for a global FB-RIB types (similar to The Top-level Yang structure for a global FB-RIB types (similar to
acl) is not defined for filter-based RIBS. The I2RS Filter-Based RIB acl) is not defined for filter-based RIBS. The I2RS Filter-Based RIB
should be defined under this structure under a routing instance. The should be defined under this structure under a routing instance. The
three things under this RIB would be: configured Filter-Based RIB three things under this RIB would be: configured Filter-Based RIB
(aka Policy routing), I2RS reboot Ephemeral Filter-Based RIB, and BGP (aka Policy routing), I2RS reboot Ephemeral Filter-Based RIB, and BGP
Flow Specification's Filter-Based RIB. All of these RIBs have Flow Specification's Filter-Based RIB. All of these RIBs have
similar actions. similar actions.
skipping to change at page 9, line 22 skipping to change at page 9, line 22
| | +--rw name string | | +--rw name string
| | +--rw intf if:interface | | +--rw intf if:interface
| +--rw default-rib | +--rw default-rib
| | +--rw rt-rib string | | +--rw rt-rib string
| | +--rw config-rib string; // config rib name | | +--rw config-rib string; // config rib name
| | +--rw i2rs-rib:routing-instance:name | | +--rw i2rs-rib:routing-instance:name
| | +--rw i2rs-rib string; //ephemeral rib name | | +--rw i2rs-rib string; //ephemeral rib name
| | +--rw bgp-instance-name string | | +--rw bgp-instance-name string
| | +--rw bgp-rib string //session ephemeral | | +--rw bgp-rib string //session ephemeral
| +--rw fb-rib-refs | +--rw fb-rib-refs
| | +--rw fb-rib-update-ref uint32 /count of writes | | +--rw fb-rib-update-ref uint32
| | /count of writes
| +--rw instance-using* | +--rw instance-using*
| | device:networking-instance:networking-instance-name | | device:networking-instance:\
| +--use pkt-eca:pkt-eca-policy-set | | /networking-instance-name
| +--uses pkt-eca:pkt-eca-policy-set
rt-rib - refer to static rib. | +--uses acls:access-lists
Figure 6: FB RIB Type Structure Figure 6: FB RIB Type Structure
Note: acls:access-lists is the list of ACL filters in
[I-D.ietf-netmod-acl-model].
HIgh Level Yang HIgh Level Yang
+--rw fb-ribs-oper-status +--rw fb-ribs-oper-status
+--rw fb-rib-oper-status* [fb-rib-name] +--rw fb-rib-oper-status* [fb-rib-name]
uses pkt-eca:pkt-eca-opstate uses pkt-eca:pkt-eca-opstate
5. yang models 5. yang models
5.1. Filter-Based RIB types 5.1. Filter-Based RIB types
<CODE BEGINS> file "ietf-fb-rib-types@2016-02-09.yang" <CODE BEGINS> file "ietf-fb-rib-types@2017-03-13.yang"
module ietf-fb-rib-types { module ietf-fb-rib-types {
yang-version "1"; yang-version "1";
// namespace // namespace
namespace "urn:ietf:params:xml:ns:yang:ietf-fb-rib-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-fb-rib-types";
prefix "fb-rib-t"; prefix "fb-rib-t";
import ietf-interfaces {prefix "if";} import ietf-interfaces {prefix "if";}
import ietf-routing {prefix "rt";} import ietf-routing {prefix "rt";}
import ietf-pkt-eca-policy {prefix "pkt-eca";} import ietf-pkt-eca-policy {prefix "pkt-eca";}
import ietf-access-control-lists {prefix "acls";}
// meta // meta
organization organization
"IETF"; "IETF";
contact contact
"email: shares@ndzh.com; "email: shares@ndzh.com;
email: sriganesh.kini@ericsson.com email: sriganesh.kini@ericsson.com
email: cengiz@packetdesign.com email: cengiz@packetdesign.com
email: ivandean@gmal.org email: ivandean@gmal.org
skipping to change at page 10, line 33 skipping to change at page 10, line 38
Copyright (c) 2015 IETF Trust and the persons identified as Copyright (c) 2015 IETF Trust and the persons identified as
the document authors. All rights reserved. the document authors. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's Legal License set forth in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info)."; (http://trustee.ietf.org/license-info).";
revision "2016-02-09" { revision "2017-03-13" {
description description
"Filter-Based RIB protocol "; "Filter-Based RIB protocol ";
reference "draft-hares-i2rs-fb-rib-data-model-01"; reference "draft-ietf-i2rs-fb-rib-data-model-01";
} }
typedef fb-rib-type-def { typedef fb-rib-type-def {
type identityref { type identityref {
base "fb-rib-type"; base "fb-rib-type";
} }
description description
"This type is used to refer to "This type is used to refer to
source of Filter-Based RIB: source of Filter-Based RIB:
configuration, I2RS, Flow-Spec."; configuration, I2RS, Flow-Spec.";
} }
identity fb-rib-type { identity fb-rib-type {
description description
"This type is used to refer to "This type is used to refer to
source of Filter-Based RIB: source of Filter-Based RIB:
configuration, I2RS, Flow-Spec."; configuration, I2RS, Flow-Spec.";
} }
skipping to change at page 15, line 13 skipping to change at page 15, line 19
description description
" name of instance using this fb-rib " name of instance using this fb-rib
rt:routing-instance"; rt:routing-instance";
} }
description "instances using description "instances using
this fb-rib"; this fb-rib";
} }
// ordered rule list + group list // ordered rule list + group list
uses pkt-eca:pkt-eca-policy-set; uses pkt-eca:pkt-eca-policy-set;
description "Configuration of // ordered acl list
uses acls:access-lists;
description "Configuration of
an filter-based rib list"; an filter-based rib list";
} }
description "fb-rib group"; description "fb-rib group";
} }
grouping fb-ribs-oper-status { grouping fb-ribs-oper-status {
list fb-rib-oper-status { list fb-rib-oper-status {
key fb-rib-name; key fb-rib-name;
leaf fb-rib-name { leaf fb-rib-name {
type string; type string;
description "rib name"; description "rib name";
} }
leaf pkt-eca-cfged {
type boolean;
description
"pkt eca configured";
}
leaf acls-cfged {
type boolean;
description
"acls configured";
}
uses pkt-eca:pkt-eca-opstate; uses pkt-eca:pkt-eca-opstate;
description "Configuration of description
"Configuration of
an filter-based rib list"; an filter-based rib list";
} }
description "list of FB-FIB operational description
"list of FB-FIB operational
status"; status";
} }
} }
<CODE ENDS> <CODE ENDS>
5.2. FB-RIB 5.2. FB-RIB
<CODE BEGINS> file "ietf-fb-rib@2016-02-09.yang" <CODE BEGINS> file "ietf-fb-rib@2017-03-13.yang"
module ietf-fb-rib { module ietf-fb-rib {
yang-version "1"; yang-version "1";
// namespace // namespace
namespace "urn:ietf:params:xml:ns:yang:ietf-fb-rib"; namespace "urn:ietf:params:xml:ns:yang:ietf-fb-rib";
// replace with iana namespace when assigned // replace with iana namespace when assigned
prefix "fb-rib"; prefix "fb-rib";
// import some basic inet types // import some basic inet types
import ietf-yang-types {prefix "yang";} import ietf-yang-types {prefix "yang";}
skipping to change at page 16, line 25 skipping to change at page 16, line 44
email: ivandean@gmail.org email: ivandean@gmail.org
email: shares@ndzh.com; email: shares@ndzh.com;
email: linda.dunbar@huawei.com; email: linda.dunbar@huawei.com;
email: russ@riw.com; email: russ@riw.com;
"; ";
description description
"This Top level module describes a YANG model for the I2RS "This Top level module describes a YANG model for the I2RS
Filter-based RIB which is an global protocol independent FB RIB module."; Filter-based RIB which is an global protocol independent FB RIB module.";
revision "2016-02-09" { revision "2017-03-13" {
description "initial revision"; description "initial revision";
reference "draft-hares-i2rs-fb-rib-data-model-01"; reference "draft-ietf-i2rs-fb-rib-data-model-01";
} }
feature config-filter-based-RIB { feature config-filter-based-RIB {
description description
"This feature means that a node support "This feature means that a node support
config filter-based rib."; config filter-based rib.";
} }
feature I2RS-filter-based-RIB { feature I2RS-filter-based-RIB {
description description
"This feature means that a node support "This feature means that a node support
I2RS filter-based rib."; I2RS filter-based rib.";
} }
feature BGP-FS-filter-based-RIB { feature BGP-FS-filter-based-RIB {
skipping to change at page 18, line 42 skipping to change at page 19, line 20
change the operation of forwarding by allow dyanmic policy and change the operation of forwarding by allow dyanmic policy and
ephemeral RIBs to alter the traffic paths set by routing ephemeral RIBs to alter the traffic paths set by routing
configuration. Care must be taken in deployments to use the configuration. Care must be taken in deployments to use the
appropriate security and operational control to make use of the tools appropriate security and operational control to make use of the tools
the I2RS RIB and I2RS FB-RIB provide. the I2RS RIB and I2RS FB-RIB provide.
8. References 8. References
8.1. Normative References: 8.1. Normative References:
[I-D.hares-i2rs-pkt-eca-data-model] [I-D.ietf-i2rs-pkt-eca-data-model]
Hares, S., Wu, Q., and R. White, "Filter-Based Packet Hares, S., Wu, Q., and R. White, "Filter-Based Packet
Forwarding ECA Policy", draft-hares-i2rs-pkt-eca-data- Forwarding ECA Policy", draft-ietf-i2rs-pkt-eca-data-
model-02 (work in progress), February 2016. model-02 (work in progress), October 2016.
[I-D.ietf-i2rs-architecture]
Atlas, A., Halpern, J., Hares, S., Ward, D., and T.
Nadeau, "An Architecture for the Interface to the Routing
System", draft-ietf-i2rs-architecture-15 (work in
progress), April 2016.
[I-D.ietf-i2rs-rib-data-model] [I-D.ietf-i2rs-rib-data-model]
Wang, L., Ananthakrishnan, H., Chen, M., Wang, L., Ananthakrishnan, H., Chen, M.,
amit.dass@ericsson.com, a., Kini, S., and N. Bahadur, "A amit.dass@ericsson.com, a., Kini, S., and N. Bahadur, "A
YANG Data Model for Routing Information Base (RIB)", YANG Data Model for Routing Information Base (RIB)",
draft-ietf-i2rs-rib-data-model-05 (work in progress), draft-ietf-i2rs-rib-data-model-07 (work in progress),
March 2016. January 2017.
[I-D.ietf-i2rs-rib-info-model]
Bahadur, N., Kini, S., and J. Medved, "Routing Information
Base Info Model", draft-ietf-i2rs-rib-info-model-08 (work
in progress), October 2015.
[I-D.ietf-netmod-acl-model] [I-D.ietf-netmod-acl-model]
Bogdanovic, D., Koushik, K., Huang, L., and D. Blair, Bogdanovic, D., Koushik, K., Huang, L., and D. Blair,
"Network Access Control List (ACL) YANG Data Model", "Network Access Control List (ACL) YANG Data Model",
draft-ietf-netmod-acl-model-07 (work in progress), March draft-ietf-netmod-acl-model-10 (work in progress), March
2016. 2017.
[I-D.ietf-netmod-routing-cfg] [I-D.ietf-netmod-routing-cfg]
Lhotka, L. and A. Lindem, "A YANG Data Model for Routing Lhotka, L. and A. Lindem, "A YANG Data Model for Routing
Management", draft-ietf-netmod-routing-cfg-21 (work in Management", draft-ietf-netmod-routing-cfg-25 (work in
progress), March 2016. progress), November 2016.
[I-D.kini-i2rs-fb-rib-info-model]
Kini, S., Hares, S., Dunbar, L., Ghanwani, A., Krishnan,
R., Bogdanovic, D., and R. White, "Filter-Based RIB
Information Model", draft-kini-i2rs-fb-rib-info-model-03
(work in progress), February 2016.
8.2. Informative References 8.2. Informative References
[I-D.acee-rtgwg-yang-rib-extend] [I-D.ietf-i2rs-fb-rib-info-model]
Lindem, A. and Y. Qu, "RIB YANG Data Model", draft-acee- Kini, S., Hares, S., Dunbar, L., Ghanwani, A., Krishnan,
rtgwg-yang-rib-extend-01 (work in progress), March 2016. R., Bogdanovic, D., and R. White, "Filter-Based RIB
Information Model", draft-ietf-i2rs-fb-rib-info-model-00
(work in progress), June 2016.
[I-D.ietf-i2rs-usecase-reqs-summary] [I-D.ietf-i2rs-rib-info-model]
Hares, S. and M. Chen, "Summary of I2RS Use Case Bahadur, N., Kini, S., and J. Medved, "Routing Information
Requirements", draft-ietf-i2rs-usecase-reqs-summary-02 Base Info Model", draft-ietf-i2rs-rib-info-model-10 (work
(work in progress), March 2016. in progress), December 2016.
[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>.
[RFC7921] Atlas, A., Halpern, J., Hares, S., Ward, D., and T.
Nadeau, "An Architecture for the Interface to the Routing
System", RFC 7921, DOI 10.17487/RFC7921, June 2016,
<http://www.rfc-editor.org/info/rfc7921>.
Authors' Addresses Authors' Addresses
Susan Hares Susan Hares
Huawei Huawei
7453 Hickory Hill 7453 Hickory Hill
Saline, MI 48176 Saline, MI 48176
USA USA
Email: shares@ndzh.com Email: shares@ndzh.com
 End of changes. 46 change blocks. 
100 lines changed or deleted 115 lines changed or added

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