Skip to content

Commit

Permalink
Script updating gh-pages from 69f7ec8. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Nov 23, 2023
1 parent a614795 commit 9f9bfd8
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 10 deletions.
10 changes: 5 additions & 5 deletions secdir-review/draft-ietf-core-oscore-edhoc.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1033,7 +1033,7 @@
</tr></thead>
<tfoot><tr>
<td class="left">Palombini, et al.</td>
<td class="center">Expires 25 May 2024</td>
<td class="center">Expires 26 May 2024</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
Expand All @@ -1046,12 +1046,12 @@
<dd class="internet-draft">draft-ietf-core-oscore-edhoc-latest</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2023-11-22" class="published">22 November 2023</time>
<time datetime="2023-11-23" class="published">23 November 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-05-25">25 May 2024</time></dd>
<dd class="expires"><time datetime="2024-05-26">26 May 2024</time></dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
Expand Down Expand Up @@ -1112,7 +1112,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 25 May 2024.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
This Internet-Draft will expire on 26 May 2024.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
</section>
</div>
<div id="copyright">
Expand Down Expand Up @@ -1587,7 +1587,7 @@ <h2 id="name-edhoc-combined-with-oscore">
<p id="section-3-8.2.2.1.1">C_R is the OSCORE Sender ID of the client and hence transported in the 'kid' field of the OSCORE Option (see <span><a href="https://rfc-editor.org/rfc/rfc8613#section-6.1" class="relref">Section 6.1</a> of [<a href="#RFC8613" class="cite xref">RFC8613</a>]</span>). Unlike in the sequential workflow shown in <a href="#fig-non-combined" class="auto internal xref">Figure 1</a>, C_R is thus not transported in the payload of the EDHOC + OSCORE request.<a href="#section-3-8.2.2.1.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="section-3-8.2.2.2">
<p id="section-3-8.2.2.2.1">EDHOC message_3 is transported in the payload of the EDHOC + OSCORE request prepended to the payload of the OSCORE Request. This is because EDHOC message_3 may be too large to be included in a CoAP Option, e.g., if conveying a large public key certificate chain as ID_CRED_I (see <span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-lake-edhoc-22#section-3.5.3" class="relref">Section 3.5.3</a> of [<a href="#I-D.ietf-lake-edhoc" class="cite xref">I-D.ietf-lake-edhoc</a>]</span>) or if conveying large External Authorization Data as EAD_3 (see <span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-lake-edhoc-22#section-3.8" class="relref">Section 3.8</a> of [<a href="#I-D.ietf-lake-edhoc" class="cite xref">I-D.ietf-lake-edhoc</a>]</span>).<a href="#section-3-8.2.2.2.1" class="pilcrow"></a></p>
<p id="section-3-8.2.2.2.1">EDHOC message_3 is transported in the payload of the EDHOC + OSCORE request prepended to the payload of the OSCORE Request. This is because EDHOC message_3 may be too large to be included in a CoAP Option, e.g., when conveying a large public key certificate chain as ID_CRED_I (see <span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-lake-edhoc-22#section-3.5.3" class="relref">Section 3.5.3</a> of [<a href="#I-D.ietf-lake-edhoc" class="cite xref">I-D.ietf-lake-edhoc</a>]</span>) or when conveying large External Authorization Data as EAD_3 (see <span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-lake-edhoc-22#section-3.8" class="relref">Section 3.8</a> of [<a href="#I-D.ietf-lake-edhoc" class="cite xref">I-D.ietf-lake-edhoc</a>]</span>).<a href="#section-3-8.2.2.2.1" class="pilcrow"></a></p>
</li>
</ul>
</li>
Expand Down
10 changes: 5 additions & 5 deletions secdir-review/draft-ietf-core-oscore-edhoc.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5,13 +5,13 @@
CoRE Working Group F. Palombini
Internet-Draft Ericsson
Intended status: Standards Track M. Tiloca
Expires: 25 May 2024 R. Höglund
Expires: 26 May 2024 R. Höglund
RISE AB
S. Hristozov
Fraunhofer AISEC
G. Selander
Ericsson
22 November 2023
23 November 2023


Using EDHOC with CoAP and OSCORE
Expand Down Expand Up @@ -55,7 +55,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 25 May 2024.
This Internet-Draft will expire on 26 May 2024.

Copyright Notice

Expand Down Expand Up @@ -375,9 +375,9 @@ Table of Contents
- EDHOC message_3 is transported in the payload of the EDHOC +
OSCORE request prepended to the payload of the OSCORE Request.
This is because EDHOC message_3 may be too large to be included
in a CoAP Option, e.g., if conveying a large public key
in a CoAP Option, e.g., when conveying a large public key
certificate chain as ID_CRED_I (see Section 3.5.3 of
[I-D.ietf-lake-edhoc]) or if conveying large External
[I-D.ietf-lake-edhoc]) or when conveying large External
Authorization Data as EAD_3 (see Section 3.8 of
[I-D.ietf-lake-edhoc]).

Expand Down

0 comments on commit 9f9bfd8

Please sign in to comment.