Use Cases and Requirements for Layer Independent OAM Management in multi-layer environments
draft-king-opsawg-lime-multi-layer-oam-use-case-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Daniel King , Mohamed Boucadair , Sam Aldrin , Greg Mirsky , Mishael Wexler | ||
Last updated | 2015-03-29 (Latest revision 2014-09-25) | ||
Replaces | draft-king-opsawg-time-multi-layer-oam-use-case | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
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
As operators deploy and operate multi-layer networks and diverse transport technologies, layer independent Operations, Maintenance & Administration Management (OAM) would be beneficial for monitoring and troubleshooting operations of network and service infrastructure. This document identifies and discusses the key use-cases and high- level requirements for layer independent Operations, Administration, and Maintenance management to facilitate operations and maintenance in multi-layer and multi-domain networks utilizing a wide variety of heterogeneous networking technologies.
Authors
Daniel King
Mohamed Boucadair
Sam Aldrin
Greg Mirsky
Mishael Wexler
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)