I think there are cases when it is use full to have the tag (maybe few) and
I think the draft is clear enough in discouraging the usage when not needed.
“Its use is optional, and is intended for use in cases in which this
information would not otherwise be known.”
To write code that supports unwr
Hi Jim,
I don't think that your statement is correct: as far as I understood the
oscoap-joining document, the RS is the group manager, while in the pubsub
document (even generalizing it and making a group communication profile as
Carsten was suggesting) the entity that does group management is
Hi Stevie,
"Beck, Stefan" writes:
> Hi Derek,
>
> The requirement roughly is:
> Assume a few light switches as multicasters and many luminaires as listeners
> - turning lights on / off via multicast
> The end-2-end processing (multicaster to encrypt&sign the message, the
> network to transmit th
Hi Jim,
I support Francesca's thoughts on this. Please, find inline a few more
comments.
Ciao,
/Marco
On 2017-10-20 15:20, Francesca Palombini wrote:
> Hi Jim,
>
> I don't think that your statement is correct: as far as I understood the
> oscoap-joining document, the RS is the group manager, wh
Hannes Tschofenig wrote:
> Hi Stefan,
> I am trying to understand your ideas.
> ~snip ~
>> For multicast, my focus is on using asymmetric encryption for
> authentication & integrity, and using symmetric encryption for
> confidentiality.
> In your view, you are send
Francesca,
My first concern is that the messages being send around to do the group
communication setup should be, if not identical, highly coordinated in how
they are formatted. I don't really want two different sets of messages.
I understand, and indeed noted, that the current model of how the
Just to highlight this and make it concrete.
COSE did the same thing in defining optional tags that can be used. Looking at
the CWT document, the tags are being used because without the tag one cannot
tell what the security operation is that is being used. However the
OAuth-Authz draft is usi
Dear Kepeng Li,
The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request.
ace Session 1 (2:30:00)
Tuesday, Morning Session I 0930-1200
Room Name: Collyer size: 250
-