[Ace] Last Call: (EAP-based Authentication Service for CoAP) to Proposed Standard

2024-01-11 Thread The IESG
The IESG has received a request from the Authentication and Authorization for Constrained Environments WG (ace) to consider the following document: - 'EAP-based Authentication Service for CoAP' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final co

[Ace] Last Call: (EAP-based Authentication Service for CoAP) to Proposed Standard

2024-09-05 Thread The IESG
The IESG has received a request from the Authentication and Authorization for Constrained Environments WG (ace) to consider the following document: - 'EAP-based Authentication Service for CoAP' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final com

Re: [Ace] Last Call: (EAP-based Authentication Service for CoAP) to Proposed Standard

2024-01-11 Thread Carsten Bormann
I have a quick question on Figure 6: This says: CoAP-EAP_Info = { ? 1 : array, ; cipher suite […] for the cipher suite. I assume array …really should be [+ int/tstr] …so this can be a non-empty list of RFC 9052 algorithm identifiers? I’m not seeing an example

Re: [Ace] Last Call: (EAP-based Authentication Service for CoAP) to Proposed Standard

2024-01-25 Thread Dan Garcia Carrillo
Dear Carsten, Thank you very much for the comments. Yes, you are correct. The content of the array contains a non-empty list of RFC 9052 algorithm identifiers. There is a case, where the element representing the list is not sent, that is intended to signify that the default cipher suites are c