A Framework for SFC Metadata

Document Type Expired Internet-Draft (individual)
Authors sunilvk@f5.com  , Linda Dunbar  , David Dolson 
Last updated 2017-01-08 (latest revision 2016-07-07)
Stream (None)
Intended RFC status (None)
Expired & archived
plain text htmlized pdfized 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


Various types of metadata are applicable to Service Function Chaining (SFC). Metadata can be used for many purposes, such as conveying processing information, resource usage, and flow specific information, from prior nodes along the Service Function Path. It can also be vendor specific to leverage vendor capabilities and hint to downstream Service functions dynamically for improved performance. In contrast, metadata carried out of band introduces latency and overhead with inefficiency and non-synchronous to real- time traffic. A Service Function (SF) that needs to process the information carried by the metadata may need detailed information of the metadata structure carried by the packets and can have local policies based on metadata. The purpose of this document is to specify a framework and information model on how to provision information about metadata among classifiers and service functions on a service function chain.


sunilvk@f5.com (sunilvk@f5.com)
Linda Dunbar (ldunbar@huawei.com)
David Dolson (ddolson@sandvine.com)

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