On 4 May 2017 at 11:31, Salz, Rich <rs...@akamai.com> wrote: > Well, for example, Chrome/boringSSL should arguably know better but are > treating it all as one equivalent stream. > > Is FF/NSS doing the same thing?
Yes. > Why? Because doing anything else makes it a lot harder for the application. I realize that you *want* that, but clearly we disagree about the utility of API hurdles. Given that the application already took extraordinary steps to enable 0-RTT, we don't think that adding artificial hurdles is going to change things. _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls