An Overview of Operations, Administration, and Maintenance (OAM) Mechanisms
draft-mizrahi-opsawg-oam-overview-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tal Mizrahi | ||
| Last updated | 2012-05-15 (Latest revision 2009-10-07) | ||
| Replaced by | draft-ietf-opsawg-oam-overview | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-opsawg-oam-overview | |
| 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
Operations, Administration, and Maintenance (OAM) is a general term that refers to detecting and reporting link failures. OAM mechanisms have been defined for various layers in the protocol stack, and are used with a variety of protocols. This document presents an overview of the OAM mechanisms that have been defined and are currently being defined by the IETF, as well as a comparison to other OAM mechanisms that have been defined by the IEEE and ITU-T.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)