Rationale for Transport-independent Common Operations, Administration and Maintenance (OAM)
draft-mwnpkazcap-rtgwg-common-oam-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Greg Mirsky , Russ White , Erik Nordmark , Carlos Pignataro , Nagendra Kumar Nainar , Sam Aldrin , Lianshu Zheng , Mach Chen , Nobo Akiya , Santosh Pallagatti | ||
Last updated | 2016-04-21 (Latest revision 2015-10-19) | ||
RFC stream | (None) | ||
Intended RFC status | (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 discusses set of Operations, Administration and Maintenance (OAM) tools that can be used as common OAM independent of specific encapsulation at server layer. Requirements toward server layer to support common OAM are listed as well.
Authors
Greg Mirsky
Russ White
Erik Nordmark
Carlos Pignataro
Nagendra Kumar Nainar
Sam Aldrin
Lianshu Zheng
Mach Chen
Nobo Akiya
Santosh Pallagatti
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)