<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-2022-jp">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"MS PGothic";
panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
{font-family:"\@MS PGothic";}
@font-face
{font-family:"\@Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"MS PGothic",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.xmsonormal, li.xmsonormal, div.xmsonormal
{mso-style-name:x_msonormal;
margin:0in;
font-size:12.0pt;
font-family:"MS PGothic",sans-serif;}
span.EmailStyle22
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi Petteri,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Why do you need JSON-LD for selective disclosure if you are doing atomic credentials?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In other words, “</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">- Each claim is issued in a separate credential.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">”
Why does this has to be JSON-LD and not JSON serialized?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thank you,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Kristina</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Openid-specs-ab <openid-specs-ab-bounces@lists.openid.net>
<b>On Behalf Of </b>Petteri Stenius via Openid-specs-ab<br>
<b>Sent:</b> Monday, September 26, 2022 9:07 AM<br>
<b>To:</b> Artifact Binding/Connect Working Group <openid-specs-ab@lists.openid.net><br>
<b>Cc:</b> Petteri Stenius <Petteri.Stenius@ubisecure.com><br>
<b>Subject:</b> Re: [Openid-specs-ab] SIOP Special Topic Call Notes 22-Sep-22<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Hi,
<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">The selective disclosure model of Finnish ID system is quite simple:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">- There's a relatively small number of claims.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">- Each claim is issued in a separate credential.
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">- A relying party can request specific claims by using scope or claims parameter.
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">- Resulting vp_token contains one or more credentials with the requested claims.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">- The wallet app can refresh credentials so that claims such as age_over_18 have valid information.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Link to more detailed information
<a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.dvv.fi%2Fdisplay%2FDHHJD%2FSIOPv2%2BPOC%2B-%2BGuide%2Bfor%2BRelying%2BParties&data=05%7C01%7CKristina.Yasuda%40microsoft.com%7C9c57ccd4677d4a6831a908da9fd94217%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637998054260407349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=YsEQkqMOjSoajTd0X11GU0hJCFal8ejxgxFrJ7R5qbE%3D&reserved=0">
https://wiki.dvv.fi/display/DHHJD/SIOPv2+POC+-+Guide+for+Relying+Parties</a> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Petteri<o:p></o:p></span></p>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="98%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> Openid-specs-ab <<a href="mailto:openid-specs-ab-bounces@lists.openid.net">openid-specs-ab-bounces@lists.openid.net</a>>
on behalf of Nat Sakimura via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a>><br>
<b>Sent:</b> Friday, September 23, 2022 11:36<br>
<b>To:</b> Artifact Binding/Connect Working Group <<a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a>><br>
<b>Cc:</b> Nat Sakimura <<a href="mailto:nat@nat.consulting">nat@nat.consulting</a>><br>
<b>Subject:</b> Re: [Openid-specs-ab] SIOP Special Topic Call Notes 22-Sep-22</span>
<o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">It would be great if how Finnish LD-Proof is approaching selective disclosure can be documented. It will help this community. <o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">2022<span lang="JA">年</span>9<span lang="JA">月</span>23<span lang="JA">日</span>(<span lang="JA">金</span>) 4:48 Mike Jones via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a>>:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="xmsonormal">SIOP Special Topic Call Notes 22-Sep-22<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">Mike Jones<o:p></o:p></p>
<p class="xmsonormal">Petteri Stenius<o:p></o:p></p>
<p class="xmsonormal">David Chadwick<o:p></o:p></p>
<p class="xmsonormal">Joseph Heenan<o:p></o:p></p>
<p class="xmsonormal">Torsten Lodderstedt<o:p></o:p></p>
<p class="xmsonormal">Bjorn Hjelm<o:p></o:p></p>
<p class="xmsonormal">Kristina Yasuda<o:p></o:p></p>
<p class="xmsonormal">David Waite (DW)<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">Petteri reported on the Finnish ID system being developed<o:p></o:p></p>
<p class="xmsonormal"> They have chosen SIOP<o:p></o:p></p>
<p class="xmsonormal"> It uses a wallet<o:p></o:p></p>
<p class="xmsonormal"> The credentials will be JSON-LD<o:p></o:p></p>
<p class="xmsonormal"> There is selective disclosure for age verification<o:p></o:p></p>
<p class="xmsonormal"> They are building a wallet from scratch to hold the Finnish identity documents<o:p></o:p></p>
<p class="xmsonormal"> <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdvv.fi%2Fen%2F-%2Fdevelopment-of-the-digital-identity-card-already-far-along-feedback-from-test-users-guiding-completion-of-the-mobile-application&data=05%7C01%7CKristina.Yasuda%40microsoft.com%7C9c57ccd4677d4a6831a908da9fd94217%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637998054260407349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=85FaL%2FVfjHamRZT%2FeGLP1NMAeD5hyA4S55h4TfbFZLM%3D&reserved=0" target="_blank">
https://dvv.fi/en/-/development-of-the-digital-identity-card-already-far-along-feedback-from-test-users-guiding-completion-of-the-mobile-application</a><o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">Public Review Period for Proposed Final Unmet Authentication Requirements Specification<o:p></o:p></p>
<p class="xmsonormal"> Nat had privately asked if there are multiple implementations of the specification<o:p></o:p></p>
<p class="xmsonormal"> Torsten said that this a mandatory to implement requirement for IdPs using
<a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fyes.com%2F&data=05%7C01%7CKristina.Yasuda%40microsoft.com%7C9c57ccd4677d4a6831a908da9fd94217%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637998054260407349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VqGUeF3thi%2FR5Q2h%2FOiFtTVAU2H3axR053DauqmwdH0%3D&reserved=0" target="_blank">
yes.com</a><o:p></o:p></p>
<p class="xmsonormal"> He said that there are least four different implementations in the
<a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fyes.com%2F&data=05%7C01%7CKristina.Yasuda%40microsoft.com%7C9c57ccd4677d4a6831a908da9fd94217%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637998054260407349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VqGUeF3thi%2FR5Q2h%2FOiFtTVAU2H3axR053DauqmwdH0%3D&reserved=0" target="_blank">
yes.com</a> ecosystem<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">Pull Requests<o:p></o:p></p>
<p class="xmsonormal"> <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbitbucket.org%2Fopenid%2Fconnect%2Fpull-requests%2F&data=05%7C01%7CKristina.Yasuda%40microsoft.com%7C9c57ccd4677d4a6831a908da9fd94217%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637998054260407349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=f%2BTgUgdzj8wYU%2F3ebaHrS14DtkrSh4IxAeMQUdkstbI%3D&reserved=0" target="_blank">
https://bitbucket.org/openid/connect/pull-requests/</a><o:p></o:p></p>
<p class="xmsonormal"> PR #240: Add "type" to OP Metadata (Issues #1566, #1592, #1628)<o:p></o:p></p>
<p class="xmsonormal"> Torsten, Oliver, and David Chadwick are working on a new proposal for credential metadata<o:p></o:p></p>
<p class="xmsonormal"> It has a credentials_supported structure<o:p></o:p></p>
<p class="xmsonormal"> It has a "standard" element - for instance "iso-mdoc"<o:p></o:p></p>
<p class="xmsonormal"> They do not want issuers to have to invent something on top of the existing credential formats<o:p></o:p></p>
<p class="xmsonormal"> David said that each standard has their own naming schemes<o:p></o:p></p>
<p class="xmsonormal"> But we can use common display names to present information to the user<o:p></o:p></p>
<p class="xmsonormal"> Kristina is not a fan of the structure having the "standard" and the "proof" separately<o:p></o:p></p>
<p class="xmsonormal"> Some of these things are standard-specific already so we don't have to separately declare the "standard"<o:p></o:p></p>
<p class="xmsonormal"> Torsten understands Kristina's feedback and is leaning in that direction<o:p></o:p></p>
<p class="xmsonormal"> Torsten simplified his displayed proposed example to eliminate "standard" and to include, for instance "format": "jwt_vc"<o:p></o:p></p>
<p class="xmsonormal"> Kristina questioned whether to include @context<o:p></o:p></p>
<p class="xmsonormal"> She said that, as discussed in the VCWG last week, there are JSON credentials that don't use @context data structures<o:p></o:p></p>
<p class="xmsonormal"> For instance, a "university_degree" credential may be understood by the parties without @context<o:p></o:p></p>
<p class="xmsonormal"> @context is ignored in JSON-serialized VCs<o:p></o:p></p>
<p class="xmsonormal"> Kristina requested that this be described in multiple PRs<o:p></o:p></p>
<p class="xmsonormal"> For instance, the base PR shouldn't introduce @context<o:p></o:p></p>
<p class="xmsonormal"> Torsten thinks that it may be premature to write PRs<o:p></o:p></p>
<p class="xmsonormal"> Mike opined that PRs should be written once there is consensus on how to resolve an issue and not before<o:p></o:p></p>
<p class="xmsonormal"> Torsten said that the decision to drop the top-level parameter has implications<o:p></o:p></p>
<p class="xmsonormal"> This would also have to be propagated to the authorization_details and credential issuance parameters<o:p></o:p></p>
<p class="xmsonormal"> The primary parameter "format" would determine the rest<o:p></o:p></p>
<p class="xmsonormal"> Kristina said that we already have a "format" parameter<o:p></o:p></p>
<p class="xmsonormal"> This is an extension point<o:p></o:p></p>
<p class="xmsonormal"> David Chadwick said that the key issue is whether the different metadata formats can be unified or whether they should be format-specific<o:p></o:p></p>
<p class="xmsonormal"> PR #294: clarifying that aud is not required in a signed request in SIOPv2, issue #1602<o:p></o:p></p>
<p class="xmsonormal"> DW asserted that this is ready to merge<o:p></o:p></p>
<p class="xmsonormal"> We discussed the choice of <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fself-issued.me%2F&data=05%7C01%7CKristina.Yasuda%40microsoft.com%7C9c57ccd4677d4a6831a908da9fd94217%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637998054260407349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xJcUBtmZhs1nQh4bgDrN9KCoQYtRvF9Xp%2B504TdZb64%3D&reserved=0" target="_blank">
https://self-issued.me</a> to indicate static metadata<o:p></o:p></p>
<p class="xmsonormal"> DW suggested we change this to <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fself-issued.me%2Fv2&data=05%7C01%7CKristina.Yasuda%40microsoft.com%7C9c57ccd4677d4a6831a908da9fd94217%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637998054260563596%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BNW7u0FZnQzvUJ6dXDB6jhZmpjZIfmxyz4hZTrZmCPc%3D&reserved=0" target="_blank">
https://self-issued.me/v2</a><o:p></o:p></p>
<p class="xmsonormal"> We agreed on the call to change it to
<a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fself-issued.me%2Fv2&data=05%7C01%7CKristina.Yasuda%40microsoft.com%7C9c57ccd4677d4a6831a908da9fd94217%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637998054260563596%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BNW7u0FZnQzvUJ6dXDB6jhZmpjZIfmxyz4hZTrZmCPc%3D&reserved=0" target="_blank">
https://self-issued.me/v2</a> and then merge<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">Testing for OpenID4VC specs<o:p></o:p></p>
<p class="xmsonormal"> Joseph told us about writing tests for the OpenID4VC specs<o:p></o:p></p>
<p class="xmsonormal"> He is working with David Chadwick on this<o:p></o:p></p>
<p class="xmsonormal"> Joseph wrote initial tests for the issuance spec<o:p></o:p></p>
<p class="xmsonormal"> They use the pre-authorized code route<o:p></o:p></p>
<p class="xmsonormal"> He is also writing initial tests for the presentation spec<o:p></o:p></p>
<p class="xmsonormal"> Gail Hodges is asking the certification team about testing for the OpenID4VC specs<o:p></o:p></p>
<p class="xmsonormal"> Joseph doesn't have enough information to do estimates yet<o:p></o:p></p>
<p class="xmsonormal"> David Chadwick gave some background on his request for tests<o:p></o:p></p>
<p class="xmsonormal"> He wants to test the features that are already stable<o:p></o:p></p>
<p class="xmsonormal"> Then add more tests as additional features mature<o:p></o:p></p>
<p class="xmsonormal"> As background, Mike described that it's the responsibility of the working group to define testing requirements<o:p></o:p></p>
<p class="xmsonormal"> and it's the responsibility of the certification team to implement the tests<o:p></o:p></p>
<p class="xmsonormal"> Joseph reported that Kristina, Torsten, and Joseph wrote a document describing the desired tests<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">Issues<o:p></o:p></p>
<p class="xmsonormal"> <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbitbucket.org%2Fopenid%2Fconnect%2Fissues%3Fstatus%3Dnew%26status%3Dopen&data=05%7C01%7CKristina.Yasuda%40microsoft.com%7C9c57ccd4677d4a6831a908da9fd94217%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637998054260563596%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=QfL1GhjXn6BxjaB6Fr6Q9WAYW8ZY8OiiryPRosQgya4%3D&reserved=0" target="_blank">
https://bitbucket.org/openid/connect/issues?status=new&status=open</a><o:p></o:p></p>
<p class="xmsonormal"> #1643: Define error codes for the Credential Issuance Endpoint<o:p></o:p></p>
<p class="xmsonormal"> We discussed when to use the HTTP status code 400<o:p></o:p></p>
<p class="xmsonormal"> RFC 6750, Section 3.1 (Error Codes) describes the use of 400, 401, 403, or 405 with OAuth error codes<o:p></o:p></p>
<p class="xmsonormal"> David agreed to update the issue based on Torsten's comments and the information from RFC 6750<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">Next Call<o:p></o:p></p>
<p class="xmsonormal"> The next call will be Monday, September 26, 2022 at 4pm Pacific Time<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a><br>
<a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.openid.net%2Fmailman%2Flistinfo%2Fopenid-specs-ab&data=05%7C01%7CKristina.Yasuda%40microsoft.com%7C9c57ccd4677d4a6831a908da9fd94217%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637998054260563596%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=oUMpfh94f5TUF5Kv1KFIyMsPXbXah1dpG6boHDKsar4%3D&reserved=0" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-ab</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
</body>
</html>