[tsvwg] New Version of draft-ietf-tsvwg-transport-encrypt (12)

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Thu, 27 February 2020 09:08 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 284C83A159D for <tsvwg@ietfa.amsl.com>; Thu, 27 Feb 2020 01:08:58 -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, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id DIjDez57L-9e for <tsvwg@ietfa.amsl.com>; Thu, 27 Feb 2020 01:08:56 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk []) by ietfa.amsl.com (Postfix) with ESMTP id 5CD163A159C for <tsvwg@ietf.org>; Thu, 27 Feb 2020 01:08:56 -0800 (PST)
Received: from GF-MacBook-Pro.local (fgrpf.plus.com []) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id CB60C1B0023F for <tsvwg@ietf.org>; Thu, 27 Feb 2020 09:08:53 +0000 (GMT)
References: <158279435525.6196.11790581771168846041.idtracker@ietfa.amsl.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
X-Forwarded-Message-Id: <158279435525.6196.11790581771168846041.idtracker@ietfa.amsl.com>
Message-ID: <3c7f9e3c-d4f6-b002-5e16-6611d654c8eb@erg.abdn.ac.uk>
Date: Thu, 27 Feb 2020 09:08:53 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <158279435525.6196.11790581771168846041.idtracker@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/YctQqFgK4HZscYwxB63Or9aT7cs>
Subject: [tsvwg] New Version of draft-ietf-tsvwg-transport-encrypt (12)
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, 27 Feb 2020 09:08:58 -0000

The editors have just uploaded a new revision of 
draft-ietf-tsvwg-transport-encrypt following review comments. We are not 
aware of further review comments and now think that this new version is 
now ready to proceed.

Best wishes,

Gorry and Colin

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

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

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, enable transport
evolution, and respect user privacy.