Network Service Header (NSH) MD Type 1: Context Header Allocation (Data Center)
draft-ietf-sfc-nsh-dc-allocation-00
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
---|---|---|---|
Authors | Jim Guichard , Michael Smith , Surendra Kumar , Sumandra Majee , Puneet Agarwal , Kevin Glavin , Youcef Laribi , Tal Mizrahi | ||
Last updated | 2018-08-16 (Latest revision 2018-02-12) | ||
Replaces | draft-guichard-sfc-nsh-dc-allocation | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
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 provides a recommended default allocation for the Network Service Header (NSH) MD Type 1 fixed length context header when NSH is used for Service Function Chaining within a data center.
Authors
Jim Guichard
Michael Smith
Surendra Kumar
Sumandra Majee
Puneet Agarwal
Kevin Glavin
Youcef Laribi
Tal Mizrahi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)