Re: Getting to a First Implementation Draft

Eric Rescorla <ekr@rtfm.com> Sat, 13 May 2017 18:57 UTC

Return-Path: <ekr@rtfm.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 01DF112ACAF for <quic@ietfa.amsl.com>; Sat, 13 May 2017 11:57:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 tZIXMoUHF8uC for <quic@ietfa.amsl.com>; Sat, 13 May 2017 11:57:50 -0700 (PDT)
Received: from mail-yb0-x22f.google.com (mail-yb0-x22f.google.com [IPv6:2607:f8b0:4002:c09::22f]) (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 0203A127863 for <quic@ietf.org>; Sat, 13 May 2017 11:55:12 -0700 (PDT)
Received: by mail-yb0-x22f.google.com with SMTP id p143so20262594yba.2 for <quic@ietf.org>; Sat, 13 May 2017 11:55:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=AboHTht1uDyXTSQn3tW64ZWyYsScWcVSIxGFpIlUTKY=; b=PqUFR+7DCg9etuwe6KmKCALN6ikfL95gYGdDqr7ys8WOvUC8YIr8gwTr2UHAkffUTn ppV7J9fsVNJh3pK/mcjsTWkcmIV/LO+MFrB4kjC1agQ2qf6bez+7UMIX2OQqT54T3Onr iO8V9xePxGa54dQ3kdkZDiMUjivuRGWrxJN+0dWPLrMpC4J6zyz34mp76ybVUDSDFH+q F8SmaESZsinjP6JDwZlSumcHttI/Pb1I9H6XDGNJRImbjJnIUjhh/zPgn5MaV9hD2w5E bp6i+6gxsFj3q/ortKcJ7/CDnZnwtAAk/dnE/4oURYOzYdk2WhOhMlXMeTiJG9zGvCa0 0UqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=AboHTht1uDyXTSQn3tW64ZWyYsScWcVSIxGFpIlUTKY=; b=lmzQovU4vAhAClAkzfCPZZqR2h+f4ZxOKfKgb28RQf1RyyFvT5Wh7rn8imdbYoZpIp T3kfverEaZHhRFP8K1d12mR7/wfo2yYkA0O4bzIUnqhVQKan7JSH7da4Cp8WEpGc0Bek WZJIXdjS3/EnGYrwmYyJkUNXsTDFXU+iWCXZUghyp3wyeMlMwMj8GB2YxzkHHcmv9vAr Ds6xDi4UOspoVCDwBJ1P4IuDDLjHvz+I+Wo02Aiy93F1RD0QNsW+n7bFn06T1wZ5Ks9r gbMchXzjEeLJJPyBniIggqbPYd2J1BlxuHBE4kH/7K9WB00EFaf4dprKerlChkm9ha5o zDpw==
X-Gm-Message-State: AODbwcAdK8HkcRl0TKgUY8MBk+VHu4PF8n8uYU3X2lLE72pXiGyAO6gp RnZm80/7Rm33msIQmd8Ao00L7G1GgI6vlKs=
X-Received: by 10.37.41.130 with SMTP id p124mr8641963ybp.24.1494701711127; Sat, 13 May 2017 11:55:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.131.150 with HTTP; Sat, 13 May 2017 11:54:30 -0700 (PDT)
In-Reply-To: <20DB6018-3E7B-454F-8BEC-0F839D949AFE@mnot.net>
References: <20DB6018-3E7B-454F-8BEC-0F839D949AFE@mnot.net>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 13 May 2017 11:54:30 -0700
Message-ID: <CABcZeBNqYE3e0M-zV-AWt33Q6vduXk5rgsvwXHVZLrXBU4XK=Q@mail.gmail.com>
Subject: Re: Getting to a First Implementation Draft
To: Mark Nottingham <mnot@mnot.net>
Cc: IETF QUIC WG <quic@ietf.org>, Lars Eggert <lars@netapp.com>
Content-Type: multipart/alternative; boundary="94eb2c14d834898b6a054f6c5cd7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/pP_3xhleRtiR4g-G3qXp0hCNiLU>
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: Sat, 13 May 2017 18:57:52 -0000

A few comments on this proposed list:

> Integration with TLS 1.3 handshake - The basic 1-RTT mode must be
> supported. TLS exporters are not needed, nor are session
> tickets. Basic key exchange is sufficient and implementations can
> use any certificate. All MTI algorithms listed in TLS 1.3 are
> expected.

I note that this and the transport parameters and HRR stuff below
necessitate the generic changes to the TLS library to permit adding
extra extensions. I wonder if it might make life better to just have a
canned set of parameters for now. It's not that it's a lot of work,
it's just that it's not critical path otherwise.


> Packet protection - All post handshake packets must be sent with
> 1RTT keys and packet protection.

This is inconsistent with not requiring exporters above. As far
as I can tell, if you're not doing NST, you don't need post-handshake
packets anyway here, so you can probably skip this.



On Wed, May 10, 2017 at 9:53 PM, Mark Nottingham <mnot@mnot.net> wrote:

> Previously, we've mentioned an intention to have a First Implementation
> Draft -- that is, an Internet-Draft that we feel is suitable for
> implementers to write code to, for the purposes of interoperability testing
> and gathering feedback -- shortly after the Paris interim.
>
> Due to the size and complexity of HTTP-over-QUIC, implementing all four
> drafts for this purpose on a reasonable timeline isn't workable.
>
> Instead, the editors have identified a subset of functionality that they
> believe will serve as a suitable starting point. See:
>   https://github.com/quicwg/base-drafts/wiki/First-Implementation-Draft
>
> They've also identified the set of issues that we believe will be
> necessary to have proposals for before Paris; see:
>   https://github.com/quicwg/base-drafts/milestone/1
>
> If all goes well, the plan is to have a set of drafts out (very) soon that
> do so; then, we can discuss them and the First Implementation Draft
> Candidate in the lead-up to and during the Paris interim.
>
> After Paris, we'll make any necessary adjustments to the documents and
> publish another set, which will be the First Implementation Draft.
>
> Please comment / raise concerns / make suggestions on-list.
>
> Regards,
>
> --
> Mark Nottingham   https://www.mnot.net/
>
>