Hi Josh,
Thanks for the support.
At first sight, I would say that, from the perspective of a very
constrained devices and networks, it would be better to directly design
an EAP lower-layer based on CoAP without introducing any intermediate
layer.
Best Regards,
Dan.
On 7/12/20 16:50, josh.
Hi all,
I have worked with EAP-NOOB and implemented a constrained version for
Contiki (https://github.com/eduingles/coap-eap-noob). I exposed some
issues on the list such as adding support for P-256 and clarifying the
text on waiting exchange and the authors have addressed my issues. The
draf
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,
OS
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
places
Hello ACE,
On Thu, Dec 03, 2020 at 01:20:08PM +, Daniel Migault wrote:
> It seems ACE to me that ACE could be home for such a document. I am
> wondering if emu core or any other WG believe there is a better place
> for it.
If nothing else, I'd be curious to see EAP-over-CoAP this sketched out
On 2020-12-09, at 14:28, Christian Amsüss wrote:
>
> follow CoRE best practices
Indeed; for instance, we “RESTified” documents in ACE before (and they not just
became ideologically correct, but also plain better).
Grüße, Carsten
signature.asc
Description: Message signed with OpenPGP
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 as
