In omy investigation towards kerberos constraint delegation I found a funny packet that needed further investigation.. it's a protocol called LTP-DEEPSPACE..
in my trace I saw a connection from one of the clients
192.168.10.2 192.168.10.1 TCP ltp-deepspace > kerberos [SYN] Seq=0 Win=65535 Len=0 MSS=1460
followed by the ACK
192.168.10.1 192.168.10.2 TCP kerberos > ltp-deepspace [SYN, ACK] Seq=0 Ack=1 Win=16384 Len=0 MSS=1460
Now why would a protocol connect to my Kerberos port.. Google offcourse gave the answer: ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-irtf-dtnrg-ltp-10.txt
"
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.
LTP does Automatic Repeat reQuest (ARQ) of data transmissions by
soliciting selective-acknowledgment reception reports. It is
stateful, and has no negotiation or handshakes.
In an Interplanetary Internet setting deploying the Bundle protocol
that is being developed by the Delay Tolerant Networking Research
Group, LTP is intended to serve as a reliable "convergence layer"
protocol operating in pairwise fashion between adjacent
Interplanetary Internet nodes that are in direct RF communication.
In that operational scenario, and potentially in some other
deployments of the Bundle Protocol, LTP runs directly over a data-
link layer protocol; when this is the case, forward error correction
coding and/or checksum mechanisms in the underlying data-link layer
protocol must assure the integrity of the data passed between the
communicating entities.
Since no mechanisms for flow control or congestion control are
included in the design of LTP, this protocol is not intended or
appropriate for ubiquitous deployment in the global Internet.
When LTP is run over UDP, it must only be used for software
development or in private local area networks. When LTP is not run
over UDP, it must be run directly over a protocol, (nominally a link-
layer protocol), that meets the requirements specified in section 5.
"
Nice to know mankind is looking forward in expanding the boundaries of TCP/IP into space