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

Author: ID Bot

draft-ietf-cose-cbor-encoded-cert.html

@@ -6665,7 +6665,7 @@ <h3 id="name-coap-content-formats-regist">
         <h3 id="name-tls-certificate-types-regis">
 <a href="#section-9.17" class="section-number selfRef">9.17. </a><a href="#name-tls-certificate-types-regis" class="section-name selfRef">TLS Certificate Types Registry</a>
         </h3>
-<p id="section-9.17-1">This document registers the following entry in the "TLS Certificate Types" registry under the "Transport Layer Security (TLS) Extensions" heading. The new certificate type can be used with additional TLS certificate compression <span>[<a href="#RFC8879" class="cite xref">RFC8879</a>]</span>. C509 is defined in the same way as as X.509, but uses a different value and instead of DER-encoded X.509 certificate, opaque cert_data&lt;1..2^24-1&gt; contains a the CBOR sequence ~C509Certificate (an unwrapped C509Certificate).<a href="#section-9.17-1" class="pilcrow">¶</a></p>
+<p id="section-9.17-1">This document registers the following entry in the "TLS Certificate Types" registry under the "Transport Layer Security (TLS) Extensions" heading. The new certificate type can be used with additional TLS certificate compression <span>[<a href="#RFC8879" class="cite xref">RFC8879</a>]</span>. C509 is defined in the same way as as X.509, but uses a different value and instead of DER-encoded X.509 certificate, opaque cert_data&lt;1..2^24-1&gt; in TLS 1.3 and opaque ASN.1Cert&lt;1..2^24-1&gt; in TLS 1.2 contains a the CBOR sequence ~C509Certificate (an unwrapped C509Certificate). Similar to COSE_C509, the TLS handshake contains the length of each certificate. The TLS extensions client_certificate_type and server_certificate_type <span>[<a href="#RFC7250" class="cite xref">RFC7250</a>]</span> are used to negotiate the use of C509.<a href="#section-9.17-1" class="pilcrow">¶</a></p>
 <div id="section-9.17-2">
           <div class="alignLeft art-svg artwork" id="section-9.17-2.1">
 <svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="112" width="560" viewBox="0 0 560 112" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
@@ -6821,6 +6821,10 @@ <h3 id="name-normative-references">
         <dd>
 <span class="refAuthor">Cotton, M.</span>, <span class="refTitle">"Early IANA Allocation of Standards Track Code Points"</span>, <span class="seriesInfo">BCP 100</span>, <span class="seriesInfo">RFC 7120</span>, <span class="seriesInfo">DOI 10.17487/RFC7120</span>, <time datetime="2014-01" class="refDate">January 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc7120">https://www.rfc-editor.org/rfc/rfc7120</a>&gt;</span>. </dd>
 <dd class="break"></dd>
+<dt id="RFC7250">[RFC7250]</dt>
+        <dd>
+<span class="refAuthor">Wouters, P., Ed.</span>, <span class="refAuthor">Tschofenig, H., Ed.</span>, <span class="refAuthor">Gilmore, J.</span>, <span class="refAuthor">Weiler, S.</span>, and <span class="refAuthor">T. Kivinen</span>, <span class="refTitle">"Using Raw Public Keys in Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)"</span>, <span class="seriesInfo">RFC 7250</span>, <span class="seriesInfo">DOI 10.17487/RFC7250</span>, <time datetime="2014-06" class="refDate">June 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc7250">https://www.rfc-editor.org/rfc/rfc7250</a>&gt;</span>. </dd>
+<dd class="break"></dd>
 <dt id="RFC8126">[RFC8126]</dt>
         <dd>
 <span class="refAuthor">Cotton, M.</span>, <span class="refAuthor">Leiba, B.</span>, and <span class="refAuthor">T. Narten</span>, <span class="refTitle">"Guidelines for Writing an IANA Considerations Section in RFCs"</span>, <span class="seriesInfo">BCP 26</span>, <span class="seriesInfo">RFC 8126</span>, <span class="seriesInfo">DOI 10.17487/RFC8126</span>, <time datetime="2017-06" class="refDate">June 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc8126">https://www.rfc-editor.org/rfc/rfc8126</a>&gt;</span>. </dd>

draft-ietf-cose-cbor-encoded-cert.txt

@@ -2924,8 +2924,13 @@ Table of Contents
    heading.  The new certificate type can be used with additional TLS
    certificate compression [RFC8879].  C509 is defined in the same way
    as as X.509, but uses a different value and instead of DER-encoded
-   X.509 certificate, opaque cert_data<1..2^24-1> contains a the CBOR
-   sequence ~C509Certificate (an unwrapped C509Certificate).
+   X.509 certificate, opaque cert_data<1..2^24-1> in TLS 1.3 and opaque
+   ASN.1Cert<1..2^24-1> in TLS 1.2 contains a the CBOR sequence
+   ~C509Certificate (an unwrapped C509Certificate).  Similar to
+   COSE_C509, the TLS handshake contains the length of each certificate.
+   The TLS extensions client_certificate_type and
+   server_certificate_type [RFC7250] are used to negotiate the use of
+   C509.
 
    +-------+------------------+-------------+--------------------------+
    | Value | Name             | Recommended | Comment                  |
@@ -3021,6 +3026,12 @@ Table of Contents
               Points", BCP 100, RFC 7120, DOI 10.17487/RFC7120, January
               2014, <https://www.rfc-editor.org/rfc/rfc7120>.
 
+   [RFC7250]  Wouters, P., Ed., Tschofenig, H., Ed., Gilmore, J.,
+              Weiler, S., and T. Kivinen, "Using Raw Public Keys in
+              Transport Layer Security (TLS) and Datagram Transport
+              Layer Security (DTLS)", RFC 7250, DOI 10.17487/RFC7250,
+              June 2014, <https://www.rfc-editor.org/rfc/rfc7250>.
+
    [RFC8126]  Cotton, M., Leiba, B., and T. Narten, "Guidelines for
               Writing an IANA Considerations Section in RFCs", BCP 26,
               RFC 8126, DOI 10.17487/RFC8126, June 2017,