Multicast in the Data Center Overview
draft-ietf-mboned-dc-deploy-09
| Document | Type |
Expired Internet-Draft
(mboned WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mike McBride , Olufemi Komolafe | ||
| Last updated | 2020-08-07 (Latest revision 2020-02-04) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| 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
The volume and importance of one-to-many traffic patterns in data centers is likely to increase significantly in the future. Reasons for this increase are discussed and then attention is paid to the manner in which this traffic pattern may be judiciously handled in data centers. The intuitive solution of deploying conventional IP multicast within data centers is explored and evaluated. Thereafter, a number of emerging innovative approaches are described before a number of recommendations are made.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)