%% You should probably cite draft-ietf-core-observe-multicast-notifications instead of this I-D.
@techreport{tiloca-core-observe-multicast-notifications-02,
    number =    {draft-tiloca-core-observe-multicast-notifications-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-tiloca-core-observe-multicast-notifications/02/},
    author =    {Marco Tiloca and Rikard Höglund and Christian Amsüss and Francesca Palombini},
    title =     {{Observe Notifications as CoAP Multicast Responses}},
    pagetotal = 34,
    year =      2020,
    month =     mar,
    day =       9,
    abstract =  {The Constrained Application Protocol (CoAP) allows clients to "observe" resources at a server, and receive notifications as unicast responses upon changes of the resource state. In some use cases, such as based on publish-subscribe, it would be convenient for the server to send a single notification to all the clients observing a same target resource. This document defines how a CoAP server sends observe notifications as response messages over multicast, by synchronizing all the observers of a same resource on a same shared Token value. Besides, this document defines how Group OSCORE can be used to protect multicast notifications end-to-end from the CoAP server to the multiple observer clients.},
}