We need a replacement for TCP in the datacenter [pdf]
FWIU, barring FTL; superluminal communication breakthroughs and controls, Deep Space Networking needs a new TCP, as well:<p>From <a href="https://github.com/torvalds/linux/blob/master/net/ipv4/tcp_timer.c" rel="nofollow">https://github.com/torvalds/linux/blob/master/net/ipv4/tcp_t...</a> :<p><pre><code>  void tcp_retransmit_timer(struct sock *sk) {
  
 /* Increase the timeout each time we retransmit.  Note that
  * we do not increase the rtt estimate.  rto is initialized
  * from rtt, but increases here.  Jacobson (SIGCOMM 88) suggests
  * that doubling rto each time is the least we can get away with.
  * In KA9Q, Karn uses this for the first few times, and then
  * goes to quadratic.  netBSD doubles, but only goes up to *64,
  * and clamps at 1 to 64 sec afterwards.  Note that 120 sec is
  * defined in the protocol as the maximum possible RTT.  I guess
  * we'll have to use something other than TCP to talk to the
  * University of Mars.
  *
  * PAWS allows us longer timeouts and large windows, so once
  * implemented ftp to mars will work nicely. We will have to fix
  * the 120 second clamps though!
  */
</code></pre>
/? "tp-planet" "tcp-planet"
<a href="https://www.google.com/search?q=%22tp-planet%22+%22tcp-planet%22+%22SCPS-TP%22" rel="nofollow">https://www.google.com/search?q=%22tp-planet%22+%22tcp-plane...</a>  <a href="https://scholar.google.com/scholar?q=%22tp-planet%22+%22tcp-planet%22+%22SCPS-TP%22" rel="nofollow">https://scholar.google.com/scholar?q=%22tp-planet%22+%22tcp-...</a>