Skip to main content

Filter-Based Packet Forwarding ECA Policy
draft-hares-i2rs-pkt-eca-data-model-02

Document Type Replaced Internet-Draft (candidate for i2rs WG)
Expired & archived
Authors Susan Hares , Qin Wu , Russ White
Last updated 2016-04-07 (Latest revision 2016-02-09)
Replaces draft-hares-i2rs-bnp-eca-data-model
Replaced by draft-ietf-i2rs-pkt-eca-data-model
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Call For Adoption By WG Issued
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-i2rs-pkt-eca-data-model
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

This document describes the yang data model for packet forwarding policy that filters received packets and forwards (or drops) the packets. Prior to forwarding the packets out other interfaces, some of the fields in the packets may be modified. If one considers the packet reception an event, this packet policy is a minimalistic Event-Match Condition-Action policy. This policy controls forwarding of packets received by a routing device on one or more interfaces on which this policy is enabled. The policy is composed of an ordered list of policy rules. Each policy policy rule contains a set of match conditions that filters for packets plus a set of actions to modify the packet and forward packets. The match conditions can match tuples in multiple layers (L1-L4, application), interface received on, and and other conditions regarding the packet (size of packet, time of day). The modify packet actions allow for setting things within the packet plus decapsulation and encapsulation packet. The forwarding actions include forwarding via interfaces, tunnels, or nexthops and dropping the packet. The policy model can be used with the session ephemeral (BGP Flow Specifications), reboot ephemeral state (I2RS ephemeral), and non-ephemeral routing/forwarding state (e.g. configuration state ).

Authors

Susan Hares
Qin Wu
Russ White

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)