<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-2022-jp">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="">
<div style="">
<div style="margin-top: 0in; margin-left: 0in;">
<div style="margin-top: 0in; margin-left: 0in;">
<div style="margin: 0px 0in 0px 0.375in;" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Spec Call Notes 11-Mar-21</span><br>
</div>
<div style="margin: 0px 0in 0px 0.375in;" lang="en-US"><br>
</div>
<p style="margin: 0in 0in 0in 0.375in;" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Nat Sakimura</span></p>
<p style="margin: 0in 0in 0in 0.375in;" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Mike Jones</span></p>
<p style="margin: 0in 0in 0in 0.375in;" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Filip Skokan
</span></p>
<p style="margin: 0in 0in 0in 0.375in;" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Adam Lemmon</span></p>
<p style="margin: 0in 0in 0in 0.375in;" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">George Fletcher</span></p>
<p style="margin: 0in 0in 0in 0.375in;" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Joseph Heenan</span></p>
<p style="margin: 0in 0in 0in 0.375in;" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Tim Cappalli</span></p>
<p style="margin: 0in 0in 0in 0.375in;" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Brian Campbell</span></p>
<p style="margin: 0in 0in 0in 0.375in;" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">John Bradley</span></p>
<p style="margin: 0in 0in 0in 0.375in;" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Tom Jones</span></p>
<p style="margin: 0in 0in 0in 0.375in;" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Kristina Yasuda</span><span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt;"> </span></p>
<div style="">
<ul style="">
<li><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Agenda</span></li><ul>
<li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Browser Interactions special call report</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Claims aggregation draft update</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">External organizations (no time)</span></li></ul>
</ul>
<ul style="">
<li><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Browser Interactions special call</span></li><ul>
<li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Tim reported on the progress of WedID</span></li><ul>
<li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">WebID draft by Google evolved: </span><a href="https://github.com/samuelgoto/WebID" style=""><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">https://github.com/samuelgoto/WebID</span></a><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">. </span><span style="text-align: start; display: inline !important; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Explicit
roadmap section added. But the topic is not yet ready for a WG.</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Concern of deferral of any problem into a enterprise construct. How you determine
it is an enterprise context is a hard unsolved issue. </span><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">"Work profile" concept is promising, but concern of it becoming a bucket is acknowledged. Firm
stance - n</span><span style="display: inline !important; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">ot against MDM augmenting,</span><span style="display: inline !important; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
but</span><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">nothing will be dependent on device management, and can not be a requirement for enterprise scenarios. </span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Still in the phase of educating Google on various use-cases.</span><br>
</li></ul>
<li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">How much changes RP will be required to make - new AS? support a new API? new
JSON file?</span></li><ul>
<li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">George: OIDC breaks with WebID - some constructs remain, but not an OIDC flow
anymore. Top-level question - any desire how to do what they want to do while preserving existing identity flow</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Tim: that is added to a new roadmap section. What can we do to profile these
flow is create allow lists for those flows. May be able to classify OIDC flows. Are you ok that for 2 years advertisers leverage identity flows to continue tracking?</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">George: browsers could do without breaking the flow is what safari does - do
you want to log in to this website? If RP can advertise, that "this is OIDC provider I support". Very few RP open to a random IdP already. Easy for the browser to determine an identity flow - pause issuer during redirect and ask "do you want to log in" - will
kill all the advertisers who do not want to involve the users. Option to the user to remember the decision.</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Tim: The minute we ask RPs to make changes, Google will say "than ask RPs to
use this new API (for WebID from Google)</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">George: to make WebID work now, RPs have to implement a new AS that talks a new
protocol. </span><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">cannot do the code flow. Are we ok as Connect WG with that?</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Tim: us creating a band-aid solution does not seem right, if google solidifies
this API and it becomes standardized in W3C for example.</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">John: W3C standard does not necessarily mean adoption.</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">George: being identity guy for RPs, RP change over IdP change is a preference</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Nat:
</span><span lang="ja" style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Putting</span><span lang="en-US" style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"> just
one JSON file in RP is easier than a new AS.</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">John:
</span><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">I can see that the danger, t</span><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">he RPS
will add the file, which puts all the fork button networks, or in other evil tracking people like Google ad sets, into that file. </span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Nat: why does it have to be calling API? Instead of putting RP metadata file
at RP domain</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Tim: because that assumes RP supports all IdPs.</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Mike: we probably only get one shot to ask people to change things. Companies
are thinking of multiple phases of changes, but that is chaos. Zero to one opportunities. Many RPs will not change much unless web providers change a lot.</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">George: if RP only change once, WebID should be a smaller priority than decentralized.
RP will change whenever necessary to keep the traffic. RPs will need logged in traffic in the best interest of revenue stream. Log in walls if not pay walls. Dealing with decentralized identity is a larger change that the change we are talking about here. </span></li></ul>
<li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><font color="#000000" face="Calibri, Arial, Helvetica, sans-serif"><span style="font-size: 14.6667px;">Role of DIDs</span></font></li><ul>
<li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Tim: disagree. processing is different, but transmission of the identifier and
assertion remains the same.</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">George: no, dealing with a claim signed by a private key of a user is different
from a confidential client. Concept is similar but the code is different. Code change for decentralized identifier is important.</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Brian: concurring with George in difficulties in making these changes. Decentralized
may be similar concept but changes required are larger.</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Tim: we have to stop of thinking of DIDs as only for decentralized identity.
Why not use a spec as a structured identifier instead of Google creating a new identifier type. It is not only an SSI concept</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">George: not against DIDs being used more broadly. That is not going to stop RP
from saying "</span><span lang="ja" style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">I received your DID, now give</span><span lang="en-US" style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
</span><span lang="ja" style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">me your email</span><span lang="en-US" style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">". </span><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">You
can potentially build on top of DIDs and add additional cool features, and Apple and Google using pairwise pseudonymous identifiers would be great. </span></li></ul>
<li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Involvement of other browsers</span></li><ul>
<li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Mike: potential browser API will only build an ecosystem as far as browsers build
it - but Apple is hostile to participate. Unless Apple and Firefox in, we can't change the browser world - WebAuthn proved it.</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">John: I would not count on Firefox implementing anything like WebID soon</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Tim: firefox is at least loosely engaged with google. Apple is not even talking</span></li></ul>
<li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Vision: long-term solution</span></li><ul>
<li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Tim: For special browser calls, smaller group of 4 people will come up with a
more detailed agenda to have more structure. We have to ask - as OpenID, are we looking at sustaining things, or are we looking into a long-term solution like account chooser, etc?</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">George: long-term view but recognize there will be implementation hurdles and
make sure things do not break unpredictably.</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">John: looking at consolidated flows has to be grappled with. Web payments API
to prevent extra concents. How we combine Conect, Webauthn so that we have consolidated flows for the user is a high priority.</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">George: how to make customer journey better? Not just about authentication, but
all identity lifecycle including revocation. Next gen OIDC that works with the browsers.</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">John: in a privacy preserving way that preserves user experience. Much more free
to experiment - Google?</span></li></ul>
<li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Use-cases missing</span></li><ul>
<li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Nat: is there use-cases for WebID?</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">George: not in Google repo, but in IETF repo initiated by George and Vittorio: </span><a href="https://github.com/IDBrowserUseCases/docs"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">https://github.com/IDBrowserUseCases/docs</span></a></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Nat: Use-case and privacy considerations are very important. (privacy considerations)
should not be dictated by what Google believes is privacy preserving. For example, Floc is a terrible idea </span><a href="https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-idea"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-idea</span></a></li></ul>
<li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><font color="#000000" face="Calibri, Arial, Helvetica, sans-serif"><span style="font-size: 14.6667px;">Efforts to align UI/UX needed</span></font></li><ul>
<li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">George: a lot to learn in terms of user experience from webauthn. Do the user
understand what it is? Words, UX describing external authenticator is different per implementation…</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Tim: whole fact that UI continue being this hostile for over 20 years - will
be the devil. In Wifi alliance, got to agree the providers to follow UI/UX guide. It is unacceptable for each platforms. UI/UX certifications? Even chrome is not internally consistent.</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">George: Is there a place for foundation to have a stronger voice in UX. Sub working
group? Whatever we do at the protocol level should be a straight progression of where we want people to be.</span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Tim: FIDO has a UI/UX working group that seems to work quite well. </span></li><li style="margin-top:0;margin-bottom:0;vertical-align:middle" lang="en-US"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Nat/John: If output is some sort of the document that people are expected to
follow, IPR agreement should be present</span></li></ul>
</ul>
</ul>
<ul style="">
<li style=""><span style="margin: 0px; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Claims aggregation draft update</span></li><ul style="">
<li style=""><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Adam: not much to report on. Flows (in Credential Provider draft) are getting positive reviews as it sits today.
</span><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Adam will send
</span><span style="display: inline !important; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">send the text version of </span><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Credential
provider draft to </span><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">the ML, and will start </span><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">raising
issues against claims aggregation draft. </span></li></ul>
</ul>
</div>
<div style="">
<ul style="">
<li><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"> Quotes of the day</span></li><ul>
<li><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">"I received your DID, now give me your email"</span><br>
</li><li><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">UI/UX certifiaction needed</span></li></ul>
</ul>
<div style=""><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Full notes are
</span><a href="https://bitbucket.org/openid/connect/wiki/Connect%20Meeting%20Notes%202021-03-11%20Atlantic" title="https://bitbucket.org/openid/connect/wiki/Connect%20Meeting%20Notes%202021-03-11%20Atlantic"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">in
the Wiki</span></a><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"> </span></div>
</div>
</div>
</div>
</div>
<br>
</div>
</body>
</html>