Skip to main content

Separating Crypto Negotiation and Communication

Document Type Replaced Internet-Draft (individual)
Author Mirja Kühlewind
Last updated 2017-03-13
Replaced by draft-kuehlewind-taps-crypto-sep
Stream (None)
Intended RFC status (None)
Expired & archived
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-kuehlewind-taps-crypto-sep
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Based on the increasing deployment of session resumption mechanisms where cryptographic context can be resumed to transmit application data with the first packet without delay for connection setup and negotiation, this draft proposes a split to separate connections used to set up encryption context and negotiate capabilities from connections used to transmit application data. 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 has to be performed on the same transport connection. This document discusses requirements on the cryptographic protocol to establish medium- to long-lived association that can be used by different transport protocols that implement different transport services.


Mirja Kühlewind

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)