Skip to content

Commit

Permalink
Script updating gh-pages from 9f7e3b8. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Dec 19, 2024
1 parent b7007ff commit 1481633
Show file tree
Hide file tree
Showing 3 changed files with 40 additions and 40 deletions.
16 changes: 8 additions & 8 deletions draft-ietf-core-corr-clar.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1059,7 +1059,7 @@
</tr></thead>
<tfoot><tr>
<td class="left">Bormann</td>
<td class="center">Expires 21 June 2025</td>
<td class="center">Expires 22 June 2025</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
Expand All @@ -1075,12 +1075,12 @@
<a href="https://www.rfc-editor.org/rfc/rfc6690" class="eref">6690</a>, <a href="https://www.rfc-editor.org/rfc/rfc7252" class="eref">7252</a>, <a href="https://www.rfc-editor.org/rfc/rfc7641" class="eref">7641</a>, <a href="https://www.rfc-editor.org/rfc/rfc7959" class="eref">7959</a>, <a href="https://www.rfc-editor.org/rfc/rfc8132" class="eref">8132</a>, <a href="https://www.rfc-editor.org/rfc/rfc8323" class="eref">8323</a> (if approved)</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2024-12-18" class="published">18 December 2024</time>
<time datetime="2024-12-19" class="published">19 December 2024</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="2025-06-21">21 June 2025</time></dd>
<dd class="expires"><time datetime="2025-06-22">22 June 2025</time></dd>
<dt class="label-authors">Author:</dt>
<dd class="authors">
<div class="author">
Expand Down Expand Up @@ -1141,7 +1141,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 21 June 2025.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
This Internet-Draft will expire on 22 June 2025.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
</section>
</div>
<div id="copyright">
Expand Down Expand Up @@ -1830,7 +1830,7 @@ <h4 id="name-replay-protection">
when all the security mechanism's guarantees are available.
Instead, servers can send 4.01 Unauthorized responses with Echo option;
clients then repeat the request with the Echo value in the request.<a href="#section-2.6.2-5" class="pilcrow"></a></p>
<p id="section-2.6.2-6">[Appendix B.1.2 of RFC8613] describes how this is used to recover loss of state in OSCORE.
<p id="section-2.6.2-6"><span><a href="https://rfc-editor.org/rfc/rfc8613#appendix-B.1.2" class="relref">Appendix B.1.2</a> of [<a href="#RFC8613" class="cite xref">RFC8613</a>]</span> describes how this is used to recover loss of state in OSCORE.
Exceeding what is described there, a server can safely send a successful response,
provided its criteria for 0RTT responses are met.
The server can still send an Echo option with the successful response:
Expand All @@ -1839,7 +1839,7 @@ <h4 id="name-replay-protection">
<p id="section-2.6.2-7">Implementers of OSCORE should be aware that answering potential replays can only be determined to be safe from the CoAP application's point of view.
As always, unless the sequence number in the request has just been removed from an initialized replay window,
the response can not reuse the request's nonce, but needs to be sent with a new sequence number from the server's space.<a href="#section-2.6.2-7" class="pilcrow"></a></p>
<p id="section-2.6.2-8">Requests with 0RTT properties currently cannot happen in DTLS because 0-RTT Data is not allowed for CoAP (cf. <span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-uta-tls13-iot-profile-09#section-14" class="relref">Section 14</a> of [<a href="#I-D.ietf-uta-tls13-iot-profile-09" class="cite xref">I-D.ietf-uta-tls13-iot-profile-09</a>]</span>). However, that may change if a future document defines a profile for using early data with CoAP.<a href="#section-2.6.2-8" class="pilcrow"></a></p>
<p id="section-2.6.2-8">Requests with 0RTT properties currently cannot happen in DTLS because 0-RTT Data is not allowed for CoAP (cf. <span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-uta-tls13-iot-profile-11#section-14" class="relref">Section 14</a> of [<a href="#I-D.ietf-uta-tls13-iot-profile" class="cite xref">I-D.ietf-uta-tls13-iot-profile</a>]</span>). However, that may change if a future document defines a profile for using early data with CoAP.<a href="#section-2.6.2-8" class="pilcrow"></a></p>
</section>
</div>
</section>
Expand Down Expand Up @@ -2023,9 +2023,9 @@ <h3 id="name-informative-references">
<dd>
<span class="refAuthor">Tschofenig, H.</span>, <span class="refAuthor">Kraus, A.</span>, and <span class="refAuthor">T. Fossati</span>, <span class="refTitle">"Return Routability Check for DTLS 1.2 and DTLS 1.3"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-tls-dtls-rrc-12</span>, <time datetime="2024-09-24" class="refDate">24 September 2024</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-tls-dtls-rrc-12">https://datatracker.ietf.org/doc/html/draft-ietf-tls-dtls-rrc-12</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="I-D.ietf-uta-tls13-iot-profile-09">[I-D.ietf-uta-tls13-iot-profile-09]</dt>
<dt id="I-D.ietf-uta-tls13-iot-profile">[I-D.ietf-uta-tls13-iot-profile]</dt>
<dd>
<span class="refAuthor">Tschofenig, H.</span>, <span class="refAuthor">Fossati, T.</span>, and <span class="refAuthor">M. Richardson</span>, <span class="refTitle">"TLS/DTLS 1.3 Profiles for the Internet of Things"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-uta-tls13-iot-profile-09</span>, <time datetime="2024-03-03" class="refDate">3 March 2024</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-uta-tls13-iot-profile-09">https://datatracker.ietf.org/doc/html/draft-ietf-uta-tls13-iot-profile-09</a>&gt;</span>. </dd>
<span class="refAuthor">Tschofenig, H.</span>, <span class="refAuthor">Fossati, T.</span>, and <span class="refAuthor">M. Richardson</span>, <span class="refTitle">"TLS/DTLS 1.3 Profiles for the Internet of Things"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-uta-tls13-iot-profile-11</span>, <time datetime="2024-10-20" class="refDate">20 October 2024</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-uta-tls13-iot-profile-11">https://datatracker.ietf.org/doc/html/draft-ietf-uta-tls13-iot-profile-11</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="I-D.irtf-t2trg-amplification-attacks">[I-D.irtf-t2trg-amplification-attacks]</dt>
<dd>
Expand Down
62 changes: 31 additions & 31 deletions draft-ietf-core-corr-clar.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,10 @@

Network Working Group C. Bormann
Internet-Draft Universität Bremen TZI
Updates: 6690, 7252, 7641, 7959, 8132, 8323 (if 18 December 2024
Updates: 6690, 7252, 7641, 7959, 8132, 8323 (if 19 December 2024
approved)
Intended status: Standards Track
Expires: 21 June 2025
Expires: 22 June 2025


Constrained Application Protocol (CoAP): Corrections and Clarifications
Expand Down Expand Up @@ -53,7 +53,7 @@ Status of This Memo



Bormann Expires 21 June 2025 [Page 1]
Bormann Expires 22 June 2025 [Page 1]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand All @@ -68,7 +68,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024
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 21 June 2025.
This Internet-Draft will expire on 22 June 2025.

Copyright Notice

Expand Down Expand Up @@ -109,7 +109,7 @@ Table of Contents



Bormann Expires 21 June 2025 [Page 2]
Bormann Expires 22 June 2025 [Page 2]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -165,7 +165,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 3]
Bormann Expires 22 June 2025 [Page 3]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -221,7 +221,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 4]
Bormann Expires 22 June 2025 [Page 4]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -277,7 +277,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 5]
Bormann Expires 22 June 2025 [Page 5]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -333,7 +333,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 6]
Bormann Expires 22 June 2025 [Page 6]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -389,7 +389,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 7]
Bormann Expires 22 June 2025 [Page 7]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -445,7 +445,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 8]
Bormann Expires 22 June 2025 [Page 8]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -501,7 +501,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 9]
Bormann Expires 22 June 2025 [Page 9]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -557,7 +557,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 10]
Bormann Expires 22 June 2025 [Page 10]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -613,7 +613,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 11]
Bormann Expires 22 June 2025 [Page 11]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -669,7 +669,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 12]
Bormann Expires 22 June 2025 [Page 12]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -725,7 +725,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 13]
Bormann Expires 22 June 2025 [Page 13]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -781,7 +781,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 14]
Bormann Expires 22 June 2025 [Page 14]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -837,7 +837,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 15]
Bormann Expires 22 June 2025 [Page 15]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -893,7 +893,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 16]
Bormann Expires 22 June 2025 [Page 16]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand All @@ -918,7 +918,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024
send 4.01 Unauthorized responses with Echo option; clients then
repeat the request with the Echo value in the request.

