Network Service Header (NSH) Context Header Allocation (Data Center)
draft-guichard-sfc-nsh-dc-allocation-05
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Jim Guichard , Michael Smith , Surendra Kumar , Sumandra Majee , Puneet Agarwal , Kevin Glavin , Youcef Laribi | ||
| Last updated | 2017-02-13 (Latest revision 2016-08-12) | ||
| Replaced by | draft-ietf-sfc-nsh-dc-allocation | ||
| 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 provides a recommended default allocation for the fixed context headers within a Network Service Header (NSH). NSH is defined in [I-D.ietf-sfc-nsh]. The allocation scheme is relevant when NSH is used for Service Function Chaining within a data center and may be used to support use cases such as those described in [I-D.ietf-sfc-dc-use-cases].
Authors
Jim Guichard
Michael Smith
Surendra Kumar
Sumandra Majee
Puneet Agarwal
Kevin Glavin
Youcef Laribi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)