MSDP Traceroute
draft-ietf-msdp-traceroute-06
Document | Type |
Expired Internet-Draft
(msdp WG)
Expired & archived
|
|
---|---|---|---|
Author | Randy Roberts | ||
Last updated | 2001-07-25 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
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
In order to diagnose problems with the Peer-RPF-Flooding mechanisms in the Multicast Source Discovery Protocol [2], we introduce a method of tracing the path that an SA message should have taken, along with collecting statistics along that path. This occurs in a way similar to multicast traceroute [3], with each router appending information about this hop and forwarding the message towards the desired RP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)