Draft 02 - PR

.refcache/reference.RFC.5646.xml

@@ -0,0 +1,14 @@
+<reference anchor="RFC5646" target="https://www.rfc-editor.org/info/rfc5646">
+  <front>
+    <title>Tags for Identifying Languages</title>
+    <author fullname="A. Phillips" initials="A." role="editor" surname="Phillips"/>
+    <author fullname="M. Davis" initials="M." role="editor" surname="Davis"/>
+    <date month="September" year="2009"/>
+    <abstract>
+      <t>This document describes the structure, content, construction, and semantics of language tags for use in cases where it is desirable to indicate the language used in an information object. It also describes how to register values for use in language tags and the creation of user-defined extensions for private interchange. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
+    </abstract>
+  </front>
+  <seriesInfo name="BCP" value="47"/>
+  <seriesInfo name="RFC" value="5646"/>
+  <seriesInfo name="DOI" value="10.17487/RFC5646"/>
+</reference>

.refcache/reference.RFC.7523.xml

@@ -0,0 +1,14 @@
+<reference anchor="RFC7523" target="https://www.rfc-editor.org/info/rfc7523">
+  <front>
+    <title>JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants</title>
+    <author fullname="M. Jones" initials="M." surname="Jones"/>
+    <author fullname="B. Campbell" initials="B." surname="Campbell"/>
+    <author fullname="C. Mortimore" initials="C." surname="Mortimore"/>
+    <date month="May" year="2015"/>
+    <abstract>
+      <t>This specification defines the use of a JSON Web Token (JWT) Bearer Token as a means for requesting an OAuth 2.0 access token as well as for client authentication.</t>
+    </abstract>
+  </front>
+  <seriesInfo name="RFC" value="7523"/>
+  <seriesInfo name="DOI" value="10.17487/RFC7523"/>
+</reference>

.refcache/reference.RFC.8705.xml

@@ -0,0 +1,15 @@
+<reference anchor="RFC8705" target="https://www.rfc-editor.org/info/rfc8705">
+  <front>
+    <title>OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access Tokens</title>
+    <author fullname="B. Campbell" initials="B." surname="Campbell"/>
+    <author fullname="J. Bradley" initials="J." surname="Bradley"/>
+    <author fullname="N. Sakimura" initials="N." surname="Sakimura"/>
+    <author fullname="T. Lodderstedt" initials="T." surname="Lodderstedt"/>
+    <date month="February" year="2020"/>
+    <abstract>
+      <t>This document describes OAuth client authentication and certificate-bound access and refresh tokens using mutual Transport Layer Security (TLS) authentication with X.509 certificates. OAuth clients are provided a mechanism for authentication to the authorization server using mutual TLS, based on either self-signed certificates or public key infrastructure (PKI). OAuth authorization servers are provided a mechanism for binding access tokens to a client's mutual-TLS certificate, and OAuth protected resources are provided a method for ensuring that such an access token presented to it was issued to the client presenting the token.</t>
+    </abstract>
+  </front>
+  <seriesInfo name="RFC" value="8705"/>
+  <seriesInfo name="DOI" value="10.17487/RFC8705"/>
+</reference>

.refcache/reference.RFC.9325.xml

@@ -0,0 +1,16 @@
+<reference anchor="RFC9325" target="https://www.rfc-editor.org/info/rfc9325">
+  <front>
+    <title>Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)</title>
+    <author fullname="Y. Sheffer" initials="Y." surname="Sheffer"/>
+    <author fullname="P. Saint-Andre" initials="P." surname="Saint-Andre"/>
+    <author fullname="T. Fossati" initials="T." surname="Fossati"/>
+    <date month="November" year="2022"/>
+    <abstract>
+      <t>Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) are used to protect data exchanged over a wide range of application protocols and can also form the basis for secure transport protocols. Over the years, the industry has witnessed several serious attacks on TLS and DTLS, including attacks on the most commonly used cipher suites and their modes of operation. This document provides the latest recommendations for ensuring the security of deployed services that use TLS and DTLS. These recommendations are applicable to the majority of use cases.</t>
+      <t>RFC 7525, an earlier version of the TLS recommendations, was published when the industry was transitioning to TLS 1.2. Years later, this transition is largely complete, and TLS 1.3 is widely available. This document updates the guidance given the new environment and obsoletes RFC 7525. In addition, this document updates RFCs 5288 and 6066 in view of recent attacks.</t>
+    </abstract>
+  </front>
+  <seriesInfo name="BCP" value="195"/>
+  <seriesInfo name="RFC" value="9325"/>
+  <seriesInfo name="DOI" value="10.17487/RFC9325"/>
+</reference>