Zeroconf Multicast Address Allocation Problem Statement and Requirements
draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-00
| Document | Type |
Expired Internet-Draft
(pim WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Nathan Karstens , Dino Farinacci , Mike McBride | ||
| Last updated | 2024-03-18 (Latest revision 2023-09-15) | ||
| Replaces | draft-karstens-pim-zeroconf-mcast-addr-alloc-ps | ||
| 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
This document describes a network that requires unique multicast addresses to distribute data. Various challenges are discussed, such as the use of multicast snooping to ensure efficient use of bandwidth, limitations of switch hardware, problems associated with address collisions, and the need to avoid user configuration. After all limitations were considered it was determined that multicast addresses need to be dynamically-assigned by a decentralized, zero- configuration protocol. Requirements and recommendations for suitable protocols are listed and specific considerations for assigning IPv4 and IPv6 addresses are reviewed. The document closes with several solutions that are precluded from consideration.
Authors
Nathan Karstens
Dino Farinacci
Mike McBride
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)