| rfc9201v4.txt | rfc9201.txt | |||
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) L. Seitz | Internet Engineering Task Force (IETF) L. Seitz | |||
| Request for Comments: 9201 Combitech | Request for Comments: 9201 Combitech | |||
| Category: Standards Track May 2022 | Category: Standards Track August 2022 | |||
| ISSN: 2070-1721 | ISSN: 2070-1721 | |||
| Additional OAuth Parameters for Authentication and Authorization for | Additional OAuth Parameters for Authentication and Authorization for | |||
| Constrained Environments (ACE) | Constrained Environments (ACE) | |||
| Abstract | Abstract | |||
| This specification defines new parameters and encodings for the OAuth | This specification defines new parameters and encodings for the OAuth | |||
| 2.0 token and introspection endpoints when used with the framework | 2.0 token and introspection endpoints when used with the framework | |||
| for Authentication and Authorization for Constrained Environments | for Authentication and Authorization for Constrained Environments | |||
| skipping to change at line 91 ¶ | skipping to change at line 91 ¶ | |||
| use in a manner independent of [RFC9200]. | use in a manner independent of [RFC9200]. | |||
| Note that although all examples are shown in Concise Binary Object | Note that although all examples are shown in Concise Binary Object | |||
| Representation (CBOR) [RFC8949], JSON [RFC8259] MAY be used as an | Representation (CBOR) [RFC8949], JSON [RFC8259] MAY be used as an | |||
| alternative for HTTP-based communications, as specified in [RFC9200]. | alternative for HTTP-based communications, as specified in [RFC9200]. | |||
| 2. Terminology | 2. Terminology | |||
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
| "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and | "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and | |||
| "OPTIONAL" in this document are to be interpreted as described in BCP | "OPTIONAL" in this document are to be interpreted as described in | |||
| 14 [RFC2119] [RFC8174] when, and only when, they appear in all | BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all | |||
| capitals, as shown here. | capitals, as shown here. | |||
| Readers are assumed to be familiar with the terminology from | Readers are assumed to be familiar with the terminology from | |||
| [RFC9200], especially the terminology for entities in the | [RFC9200], especially the terminology for entities in the | |||
| architecture such as client (C), resource server (RS), and | architecture such as client (C), resource server (RS), and | |||
| authorization server (AS). | authorization server (AS). | |||
| Terminology from [RFC8152] is used in the examples, especially | Terminology from [RFC8152] is used in the examples, especially | |||
| COSE_Key, which is defined in Section 7 of [RFC8152]. | COSE_Key, which is defined in Section 7 of [RFC8152]. | |||
| skipping to change at line 467 ¶ | skipping to change at line 467 ¶ | |||
| [RFC8949] Bormann, C. and P. Hoffman, "Concise Binary Object | [RFC8949] Bormann, C. and P. Hoffman, "Concise Binary Object | |||
| Representation (CBOR)", STD 94, RFC 8949, | Representation (CBOR)", STD 94, RFC 8949, | |||
| DOI 10.17487/RFC8949, December 2020, | DOI 10.17487/RFC8949, December 2020, | |||
| <https://www.rfc-editor.org/info/rfc8949>. | <https://www.rfc-editor.org/info/rfc8949>. | |||
| [RFC9200] Seitz, L., Selander, G., Wahlstroem, E., Erdtman, S., and | [RFC9200] Seitz, L., Selander, G., Wahlstroem, E., Erdtman, S., and | |||
| H. Tschofenig, "Authentication and Authorization for | H. Tschofenig, "Authentication and Authorization for | |||
| Constrained Environments (ACE) Using the OAuth 2.0 | Constrained Environments (ACE) Using the OAuth 2.0 | |||
| Framework (ACE-OAuth)", RFC 9200, DOI 10.17487/RFC9200, | Framework (ACE-OAuth)", RFC 9200, DOI 10.17487/RFC9200, | |||
| May 2022, <https://www.rfc-editor.org/info/rfc9200>. | August 2022, <https://www.rfc-editor.org/info/rfc9200>. | |||
| 11.2. Informative References | 11.2. Informative References | |||
| [RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained | [RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained | |||
| Application Protocol (CoAP)", RFC 7252, | Application Protocol (CoAP)", RFC 7252, | |||
| DOI 10.17487/RFC7252, June 2014, | DOI 10.17487/RFC7252, June 2014, | |||
| <https://www.rfc-editor.org/info/rfc7252>. | <https://www.rfc-editor.org/info/rfc7252>. | |||
| Acknowledgments | Acknowledgments | |||
| End of changes. 3 change blocks. | ||||
| 4 lines changed or deleted | 4 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. | ||||