> Begin forwarded message:
> 
> From: internet-dra...@ietf.org
> Subject: New Version Notification for draft-kuehlewind-taps-crypto-sep-00.txt
> Date: July 3, 2017 at 8:08:21 AM PDT
> To: Mirja Kuehlewind <mirja.kuehlew...@tik.ee.ethz.ch>, Christopher Wood 
> <caw...@apple.com>, Tommy Pauly <tpa...@apple.com>, "Christopher A. Wood" 
> <caw...@apple.com>
> 
> 
> A new version of I-D, draft-kuehlewind-taps-crypto-sep-00.txt
> has been successfully submitted by Christopher A. Wood and posted to the
> IETF repository.
> 
> Name:         draft-kuehlewind-taps-crypto-sep
> Revision:     00
> Title:                Separating Crypto Negotiation and Communication
> Document date:        2017-07-03
> Group:                Individual Submission
> Pages:                12
> URL:            
> https://www.ietf.org/internet-drafts/draft-kuehlewind-taps-crypto-sep-00.txt
> Status:         
> https://datatracker.ietf.org/doc/draft-kuehlewind-taps-crypto-sep/
> Htmlized:       
> https://tools.ietf.org/html/draft-kuehlewind-taps-crypto-sep-00
> Htmlized:       
> https://datatracker.ietf.org/doc/html/draft-kuehlewind-taps-crypto-sep-00
> 
> 
> Abstract:
>   Due to the latency involved in connection setup and security
>   handshakes, there is an increasing deployment of cryptographic
>   session resumption mechanisms.  While cryptographic context and
>   endpoint capabilities need to be be known before encrypted
>   application data can be sent, there is otherwise no technical
>   constraint that the crypto handshake must be performed on the same
>   transport connection.  This document recommends a logical separation
>   between the mechanism(s) used to negotiate capabilities and set up
>   encryption context (handshake protocol), the application of
>   encryption and authentication state to data (record protocol), and
>   the associated transport connection(s).
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
> 

_______________________________________________
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

Reply via email to