Service Function Chaining: Subscriber and Service Identification Use Cases and Variable-Length NSH Context Headers
draft-sarikaya-sfc-hostid-serviceheader-07
Document | Type |
Replaced Internet-Draft
(sfc WG)
Expired & archived
|
|
---|---|---|---|
Authors | Behcet Sarikaya , Mohamed Boucadair , Dirk Von Hugo | ||
Last updated | 2018-10-24 (Latest revision 2018-06-21) | ||
Replaced by | draft-sfc-serviceid-header | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Held by WG | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-sfc-serviceid-header | |
Consensus boilerplate | Unknown | ||
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 how to inform Service Functions about service- and subscriber-related information 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, it is stripped from packets when they leave the SFC-enabled domain. Thus privacy-sensitive information is not leaked outside the domain.
Authors
Behcet Sarikaya
Mohamed Boucadair
Dirk Von Hugo
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)