SFC Header Mapping for Legacy SF
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|Authors||Haibin Song , Jianjie You , Lucy Yong , Yuanlong Jiang , Linda Dunbar , Nicolas Bouthors , David Dolson|
|Last updated||2016-02-20 (Latest revision 2015-08-19)|
|Stream||Stream state||(No stream defined)|
|RFC Editor Note||(None)|
|Send notices to||(None)|
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 having support for the SFC header, or even being aware of it. This document provides a mechanism 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.
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)