Hi Yaron and Leif,
I also need a consensus about adding standby ciphers into TLS-BCP. And I understood that UTA WG focuses on getting a first version of the BCP out as soon as possible. In first, I want to point out it seems that very little interest in the idea of standby cipher that you pointed out is not fact. I heard from David that there are some interests in idea of standby ciphers. My concern is that when vulnerability related to the primitive is found it takes a lot of time to migrate from insecure primitive to secure one. In fact, it is seemed to me that it takes a lot of time to migrate to TLS1.2. (My proposal that TLS-BCP recommends standby ciphers is one of the solutions for a delay of migration.) What do you think about my concern? For example, shall we consider the procedure for review of algorithms in TLS-BCP and update of TLS-BCP in order to deal with the following events? 1. Operations of new algorithms in TLS implementations are so increasing that we cannot ignore it. 2. Vulnerability of TLS is found. Best, Kohei KASAMATSU (2014/08/11 18:33), Leif Johansson wrote: > On 2014-08-11 10:44, Yaron Sheffer wrote: >> Hi Kohei, >> >> Personally I support the idea of alternative (or "standby") ciphers, see >> http://tools.ietf.org/html/draft-mcgrew-standby-cipher-00. However there >> was very little interest in this idea when we brought it up at CFRG. >> >> IMHO for inclusion in the BCP there should be wide consensus about both >> the need for standby ciphers (and there is none, as far as I can tell) >> as well as the individual algorithms. >> > > I think that is a fair assessment. Our focus now should be on getting a > first version of the BCP out as soon as possible. > > Cheers Leif > > _______________________________________________ > Uta mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/uta > _______________________________________________ Uta mailing list [email protected] https://www.ietf.org/mailman/listinfo/uta
