%% You should probably cite draft-ietf-core-oscore-capable-proxies instead of this I-D.
@techreport{tiloca-core-oscore-capable-proxies-00,
    number =    {draft-tiloca-core-oscore-capable-proxies-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-tiloca-core-oscore-capable-proxies/00/},
    author =    {Marco Tiloca and Rikard Höglund},
    title =     {{OSCORE-capable Proxies}},
    pagetotal = 23,
    year =      2021,
    month =     jul,
    day =       12,
    abstract =  {Object Security for Constrained RESTful Environments (OSCORE) can be used to protect CoAP messages end-to-end between two endpoints at the application layer, also in the presence of intermediaries such as proxies. This document defines how OSCORE is used to protect CoAP messages also between an origin application endpoint and an intermediary, or between two intermediaries. Besides, it defines how a CoAP message can be double-protected through "OSCORE-in-OSCORE", i.e., both end-to-end between origin application endpoints, as well as between an application endpoint and an intermediary or between two intermediaries. Thus, this document updates RFC 8613. The same approach applies to Group OSCORE, for protecting CoAP messages when group communication with intermediaries is used.},
}