Re: New Version Notification for draft-fairhurst-tsvwg-transport-encrypt-04.txt

"Gorry (erg)" <gorry@erg.abdn.ac.uk> Fri, 29 September 2017 11:26 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D8E41344F1 for <quic@ietfa.amsl.com>; Fri, 29 Sep 2017 04:26:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xH5DHAQhCMJm for <quic@ietfa.amsl.com>; Fri, 29 Sep 2017 04:26:16 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:241:204::f0f0]) by ietfa.amsl.com (Postfix) with ESMTP id 2781F1344E8 for <quic@ietf.org>; Fri, 29 Sep 2017 04:26:16 -0700 (PDT)
Received: from [10.236.169.111] (unknown [148.252.129.147]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 0377B1B00056 for <quic@ietf.org>; Fri, 29 Sep 2017 12:26:15 +0100 (BST)
From: "Gorry (erg)" <gorry@erg.abdn.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Date: Fri, 29 Sep 2017 12:23:58 +0100
Subject: Re: New Version Notification for draft-fairhurst-tsvwg-transport-encrypt-04.txt
Message-Id: <AB9D3CCF-ADF6-479D-BC3D-67A950BB52D0@erg.abdn.ac.uk>
References: <150668328447.14229.13098365888682582505.idtracker@ietfa.amsl.com>
In-Reply-To: <150668328447.14229.13098365888682582505.idtracker@ietfa.amsl.com>
To: quic@ietf.org
X-Mailer: iPhone Mail (14G60)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/maRXJ1xeJlWvQxjPfrJEau6W1-A>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Sep 2017 11:26:20 -0000

I enclose a link to the new transport header encryption ID. We hope this provides a useful input to the Quic-dt looking at tradeoffs.

Many thanks to all who provided feedback on the last rev. I am particularly pleased Colin Perkins has now joined me as a co-author. The restructuring and updates should make this more accessible to readers -- all comments are welcome via QUIC or TSVWG (on general transport issues)

Best wishes Colin and Gorry

> On 29 Sep 2017, at 12:08, internet-drafts@ietf.org wrote:
> 
> 
> A new version of I-D, draft-fairhurst-tsvwg-transport-encrypt-04.txt
> has been successfully submitted by Godred Fairhurst and posted to the
> IETF repository.
> 
> Name:        draft-fairhurst-tsvwg-transport-encrypt
> Revision:    04
> Title:        The Impact of Transport Header Encryption on Operation and Evolution of the Internet
> Document date:    2017-09-27
> Group:        Individual Submission
> Pages:        27
> URL:            https://www.ietf.org/internet-drafts/draft-fairhurst-tsvwg-transport-encrypt-04.txt
> Status:         https://datatracker.ietf.org/doc/draft-fairhurst-tsvwg-transport-encrypt/
> Htmlized:       https://tools.ietf.org/html/draft-fairhurst-tsvwg-transport-encrypt-04
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-fairhurst-tsvwg-transport-encrypt-04
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-fairhurst-tsvwg-transport-encrypt-04
> 
> Abstract:
>   This document describes implications of applying end-to-end
>   encryption at the transport layer.  It identifies some in-network
>   uses of transport layer header information that can be used with a
>   transport header integrity check.  It reviews the implication of
>   developing encrypted end-to-end transport protocols and examines the
>   implication of developing and deploying encrypted end-to-end
>   transport protocols.  Since transport measurement and analysis of the
>   impact of network characteristics have been important to the design
>   of current transport protocols, it also considers some anticipated
>   implications on transport and application evolution.
> 
> 
> 
> 
> 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