Re: [Pearg] Call for adoption: draft-wood-pearg-website-fingerprinting-00

Amelia Andersdotter <> Tue, 21 January 2020 10:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0C7311200E3 for <>; Tue, 21 Jan 2020 02:38:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id cgdGkfZQf0VQ for <>; Tue, 21 Jan 2020 02:38:10 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DD6F3120091 for <>; Tue, 21 Jan 2020 02:38:08 -0800 (PST)
Received: from [] (unknown []) (Authenticated sender: by (Postfix) with ESMTPSA id DEA61240009 for <>; Tue, 21 Jan 2020 10:38:05 +0000 (UTC)
References: <>
From: Amelia Andersdotter <>
Message-ID: <>
Date: Tue, 21 Jan 2020 11:38:04 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-Language: en-US-large
Archived-At: <>
Subject: Re: [Pearg] Call for adoption: draft-wood-pearg-website-fingerprinting-00
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Enhancements and Assessment Proposed RG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 21 Jan 2020 10:38:14 -0000

Hi all,

I support adoption. Bearing mind Stephen's comments from earlier, there
may some work already ongoing in IPSecME:


"This document describes a mechanism to enhance IPsec traffic flow
security by adding traffic flow confidentiality to encrypted IP
encapsulated traffic.  Traffic flow confidentiality is provided by
obscuring the size and frequency of IP traffic using a fixed-sized,
constant-send-rate IPsec tunnel.  The solution allows for congestion
control as well."

There's also a project in IEEE 802.1 (well, it's starting up at this
time) that tries to explore ways of mitigating web traffic
fingerprinting by ensuring packet length/timing etc. are homogeneous. It
will be covered eventually here:

best regards,


On 2020-01-13 10:42, Sara Dickinson wrote:
> Hi All, 
> A draft called ‘Network-Based Website Fingerprinting' ( has been presented twice in PEARG meetings and received positive feedback at IETF 106. This email starts a two week Call for Adoption of this document.
> Please review this draft to see if you think it is suitable for adoption by PEARG and send comments to the list, clearly stating your view.
> This call for adoption ends on 27th January 2020.
> Sara.