Service Function Chaining (SFC): Subscriber and Host Identification Considerations

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2016-03-12 (latest revision 2015-09-09)
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 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 functional elements, the information is stripped from packets so that privacy-sensitive information is not leaked outside an SFC-enabled domain.


Behcet Sarikaya (
Dirk Hugo (
Mohamed Boucadair (

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