Re: [tsvwg] I-D Action: draft-ietf-tsvwg-transport-encrypt-11.txt

Tom Herbert <> Fri, 31 January 2020 18:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 76570120105 for <>; Fri, 31 Jan 2020 10:48:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 g2PjhV25sODB for <>; Fri, 31 Jan 2020 10:48:25 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::529]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 528C712011B for <>; Fri, 31 Jan 2020 10:48:25 -0800 (PST)
Received: by with SMTP id j17so8889285edp.3 for <>; Fri, 31 Jan 2020 10:48:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=yYQJibWwr3Pa5icsQvnyYjsdACE0kTb0Kpb/5U1UPPA=; b=Py7vLYjhs6/YOm/PwbfxvqQv+vIk97S0k6ncHXrhYiMS/SYI+lnk3UZYcp6/oGmlEy /N8eL+V4swlup3jccZxHgSprFj7HqPxz1H6W8K97sjIfGO9SNNYQTrnUARPB6dvBY27T y5g0d1i8vn0D8EO1EVxPrkI6h8SJ8YDM1m3kNU01BEgPtsQ8+WPOjiIIlVMBEZ/S4e15 pnRKXe6CWj7t0K2YyuxugzzzbTtdECw5UESXZr2I6KIbVb3T28VKNQsGa5ay0h/KTibI arsv309evoZRtxvz7A01up/TC9s5f/sceKu9ZdREZjvAM1U5ZpTh1eJXceHrx8T0uE7O bEcw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=yYQJibWwr3Pa5icsQvnyYjsdACE0kTb0Kpb/5U1UPPA=; b=Cgq8xZwX/sEjDH6/UaVKgewFLZ0CsCdX1y6fn9Bpbosgo8f3e3c4i9kp781DU2eTl9 xOdxitwiSEfXCPT3k4M7DG2yaZNxHMgNvANLoanEIW2GCzNZs7muQqfsfZewcR5WHRqW RYt72lgZW2sE23kYJfLxr1OdKtNJbqrTf1H/+w9bO/UxGkse6a1tHQkVunjbYr9E0x6w 2Vl+GZ6FgjzyIm3CLJlhfkGi8wG7KFHMam9bSnQMVybvZajmFTsUUPPz1lX4dB9vCwPG KRq+52GWtqLLmitap3xp6Wvb970IifdIGO96tNzCbUaELoLJrLGNcR+ij79cfx5DLxcB IgNw==
X-Gm-Message-State: APjAAAX53BYkQeIPNiCC/OTkBkbS+/IroZEMGMiYhpE0tbYcwPlx8Z/U Xosx2ZIAXZCnBvwG/34CrX+L5hzCKJsNDfwHNZ2LufuvtSY=
X-Google-Smtp-Source: APXvYqzkRdEBztJuUmPuZ+bCdQTkADSs8GzQklGj5cuwQhs07C5dxZXIkVJAum4aHSKJH+G1rSdpZjIqC2KiB3C+g7c=
X-Received: by 2002:a17:906:55d3:: with SMTP id z19mr10344262ejp.304.1580496503397; Fri, 31 Jan 2020 10:48:23 -0800 (PST)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Tom Herbert <>
Date: Fri, 31 Jan 2020 10:48:11 -0800
Message-ID: <>
To: tsvwg <>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-transport-encrypt-11.txt
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: Fri, 31 Jan 2020 18:48:27 -0000

One comment:

>From the draft:

"Observing the protocol sequence number pattern of network usage.
Measurements can be per endpoint or for and packet size offers one way
to meausre this (e.g., measurements an endpoint aggregate (e.g., to
assess subscriber usage). observing counters in periodic reports such
as RTCP"

Misspelling measure. Note that tracking sequence numbers in the
network, flow tracking general, typically presumes that all packets
for a flow take the same path and consistently traverse the node
tracking transport state information. There's no requirement in IP for
that to hold.


On Fri, Jan 31, 2020 at 10:35 AM <> wrote:
> 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-11.txt
>         Pages           : 48
>         Date            : 2020-01-31
> 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, enable transport
>    evolution, and respect user privacy.
> The IETF datatracker status page for this draft is:
> There are also htmlized versions available at:
> A diff from the previous version is available at:
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at
> Internet-Drafts are also available by anonymous FTP at: