Re: [quicwg/base-drafts] Tweak traffic analysis text (#3411)

ekr <> Tue, 04 February 2020 15:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BC4B612011F for <>; Tue, 4 Feb 2020 07:54:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.595
X-Spam-Status: No, score=-6.595 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id i8pstbLSf3uK for <>; Tue, 4 Feb 2020 07:54:15 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 06D3E120119 for <>; Tue, 4 Feb 2020 07:54:15 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 1B806521E74 for <>; Tue, 4 Feb 2020 07:54:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1580831654; bh=N6ZMHmYW+PWxdDkDqG5aRoNNG5YWZ7nIiEBFXR6RBhU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xZrew4aDM6crXDSFRnTGzqMHB/+7yF4xAb6wHmb/tuDYqeP/UQA/t2els9hkm6ld2 saw4vg/2a4gQ89OsHyJZmMBAVU0HeHCs93CilgTkiANdCAbnHIPc+8tJwTFwkcsJsZ NKBDv+L7onlBDu3OBaZOUDylOFJ4CJbxk6QB+ttQ=
Date: Tue, 04 Feb 2020 07:54:14 -0800
From: ekr <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3411/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Tweak traffic analysis text (#3411)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e3993a6a0a7_5d153fa6938cd95c439039"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 04 Feb 2020 15:54:17 -0000

ekr commented on this pull request.

> @@ -1527,8 +1527,10 @@ Where HTTP/2 employs PADDING frames and Padding fields in other frames to make a
 connection more resistant to traffic analysis, HTTP/3 can either rely on
 transport-layer padding or employ the reserved frame and stream types discussed
 in {{frame-reserved}} and {{stream-grease}}.  These methods of padding produce
-different results in terms of the granularity of padding, the effect of packet
-loss and recovery, and how an implementation might control padding.
+different results in terms of the granularity of padding, how padding is
+arranged in relation to the information that is being protected, whether
+padding is applied in the case of packet loss, and how an implementation might
+control padding.

How about a citation to

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: