Re: [tsvwg] RFC 9065 on Considerations around Transport Header Confidentiality, Network Operations, and the Evolution of Internet Transport Protocols
Colin Perkins <csp@csperkins.org> Tue, 20 July 2021 21:34 UTC
Return-Path: <csp@csperkins.org>
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 01D363A3338 for <tsvwg@ietfa.amsl.com>; Tue, 20 Jul 2021 14:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=csperkins.org
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 4sx4fifxmi-V for <tsvwg@ietfa.amsl.com>; Tue, 20 Jul 2021 14:34:48 -0700 (PDT)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 507A03A3337 for <tsvwg@ietf.org>; Tue, 20 Jul 2021 14:34:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=csperkins.org; s=mythic-beasts-k1; h=To:Date:From:Subject; bh=6bqsMyePrFTN4hz65c4vtN7/cnPt7chmMaRfEtNIWz4=; b=eVQXjd+gvjQ1RVgjUxCXZfat2u pNDrh851NH67VHjlgbVnG/mJU3Y4Bfw5ZD2TWnnS9GHoUjWC7ZhNnqyIpCiE6YJBpxcTgmP3iPlMt UNrjQMqiQ4Spu0gFOraYVyLf6WDW9KnYLKydFP/waS2OhtXcvOnHlPszaHOL+jFzJ3v1r69I+2azY oAEICWLPrF9C6IScmARRchcH9DgbAS+xFOeqMIQT7ZY+ZhhZbemxVokUe8FwFMFeBBDAAJuzCVPbP w/RY6X7mgvxHiVYJ4LR4V0NB6jbEofCreu4qUykrsYFpHUV7i701oJU7rMRcDswp+wVhDecVMr42X XTy/ertw==;
Received: from [81.187.2.149] (port=48211 helo=[192.168.0.83]) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from <csp@csperkins.org>) id 1m5xNy-0005dz-Pz; Tue, 20 Jul 2021 22:34:47 +0100
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <MN2PR19MB4045BC62EF5FC859EF18A3EB83129@MN2PR19MB4045.namprd19.prod.outlook.com>
Date: Tue, 20 Jul 2021 22:34:40 +0100
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E2F8EDE-6A0D-45AA-9B6D-8C4681010153@csperkins.org>
References: <20210715064356.BF655F40709@rfc-editor.org> <MN2PR19MB4045BC62EF5FC859EF18A3EB83129@MN2PR19MB4045.namprd19.prod.outlook.com>
To: "Black, David" <David.Black@dell.com>
X-Mailer: Apple Mail (2.3445.104.21)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/MCCGitKx4UR2iNdwwxtjDByrkpo>
Subject: Re: [tsvwg] RFC 9065 on Considerations around Transport Header Confidentiality, Network Operations, and the Evolution of Internet Transport Protocols
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: Tue, 20 Jul 2021 21:34:54 -0000
Thanks, David. Hopefully the resulting document is useful to some. Colin > On 15 Jul 2021, at 21:12, Black, David <David.Black@dell.com> wrote: > > Congratulations to Gorry and Colin (authors) on publication of this RFC, and many thanks to all who have contributed. > > Thanks, --David (document shepherd) > > David L. Black, Sr. Distinguished Engineer, Technology & Standards > Infrastructure Solutions Group, Dell Technologies > mobile +1 978-394-7754 David.Black@dell.com > > -----Original Message----- > From: IETF-Announce <ietf-announce-bounces@ietf.org> On Behalf Of rfc-editor@rfc-editor.org > Sent: Thursday, July 15, 2021 2:44 AM > To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org > Cc: drafts-update-ref@iana.org; tsvwg@ietf.org; rfc-editor@rfc-editor.org > Subject: RFC 9065 on Considerations around Transport Header Confidentiality, Network Operations, and the Evolution of Internet Transport Protocols > > > [EXTERNAL EMAIL] > > A new Request for Comments is now available in online RFC libraries. > > > RFC 9065 > > Title: Considerations around Transport Header Confidentiality, > Network Operations, and the Evolution of > Internet Transport Protocols > Author: G. Fairhurst, > C. Perkins > Status: Informational > Stream: IETF > Date: July 2021 > Mailbox: gorry@erg.abdn.ac.uk, > csp@csperkins.org > Pages: 37 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-ietf-tsvwg-transport-encrypt-21.txt > > URL: https://urldefense.com/v3/__https://www.rfc-editor.org/info/rfc9065__;!!LpKI!3M0NO0ODV-nt3C_DC5DEbl-yI4A8OwdN7J0j217lSSwjSNEywrkzCV8F7p9ezBCb$ [rfc-editor[.]org] > > DOI: 10.17487/RFC9065 > > To protect user data and privacy, Internet transport protocols have > supported payload encryption and authentication for some time. Such > encryption and authentication are 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. > > This document is a product of the Transport Area Working Group Working Group of the IETF. > > > INFORMATIONAL: This memo provides information for the Internet community. > It does not specify an Internet standard of any kind. Distribution of > this memo is unlimited. > > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/ietf-announce__;!!LpKI!3M0NO0ODV-nt3C_DC5DEbl-yI4A8OwdN7J0j217lSSwjSNEywrkzCV8F7h725XPb$ [ietf[.]org] > https://urldefense.com/v3/__https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist__;!!LpKI!3M0NO0ODV-nt3C_DC5DEbl-yI4A8OwdN7J0j217lSSwjSNEywrkzCV8F7uTvOMSc$ [mailman[.]rfc-editor[.]org] > > For searching the RFC series, see https://urldefense.com/v3/__https://www.rfc-editor.org/search__;!!LpKI!3M0NO0ODV-nt3C_DC5DEbl-yI4A8OwdN7J0j217lSSwjSNEywrkzCV8F7hsHsezy$ [rfc-editor[.]org] > For downloading RFCs, see https://urldefense.com/v3/__https://www.rfc-editor.org/retrieve/bulk__;!!LpKI!3M0NO0ODV-nt3C_DC5DEbl-yI4A8OwdN7J0j217lSSwjSNEywrkzCV8F7ieNbsoW$ [rfc-editor[.]org] > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > > The RFC Editor Team > Association Management Solutions, LLC > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/ietf-announce__;!!LpKI!3M0NO0ODV-nt3C_DC5DEbl-yI4A8OwdN7J0j217lSSwjSNEywrkzCV8F7h725XPb$ [ietf[.]org] > -- Colin Perkins https://csperkins.org/
- [tsvwg] RFC 9065 on Considerations around Transpo… rfc-editor
- Re: [tsvwg] RFC 9065 on Considerations around Tra… Black, David
- Re: [tsvwg] RFC 9065 on Considerations around Tra… Colin Perkins