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

From: Gorry Fairhurst <[email-masked]>
Date: Mon, 8 Mar 2021 18:25:41 +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, [email-masked] 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
>