Multicast Lessons Learned from Decades of Deployment Experience
draft-mcbride-mboned-lessons-learned-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dino Farinacci , Lenny Giuliano , Mike McBride , Nils Warnke | ||
| Last updated | 2023-02-22 | ||
| Replaced by | draft-ietf-pim-multicast-lessons-learned | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-pim-multicast-lessons-learned | |
| 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 gives a historical perspective about the design and deployment of multicast routing protocols. The document describes the technical challenges discovered from building these protocols. Even though multicast has enjoyed success of deployment in special use-cases, we discuss what were, and are, the obstacles for mass deployment across the Internet. Individuals who are working on new multicast related protocols will benefit by knowing why we aren't using certain older protocols today.
Authors
Dino Farinacci
Lenny Giuliano
Mike McBride
Nils Warnke
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)