From c43dd56b736ce53d93e1bbd51c9391f9e5ba1445 Mon Sep 17 00:00:00 2001 From: Hannes Tschofenig Date: Fri, 23 Feb 2024 16:46:18 +0100 Subject: [PATCH] Update draft-ietf-uta-tls13-iot-profile.md --- draft-ietf-uta-tls13-iot-profile.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/draft-ietf-uta-tls13-iot-profile.md b/draft-ietf-uta-tls13-iot-profile.md index 41d68be..9849a62 100644 --- a/draft-ietf-uta-tls13-iot-profile.md +++ b/draft-ietf-uta-tls13-iot-profile.md @@ -132,7 +132,8 @@ partially replaced the need for the re-negotiation feature {{?RFC5746}} availabl in earlier TLS versions. However, rekeying defined in {{Section 4.6.3 of TLS13}} does not provide forward secrecy and post-handshake authentication defined in {{Section 4.6.2 of TLS13}} only offers client-to-server authentication. -{{?RFC9261}} later added support for mutual, post-handshake authentication but +The "Exported Authenticator" specification, see {{?RFC9261}}, recently added support for mutual, +post-handshake authentication but requires payloads to be exchanged by the application layer protocol. - Rekeying of the application traffic secret does not lead to an update of the