RFC 3451: Layered Coding Transport (LCT) Building Block
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5651.
Current version: RFC 5651 — Layered Coding Transport (LCT) Building Block
In plain English — editorial summary, not part of the RFC
Layered Coding Transport (LCT) provides transport level support for reliable content delivery and stream delivery protocols. LCT is specifically designed to support protocols using IP multicast, but also provides support to protocols that use unicast. LCT is compatible with congestion control that provides multiple rate delivery to receivers and is also compatible with coding techniques that provide reliable delivery of content. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC3451
- Published
- December 2002
- Authors
- M. Luby; J. Gemmell; L. Vicisano; L. Rizzo; M. Handley; J. Crowcroft
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 29
- Also known as
- —
- Obsoleted by:
- RFC 5651
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 3452Forward Error Correction (FEC) Building BlockObsoleted
December 2002
- RFC 3695Compact Forward Error Correction (FEC) SchemesObsoleted
February 2004
- RFC 5445Basic Forward Error Correction (FEC) SchemesCurrent
March 2009
- RFC 5775Asynchronous Layered Coding (ALC) Protocol InstantiationCurrent
April 2010
- RFC 3450Asynchronous Layered Coding (ALC) Protocol InstantiationObsoleted
December 2002
- RFC 3307Allocation Guidelines for IPv6 Multicast AddressesUpdated
September 2002
- RFC 3738Wave and Equation Based Rate Control (WEBRC) Building BlockCurrent
April 2004
- RFC 3376Internet Group Management Protocol, Version 3Obsoleted
October 2002
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?