[Openid-specs-ab] Call for adoption of Self-Issued OpenID Provider V2, draft 01

[nadalin at prodigy.net]

I don't think a call from adoption should happen before the scope is agreed
upon as this is the basics for any standards body to prevent creep and
understand exactly what the bounds of the specification are. From the call
this week the scope is still in question.

 

From: Openid-specs-ab <openid-specs-ab-bounces at lists.openid.net> On Behalf
Of Kristina Yasuda via Openid-specs-ab
Sent: Tuesday, December 8, 2020 6:23 PM
To: 'Artifact Binding/Connect Working Group'
<openid-specs-ab at lists.openid.net>
Cc: Kristina Yasuda <Kristina.Yasuda at microsoft.com>
Subject: [Openid-specs-ab] Call for adoption of Self-Issued OpenID Provider
V2, draft 01

 

Dear AB/Connect WG experts,

 

We would like to do a call for adoption for a Self-Issued OpenID Provider
V2, draft 01 as has been discussed in the Connect WG call. Here is a link to
the draft text:
<https://bitbucket.org/openid/connect/src/master/openid-connect-self-issued-
v2-1_0.md>
https://bitbucket.org/openid/connect/src/master/openid-connect-self-issued-v
2-1_0.md

This draft covers scopes 1, 2 and 5 from 5 proposed SIOP scopes that are
being discussedf, with an ongoing effort to reflect proposals regarding
Discovery. 

 

Best Regards,

Kristina

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20201208/4eb73e54/attachment.html>