SFC Header Mapping for Legacy SF
draft-song-sfc-legacy-sf-mapping-08
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Haibin Song , Jianjie You , Lucy Yong , Yuanlong Jiang , Linda Dunbar , Nicolas Bouthors , David Dolson | ||
| Last updated | 2017-03-10 (Latest revision 2016-09-06) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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
A Service Function Chain (SFC) defines a set of abstract Service Functions (SF) and ordering constraints that must be applied to packets and/or frames selected as a result of classification. One assumption of this document is that legacy service functions can participate in service function chains without supporting the SFC header, or even being aware of it. This document provides some of the mechanisms between an SFC proxy and an SFC-unaware service function (herein termed "legacy SF"), to identify the SFC header associated with a packet that is returned from a legacy SF, without an SFC header being explicitly carried in the wired protocol between SFC proxy and legacy SF.
Authors
Haibin Song
Jianjie You
Lucy Yong
Yuanlong Jiang
Linda Dunbar
Nicolas Bouthors
David Dolson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)