Re: Explicit measurability in the QUIC wire image (was Re: Packet number encryption)

Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com> Wed, 07 February 2018 10:23 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 9A6ED126C19 for <quic@ietfa.amsl.com>; Wed, 7 Feb 2018 02:23:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 tcdzFBFJBvrY for <quic@ietfa.amsl.com>; Wed, 7 Feb 2018 02:23:58 -0800 (PST)
Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::229]) (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 07107120727 for <quic@ietf.org>; Wed, 7 Feb 2018 02:23:58 -0800 (PST)
Received: by mail-it0-x229.google.com with SMTP id u12-v6so14964940ite.0 for <quic@ietf.org>; Wed, 07 Feb 2018 02:23:57 -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=YKQD60bweJ9vOO/Ny2efJ2FbjyV7w6RD6USMetmNkus=; b=KdV9DWdDnL4TwLbo1jOdTcwxfnlqfGBPJ+TCKT/ozS+dyQV5D4ENRQ4COL2QfMIMAj wZEtrULpccdy6DIRp1WjKvUbnnnEOhpC6FO/3W2TJeHZte9DrKVbM3/yASl2Hn4+Jatn F2OGS5+5kKcnTjoH/8MS7Yhg6LGUoL7doAv1D2WrSUWmzU4/Di2dTt1cxrFRtSSK5S0h mauvNhrqRKXWya68Z2S9TrZ4+LEFAi3fr7BYIIwx5XjhKkYik9cWJmUGiwE230NI7h9h TIT4MkAR6aA4SEEhcXQ6xnTdhwOQad97BMYYuu0Cn6mMe60O+vQPmDSdJX3RcW/IQ0VZ nijg==
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=YKQD60bweJ9vOO/Ny2efJ2FbjyV7w6RD6USMetmNkus=; b=rHqQggoIGGTvqlYemL6RF8kyHUGe3yFmKy+EVjw0lsdPV2N3YHMWkH2iGfHMNJKLmX C2eoT90HRjrGP2nGjTPBNENA0qLHAwP56AkvQr+ZgozEYsOeYwmuc5XWHIeaRIVWSqqa 6d8Hc3Ui9jDh7tT+JwkR/tDg5XV8zo2ycMP66zb0XMRJ+qtSrmlPpHB+liwNfW5uuU0e +6OQ0zXYVKFPsG9gafAhat3NmiI0hRA5rSxwP4QVnMSy5QZB9haA5BidMo2neeGekPt8 t6w3DdKPgO3izJTCqADg2xJ2doYXrrNFUzg8lqP+FUdB8UpuWWhDHEcDej/P+63nm5mV Dp5g==
X-Gm-Message-State: APf1xPAk5MHKzbvgvaqPNVft8lE5GEGBx4r6KCJtXM+tRYXCMrh5YgLj RWN9VEge+A0S4BqF5kWVV/O1jv+Ejqd1Rp4kwbU=
X-Google-Smtp-Source: AH8x226YTUCRo9SzIqLeCYh/VHrWh+7pJLp14S56X0RIiMEDo7eoZCaAfrp7unD+nxBg3mD69MPoQAWP6hvtsV7a7HQ=
X-Received: by 10.36.178.26 with SMTP id u26mr7038759ite.4.1517999037284; Wed, 07 Feb 2018 02:23:57 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 7 Feb 2018 02:23:56 -0800
From: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
In-Reply-To: <CABkgnnXkEsQkmdgX6c4_9w6YhTaPYrtdhUEJ8imi7NSChyC32g@mail.gmail.com>
References: <CABkgnnVyo3MmWtVULiV=FJTnR528qfY8-OmKGWAs0bCvri-a_g@mail.gmail.com> <1F7FB3B8-A94C-4354-9944-FB09FB8DB68B@trammell.ch> <CABcZeBMbwdwyC9TxxHBLYaZKfNB-FG2wCGjqUZ_mNR-A1R47FA@mail.gmail.com> <9096e5ec-581e-875a-b1dd-bff0b05206fd@huitema.net> <CABkgnnWRQSAufwPss+qf=xAzCwRYeNNH8XLPm3yFaHxOb+ba4g@mail.gmail.com> <BF80500A-6277-45DC-8525-9C3FE138B76D@tik.ee.ethz.ch> <5A7191E0.6010003@erg.abdn.ac.uk> <5214AD93-8376-4B25-922F-AF5551CC2E95@netapp.com> <F990E064-E6F8-41A3-B791-F776C9955E15@nokia.com> <CAGD1bZab0GaZFsHwC+nw3AxxC4VusxMJ6oDanzk3dSDdWKAXdw@mail.gmail.com> <2C515BE8694C6F4B9B6A578BCAC32E2F83BA1443@MBX021-W3-CA-2.exch021.domain.local> <BY2PR15MB07757473DB9788558B902EB5CDF80@BY2PR15MB0775.namprd15.prod.outlook.com> <6E58094ECC8D8344914996DAD28F1CCD861B7F@DGGEMM506-MBX.china.huawei.com> <e529144067624fcba636fc8c24ee3ff4@usma1ex-dag1mb5.msg.corp.akamai.com> <BY2PR15MB07754D83A1721F2BD742359BCDFE0@BY2PR15MB0775.namprd15.prod.outlook.com> <2CD9DC43-D69B-43F0-8474-DFE798850A52@akamai.com> <CAGD1bZaUuNxqpDkn62B0wWcFD8=mCUWrAwWGG-rAOxH7Mf1=cQ@mail.gmail.com> <CY4PR21MB01334E30C7AF6AE75F58EEFDB6FE0@CY4PR21MB0133.namprd21.prod.outlook.com> <CAGD1bZaxrqzdkk0wxRaULwOTgg6wnrSrXNBK31s4uxdozaACBA@mail.gmail.com> <CAGD1bZbOAaSBcQw4nVtGuwRunaAW8MYHq9yPxNN6DdKHzt5HtQ@mail.gmail.com> <CANatvzx+uDHMV5XS=OuVYBqe_RYX=EmVWAmjuONS8BpNYCPweA@mail.gmail.com> <5233815B-00F3-4961-ABB8-505906258B89@trammell.ch> <CAN1APdcuKSLYw4Odyc4g=+4_+ojsNekeqmM9eYqxykkfxRx3Cg@mail.gmail.com> <CANatvzz3rmGPRgu1Z5+bAHhgjiN3L5OVTDhb4fmpPX+M8o4z3w@mail.gmail.com> <DB6PR10MB17661B9957DF90733FA28EC5ACFD0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <DB6PR10MB176682C63A91007574BBEAECACFC0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <CAN1APddkFxLFREQQe+0Kqqi+zJeU20ALjzN4R0Muf9FD1BzZUg@mail.gmail.com> <CABkgnnXkEsQkmdgX6c4_9w6YhTaPYrtdhUEJ8imi7NSChyC32g@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Wed, 07 Feb 2018 02:23:56 -0800
Message-ID: <CAN1APdfC6Tt15Bz3ns2y8E_pB1N+cJB4Bjc-x8cB=r+HJTdKnw@mail.gmail.com>
Subject: Re: Explicit measurability in the QUIC wire image (was Re: Packet number encryption)
To: Martin Thomson <martin.thomson@gmail.com>
Cc: QUIC WG <quic@ietf.org>, "Brian Trammell (IETF)" <ietf@trammell.ch>, Kazuho Oku <kazuhooku@gmail.com>
Content-Type: multipart/alternative; boundary="f403045d914c63042c05649cb174"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/TYjvr52uODaYdAE38m53XskkShE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 07 Feb 2018 10:24:00 -0000

On 7 February 2018 at 11.10.21, Martin Thomson (martin.thomson@gmail.com)
wrote:

I looked into these when I first considered packet number encryption.

Hi Martin, I think you might be misreading the intention behind this
sequence.

The idea is to generate 1 bit for every packet sent on a specific path, in
the order the packet was sent, not to encode packet numbers directly. The
encoding of packet numbers is a separate thing whether encrypted or
otherwise.

When an observer collects these bits into words from several packets, it is
possible to compare the gathered string with the expected sequence.

The random access is only needed for analytical purposes to know about
packet loss in the network, not to operate the QUIC transport as such. If
the sequence is fixed and repeats with reasonable cycle length, it can be
done efficiently in hardware.

It is true that if you sample, say 32 bits, the mapping is not bijective so
if you match the sequence, it is ambiguous. But since you already know what
to expect next and you can choose the sample length as long as you want,
say 128 bits, you do get very good information about where loss and
reordering happened. If the sequence was not random, you would not have
this property.

As to reverse engineering, packets are already sent in order, so learning
what the original order was, is hardly a significant compromise, except if
you have multiple connections on the same tuple without transmitting an
observable connection ID.