Script updating gh-pages from c2c7d6d. [ci skip]

draft-ietf-core-oscore-edhoc.html

@@ -1578,7 +1578,7 @@ <h2 id="name-edhoc-combined-with-oscore">
         </figcaption></figure>
 </div>
 <p id="section-3-6">To this end, the specific approach defined in this section consists of sending a single EDHOC + OSCORE request, which conveys the pair (C_R, EDHOC message_3) within an OSCORE-protected CoAP message.<a href="#section-3-6" class="pilcrow">¶</a></p>
-<p id="section-3-7">That is, the EDHOC + OSCORE request is composed of the following two parts combined together in a single CoAP message:<a href="#section-3-7" class="pilcrow">¶</a></p>
+<p id="section-3-7">That is, the EDHOC + OSCORE request is composed of the following two parts combined together in a single CoAP message. The steps for processing the EDHOC + OSCORE request and the two parts combined in there are defined in <a href="#client-processing" class="auto internal xref">Section 3.2.1</a> and <a href="#server-processing" class="auto internal xref">Section 3.3.1</a>.<a href="#section-3-7" class="pilcrow">¶</a></p>
 <ul class="normal">
 <li class="normal" id="section-3-8.1">
           <p id="section-3-8.1.1">The OSCORE Request from <a href="#fig-non-combined" class="auto internal xref">Figure 1</a>, which is also in this case sent to a protected resource, with the correct CoAP method and options intended for accessing that resource.<a href="#section-3-8.1.1" class="pilcrow">¶</a></p>
@@ -1590,7 +1590,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., 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>
+              <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>
@@ -2604,7 +2604,7 @@ <h3 id="name-version-00-to-01">
       <h2 id="name-acknowledgments">
 <a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a>
       </h2>
-<p id="appendix-B-1">The authors sincerely thank <span class="contact-name">Christian Amsüss</span>, <span class="contact-name">Carsten Bormann</span>, <span class="contact-name">Esko Dijk</span>, <span class="contact-name">Wes Hardaker</span>, <span class="contact-name">Klaus Hartke</span>, <span class="contact-name">John Preuß Mattsson</span>, <span class="contact-name">David Navarro</span>, <span class="contact-name">Jim Schaad</span>, <span class="contact-name">Jürgen Schönwälder</span>, <span class="contact-name">Mališa Vučinić</span>, and <span class="contact-name">Paul Wouters</span> for their feedback and comments.<a href="#appendix-B-1" class="pilcrow">¶</a></p>
+<p id="appendix-B-1">The authors sincerely thank <span class="contact-name">Christian Amsüss</span>, <span class="contact-name">Carsten Bormann</span>, <span class="contact-name">Esko Dijk</span>, <span class="contact-name">Joel Halpern</span>, <span class="contact-name">Wes Hardaker</span>, <span class="contact-name">Klaus Hartke</span>, <span class="contact-name">John Preuß Mattsson</span>, <span class="contact-name">David Navarro</span>, <span class="contact-name">Jim Schaad</span>, <span class="contact-name">Jürgen Schönwälder</span>, <span class="contact-name">Mališa Vučinić</span>, and <span class="contact-name">Paul Wouters</span> for their feedback and comments.<a href="#appendix-B-1" class="pilcrow">¶</a></p>
 <p id="appendix-B-2">The work on this document has been partly supported by VINNOVA and the Celtic-Next project CRITISEC; and by the H2020 project SIFIS-Home (Grant agreement 952652).<a href="#appendix-B-2" class="pilcrow">¶</a></p>
 </section>
 </div>

draft-ietf-core-oscore-edhoc.txt

@@ -362,7 +362,9 @@ Table of Contents
    (C_R, EDHOC message_3) within an OSCORE-protected CoAP message.
 
    That is, the EDHOC + OSCORE request is composed of the following two
-   parts combined together in a single CoAP message:
+   parts combined together in a single CoAP message.  The steps for
+   processing the EDHOC + OSCORE request and the two parts combined in
+   there are defined in Section 3.2.1 and Section 3.3.1.
 
    *  The OSCORE Request from Figure 1, which is also in this case sent
       to a protected resource, with the correct CoAP method and options
@@ -378,7 +380,7 @@ Table of Contents
          EDHOC + OSCORE request.
 
       -  EDHOC message_3 is transported in the payload of the EDHOC +
-         OSCORE request prepended to the payload of the OSCORE Request.
+         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 Section 3.5.3 of
@@ -1406,9 +1408,9 @@ A.10.  Version -00 to -01
 Acknowledgments
 
    The authors sincerely thank Christian Amsüss, Carsten Bormann, Esko
-   Dijk, Wes Hardaker, Klaus Hartke, John Preuß Mattsson, David Navarro,
-   Jim Schaad, Jürgen Schönwälder, Mališa Vučinić, and Paul Wouters for
-   their feedback and comments.
+   Dijk, Joel Halpern, Wes Hardaker, Klaus Hartke, John Preuß Mattsson,
+   David Navarro, Jim Schaad, Jürgen Schönwälder, Mališa Vučinić, and
+   Paul Wouters for their feedback and comments.
 
    The work on this document has been partly supported by VINNOVA and
    the Celtic-Next project CRITISEC; and by the H2020 project SIFIS-Home

index.html

@@ -29,7 +29,7 @@ <h2>Preview for branch <a href="genart-review">genart-review</a></h2>
       <tr>
         <td><a href="genart-review/draft-ietf-core-oscore-edhoc.html" class="html draft-ietf-core-oscore-edhoc" title="Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) (HTML)">Using EDHOC with CoAP and OSCORE</a></td>
         <td><a href="genart-review/draft-ietf-core-oscore-edhoc.txt" class="txt draft-ietf-core-oscore-edhoc" title="Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) (Text)">plain text</a></td>
-        <td><a href="https://author-tools.ietf.org/api/iddiff?url_1=https://core-wg.github.io/oscore-edhoc/draft-ietf-core-oscore-edhoc.txt&amp;url_2=https://core-wg.github.io/oscore-edhoc/genart-review/draft-ietf-core-oscore-edhoc.txt" class="diff draft-ietf-core-oscore-edhoc">diff with main</a></td>
+        <td>same as main</td>
       </tr>
     </table>
     <h2>Preview for branch <a href="secdir-review">secdir-review</a></h2>
@@ -53,7 +53,7 @@ <h2>Preview for branch <a href="opsdir-review">opsdir-review</a></h2>
       <tr>
         <td><a href="opsdir-review/draft-ietf-core-oscore-edhoc.html" class="html draft-ietf-core-oscore-edhoc" title="Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) (HTML)">Using EDHOC with CoAP and OSCORE</a></td>
         <td><a href="opsdir-review/draft-ietf-core-oscore-edhoc.txt" class="txt draft-ietf-core-oscore-edhoc" title="Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE) (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/oscore-edhoc/draft-ietf-core-oscore-edhoc.txt&amp;url_2=https://core-wg.github.io/oscore-edhoc/opsdir-review/draft-ietf-core-oscore-edhoc.txt" class="diff draft-ietf-core-oscore-edhoc">diff with main</a></td>
       </tr>
     </table>
     <script>