Hmm ... I might suggest consulting the TLS 1.3 draft's version history: https://tools.ietf.org/html/draft-ietf-tls-tls13-11#section-1.2
There are significant changes to the initial handshake from TLS 1.2, and that initial handshake is the primary focus of the tcpinc profile of TLS. Thanks, --David > -----Original Message----- > From: Tcpinc [mailto:[email protected]] On Behalf Of Joe Touch > Sent: Monday, February 29, 2016 7:31 PM > To: Derek Fawcus; tcpinc ([email protected]) > Cc: [email protected] > Subject: Re: [tcpinc] TCPINC - security protocols > > > > > > Black, David wrote: > > While the TLS WG is hard at work on TLS 1.3, that protocol is not finished > > yet; the chairs believe that completion of that base protocol is a necessary > > prerequisite for a TCPINC profile of TLS 1.3 (e.g., as a TCPINC profile will > > have to normatively reference the TLS 1.3 specification). In addition, > > from a broader IETF perspective, completion of TLS 1.3 really does need > > to be the first priority for TLS experts such as Eric Rescorla. > > Sorry if this has been asked (I didn't see it), but is this merely a > person-cycles issue or is there some deeper reason for not designing it > agnostic to 1.2 vs. 1.3 and requiring 1.2 support until 1.3 is ready? > > Joe > > _______________________________________________ > Tcpinc mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/tcpinc _______________________________________________ Tcpinc mailing list [email protected] https://www.ietf.org/mailman/listinfo/tcpinc
