Rationale for Transport-independent Common Operations, Administration and Maintenance (OAM)
draft-mwnpkazcap-rtgwg-common-oam-00

Document Type Expired Internet-Draft (individual)
Last updated 2016-04-21 (latest revision 2015-10-19)
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-mwnpkazcap-rtgwg-common-oam-00.txt

Abstract

This document discusses set of Operations, Administration and Maintenance (OAM) tools that can be used as common OAM independent of specific encapsulation at server layer. Requirements toward server layer to support common OAM are listed as well.

Authors

Gregory Mirsky (gregory.mirsky@ericsson.com)
Russ White (russ@riw.us)
Erik Nordmark (nordmark@acm.org)
Carlos Pignataro (cpignata@cisco.com)
Nagendra Kumar (naikumar@cisco.com)
Sam Aldrin (aldrin.ietf@gmail.com)
Lianshu Zheng (vero.zheng@huawei.com)
Mach Chen (mach.chen@huawei.com)
Nobo Akiya (nobo.akiya.dev@gmail.com)
Juniper Networks (santoshpk@juniper.net)

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