Problem Statement and Architecture for Transport-Independent Multiple Layer OAM

Document Type Replaced Internet-Draft (individual)
Authors Qin Wu  , Mishael Wexler  , Mohamed Boucadair  , Sam Aldrin  , Greg Mirsky  , Pradeep Jain 
Last updated 2014-10-24 (latest revision 2014-07-04)
Replaced by draft-edprop-opsawg-multi-layer-oam-ps
Stream (None)
Intended RFC status (None)
Expired & archived
plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-edprop-opsawg-multi-layer-oam-ps
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


Operations, Administration, and Maintenance (OAM) mechanisms are critical building blocks in network operations that are used for service assurance, fulfillment, or service diagnosis, troubleshooting, and repair. The current practice is that many technologies rely on their own OAM protocols that are exclusive to a given layer. There is little consolidation of OAM in either data plane or management plane nor well-documented inter-layer OAM operations. Vendors and Operators dedicate significant resources and effort through the whole OAM life-cycle each time when a new technology is (to be) introduced. This is even exacerbated when dealing with integration of OAM across multiple technologies. This document describes the problem space and defines an architecture for the generic and integrated OAM with a focus of multi-layer and cross-layer considerations.


Qin Wu (
Mishael Wexler (
Mohamed Boucadair (
Sam Aldrin (
Greg Mirsky (
Pradeep Jain (

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