OAM tool for RBridges: Multi-destination Ping
draft-yizhou-trill-multi-destination-ping-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | David Mich Bond , Vishwas Manral , Hao Weiguo , Yizhou Li | ||
| Last updated | 2012-05-03 (Latest revision 2011-10-31) | ||
| 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
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
David Mich Bond
Vishwas Manral
Hao Weiguo
Yizhou Li
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)