Skip to content

Commit

Permalink
Additional info for Exported authenticators
Browse files Browse the repository at this point in the history
  • Loading branch information
hannestschofenig authored Oct 7, 2024
1 parent 41f57bc commit e25521c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion draft-ietf-uta-tls13-iot-profile.md
Original file line number Diff line number Diff line change
Expand Up @@ -133,7 +133,7 @@ does not provide forward secrecy and post-handshake authentication defined in
{{Section 4.6.2 of TLS13}} only offers client-to-server authentication.
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.
requires the Certificate, CertificateVerify and the Finished messages to be exchanged by the application layer protocol, as it is exercised for HTTP/2 and HTTP/3 in {{?I-D.ietf-httpbis-secondary-server-certs}}.

- Rekeying of the application traffic secret does not lead to an update of the
exporter secret (see {{Section 7.5 of TLS13}}) since the derived export secret is
Expand Down

0 comments on commit e25521c

Please sign in to comment.