Re: [tsvwg] New Version Notification for draft-ietf-tsvwg-transport-encrypt-20.txt

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Mon, 08 March 2021 18:25 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8C483A1445 for <tsvwg@ietfa.amsl.com>; Mon, 8 Mar 2021 10:25:45 -0800 (PST)
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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 q7Z8ESLeGiWI for <tsvwg@ietfa.amsl.com>; Mon, 8 Mar 2021 10:25:44 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id 34AF83A143C for <tsvwg@ietf.org>; Mon, 8 Mar 2021 10:25:44 -0800 (PST)
Received: from GF-MBP-2.lan (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 5D7D81B0010D for <tsvwg@ietf.org>; Mon, 8 Mar 2021 18:25:42 +0000 (GMT)
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
References: <161522781401.1888.7824541642226747419@ietfa.amsl.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <86f2128d-4b43-a7b3-cae4-76243141eb5b@erg.abdn.ac.uk>
Date: Mon, 8 Mar 2021 18:25:41 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <161522781401.1888.7824541642226747419@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/o0_K0eIYqGkPjj4cSgpu6BB-RiY>
Subject: Re: [tsvwg] New Version Notification for draft-ietf-tsvwg-transport-encrypt-20.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2021 18:25:46 -0000

This is a revision to address IETFLC review comments, and allow the 
review process to continue. Thanks to all who provided feedback, and 
help in preparing this revision.

Gorry & Colin

On 08/03/2021 18:23, internet-drafts@ietf.org wrote:
> A new version of I-D, draft-ietf-tsvwg-transport-encrypt-20.txt
> has been successfully submitted by Godred Fairhurst and posted to the
> IETF repository.
>
> Name:		draft-ietf-tsvwg-transport-encrypt
> Revision:	20
> Title:		Considerations around Transport Header Confidentiality, Network Operations, and the Evolution of Internet Transport Protocols
> Document date:	2021-03-08
> Group:		tsvwg
> Pages:		47
> URL:            https://www.ietf.org/archive/id/draft-ietf-tsvwg-transport-encrypt-20.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-tsvwg-transport-encrypt/
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-transport-encrypt
> Htmlized:       https://tools.ietf.org/html/draft-ietf-tsvwg-transport-encrypt-20
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-transport-encrypt-20
>
> Abstract:
>     To protect user data and privacy, Internet transport protocols have
>     supported payload encryption and authentication for some time.  Such
>     encryption and authentication is now also starting to be applied to
>     the transport protocol headers.  This helps avoid transport protocol
>     ossification by middleboxes, mitigate attacks against the transport
>     protocol, and protect metadata about the communication.  Current
>     operational practice in some networks inspect transport header
>     information within the network, but this is no longer possible when
>     those transport headers are encrypted.
>
>     This document discusses the possible impact when network traffic uses
>     a protocol with an encrypted transport header.  It suggests issues to
>     consider when designing new transport protocols or features.
>
>                                                                                    
>
>
> 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
>