IETF Logo Mail Archive

Re: Key updates

Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com> Mon, 06 August 2018 09:44 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 02784130EB5 for <quic@ietfa.amsl.com>; Mon, 6 Aug 2018 02:44:55 -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 lVrXMZ-eroDl for <quic@ietfa.amsl.com>; Mon, 6 Aug 2018 02:44:53 -0700 (PDT)
Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (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 AC385130EB2 for <quic@ietf.org>; Mon, 6 Aug 2018 02:44:53 -0700 (PDT)
Received: by mail-it0-x230.google.com with SMTP id v71-v6so17228769itb.3 for <quic@ietf.org>; Mon, 06 Aug 2018 02:44:53 -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=LKUfUmbTKFEPRANltQ6sfkno5KbZZLM5bLgGdCAFB5Y=; b=sbdfBDS76PNzf9Z+dQy+9M3EdFQua8ZFOwxCIZi9cc+BuWUt3gyP+rafTgGc6ZaaPV 4FqQD3u1FmRnqplOFomOo0Tsg0Z1Dt1eIYXMBP/TY5iM3YsTA0JGeuNSmPMjW1mpUmQe y1uwcgtHdVDfSmLmpUQYOuWHPsfW+Y5JofVKwvaw0BZqbf+iIbhaPJQh35NKc8KnvEe4 +Ardn/JSWBTrMjb8/2Wq4Cx54oLj/5ZYie17Nay2mrEPWOAVy1kWSLQsn0mskguOi+wA F3o2x9ObmGA3WpzxXOr2HDd4Tc5KHx+pjMjJ3SfuD+5bOfD+tjJODco764LeLuh931a1 PttA==
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=LKUfUmbTKFEPRANltQ6sfkno5KbZZLM5bLgGdCAFB5Y=; b=KY4eNy1QO4MUrA5PMbSXsnvH6TWQ02kCMOelmn0VUWq2IlKBySEDeNqRWLW8djACIN hNeE2INbywczHLbjRTK8Be/SkQBoQHYiuHlCounIbwyt4j0sxlGB/27FILgdCAH8CI22 RI8hjxTgX/+KIfcJk+aqMKEbnUa0Oor5y9awpebaJAfTxHZgK2AX/NuQ5f46I38neuVZ bKv1sfeP9FVQztbWxoAf25BgGgtOmGDwB/tEIhZoTrhdus4+VeVGSBFx+pbAb2vt/gWv gAqvv/0h1L8DIUB6iQxMmatjuW4Ib34DayB5axrgWbXP6fcjIbIiKLJJTbc2uXKAIsAA p2VQ==
X-Gm-Message-State: AOUpUlFskjIUEqQpKOdJh/xX2tlDtg381bLx4hmRn6FfhL3kifIoNcO+ QOu95/lndFhkFtpxbKucsrNZyZz/AvCz+f+TOOU=
X-Google-Smtp-Source: AAOMgpe7GIfYo10wBr5fUJOHh59M0+BBhcE9pdEWOHk95A3LGUA6NrUXLSZiZ8zHFVShoFJjHmF5+jqvee6bNIeOCvY=
X-Received: by 2002:a02:8c75:: with SMTP id j50-v6mr12319836jal.76.1533548693100; Mon, 06 Aug 2018 02:44:53 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Mon, 6 Aug 2018 02:44:52 -0700
From: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
In-Reply-To: <CAN1APdc7-CwG1bDv-YdbXvaOu2YwrgVa7+cukf_vmoRv58AfKg@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> <CAN1APdc7-CwG1bDv-YdbXvaOu2YwrgVa7+cukf_vmoRv58AfKg@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Mon, 06 Aug 2018 02:44:52 -0700
Message-ID: <CAN1APdeXa_zrEnjkP9YwESNq6QmiX5=axwZ-7S8h092EgWZm=g@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="000000000000191db20572c121be"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/m0d03UflXrx4aDWkQ5xPNxq8P3E>
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:44:55 -0000

This is definitely an option I have considered. If you have a workable
design, I would be interested. I couldn't reconcile the desired rates of
updates. Connection IDs are needed in spikes, where the rate for key
updates is more measured.

I believe the current consensus is to have an ordered set of connections
ID’s. If that were not the case, or if there were two sets, then some
connection ID’s could be associated with a key update. If running out of
key update ID’s, a new such ID would be requested. This is somewhat similar
to the commit based option.

v2.46.0 | Report a Bug | By Email | System Status