IETF Logo Mail Archive

Re: A question about user tracking with QUIC

Lucas Pardue <lucaspardue.24.7@gmail.com> Mon, 07 June 2021 12:52 UTC

Return-Path: <lucaspardue.24.7@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 14F473A150C for <quic@ietfa.amsl.com>; Mon, 7 Jun 2021 05:52:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 SkjstnjtFTGV for <quic@ietfa.amsl.com>; Mon, 7 Jun 2021 05:52:33 -0700 (PDT)
Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (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 2C0D83A1509 for <quic@ietf.org>; Mon, 7 Jun 2021 05:52:32 -0700 (PDT)
Received: by mail-ed1-x52e.google.com with SMTP id w21so20119642edv.3 for <quic@ietf.org>; Mon, 07 Jun 2021 05:52:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/O2zSn8+dDIdhze/2CoqlTIfB+ibP/VujTp1ZddIj/A=; b=GrtlyS8t4iccHRiZEdXvxc03dzFt36IUGfYI8nD0UNWNhIGMFSRQxcCUeRETuwDeWn CjvUAvCy3MNsNcLd31HNVDcsK2Dd2LA/ZtiSfBm+ugaOS5ZhEtlqKWpyGft6pygNdUlx plLZLwQXxYAbTlvQudrn6Aze+y5Cz6EuoFBxJg/nW7qnI+bVD12eyKen1w0peDftSgVi /uzsh6jmCTCEfhKG0r06ILGsbrq/UBILlyO5yOF5iGHheCRWi8oaInugqcq3OqkAFPG8 LX/YpgtkASWnu29dmljCaEoDgoYaxP6C9rDW31eAgmb5Q3IkJMIkmtNgyQChKgANVZHi zynA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/O2zSn8+dDIdhze/2CoqlTIfB+ibP/VujTp1ZddIj/A=; b=NkLf5sUbCaWhbLke0Dvag+BcmtXkN+womABxSghY6kaNrI5JLmnE/Soh6UerNourOM aiPDQZmEQl7R0mpkDhgxDJN12kv+8BZiHvXZWtHww8YWdtYQ/k0hiiiXwHc1j9iFKWIe QHzDtFudHTmf6BYI5vTSEge59R8kimeousSXoJwIjz3Kjm2+D5wG5nrbUGapAoAM5Oxe RNTrnjtvuxILi6XGd+GFzUb2dukUaBv6G2amweQNKfIrE55ZyWamX8UsRMv8PBS5C7+z CtSWMrTC6PK7/alunA0Zq9cs0Qo1v7DaIQcY79FNGb/nNLEAXuCFqcc7ev9VSYP1fEpS hMhg==
X-Gm-Message-State: AOAM532saX4vKST2nSghAdCJRnFNwY1X9iuAGBs3j+l+wFtQtUh8UyXO GvOJ5F9Eqyd4kl0GaIrwdoGsBzFsMqSVcVRCnHc=
X-Google-Smtp-Source: ABdhPJw0i5sFKkw73AXD76ZJeaW1jpOifcODh7OpF3M/DhzZo0ek4LnSSgbQNi3jt0an820k1ffnTzUDWguh4zMz5nQ=
X-Received: by 2002:a05:6402:510f:: with SMTP id m15mr19911496edd.283.1623070350529; Mon, 07 Jun 2021 05:52:30 -0700 (PDT)
MIME-Version: 1.0
References: <20210607123854.GA16312@nic.fr> <CAC7UV9bkqOeCgDsCH+Hdq0v=zmRKNNDtpfiq6Ap_vzm5zUzGVg@mail.gmail.com>
In-Reply-To: <CAC7UV9bkqOeCgDsCH+Hdq0v=zmRKNNDtpfiq6Ap_vzm5zUzGVg@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Mon, 07 Jun 2021 13:52:19 +0100
Message-ID: <CALGR9oZiUe5TyY3Tv432__GH=v+Lpv2EZah0G4ZD+g3E2FkaMg@mail.gmail.com>
Subject: Re: A question about user tracking with QUIC
To: Robin MARX <robin.marx=40uhasselt.be@dmarc.ietf.org>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b056f105c42c8378"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/BH43pUI2qJDSStO7IjKDXSLa1z8>
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 12:52:48 -0000

Hi Stephane,

As Robin says, to survive such client IP changes would require QUIC
connection migration. RFC 9000 Section 9.5 [1] deals with the privacy
implications of migration.

Cheers
Lucas

[1] https://www.rfc-editor.org/rfc/rfc9000.html#section-9.5

v2.46.0 | Report a Bug | By Email | System Status