RFC 1301: Multicast Transport Protocol
In plain English — editorial summary, not part of the RFC
This memo describes a protocol for reliable transport that utilizes the multicast capability of applicable lower layer networking architectures. The transport definition permits an arbitrary number of transport providers to perform realtime collaborations without requiring networking clients (aka, applications) to possess detailed knowledge of the population or geographical dispersion of the participating members. It is not network architectural specific, but does implicitly require some form of multicasting (or broadcasting) at the data link level, as well as some means of communicating that capability up through the layers to the transport. This memo provides information for the Internet community. It does not specify an Internet standard.
Document record
- Document ID
- RFC1301
- Published
- February 1992
- Authors
- S. Armstrong; A. Freier; K. Marzullo
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 38
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4563The Key ID Information Type for the General Extension Payload in Multimedia Internet KEYing (MIKEY)Updated
June 2006
- RFC 5775Asynchronous Layered Coding (ALC) Protocol InstantiationCurrent
April 2010
- RFC 9119Multicast Considerations over IEEE 802 Wireless MediaCurrent
October 2021
- RFC 9223Real-Time Transport Object Delivery over Unidirectional Transport (ROUTE)Current
April 2022
- RFC 1112Host extensions for IP multicastingUpdated
August 1989
- RFC 1585MOSPF: Analysis and ExperienceCurrent
March 1994
- RFC 988Host extensions for IP multicastingObsoleted
July 1986
- RFC 786Mail Transfer Protocol: ISI TOPS20 MTP-NIMAIL interfaceCurrent
July 1981
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?