Re: QUICWG Temporary IANA Registry

Samuel Hurst <samuelh@rd.bbc.co.uk> Wed, 03 February 2021 15:44 UTC

Return-Path: <samuelh@rd.bbc.co.uk>
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 080C93A0A2B for <quic@ietfa.amsl.com>; Wed, 3 Feb 2021 07:44:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, 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 tKdtfjkSwV2u for <quic@ietfa.amsl.com>; Wed, 3 Feb 2021 07:44:06 -0800 (PST)
Received: from tlsmtp.bbc.co.uk (tlsmtp0.telhc.bbc.co.uk [132.185.161.172]) (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 190D13A0A29 for <quic@ietf.org>; Wed, 3 Feb 2021 07:44:05 -0800 (PST)
Received: from gateh.lh.bbc.co.uk ([10.118.193.77]) by tlsmtp.bbc.co.uk (8.15.2/8.15.2) with ESMTPS id 113Fi32C010054 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Feb 2021 15:44:04 GMT
Received: from mailhub0.rd.bbc.co.uk ([172.29.120.128]) by gateh.lh.bbc.co.uk (8.14.5+Sun/8.13.6) with ESMTP id 113Fi34e020876; Wed, 3 Feb 2021 15:44:03 GMT
Received: from [172.29.197.148] (port=49240) by mailhub0.rd.bbc.co.uk with esmtp (Exim 4.92) (envelope-from <samuelh@rd.bbc.co.uk>) id 1l7KK2-0008Dj-Ur; Wed, 03 Feb 2021 15:44:03 +0000
Subject: Re: QUICWG Temporary IANA Registry
To: quic@ietf.org
References: <d0288167-a324-1264-7daa-d7b29b7ede03@rd.bbc.co.uk> <20210203133604.GA801221@okhta>
Cc: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
From: Samuel Hurst <samuelh@rd.bbc.co.uk>
Autocrypt: addr=samuelh@rd.bbc.co.uk; prefer-encrypt=mutual; keydata= LS0tLS1CRUdJTiBQR1AgUFVCTElDIEtFWSBCTE9DSy0tLS0tCgptRE1FWFZacHVSWUpLd1lC QkFIYVJ3OEJBUWRBTC9KNCtaMUVGRGNLR3ByNzdvYzZKRWVOemZXQ0t4VXBCNXJ6CnVUN0tm dHEwSTFOaGJYVmxiQ0JJZFhKemRDQThjMkZ0ZFdWc2FFQnlaQzVpWW1NdVkyOHVkV3MraUpZ RUV4WUkKQUQ0V0lRUi9NaG1CLzJtREdicVJEUUZGM3RxdVp0UWdLd1VDWFZacHVRSWJBd1VK Q1dZQmdBVUxDUWdIQWdZVgpDZ2tJQ3dJRUZnSURBUUllQVFJWGdBQUtDUkJGM3RxdVp0UWdL L0p6QVFEZUxZZjNSQVgzOTk3THgzcDZnbTZQClRCYlJSV2JVeDJ0VHovOTFzQytUREFFQTVz di9GdFdNN045VS83L0p2MDdQVkpGS0VTS3JQRENFdHBDSHdwbG0KblF5NE9BUmRWbW01RWdv ckJnRUVBWmRWQVFVQkFRZEFnVWpnZ09jb25pV0RFWkxQazBQNHVvRGtGMmZubFR1egpmSVpl dm9kTGhBNERBUWdIaUg0RUdCWUlBQ1lXSVFSL01obUIvMm1ER2JxUkRRRkYzdHF1WnRRZ0t3 VUNYVlpwCnVRSWJEQVVKQ1dZQmdBQUtDUkJGM3RxdVp0UWdLNys4QVFETFZlaW9rVlBIaUlG TXpWRzltS2dib3A1am1CQkkKazFpUWw5d0NJMVFOUVFEK0x1LzhRZnJPcjBSOGNEemUxSjlW Q0VmQmVjcjdROElHcVhCWHpZWkU4QTA9Cj1UNFJwCi0tLS0tRU5EIFBHUCBQVUJMSUMgS0VZ IEJMT0NLLS0tLS0K
Message-ID: <f98a39ae-0d7a-2141-9285-5f6033b7473f@rd.bbc.co.uk>
Date: Wed, 03 Feb 2021 15:43:57 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <20210203133604.GA801221@okhta>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="FLoBLB9tDNuXVR8JxYh7c349EObSI6xAt"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/8ZbED7j8VHcyoMrLEZGFMjLwyos>
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: Wed, 03 Feb 2021 15:44:08 -0000

Hi Dmitri,

On 03/02/2021 13:36, Dmitri Tikhonov wrote:
> Yes, this value is fine.  (If you expect your extention to evolve and
> the frame format to change, one approach is to use a different value
> in your initial drafts, e.g 0xFF...D0F, while targeting 0xD0F to be
> the final value.)  In any case, do add it to the list to call dibs.

That's a very good idea, and I'll keep it in mind. Would I put both my
initial starting value in the registry, as well as my final target value
just to keep dibs on it? Or would it be frowned upon to camp on space
that I'm not using (although with a 62-bit number space, we'd need a lot
of extensions before anyone is treading on other's toes, I'd guess).

-Sam