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) | |
|---|---|---|---|
| Last updated | 2018-10-24 (latest revision 2018-06-21) | ||
| Replaced by | draft-sfc-serviceid-header | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | Held by WG | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-sfc-serviceid-header | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-sarikaya-sfc-hostid-serviceheader-07.txt
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
(sarikaya@ieee.org)
Mohamed Boucadair
(mohamed.boucadair@orange.com)
Dirk Hugo
(dirk.von-hugo@telekom.de)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)