Packet Generation in Service Function Chains
draft-penno-sfc-packet-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Reinaldo Penno , Carlos Pignataro , Chui-Tin Yen , Eric Wang , Kent Leung | ||
| Last updated | 2016-04-07 (Latest revision 2015-10-05) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
Service Functions (e.g., Firewall, NAT, Proxies and Intrusion Prevention Systems) generate packets in the reverse flow direction to the source of the current in-process packet/flow. In this document we discuss and propose how to support this required functionality within the SFC framework.
Authors
Reinaldo Penno
Carlos Pignataro
Chui-Tin Yen
Eric Wang
Kent Leung
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)