You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<ahref="#name-publish-subscribe-architect" class="selfRef">Publish-subscribe architecture over CoAP</a>
1439
1439
</figcaption></figure>
1440
1440
</div>
1441
-
<pid="section-1.2-6">This document describes two sets of interactions, interactions to configure topics and their lifecycle (see <ahref="#topic-configuration-interactions" class="auto internal xref">Section 2.5</a>) and interactions about the topic-data (see <ahref="#topic-data-interactions" class="auto internal xref">Section 3.2</a>).<ahref="#section-1.2-6" class="pilcrow">¶</a></p>
1441
+
<pid="section-1.2-6">This document describes two sets of interactions; interactions to configure topics and their lifecycle (see <ahref="#topic-configuration-interactions" class="auto internal xref">Section 2.5</a>) and interactions about the topic-data (see <ahref="#topic-data-interactions" class="auto internal xref">Section 3.2</a>).<ahref="#section-1.2-6" class="pilcrow">¶</a></p>
1442
1442
<pid="section-1.2-7">Topic-configuration interactions are discovery, create, read configuration, update configuration, and delete configuration. These operations handle the management of the topics.<ahref="#section-1.2-7" class="pilcrow">¶</a></p>
1443
1443
<pid="section-1.2-8">Topic-data interactions are publish, subscribe, unsubscribe, read, and delete. These operations are oriented on how data is transferred from a publisher to a subscriber.<ahref="#section-1.2-8" class="pilcrow">¶</a></p>
<pid="appendix-B-1">The current version of this document contains a substantial contribution by Klaus Hartke's proposal <span>[<ahref="#I-D.hartke-t2trg-coral-pubsub" class="cite xref">I-D.hartke-t2trg-coral-pubsub</a>]</span>, which defines the topic resource model and structure as well as the topic lifecycle and interactions. It also follows a similar architectural design as that provided by Marco Tiloca's <span>[<ahref="#I-D.ietf-ace-oscore-gm-admin" class="cite xref">I-D.ietf-ace-oscore-gm-admin</a>]</span>.<ahref="#appendix-B-1" class="pilcrow">¶</a></p>
2904
-
<pid="appendix-B-2">The authors would like to also thank <spanclass="contact-name">Marco Tiloca</span>, <spanclass="contact-name">Carsten Bormann</span>, <spanclass="contact-name">Hannes Tschofenig</span>, <spanclass="contact-name">Zach Shelby</span>, <spanclass="contact-name">Mohit Sethi</span>, Peter van der Stok, Tim Kellogg, Anders Eriksson, <spanclass="contact-name">Goran Selander</span>, Mikko Majanen, <spanclass="contact-name">Olaf Bergmann</span>, <spanclass="contact-name">David Navarro</span> and Oscar Novo for their valuable contributions and reviews.<ahref="#appendix-B-2" class="pilcrow">¶</a></p>
2904
+
<pid="appendix-B-2">The authors would like to also thank <spanclass="contact-name">Marco Tiloca</span>, <spanclass="contact-name">Carsten Bormann</span>, <spanclass="contact-name">Hannes Tschofenig</span>, <spanclass="contact-name">Zach Shelby</span>, <spanclass="contact-name">Mohit Sethi</span>, Peter van der Stok, Tim Kellogg, Anders Eriksson, <spanclass="contact-name">Goran Selander</span>, Mikko Majanen, <spanclass="contact-name">Olaf Bergmann</span>, <spanclass="contact-name">David Navarro</span>, Oscar Novo and Lorenzo Corneo for their valuable contributions and reviews.<ahref="#appendix-B-2" class="pilcrow">¶</a></p>
0 commit comments