Service Function Chaining Service, Subscriber and Host Identification Use Cases and Metadata

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2017-07-20 (latest revision 2017-01-16)
Replaced by draft-sfc-serviceid-header
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized 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


This document discusses considerations related to passing service-, host- and subscriber-related information to upstream Service Functions for the sake of policy enforcement and appropriate SFC- inferred forwarding. Once the information is consumed by SFC-aware elements of an SFC-enabled domain, the information is stripped from packets so that privacy-sensitive information is not leaked outside an SFC-enabled domain.


Mohamed Boucadair (
Dirk Hugo (
Behcet Sarikaya (

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