%% You should probably cite draft-ietf-core-attacks-on-coap-04 instead of this revision.
@techreport{ietf-core-attacks-on-coap-02,
    number =    {draft-ietf-core-attacks-on-coap-02},
    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-core-attacks-on-coap/02/},
    author =    {John Preuß Mattsson and John Fornehed and Göran Selander and Francesca Palombini and Christian Amsüss},
    title =     {{Attacks on the Constrained Application Protocol (CoAP)}},
    pagetotal = 19,
    year =      2022,
    month =     dec,
    day =       23,
    abstract =  {Being able to securely read information from sensors, to securely control actuators, and to not enable distributed denial-of-service attacks are essential in a world of connected and networking things interacting with the physical world. Using a security protocol such as DTLS, TLS, or OSCORE to protect CoAP is a requirement for secure operation and protects against many attacks. This document summarizes a number of known attacks on CoAP deployments and show that just using CoAP with a security protocol like DTLS, TLS, or OSCORE is not enough for secure operation. Several of the discussed attacks can be mitigated with the solutions in RFC 9175.},
}