From 1f824e90718f65ffcaf1dd9406f5e8911f363c0d Mon Sep 17 00:00:00 2001 From: Thomas Fossati Date: Mon, 7 Oct 2024 16:34:08 +0200 Subject: [PATCH] reflect intro changes to abstract also fix internal refs Signed-off-by: Thomas Fossati --- draft-ietf-uta-tls13-iot-profile.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/draft-ietf-uta-tls13-iot-profile.md b/draft-ietf-uta-tls13-iot-profile.md index 38a73ca..a519aff 100644 --- a/draft-ietf-uta-tls13-iot-profile.md +++ b/draft-ietf-uta-tls13-iot-profile.md @@ -109,7 +109,7 @@ informative: This document is a companion to RFC 7925 and defines TLS/DTLS 1.3 profiles for Internet of Things devices. It also updates RFC 7925 with regards to the X.509 -certificate profile. +certificate profile and ciphersuite requirements. --- middle @@ -312,7 +312,7 @@ The recommendations in Section 20 of {{!RFC7925}} are applicable. At the time of writing, no such profile has been defined for CoAP {{CoAP}}. Therefore, 0-RTT MUST NOT be used by CoAP applications. -# Certificate Profile +# Certificate Profile {#certificate_profile} This section contains updates and clarifications to the certificate profile defined in {{!RFC7925}}. The content of Table 1 of {{!RFC7925}} has been @@ -733,7 +733,7 @@ on the anticipated deployment environment, the availability of code, and the constraints imposed by already deployed infrastructure (e.g., CA infrastructure, tool support). -# Ciphersuites +# Ciphersuites {#ciphersuites} According to {{Section 4.5.3 of DTLS13}}, the use of AES-CCM with 8-octet authentication tags (CCM_8) is considered unsuitable for general use with DTLS.