RFC 9201: Additional OAuth Parameters for Authentication and Authorization for Constrained Environments (ACE)

This specification defines new parameters and encodings for the OAuth 2.0 token and introspection endpoints when used with the framework for Authentication…

Read RFC 9201 on the RFC Editor

Outgoing relationships (11 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format
Normative reference — RFC 6749: The OAuth 2.0 Authorization Framework
Normative reference — RFC 8949: Concise Binary Object Representation (CBOR)
Normative reference — RFC 8152: CBOR Object Signing and Encryption (COSE)
Normative reference — RFC 8747: Proof-of-Possession Key Semantics for CBOR Web Tokens (CWTs)
Normative reference — RFC 7800: Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)
Normative reference — RFC 8705: OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access Tokens
Normative reference — RFC 9200: Authentication and Authorization for Constrained Environments Using the OAuth 2.0 Framework (ACE-OAuth)
Informative reference — RFC 7252: The Constrained Application Protocol (CoAP)

Incoming relationships (3 related RFCs)

Normatively referenced by — RFC 9200: Authentication and Authorization for Constrained Environments Using the OAuth 2.0 Framework (ACE-OAuth)
Normatively referenced by — RFC 9202: Datagram Transport Layer Security (DTLS) Profile for Authentication and Authorization for Constrained Environments (ACE)
Normatively referenced by — RFC 9203: The Object Security for Constrained RESTful Environments (OSCORE) Profile of the Authentication and Authorization for Constrained Environments (ACE) Framework