Re: [TLS] Updated draft

I find the reference to
      immediately previous handshake
in s.3 unclear.

Thinking of session resumption, as identified in RFC5246, there are three cases
namely
  "The session identifier MAY be from an earlier connection,
   this connection, or from another currently active connection."

Which connection should the immediately previous handshake come from
given that there may be one session and multiple connections
(each of which may be independently re-negotiating) in each of these three
cases?

My grasp of TLS session and TLS connection may not be as crystal clear
as it might be; I see session as defined by a common session
identifier but connection being the construct whose protocol is changed by
this I-D.

Tom Petch

----- Original Message -----
From: "Eric Rescorla" <ekr@networkresonance.com>
To: <tls@ietf.org>
Sent: Wednesday, December 16, 2009 10:32 PM
Subject: [TLS] Updated draft

> I've just submitted a new draft that is intended to enact most of
> Pasi's message as well as the noncontroversial editorial comments
> people have raised. Here is what I know still needs work:
>
> - The final resolution to what's sent in the legacy renegotiation
>   case (see Pasi's message and the text I sent earlier).
> - New text for the identity section in Security considerations.
>   (Pending closure on the list).
> - Make a pass through for clarity for implementors.
>   (Also, I have some text here that Pasi contributed that I
>   need to work in).
>
> If you think you made a comment which is noncontroversial
> that didn't make it in and/or I screwed up incorporating your
> comment, please let me know and I'll try to fix.
>
> For some reason, the submission tool is forcing manual
> submission. In the interim you can find it at:
> https://svn.resiprocate.org/rep/ietf-drafts/ekr/draft-ietf-tls-renegotiate.txt
>
> Thanks,
> -Ekr
>
>
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls