"The OAM Acronym Soup"
draft-andersson-mpls-tp-oam-def-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Loa Andersson , Malcolm Betts , Ron Bonica , Huub Helvoort , Dan Romascanu | ||
| Last updated | 2010-08-03 (Latest revision 2009-01-16) | ||
| Replaced by | draft-ietf-opsawg-mpls-tp-oam-def | ||
| 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-mpls-tp-oam-def | |
| 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
At first glance the acronym "OAM" seems to be well known and well understood. Looking at it a bit more closely reveals a set of recurring problems that are revisited time and again. This document has one primary and a secondary goal. The primary goal is to find an understanding of OAM that is feasible for the MPLS Transport Profile (MPLS-TP)effort. The secondary goal is to make this understanding applicable in a wider scope
Authors
Loa Andersson
Malcolm Betts
Ron Bonica
Huub Helvoort
Dan Romascanu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)