IP multicasting and broadcasting extension for PPPoE Protocol
draft-song-pppoe-ext-multicast-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | You Song , Reinaldo Penno | ||
| Last updated | 2001-08-22 | ||
| 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
In the year following the publication of the PPPoE protocol much operational experience and customer feedback was gathered. One problem that access providers usually mention is that when PPPoE Server needs to send IP multicast packets or broadcast packets to PPPoE Clients in a same Ethernet, it has to send these packets to each PPPoE Client over each PPPoE link. Because the PPPoE Clients are all in a Ethernet, this multiplication of packets affects performance and wastes the net's resource.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)