Re: [C430] RFC 9000: Re: [IANA #1196209] Protocol Action: 'QUIC: A UDP-Based Multiplexed and Secure Transport' to Proposed Standard (draft-ietf-quic-transport-34.txt)
"Martin Thomson" <mt@lowentropy.net> Mon, 03 May 2021 23:12 UTC
Return-Path: <mt@lowentropy.net>
X-Original-To: c430@rfc-editor.org
Delivered-To: c430@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id B346FF407DF for <c430@rfc-editor.org>; Mon, 3 May 2021 16:12:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Spam-Flag: NO
X-Spam-Score: -100.68
X-Spam-Level:
X-Spam-Status: No, score=-100.68 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=0.01, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=0.01, SPF_PASS=-0.001, SUBJECT_IN_WHITELIST=-100, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=AqZ7wF22; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=n2z+XUNv
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NcRaRLdjpp4b for <c430@rfc-editor.org>; Mon, 3 May 2021 16:12:51 -0700 (PDT)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) by rfc-editor.org (Postfix) with ESMTPS id 04BF3F407DC for <c430@rfc-editor.org>; Mon, 3 May 2021 16:12:50 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id EEBB01844; Mon, 3 May 2021 19:13:04 -0400 (EDT)
Received: from imap10 ([10.202.2.60]) by compute1.internal (MEProxy); Mon, 03 May 2021 19:13:05 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm2; bh=4Ad0TfkheVmJ2xLaoaws0tVECvgjMLg zjgiPUB5w1B0=; b=AqZ7wF22nbm4W8T71KfvQJyhVIgVE89qWfbWFkay3CUz4fU q3K39N2szZ4ldais+HIo8xFxUrTuz5+7oSfLH8m54mnt4UAHorQMy1IcxqLl/55A 5g92ZnjFDe6NoruXWfl7ZgxNQFg6/VqRVd58rIw/HWU6kbhNdUCco0WQbw0Q7YcQ ipZnT0hS3lil8Uh9HOzZ8mm/wU5jCkgZpMmSPFAMxen2qJVxu6aHidi/SrxhOnKq 0A+hVCLtubba9Vvk/h3zB7nsuIeCtPSI/fv9dHypgIhZu99qnjGMBVr9txJKa8wU MxFcF5YcN4NTeDa5is47inCk1CleCHjuYl9NSDw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=4Ad0Tf kheVmJ2xLaoaws0tVECvgjMLgzjgiPUB5w1B0=; b=n2z+XUNvaDoOoeNnbCY2/w /4c4kmx8SVSOmdB2KkRjCHaCiuuLTs/a9H65/5fFK9jeazYAc5bmk9PKJo67g0+F ibdskrhz0XNy3J+/fccFgbRTfFVlMDmsqBEfiuCIa4R//dn/9GZrQ80SgG6E7RFp odHVt6wewURg57nR9qr1O8ylHaklbayJZd91jYdcP+1nuN4JJRucdIiamcdLMLnd RBbUSt8XWIEtI/c1yQ3/VbYFEVLRPzEkqXYYIMvfiZ9AihcwuRpCexsnajDw6OaE ryoWf/2z+7lq3uXKcMcVEiyB/f4yynG+js3fO8iIkvimXONNQwgQoHfaM2thCPcg ==
X-ME-Sender: <xms:f4OQYIrbGyNXRJV4wdS1N7w9RE_ryPpDNX1y_EYRj9GxYsPGT9VRDg> <xme:f4OQYOqRSFEWh9kbRpEG90ImAtOKtm7bf7aIZGPG_Ax3lLC35v1Oc7mnxZ5RMzGT6 7Ny7BFWMtooF0oxV5Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvdefhedgudelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreerjeenucfhrhhomhepfdforghr thhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnthhrohhphidrnhgvtheqnecugg ftrfgrthhtvghrnhepieeitdffkeekvddvffegfeelheffieegkefhveeuiefhffduueef heevgfelhfdunecuffhomhgrihhnpehgihhthhhusgdrtghomhdpihgvthhfrdhorhhgpd hirghnrgdrohhrghdprhhftgdqvgguihhtohhrrdhorhhgnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnh gvth
X-ME-Proxy: <xmx:f4OQYNO0FjZPaBgCFz2A-QoFdREqHw5mWsPf7ZVBMoBjjhZ75ciGMQ> <xmx:f4OQYP77h19J89sClcwv1xXxRLlathzcBo_vCat8qj8WHowOtRq_Pg> <xmx:f4OQYH5DuKe4k69ulhq0N_A9M_JUl7cLRRR5g64nUAWJ258xcmENLg> <xmx:gIOQYAVYkWlKoHetsNjBeRx67sklOBhc2d0v7yK-Im7bq2hYRVOjzA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 85CCD4E0178; Mon, 3 May 2021 19:13:03 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-403-gbc3c488b23-fm-20210419.005-gbc3c488b
Mime-Version: 1.0
Message-Id: <d148ddeb-15fc-46e1-aed4-35eeb53eaaaa@www.fastmail.com>
In-Reply-To: <028FC7D9-644A-4703-B7B5-033B7A65D5C3@amsl.com>
References: <RT-Ticket-1196209@icann.org> <RT-Ticket-1188362@icann.org> <161237263486.16375.16046346962390939039@ietfa.amsl.com> <rt-4.4.3-2459-1613104363-271.1188362-37-0@icann.org> <7357872F-30B2-47F5-BCF4-958913894591@amsl.com> <rt-4.4.3-12070-1619736994-848.1196209-37-0@icann.org> <F2DF8B2F-8FDE-498A-B25A-13293327412A@amsl.com> <028FC7D9-644A-4703-B7B5-033B7A65D5C3@amsl.com>
Date: Tue, 04 May 2021 09:12:43 +1000
From: Martin Thomson <mt@lowentropy.net>
To: C430 <c430@rfc-editor.org>, Sandy Ginoza <sginoza@amsl.com>
Content-Type: text/plain
Subject: Re: [C430] RFC 9000: Re: [IANA #1196209] Protocol Action: 'QUIC: A UDP-Based Multiplexed and Secure Transport' to Proposed Standard (draft-ietf-quic-transport-34.txt)
X-BeenThere: c430@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <c430.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/c430>, <mailto:c430-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/c430/>
List-Post: <mailto:c430@rfc-editor.org>
List-Help: <mailto:c430-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/c430>, <mailto:c430-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Mon, 03 May 2021 23:12:55 -0000
Hi Sandy, On Tue, May 4, 2021, at 06:35, Sandy Ginoza via C430 wrote: > >> It does look like 0x100-0x1FF (or possibly 0x0100-0x01FF, or 0x01xx; I think that for the HTTP/3 document they wanted padding to the byte?) does need to be recorded in the registry in some form. How would they want this entry filled in? I can't believe we missed these. I think that a range is easier to understand and is consistent with our other tables and registries. And the leading zero convention is good. So 0x0100-0x01ff but lowercase. I have prepared a change to the drafts: https://github.com/quicwg/base-drafts/pull/4885 Cheers, Martin > >>> Also, would you please update the capitalization of the description to > >>> match what appears in the I-D and the other items in the registry: > >>> > >>> https://www.ietf.org/archive/id/draft-ietf-quic-transport- > >>> 34.html#iana-error-table <https://www.ietf.org/archive/id/draft-ietf- > >>> quic-transport-34.html#iana-error-table> > >>> > >>> > >>> IANA: > >>> 0x00 NO_ERROR no error > >>> > >>> > >>> Current doc (caps was used in the original I-D): > >>> 0x00 NO_ERROR No error > >> > >> Done: > >> > >> https://www.iana.org/assignments/quic/quic.xhtml#quic-transport-error-codes > >> > >> thanks, > >> Amanda > >> > >> > >>> Thanks! > >>> Sandy > >>> > >>> > >>> > >>> > >>>> On Feb 11, 2021, at 8:32 PM, Amanda Baber via RT <drafts- > >>>> approval@iana.org> wrote: > >>>> > >>>> RFC Editor: > >>>> > >>>> NOTE: with the authors' permission, we've added padding to the values > >>>> in Table 7 to match other QUIC registries (e.g. 0x00 instead of 0x0) > >>>> and changed "Received" in that table to "received." > >>>> > >>>> We've completed the registry actions for the following RFC-to-be: > >>>> > >>>> draft-ietf-quic-transport-34 > >>>> > >>>> IANA has created the QUIC Versions, QUIC Transport Parameters, QUIC > >>>> Frame Types, and QUIC Transport Error Codes under the "QUIC" heading > >>>> at > >>>> > >>>> Please see > >>>> https://www.iana.org/assignments/quic > >>>> > >>>> Please reply to this message to acknowledge receipt of these actions. > >>>> > >>>> Please let us know when an RFC number has been assigned and the date > >>>> of publication by sending a new message to <drafts-update- > >>>> ref@icann.org>. > >>>> > >>>> Thanks, > >>>> > >>>> Amanda Baber > >>>> Lead IANA Services Specialist > >>>> > >> > > > > -- > C430 mailing list > C430@rfc-editor.org > https://www.rfc-editor.org/mailman/listinfo/c430 >
- [C430] RFC 9000: Re: [IANA #1196209] Protocol Act… Sandy Ginoza
- Re: [C430] RFC 9000: Re: [IANA #1196209] Protocol… Sandy Ginoza
- Re: [C430] RFC 9000: Re: [IANA #1196209] Protocol… Martin Thomson