Hi,
I have three questions, in order of importance :)
Why does "CoAP-EAP Exporter Label" need to be an IANA registry? These are
free
form strings, no limited numbers, etc. If there is a risk someone uses the
same
label for a different operation, even having the registry wouldn't gain us
that
much? Also, if it is needed, should it not also contain "CoAP-EAP DTLS PSK"
?
Minimum MTU. Lower layers need to provide an EAP MTU size of
1020 octets or greater. CoAP assumes an upper bound of 1024 for
its payload which covers the requirements of EAP.
Is the "EAP MTU size" amd the "upper bound for its payload" the exact same
thing? Or is there a framing/prefix/header difference? Because there is only
4 bytes leeway here.
There is a consideration that needs to be considered when using
proxies in the CoAP-EAP, as the exchange contains a role-reversal
process at the beginning of the exchange. In the first message,
the IoT device acts as a CoAP client and the Controller as the
CoAP server. After that, in the remaining exchanges the roles
are reversed, being the IoT device, the CoAP server and the
Controller, the CoAP client.
So what is the "consideration" that "needs to be considered" ?
Thanks,
Paul
_______________________________________________
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace
