Re: [quicwg/base-drafts] Change transport parameter IANA registration policy (#3109)

David Schinazi <notifications@github.com> Fri, 25 October 2019 02:38 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E2F6120096 for <quic-issues@ietfa.amsl.com>; Thu, 24 Oct 2019 19:38:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level:
X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 yFAqAFcc9WVI for <quic-issues@ietfa.amsl.com>; Thu, 24 Oct 2019 19:38:37 -0700 (PDT)
Received: from out-18.smtp.github.com (out-18.smtp.github.com [192.30.252.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E37FD12008D for <quic-issues@ietf.org>; Thu, 24 Oct 2019 19:38:36 -0700 (PDT)
Received: from github-lowworker-edec459.ac4-iad.github.net (github-lowworker-edec459.ac4-iad.github.net [10.52.18.32]) by smtp.github.com (Postfix) with ESMTP id 316F16E123F for <quic-issues@ietf.org>; Thu, 24 Oct 2019 19:38:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1571971116; bh=h4ZLtULVqBoVFoBxcRuRw3Nlv6c/nP852WZXntxpdV4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fAzPsHcOtbTqEJgknl+nLJeZZUfYSuhbCFFjxU2NlxngGztTgoOpijL7NU4zCoc8I e3WUGXNqUi5up0gHGwnUqPJVorSQ5/QwatbuM5mNtVuB06SdraFYhaDvUyv5JDulHr HIOb5C95s5lCcvkoMC/ss+uaAuA8jEiFuhzGnhYc=
Date: Thu, 24 Oct 2019 19:38:36 -0700
From: David Schinazi <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK73R5SJ65AML3BKSL53X6QLZEVBNHHB4UD5BQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3109/review/306956541@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3109@github.com>
References: <quicwg/base-drafts/pull/3109@github.com>
Subject: Re: [quicwg/base-drafts] Change transport parameter IANA registration policy (#3109)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5db2602c1f324_5dc73fe103ccd96c991d1"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: DavidSchinazi
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Z6dbffy9XmrtKJ0cPfpu3uBlDys>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Oct 2019 02:38:39 -0000

DavidSchinazi commented on this pull request.



> @@ -5830,17 +5830,18 @@ IANA \[SHALL add/has added] a registry for "QUIC Transport Parameters" under a
 "QUIC Protocol" heading.
 
 The "QUIC Transport Parameters" registry governs a 16-bit space.  This space is
-split into two spaces that are governed by different policies.  Values with the
-first byte in the range 0x00 to 0xfe (in hexadecimal) are assigned via the
-Specification Required policy {{!RFC8126}}.  Values with the first byte 0xff are
-reserved for Private Use {{!RFC8126}}.
+split into three spaces that are governed by different policies.  Values between
+0x0000 and 0x003f (in hexadecimal) are assigned via the Standards Action or IESG

@janaiyengar `Standards Action` means WG-track RFC so it requires some amount of IETF consensus, whereas `Specification Required` just means someone wrote a draft. See RFC 8126 for details

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/3109#discussion_r338864783