Use Cases and Requirements for Transport-Independent Multiple Layer OAM
draft-king-opsawg-time-multi-layer-oam-use-case-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Daniel King , Mohamed Boucadair , Sam Aldrin , Greg Mirsky , Qin Wu | ||
| Last updated | 2014-10-24 (Latest revision 2014-07-04) | ||
| Replaced by | draft-king-opsawg-lime-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 | Replaced by draft-king-opsawg-lime-multi-layer-oam-use-case | |
| 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
This document identifies and discusses use-cases and high level requirements for transport technology independent OAM that need to interface multi-layer or multi-domain transport networks to cover heterogeneous networking technologies. As providers face multi-layer networks and diverse transport technologies, generic and integrated OAM is desirable for simplifying network operations and maintenance.
Authors
Daniel King
Mohamed Boucadair
Sam Aldrin
Greg Mirsky
Qin Wu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)