''shared-mtrace'': A Multicast 'traceroute' facility for Shared Trees
draft-ballardie-shared-mtrace-00

Document Type Expired Internet-Draft (individual)
Author Anthony Ballardie 
Last updated 1997-10-27
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized 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-ballardie-shared-mtrace-00.txt

Abstract

''mtrace'' [1] is a very useful tool for diagnosing IP multicast rout- ing problems, such as multicast routing loops and misconfigured mul- ticast routers, associated with source-rooted RPF-based distribution trees. For ''mtrace'' to be useful in a shared tree environment (e.g. PIM [2], CBT [3], GUM [4]) its behaviour must be modified. This draft speci- fies that behaviour, which is sufficiently general to be applicable to all shared tree types and operating modes. A new ''wildcard'' mode of behaviour is also described, which allows a trace of a complete shared tree. Authentication is recommended in this mode because of its potential as a vehicle for denial of service attacks. It is intended that this draft become a document of the Mbone Deploy- ment (mboned) working group of the IETF. Therefore, comments are solicited and should be sent to mboned's mailing list <mboned@network- services.uoregon.edu> and/or the author.

Authors

Anthony Ballardie (ABallardie@acm.org)

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