LTP Fragmentation
draft-templin-dtn-ltpfrag-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Author | Fred Templin | ||
| Last updated | 2020-10-12 (Latest revision 2020-04-10) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Licklider Transmission Protocol (LTP) provides a reliable datagram "covergence layer" for the Delay/Disruption Tolerant Networking (DTN) Bundle Protocol. In common practice, LTP is often configured over UDP/IP sockets and inherits its maximum segment size from the maximum-sized UDP datagram. This document discussses LTP interactions with IP fragmentation and mitigations for managing the amount of IP fragmentation employed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)