Hi Hannes, and all
Thanks for the announcement.
To be a little bit more precise, the statement is that a CoAP-mappable
HTTP message can be mapped to CoAP (using RFC 8075), protected with OSCORE
(as specified in the referenced draft) and transported with HTTP (as
exemplified in the referenced dra
o find a suitable solution.
>
>Ciao
>Hannes
>
>
>-Original Message-
>From: Göran Selander [mailto:goran.selan...@ericsson.com]
>Sent: 07 February 2018 15:37
>To: Hannes Tschofenig; OAuth@ietf.org
>Cc: draft-ietf-core-object-secur...@ietf.org
>Subject: [OAUTH-W
