Re: [tsvwg] [saag] 3rd WGLC (limited-scope): draft-ietf-tsvwg-transport-encrypt-15, closes 29 June 2020 Wed, 01 July 2020 12:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 903133A0A05; Wed, 1 Jul 2020 05:58:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id BTy7IWhqfqQw; Wed, 1 Jul 2020 05:58:01 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E41D23A0A02; Wed, 1 Jul 2020 05:58:00 -0700 (PDT)
Received: from (unknown [xx.xx.xx.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (ESMTP service) with ESMTPS id 49xh930g91z108j; Wed, 1 Jul 2020 14:57:59 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=ORANGE001; t=1593608279; bh=+jCYGKBn3Y3//Tdee16/RWBj7w/MOP8yoBzqxulUKU4=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=KF6054p1nNP/zpS9WSagppgjFXZSVU9LM6sXheMFmIBlvvorDxZbgcKpSuTqoietr nGJfn4lw+zsJf1FVzcHsRQhvDpGRHbFqGOJU081n8veopt2IU1jDaLuvx/xJzNozWz R+EGWfMex3zIuNpAlvVZ/V4gVBvounQmHLEOlRcW3wT5LALTrL+afJtuULsmWTWwQN CPEC4uWNUQBiqs2exK1YQv9mt+Hu7kCc1cOY1eb7Z71S4EHoqWYwn01H+sQNy0VT/W Wm1jTlz6YbP44wIfyL0lIzgOsbQ/WgnpLSNk3LDW3Ck5lp1hwTKqS6ejd0Qd7jX3gk nvkswEOgW529g==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (ESMTP service) with ESMTPS id 49xh926K67zDq7j; Wed, 1 Jul 2020 14:57:58 +0200 (CEST)
From: <>
To: Hannes Tschofenig <>, "Black, David" <>
CC: int-area <>, "" <>, IETF SAAG <>
Thread-Topic: [saag] 3rd WGLC (limited-scope): draft-ietf-tsvwg-transport-encrypt-15, closes 29 June 2020
Thread-Index: AdY9/kL5KQoLk/CbSKeZ9xMZ8uq3SAQe3d4AAAnHrZAAQX40gA==
Date: Wed, 1 Jul 2020 12:57:57 +0000
Message-ID: <21886_1593608278_5EFC8856_21886_470_1_787AE7BB302AE849A7480A190F8B9330314EBA5C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <> <> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B9330314EBA5COPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [tsvwg] [saag] 3rd WGLC (limited-scope): draft-ietf-tsvwg-transport-encrypt-15, closes 29 June 2020
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 01 Jul 2020 12:58:04 -0000

Hi Hannes,

It would be helpful if you can explicit the “wrong message” you are referring to, and preferably with text from the draft conveying that message.

Thank you.


De : Int-area [] De la part de Hannes Tschofenig
Envoyé : mardi 30 juin 2020 07:50
À : Eric Rescorla; Black, David
Cc : int-area;; IETF SAAG
Objet : Re: [Int-area] [saag] 3rd WGLC (limited-scope): draft-ietf-tsvwg-transport-encrypt-15, closes 29 June 2020

I believe this document signals a wrong message to the wider Internet community. I agree that it should not be published as a consensus document.

I understand that some people are unhappy about encrypting more meta-data. This prevents them from doing things they used to do in the past, some of which they should have never done in the first place.
Improving the protection of meta-data is important and well supported by a large number of activities in the IETF (the notable exception being CoAP+OSCORE).


From: saag <> On Behalf Of Eric Rescorla
Sent: Tuesday, June 30, 2020 3:00 AM
To: Black, David <>
Cc: int-area <>rg>;; IETF SAAG <>
Subject: Re: [saag] 3rd WGLC (limited-scope): draft-ietf-tsvwg-transport-encrypt-15, closes 29 June 2020

> This 3rd WGLC is limited to the following two topics:
>     Whether or not to proceed with a request for RFC publication
> of the draft.   The decision on whether or not to proceed will
> be based on rough consensus of the WG, see RFC 7282.
> During the 2nd WGLC, Eric Rescorla and David Schinazi expressed
> strong views that this draft should not be published –  those
> concerns have not been resolved and are carried forward to
> this WGLC.  This email message was an attempt to summarize
> those concerns:
> Further explanation from both Eric Rescorla and David Schinazi
> is welcome and encouraged to ensure that their concerns are
> clearly understood.

Well, I'll try again, but I'm not sure that I can do better than
I have before.

For reasons that are laid out in RFC 7258, the trend in protocol
design in IETF is towards encrypting more and more. The last two
transport protocols that were designed and widely deployed (SCTP over
DTLS and QUIC) both encrypt the vast majority of the protocol
metadata. This document advertises itself as "considerations"
for design of such protocols:

   The transport protocols developed for the Internet are used across a
   wide range of paths across network segments with many different
   regulatory, commercial, and engineering considerations.  This
   document considers some of the costs and changes to network
   management and research that are implied by widespread use of
   transport protocols that encrypt their transport header information.
   It reviews the implications of developing transport protocols that
   use end-to-end encryption to provide confidentiality of their
   transport layer headers, and considers the effect of such changes on
   transport protocol design, transport protocol evolution, and network
   operations.  It also considers some anticipated implications on
   application evolution.  This provides considerations relating to the
   design of transport protocols and features where the transport
   protocol encrypts some or all of their header information.

However, as I said above, the new transport protocols that are
actually being designed already feature metadata encryption and as far
as I can tell, there is no prospective protocol new transport protocol
design project for which these issues might be live. In that context,
it's hard not to read this document with its long litany of practices
which are impacted by metadata encryption as a critique of the
decisions by SCTP/DTLS and QUIC to encrypt most of the metadata.

This impression is reinforced by the description of the actual
practices themselves, which focuses almost entirely on practices
which appear to be benignly motivated (e.g., performance monitoring,
troubleshooting, etc.) However, we also know that metadata is widely
used for practices in which the network operator is adversarial
to the user, for instance:

- Blocking traffic based on TCP port, IP address, SNI, etc.

- Performance-based traffic class discrimination

- Monitoring the user's behavior via indicia like the ones above
  or via traffic analysis (see [0])

Yes, I understand that the authors explicitly disclaim judgement on
these practices, and the document does briefly touch on the general
idea, though the "concerns...have been voiced" tends to minimize those
concerns [1] but the selection of practices to focus on is extremely
telling. Focusing on the downsides of encryption for (at least
arguably well-meaning) network players while mostly ignoring the large
class of non-benign behaviors which encryption is intended to protect
against has the effect of overemphasizing the costs of encryption to
those players and minimizing the benefits to the endpoints whom it is
intended to protect.

To be maximally clear: I don't object to this document existing
and I don't think that the opinions implicit in it are ones that
should not be expressed. I merely don't think that it should be
published as an IETF Consensus document.


[1]    Another motivation stems from increased concerns about privacy and
      surveillance.  Users value the ability to protect their identity
      and location, and defend against analysis of the traffic.
      Revelations about the use of pervasive surveillance [RFC7624]
      have, to some extent, eroded trust in the service offered by
      network operators and have led to an increased use of encryption
      to avoid unwanted eavesdropping on communications.  Concerns have
      also been voiced about the addition of information to packets by
      third parties to provide analytics, customisation, advertising,
      cross-site tracking of users, to bill the customer, or to
      selectively allow or block content.  Whatever the reasons, the
      IETF is designing protocols that include transport header
      encryption (e.g., QUIC [I-D.ietf-quic-transport]) to supplement
      the already widespread payload encryption, and to further limit
      exposure of transport metadata to the network.

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.