[Appendix B.1.2 of RFC8613] describes how this is used to recover
Appendix B.1.2 of [RFC8613] describes how this is used to recover
loss of state in OSCORE. Exceeding what is described there, a server
can safely send a successful response, provided its criteria for 0RTT
responses are met. The server can still send an Echo option with the
Expand All @@ -934,7 +934,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024

Requests with 0RTT properties currently cannot happen in DTLS because
0-RTT Data is not allowed for CoAP (cf. Section 14 of
[I-D.ietf-uta-tls13-iot-profile-09]). However, that may change if a
[I-D.ietf-uta-tls13-iot-profile]). However, that may change if a
future document defines a profile for using early data with CoAP.

2.7. RFC 7252-12.3: Content-Format Registry
Expand All @@ -949,7 +949,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 17]
Bormann Expires 22 June 2025 [Page 17]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -1005,7 +1005,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 18]
Bormann Expires 22 June 2025 [Page 18]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -1061,7 +1061,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 19]
Bormann Expires 22 June 2025 [Page 19]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -1117,7 +1117,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 20]
Bormann Expires 22 June 2025 [Page 20]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -1151,13 +1151,13 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024
September 2024, <https://datatracker.ietf.org/doc/html/
draft-ietf-tls-dtls-rrc-12>.

