The Multicast Application Ports
draft-karstens-pim-multicast-application-ports-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Nathan Karstens , Stuart Cheshire , Mike McBride | ||
| Last updated | 2024-07-23 | ||
| Replaced by | draft-karstens-multicast-application-port | ||
| 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-karstens-multicast-application-port | |
| 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 discusses the drawbacks of the current practice of assigning a UDP port to each multicast application. Such assignments are redundant because the multicast address already uniquely identifies the data. The document proposes assigning two UDP ports specifically for use with multicast applications and lists requirements for using these ports.
Authors
Nathan Karstens
Stuart Cheshire
Mike McBride
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)