<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.tiloca-core-observe-multicast-notifications" target="https://datatracker.ietf.org/doc/html/draft-tiloca-core-observe-multicast-notifications-00">
   <front>
      <title>Observe Notifications as CoAP Multicast Responses</title>
      <author initials="M." surname="Tiloca" fullname="Marco Tiloca">
         <organization>RISE AB</organization>
      </author>
      <author initials="R." surname="Höglund" fullname="Rikard Höglund">
         <organization>RISE AB</organization>
      </author>
      <author initials="C." surname="Amsüss" fullname="Christian Amsüss">
         </author>
      <author initials="F." surname="Palombini" fullname="Francesca Palombini">
         <organization>Ericsson AB</organization>
      </author>
      <date month="July" day="6" year="2019" />
      <abstract>
	 <t>   The Constrained Application Protocol (CoAP) allows clients to
   &quot;observe&quot; 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 CoAP clients registered as observers.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-tiloca-core-observe-multicast-notifications-00" />
   
</reference>
