Re: [TLS] Early IANA Allocations for draft-ietf-tls-dtls-rrc

Sean Turner <sean@sn3rd.com> Wed, 15 November 2023 18:10 UTC

Return-Path: <sean@sn3rd.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 741B7C14CE40 for <tls@ietfa.amsl.com>; Wed, 15 Nov 2023 10:10:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j6ixSgWBnBtj for <tls@ietfa.amsl.com>; Wed, 15 Nov 2023 10:10:04 -0800 (PST)
Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com [IPv6:2607:f8b0:4864:20::72b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74F05C14CE2B for <tls@ietf.org>; Wed, 15 Nov 2023 10:10:04 -0800 (PST)
Received: by mail-qk1-x72b.google.com with SMTP id af79cd13be357-777754138bdso465534885a.1 for <tls@ietf.org>; Wed, 15 Nov 2023 10:10:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; t=1700071802; x=1700676602; darn=ietf.org; h=message-id:in-reply-to:to:references:date:subject:mime-version :content-transfer-encoding:from:from:to:cc:subject:date:message-id :reply-to; bh=4HPA147twyhVc3z1cQ7XECylU38EzDMnwX2r5hWafLE=; b=EzykLTK1neihJGTi6VwaKSGmXkfpxXl1JrfnA9WO0fUsWr/oMqnyEseTREuaRn0KVH wp5I6CIEZpxk+HIL2GRdiJNIU+tAhUBLHdgywrqWTAZrLxRb/W01EojraGbbu93YrLqw wY5pt/qeJH/aR2M0A0mSJpMOLhpEuG9q6eJbA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700071802; x=1700676602; h=message-id:in-reply-to:to:references:date:subject:mime-version :content-transfer-encoding:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=4HPA147twyhVc3z1cQ7XECylU38EzDMnwX2r5hWafLE=; b=VJ7gTX2jv7qq5QLNib0HagHftHhlnu/RsL1sbdF3rNjISMegE2Neo9NRFzgOQleNUW k+nwXdutUEoy9WladerfV6JmxEbJkIEQgd3jm4wEv2Ar1Ab+pmgqzb+Vq2iZQVLkgkcS GkqCZZ7xJkqFO12EtAn8nkSBH0lVDaVj3mY/DHb9x5Lija3fC0fkyKwlwfECn/Mq7Ir+ QY8UDVaEOXmqLKdQ8R5Q8jsE+zBhfdy79iuWgXjzllIs6QkDgNSrhZmtFND0PT218Z5L HDUNErCZ88XKXx9i1RTOg0V6dqfxM3wG/BXhm0KQr158DO4rDr/ggqKd/zghpWLze7FN 6S7g==
X-Gm-Message-State: AOJu0Yx57dKiSl4V0CSiYiO06vDuuhy2VyAMOQsQ4bm/RZ4//BJQgEu3 A07XKi/F24/3Czbdq/157/hI2r5oYxW1m9IjCQ8=
X-Google-Smtp-Source: AGHT+IHdpOuKhOSg+NM0HOJDc1Ndjlua0J5nA8temyIvQAE/whDYLFiZjZTrtsZdxt2YZTstZk2u1A==
X-Received: by 2002:a05:620a:25d3:b0:77b:d529:f957 with SMTP id y19-20020a05620a25d300b0077bd529f957mr5955890qko.44.1700071802460; Wed, 15 Nov 2023 10:10:02 -0800 (PST)
Received: from smtpclient.apple (pool-138-88-17-47.washdc.fios.verizon.net. [138.88.17.47]) by smtp.gmail.com with ESMTPSA id rf2-20020a05620a8e8200b00763b94432ebsm3653955qkn.18.2023.11.15.10.10.01 for <tls@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Nov 2023 10:10:02 -0800 (PST)
From: Sean Turner <sean@sn3rd.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.15\))
Date: Wed, 15 Nov 2023 13:10:01 -0500
References: <B6402C0F-7550-487B-A2E7-30C34919D209@sn3rd.com>
To: TLS List <tls@ietf.org>
In-Reply-To: <B6402C0F-7550-487B-A2E7-30C34919D209@sn3rd.com>
Message-Id: <F6CEB6D7-5045-444F-91E7-190A11FDB71A@sn3rd.com>
X-Mailer: Apple Mail (2.3654.120.0.1.15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/rZhEVV1ARwtEINFnj6Iso82f-24>
Subject: Re: [TLS] Early IANA Allocations for draft-ietf-tls-dtls-rrc
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Nov 2023 18:10:08 -0000

Hi! This early allocation check is still going on.

Even though I can infer some implicit support from the WG because this I-D has been a WG item for years, it would be good to get some emails in support of the assignments because the I-D does assign a new content type value from one of our “scarce” registries.

Thanks,
spt

> On Nov 6, 2023, at 06:01, Sean Turner <sean@sn3rd.com> wrote:
> 
> Hi! After discussions with the authors of draft-ietf-tls-dtls-rrc, I would like to determine whether there is consensus to request two early code point assignments; see RFC 7120. One is for the return_routability_check content type and would go in the TLS ContentType registry and one is for the rrc extension that would go in the TLS ExtensionType Values registry; see Section 10 of the I-D. Please let the list know by 20 November 2023 if you support these early allocations.
> 
> Note the I-D also creates a new sub-registry, but IANA cannot create a temporary registry and then manage it for us. We will do that in the WG/I-D; there is not much to manage as only the initial 3 values are needed.
> 
> Cheers,
> spt