> 1-RTT should be ok on server with boringssl, alpn http/1.1 and AEAD ciphers. > For client i think it lack an option to activate FalseStart.
Could we fix this with a future option? > > For 0-RTT is not clear for me, i only know it need TLSv1.3 with psk mechanism. > It also introduce a security hole as said Cloudflare int this blog For backend ssl client, should be OK with 0 rtt. In some scenario, having long roundtrip backend ssl server, 0 rtt should help a lot. ref1: https://blog.cloudflare.com/introducing-0-rtt/ ref2: https://github.com/nghttp2/nghttp2/pull/846 > > Manu > >> Le 26 mars 2017 à 17:54, Igor Pav <[email protected]> a écrit : >> >> Hi, Emmanuel. Any plan to add tls 1.3 zero rtt support for both server >> and client side? >> >> On Sat, Mar 25, 2017 at 2:13 AM, Emmanuel Hocdet <[email protected]> wrote: >>> >>> Hi Emeric, >>> patches serie updated. The new one is 0004. >>> It should match what you are requesting and what I observed in the openssl >>> code. >>> >>> ++ >>> Manu >>> >>> >> >
