[Openid-specs-ab] SIOP Special Call Notes 17-Feb-22

[David Waite]

On Feb 18, 2022, at 1:34 AM, Torsten Lodderstedt via Openid-specs-ab <openid-specs-ab at lists.openid.net> wrote:
> 
> Hi,
> 
> On issue 1400.
> 
>> Kristina said that DW indicated on the last Connect call that Ping Identity plans to use "iss" for a trust framework reference
>>                                          Torsten said that a trust framework reference could be included elsewhere in the ID Token
> 
> 
> I also mentioned that OpenID Connect 4 Identity Assurance (https://openid.net/specs/openid-connect-4-identity-assurance-1_0-ID3.html <https://openid.net/specs/openid-connect-4-identity-assurance-1_0-ID3.html>) defines syntax for conveying information about trust frameworks and so on. I suggest to use this as basis for solving Ping’s requirements. 
> 
> We also had a good discussion about trust frameworks and schemes in the context of OIDC4VPs. David has created a PR: https://bitbucket.org/openid/connect/pull-requests/107 <https://bitbucket.org/openid/connect/pull-requests/107>
> 
> @DW: May I ask you to fill an issue with your requirements? 
> 

What would you like to see in particular other than my objections and justifications as currently stated on issue #1400?

To be clear, we are looking to preserve existing Core, Discovery, and Federation functionality in SIOP v2, not to attempt to add some of it back via additional specifications. As such, PR #107 is insufficient.

-DW

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20220218/853437a5/attachment.html>