IETF Logo Mail Archive

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

Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com> Tue, 06 February 2018 15:15 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 F293B12E76A for <quic@ietfa.amsl.com>; Tue, 6 Feb 2018 07:15:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 89OAkXGWa67Y for <quic@ietfa.amsl.com>; Tue, 6 Feb 2018 07:15:09 -0800 (PST)
Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 790721243FE for <quic@ietf.org>; Tue, 6 Feb 2018 07:15:09 -0800 (PST)
Received: by mail-io0-x235.google.com with SMTP id m11so2837937iob.2 for <quic@ietf.org>; Tue, 06 Feb 2018 07:15:09 -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=jvAVp6lR5fMHnx17StKI8f06PsJplTYNysm/Grqy4yc=; b=srSbop893nb30HpE/LoYFc3aFRzPd4ibLIoN7SUtqbbuV80dsiDnCM6sXwFCxya/Bz kf6a2lbv6xfX7M34cvxpyYXiUJ5UYjCRD7nxS8TWxzYW6rHEvrEfwoKJxXYvZhylJs3a 7TJuH6N/zfADXvWHp6GX1cqNDWCq9vE/ja/jfTomS/Hez1ZLSgyl0WH9tWi1gyZtkDP0 AHBUTg9mnVKKWpGqcg2czWqEZHzEDy8jVFIGm1rqBKaBCSwVpE7lCCSg1oChyA3bKjFy 44lUci4BBcyhgOoV5DA+hp6sPrTDYqlsOZ/wl0neO+8FMlCQYq7pxQBiKaUiYEpx2WeP xpYA==
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=jvAVp6lR5fMHnx17StKI8f06PsJplTYNysm/Grqy4yc=; b=M45WiuNdIgO8Xp80r8IlQPxVx9uZ8zAMNLazPF+Advq9E80yrGJ0qb4u8a6NzNic2V oifTUmcWyX6FxpdTkUWjsnLxJ5u/jT5A7UeAjdWlYMkOjjZqQyRWUDvz/5rRPFUjxOgS h/fpSMq7e118Jx+jdO4r4I5Bmg+QL+NY9TdbXXUqJ3ew3Fo1n2d1Z51iojtywtQ4+AYF YhB+L7QsfoCoHnTcao3ZL0eQy7Ih1k3+LcnrEgSd4xOnPxbdt3Z6GylOHZI+QehNP/Sp Ps66ldF6AAkgHVmdCn9FJQGD5R8fpaRTL4NZF34E/af7wI8C8STUegKn2NBOHZqk7iuo gYaA==
X-Gm-Message-State: APf1xPDOAtAtCvv/5CxDMzJVuh9GTcJ5A6u55Buw/HV3Npre4RLjgEHM nKeNCDy7/cNyH4F2QCTpX+7aMC8kaSQEyDYCkDSIyVIw
X-Google-Smtp-Source: AH8x227ov7lpldy4TaajibuID+ZXCasTYU9Arqo9qldgpSpQQoio/sns/fuvF6rWE4vIeLfhsge2Qlc4TFxuFzPhMqY=
X-Received: by 10.107.140.207 with SMTP id o198mr3258839iod.175.1517930108975; Tue, 06 Feb 2018 07:15:08 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 6 Feb 2018 07:15:08 -0800
From: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
In-Reply-To: <CAN1APdehS5MvNVQS-KQPjFGoLt5qJFOUK0SRm9a_NnkzLkfQLA@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> <CAN1APdehS5MvNVQS-KQPjFGoLt5qJFOUK0SRm9a_NnkzLkfQLA@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Tue, 06 Feb 2018 07:15:08 -0800
Message-ID: <CAN1APdc9iOZ+K9Si5XagJtkbP2bNqd-hWGAUL83Ay7GNmY1wXg@mail.gmail.com>
Subject: Re: Explicit measurability in the QUIC wire image (was Re: Packet number encryption)
To: "Brian Trammell (IETF)" <ietf@trammell.ch>, Kazuho Oku <kazuhooku@gmail.com>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c05a3ecf080b905648ca4f9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/iRLXcRCyT3nSHO5nfbDQA-UkU0U>
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: Tue, 06 Feb 2018 15:15:11 -0000

Or likewise, you could generate a known random sequence such as PI, or
perhaps simpler, an AES generated sequence.


Such a signal would work against privacy unless it restarts with each new
connection ID or it is keyed by connection ID.

v2.23.0 | Report a Bug | By Email