Skip to content

Commit

Permalink
Script updating gh-pages from 0eb309f. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Oct 23, 2023
1 parent 6ead31b commit e5ab8a8
Show file tree
Hide file tree
Showing 5 changed files with 145 additions and 172 deletions.
148 changes: 67 additions & 81 deletions draft-ietf-lamps-kyber-certificates.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -14,32 +14,30 @@
algorithm identifiers and ASN.1 encoding format for Kyber in public
key certificates. The encoding for public and private keys are also
provided.
[EDNOTE:
\ [EDNOTE:
This document is not expected to be finalized before the NIST PQC
Project has standardized PQ algorithms. This specification will use
object identifiers for the new algorithms that are assigned by NIST,
and will use placeholders until these are released.]
and will use placeholders until these are released.
" name="description">
<meta content="xml2rfc 3.17.0" name="generator">
<meta content="xml2rfc 3.18.2" name="generator">
<meta content="Kyber KEM Certificate X.509 PKIX" name="keyword">
<meta content="draft-ietf-lamps-kyber-certificates-latest" name="ietf.draft">
<!-- Generator version information:
xml2rfc 3.17.0
Python 3.10.10
appdirs 1.4.4
xml2rfc 3.18.2
Python 3.11.6
ConfigArgParse 1.5.3
google-i18n-address 2.5.2
html5lib 1.1
google-i18n-address 3.1.0
intervaltree 3.1.0
Jinja2 3.1.2
lxml 4.9.2
MarkupSafe 2.1.1
lxml 4.9.3
platformdirs 3.11.0
pycountry 22.3.5
PyYAML 6.0
requests 2.28.1
setuptools 65.6.0
requests 2.31.0
setuptools 67.7.2
six 1.16.0
wcwidth 0.2.6
wcwidth 0.2.8
-->
<link href="draft-ietf-lamps-kyber-certificates.xml" rel="alternate" type="application/rfc+xml">
<link href="#copyright" rel="license">
Expand Down Expand Up @@ -621,6 +619,7 @@
clear: left;
float: left;
text-align: right;
margin-right: 1ch;
}
#identifiers dd {
margin: 0;
Expand Down Expand Up @@ -661,7 +660,7 @@
}
#toc nav li {
line-height: 1.3em;
margin: 0.75em 0;
margin: 2px 0;
padding-left: 1.2em;
text-indent: -1.2em;
}
Expand All @@ -672,15 +671,16 @@
.references dt {
text-align: right;
font-weight: bold;
min-width: 7em;
min-width: 10ch;
margin-right: 1.5ch;
}
.references dt:target::before {
content: "⇒";
width: 15px;
margin: 0 10px 0 -25px;
}
.references dd {
margin-left: 8em !important;
margin-left: 12ch !important;
overflow: auto;
}

