A new Request for Comments is now available in online RFC libraries.
RFC 9820
Title: Authentication Service Based on the
Extensible Authentication Protocol (EAP) for Use
with the Constrained Application Protocol (CoAP)
Author: R. Marin-Lopez,
D. Garcia-Carrillo
Status: Standards Track
Stream: IETF
Date: September 2025
Mailbox: [email protected],
[email protected]
Pages: 35
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ace-wg-coap-eap-15.txt
URL: https://www.rfc-editor.org/info/rfc9820
DOI: 10.17487/RFC9820
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.
This document is a product of the Authentication and Authorization for
Constrained Environments Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org
