OAM tool for RBridges: Multi-destination Ping
draft-yizhou-trill-multi-destination-ping-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yizhou Li , Hao Weiguo , David Mich Bond , Vishwas Manral | ||
| Last updated | 2012-11-05 (Latest revision 2012-05-03) | ||
| 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
Unicast and multi-destination data frame may follow the different path in TRILL network. We need the ping and traceroute like applications for the connectivity testing and fault isolation on the multi-destination path in addition to the unicast path. This document specifies the format and handling of the new TRILL OAM protocol messages and TLVs which can be used for the multi-destination OAM.
Authors
Yizhou Li
Hao Weiguo
David Mich Bond
Vishwas Manral
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)