Extension of the MLD proxy functionality to support multiple upstream interfaces
draft-contreras-pim-multiple-upstreams-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Luis M. Contreras , Carlos J. Bernardos , Juan-Carlos Zúñiga | ||
| Last updated | 2014-01-04 (Latest revision 2013-07-03) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document presents different scenarios of applicability for an MLD proxy running more than one upstream interface. Since those scenarios impose different requirements on the MLD proxy with multiple upstream interfaces, it is important to ensure that the proxy functionality addresses all of them for compatibility. The purpose of this document is to define the requirements in an MLD proxy with multiple interfaces covering a variety of applicability scenarios, and to specify the proxy functionality to satisfy all of them.
Authors
Luis M. Contreras
Carlos J. Bernardos
Juan-Carlos Zúñiga
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)