Multicast Reachability Monitor (MRM)
draft-ietf-mboned-mrm-01
| Document | Type | Expired Internet-Draft (mboned WG) | |
|---|---|---|---|
| Authors | Kevin Almeroth , Liming Wei , Dino Farinacci | ||
| Last updated | 2000-07-14 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
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-01.txt
Abstract
MRM facilitates automated fault detection and fault isolation in a large multicast routing infrastructure. It is designed to alarm a network administrator of multicast reachability problems in close to real-time. There are two basic types of components in MRM, MRM manager and MRM testers. This document specifies the protocol with which the two MRM components communicate, the types of operations the testers perform, and information an MRM manager can obtain.
Authors
Kevin Almeroth
(almeroth@cs.ucsb.edu)
Liming Wei
(lwei@redback.com)
Dino Farinacci
(dino@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)