IETF Logo Mail Archive

Re: A question about user tracking with QUIC

Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com> Mon, 07 June 2021 14:37 UTC

Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 266953A18B8 for <quic@ietfa.amsl.com>; Mon, 7 Jun 2021 07:37:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 a1Cyllf8mu98 for <quic@ietfa.amsl.com>; Mon, 7 Jun 2021 07:37:50 -0700 (PDT)
Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEFF03A18BE for <quic@ietf.org>; Mon, 7 Jun 2021 07:37:49 -0700 (PDT)
Received: by mail-wr1-x42f.google.com with SMTP id i94so12860244wri.4 for <quic@ietf.org>; Mon, 07 Jun 2021 07:37:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=goBfjKY8oD0Woy/0sFUS57zXfNTQhyY8SK6OoPlhKSM=; b=By3pBha9hrNSRMo+Jqm7pzA/eJlqFYbXMr1W2CeNs3uEL84LcHR5d7LDbytZl/Z3dX f6srNhfFj13++dwMN2IIwxSstt1Wor9jslIy7a9Cldh4eRxWFalA4qBEkuB+Qsf5CCJZ UOFE6ho5XGhyJyD5F3bfCHhP5eIeHcKopx/hyYj/+X5ummyqIbnSL1SNlMHAg+hHW7GH 86xtqdDN3h8GZJbsrhMwVM+a7tN9logsjdVBihA4ix7pJPz8AmvCsgmiWEGrquSbOLBN eJ8l5Q9VSvsDslzUDP1zM7AHhyGAX1e7dkrMYRdwdUkXCwPztQ3Kgn+RJozN89yOiFrQ L03A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=goBfjKY8oD0Woy/0sFUS57zXfNTQhyY8SK6OoPlhKSM=; b=Vkps4fCAImvVkXgdsAw4nZvNffTQ/t5ezif+DAZCgm/m3rHX2qJSywAjzpbwf/txBQ vJBHo5NZLG8EIx3y+Cnk61mQwyofJprH6DQCIGQxxc9o9sy9STKKrR8dQPIrkgVk8RVJ GjQFQDqcKlh+WvEXLakUlJdO+dAn2fawLUcFXryoeK4ejWjAWuIHjGkAJZzNWxWxqfHR pcWlnxeIXkF9sHP1VTKgXfooaqCWYafX6Kon/HAuqyXQsiY7EU8+puEqTl1l5aRs1UzY eIc0Hsty8tmtX/kN/lLtJpXCAqGj+vUCjqRs2+fBHxDXE8ulOOiwR6BynEj3KlBsIASb Z8ZA==
X-Gm-Message-State: AOAM53216+Kpy/I3Wnc2TAGreQT7gs4sv4GElDHwfolTeBAMINqoIy9R 3oOKHTCjm1DgGeCDf6RiQp4=
X-Google-Smtp-Source: ABdhPJw3TzDJTRWl854R45qajtaFwYt6vs9RCQNQ1vL8uNam3dIy8e9yLD9WxN9Xmlj1J+15wc0BEA==
X-Received: by 2002:adf:e109:: with SMTP id t9mr17220671wrz.372.1623076666484; Mon, 07 Jun 2021 07:37:46 -0700 (PDT)
Received: from [192.168.1.3] ([87.72.40.193]) by smtp.gmail.com with ESMTPSA id k16sm14407548wmr.42.2021.06.07.07.37.45 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 Jun 2021 07:37:46 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Re: A question about user tracking with QUIC
From: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
In-Reply-To: <20210607142015.GA31240@sources.org>
Date: Mon, 07 Jun 2021 16:37:45 +0200
Cc: Lucas Pardue <lucaspardue.24.7@gmail.com>, IETF QUIC WG <quic@ietf.org>, Robin MARX <robin.marx=40uhasselt.be@dmarc.ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C1B56269-0EF7-42EC-8824-70F7485807B2@gmail.com>
References: <20210607123854.GA16312@nic.fr> <CAC7UV9bkqOeCgDsCH+Hdq0v=zmRKNNDtpfiq6Ap_vzm5zUzGVg@mail.gmail.com> <CALGR9oZiUe5TyY3Tv432__GH=v+Lpv2EZah0G4ZD+g3E2FkaMg@mail.gmail.com> <20210607130422.GA27971@sources.org> <EE723B6D-7B6B-4B68-A4A1-F1809CF68F1B@gmail.com> <20210607142015.GA31240@sources.org>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ZYDBPdbdtfqdlCA_YPMvsIv8ryo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jun 2021 14:37:54 -0000

Also note that a lot of dicussions have taken place on github issues and pull requests.

> On 7 Jun 2021, at 16.20, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
> 
> On Mon, Jun 07, 2021 at 03:36:31PM +0200,
> Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com> wrote 
> a message of 37 lines which said:
> 
>> User tracking has been discussed a lot during the development of the
>> QUIC protocol.
> 
> User tracking BY THE SERVER? I'm sure the WG left no stone unturned
> but I cannot find this discussions in the email archives. I probably
> used the wrong keywords.
> 
>> For servers, it is necessary to track users across migrations,
>> because you need to maintain connection state and to maintain the IP
>> address of where to send data.
> 
> This is why that I suggested (but it may be a bad idea, may be I
> didn't think of everything) that a privacy-conscious client may be
> better by not using connection migration, and resetting to an entirely
> new connection when the IP address changes.
>

v2.23.0 | Report a Bug | By Email