Problem Statement for Layer and Technology Independent OAM in a Multi- Layer Environment
draft-edprop-opsawg-multi-layer-oam-ps-02

Document Type Expired Internet-Draft (individual)
Last updated 2015-03-30 (latest revision 2014-09-26)
Replaces draft-ww-opsawg-multi-layer-oam
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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-edprop-opsawg-multi-layer-oam-ps-02.txt

Abstract

Operations, Administration, and Maintenance (OAM) mechanisms are critical building blocks in network operations. They used for service fulfillment assurance, and for service diagnosis, troubleshooting, and repair. The current practice is that many technologies rely on their own OAM protocols and procedures that are exclusive to a given layer. At present, there is little consolidation of OAM in the management plane or well-documented inter-layer OAM operation. Vendors and operators dedicate significant resources and effort through the whole OAM life-cycle each time a new technology is introduced. This is exacerbated when dealing with integration of OAM into overlay networks, which require better OAM visibility since there is no method to exchange OAM information between overlay and underlay. This document analyzes the problem space for multi-layer OAM in the management plane with a focus on layer and technology independent OAM management considerations. It concludes that an attempt to define an architecture for consolidated management should be undertaken, and if this attempt satisfies key objectives, a gap analysis and a program of standardization should follow.

Authors

Qin Wu (bill.wu@huawei.com)
Mishael Wexler (mishael.wexler@huawei.com)
Dan Romascanu (dromasca@avaya.com)
Tom Taylor (tom.taylor.stds@gmail.com)

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