Skip to main content

Justification for and use of the Multicast Routing Monitor (MRM) Protocol

Document Type Expired Internet-Draft (mboned WG)
Expired & archived
Authors Liming Wei , Dr. Kevin C. Almeroth
Last updated 1999-03-03
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
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:


This document motivates the need for the Multicast Routing Monitor (MRM) [MRM] protocol by describing the niche that exists for a router-based multicast management protocol. Using the 'sufficient and necessary' argument, we suggest that existing protocols and techniques lack important management functionality. This document briefly describes the methodology used by MRM, justifies the existence of MRM, and describes some of the scenarios in which MRM will be of value.


Liming Wei
Dr. Kevin C. Almeroth

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