Skip to content

Commit

Permalink
Script updating gh-pages from 3807670. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Oct 16, 2023
1 parent da6751f commit 4ba8e9b
Show file tree
Hide file tree
Showing 2 changed files with 46 additions and 20 deletions.
31 changes: 22 additions & 9 deletions ps-rev/draft-ietf-core-coap-pubsub.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1031,7 +1031,7 @@
</tr></thead>
<tfoot><tr>
<td class="left">Jimenez, et al.</td>
<td class="center">Expires 8 April 2024</td>
<td class="center">Expires 18 April 2024</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
Expand All @@ -1044,12 +1044,12 @@
<dd class="internet-draft">draft-ietf-core-coap-pubsub-latest</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2023-10-06" class="published">6 October 2023</time>
<time datetime="2023-10-16" class="published">16 October 2023</time>
</dd>
<dt class="label-intended-status">Intended Status:</dt>
<dd class="intended-status">Standards Track</dd>
<dt class="label-expires">Expires:</dt>
<dd class="expires"><time datetime="2024-04-08">8 April 2024</time></dd>
<dd class="expires"><time datetime="2024-04-18">18 April 2024</time></dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
Expand Down Expand Up @@ -1106,7 +1106,7 @@ <h2 id="name-status-of-this-memo">
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."<a href="#section-boilerplate.1-3" class="pilcrow"></a></p>
<p id="section-boilerplate.1-4">
This Internet-Draft will expire on 8 April 2024.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
This Internet-Draft will expire on 18 April 2024.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
</section>
</div>
<div id="copyright">
Expand Down Expand Up @@ -1319,7 +1319,7 @@ <h3 id="name-terminology">
<p id="section-1.1-2">This specification requires readers to be familiar with all the terms and
concepts that are discussed in <span>[<a href="#RFC8288" class="cite xref">RFC8288</a>]</span> and <span>[<a href="#RFC6690" class="cite xref">RFC6690</a>]</span>. Readers
should also be familiar with the terms and concepts discussed in
<span>[<a href="#RFC7252" class="cite xref">RFC7252</a>]</span>, <span>[<a href="#RFC9167" class="cite xref">RFC9167</a>]</span> and <span>[<a href="#RFC7641" class="cite xref">RFC7641</a>]</span>. The URI template
<span>[<a href="#RFC7252" class="cite xref">RFC7252</a>]</span>, <span>[<a href="#RFC9176" class="cite xref">RFC9176</a>]</span> and <span>[<a href="#RFC7641" class="cite xref">RFC7641</a>]</span>. The URI template
format <span>[<a href="#RFC6570" class="cite xref">RFC6570</a>]</span> is used to describe the REST API defined in
this specification.<a href="#section-1.1-2" class="pilcrow"></a></p>
<p id="section-1.1-3">This specification makes use of the following terminology:<a href="#section-1.1-3" class="pilcrow"></a></p>
Expand Down Expand Up @@ -1723,7 +1723,20 @@ <h3 id="name-discovery">
<h4 id="name-broker-discovery">
<a href="#section-2.3.1" class="section-number selfRef">2.3.1. </a><a href="#name-broker-discovery" class="section-name selfRef">Broker Discovery</a>
</h4>
<p id="section-2.3.1-1">CoAP clients <span class="bcp14">MAY</span> discover brokers by using CoAP Simple Discovery, via multicast, through a Resource Directory (RD) <span>[<a href="#RFC9167" class="cite xref">RFC9167</a>]</span> or by other means specified in extensions to <span>[<a href="#RFC7252" class="cite xref">RFC7252</a>]</span>. Brokers <span class="bcp14">MAY</span> register with a RD by following the steps on Section 5 of <span>[<a href="#RFC9167" class="cite xref">RFC9167</a>]</span> with the resource type set to "core.ps" as defined in <a href="#iana" class="auto internal xref">Section 6</a> of this document.<a href="#section-2.3.1-1" class="pilcrow"></a></p>
<p id="section-2.3.1-1">CoAP clients <span class="bcp14">MAY</span> discover brokers by using CoAP Simple Discovery, via multicast, through a Resource Directory (RD) <span>[<a href="#RFC9176" class="cite xref">RFC9176</a>]</span> or by other means specified in extensions to <span>[<a href="#RFC7252" class="cite xref">RFC7252</a>]</span>. Brokers <span class="bcp14">MAY</span> register with a RD by following the steps on Section 5 of <span>[<a href="#RFC9176" class="cite xref">RFC9176</a>]</span> with the resource type set to "core.ps" as defined in <a href="#iana" class="auto internal xref">Section 6</a> of this document.<a href="#section-2.3.1-1" class="pilcrow"></a></p>
<p id="section-2.3.1-2">The following example shows an endpoint discovering a broker using the "core.ps" resource type over a multicast network. Brokers within the multicast scope will answer the query.<a href="#section-2.3.1-2" class="pilcrow"></a></p>
<div class="alignLeft art-text artwork" id="section-2.3.1-3">
<pre>
=&gt; 0.01 GET
Uri-Path: coap://[ff0x::fe]/.well-known/core
Resource-Type: core.ps

