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

Sean Turner <sean@sn3rd.com> Fri, 24 November 2023 16:38 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 6E801C1519B8 for <tls@ietfa.amsl.com>; Fri, 24 Nov 2023 08:38:03 -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=unavailable 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 aKZys0uc4YHm for <tls@ietfa.amsl.com>; Fri, 24 Nov 2023 08:37:59 -0800 (PST)
Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (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 82114C1519B3 for <tls@ietf.org>; Fri, 24 Nov 2023 08:37:59 -0800 (PST)
Received: by mail-qk1-x733.google.com with SMTP id af79cd13be357-77d606355e7so110167585a.2 for <tls@ietf.org>; Fri, 24 Nov 2023 08:37:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; t=1700843878; x=1701448678; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=5eI4ZiA75/H85lrzhY0k53uE+T34GhUvKZ0vXL59QZE=; b=IdcYqDBMajCsQtcb/34LEk/vL6F9pHs4zi/CShXaJglUWZefbzmPQMyBTR9+8JDUMa XZ68HYWZW0ikNcM6k61snk1XJonqvl8/mIpnUfksDWsxfIKnpfED9wT2xqcb1TMyyo+h GBY3AeuYhnZSKJ83NtSJtyVHp6AZFx9yJo2lk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700843878; x=1701448678; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=5eI4ZiA75/H85lrzhY0k53uE+T34GhUvKZ0vXL59QZE=; b=WOeynkzUZOOYjZ+O8M+1CtDKVa6uhUhTeOF6OPTi5VJE3EszddNeLVMm2El4wiURvj +yYbIM7iEhUysaF59aHpehuvMG/bJoIUCtApjKNSfSyw9Wy7lxsmQGXjutORYuCr2yIJ 1mPQFJKpn0rVCbxYBK/X4ct6EAqm1phEVgiaPC0N9ik+QTGzL0Ymf32VRVpE91L+HQsY zsWIy14nVlxJX0Gts9Yb/zhfHvN1kbomz5Qlct3VbnBt8HvOLjo/gsoJ7H8II6iejDfE xqFJ7/Nw8GtpLNl9HrhKAbT5tqyZvnDpcaCLqH6Hs/adOHO/vmdlxdEwhGfRVn45eTDj LobQ==
X-Gm-Message-State: AOJu0YxbLBT05v9FJLzOmxxhz2B4j1FQci4Vdh5yjWJoYP5ziVnJ4Dto 5ut2g7tCFvZKf4lruh2bBU9fC7d3TBDzFlvBhMM=
X-Google-Smtp-Source: AGHT+IFQP1BhM24zMKu2ImxKz2j2MuoYN4y6L/v+LC12vfitkhvSLFkNJr1y1bVLnXiCi5noc4gDDA==
X-Received: by 2002:a05:620a:1a24:b0:775:dabd:a234 with SMTP id bk36-20020a05620a1a2400b00775dabda234mr4157622qkb.22.1700843877841; Fri, 24 Nov 2023 08:37:57 -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 qg1-20020a05620a664100b0076cc4610d0asm1333358qkn.85.2023.11.24.08.37.57 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Nov 2023 08:37:57 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.15\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <B6402C0F-7550-487B-A2E7-30C34919D209@sn3rd.com>
Date: Fri, 24 Nov 2023 11:37:56 -0500
Cc: draft-ietf-tls-dtls-rrc@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <43ED94BB-36A4-4F49-A545-646EEF1065CF@sn3rd.com>
References: <B6402C0F-7550-487B-A2E7-30C34919D209@sn3rd.com>
To: TLS List <tls@ietf.org>
X-Mailer: Apple Mail (2.3654.120.0.1.15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/oue1KjP3n3UcMrfYGUlPNQvSVWQ>
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: Fri, 24 Nov 2023 16:38:03 -0000

Hi! I am going to go ahead and close this call.  While there was a lot of mail on this thread, I am going to send the request to IANA because this I-D has been around for years and at least one person (a DE) said it was fine.

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