IETF Logo Mail Archive

Re: Multipath (was: Re: Re-chartering for extension work)

Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com> Mon, 16 December 2019 19:20 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 B6FFD1208EA for <quic@ietfa.amsl.com>; Mon, 16 Dec 2019 11:20:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 TjoQ84IbGRJF for <quic@ietfa.amsl.com>; Mon, 16 Dec 2019 11:20:20 -0800 (PST)
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 D35E11208D3 for <quic@ietf.org>; Mon, 16 Dec 2019 11:20:19 -0800 (PST)
Received: by mail-ed1-x52e.google.com with SMTP id c26so5945246eds.8 for <quic@ietf.org>; Mon, 16 Dec 2019 11:20:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=xSx4tmOFUYPw6yazR7XwdSv4N3zcC8N2hds2QbVxDhQ=; b=eDb//UQUD62F9aJ0d2wBTa0DJ8BaQHVLF2eLIrHiga06YFCgRWfU0Y0mx2OTN2amlB 6GnDQ1ThAzyR8ywsCFnhyV2KjKm87LDWt8tdsAaniREvgW5ZckTrO4cvixXKxtyAw7Id 7koG6lCjj/9x+BSBfQG41SjPPcDmfkfbaUP8acTpd/yw4fmGaPcDtnJh6VNT1a/jcokO HltWOXpkaF3NBSBTB1ObOt/kp1uUO9g/y1Zr5g+p+2LjLQxcMemwY5CKm3lwJ9vNGc9s 5jigHv/Tsg5d3YOpCAj0x7R0dM3EOar6KZrY8Y9T7egx5eWn87rmeAMvviDGKkY6z8pn f1sA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=xSx4tmOFUYPw6yazR7XwdSv4N3zcC8N2hds2QbVxDhQ=; b=RKhPB3h0jaT4oUxusM3rU10Ok8oUYvl84xw3tKICpUWxyVlw7sJLv89XKd3a+TZJOP UAqmHX7eHAxTz1fZ6gitmrkb53Qbrbf8rM1nBIFMzZMlmHDv7kJpLOX4qUcbUlJ4jDK8 Di/E1qJdTQcMq3rHKX807JcYfSP+XEa4PRI13z+kPVkUc8dO6wAWT0RLNmb8fenIRmz6 XQF2uN9QxB+i417xipllgDkel93holWeyYB/tx1v9+V5HClb5CthKt9l2XoIPC0EWwGa BhEyhpU8lQz7+q731UM/H2ZxW78ywdtsAWdY9bb7dgWaqfiMD1n2zgFrcq0L9OSUTOup CUmg==
X-Gm-Message-State: APjAAAXnOn8BhjYgRMOOdiiX4S/nx6xeO0T9Z3w5EvCvblvzPDanANjF zyekj1moEa6r+et3uL8uN+7ggtRwsfXe2j2HJn+LlmCN
X-Google-Smtp-Source: APXvYqxA8GZJNM3Y1klD7Xx3bdATpfbwCoAKya0bmN9e2rDIR3sdGMog8Mt98tf12l58xvLVl0cbl7biz+bip6OZi0I=
X-Received: by 2002:a17:906:2f09:: with SMTP id v9mr588095eji.91.1576524018263; Mon, 16 Dec 2019 11:20:18 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Mon, 16 Dec 2019 14:20:17 -0500
From: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
In-Reply-To: <DF4E42C3-3D90-4C68-989C-6B11833005F9@tessares.net>
References: <A56547B6-2E3B-4ABE-8C9B-BA9ACC489FB2@mnot.net> <1E872371-F543-4822-8C11-05601913A72E@tessares.net> <752D0B90-8B29-4DBC-9B2F-09E834335598@eggert.org> <49366B32-6425-486C-9453-96D27E2E8EAE@tessares.net> <CAN1APdfNyMBzeWKVRQojo4W_mgxXSSwj4X4EvFC9Pfz4bZ+Pdg@mail.gmail.com> <DF4E42C3-3D90-4C68-989C-6B11833005F9@tessares.net>
MIME-Version: 1.0
Date: Mon, 16 Dec 2019 14:20:17 -0500
Message-ID: <CAN1APddWow_QBs+_6GRLyauWFrLVvcr7LA9Mjqdgw-Bcp0d=tQ@mail.gmail.com>
Subject: Re: Multipath (was: Re: Re-chartering for extension work)
To: Olivier Bonaventure <olivier.bonaventure@tessares.net>
Cc: quentin.deconinck@uclouvain.be, Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>, Mark Nottingham <mnot@mnot.net>
Content-Type: multipart/alternative; boundary="00000000000016b0600599d71ad9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/RC6Wlrd1QFlZWQhQNkZm9Uk8WDU>
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, 16 Dec 2019 19:20:22 -0000

If you can observe encrypted traffic on both paths you have an opportunity
to correlate traffic if an endpoint consistently acks on one path and sends
on another. On path has small packets a fixed interval after larger packets
on the other paths. That could happen in a migration scenario where one
path is not yet fully committed so ACKs stay on the main path.

I don’t recall how it works today with single path migration, but I think
that it is required that ACKs happen on the same path as the packets on
which they are sent.

Mikkel


On 16 December 2019 at 18.29.29, Olivier Bonaventure (
olivier.bonaventure@tessares.net) wrote:

Mikkel,

On 16 Dec 2019, at 16:42, Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
wrote:

ACK across paths could lead to privacy leaks, no?


Since all QUIC packets are encrypted, a passive observer cannot easily
determine that acks are exchanged over a specific path. If the size of the
acks is a concern, then it is possible to pad QUIC frames to hide the fact
that such acks are exchanged.

Olivier


------------------------------

Disclaimer: https://www.tessares.net/mail-disclaimer/

v2.23.0 | Report a Bug | By Email