I have found that I had to put a scope encoding format into my database for
each audience definition. Just saying that the scope is CBOR is not going to
be sufficient, just like saying that it is a text string is not enough.
For the text string side you have:
* It is a text string
*
I was starting to code up the encoding of scope and wanted to clarify what
the encoding is.
The text appears to say that the encoding is:
scope = [ groupId: tstr, ?[* role : any ]]
I was expecting this to be more along the lines of
scope = [ + scope_item ]
scopeItem = [ groupId: tstr, ?[* role
On 2020-02-24, at 18:04, Jim Schaad wrote:
>
> • The proposal from Carsten that has not get adopted anywhere yet.
Well, not adopted in the literal sense, but it has been used as a blueprint
both in research works and in standardization.
The main question that is holding this back from be
Hi Jim,
On 2020-02-24 19:02, Jim Schaad wrote:
> I was starting to code up the encoding of scope and wanted to clarify what
> the encoding is.
>
> The text appears to say that the encoding is:
>
> scope = [ groupId: tstr, ?[* role : any ]]
>
> I was expecting this to be more along the lines of
>
>
-Original Message-
From: Marco Tiloca
Sent: Monday, February 24, 2020 2:14 PM
To: Jim Schaad ;
draft-ietf-ace-key-groupcomm-osc...@ietf.org
Cc: 'Ace Wg'
Subject: Re: Scope question
Hi Jim,
On 2020-02-24 19:02, Jim Schaad wrote:
> I was starting to code up the encoding of scope and w
Hi Francesca,
Sorry to cut this so close to the wire...I was on vacation and came back to
a sizeable inbox.
On Mon, Feb 17, 2020 at 03:55:29PM +, Francesca Palombini wrote:
> Hi Ben,
>
> I am now done with updating the draft following most of your review comments.
> Out of the 105, I have i
