Examples for Using DCAF with less constrained devices

Document Type Expired Internet-Draft (individual)
Authors Stefanie Gerdes  , Olaf Bergmann  , Carsten Bormann 
Last updated 2016-01-07 (latest revision 2015-07-06)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Constrained nodes are devices which are limited in terms of processing power, memory, non-volatile storage and transmission capacity. Due to these constraints, commonly used security protocols are not easily applicable. Nevertheless, an authentication and authorization solution is needed to ensure the security of these devices. The Delegated CoAP Authorization Framework (DCAF) specifies how resource-constrained nodes can delegate defined authentication- and authorization-related tasks to less-constrained devices called Authorization Managers, thus limiting the hardware requirements of the security solution for the constrained devices. To realize the vision of "one Internet for all", constrained devices need to securely establish trust relationships with less constrained devices. This document lists examples for using DCAF with less constrained devices.


Stefanie Gerdes (gerdes@tzi.org)
Olaf Bergmann (bergmann@tzi.org)
Carsten Bormann (cabo@tzi.org)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)