Cool, even TLS 1.3 0 RTT feature requires no changes?

On Fri, Dec 16, 2016 at 3:03 AM, Lukas Tribus <[email protected]> wrote:
> Hi Igor,
>
>
> Am 14.12.2016 um 20:47 schrieb Igor Pav:
>>
>> Hi Lukas, in fact, openssl already gets early TLS 1.3 adoption in dev,
>> will release in 1.1.1, and BoringSSL supports TLSv1.3 already.
>
>
> That's nice, and in fact since 1.1.1 will be API compatible with 1.1.0 [1]
> *and* support
> TLS 1.3 (or whatever we end up calling it [2]), this shouldn't require any
> changes in
> haproxy at all.
>
>
>
> [1] https://www.openssl.org/blog/blog/2016/10/24/f2f-roadmap/
> [2] https://www.ietf.org/mail-archive/web/tls/current/msg21888.html

Reply via email to