Inter-Carrier OAM Requirements
draft-georgiades-opsawg-intercar-oam-req-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Michael Georgiades , Filippo Cugini , David Berechya , Oscar Gonzalez de Dios | ||
| Last updated | 2012-11-26 (Latest revision 2012-05-25) | ||
| RFC stream | (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
This draft specifies requirements for inter-carrier OAM supporting end-to-end OAM functionality and mechanisms development in a multi- operator environment. It reviews the already proposed OAM requirements addressed in IETF [RFC5706, RFC5860], ITU-T [Y.1730], MEF [MEFOAM] and IEEE [IEEE1, IEEE2] which were mainly proposed on a per transport technology basis. This document specifies additional requirements for the inter-carrier OAM operations.
Authors
Michael Georgiades
Filippo Cugini
David Berechya
Oscar Gonzalez de Dios
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)