%% You should probably cite draft-ietf-ace-wg-coap-eap-10 instead of this revision.
@techreport{ietf-ace-wg-coap-eap-07,
    number =    {draft-ietf-ace-wg-coap-eap-07},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-ace-wg-coap-eap/07/},
    author =    {Rafael Marin-Lopez and Dan Garcia-Carrillo},
    title =     {{EAP-based Authentication Service for CoAP}},
    pagetotal = 31,
    year =      2022,
    month =     may,
    day =       27,
    abstract =  {This document specifies an authentication service that uses the Extensible Authentication Protocol (EAP) transported employing Constrained Application Protocol (CoAP) messages. 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 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.},
}