&lt;= 2.05 Content
Payload:
Content-Format: 40 (application/link-format)
&lt;coap://mythinguri.com/broker/v1&gt;; rt=core.ps
</pre><a href="#section-2.3.1-3" class="pilcrow"></a>
</div>
</section>
</div>
<div id="topic-collection-discovery">
Expand Down Expand Up @@ -2193,7 +2206,7 @@ <h4 id="name-subscribe">
</dd>
<dd class="break"></dd>
</dl>
<p id="section-3.2.2-6">If the 'max-clients' parameter has been reached, the server must treat that as specified in section 4.1 of <span>[<a href="#RFC7641" class="cite xref">RFC7641</a>]</span>. The response <span class="bcp14">MUST NOT</span> include an Observe Option, the absence of which signals to the subscriber that the subscription failed.<a href="#section-3.2.2-6" class="pilcrow"></a></p>
<p id="section-3.2.2-6">If the 'max-subscribers' parameter has been reached, the server must treat that as specified in section 4.1 of <span>[<a href="#RFC7641" class="cite xref">RFC7641</a>]</span>. The response <span class="bcp14">MUST NOT</span> include an Observe Option, the absence of which signals to the subscriber that the subscription failed.<a href="#section-3.2.2-6" class="pilcrow"></a></p>
<p id="section-3.2.2-7">Example:<a href="#section-3.2.2-7" class="pilcrow"></a></p>
<div class="alignLeft art-text artwork" id="section-3.2.2-8">
<pre>
Expand Down Expand Up @@ -2480,9 +2493,9 @@ <h3 id="name-normative-references">
<dd>
<span class="refAuthor">Keranen, A.</span>, <span class="refTitle">""Too Many Requests" Response Code for the Constrained Application Protocol"</span>, <span class="seriesInfo">RFC 8516</span>, <span class="seriesInfo">DOI 10.17487/RFC8516</span>, <time datetime="2019-01" class="refDate">January 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc8516">https://www.rfc-editor.org/rfc/rfc8516</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC9167">[RFC9167]</dt>
<dt id="RFC9176">[RFC9176]</dt>
<dd>
<span class="refAuthor">Sattler, T.</span>, <span class="refAuthor">Carney, R.</span>, and <span class="refAuthor">J. Kolker</span>, <span class="refTitle">"Registry Maintenance Notification for the Extensible Provisioning Protocol (EPP)"</span>, <span class="seriesInfo">RFC 9167</span>, <span class="seriesInfo">DOI 10.17487/RFC9167</span>, <time datetime="2021-12" class="refDate">December 2021</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc9167">https://www.rfc-editor.org/rfc/rfc9167</a>&gt;</span>. </dd>
<span class="refAuthor">Amsüss, C., Ed.</span>, <span class="refAuthor">Shelby, Z.</span>, <span class="refAuthor">Koster, M.</span>, <span class="refAuthor">Bormann, C.</span>, and <span class="refAuthor">P. van der Stok</span>, <span class="refTitle">"Constrained RESTful Environments (CoRE) Resource Directory"</span>, <span class="seriesInfo">RFC 9176</span>, <span class="seriesInfo">DOI 10.17487/RFC9176</span>, <time datetime="2022-04" class="refDate">April 2022</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc9176">https://www.rfc-editor.org/rfc/rfc9176</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
Expand Down
35 changes: 24 additions & 11 deletions ps-rev/draft-ietf-core-coap-pubsub.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,10 @@
Internet Engineering Task Force J. Jimenez
Internet-Draft Ericsson
Intended status: Standards Track M. Koster
Expires: 8 April 2024 Dogtiger Labs
Expires: 18 April 2024 Dogtiger Labs
A. Keranen
Ericsson
6 October 2023
16 October 2023


