RFC 9200: Authentication and Authorization for Constrained Environments Using the OAuth 2.0 Framework (ACE-OAuth)

This specification defines a framework for authentication and authorization in Internet of Things (IoT) environments called ACE-OAuth. The framework is based…

Read RFC 9200 on the RFC Editor

Outgoing relationships (43 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 3986: Uniform Resource Identifier (URI): Generic Syntax
Normative reference — RFC 8126: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 4648: The Base16, Base32, and Base64 Data Encodings
Normative reference — RFC 6347: Datagram Transport Layer Security Version 1.2
Normative reference — RFC 6838: Media Type Specifications and Registration Procedures
Normative reference — RFC 7252: The Constrained Application Protocol (CoAP)
Normative reference — RFC 7519: JSON Web Token (JWT)
Normative reference — RFC 6749: The OAuth 2.0 Authorization Framework
Normative reference — RFC 8610: Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures
Normative reference — RFC 8949: Concise Binary Object Representation (CBOR)
Normative reference — RFC 6750: The OAuth 2.0 Authorization Framework: Bearer Token Usage
Normative reference — RFC 8392: CBOR Web Token (CWT)
Normative reference — RFC 8152: CBOR Object Signing and Encryption (COSE)
Normative reference — RFC 7662: OAuth 2.0 Token Introspection
Normative reference — RFC 6920: Naming Things with Hashes
Normative reference — RFC 8747: Proof-of-Possession Key Semantics for CBOR Web Tokens (CWTs)
Normative reference — RFC 8693: OAuth 2.0 Token Exchange
Normative reference — RFC 9201: Additional OAuth Parameters for Authentication and Authorization for Constrained Environments (ACE)
Informative reference — RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3
Informative reference — RFC 9000: QUIC: A UDP-Based Multiplexed and Secure Transport
Informative reference — RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format
Informative reference — RFC 4949: Internet Security Glossary, Version 2
Informative reference — RFC 9110: HTTP Semantics
Informative reference — RFC 7228: Terminology for Constrained-Node Networks
Informative reference — RFC 9147: The Datagram Transport Layer Security (DTLS) Protocol Version 1.3
Informative reference — RFC 9113: HTTP/2
Informative reference — RFC 8613: Object Security for Constrained RESTful Environments (OSCORE)
Informative reference — RFC 6690: Constrained RESTful Environments (CoRE) Link Format
Informative reference — RFC 8414: OAuth 2.0 Authorization Server Metadata
Informative reference — RFC 7959: Block-Wise Transfers in the Constrained Application Protocol (CoAP)
Informative reference — RFC 6819: OAuth 2.0 Threat Model and Security Considerations
Informative reference — RFC 7591: OAuth 2.0 Dynamic Client Registration Protocol
Informative reference — RFC 7641: Observing Resources in the Constrained Application Protocol (CoAP)
Informative reference — RFC 7009: OAuth 2.0 Token Revocation
Informative reference — RFC 7521: Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants
Informative reference — RFC 8252: OAuth 2.0 for Native Apps
Informative reference — RFC 8628: OAuth 2.0 Device Authorization Grant
Informative reference — RFC 9202: Datagram Transport Layer Security (DTLS) Profile for Authentication and Authorization for Constrained Environments (ACE)
Informative reference — RFC 9203: The Object Security for Constrained RESTful Environments (OSCORE) Profile of the Authentication and Authorization for Constrained Environments (ACE) Framework
Informative reference — RFC 7744: Use Cases for Authentication and Authorization in Constrained Environments
Informative reference — RFC 8516: "Too Many Requests" Response Code for the Constrained Application Protocol

Incoming relationships (6 related RFCs)

Normatively referenced by — RFC 9201: Additional OAuth Parameters for Authentication and Authorization for Constrained Environments (ACE)
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
Normatively referenced by — RFC 9770: Notification of Revoked Access Tokens in the Authentication and Authorization for Constrained Environments (ACE) Framework
Informatively referenced by — RFC 9237: An Authorization Information Format (AIF) for Authentication and Authorization for Constrained Environments (ACE)
Informatively referenced by — RFC 9820: Authentication Service Based on the Extensible Authentication Protocol (EAP) for Use with the Constrained Application Protocol (CoAP)