Multi-Upstream Interfaces IGMP/MLD Proxy
draft-zhang-pim-muiimp-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Hong-Ke Zhang , Thomas C. Schmidt | ||
| Last updated | 2015-11-29 (Latest revision 2015-05-28) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-zhang-pim-muiimp-02.txt
Abstract
In this document, followed by the idea mentioned in [1] and subsequently updated in [2], an IGMP/MLD proxy with multiple upstream interfaces called MUIIMP is proposed and analyzed. The MUIIMP inherits the basic rule of the IGMP/MLD proxy but extends with multiple upstream interfaces. To avoid data redundancy, each upstream interface of an MUIIMP device MUST NOT send or subscribe to the same data simultaneously.
Authors
Hong-Ke Zhang
Thomas C. Schmidt
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)