From c3e229a3f82781e36a8f1c78640efa839bb7c5ca Mon Sep 17 00:00:00 2001 From: Hannes Tschofenig Date: Mon, 16 Dec 2024 17:00:42 +0100 Subject: [PATCH] Update draft-ietf-uta-tls13-iot-profile.md Co-authored-by: Thomas Fossati --- draft-ietf-uta-tls13-iot-profile.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-uta-tls13-iot-profile.md b/draft-ietf-uta-tls13-iot-profile.md index 0b2789d..1238e80 100644 --- a/draft-ietf-uta-tls13-iot-profile.md +++ b/draft-ietf-uta-tls13-iot-profile.md @@ -701,7 +701,7 @@ optimizations typically get implemented last. certificates that need to be transmitted and processed. See {{?I-D.irtf-t2trg-taxonomy-manufacturer-anchors}} for a discussion about CA hierarchies. - Most security requirements can be satisfied with a PKI depth of 3 (root CA, 1 subordinate CA, and End-Entity certificates). + Most security requirements can be satisfied with a PKI depth of 3 (root CA, one subordinate CA, and end entity certificates). * Pay attention to the amount of information conveyed inside certificates. * Use session resumption to reduce the number of times a full handshake is needed. Use Connection IDs {{RFC9146}}, when possible, to enable