Licklider Transmission Protocol - Security Extensions
RFC 5327, “Licklider Transmission Protocol - Security Extensions”, is an Experimental document published in September 2008 by S. Farrell, M. Ramadas, S. Burleigh. The canonical text is published by the RFC Editor.
Abstract
The Licklider Transmission Protocol (LTP) is intended to serve as a reliable convergence layer over single-hop deep-space radio frequency (RF) links. LTP does Automatic Repeat reQuest (ARQ) of data transmissions by soliciting selective-acknowledgment reception reports. It is stateful and has no negotiation or handshakes. This document describes security extensions to LTP, and is part of a series of related documents describing LTP.
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.
What “Experimental” means
Describes a specification that is part of a research or development effort, published so the community can gain experience with it.
The canonical text of RFC 5327 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5326 Licklider Transmission Protocol - Specification
- RFC 5328 A Uniform Resource Name Namespace for the Digital Video Broadcasting Project
- RFC 5325 Licklider Transmission Protocol - Motivation
- RFC 5329 Traffic Engineering Extensions to OSPF Version 3
- RFC 5324 MIB for Fibre-Channel Security Protocols
- RFC 5330 A Link-Type sub-TLV to Convey the Number of Traffic Engineering Label Switched Paths Signalled with Zero Reserved Bandwidth across a Link
- RFC 5323 Web Distributed Authoring and Versioning SEARCH
- RFC 5331 MPLS Upstream Label Assignment and Context-Specific Label Space