RFC 1458: Requirements for Multicast Protocols
In plain English — editorial summary, not part of the RFC
This memo discusses some of these unresolved issues, and provides a high-level design for a new multicast transport protocol, group address and membership authority, and modifications to existing routing protocols. This memo provides information for the Internet community. It does not specify an Internet standard.
Document record
- Document ID
- RFC1458
- Published
- May 1993
- Authors
- R. Braudes; S. Zabele
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2190RTP Payload Format for H.263 Video StreamsCurrent
September 1997
- RFC 2542Terminology and Goals for Internet FaxCurrent
March 1999
- RFC 2689Providing Integrated Services over Low-bitrate LinksCurrent
September 1999
- RFC 2721RTFM: Applicability StatementCurrent
October 1999
- RFC 2723SRL: A Language for Describing Traffic Flows and Specifying Actions for Flow GroupsCurrent
October 1999
- RFC 2736Guidelines for Writers of RTP Payload Format SpecificationsUpdated
December 1999
- RFC 2793RTP Payload for Text ConversationObsoleted
May 2000
- RFC 3096Requirements for robust IP/UDP/RTP header compressionCurrent
July 2001
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?