| 2119 | Key words for use in RFCs to Indicate Requirement LevelsS. Bradner | Best Current Practice | March 1997 |
| 3986 | Uniform Resource Identifier (URI): Generic SyntaxT. Berners-Lee, R. Fielding, L. Masinter | Internet Standard | January 2005 |
| 6749 | The OAuth 2.0 Authorization FrameworkD. Hardt, Ed. | Proposed Standard | October 2012 |
| 6750 | The OAuth 2.0 Authorization Framework: Bearer Token UsageM. Jones, D. Hardt | Proposed Standard | October 2012 |
| 6819 | OAuth 2.0 Threat Model and Security ConsiderationsT. Lodderstedt, Ed., M. McGloin, P. Hunt | Informational | January 2013 |
| 7521 | Assertion Framework for OAuth 2.0 Client Authentication and Authorization GrantsB. Campbell, C. Mortimore, M. Jones, Y. Goland | Proposed Standard | May 2015 |
| 7523 | JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization GrantsM. Jones, B. Campbell, C. Mortimore | Proposed Standard | May 2015 |
| 7591 | OAuth 2.0 Dynamic Client Registration ProtocolJ. Richer, Ed., M. Jones, J. Bradley, M. Machulak, P. Hunt | Proposed Standard | July 2015 |
| 7636 | Proof Key for Code Exchange by OAuth Public ClientsN. Sakimura, Ed., J. Bradley, N. Agarwal | Proposed Standard | September 2015 |
| 7841 | RFC Streams, Headers, and BoilerplatesJ. Halpern, Ed., L. Daigle, Ed., O. Kolkman, Ed. | Informational | May 2016 |
| 8174 | Ambiguity of Uppercase vs Lowercase in RFC 2119 Key WordsB. Leiba | Best Current Practice | May 2017 |
| 8252 | OAuth 2.0 for Native AppsW. Denniss, J. Bradley | Best Current Practice | October 2017 |
| 8414 | OAuth 2.0 Authorization Server MetadataM. Jones, N. Sakimura, J. Bradley | Proposed Standard | June 2018 |
| 8705 | OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access TokensB. Campbell, J. Bradley, N. Sakimura, T. Lodderstedt | Proposed Standard | February 2020 |
| 8707 | Resource Indicators for OAuth 2.0B. Campbell, J. Bradley, H. Tschofenig | Proposed Standard | February 2020 |
| 8996 | Deprecating TLS 1.0 and TLS 1.1K. Moriarty, S. Farrell | Best Current Practice | March 2021 |
| 9068 | JSON Web Token (JWT) Profile for OAuth 2.0 Access TokensV. Bertocci | Proposed Standard | October 2021 |
| 9101 | The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request (JAR)N. Sakimura, J. Bradley, M. Jones | Proposed Standard | August 2021 |
| 9110 | HTTP SemanticsR. Fielding, Ed., M. Nottingham, Ed., J. Reschke, Ed. | Internet Standard | June 2022 |
| 9126 | OAuth 2.0 Pushed Authorization RequestsT. Lodderstedt, B. Campbell, N. Sakimura, D. Tonge, F. Skokan | Proposed Standard | September 2021 |
| 9207 | OAuth 2.0 Authorization Server Issuer IdentificationK. Meyer zu Selhausen, D. Fett | Proposed Standard | March 2022 |
| 9325 | Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)Y. Sheffer, P. Saint-Andre, T. Fossati | Best Current Practice | November 2022 |
| 9396 | OAuth 2.0 Rich Authorization RequestsT. Lodderstedt, J. Richer, B. Campbell | Proposed Standard | May 2023 |
| 9440 | Client-Cert HTTP Header FieldB. Campbell, M. Bishop | Informational | July 2023 |
| 9449 | OAuth 2.0 Demonstrating Proof of Possession (DPoP)D. Fett, B. Campbell, J. Bradley, T. Lodderstedt, M. Jones, D. Waite | Proposed Standard | September 2023 |