Multicast Reachability Monitor (MRM)
draft-ietf-mboned-mrm-01
| Document | Type |
Expired Internet-Draft
(mboned WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dr. Kevin C. Almeroth , Liming Wei , Dino Farinacci | ||
| Last updated | 2000-07-14 | ||
| 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
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
Dr. Kevin C. Almeroth
Liming Wei
Dino Farinacci
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)