Re: [Ace] Innovating

[Stefanie Gerdes <[e-mail]>]

Hi all,

The solutions in ACE are all reusing existing solutions, they are just
using different solutions to a different extent.

The use cases show that there is a large variety of scenarios with
different characteristics. The scenarios differ from the web scenarios
which is why we founded ACE in the first place. Some of the use cases
might only require a little tweaking of existing protocols, others need
more consideration about how those protocols can be applied.

We designed DCAF to address scenarios where the client, the server or
both can be class-1 devices (see RFC 7228 [1]), where the client and the
server may belong to different owners with distinct authorization
policies and where these owners may not intervene in the authorization
process at the time of the communication. As far as I understand
draft-seitz-ace-oauth, it only supports less-constrained clients. That
might be fine for the use cases and devices that you have in mind. With
DCAF, we go a bit further into the constrained world and want to enable
constrained devices to securely communicate with other constrained devices.

Of course we want DCAF to interoperate with existing protocols. That is
why we describe how such interactions can work (see
draft-gerdes-ace-dcaf-examples [2]).

Best regards,
Steffi

[1] https://tools.ietf.org/html/rfc7228
[2] https://tools.ietf.org/html/draft-gerdes-ace-dcaf-examples-00