[Tls-reg-review] [IANA #1184473] Early allocation request for TLS extension type for QUIC (draft-ietf-quic-tls)

Michelle Cotton via RT <iana-prot-param@iana.org> Thu, 10 December 2020 16:30 UTC

Return-Path: <iana-shared@icann.org>
X-Original-To: tls-reg-review@ietfa.amsl.com
Delivered-To: tls-reg-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A53793A10B3; Thu, 10 Dec 2020 08:30:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level:
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 fIR2wCXR8LD5; Thu, 10 Dec 2020 08:30:32 -0800 (PST)
Received: from smtp.dc.icann.org (smtp.dc.icann.org [192.0.46.81]) (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 CFD6D3A10AD; Thu, 10 Dec 2020 08:30:32 -0800 (PST)
Received: from request4.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.dc.icann.org (Postfix) with ESMTP id 08119E04FD; Thu, 10 Dec 2020 16:30:32 +0000 (UTC)
Received: by request4.lax.icann.org (Postfix, from userid 48) id C136720867; Thu, 10 Dec 2020 16:30:31 +0000 (UTC)
RT-Owner: michelle.cotton
From: Michelle Cotton via RT <iana-prot-param@iana.org>
Reply-To: iana-prot-param@iana.org
In-Reply-To: <rt-4.4.3-28478-1607610432-1085.1184473-37-0@icann.org>
References: <RT-Ticket-1184473@icann.org> <5B9257F7-A3EE-4439-BFB6-3D123B313FD6@eggert.org> <rt-4.4.3-1410-1607540681-38.1184473-37-0@icann.org> <7be460ca-d296-4cf4-80d7-2728ccdbc66f@www.fastmail.com> <24c4885e-5d9c-4cd7-bfc6-90985f1a3241@www.fastmail.com> <E5F19B25-B097-4625-BD48-989FE835989E@akamai.com> <rt-4.4.3-28478-1607610432-1085.1184473-37-0@icann.org>
Message-ID: <rt-4.4.3-28479-1607617831-1550.1184473-37-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1184473
X-Managed-BY: RT 4.4.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: michelle.cotton@icann.org
To: lars@eggert.org
CC: magnus.westerlund@ericsson.com, tls-reg-review@ietf.org, mt@lowentropy.net, quic-ads@ietf.org, quic-chairs@ietf.org, tls-chairs@ietf.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Thu, 10 Dec 2020 16:30:31 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/z8MOW0bYNP2KIj4XcCXBe2IOKfI>
Subject: [Tls-reg-review] [IANA #1184473] Early allocation request for TLS extension type for QUIC (draft-ietf-quic-tls)
X-BeenThere: tls-reg-review@ietf.org
X-Mailman-Version: 2.1.29
List-Id: TLS REVIEW <tls-reg-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls-reg-review>, <mailto:tls-reg-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls-reg-review/>
List-Post: <mailto:tls-reg-review@ietf.org>
List-Help: <mailto:tls-reg-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls-reg-review>, <mailto:tls-reg-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Dec 2020 16:30:38 -0000

Hello all,

We have changed the assignment for the TLS extension type from 46 to

57	quic_transport_parameters	CH, EE	       N

See: https://www.iana.org/assignments/tls-extensiontype-values


On Thu Dec 10 14:27:12 2020, rsalz@akamai.com wrote:
> > So,  I'm going to request a new allocation for this codepoint.  57
> > seems to be the next one, but I really don't care what you select.
> > It might be better to have something chosen at random even.
> 
> 57 seems pretty random to me :)
> 
> > I am ALSO going to request that IANA mark the codepoint 46 as
> > reserved, as well as the codepoint 40.  I don't know how to formally
> > do that; I'm prepared to write an internet-draft for that purpose if
> > that is necessary.
> 
> That makes sense but I don't know the process either.
> 

As this is a Specification Required registry, we need something to point to for a reference for a Reserved value.  This can be accomplished by a brief internet-draft that describes the 2 reservations.  Alternatively, the experts could post a message to the mailing list documenting the reservation of 40 and 46 along with the reasoning.  In the registry, we could point to the mail in the archive.  It is up to the experts to determine if that is sufficient documentation.

I'm going to resolve this request as it was for the registration for quic_transport_parameters.  We can open a new request for the reservations.

Please let us know if you have any questions.

Thank you,

Michelle Cotton

********

Michelle Cotton
Protocol Parameters Engagement Sr. Manager
IANA Services