RFC 3450: Asynchronous Layered Coding (ALC) Protocol Instantiation
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5775.
Current version: RFC 5775 — Asynchronous Layered Coding (ALC) Protocol Instantiation
In plain English — editorial summary, not part of the RFC
This document describes the Asynchronous Layered Coding (ALC) protocol, a massively scalable reliable content delivery protocol. Asynchronous Layered Coding combines the Layered Coding Transport (LCT) building block, a multiple rate congestion control building block and the Forward Error Correction (FEC) building block to provide congestion controlled reliable asynchronous delivery of content to an unlimited number of concurrent receivers from a single sender. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC3450
- Published
- December 2002
- Authors
- M. Luby; J. Gemmell; L. Vicisano; L. Rizzo; J. Crowcroft
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 34
- Also known as
- —
- Obsoleted by:
- RFC 5775
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3451Layered Coding Transport (LCT) Building BlockObsoleted
December 2002
- RFC 3452Forward Error Correction (FEC) Building BlockObsoleted
December 2002
- RFC 3695Compact Forward Error Correction (FEC) SchemesObsoleted
February 2004
- RFC 2887The Reliable Multicast Design Space for Bulk Data TransferCurrent
August 2000
- RFC 5445Basic Forward Error Correction (FEC) SchemesCurrent
March 2009
- RFC 3155End-to-end Performance Implications of Links with ErrorsCurrent
August 2001
- RFC 3135Performance Enhancing Proxies Intended to Mitigate Link-Related DegradationsCurrent
June 2001
- RFC 2923TCP Problems with Path MTU DiscoveryCurrent
September 2000
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?