Expand Down Expand Up @@ -753,7 +753,7 @@
z-index: 2;
top: 0;
right: 0;
padding: 0;
padding: 1px 0 0 0;
margin: 0;
border-bottom: 1px solid #ccc;
opacity: 0.6;
Expand Down Expand Up @@ -877,16 +877,13 @@
border-top: none;
padding-top: 0;
}
figure, pre {
figure, pre, .vcard {
page-break-inside: avoid;
}
figure {
overflow: scroll;
}
h1, h2, h3, h4, h5, h6 {
page-break-after: avoid;
}
h2+*, h3+*, h4+*, h5+*, h6+* {
:is(h2, h3, h4, h5, h6)+*, dd {
page-break-before: avoid;
}
pre {
Expand All @@ -900,6 +897,9 @@
td {
border-top: 1px solid #ddd;
}
.toplink {
display: none;
}
}

@page :first {
Expand Down Expand Up @@ -1000,28 +1000,6 @@
text-align: right;
}

/* Give the table caption label the same styling as the figcaption */

@media print {
.toplink {
display: none;
}

/* avoid overwriting the top border line with the ToC header */
#toc {
padding-top: 1px;
}

/* Avoid page breaks inside dl and author address entries */
dd {
page-break-before: avoid;
}
.vcard {
page-break-inside: avoid;
}

}

/* Dark mode. */
@media (prefers-color-scheme: dark) {
:root {
Expand Down Expand Up @@ -1058,11 +1036,11 @@
<thead><tr>
<td class="left">Internet-Draft</td>
<td class="center">PQC Kyber in Certificates</td>
<td class="right">March 2023</td>
<td class="right">October 2023</td>
</tr></thead>
<tfoot><tr>
<td class="left">Turner, et al.</td>
<td class="center">Expires 29 September 2023</td>
<td class="center">Expires 25 April 2024</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
Expand All @@ -1075,12 +1053,12 @@
<dd class="internet-draft">draft-ietf-lamps-kyber-certificates-latest</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2023-03-28" class="published">28 March 2023</time>
<time datetime="2023-10-23" class="published">23 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="2023-09-29">29 September 2023</time></dd>
<dd class="expires"><time datetime="2024-04-25">25 April 2024</time></dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
Expand Down Expand Up @@ -1109,11 +1087,11 @@ <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
algorithm identifiers and ASN.1 encoding format for Kyber in public
key certificates. The encoding for public and private keys are also
provided.<a href="#section-abstract-1" class="pilcrow"></a></p>
<p id="section-abstract-2">[EDNOTE:
<p id="section-abstract-2">\ [EDNOTE:
This document is not expected to be finalized before the NIST PQC
Project has standardized PQ algorithms. This specification will use
object identifiers for the new algorithms that are assigned by NIST,
and will use placeholders until these are released.]<a href="#section-abstract-2" class="pilcrow"></a></p>
and will use placeholders until these are released.<a href="#section-abstract-2" class="pilcrow"></a></p>
</section>
<section class="note rfcEditorRemove" id="section-note.1">
<h2 id="name-about-this-document">
Expand Down Expand Up @@ -1150,7 +1128,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 29 September 2023.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
This Internet-Draft will expire on 25 April 2024.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
</section>
</div>
<div id="copyright">
Expand Down Expand Up @@ -1304,27 +1282,29 @@ <h2 id="name-algorithm-identifiers">
</pre><a href="#section-3-3" class="pilcrow"></a>
</div>
<aside id="section-3-4">
<p id="section-3-4.1">NOTE: The above syntax is from <span>[<a href="#RFC5912" class="cite xref">RFC5912</a>]</span> and is compatible with the
2021 ASN.1 syntax <span>[<a href="#X680" class="cite xref">X680</a>]</span>.<a href="#section-3-4.1" class="pilcrow"></a></p>
<p id="section-3-4.1">: The above syntax is from <span>[<a href="#RFC5912" class="cite xref">RFC5912</a>]</span> and is compatible with the
2021 ASN.1 syntax <span>[<a href="#X680" class="cite xref">X680</a>]</span>.<a href="#section-3-4.1" class="pilcrow"></a></p>
</aside>
<p id="section-3-5">The fields in AlgorithmIdentifier have the following meanings:<a href="#section-3-5" class="pilcrow"></a></p>
<ul class="normal">
<li class="normal" id="section-3-6.1">algorithm identifies the cryptographic algorithm with an object
identifier.<a href="#section-3-6.1" class="pilcrow"></a>
<li class="normal" id="section-3-6.1">
<p id="section-3-6.1.1">algorithm identifies the cryptographic algorithm with an object
identifier.<a href="#section-3-6.1.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="section-3-6.2">parameters, which are optional, are the associated parameters for
the algorithm identifier in the algorithm field.<a href="#section-3-6.2" class="pilcrow"></a>
<li class="normal" id="section-3-6.2">
<p id="section-3-6.2.1">parameters, which are optional, are the associated parameters for
the algorithm identifier in the algorithm field.<a href="#section-3-6.2.1" class="pilcrow"></a></p>
</li>
</ul>
<p id="section-3-7"><a href="#Kyber-TBD1" class="auto internal xref">Section 4</a> includes object identifiers for Kyber-512, Kyber-768, and
Kyber-1024. For all of these OIDs, the parameters <span class="bcp14">MUST</span> be absent.<a href="#section-3-7" class="pilcrow"></a></p>
<aside id="section-3-8">
<p id="section-3-8.1">NOTE: It is possible to find systems that require the parameters to be
present. This can be due to either a defect in the original 1997
syntax or a programming error where developers never got input where
this was not true. The optimal solution is to fix these systems;
where this is not possible, the problem needs to be restricted to
that subsystem and not propagated to the Internet.<a href="#section-3-8.1" class="pilcrow"></a></p>
<p id="section-3-8.1">: It is possible to find systems that require the parameters to be
present. This can be due to either a defect in the original 1997
syntax or a programming error where developers never got input where
this was not true. The optimal solution is to fix these systems;
where this is not possible, the problem needs to be restricted to
that subsystem and not propagated to the Internet.<a href="#section-3-8.1" class="pilcrow"></a></p>
</aside>
</section>
</div>
Expand Down Expand Up @@ -1372,9 +1352,9 @@ <h2 id="name-kyber-public-key-identifier">
</pre><a href="#section-4-3" class="pilcrow"></a>
</div>
<aside id="section-4-4">
<p id="section-4-4.1">NOTE: As noted in Section 3, the values for these object identifers
will be assigned by NIST. Once assigned, they will be added to a future
revision of this document.<a href="#section-4-4.1" class="pilcrow"></a></p>
<p id="section-4-4.1">: As noted in Section 3, the values for these object identifers
will be assigned by NIST. Once assigned, they will be added to a future
revision of this document.<a href="#section-4-4.1" class="pilcrow"></a></p>
</aside>
</section>
</div>
Expand All @@ -1394,17 +1374,19 @@ <h2 id="name-subject-public-key-fields">
</pre><a href="#section-5-2" class="pilcrow"></a>
</div>
<aside id="section-5-3">
<p id="section-5-3.1">NOTE: The above syntax is from <span>[<a href="#RFC5912" class="cite xref">RFC5912</a>]</span> and is compatible with the
2021 ASN.1 syntax <span>[<a href="#X680" class="cite xref">X680</a>]</span>.<a href="#section-5-3.1" class="pilcrow"></a></p>
<p id="section-5-3.1">: The above syntax is from <span>[<a href="#RFC5912" class="cite xref">RFC5912</a>]</span> and is compatible with the
2021 ASN.1 syntax <span>[<a href="#X680" class="cite xref">X680</a>]</span>.<a href="#section-5-3.1" class="pilcrow"></a></p>
</aside>
<p id="section-5-4">The fields in SubjectPublicKeyInfo have the following meaning:<a href="#section-5-4" class="pilcrow"></a></p>
<ul class="normal">
<li class="normal" id="section-5-5.1">algorithm is the algorithm identifier and parameters for the
public key (see above).<a href="#section-5-5.1" class="pilcrow"></a>
<li class="normal" id="section-5-5.1">
<p id="section-5-5.1.1">algorithm is the algorithm identifier and parameters for the
public key (see above).<a href="#section-5-5.1.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="section-5-5.2">subjectPublicKey contains the byte stream of the public key. The
<li class="normal" id="section-5-5.2">
<p id="section-5-5.2.1">subjectPublicKey contains the byte stream of the public key. The
algorithms defined in this document always encode the public key
as TODO pick format e.g., exact multiple of 8 bits?.<a href="#section-5-5.2" class="pilcrow"></a>
as TODO pick format e.g., exact multiple of 8 bits?.<a href="#section-5-5.2.1" class="pilcrow"></a></p>
</li>
</ul>
<p id="section-5-6">The following is an example of a Kyber-512 public key encoded using the
Expand Down Expand Up @@ -1457,8 +1439,8 @@ <h2 id="name-private-key-format">
</pre><a href="#section-6-2" class="pilcrow"></a>
</div>
<aside id="section-6-3">
<p id="section-6-3.1">NOTE: The above syntax is from <span>[<a href="#RFC5958" class="cite xref">RFC5958</a>]</span> and is compatible with the
2021 ASN.1 syntax <span>[<a href="#X680" class="cite xref">X680</a>]</span>.<a href="#section-6-3.1" class="pilcrow"></a></p>
<p id="section-6-3.1">: The above syntax is from <span>[<a href="#RFC5958" class="cite xref">RFC5958</a>]</span> and is compatible with the
2021 ASN.1 syntax <span>[<a href="#X680" class="cite xref">X680</a>]</span>.<a href="#section-6-3.1" class="pilcrow"></a></p>
</aside>
<p id="section-6-4">For the keys defined in this document, the private key is always an
opaque byte sequence. The ASN.1 type PqckemPrivateKey is defined in
Expand Down Expand Up @@ -1491,12 +1473,12 @@ <h2 id="name-private-key-format">
</pre><a href="#section-6-9" class="pilcrow"></a>
</div>
<aside id="section-6-10">
<p id="section-6-10.1">NOTE: There exist some private key import functions that have not
implemented the new ASN.1 structure OneAsymmetricKey that is defined in
<span>[<a href="#RFC5958" class="cite xref">RFC5958</a>]</span>. This means that they will not accept a private key
structure that contains the public key field. This means a balancing
act needs to be done between being able to do a consistency check on the
key pair and widest ability to import the key.<a href="#section-6-10.1" class="pilcrow"></a></p>
<p id="section-6-10.1">: There exist some private key import functions that have not
implemented the new ASN.1 structure OneAsymmetricKey that is defined in
<span>[<a href="#RFC5958" class="cite xref">RFC5958</a>]</span>. This means that they will not accept a private key
structure that contains the public key field. This means a balancing
act needs to be done between being able to do a consistency check on the
key pair and widest ability to import the key.<a href="#section-6-10.1" class="pilcrow"></a></p>
</aside>
</section>
</div>
Expand Down Expand Up @@ -1529,6 +1511,7 @@ <h2 id="name-iana-considerations">
<h2 id="name-references">
<a href="#section-10" class="section-number selfRef">10. </a><a href="#name-references" class="section-name selfRef">References</a>
</h2>
<div id="sec-normative-references">
<section id="section-10.1">
<h3 id="name-normative-references">
<a href="#section-10.1" class="section-number selfRef">10.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
Expand Down Expand Up @@ -1564,14 +1547,16 @@ <h3 id="name-normative-references">
<dd class="break"></dd>
</dl>
</section>
</div>
<div id="sec-informative-references">
<section id="section-10.2">
<h3 id="name-informative-references">
<a href="#section-10.2" class="section-number selfRef">10.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
</h3>
<dl class="references">
<dt id="I-D.celi-wiggers-tls-authkem">[I-D.celi-wiggers-tls-authkem]</dt>
<dd>
<span class="refAuthor">Celi, S.</span>, <span class="refAuthor">Schwabe, P.</span>, <span class="refAuthor">Stebila, D.</span>, <span class="refAuthor">Sullivan, N.</span>, and <span class="refAuthor">T. Wiggers</span>, <span class="refTitle">"KEM-based Authentication for TLS 1.3"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-celi-wiggers-tls-authkem-01</span>, <time datetime="2022-03-07" class="refDate">7 March 2022</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-celi-wiggers-tls-authkem-01">https://datatracker.ietf.org/doc/html/draft-celi-wiggers-tls-authkem-01</a>&gt;</span>. </dd>
<span class="refAuthor">Wiggers, T.</span>, <span class="refAuthor">Celi, S.</span>, <span class="refAuthor">Schwabe, P.</span>, <span class="refAuthor">Stebila, D.</span>, and <span class="refAuthor">N. Sullivan</span>, <span class="refTitle">"KEM-based Authentication for TLS 1.3"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-celi-wiggers-tls-authkem-02</span>, <time datetime="2023-08-18" class="refDate">18 August 2023</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-celi-wiggers-tls-authkem-02">https://datatracker.ietf.org/doc/html/draft-celi-wiggers-tls-authkem-02</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="I-D.ietf-lamps-kyber">[I-D.ietf-lamps-kyber]</dt>
<dd>
Expand All @@ -1587,6 +1572,7 @@ <h3 id="name-informative-references">
<dd class="break"></dd>
</dl>
</section>
</div>
</section>
<div id="acknowledgments">
<section id="appendix-A">
Expand Down
Loading

0 comments on commit e5ab8a8

Please sign in to comment.