[OIDFSC] Request for review of revision of the RISC WG charter

Nat Sakimura sakimura at gmail.com
Wed Jan 8 13:47:56 UTC 2020


I understood that he voted +1.
We only count -1 in the charter process and since there was no opposition,
it was approved on Dec. 3 as the default action.

On Wed, Jan 8, 2020 at 6:47 AM Richard Backman, Annabelle via specs-council
<openid-specs-council at lists.openid.net> wrote:

> Following up on this, I understood Mike’s response to be for himself, not
> the council. Is this correct? If so, what can I do to help the council make
> a decision?
>
>
>
>>
> Annabelle Richard Backman
>
> AWS Identity
>
>
>
>
>
> *From: *specs-council <openid-specs-council-bounces at lists.openid.net> on
> behalf of Mike Jones via specs-council <
> openid-specs-council at lists.openid.net>
> *Reply-To: *Mike Jones <Michael.Jones at microsoft.com>
> *Date: *Sunday, November 24, 2019 at 2:09 PM
> *To: *"Richard Backman, Annabelle" <richanna at amazon.com>
> *Cc: *"marius.scurtescu at coinbase.com" <marius.scurtescu at coinbase.com>, "
> openid-specs-council at lists.openid.net" <
> openid-specs-council at lists.openid.net>
> *Subject: *Re: [OIDFSC] Request for review of revision of the RISC WG
> charter
>
>
>
> Approve of this rechartering.
>
>
>
>                                                        -- Mike
>
>
>
> *From:* specs-council <openid-specs-council-bounces at lists.openid.net> *On
> Behalf Of *Richard Backman, Annabelle via specs-council
> *Sent:* Tuesday, November 19, 2019 12:22 AM
> *To:* openid-specs-council at lists.openid.net
> *Cc:* marius.scurtescu at coinbase.com
> *Subject:* [OIDFSC] Request for review of revision of the RISC WG charter
>
>
>
> Hello OIDF Specifications Council,
>
>
>
> The chairs of the RISC Working Group (myself and Marius Scurtescu) request
> that you review and approve our proposed revision of the RISC WG charter,
> attached to this message in PDF format. The purpose of these revisions is
> to expand the scope of the working group to cover a broader set of use
> cases for sharing signals and events, such as those addressed by the Continuous
> Access Evaluation Protocol (CAEP)
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcloud.google.com%2Fblog%2Fproducts%2Fidentity-security%2Fre-thinking-federated-identity-with-the-continuous-access-evaluation-protocol&data=02%7C01%7CMichael.Jones%40microsoft.com%7Ca202012348684c26592208d76cc991f8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637097485619161179&sdata=pCYvCCJNy0O59tIyg51xtsLMB5ohUq2ZzpMyGQE7Ft8%3D&reserved=0>.
> These changes will allow us to bring CAEP development into the working
> group, and help us develop a common event sharing infrastructure to support
> RISC, CAEP, and other future use cases.
>
>
>
> Note also that this revision renames the working group from “RISC” to
> “Shared Signals and Events” in order to reflect its broader scope.
>
>
>
>>
> Annabelle Richard Backman
>
> Co-chair, RISC Working Group, OpenID Foundation
>
>
>


-- 
Nat Sakimura (=nat)
Chairman, OpenID Foundation
http://nat.sakimura.org/
@_nat_en
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-council/attachments/20200108/45139355/attachment.html>


More information about the specs-council mailing list