Re: [TLS] Collisions (Re: Nico's suggestions - Re: Consensus Call:

["Kemp, David P." <[e-mail]>]

This sounds like a general problem unrelated to caching.

If a non-browser app cannot recover from failures, what happens when a
bit error gets through multiple layers of detection and correction, or a
DSL connection dies and restarts?   "Stuff happens" all the time, and
humans know how to hit the "retry" button.  An unattended application
that doesn't know how to recover from unexplained errors is not ready
for prime time.

Dave
 

-----Original Message-----
From: Nicolas Williams

That's what I expect as well, that handshake failure is not transparent
to _all_ applications, and that any retry logic will have to be in the
application.  That makes this protocol a bit problematic -- failures
will be rare, no doubt, so rare that we might not care, but when they
happen the application won't know that the failure is not permanent.
For browsers that may not be a problem (the user will just reload); for
non-browser apps (and scripts running in the browser!) this could be a
problem.