Identification of Overlay Operations, Administration, and Maintenance (OAM)
draft-mirsky-rtgwg-oam-identify-04
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Greg Mirsky | ||
| Last updated | 2020-08-29 (latest revision 2020-02-26) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-mirsky-rtgwg-oam-identify-04.txt
https://www.ietf.org/archive/id/draft-mirsky-rtgwg-oam-identify-04.txt
Abstract
This document analyzes how the presence of Operations, Administration, and Maintenance (OAM) control command and/or special data is identified in some overlay networks and an impact on the choice of identification may have on OAM functionality.
Authors
Greg Mirsky (gregimirsky@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)