RFC 5326: Licklider Transmission Protocol - Specification
In plain English — editorial summary, not part of the RFC
This document describes the Licklider Transmission Protocol (LTP), designed to provide retransmission-based reliability over links characterized by extremely long message round-trip times (RTTs) and/or frequent interruptions in connectivity. Since communication across interplanetary space is the most prominent example of this sort of environment, LTP is principally aimed at supporting "long-haul" reliable transmission in interplanetary space, but it has applications in other environments as well. This document is a product of the Delay Tolerant Networking Research Group and has been reviewed by that group. No objections to its publication as an RFC were raised. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC5326
- Published
- September 2008
- Authors
- M. Ramadas; S. Burleigh; S. Farrell
- Status
- EXPERIMENTAL
- Stream
- IRTF
- Area
- —
- Pages
- 54
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5325Licklider Transmission Protocol - MotivationCurrent
September 2008
- RFC 5327Licklider Transmission Protocol - Security ExtensionsCurrent
September 2008
- RFC 7323TCP Extensions for High PerformanceCurrent
September 2014
- RFC 9330Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: ArchitectureCurrent
January 2023
- RFC 9331The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)Current
January 2023
- RFC 9332Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S)Current
January 2023
- RFC 9956A Non-Queue-Building Per-Hop Behavior (NQB PHB) for Differentiated ServicesCurrent
May 2026
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?