<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=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<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:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Aptos",sans-serif;
mso-ligatures:standardcontextual;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:11.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="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Spec Call Notes 12-Aug-24<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Mike Jones<o:p></o:p></p>
<p class="MsoNormal">Brian Campbell<o:p></o:p></p>
<p class="MsoNormal">Nat Sakimura<o:p></o:p></p>
<p class="MsoNormal">Alan Wang<o:p></o:p></p>
<p class="MsoNormal">Dima Postnikov<o:p></o:p></p>
<p class="MsoNormal">Victor Yu<o:p></o:p></p>
<p class="MsoNormal">Bjorn Hjelm<o:p></o:p></p>
<p class="MsoNormal">Tom Jones<o:p></o:p></p>
<p class="MsoNormal">Edmund Jay<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Shared Signals Implementer's Drafts Vote<o:p></o:p></p>
<p class="MsoNormal"> Participate at <a href="https://openid.net/foundation/members/polls/334">
https://openid.net/foundation/members/polls/334</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">EU Implementing Acts<o:p></o:p></p>
<p class="MsoNormal"> There's a public comment period on the EU Implementing Acts<o:p></o:p></p>
<p class="MsoNormal"> Nat said that there are 5 documents<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives_en?text=European%20Digital%20Identity%20Wallets">
https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives_en?text=European%20Digital%20Identity%20Wallets</a><o:p></o:p></p>
<p class="MsoNormal"> The feedback period is August 12 to September 9, 2024<o:p></o:p></p>
<p class="MsoNormal"> Nat said that the implementing acts specify ISO 18013-5 as the protocol<o:p></o:p></p>
<p class="MsoNormal"> We discussed that only final specifications can be referenced from implementing acts<o:p></o:p></p>
<p class="MsoNormal"> So the OpenID4VC specs, SD-JWT, etc. are not referenced<o:p></o:p></p>
<p class="MsoNormal"> Nat said that many things are still unspecified<o:p></o:p></p>
<p class="MsoNormal"> Such as rules for attributed attestations<o:p></o:p></p>
<p class="MsoNormal"> Nat remarked that there's a protocol for credential deletion<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">[Openid-specs-ab] Call for Working Group Adoption of OpenID Federation Extended Subordinate Listing 1.0<o:p></o:p></p>
<p class="MsoNormal"> This spec defines how to do paginated listings of subordinates<o:p></o:p></p>
<p class="MsoNormal"> All respondents so far support adoption<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">[Openid-specs-ab] Call for Working Group Adoption of OpenID Federation Wallet Architectures 1.0<o:p></o:p></p>
<p class="MsoNormal"> There's been some discussion of the contribution and whether it should be adopted as-is<o:p></o:p></p>
<p class="MsoNormal"> Joseph thought that some metadata values currently defined there should be in other specs<o:p></o:p></p>
<p class="MsoNormal"> In the long term, everyone responding to him agreed with him<o:p></o:p></p>
<p class="MsoNormal"> There was disagreement on whether adoption should wait for these values to be first defined elsewhere<o:p></o:p></p>
<p class="MsoNormal"> These were written down now to enable interoperable implementations of wallet ecosystems using Federation to be developed<o:p></o:p></p>
<p class="MsoNormal"> Mike asked Nat to be ready to make the adoption decision as chair next week<o:p></o:p></p>
<p class="MsoNormal"> Since John and Mike are authors<o:p></o:p></p>
<p class="MsoNormal"> Giuseppe sent a detailed message describing each of the defined metadata parameters and their purpose<o:p></o:p></p>
<p class="MsoNormal"> Bjorn asked whether an editor's note could be added saying that the metadata parameters could eventually be defined elsewhere and then referenced there once that's been done<o:p></o:p></p>
<p class="MsoNormal"> Nat agreed that we could make non-normative updates such as adding this note<o:p></o:p></p>
<p class="MsoNormal"> Bjorn said that he isn't dismissing Joseph's concerns<o:p></o:p></p>
<p class="MsoNormal"> Bjorn said that he also wants to be sensitive to people wanting to make progress and implement now<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Metadata parameter value arrays for RP metadata<o:p></o:p></p>
<p class="MsoNormal"><a href="https://bitbucket.org/openid/connect/issues/2158/metadata-parameter-value-arrays-for-rp">https://bitbucket.org/openid/connect/issues/2158/metadata-parameter-value-arrays-for-rp</a><o:p></o:p></p>
<p class="MsoNormal"> Having PRs declare all their supported parameter values is useful in contexts where the RP isn't the one making the decision<o:p></o:p></p>
<p class="MsoNormal"> Mike is working on a small spec enabling this<o:p></o:p></p>
<p class="MsoNormal"> Nat thought it's a reasonable thing to do<o:p></o:p></p>
<p class="MsoNormal"> The Federation editors agreed with Stefan Santesson that this should be independent of the Federation spec<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Do we want to be able to retrieve Entity Configurations with the Fetch Endpoint?<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://github.com/openid/federation/issues/30">
https://github.com/openid/federation/issues/30</a><o:p></o:p></p>
<p class="MsoNormal"> Mike asked whether people have code that retrieves an Entity Configuration via the Fetch Endpoint<o:p></o:p></p>
<p class="MsoNormal"> Rather than .well-known/openid-federation<o:p></o:p></p>
<p class="MsoNormal"> The Fetch Endpoint is used to retrieve Subordinate Statements<o:p></o:p></p>
<p class="MsoNormal"> An implementer pointed out that each API should do one thing<o:p></o:p></p>
<p class="MsoNormal"> In this case, being about retrieving Subordinate Statements<o:p></o:p></p>
<p class="MsoNormal"> Rather than also being used to retrieve Entity Configurations<o:p></o:p></p>
<p class="MsoNormal"> Mike asked if people had code using Fetch to retrieve Entity Configurations<o:p></o:p></p>
<p class="MsoNormal"> Dima doesn't use it for that<o:p></o:p></p>
<p class="MsoNormal"> Mike said that the editors were leaning towards making Fetch only for Subordinate Statements<o:p></o:p></p>
<p class="MsoNormal"> Dima welcomes the simplification<o:p></o:p></p>
<p class="MsoNormal"> Mike put the question to the list after the last call<o:p></o:p></p>
<p class="MsoNormal"> [Openid-specs-ab] Making the Fetch Endpoint specific to retrieving Subordinate Statements<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Carin Alliance<o:p></o:p></p>
<p class="MsoNormal"> Mike said that he'd been reached out to by the Carin Alliance about trust establishment with Federation<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://www.carinalliance.com/">https://www.carinalliance.com/</a><o:p></o:p></p>
<p class="MsoNormal"> They work on US healthcare standards<o:p></o:p></p>
<p class="MsoNormal"> They use the Unified Data Access Profiles <a href="https://www.udap.org/">
https://www.udap.org/</a><o:p></o:p></p>
<p class="MsoNormal"> Tom reported that the Smart Health app uses OpenID Connect<o:p></o:p></p>
<p class="MsoNormal"> Tom mentioned Blue Button <a href="https://bluebutton.cms.gov/developers/">
https://bluebutton.cms.gov/developers/</a><o:p></o:p></p>
<p class="MsoNormal"> He said that Blue Button can be used in Medicare to determine payment information<o:p></o:p></p>
<p class="MsoNormal"> He said that there's problem with POST in Blue Button, which it doesn't allow<o:p></o:p></p>
<p class="MsoNormal"> Tom described the Qualified Health Information Network<o:p></o:p></p>
<p class="MsoNormal"> Tom said that they could use Federation<o:p></o:p></p>
<p class="MsoNormal"> Tom also described PEFCA<o:p></o:p></p>
<p class="MsoNormal"> Tom suggested asking Carin what the nodes are<o:p></o:p></p>
<p class="MsoNormal"> Hospitals, Health Information Network, etc.<o:p></o:p></p>
<p class="MsoNormal"> Mike is speaking with them this week<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Next Call<o:p></o:p></p>
<p class="MsoNormal"> The next call is Monday, August 19th at 4pm US Pacific Time<o:p></o:p></p>
</div>
</body>
</html>