[tsvwg] Fwd: I-D Action: draft-ietf-tsvwg-transport-encrypt-09.txt

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Sun, 03 November 2019 21:09 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 9678C1200CE for <tsvwg@ietfa.amsl.com>; Sun, 3 Nov 2019 13:09:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 owpPyLzW1Pag for <tsvwg@ietfa.amsl.com>; Sun, 3 Nov 2019 13:09:14 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:42:150::2]) by ietfa.amsl.com (Postfix) with ESMTP id ABCA81200C4 for <tsvwg@ietf.org>; Sun, 3 Nov 2019 13:09:12 -0800 (PST)
Received: from GF-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 80C201B0007A for <tsvwg@ietf.org>; Sun, 3 Nov 2019 21:09:10 +0000 (GMT)
Message-ID: <5DBF41F6.2040409@erg.abdn.ac.uk>
Date: Sun, 03 Nov 2019 21:09:10 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Reply-To: gorry@erg.abdn.ac.uk
Organization: University of Aberdeen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "tsvwg-chairs@ietf.org" <tsvwg@ietf.org>
References: <157281525757.13539.9948918598809575058@ietfa.amsl.com>
In-Reply-To: <157281525757.13539.9948918598809575058@ietfa.amsl.com>
X-Forwarded-Message-Id: <157281525757.13539.9948918598809575058@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/nGwXX9Ru07KBqq35E3xN4-Z4AJs>
Subject: [tsvwg] Fwd: I-D Action: draft-ietf-tsvwg-transport-encrypt-09.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: Sun, 03 Nov 2019 21:09:17 -0000

We've just posted a revision following the WGLC comments...

Gorry

-------- Original Message --------
Subject: 	[tsvwg] I-D Action: draft-ietf-tsvwg-transport-encrypt-09.txt


	

	

	

	

	


A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transport Area Working Group WG of the IETF.

         Title           : Considerations around Transport Header Confidentiality, Network Operations, and the Evolution of Internet Transport Protocols
         Authors         : Godred Fairhurst
                           Colin Perkins
	Filename        : draft-ietf-tsvwg-transport-encrypt-09.txt
	Pages           : 47
	Date            : 2019-11-03

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, 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.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-transport-encrypt/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-tsvwg-transport-encrypt-09
https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-transport-encrypt-09

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-transport-encrypt-09


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/