Hiya, On 09/13/2013 06:36 PM, Dean Willis wrote: >> to hear that the ability for demultiplexing HTTP 2.0 and earlier >> version will be done based on information in the TLS handshake and >> that the TLS group had decided that they prefer a solution that >> reveals the type of application and rejected a proposal for hiding >> it.
> Bad decision. Question the motivations of the people who made it. > Remember, we've been told that the security of our network is being > systematically crippled, by design, from within. I believe that to be > true, in the general (rather than specific) sense. On the other hand, > maybe they just didn't think about the problem from this > perspective. On this point: I think we're actually ok. The TLS WG were asked to provide this feature for HTTP/2.0. One proposal involved establishing confidentiality before nominating the next protocol, but was somewhat hacky in how it fit into TLS1.2. The other (ALPN) was selected as it did the job required for HTTP/2.0 more cleanly. BUT, the WG also decided (formally I guess a little later on) to start work on TLS1.3 with a major goal of that work being to confidentiality protect much more of the TLS handshake as an inherent protocol feature. And that work has started, though I don't think there's an I-D just yet. So the TLS WG decision was in fact to go for more confidentiality. FWIW I think that was the right choice, S. _______________________________________________ perpass mailing list [email protected] https://www.ietf.org/mailman/listinfo/perpass