[I-D.ietf-uta-tls13-iot-profile-09]
[I-D.ietf-uta-tls13-iot-profile]
Tschofenig, H., Fossati, T., and M. Richardson, "TLS/DTLS
1.3 Profiles for the Internet of Things", Work in
Progress, Internet-Draft, draft-ietf-uta-tls13-iot-
profile-09, 3 March 2024,
profile-11, 20 October 2024,
<https://datatracker.ietf.org/doc/html/draft-ietf-uta-
tls13-iot-profile-09>.
tls13-iot-profile-11>.

[I-D.irtf-t2trg-amplification-attacks]
Mattsson, J. P., Selander, G., and C. Amsüss,
Expand All @@ -1173,7 +1173,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 21]
Bormann Expires 22 June 2025 [Page 21]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -1229,7 +1229,7 @@ Internet-Draft Corrections and Clarifications to CoAP December 2024



Bormann Expires 21 June 2025 [Page 22]
Bormann Expires 22 June 2025 [Page 22]

Internet-Draft Corrections and Clarifications to CoAP December 2024

Expand Down Expand Up @@ -1285,4 +1285,4 @@ Author's Address



Bormann Expires 21 June 2025 [Page 23]
Bormann Expires 22 June 2025 [Page 23]
2 changes: 1 addition & 1 deletion index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ <h2>Preview for branch <a href="amplification-and-0rtt">amplification-and-0rtt</
<tr>
<td><a href="amplification-and-0rtt/draft-ietf-core-corr-clar.html" class="html draft-ietf-core-corr-clar" title="Constrained Application Protocol (CoAP): Corrections and Clarifications (HTML)">Corrections and Clarifications to CoAP</a></td>
<td><a href="amplification-and-0rtt/draft-ietf-core-corr-clar.txt" class="txt draft-ietf-core-corr-clar" title="Constrained Application Protocol (CoAP): Corrections and Clarifications (Text)">plain text</a></td>
<td>same as main</td>
<td><a href="https://author-tools.ietf.org/api/iddiff?url_1=https://core-wg.github.io/corrclar/draft-ietf-core-corr-clar.txt&amp;url_2=https://core-wg.github.io/corrclar/amplification-and-0rtt/draft-ietf-core-corr-clar.txt" class="diff draft-ietf-core-corr-clar">diff with main</a></td>
</tr>
</table>
<script>
Expand Down

0 comments on commit 1481633

Please sign in to comment.