Hi Sean, we at ARM would find it somewhat unfortunate to remove the client authentication feature from the 0-RTT exchange since this is one of the features that could speed up the exchange quite significantly and would make a big difference compared to TLS 1.2.
For the IoT use cases we need client authentication; I understand that the situation may be somewhat different in the Web space. So, I am not happy with the proposed change! Ciao Hannes On 03/29/2016 02:59 PM, Sean Turner wrote: > All, > > To make sure we’ve got a clear way forward coming out of our BA > sessions, we need to make sure there’s consensus on a couple of > outstanding issues. So... > > It seems that there is a clear consensus not to support 0-RTT client > authentication in TLS 1.3 at this time. If you think 0-RTT client > authentication needs to be supported please indicate so now and > provide your rationale. > > J&S _______________________________________________ TLS mailing list > TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
