RFC 2887: The Reliable Multicast Design Space for Bulk Data Transfer
In plain English — editorial summary, not part of the RFC
This document provides an overview of the design space and the ways in which application constraints affect possible solutions. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2887
- Published
- August 2000
- Authors
- M. Handley; S. Floyd; B. Whetten; R. Kermode; L. Vicisano; M. Luby
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3450Asynchronous Layered Coding (ALC) Protocol InstantiationObsoleted
December 2002
- RFC 3126Electronic Signature Formats for long term electronic signaturesObsoleted
September 2001
- RFC 2326Real Time Streaming Protocol (RTSP)Obsoleted
April 1998
- RFC 5126CMS Advanced Electronic Signatures (CAdES)Current
March 2008
- RFC 2923TCP Problems with Path MTU DiscoveryCurrent
September 2000
- RFC 2771An Abstract API for Multicast Address AllocationCurrent
February 2000
- RFC 2760Ongoing TCP Research Related to SatellitesCurrent
February 2000
- RFC 2722Traffic Flow Measurement: ArchitectureCurrent
October 1999
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?