Geneve applicability for service function chaining
draft-boutros-nvo3-geneve-applicability-for-sfc-03
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Sami Boutros , Dharma Rajan , Philip Kippen , Pierluigi Rolando , Jim Guichard , Sam Aldrin | ||
| Last updated | 2019-09-07 (Latest revision 2019-03-06) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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 describes the applicability of using Generic Network Virtualization Encapsulation (Geneve), to carry the service function path (SFP) information, and the network service header (NSH) encapsulation. The SFP information will be carried in Geneve option TLV(s).
Authors
Sami Boutros
Dharma Rajan
Philip Kippen
Pierluigi Rolando
Jim Guichard
Sam Aldrin
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)