Re: QUIC ossification

David Schinazi <dschinazi.ietf@gmail.com> Fri, 15 February 2019 01:09 UTC

Return-Path: <dschinazi.ietf@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 DD8E4130E1C for <quic@ietfa.amsl.com>; Thu, 14 Feb 2019 17:09:42 -0800 (PST)
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, 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 4I0Pr8uEW7Nx for <quic@ietfa.amsl.com>; Thu, 14 Feb 2019 17:09:41 -0800 (PST)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (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 0D8F2130DFA for <quic@ietf.org>; Thu, 14 Feb 2019 17:09:41 -0800 (PST)
Received: by mail-pg1-x532.google.com with SMTP id w7so3949057pgp.13 for <quic@ietf.org>; Thu, 14 Feb 2019 17:09:41 -0800 (PST)
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; bh=8n+0ABs1lhD0jUUbni7XeMibQHtECejkGONYb33sZKs=; b=MyTOBBrMGXmndZGreQk0SMJmRJcwXGB4RjL8AhVP72oeI6X2DuyX9MqmSmY/MLTcZ+ za6hPlg654YCg4QsnvEil77d/kCBT0HPc/uX0h/SKCOUY81zQU+bFiA0TwljALvizpD9 4LpVKvnrZfCZKPkFl6FuEs1+Z7zVqMKK5G49Wjbs1+ixEj3nvL3HqaP+zkR0j5L0HkuQ l7dIVRfOjjvd9JzYo2DaHkUfPqvUpqymOQsAeTuIvpmTZZpULC+x2ioaznmdwCHguHil 5RsP45yP76ONSslwluV7fqZCMKyWzPJhJhAkxb6fzYJtAZZDiRzgSspMsQMKhZB8lKKm Agtw==
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; bh=8n+0ABs1lhD0jUUbni7XeMibQHtECejkGONYb33sZKs=; b=iwYDs6+Qv4zcM8pH2WEisgx/TxJH5HhSX5ZY0Dz6GdhZv8JduP0BBo6hW2XIj6k/rX lPTaYIoNRwOPpzSMkSy6WysHe/JkV3B9ZYZN36AHgoILsHaE7AZh2TPBNa6mBZnV/Mez 7wyI1+ksgUFwBzOmB6TYbFmvvtVuGUX86d4A12gsxmYKOp4sAYoalGEOR3CgZkXrxK7H dw0297HmFGpmXi+7zZSQhD0etb8EzUHd2ErpgQAlAIdFe5sgSftZBVaepXeSPB2bI9w7 IiCystQhnS9VWiA2CktNiwdVHo+JTUtUs/4rxBBwQouaRL1/slUdmpgqPqDOua5shOrP HDpw==
X-Gm-Message-State: AHQUAuYpLIo/k0Yy5hKkIXwqfp6eZYcveYbo1A6y+rGW2ludTjBTJSuv 6VBJgcdIOsj+1z4hMT3zOgKSrVOKmFo8u6fLkyk=
X-Google-Smtp-Source: AHgI3IaW6JDYG2S91QNc9bdpdwjSQCUcFklC6gxizg4az6sGXsTa1ki1kxJIJj39/1TFPure3e3q27PC6BAvf4nnTlo=
X-Received: by 2002:a62:ee0e:: with SMTP id e14mr7095378pfi.201.1550192980272; Thu, 14 Feb 2019 17:09:40 -0800 (PST)
MIME-Version: 1.0
References: <CAM4esxTm0GiXnow4Vyv0UX6kFW4U3zJgVrN_JzD31Sm6sxoYGg@mail.gmail.com> <1550007332.441557.1656692832.0E5412AE@webmail.messagingengine.com> <9425344B-D72F-474D-A549-AA2453E57F19@fb.com> <CAPDSy+5LikoojquLhaW58DbJ3VrGXUViaD0aHcTkxBJGzFjgQA@mail.gmail.com> <47E7A834-B6CD-4D73-BF49-8768A48CADF0@fb.com> <CAM4esxThzPJUxU7R5-CY-ZcgmqhYdPFMoM5Fg17vN-Hsk_pJ8A@mail.gmail.com> <CAKcm_gMmxeHHN3dtH9kby_En96oPwTqrfHE=wpqy5Z0YbX4png@mail.gmail.com> <CAN1APdegy8n3+8J-pkgB6f-SNxHtju9p1Hiyct2tHWQ0KyeiGg@mail.gmail.com> <CA+9kkMC95TnFatowKU6121g+1DPy1hMNbKPagveMfKCXtpFSUQ@mail.gmail.com> <5B7F7D53-546D-4E3F-A0FC-AC29B1B05742@huitema.net> <CAKKJt-cQm+D2vptcfCLywz_QmuZW8tMYgcxNLoxyfC67OvYPUw@mail.gmail.com> <271E52ED-FA3A-4B4D-978C-90CE5CE57053@fb.com> <CAKKJt-f4U15Nr316xjuPb2S0QYOO6YAi9HRZzLWaZVfyXT3s8A@mail.gmail.com> <6b503e6a-d9ed-e747-9db6-f943f92fe114@huitema.net> <CACpbDcdixBEBFnLNbN1OhiKv9iTGjCpT3LQH13Rd64x1N0sJsA@mail.gmail.com> <CAM4esxTRsj7WqOSiCKfhQu2CfEosC+1-wJcm9uS1ryjchtpxdA@mail.gmail.com> <CAM4esxSqOAHEXXgAYP3iHyb-mkScrkXg1e5Dx+zA=Bi=yAcnQg@mail.gmail.com> <1550117350.927768.1657684024.116377B8@webmail.messagingengine.com> <CACpbDceGpp2Vs1pztJB3o7CJqg2f4HbL2mOoJtEPPeL7CvbXsA@mail.gmail.com> <1550120918.954942.1657706568.2C59A22F@webmail.messagingengine.com> <DB6PR10MB1766CDECAEED8E8391F61CD4AC670@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <CAF8qwaD8TKN251Ru5Q0G+NH9osyVw8MqWY5g+7VvLkzQph6jOQ@mail.gmail.com> <MWHPR22MB09916CC98D4AB60AA6A185BEDA670@MWHPR22MB0991.namprd22.prod.outlook.com> <CAPDSy+4=+Kpx0AD-xOuGJJec2T-MoFX9GOgfKWFPOPkj8D1MBg@mail.gmail.com> <CAM4esxSem6kkcd3rE7qfHJD9A1urmssoVsnagEmtJn7MU=mo5g@mail.gmail.com> <65405c4c-9bf7-4dca-91a3-d4a650ecfeb0@www.fastmail.com>
In-Reply-To: <65405c4c-9bf7-4dca-91a3-d4a650ecfeb0@www.fastmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Thu, 14 Feb 2019 17:09:28 -0800
Message-ID: <CAPDSy+4=HzVzm2zVpyt+Fuf4NQq_qyZXy6Ga==rBMnebsSyPpA@mail.gmail.com>
Subject: Re: QUIC ossification
To: Martin Thomson <mt@lowentropy.net>
Cc: quic@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ec2a3c0581e46d1c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/P4owHg8m5yoa2P3cv8pnZ9A0hqY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 15 Feb 2019 01:09:43 -0000

One potential change to v1 that has come out of this discussion is that we
could change the 32bit version number from 0x00000001 to a value randomly
generated at RFC publication time.


On Thu, Feb 14, 2019 at 17:04 Martin Thomson <mt@lowentropy.net> wrote:

> On Fri, Feb 15, 2019, at 12:02, Martin Duke wrote:
> > Collective, time for me to file a github issue? Or leave it on the list?
>
> What do you believe the issue would be?  Because a lot of the discussion
> here has been very much "quicv2" territory.
>
>