From fe60479aca7d92e5992b9d73a51ae7e430ee1ee6 Mon Sep 17 00:00:00 2001 From: ID Bot Date: Fri, 17 Nov 2023 20:09:58 +0000 Subject: [PATCH] Script updating gh-pages from d126630. [ci skip] --- draft-demarco-nonce-endpoint.html | 56 ++++++++++++++++++++----------- draft-demarco-nonce-endpoint.txt | 34 +++++++++++++------ 2 files changed, 59 insertions(+), 31 deletions(-) diff --git a/draft-demarco-nonce-endpoint.html b/draft-demarco-nonce-endpoint.html index 9748677..68369e4 100644 --- a/draft-demarco-nonce-endpoint.html +++ b/draft-demarco-nonce-endpoint.html @@ -1145,24 +1145,27 @@

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].

+
@@ -1310,22 +1317,31 @@

The security of the nonce endpoint is only as strong as the security of the encryption key. Therefore, proper key management practices are essential.

-
+
-

-8. IANA Considerations +

+8. Considerations about the JWT jti claim

-

This document has no IANA actions.

+

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]
@@ -1356,9 +1372,9 @@

-
+

-9.2. Informative References +10.2. Informative References

[BCP195]
diff --git a/draft-demarco-nonce-endpoint.txt b/draft-demarco-nonce-endpoint.txt index c291b8b..09c69fc 100644 --- a/draft-demarco-nonce-endpoint.txt +++ b/draft-demarco-nonce-endpoint.txt @@ -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 @@ -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 @@ -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, @@ -270,7 +282,7 @@ Table of Contents 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . -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.