Skip to main content

Licklider Transmission Protocol - Security Extensions
RFC 5327

Revision differences

Document history

Date By Action
2022-12-08
Cindy Morgan Notification list changed to ipr@ietf.org, draft-irtf-dtnrg-ltp-motivation@ietf.org from ipr@ietf.org., draft-irtf-dtnrg-ltp-motivation@ietf.org
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'The Licklider Transmission Protocol (LTP) is intended to serve as a reliable convergence layer over single-hop …
Received changes through RFC Editor sync (changed abstract to '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.')
2015-10-14
(System) Notify list changed from stephen.farrell@cs.tcd.ie, Scott.Burleigh@jpl.nasa.gov, ipr@ietf.org., mramadas@irg.cs.ohiou.edu, draft-irtf-dtnrg-ltp-motivation@ietf.org to ipr@ietf.org., draft-irtf-dtnrg-ltp-motivation@ietf.org
2008-09-25
Cindy Morgan State Changes to RFC Published from RFC Ed Queue by Cindy Morgan
2008-09-25
Cindy Morgan [Note]: 'RFC 5325
RFC 5326
RFC 5327' added by Cindy Morgan
2008-09-16
(System) RFC published