Authentication Service Based on the Extensible Authentication Protocol (EAP) for Use with the Constrained Application Protocol (CoAP)
RFC 9820
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2025-09-16
|
(System) | IANA registries were updated to include RFC9820 |
|
2025-09-12
|
(System) | Received changes through RFC Editor sync (created document RFC 9820, created became rfc relationship between draft-ietf-ace-wg-coap-eap and RFC 9820, set title to 'Authentication … Received changes through RFC Editor sync (created document RFC 9820, created became rfc relationship between draft-ietf-ace-wg-coap-eap and RFC 9820, set title to 'Authentication Service Based on the Extensible Authentication Protocol (EAP) for Use with the Constrained Application Protocol (CoAP)', set abstract to 'This document specifies an authentication service that uses the Constrained Application Protocol (CoAP) as a transport method to carry the Extensible Authentication Protocol (EAP). As such, it defines an EAP lower layer based on CoAP called "CoAP-EAP". One of the main goals is to authenticate a CoAP-enabled Internet of Things (IoT) device (EAP peer) that intends to join a security domain managed by a Controller (EAP authenticator). Secondly, it allows deriving key material to protect CoAP messages exchanged between them based on Object Security for Constrained RESTful Environments (OSCORE), enabling the establishment of a security association between them.', set pages to 35, set standardization level to Proposed Standard, added RFC published event at 2025-09-12) |
|
2025-09-12
|
(System) | RFC published |