IGMP-based Multicast Forwarding ('IGMP Proxying')
draft-fenner-igmp-proxy-03
| Document | Type |
Expired Internet-Draft
(idmr WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Bill Fenner (ˢˣˠ) | ||
| Last updated | 2000-07-12 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| 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
In certain topologies, it is not necessary to run a multicast rout- ing protocol. It is sufficient to learn group membership informa- tion and simply forward based upon that information. This draft describes a mechanism for forwarding based solely upon IGMP member- ship information. This document is a product of an individual. Comments are solicited and should be addressed to the author.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)