Justification for and use of the Multicast Routing Monitor (MRM) Protocol
draft-ietf-mboned-mrm-use-00
| Document | Type | Expired Internet-Draft (mboned WG) | |
|---|---|---|---|
| Last updated | 1999-03-03 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-mboned-mrm-use-00.txt
Abstract
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.
Authors
Liming Wei
(lwei@redback.com)
Kevin Almeroth
(almeroth@cs.ucsb.edu)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)