Re: Entropy in headers for connection identification at a stateful firewall

Töma Gavrichenkov <ximaera@gmail.com> Tue, 06 November 2018 09:38 UTC

Return-Path: <ximaera@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 019A4130DFF for <quic@ietfa.amsl.com>; Tue, 6 Nov 2018 01:38:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 nc8UY76VAFxc for <quic@ietfa.amsl.com>; Tue, 6 Nov 2018 01:38:00 -0800 (PST)
Received: from mail-yb1-xb32.google.com (mail-yb1-xb32.google.com [IPv6:2607:f8b0:4864:20::b32]) (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 23FA5129AB8 for <quic@ietf.org>; Tue, 6 Nov 2018 01:38:00 -0800 (PST)
Received: by mail-yb1-xb32.google.com with SMTP id f15-v6so5022517ybq.13 for <quic@ietf.org>; Tue, 06 Nov 2018 01:38:00 -0800 (PST)
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:content-transfer-encoding; bh=wZBLzhLQC+B8bsD3sGO61GovKXVPH4tqdTF0RY7liNM=; b=L8785Xreqht98yI1HTjnGcGTGzoEJBXqGwqfFq+NPkDwWHzY7GG7YV0Pi9n7sT7sUj 1rJvAxTHy0WUQCejHiQw42yrfGx4GAdyH0JvlIF2TGoN/5a3Y/bQaXaPUAByk0o1ZeiA HuwFCw9nHQcUoLdDQvzs7vHal04cYgWqyVUDkaSDUtHMf09njkqzvePxoxM51yYqKAOO 5Pg10W+vqrvjKxEguwHH3RYpd/b6slDytDKv2ZAMUZfPhq1YsKmrg8DEC2xrB1PfQ7St ly4VqV63SQUK54EB2dw97cjAHZSJYpbkhICgdKQXM5NkkWYZr/H9IyY6UaceIVxh3YGg gz7A==
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:content-transfer-encoding; bh=wZBLzhLQC+B8bsD3sGO61GovKXVPH4tqdTF0RY7liNM=; b=OTt+uCXSuBW3VIsZj+knRTyiGfnOS1v1avv0V+TwPeMNU33zdx24zCPF31MNhfCbkV PLvjxqGMz74jR0xYA9I1LLYYKVsANT/XH+P2gnjqyG72Y9cfWZVZb/7T6swSkynHh5UP H+oGPLa1WTksLL5DV1SEFhHdLyjrv37ubbdQ6act/RUpQlELRzfrd7W35h4NNRU3gb/S aZuQM1C2WtO0SRXl9lBouEi01RXS2o1D6BzEHFGz4XoIv3SlsMhgDmaQsRVQ0a3a+3SB Ve/anAgvAO96quwf1Ns51sd7FNuVUjMQ9x7Q7jEFo+7nM3RkQ6hkMApoY00q5qqjAx6F +giQ==
X-Gm-Message-State: AGRZ1gJCUhBYiirt8j4eN3nHvPErHnWpxq3Mtl0DoyK6Z2Y+s4Ww9efQ DICBBSqOLDqKQlCMRK5W3SIrFwjOGyxnXu0MrJ0=
X-Google-Smtp-Source: AJdET5fjUyxlsE/yZ1Hw8uvS+jS8LpNFPWPrK4J1SF7STc1GJLIx3SP9KeJlKwLfe3mKnFEy5RQmmq1Y/B/V4O9w6hA=
X-Received: by 2002:a25:904:: with SMTP id 4-v6mr7855132ybj.357.1541497079101; Tue, 06 Nov 2018 01:37:59 -0800 (PST)
MIME-Version: 1.0
References: <CALZ3u+ZXhEtkLUiebQq=uy+cTU+k5sG9Hbe4eaKKcdm-usGiqQ@mail.gmail.com> <CAN1APddd06DLjPMT2ZHCedgk_DnqGmv8DW+vtqOZa2juc4ndig@mail.gmail.com> <CALZ3u+YUDz50LVWZRX0i8dmqgvBKqqHiMgBwjdQUBBQB6O=CyA@mail.gmail.com> <CAN1APdeq0g0ZXCQqCYffiAGKpDc5stWmtzU9TrgikMSW=SyeMg@mail.gmail.com>
In-Reply-To: <CAN1APdeq0g0ZXCQqCYffiAGKpDc5stWmtzU9TrgikMSW=SyeMg@mail.gmail.com>
From: =?UTF-8?Q?T=C3=B6ma_Gavrichenkov?= <ximaera@gmail.com>
Date: Tue, 6 Nov 2018 16:37:47 +0700
Message-ID: <CALZ3u+ZxL7rO=umfujq9QbA1gDTOo-rQhvtb7SQ80jxmLSs2tg@mail.gmail.com>
Subject: Re: Entropy in headers for connection identification at a stateful firewall
To: mikkelfj@gmail.com
Cc: quic@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Jmg8FWSe1CeDtunf19vzUxQQCtc>
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: Tue, 06 Nov 2018 09:38:02 -0000

On Tue, Nov 6, 2018 at 4:25 PM Mikkel Fahnøe Jørgensen
<mikkelfj@gmail.com>; wrote:
> That is also what I meant: the middlebox could observe excess load on a specific 3- or 5- tuple without itself being overloaded.

Ah. Yes, this way changing to a new 5-tuple will help for some period
of time, though it makes QUIC a poor choice for e.g. video streaming
then :-(

> QUIC allows for multiple connections on the same 5-tuple

Well, sorry, this is up to the terminology. The purpose is just to
make sure an incoming packet is in fact a response to something
outgoing in the past. How many connections or streams go through those
packets is out of scope of the problem.