SFC Header Mapping for Legacy SF
draft-song-sfc-legacy-sf-mapping-08

Document Type Expired Internet-Draft (individual)
Last updated 2017-03-10 (latest revision 2016-09-06)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-song-sfc-legacy-sf-mapping-08.txt

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 (haibin.song@huawei.com)
Jianjie You (youjianjie@huawei.com)
Lucy Yong (lucy.yong@huawei.com)
Yuanlong Jiang (jiangyuanlong@huawei.com)
Linda Dunbar (ldunbar@huawei.com)
Nicolas Bouthors (Nicolas.bouthors@qosmos.com)
David Dolson (ddolson@sandvine.com)

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