[Tls-reg-review] TLS ALPN registry: Request to add CoAP-over-UDP
Christian Amsüss <christian@amsuess.com> Wed, 28 February 2024 16:17 UTC
Return-Path: <christian@amsuess.com>
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 030AFC14F5F5 for <tls-reg-review@ietfa.amsl.com>; Wed, 28 Feb 2024 08:17:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.607
X-Spam-Level:
X-Spam-Status: No, score=-2.607 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 5MsTlk-WUftw for <tls-reg-review@ietfa.amsl.com>; Wed, 28 Feb 2024 08:17:38 -0800 (PST)
Received: from smtp.akis.at (smtp.akis.at [IPv6:2a02:b18:500:a515::f455]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 5A02BC14F5F3 for <tls-reg-review@ietf.org>; Wed, 28 Feb 2024 08:17:36 -0800 (PST)
Received: from poseidon-mailhub.amsuess.com (095129206250.cust.akis.net [95.129.206.250]) by smtp.akis.at (8.17.1/8.17.1) with ESMTPS id 41SGHXd8013953 (version=TLSv1.2 cipher=ECDHE-ECDSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <tls-reg-review@ietf.org>; Wed, 28 Feb 2024 17:17:33 +0100 (CET) (envelope-from christian@amsuess.com)
X-Authentication-Warning: smtp.akis.at: Host 095129206250.cust.akis.net [95.129.206.250] claimed to be poseidon-mailhub.amsuess.com
Received: from poseidon-mailbox.amsuess.com (hermes.lan [10.13.13.254]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id E71683455A for <tls-reg-review@ietf.org>; Wed, 28 Feb 2024 17:17:31 +0100 (CET)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:e80f:997f:17f6:9706]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id A6FEC3148E for <tls-reg-review@ietf.org>; Wed, 28 Feb 2024 17:17:31 +0100 (CET)
Received: (nullmailer pid 16668 invoked by uid 1000); Wed, 28 Feb 2024 16:17:31 -0000
Date: Wed, 28 Feb 2024 17:17:31 +0100
From: Christian Amsüss <christian@amsuess.com>
To: tls-reg-review@ietf.org
Message-ID: <Zd9cmwFFDXJQVKys@hephaistos.amsuess.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="AtUULeBfSqqnWwWS"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/RiTWJ3-vE95YQ76Zk3VZySB4YEs>
Subject: [Tls-reg-review] TLS ALPN registry: Request to add CoAP-over-UDP
X-BeenThere: tls-reg-review@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
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: Wed, 28 Feb 2024 16:17:43 -0000
Dear TLS experts, please have the following entry added into the TLS ALPN registry: * Protocol: CoAP-over-DTLS * Identification sequence: 0x63 0x6f ("co") * Reference: RFC7252 RFC7252 did not register this because it predates ALPNs (it does describe CoAP and its use of DTLS), but there are now use cases related to dns-over-coap [1] and SVCB. This registration does not (can not, and does not intend to) change whether CoAP clients should send an ALPN, but later documents could change that (eg. [2] that concerns itself with DTLS1.3 used with CoAP). Given that the underlying protocol is used in constrained environments that are sensitive to message sizes, the short identifier should be warranted. Note that there is already an entry for "coap", but that refers to CoAP-over-TLS. If possible, please consider updating the "CoAP" (0x63 0x6f 0x61 0x70) entry to say "CoAP-over-TLS" to avoid confusion. This is following the recommendation at [5] to not attempt reusing the same ALPN for both the DTLS and the TLS version of a protocol. This is an individual request, which AIU should suffice for this registry given there is a document out already. I did check briefly with the CoRE group, and while not being a consensus question, got positive feedback from there[3][4]. Best regards Christian [1]: https://datatracker.ietf.org/doc/draft-ietf-core-dns-over-coap/ [2]: https://datatracker.ietf.org/doc/draft-ietf-anima-constrained-voucher/ [3]: https://mailarchive.ietf.org/arch/browse/core/?gbt=1&index=3Ih6grC8j0JxPuOQqdaFFjSC0r4 [4]: https://datatracker.ietf.org/doc/minutes-interim-2024-core-04-202402281500/#request-for-an-alpn-for-coap-over-dtls-5min-ca -- This may seem a bit weird, but that's okay, because it is weird. -- perldata(1) about perl variables
- [Tls-reg-review] TLS ALPN registry: Request to ad… Christian Amsüss
- Re: [Tls-reg-review] TLS ALPN registry: Request t… Salz, Rich
- Re: [Tls-reg-review] TLS ALPN registry: Request t… Christian Amsüss
- Re: [Tls-reg-review] TLS ALPN registry: Request t… Christian Amsüss
- Re: [Tls-reg-review] TLS ALPN registry: Request t… Salz, Rich
- [Tls-reg-review] [IANA #1360036] Re: TLS ALPN reg… Sabrina Tanamal via RT
- [Tls-reg-review] [IANA #1360036] Re: TLS ALPN reg… Sabrina Tanamal via RT
- [Tls-reg-review] [IANA #1360036] Re: TLS ALPN reg… Sabrina Tanamal via RT
- Re: [Tls-reg-review] [IANA #1360036] Re: TLS ALPN… Yoav Nir
- [Tls-reg-review] [IANA #1360036] Re: TLS ALPN reg… David Dong via RT
- Re: [Tls-reg-review] [IANA #1360036] Re: TLS ALPN… Salz, Rich