%% You should probably cite draft-ietf-ace-workflow-and-params-03 instead of this revision. @techreport{ietf-ace-workflow-and-params-02, number = {draft-ietf-ace-workflow-and-params-02}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-ace-workflow-and-params/02/}, author = {Marco Tiloca and Göran Selander}, title = {{Alternative Workflow and OAuth Parameters for the Authentication and Authorization for Constrained Environments (ACE) Framework}}, pagetotal = 52, year = , month = , day = , abstract = {This document updates the Authentication and Authorization for Constrained Environments Framework (ACE, RFC 9200) as follows. First, it defines a new, alternative workflow that the Authorization Server can use for uploading an access token to a Resource Server on behalf of the Client. Second, it defines new parameters and encodings for the OAuth 2.0 token endpoint at the Authorization Server. Third, it defines a method for the ACE framework to enforce bidirectional access control by means of a single access token. Fourth, it amends two of the requirements on profiles of the framework. Finally, it deprecates the original payload format of error responses that convey an error code, when CBOR is used to encode message payloads. For such error responses, it defines a new payload format aligned with RFC 9290, thus updating in this respect also the profiles of ACE defined in RFC 9202, RFC 9203, and RFC 9431.}, }