A publish-subscribe architecture for the Constrained Application
Expand Down Expand Up @@ -54,7 +54,7 @@ Status of This Memo
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."

This Internet-Draft will expire on 8 April 2024.
This Internet-Draft will expire on 18 April 2024.

Copyright Notice

Expand Down Expand Up @@ -156,7 +156,7 @@ Table of Contents
This specification requires readers to be familiar with all the terms
and concepts that are discussed in [RFC8288] and [RFC6690]. Readers
should also be familiar with the terms and concepts discussed in
[RFC7252], [RFC9167] and [RFC7641]. The URI template format
[RFC7252], [RFC9176] and [RFC7641]. The URI template format
[RFC6570] is used to describe the REST API defined in this
specification.

Expand Down Expand Up @@ -411,12 +411,25 @@ Table of Contents
2.3.1. Broker Discovery

CoAP clients MAY discover brokers by using CoAP Simple Discovery, via
multicast, through a Resource Directory (RD) [RFC9167] or by other
multicast, through a Resource Directory (RD) [RFC9176] or by other
means specified in extensions to [RFC7252]. Brokers MAY register
with a RD by following the steps on Section 5 of [RFC9167] with the
with a RD by following the steps on Section 5 of [RFC9176] with the
resource type set to "core.ps" as defined in Section 6 of this
document.

The following example shows an endpoint discovering a broker using
the "core.ps" resource type over a multicast network. Brokers within
the multicast scope will answer the query.

=> 0.01 GET
Uri-Path: coap://[ff0x::fe]/.well-known/core
Resource-Type: core.ps

<= 2.05 Content
Payload:
Content-Format: 40 (application/link-format)
<coap://mythinguri.com/broker/v1>; rt=core.ps

2.3.2. Topic Collection Discovery

A Broker SHOULD offer a topic discovery entry point to enable clients
Expand Down Expand Up @@ -902,7 +915,7 @@ Table of Contents

Failure: 4.04 "Not Found". The topic-data does not exist.

If the 'max-clients' parameter has been reached, the server must
If the 'max-subscribers' parameter has been reached, the server must
treat that as specified in section 4.1 of [RFC7641]. The response
MUST NOT include an Observe Option, the absence of which signals to
the subscriber that the subscription failed.
Expand Down Expand Up @@ -1222,10 +1235,10 @@ Normative References
DOI 10.17487/RFC8516, January 2019,
<https://www.rfc-editor.org/rfc/rfc8516>.

[RFC9167] Sattler, T., Carney, R., and J. Kolker, "Registry
Maintenance Notification for the Extensible Provisioning
Protocol (EPP)", RFC 9167, DOI 10.17487/RFC9167, December
2021, <https://www.rfc-editor.org/rfc/rfc9167>.
[RFC9176] Amsüss, C., Ed., Shelby, Z., Koster, M., Bormann, C., and
P. van der Stok, "Constrained RESTful Environments (CoRE)
Resource Directory", RFC 9176, DOI 10.17487/RFC9176, April
2022, <https://www.rfc-editor.org/rfc/rfc9176>.

Informative References

Expand Down

0 comments on commit 4ba8e9b

Please sign in to comment.