[tsvwg] Fwd: New Version Notification for draft-ietf-tsvwg-transport-encrypt-10.txt

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Thu, 09 January 2020 17:07 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 86C86120019 for <tsvwg@ietfa.amsl.com>; Thu, 9 Jan 2020 09:07:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id WBnkH5WPE1a1 for <tsvwg@ietfa.amsl.com>; Thu, 9 Jan 2020 09:07:53 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk []) by ietfa.amsl.com (Postfix) with ESMTP id 1692912001A for <tsvwg@ietf.org>; Thu, 9 Jan 2020 09:07:52 -0800 (PST)
Received: from Gs-MacBook-Pro.local (fgrpf.plus.com []) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 38B521B0022C for <tsvwg@ietf.org>; Thu, 9 Jan 2020 17:07:50 +0000 (GMT)
References: <157858934742.11715.7847933385953766057.idtracker@ietfa.amsl.com>
To: tsvwg@ietf.org
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
X-Forwarded-Message-Id: <157858934742.11715.7847933385953766057.idtracker@ietfa.amsl.com>
Message-ID: <c43830fd-333a-0f9b-f10e-5057b5ad0a2a@erg.abdn.ac.uk>
Date: Thu, 09 Jan 2020 17:07:49 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.3.1
MIME-Version: 1.0
In-Reply-To: <157858934742.11715.7847933385953766057.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------A54D57A440A6D0E257BF43F4"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/FvTD4VmWh5yf8c46vs66yMTSEYI>
Subject: [tsvwg] Fwd: New Version Notification for draft-ietf-tsvwg-transport-encrypt-10.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: Thu, 09 Jan 2020 17:07:55 -0000

We're pleased to upload a version of draft-ietf-tsvwg-transport-encrypt 
after processing the WGLC comments. Thanks again to all who commented, 
both on the list and in private emails during the WGLC process!

Best wishes

Gorry & Colin
(as the document editors)

-------- Forwarded Message --------





A new version of I-D, draft-ietf-tsvwg-transport-encrypt-10.txt
has been successfully submitted by Godred Fairhurst and posted to the
IETF repository.

Name: draft-ietf-tsvwg-transport-encrypt
Revision: 10
Title: Considerations around Transport Header Confidentiality, Network 
Operations, and the Evolution of Internet Transport Protocols
Document date: 2020-01-09
Group: tsvwg
Pages: 47
Status: https://datatracker.ietf.org/doc/draft-ietf-tsvwg-transport-encrypt/
Htmlized: https://tools.ietf.org/html/draft-ietf-tsvwg-transport-encrypt-10

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, while also protecting 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, to account for
network operations, prevent network ossification, and enable
transport evolution, while still respecting user privacy.

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