Skip to main content

EAP-based Authentication Service for CoAP

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Rafael Marin-Lopez , Dan Garcia-Carrillo
Last updated 2021-07-26 (Latest revision 2021-01-21)
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Associated None milestones
Feb 2021
Adoption call of "EAP-based Authentication Service for CoAP"
Aug 2021
Submission to the IESG of "EAP-based Authentication Service for CoAP"
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


This document describes an authentication service that uses EAP transported by means of CoAP messages with the following purposes: o Authenticate a CoAP-enabled device that enters a new security domain against a AAA infrastructure through a domain Controller. o Bootstrap key material to protect CoAP messages exchanged between them. o Enable the establishment of Security Associations between them.


Rafael Marin-Lopez
Dan Garcia-Carrillo

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)