Service Function Chaining Service, Subscriber and Host Identification Use Cases and Metadata
draft-sarikaya-sfc-hostid-serviceheader-03
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Mohamed Boucadair , Dirk Von Hugo , Behcet Sarikaya | ||
| Last updated | 2017-01-06 (Latest revision 2016-07-05) | ||
| Replaced by | draft-sfc-serviceid-header | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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.
Authors
Mohamed Boucadair
Dirk Von Hugo
Behcet Sarikaya
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)