Use Cases for Authentication and Authorization in Constrained Environments
RFC 7744
Revision differences
Document history
Date | By | Action |
---|---|---|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'Constrained devices are nodes with limited processing power, storage space, and transmission capacities. In many cases, … Received changes through RFC Editor sync (changed abstract to 'Constrained devices are nodes with limited processing power, storage space, and transmission capacities. In many cases, these devices do not provide user interfaces, and they are often intended to interact without human intervention. This document includes a collection of representative use cases for authentication and authorization in constrained environments. These use cases aim at identifying authorization problems that arise during the life cycle of a constrained device and are intended to provide a guideline for developing a comprehensive authentication and authorization solution for this class of scenarios. Where specific details are relevant, it is assumed that the devices use the Constrained Application Protocol (CoAP) as a communication protocol. However, most conclusions apply generally.') |
2016-01-29
|
Jean Mahoney | Closed request for Last Call review by GENART with state 'No Response' |
2016-01-29
|
(System) | RFC published |