Requirements for Operations, Administration and Maintenance (OAM) in TRILL
draft-tissa-trill-oam-req-02
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Tissa Senevirathne , David Mich Bond , Sam Aldrin , Yizhou Li , Rohit Watve , Anoop Ghanwani , Naveen Nimmu , Radia Perlman , Tal Mizrahi | ||
Last updated | 2012-07-31 (Latest revision 2012-06-29) | ||
Replaced by | draft-ietf-trill-oam-req | ||
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-ietf-trill-oam-req | |
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
OAM (Operations, Administration and Maintenance) is a general term used to identify functions and toolsets to troubleshoot and monitor networks. This document presents, OAM Requirements applicable to TRILL. Also presented in this document is the proposed frame structure for TRILL OAM messages.
Authors
Tissa Senevirathne
David Mich Bond
Sam Aldrin
Yizhou Li
Rohit Watve
Anoop Ghanwani
Naveen Nimmu
Radia Perlman
Tal Mizrahi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)