ssh transport seems ready, needs testing

1 files changed, 1 insertions, 20 deletions

diff --git a/doc/design/git-remote-daemon.mdwn b/doc/design/git-remote-daemon.mdwn
index 7ab428ecc..fbc28859b 100644
--- a/doc/design/git-remote-daemon.mdwn
+++ b/doc/design/git-remote-daemon.mdwn
@@ -162,26 +162,7 @@ over stdio to inform when refs on the remote have changed.
 
 No pushing is done for CHANGED, since git handles ssh natively.
 
-TODO:
-
-* Remote system might not be available. Find a smart way to detect it,
-  ideally w/o generating network traffic. One way might be to check
-  if the ssh connection caching control socket exists, for example.
-* Now that ssh connection caching is enabled for git push/pull in sync,
-  there's the possibility that a stale ssh connection may linger when 
-  changing network connections, and so attempts to use it will stall.  
-  (This was already a potential issue with transfers, which already
-  used the caching.)  
-
-  One option is ssh's ServerAliveCountMax, which will make a dead
-  ssh connection disconnect after approx 45 seconds, per ssh manual.
-  It would need to be enabled by setting ServerAliveInterval=15.
-  And this would add network traffic..
-
-  Another option is to disable all cached connections when the network
-  connection changes. This would handle *most* cases. The case
-  not handled is eg, my dialup ppp box getting a new public IP address,
-  which my laptop won't notice. **done**
+TODO: test!
 
 ## telehash