OAM Header for use in Overlay Networks
draft-ooamdt-rtgwg-ooam-header-03
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Greg Mirsky , Nagendra Kumar Nainar , Deepak Kumar , Mach Chen , Yizhou Li , David Dolson | ||
| Last updated | 2017-09-14 (Latest revision 2017-03-13) | ||
| 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 introduces Overlay Operations, Administration, and Maintenance (OOAM) Header to be used in overlay networks to create Overlay Associated Channel (OAC) to ensure that OOAM control packets are in-band with user traffic and de-multiplex OOAM protocols.
Authors
Greg Mirsky
Nagendra Kumar Nainar
Deepak Kumar
Mach Chen
Yizhou Li
David Dolson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)