%% You should probably cite draft-ietf-core-observe-multicast-notifications-10 instead of this revision. @techreport{ietf-core-observe-multicast-notifications-04, number = {draft-ietf-core-observe-multicast-notifications-04}, 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-observe-multicast-notifications/04/}, author = {Marco Tiloca and Rikard Höglund and Christian Amsüss and Francesca Palombini}, title = {{Observe Notifications as CoAP Multicast Responses}}, pagetotal = 84, year = 2022, month = jul, day = 11, 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 addressed to all the clients observing a same target resource. This document updates RFC7252 and RFC7641, and defines how a server sends observe notifications as response messages over multicast, 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 between the server and the observer clients.}, }