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

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, 08 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
Precedence: list

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
>

Re: [tsvwg] New Version Notification for draft-ie… Gorry Fairhurst