IETF Logo Mail Archive

Re: Key updates

Martin Thomson <martin.thomson@gmail.com> Tue, 07 August 2018 00:39 UTC

Return-Path: <martin.thomson@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 5287F130E53 for <quic@ietfa.amsl.com>; Mon, 6 Aug 2018 17:39:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=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 oD3aKZIhDsRT for <quic@ietfa.amsl.com>; Mon, 6 Aug 2018 17:39:35 -0700 (PDT)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (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 DF2ED130E60 for <quic@ietf.org>; Mon, 6 Aug 2018 17:39:34 -0700 (PDT)
Received: by mail-oi0-x22e.google.com with SMTP id v8-v6so25490840oie.5 for <quic@ietf.org>; Mon, 06 Aug 2018 17:39:34 -0700 (PDT)
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=wtlsPD0521nq8YQu1i1c3OYqB0n7m2k2oQUz92I4lfc=; b=ld7yG8evMNKWrK4Fhfj1wnFOgx7GbMJn7OWb9psVyLyb6qSPckA0Mh6NGoeBcJZjcI +Fjn7LMPP8z32WK4cBHwau4C82WdGeETsEE/NeJO4YyBza5aCs/GZGTr0HrwY6uTg2/+ DWlQDsj2qNhwCTe09cq18o4yv0qu+ph8S5YdHk36lPqFdBm96wqUnMcGfgV6hgPrfcFF ZqNnmp6va5LaOfRQ5ukBt0W++wK769oLFxtwuKLaPQa12mfPasm4hkoSpGJPd2DHEWgR Q8vBrQ3qEvtN/CgDkzs5SHwyENHrrHY35/82uTVj6BC2pw9SFSZh/rFT/+31wIGeNNdF l+8Q==
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=wtlsPD0521nq8YQu1i1c3OYqB0n7m2k2oQUz92I4lfc=; b=RAagY+G5xcwx4VwDqI6lS4aExvwyXARMauBwmQSx5OwbhzrQYiGfPIywnVichK7b4v mAVe88tTji3RnieQUGYDzaDf8mlNA7DyJ6Z4LLmrwBKO8b45cPd0C751doUiX3bURxU/ c6iNLdY/y2LoNLqiZbN1jJzj38WYxTnY1KkhFKCfjA7RpEKCYflYKUujq0eOWmO3jwvt Bs8CGgpICw7l/BqPU8ULWYToJsSEmJNbg+USySVulJcsIWzzaAL3fscD/02OQC228EoX m9lPNfYI34q6z8hWoZemAUhSA/yNoz5CJ7e3SL179zkHFuKSRQkSyR2t4WwG0gRtOz7o svIA==
X-Gm-Message-State: AOUpUlFuFpfbpuVEKYLIVNIM+I72kJwqP9nvZxlFmzXRfetvLnP0LeV8 HU6vs4lZLlGGqnLlUM3p9xCdcdKm9/kbD4re90I0VBi2
X-Google-Smtp-Source: AA+uWPzn+/Hx1ftCkNN5EqmvMPcwdT5g4DqxD9mORTkknaQjnSpgOkExK/7xdRHR2azbgycgBahxa4bfcUBcWGWJNLM=
X-Received: by 2002:aca:a8c1:: with SMTP id r184-v6mr17817863oie.215.1533602374123; Mon, 06 Aug 2018 17:39:34 -0700 (PDT)
MIME-Version: 1.0
References: <CABkgnnW9-Jn1CH0rSwbtDmMrOZ+jstugVsOpWtShDJgT_KSyOw@mail.gmail.com> <CAKcm_gPXFXZc4ysm7ugG0T8GTWjgcO9hvO6ATj0MRiEufie=bQ@mail.gmail.com> <193166ED-C8C3-4A6B-9483-5546C34B5BDA@tik.ee.ethz.ch>
In-Reply-To: <193166ED-C8C3-4A6B-9483-5546C34B5BDA@tik.ee.ethz.ch>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 07 Aug 2018 10:39:23 +1000
Message-ID: <CABkgnnW1VhCKc+SDTGLJ0Q4BZZz9jJLmv3nOPrGTWWJe-dHTvg@mail.gmail.com>
Subject: Re: Key updates
To: Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/CGVDzk8UdH3f_kF2-rHTcU5e6ko>
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: Tue, 07 Aug 2018 00:39:36 -0000

On Mon, Aug 6, 2018 at 11:06 PM Mirja Kühlewind
<mirja.kuehlewind@tik.ee.ethz.ch> wrote:
> However, this brings us back to Martin’s other question: does it make sense to have a couple of reserved bits to make it easy to add a bit for the next version with minimal changes to the protocol machinery/wire image?

I think that was Dirkjan who asked that question.

The driving principle behind defining invariants was to avoid having
to come back to this question repeatedly.  We have a version
negotiation mechanism that allows us to change an awful lot between
different protocol version.  We don't need to reserve a few bits
because most of them are already reserved.

v2.23.0 | Report a Bug | By Email