rfc.dk

Cited in: RFC 9201

12 RFCs mentioned in the text of RFC 9201 (Additional OAuth Parameters for Authentication and Authorization for Constrained Environments (ACE))

RFCTitleStatusDate
2119Key words for use in RFCs to Indicate Requirement LevelsS. BradnerBest Current PracticeMarch 1997
6749The OAuth 2.0 Authorization FrameworkD. Hardt, Ed.Proposed StandardOctober 2012
7252The Constrained Application Protocol (CoAP)Z. Shelby, K. Hartke, C. BormannProposed StandardJune 2014
7800Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)M. Jones, J. Bradley, H. TschofenigProposed StandardApril 2016
7841RFC Streams, Headers, and BoilerplatesJ. Halpern, Ed., L. Daigle, Ed., O. Kolkman, Ed.InformationalMay 2016
8152CBOR Object Signing and Encryption (COSE)J. Schaad · obsoleted by RFC 9052, RFC 9053Proposed StandardJuly 2017
8174Ambiguity of Uppercase vs Lowercase in RFC 2119 Key WordsB. LeibaBest Current PracticeMay 2017
8259The JavaScript Object Notation (JSON) Data Interchange FormatT. Bray, Ed.Internet StandardDecember 2017
8705OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access TokensB. Campbell, J. Bradley, N. Sakimura, T. LodderstedtProposed StandardFebruary 2020
8747Proof-of-Possession Key Semantics for CBOR Web Tokens (CWTs)M. Jones, L. Seitz, G. Selander, S. Erdtman, H. TschofenigProposed StandardMarch 2020
8949Concise Binary Object Representation (CBOR)C. Bormann, P. HoffmanInternet StandardDecember 2020
9200Authentication and Authorization for Constrained Environments Using the OAuth 2.0 Framework (ACE-OAuth)L. Seitz, G. Selander, E. Wahlstroem, S. Erdtman, H. TschofenigProposed StandardAugust 2022