IETF Logo Mail Archive

Privacy considerations of multipath (Re: My BoF report: multipath)

Lucas Pardue <lucaspardue.24.7@gmail.com> Fri, 23 October 2020 20:32 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 318A73A0121 for <quic@ietfa.amsl.com>; Fri, 23 Oct 2020 13:32:10 -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 yC4UjJjuDcgm for <quic@ietfa.amsl.com>; Fri, 23 Oct 2020 13:32:09 -0700 (PDT)
Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) (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 DC1FF3A011B for <quic@ietf.org>; Fri, 23 Oct 2020 13:32:08 -0700 (PDT)
Received: by mail-ej1-x62a.google.com with SMTP id ce10so4120974ejc.5 for <quic@ietf.org>; Fri, 23 Oct 2020 13:32:08 -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=iKXODRq7ihKTeljQ6mtV+zVv7+wjWnGRI92Aj82WaD4=; b=JPvqsjo+960vQLkj073Wnm/sNnhh/gVBadlJeP8wkaNCQYnKAQtUcAg3a68vD6VP7v 9LaszaXlTTkNPY9CBwEiVCGU6coH9vdsGnlaollqWmXUZ7wmoNuWSTRtaS3PCrmOKwlQ isEErKhgMDvubQzBjfAtK4RZReXlRY7wwi/+3vvlyCNNsK6iEXguZbifV4CskDQyuKTk iUMxgltGUokPhxwq0sPj+fNFNwdZ3RpHNTqBVm0PpjvqYrr4YByN3kLjaHkrogUmgDJf 4C3AbzRrFcFInsjyDgXqyN5/Tz0t2b9/0lbIXLb/Hkp2n1bRWgElgYNLGRJyIzFcAz2G arlw==
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=iKXODRq7ihKTeljQ6mtV+zVv7+wjWnGRI92Aj82WaD4=; b=ktBpzII2+fhh9Xfs3lV2idp89ud3jQ9Q6L8224VpH2kw8o90CIcb8+20a/XSN9sJra uOy7tYY1rlqIf3H0X6z/Dvacfo7MG0jhLxXMTh5ODTNtMS+eBNaLWZLCwNolv/ihE8fX i1Bgo/eavDORx67/u62NQHMveo61FJWZ4H4nKYhiXbgzKbpN/QbFDMlYd1smOYjrisfv gZ7YNMN035PMhvSKwVBz1HbzEbj4pqGxgOUPzB3JuzmGJVgIV+UA1UAwB52BfHrqCMVt GVCOh9zsSOnxW6RLBsfeVpR/1HaOcNHtltKTt+2sx55uDHmi+/VYgikcixuYVEkeyK0I hx/w==
X-Gm-Message-State: AOAM533JGH4Rzn64F9B6kepyV46zcYVx73ilZEnrZrdy52fopj68RYay DQ9GjhsHxHQugsUtZLdiZ+bBEW8ZLUcRJsIcY+0=
X-Google-Smtp-Source: ABdhPJwAgzOmQR9TaCzamAl0ZF6xFzKFG+LdTOB8sauuYq8prov3TLalKrD44iRJJgVj+z/tvTIOACbrLlJg/MgSLaE=
X-Received: by 2002:a17:907:94d2:: with SMTP id dn18mr3872755ejc.374.1603485127187; Fri, 23 Oct 2020 13:32:07 -0700 (PDT)
MIME-Version: 1.0
References: <d84c82b1-fa67-4676-9ce2-d2a53d81b5f7@www.fastmail.com> <5741601d-7e67-898e-5840-70feceb994e9@uclouvain.be> <CALGR9oZW0s6c6+N+3R8bD17yPBPQa4E_cVOaTOSNTVQPYy6sUg@mail.gmail.com> <CAC8QAcditJ0nzdCNHOhi-1xtezoXb0u=hrGBWtZ3Cj3XP6CW4g@mail.gmail.com> <CALGR9oZfw5LqfPyZw6Yb8JTmuqi0prTL0f0yT9Rdq6oz5u51fg@mail.gmail.com> <ccbd3f9a-883e-6262-5735-2b9f25c6c6c4@zinks.de>
In-Reply-To: <ccbd3f9a-883e-6262-5735-2b9f25c6c6c4@zinks.de>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Fri, 23 Oct 2020 21:31:56 +0100
Message-ID: <CALGR9oaw_-dbYSu5oN1Usvwr2h8wp-gvcmzx+0+2HJM-4Ac+4A@mail.gmail.com>
Subject: Privacy considerations of multipath (Re: My BoF report: multipath)
To: Roland Zink <roland@zinks.de>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000068d9c305b25c79cf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/DKPu-EhjaiAHRrKJXALfwztbfpE>
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: Fri, 23 Oct 2020 20:32:10 -0000

Hi Roland,

On Fri, Oct 23, 2020 at 8:34 PM Roland Zink <roland@zinks.de> wrote:

> A application works with a single connection most of the time. As
> application developer you probably can't afford to put any effort in
> improving this when it isn't absolute necessary. If you do it on the
> application layer then the application may also get location information
> out of it, like IP addresses or WiFi names, and this is a privacy issue.
>

This is an interesting thought and I wonder if you might be able to
elaborate some. The userland QUIC libraries I'm familiar with require
applications to do a lot of their own lifting with regards to the network.

I'm particularly interested whether there is any difference say between:

1) An HTTP/3 client application that wants to open two QUIC connections
using a userland QUIC library.

2) An HTTP/3 client application that wants to open one multipath QUIC using
a userland QUIC library.

Is the expectation here that there is some TBD OS-level API would abstract
network layer information from the application in the name of privacy?

Cheers
Lucas

>
>

v2.23.0 | Report a Bug | By Email