diff --git a/hannestschofenig-patch-6/draft-ietf-uta-tls13-iot-profile.html b/hannestschofenig-patch-6/draft-ietf-uta-tls13-iot-profile.html index 103e18a..5c58ba4 100644 --- a/hannestschofenig-patch-6/draft-ietf-uta-tls13-iot-profile.html +++ b/hannestschofenig-patch-6/draft-ietf-uta-tls13-iot-profile.html @@ -1288,33 +1288,36 @@
19. Fault Attacks on Deterministic Signature Schemes
Rekeying of the application traffic secret does not lead to an update of the @@ -2218,39 +2221,48 @@
As detailed in [I-D.ietf-pquip-pqc-engineers], the IETF is actively working to address the challenges of adopting PQC in various protocols, including TLS. The document highlights key aspects engineers must consider, such as algorithm selection, performance impacts, and deployment strategies. It emphasizes the importance of gradual integration of PQC to ensure secure communication while accounting for the increased computational, memory, and bandwidth requirements of PQC algorithms. These challenges are especially relevant in the context of IoT, where device constraints limit the adoption of larger key sizes and more complex cryptographic operations.¶
+Incorporating PQC into TLS is still ongoing, with key exchange message sizes increasing due to larger public keys. These larger keys demand more flash storage and higher RAM usage, presenting significant obstacles for resource-constrained IoT devices. The transition from classical cryptographic algorithms to PQC will be a significant challenge for constrained IoT devices, requiring careful planning to select hardware suitable for the task considering the lifetime of an IoT product.¶
+A list of open issues can be found at https://github.com/thomas-fossati/draft-tls13-iot/issues¶
+A list of open issues can be found at https://github.com/thomas-fossati/draft-tls13-iot/issues¶
This entire document is about security.¶
+This entire document is about security.¶
This document makes no requests to IANA.¶
+This document makes no requests to IANA.¶