Re: [TLS] New I-Ds: draft-rescorla-tls-opaque-prf-input-00 and draft-rescorla-tls-suiteb-00

Peter,

*please* figure out some way to put line breaks in your messages.
It makes them very hard to read.

Peter Williams <home_pw@msn.com> wrote:
> What the architecture change in the I-D seems to propose is that
> applications in unix host type environments may require
> API/socket-level access to more than the sessionid.

That's always been true. Recall that TLS doesn't specify how
one checks certificates. That's done at higher layers (E.g.,
RFC 2818). So, the next layer protocol generally needs a 
fair amount of access to properties of the TLS session. 
It's also generally common to provide access to the cipher
suite.

> I do note that the spec is targeting an HTTP extension, worries alot
> about the extension negotiation rules, and of course entails that the
> extension's user-data might be passing over OOB channels beyond the
> control of load balancers and their traditional engineering work in
> trying to tie keepalives, ssl sessions, and cryptobox sessions
> together.

Why do you say "HTTP extension"? This is a pure TLS extension.

-Ekr

_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls