%% You should probably cite draft-ietf-ace-wg-coap-eap-10 instead of this revision.
@techreport{ietf-ace-wg-coap-eap-03,
    number =    {draft-ietf-ace-wg-coap-eap-03},
    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/03/},
    author =    {Rafael Marin-Lopez and Dan Garcia-Carrillo},
    title =     {{EAP-based Authentication Service for CoAP}},
    pagetotal = 27,
    year =      2021,
    month =     jul,
    day =       26,
    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 primer goals is to authenticate a CoAP-enabled device (EAP peer) that intends to join a security domain managed by a domain 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 also provides guidelines on how to generate key material for other types of security associations.},
}