[Secdispatch] FW: [secdir] EDHOC and Transports

[Jim Schaad <[e-mail]>]

Move to the list I meant it to be on.

-----Original Message-----
From: Tero Kivinen <[e-mail]> 
Sent: Friday, January 25, 2019 6:36 AM
To: Jim Schaad <[e-mail]>
Cc: [e-mail]
Subject: [secdir] EDHOC and Transports

Jim Schaad writes:
> 3. 6LoPan over IEEE 802.15.4:  This has a packet size of 127 bytes.  
> The maximum frame overhead size is 25 bytes allowing for 102 bytes of
message
> space.   If one assumes 20 bytes of overhead for CoAP then this means a
> protocol packet size of 82 bytes.  If one needs to break the message 
> across multiple packets then the maximum data size is going to be 64 
> bytes using CoAP blockwise options.

IEEE 802.15.9 which provides framework for providing key management for IEEE
802.15.4 do provide its own fragmentation and reassembly service, thus
allows bigger packets to delivered between devices. When
802.15.9 was being specified we saw that support for larger packets in KMP
is needed than what 802.15.4 provides (note, that in some cases the phy
layer limits the packet size even more), and thats why we did define a
fragmentation and reassembly protocol there too. 

Currently specified key management protocols for 802.15.9 include
802.1X/MKA, HIP, IKEv2, PANA, Dragonfly, 802.11/4WH, 802.11/GKH, ETSI TS 102
887-2. Someone would need to write specification how to use EDHOC over
802.15.9 to make it usable there too. Another omission in the KMPs provided
by the 802.15.9 is the TLS, as nobody wanted to write that specification. In
the IEEE there is some plans of doing amendment to the 802.15.9 which could
include some new key management protocols, depending who would be
interesting to write the text...
--
[e-mail]