Hi Michael,
"/1) .../"
For onboarding a new device, where there is no connectivity after
authentication, you propose to use 802.1X, which is an EAP lower layer.
EAP over CoAP is in fact a proposal for a application level EAP lower
layer that overcomes the limitation that 802.1X works on an
Dan Garcia wrote:
> EAP can be used in the context of IoT for authentication.
But, to what end?
1) If it is onboarding a new device, then there is no connectivity until after
authentication.
so you can't use CoAP, you have to use 802.1x, or some equivalent, or
create a system such
Dear all,
I support the inclusion of EAP-over-CoAP to the charter.
We've done work on this particular item in the past, and we've identified
the need for it in many places.. but unfortunately the draft didn't have a
proper "home" and things never advanced much. Use-cases we've seen include
Hi Michael,
EAP can be used in the context of IoT for authentication. To transport
EAP from the IoT device we need a light EAP lower-layer. This would be
CoAP. Morover, according to EAP key management framework, keys are
exported to protect the link and the EAP lower-layer itself. So yes,
Could someone point to a use case for "EAP over CoAP" please?
Is the goal to key an OSCORE context, or what?
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works|IoT architect [
] m...@sandelman.ca
