"The OAM Acronym Soup"
draft-andersson-mpls-tp-oam-def-01

Document Type Replaced Internet-Draft (individual)
Last updated 2010-08-03 (latest revision 2009-01-16)
Replaced by draft-ietf-opsawg-mpls-tp-oam-def
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
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
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-andersson-mpls-tp-oam-def-01.txt

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 (loa@pi.nu)
Malcolm Betts (betts01@nortel.com)
Ron Bonica (rbonica@juniper.net)
Huub Helvoort (hhelvoort@chello.nl)
Dan Romascanu (dromasca@avaya.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)