IETF Logo Mail Archive

Re: Review of draft-ietf-quic-transport-10, and a proposal for a human-friendly QUIC version numbering

Christian Huitema <huitema@huitema.net> Mon, 09 April 2018 16:43 UTC

Return-Path: <huitema@huitema.net>
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 662A212D77A for <quic@ietfa.amsl.com>; Mon, 9 Apr 2018 09:43:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.701
X-Spam-Level:
X-Spam-Status: No, score=-0.701 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 jBUshUtGDLDT for <quic@ietfa.amsl.com>; Mon, 9 Apr 2018 09:43:52 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3768012D777 for <quic@ietf.org>; Mon, 9 Apr 2018 09:43:52 -0700 (PDT)
Received: from xsmtp31.mail2web.com ([168.144.250.234] helo=xsmtp11.mail2web.com) by mx60.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1f5ZtU-000FlW-3D for quic@ietf.org; Mon, 09 Apr 2018 18:43:50 +0200
Received: from [10.5.2.13] (helo=xmail03.myhosting.com) by xsmtp11.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1f5ZtQ-0001rt-JR for quic@ietf.org; Mon, 09 Apr 2018 12:43:45 -0400
Received: (qmail 21677 invoked from network); 9 Apr 2018 16:43:40 -0000
Received: from unknown (HELO [192.168.1.105]) (Authenticated-user:_huitema@huitema.net@[172.56.42.61]) (envelope-sender <huitema@huitema.net>) by xmail03.myhosting.com (qmail-ldap-1.03) with ESMTPA for <martin.thomson@gmail.com>; 9 Apr 2018 16:43:40 -0000
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Christian Huitema <huitema@huitema.net>
X-Mailer: iPhone Mail (15D100)
In-Reply-To: <20180409112405.ba37t74psgw8840w@webmail.eurecom.fr>
Date: Mon, 09 Apr 2018 09:43:38 -0700
Cc: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>, Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>, Lucas Pardue <lucas.pardue@bbc.co.uk>, Martin Thomson <martin.thomson@gmail.com>, Jana Iyengar <jri.ietf@gmail.com>, QUIC WG <quic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <20ED4DA3-F688-42BE-ABD8-FDC97FC1D26D@huitema.net>
References: <20180408200158.kuekyw4nk8ks4kkw@webmail.eurecom.fr> <CABkgnnXWcshxAE8F7+TuMNG+zSD620ZLwk=b1a=QdkSfQ+20AQ@mail.gmail.com> <0c2bbb1f-af3c-e196-3605-db9458936a42@it.aoyama.ac.jp> <20180409090233.hxlqgu1wqo0o04c0@webmail.eurecom.fr> <CABkgnnWha2_dHpo=Lj=4dMmDbLHjfqN4eMyiMBKfM5bMeVtf6w@mail.gmail.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB22349@bgb01xud1012> <CAN1APdemJR5Ut42Ars+L0RQAEeSszQS0=1-dJ7pqsw6+WjDxZw@mail.gmail.com> <20180409104208.qwe4ab3s8woowgsc@webmail.eurecom.fr> <49c3e44b-4e61-b2d8-0059-ab4310bd474a@it.aoyama.ac.jp> <20180409112405.ba37t74psgw8840w@webmail.eurecom.fr>
To: Ariel Otilibili Anieli <otilibil@eurecom.fr>
Subject: Re: Review of draft-ietf-quic-transport-10, and a proposal for a human-friendly QUIC version numbering
X-Originating-IP: 168.144.250.234
X-AntiSpamCloud-Domain: xsmtpout.mail2web.com
X-AntiSpamCloud-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-AntiSpamCloud-Outgoing-Class: unsure
X-AntiSpamCloud-Outgoing-Evidence: Combined (0.18)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5hyqkp4a8DvguduhhF4ZeJN602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO37pNwwF1lRXh5rzvPzo9Jts1ujulqUFmMITHM77eiVio1HEuyN83VD1ujmZV0zqCs7i TvJ2/ZGzVWB9scFAaCdIFaUvXN+CI+RGy3Me16pB6b6XZpNC1wnpsGpZepb/px/TBCf6oYXAWGet lavcAjD9ytQxIHf9lN5jjLJaPK8lRJSPf/SXbEnDSsal/zZzc4n9VZdr7RAFD5mRwooUYhwMPaBP aKeQW+/QlaOdv8isl/qMm08Zpim2AHUKEWvQ6G/bWfgucjnNmABpGhD9TTttrFCuZ0NkwnSz2Luu o1u9uevuNfM1HjkNEFwape+IgNezYqxGMqsKjARq8PBC4qjpVMhqNcdjhoIlgrKzBvjTmdySlZou 9qHIGOZDEEo7Oyc1nq0gsY582CWqKjiRB3ukywmZtiDkyd4mEBjJGGEJgawbllbHk+xyUKopM6rc KCaQX/lIXcRWtobViGg9fpX8nIu6prlMU9qLY4Lxa6TDEUDpzUh97nbRBafHFU0M5cJ9Mzv+g54q kQltgJYTLEiO98fck6astPPFccqiLCixm7xl+RQ3vIZqfBpLwZArl3I1g+tBSv0B+cgW7VoPEiDI +8QkA7WZKXURE/tHtZ/u0KOJrIKT6Yz+kw/sINDgmVhNqyux1yaQvYroLJ1yFFq84+OHMz/cWp3h cOTrnvEhQZs4iXA/pTuddAL2KCGOjKaoYeoLX/yEBEWAApw66Tq3t9PKqfIkYUDuwnGn3d4uZhUF HKbUZMv7c3cOU/0VErE2BJ6+Ocmt1JPBpwCeIwTbMcctPzMPLiqwr8e+aie3zxvdN0leIxaNIjs7 cbPZdZnckpWaLvahyBjmQxBKOztcoEJy5JI/WnEUTEvEJGtKRioNM4YdAO5dQww9T9HjAWtJl6pO HngTL5HKgxzCo5M=
X-Report-Abuse-To: spam@quarantine6.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/4d4mtj9m942x6iibtiIgEr2PnvE>
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: Mon, 09 Apr 2018 16:43:54 -0000

I would drop the part about past backronym. If you repeat it, you perpetuate it. If you want history, you have to explain the lineage from FAST    to QUIC, and an RFC is not the place to do that.

-- Christian Huitema 

> On Apr 9, 2018, at 2:24 AM, Ariel Otilibili Anieli <otilibil@eurecom.fr> wrote:
> 
> Hi all,
> 
> Inline the pull request I will propose in the Introduction. Does everyone agree with it?
> 
> Regards,
> Ariel
> 
> Quoting "Martin J. Dürst" <duerst@it.aoyama.ac.jp>:
> 
>>> On 2018/04/09 17:42, Ariel Otilibili Anieli wrote:
>>> 
>>> I will propose a pull request: "QUIC used to be known as 'Quick UDP  Internet Connections', but the present RFC advises it be used no  more: QUIC does not stand for an acronym".
>> 
>> "QUIC does not stand for an acronym" -> "QUIC is not an acronym" and/or
>> "QUIC does not stand for anything".
> Fixed: "QUIC is not an acronym: it does not stand for anything."
>> 
>> Regards,   Martin.
> 
> 
> 
> -------------------------------------------------------------------------------
> This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
>

v2.23.0 | Report a Bug | By Email