Re: Key updates

Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com> Mon, 06 August 2018 09:39 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 5FCF6130EB8 for <quic@ietfa.amsl.com>; Mon, 6 Aug 2018 02:39:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_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 d8Io_NvEeR9y for <quic@ietfa.amsl.com>; Mon, 6 Aug 2018 02:39:25 -0700 (PDT)
Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (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 8BB90130EB4 for <quic@ietf.org>; Mon, 6 Aug 2018 02:39:24 -0700 (PDT)
Received: by mail-it0-x22a.google.com with SMTP id h23-v6so17181199ita.5 for <quic@ietf.org>; Mon, 06 Aug 2018 02:39:24 -0700 (PDT)
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=am2o/0Aaomsi3znF6ZsM+0NFtysbarjLKpDIEOML60s=; b=FxXfcaZG83umIUb3TQUjwHbzHHdcZFHX93QDGM3dLN35KZrr9Z3EJwn1bVRHoa4VL8 VoNA5k5lohDk8Pv73yXCoLSny+n/J45jBnRWDyB9u/SSrvEXFYWIlZ2sHqeR6CeC/2C2 CGhUtcirSg+ANhFLqieLpLOwGtNuLvh6YZEvRgNxbfipko5+lFAvxKWxZrtcreK6gssI Teq4SDhUXHNUT9vUhfTjZSWqLWgh2yygyjDmR8UrJfX7ykHsMYga6xnHhPQN/Ez/6sOU XKb+Y5BEZa1wd4hHQ8c+wPW7KqkzIfoImpnlQOmGGYw8ICE19b83BJnSSMKGFkPKXRqD d2dA==
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=am2o/0Aaomsi3znF6ZsM+0NFtysbarjLKpDIEOML60s=; b=niOQR+jmUNVoFVM0O4GT7MICmGfVriooaFBhfsOJLTyXrYcQBDaeKYBoc4Hcxi8waA oZ0EG4Luw4JoivOQLDAt7e5hVur1htGFKjNRsmjLnLIXrvY8Er/FRr9pCTLxhAtlzJHI xvjLP7EdbTTjGFwgIsDOZkpum1v9eWsS5qC+YU32VSitm0GkIQttCmvdFOFpUb/Gl1tZ kFUGueht4pQ/aCE1uN4Xh1eVK+XZj5vlLaUEFPIyu95180KpcQ8AtiYjx+A/Rq0dL4UQ jq49AcMhAt1SrYj9mEf8Vtg/gxvTF8FZMbVoHTA51VUuxVKEODTsJxl3N2ac6nzJqGF6 1W1Q==
X-Gm-Message-State: AOUpUlFPuPmS4kRFx8pCUKZhlrvRp1gQKWH9/wfOdceEPATJABTSGhbX T40cJM923rWF9m117ZTCek7tNjzoZ9g5jdtN8SgMGw==
X-Google-Smtp-Source: AAOMgpf7WBrJXi0oVZt+2UDrZkCziVuwjltRVCNHsKnm5OsaqLKWKMM3SwfspOJYArCwcQhhfKX8uuzspXZc8/5orKQ=
X-Received: by 2002:a24:5e0b:: with SMTP id h11-v6mr14598684itb.80.1533548363909; Mon, 06 Aug 2018 02:39:23 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Mon, 6 Aug 2018 02:39:23 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <CABkgnnWQRqum83WXE0+wO5=f2x5dY9E0J14R=vb3rCtH7_+J=g@mail.gmail.com>
References: <CABkgnnW9-Jn1CH0rSwbtDmMrOZ+jstugVsOpWtShDJgT_KSyOw@mail.gmail.com> <CAN1APddA3f3t76aoW3Z06ng-5usadf5u9qeqnWT0hRxv6SqH2Q@mail.gmail.com> <CABkgnnWQRqum83WXE0+wO5=f2x5dY9E0J14R=vb3rCtH7_+J=g@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Mon, 6 Aug 2018 02:39:23 -0700
Message-ID: <CAN1APdc7-CwG1bDv-YdbXvaOu2YwrgVa7+cukf_vmoRv58AfKg@mail.gmail.com>
Subject: Re: Key updates
To: Martin Thomson <martin.thomson@gmail.com>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007a0e0d0572c10de3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7Qexl4a_7kAK7OT1WHp7TP_Cdbw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.27
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, 06 Aug 2018 09:39:28 -0000

The size of a packet number is hidden. Given that most packets are full
sized, the only effect on those would be less available space for payload.
ACK packets would increase in size by a couple of octets, which could be
masked easily and cheaply if necessary.

I’d challenge that, especially in the cases where it matters most: long
running mobility applications. For example a car management system that
uploads battery and other operational statistics, geofencing applications,
or chat applications used by train commuters.