Yes, it is my plan to make 0-RTT data opt-in only in the Windows TLS stack, with a clear distinction in the API. It is possible, however, that certain middleware components above the TLS stack might choose to blur this distinction (which would be bad design, in my opinion).
Cheers, Andrei -----Original Message----- From: TLS [mailto:tls-boun...@ietf.org] On Behalf Of Salz, Rich Sent: Tuesday, May 23, 2017 11:48 AM To: Markulf Kohlweiss <mark...@microsoft.com>; Kaduk, Ben <bka...@akamai.com>; tls@ietf.org Cc: Antoine Delignat-Lavaud <an...@microsoft.com>; Samin Ishtiaq <samin.isht...@microsoft.com>; Britta Hale <britta.h...@item.ntnu.no> Subject: Re: [TLS] Comments on EndOfEarlyData > Given that 0-RTT and 1-RTT guarantees are very different, it seem important > to distinguish the two streams and model them separately. Cool; is SChannel going to do that? OpenSSL does. _______________________________________________ TLS mailing list TLS@ietf.org https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Ftls&data=02%7C01%7CAndrei.Popov%40microsoft.com%7Cdd3c1a8132a34d29c46908d4a20c5706%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636311621300870812&sdata=MXINz0jr8SWWW9GWOt3Ayrojidu3RdiK%2FkBffEZZ0Eo%3D&reserved=0 _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
