Hi,

We submitted -07. This version takes care of all the remaining issues as well 
as the comments received on the TLS WG list from Achim Kraus. We feel that the 
draft is done and ready to progress.


Changes:


- Added a reference to draft-ietf-uta-tls13-iot-profile. This is important as 
it specifies MTI algorithms for DTLS 1.3 in the IoT.

- Added “TLS is typically sent over 8 bytes UDP datagram headers while TLS is 
typically sent over 20 bytes TCP segment headers.  TCP also uses some more 
bytes for additional messages used in TCP internally.” as suggested by Achim 
Kraus on the TLS WG list.

- Added how 16 bytes tags would affect the sizes as suggested by Achim Kraus on 
the TLS WG list. This was added as text as the changes are trivial. Kept CCM8 
in tables as that is the MTI in RFC 7925, draft-ietf-uta-tls13-iot-profile, and 
draft-ietf-core-oscore-edhoc.

- As discussed on the TLS WG list, the sizes for (D)TLS are heavily dependent 
on the key exchange, signature, and PRK format used. Based on this one table 
now uses secp256r1 and ecdsa_secp256r1_sha256 while another table uses the more 
optimized x25519 and ed25519. A new table was needed as the changes are a bit 
complex.

- As discussed on the TLS WG list and in draft-mattsson-tls-compact-ecc the 
ECDSA signatures in (D)TLS 1.3 are variable length with significant overhead 
from the DER encoding. The examples were updates with the average 75 bytes 
encoding (probabilities are roughly 25% for 76, 50% for 75, 25% for 74, and 0% 
for < 74).

- added ed25519 PRK example as the size differs significantly from uncompressed 
and compressed secp256r1 RPKs.

- The detailed DTLS example handshake now uses ecdsa_secp256r1_sha256 while the 
detailed TLS example uses x25519 and ed25519. The table gives numbers for all 
combinations.

- Added text on overhead when draft-ietf-core-oscore-edhoc is used.

- Much more cTLS handshake examples added. cTLS now has the same examples as 
TLS 1.3. New section on cTLS explains the numbers.

- Reference updates.
- Various editorial improvements.

Cheers,
John

From: [email protected] <[email protected]>
Date: Tuesday, 24 January 2023 at 13:22
To: Mališa Vučinić <[email protected]>, John Mattsson 
<[email protected]>, Francesca Palombini 
<[email protected]>, John Mattsson <[email protected]>, 
Malisa Vucinic <[email protected]>
Subject: New Version Notification for 
draft-ietf-lwig-security-protocol-comparison-07.txt

A new version of I-D, draft-ietf-lwig-security-protocol-comparison-07.txt
has been successfully submitted by John Preuß Mattsson and posted to the
IETF repository.

Name:           draft-ietf-lwig-security-protocol-comparison
Revision:       07
Title:          Comparison of CoAP Security Protocols
Document date:  2023-01-24
Group:          lwig
Pages:          47
URL:            
https://www.ietf.org/archive/id/draft-ietf-lwig-security-protocol-comparison-07.txt
Status:         
https://datatracker.ietf.org/doc/draft-ietf-lwig-security-protocol-comparison/
Html:           
https://www.ietf.org/archive/id/draft-ietf-lwig-security-protocol-comparison-07.html
Htmlized:       
https://datatracker.ietf.org/doc/html/draft-ietf-lwig-security-protocol-comparison
Diff:           
https://author-tools.ietf.org/iddiff?url2=draft-ietf-lwig-security-protocol-comparison-07

Abstract:
   This document analyzes and compares the sizes of key exchange flights
   and the per-packet message size overheads when using different
   security protocols to secure CoAP.  Small message sizes are very
   important for reducing energy consumption, latency, and time to
   completion in constrained radio network such as Low-Power Wide Area
   Networks (LPWANs).  The analyzed security protocols are DTLS 1.2,
   DTLS 1.3, TLS 1.2, TLS 1.3, cTLS, EDHOC, OSCORE, and Group OSCORE.
   The DTLS and TLS record layers are analyzed with and without 6LoWPAN-
   GHC compression.  DTLS is analyzed with and without Connection ID.




The IETF Secretariat
_______________________________________________
Lwip mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lwip

Reply via email to