I-D Action: draft-kuehlewind-taps-crypto-sep-00.txt
internet-drafts@ietf.org Mon, 03 July 2017 15:08 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: i-d-announce@ietf.org
Delivered-To: i-d-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 03D1C131660 for <i-d-announce@ietf.org>; Mon, 3 Jul 2017 08:08:21 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-kuehlewind-taps-crypto-sep-00.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149909450097.22739.8729051268236569391@ietfa.amsl.com>
Date: Mon, 03 Jul 2017 08:08:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/tPk2prolvaybhbC-1kMJk5DQl68>
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i-d-announce/>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jul 2017 15:08:21 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Separating Crypto Negotiation and Communication Authors : Mirja Kuehlewind Tommy Pauly Christopher A. Wood Filename : draft-kuehlewind-taps-crypto-sep-00.txt Pages : 12 Date : 2017-07-03 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). The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-kuehlewind-taps-crypto-sep/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-kuehlewind-taps-crypto-sep-00 https://datatracker.ietf.org/doc/html/draft-kuehlewind-taps-crypto-sep-00 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/
- I-D Action: draft-kuehlewind-taps-crypto-sep-00.t… internet-drafts