Re: [Secdispatch] [Lake] LAKE next steps

[Yoav Nir <[e-mail]>]

Hi, Rene

> On 27 Aug 2019, at 6:21, Rene Struik <[e-mail]> wrote:
> 
> 
> RS>> (Technical.) It would be prudent for IETF not to put too many eggs in the same basket and, thereby, not have most protocols share the same crypto design philosophy, protocol flow framework, and instantiation. While arguably convenient, this is contrary to algorithm agility requirements (since results in in-tandem vulnerabilities and easily ossified code). 

I disagree with this.  It is not the IETF that is putting many eggs in one basket, but the market. It is the market that is protecting every piece of privacy-sensitive information using TLS: financial transaction, bank statements, credit cards, school transcripts, medical appointments and test results, email in transit to name but a few.

If TLS is compromised, all of that is compromised, and the fact that SSH or IPsec or some new OSCORE thing exist does not help me or anyone else whose personal information is now exposed.  If TLS is compromised we’ll have to fix TLS.  So regardless of what we decide at the IETF, a whole lot of our eggs are already in one basket. It’s a better use of our resources to make sure that basket is protected than to spend them on making a new basket that hardly anyone will use.

Yoav