Technical Summary
This series of three documents are about the Licklider Transmission
Protocol developed in the DTNRG.
<draft-irtf-dtnrg-ltp-10.txt>
serves as the main protocol specification of LTP.
<draft-irtf-dtnrg-ltp-extensions-08.txt>
defines two security extensions.
<draft-irtf-dtnrg-ltp-motivation-07.txt>
provides motivation for the protocol.
Working Group Summary
No IETF WG was involved. This protocol was developed in the IRTF.
Document Quality
The document reached consensus in the DTNRG.
The document was reviewed by Russ Housley for the IESG.
Personnel
Kevin Fall <kfall@cs.berkeley.edu> is the document shepherd.
IESG Notes
For draft-irtf-dtnrg-ltp-motivation-07.txt:
This RFC is not a candidate for any level of Internet Standard.
It represents the consensus of the Delay Tolerant Networking (DTN)
Research Group of the Internet Research Task Force (IRTF). See
RFC 3932 for more information.
For draft-irtf-dtnrg-ltp-10.txt:
This RFC is not a candidate for any level of Internet Standard.
It represents the consensus of the Delay Tolerant Networking (DTN)
Research Group of the Internet Research Task Force (IRTF). It may
be considered for standardization by the IETF in the future, but the
IETF disclaims any knowledge of the fitness of this RFC for any
purpose and in particular notes that the decision to publish is not
based on IETF review for such things as security, congestion control,
or inappropriate interaction with deployed protocols. See RFC 3932
for more information.
For draft-irtf-dtnrg-ltp-extensions-08.txt:
This RFC is not a candidate for any level of Internet Standard.
It represents the consensus of the Delay Tolerant Networking (DTN)
Research Group of the Internet Research Task Force (IRTF). It may
be considered for standardization by the IETF in the future, but the
IETF disclaims any knowledge of the fitness of this RFC for any
purpose and in particular notes that the decision to publish is not
based on IETF review for such things as security, congestion control,
or inappropriate interaction with deployed protocols. See RFC 3932
for more information.