Skip to content

Commit

Permalink
Script updating gh-pages from d126630. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Nov 17, 2023
1 parent 52e5107 commit fe60479
Show file tree
Hide file tree
Showing 2 changed files with 59 additions and 31 deletions.
56 changes: 36 additions & 20 deletions draft-demarco-nonce-endpoint.html
Original file line number Diff line number Diff line change
Expand Up @@ -1145,24 +1145,27 @@ <h2 id="name-copyright-notice">
<p id="section-toc.1-1.7.1"><a href="#section-7" class="auto internal xref">7</a>.  <a href="#name-security-considerations" class="internal xref">Security Considerations</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8">
<p id="section-toc.1-1.8.1"><a href="#section-8" class="auto internal xref">8</a>.  <a href="#name-iana-considerations" class="internal xref">IANA Considerations</a></p>
<p id="section-toc.1-1.8.1"><a href="#section-8" class="auto internal xref">8</a>.  <a href="#name-considerations-about-the-jw" class="internal xref">Considerations about the JWT jti claim</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9">
<p id="section-toc.1-1.9.1"><a href="#section-9" class="auto internal xref">9</a>.  <a href="#name-references" class="internal xref">References</a></p>
<p id="section-toc.1-1.9.1"><a href="#section-9" class="auto internal xref">9</a>.  <a href="#name-iana-considerations" class="internal xref">IANA Considerations</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10">
<p id="section-toc.1-1.10.1"><a href="#section-10" class="auto internal xref">10</a><a href="#name-references" class="internal xref">References</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.1">
<p id="section-toc.1-1.9.2.1.1"><a href="#section-9.1" class="auto internal xref">9.1</a>.  <a href="#name-normative-references" class="internal xref">Normative References</a></p>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.1">
<p id="section-toc.1-1.10.2.1.1"><a href="#section-10.1" class="auto internal xref">10.1</a>.  <a href="#name-normative-references" class="internal xref">Normative References</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.2">
<p id="section-toc.1-1.9.2.2.1"><a href="#section-9.2" class="auto internal xref">9.2</a>.  <a href="#name-informative-references" class="internal xref">Informative References</a></p>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.2">
<p id="section-toc.1-1.10.2.2.1"><a href="#section-10.2" class="auto internal xref">10.2</a>.  <a href="#name-informative-references" class="internal xref">Informative References</a></p>
</li>
</ul>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10">
<p id="section-toc.1-1.10.1"><a href="#appendix-A" class="auto internal xref"></a><a href="#name-acknowledgments" class="internal xref">Acknowledgments</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11">
<p id="section-toc.1-1.11.1"><a href="#appendix-B" class="auto internal xref"></a><a href="#name-authors-address" class="internal xref">Author's Address</a></p>
<p id="section-toc.1-1.11.1"><a href="#appendix-A" class="auto internal xref"></a><a href="#name-acknowledgments" class="internal xref">Acknowledgments</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12">
<p id="section-toc.1-1.12.1"><a href="#appendix-B" class="auto internal xref"></a><a href="#name-authors-address" class="internal xref">Author's Address</a></p>
</li>
</ul>
</nav>
Expand Down Expand Up @@ -1193,7 +1196,11 @@ <h2 id="name-conventions-and-definitions">
<h2 id="name-terminology">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a>
</h2>
<p id="section-3-1">The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>", "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>", "<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as described in <span>[<a href="#RFC2119" class="cite xref">RFC2119</a>]</span>.<a href="#section-3-1" class="pilcrow"></a></p>
<ul class="normal">
<li class="normal" id="section-3-1.1">
<p id="section-3-1.1.1">Nonce: random or pseudo-random number that is generated for a specific use, typically for cryptographic communication. It is used to protect against replay attacks by ensuring that a message or data cannot be reused or retransmitted, maliciously or otherwise. The term "nonce" stands for "number used once" and it must be unique within some scope.<a href="#section-3-1.1.1" class="pilcrow"></a></p>
</li>
</ul>
</section>
</div>
<div id="nonce-endpoint">
Expand Down Expand Up @@ -1310,22 +1317,31 @@ <h2 id="name-security-considerations">
<p id="section-7-5">The security of the nonce endpoint is only as strong as the security of the encryption key. Therefore, proper key management practices are essential.<a href="#section-7-5" class="pilcrow"></a></p>
</section>
</div>
<div id="iana-considerations">
<div id="considerations-about-the-jwt-jti-claim">
<section id="section-8">
<h2 id="name-iana-considerations">
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
<h2 id="name-considerations-about-the-jw">
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-considerations-about-the-jw" class="section-name selfRef">Considerations about the JWT jti claim</a>
</h2>
<p id="section-8-1">This document has no IANA actions.<a href="#section-8-1" class="pilcrow"></a></p>
<p id="section-8-1">In this section are provided some consideration about the main differences and scopes the nonce in comparison to the <code>jti</code> claim, defined in <span>[<a href="#RFC7519" class="cite xref">RFC7519</a>]</span>.<a href="#section-8-1" class="pilcrow"></a></p>
<p id="section-8-2">TBD.<a href="#section-8-2" class="pilcrow"></a></p>
</section>
</div>
<div id="iana-considerations">
<section id="section-9">
<h2 id="name-iana-considerations">
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
</h2>
<p id="section-9-1">This document has no IANA actions.<a href="#section-9-1" class="pilcrow"></a></p>
</section>
</div>
<section id="section-10">
<h2 id="name-references">
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-references" class="section-name selfRef">References</a>
<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-9.1">
<section id="section-10.1">
<h3 id="name-normative-references">
<a href="#section-9.1" class="section-number selfRef">9.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
<a href="#section-10.1" class="section-number selfRef">10.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
</h3>
<dl class="references">
<dt id="RFC2119">[RFC2119]</dt>
Expand Down Expand Up @@ -1356,9 +1372,9 @@ <h3 id="name-normative-references">
</section>
</div>
<div id="sec-informative-references">
<section id="section-9.2">
<section id="section-10.2">
<h3 id="name-informative-references">
<a href="#section-9.2" class="section-number selfRef">9.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
<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="BCP195">[BCP195]</dt>
Expand Down
34 changes: 23 additions & 11 deletions draft-demarco-nonce-endpoint.txt
Original file line number Diff line number Diff line change
Expand Up @@ -71,10 +71,11 @@ Table of Contents
5. Errors
6. Nonce Payload Non-normative Examples
7. Security Considerations
8. IANA Considerations
9. References
9.1. Normative References
9.2. Informative References
8. Considerations about the JWT jti claim
9. IANA Considerations
10. References
10.1. Normative References
10.2. Informative References
Acknowledgments
Author's Address

Expand Down Expand Up @@ -103,9 +104,12 @@ Table of Contents

3. Terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
* Nonce: random or pseudo-random number that is generated for a
specific use, typically for cryptographic communication. It is
used to protect against replay attacks by ensuring that a message
or data cannot be reused or retransmitted, maliciously or
otherwise. The term "nonce" stands for "number used once" and it
must be unique within some scope.

4. Nonce Endpoint

Expand Down Expand Up @@ -236,13 +240,21 @@ Table of Contents
of the encryption key. Therefore, proper key management practices
are essential.

8. IANA Considerations
8. Considerations about the JWT jti claim

In this section are provided some consideration about the main
differences and scopes the nonce in comparison to the jti claim,
defined in [RFC7519].

TBD.

9. IANA Considerations

This document has no IANA actions.

9. References
10. References

9.1. Normative References
10.1. Normative References

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
Expand Down Expand Up @@ -270,7 +282,7 @@ Table of Contents
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.

9.2. Informative References
10.2. Informative References

[BCP195] Moriarty, K. and S. Farrell, "Deprecating TLS 1.0 and TLS
1.1", BCP 195, RFC 8996, March 2021.
Expand Down

0 comments on commit fe60479

Please sign in to comment.