<div dir="ltr"><div dir="auto">So these statements are in 800-63-3. It seems clear that the claimant could present claims that were not {validated, attested, verified, registered, whatever}</div><div dir="auto"><span style="background-color:transparent;color:rgb(69,68,65);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:16px;font-variant-numeric:normal;font-variant-east-asian:normal">* SP 800-63A sets requirements to achieve a given IAL. The three IALs reflect the options agencies may select from based on their risk profile and the potential harm caused by an attacker making a successful false claim of an identity. </span><br></div><div dir="auto"><span style="background-color:transparent;color:rgb(69,68,65);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:16px;font-variant-numeric:normal;font-variant-east-asian:normal"><span style="background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal">* A digital identity is always unique in the context of a digital service, but does not necessarily need to uniquely identify the subject in all contexts. In other words, accessing a digital service may not mean that the subject’s real-life identity is known. Identity proofing establishes that a subject is who they claim to be. Digital authentication is the process of determining the <u>validity of one or more authenticators used to claim</u> a digital identity</span></span></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Peace ..tom</div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jun 14, 2019 at 1:29 PM Anthony Nadalin <<a href="mailto:tonynad@microsoft.com">tonynad@microsoft.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt;color:black">
It sure is look at ISO documents and NIST documents <br>
<br>
</div>
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt;color:black">
<span id="gmail-m_4188067700522407590OutlookSignature">
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt;color:black">
Get <a href="https://aka.ms/ghei36" target="_blank">Outlook for Android</a></div>
</span><br>
</div>
<hr style="display:inline-block;width:98%">
<div id="gmail-m_4188067700522407590divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Tom Jones <<a href="mailto:thomasclinganjones@gmail.com" target="_blank">thomasclinganjones@gmail.com</a>><br>
<b>Sent:</b> Friday, June 14, 2019 12:56:00 PM<br>
<b>To:</b> Artifact Binding/Connect Working Group<br>
<b>Cc:</b> Mike Jones; Torsten Lodderstedt; Anthony Nadalin<br>
<b>Subject:</b> Re: [Openid-specs-ab] Review of openid-connect-4-identity-assurance-04</font>
<div> </div>
</div>
<div>
<div dir="auto">Tony: that's not the real world meaning of claim. A claim of title is not a title. It is only a title when it is recognized and registered. So a more historically accurate term would be a registered claim.<br>
<br>
<div>thx ..Tom (mobile)</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Jun 14, 2019, 9:48 AM Anthony Nadalin via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div class="gmail-m_4188067700522407590m_1061373888540653535WordSection1">
<p class="MsoNormal">It’s not a claim then, it’s a statement, it does not matter who has the claim, the issuer or the beholder, it’s still in doubt. I don’t understand enough of the “verified” statement since the language is vague in the specification, is it
the provenance of the data or the truth of the data ?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal"><b>From:</b> Mike Jones <<a href="mailto:Michael.Jones@microsoft.com" rel="noreferrer" target="_blank">Michael.Jones@microsoft.com</a>>
<br>
<b>Sent:</b> Friday, June 14, 2019 9:45 AM<br>
<b>To:</b> Anthony Nadalin <<a href="mailto:tonynad@microsoft.com" rel="noreferrer" target="_blank">tonynad@microsoft.com</a>>; Artifact Binding/Connect Working Group <<a href="mailto:openid-specs-ab@lists.openid.net" rel="noreferrer" target="_blank">openid-specs-ab@lists.openid.net</a>>;
Torsten Lodderstedt <<a href="mailto:torsten@lodderstedt.net" rel="noreferrer" target="_blank">torsten@lodderstedt.net</a>><br>
<b>Subject:</b> Re: Review of openid-connect-4-identity-assurance-04<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal" style="margin-bottom:12pt"><span style="font-family:Arial,sans-serif;color:black">A claim is a statement made by the issuer. A verified claim is one with evidence backing it beyond the veracity of the issuer.
<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt"><span style="font-family:Arial,sans-serif;color:black">Doubt or belief are both properties of the beholder - not the issuer.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Arial,sans-serif;color:black">-- Mike<u></u><u></u></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="98%" align="center">
</div>
<div id="gmail-m_4188067700522407590m_1061373888540653535divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> Anthony Nadalin<br>
<b>Sent:</b> Friday, June 14, 2019 6:44:29 PM<br>
<b>To:</b> Artifact Binding/Connect Working Group; Torsten Lodderstedt<br>
<b>Cc:</b> Mike Jones<br>
<b>Subject:</b> RE: Review of openid-connect-4-identity-assurance-04</span> <u></u><u></u></p>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal">A claim is something in doubt, how can you have a verified claim?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal"><b>From:</b> Openid-specs-ab <<a href="mailto:openid-specs-ab-bounces@lists.openid.net" rel="noreferrer" target="_blank">openid-specs-ab-bounces@lists.openid.net</a>>
<b>On Behalf Of </b>Mike Jones via Openid-specs-ab<br>
<b>Sent:</b> Friday, June 14, 2019 8:42 AM<br>
<b>To:</b> Torsten Lodderstedt <<a href="mailto:torsten@lodderstedt.net" rel="noreferrer" target="_blank">torsten@lodderstedt.net</a>><br>
<b>Cc:</b> Mike Jones <<a href="mailto:Michael.Jones@microsoft.com" rel="noreferrer" target="_blank">Michael.Jones@microsoft.com</a>>;
<a href="mailto:openid-specs-ab@lists.openid.net" rel="noreferrer" target="_blank">
openid-specs-ab@lists.openid.net</a><br>
<b>Subject:</b> Re: [Openid-specs-ab] Review of openid-connect-4-identity-assurance-04<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt"><span style="font-family:Arial,sans-serif;color:black">I agree with "verified_claims".<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Arial,sans-serif;color:black">Thanks!<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Arial,sans-serif;color:black">-- Mike<u></u><u></u></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="1" width="98%" align="center">
</div>
<div id="gmail-m_4188067700522407590m_1061373888540653535x_divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> Torsten Lodderstedt <<a href="mailto:torsten@lodderstedt.net" rel="noreferrer" target="_blank">torsten@lodderstedt.net</a>><br>
<b>Sent:</b> Friday, June 14, 2019 5:47:17 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Daniel Fett; <a href="mailto:openid-specs-ab@lists.openid.net" rel="noreferrer" target="_blank">
openid-specs-ab@lists.openid.net</a><br>
<b>Subject:</b> Re: Review of openid-connect-4-identity-assurance-04</span> <u></u><u></u></p>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt">Hi Mike,<br>
<br>
Thanks a lot for your substantial feedback.<br>
<br>
While I'm incorporating it, I would like to sort out one question:<br>
<br>
> On 1. Jun 2019, at 02:16, Mike Jones <<a href="mailto:Michael.Jones@microsoft.com" rel="noreferrer" target="_blank">Michael.Jones@microsoft.com</a>> wrote:<br>
> <br>
> All Sections: Generalize kinds of verified claims. The most important issue is to generalize the goal of the document from defining how to use “verified person data” to defining how to use “verified data”. This work isn’t happening in a vacuum. There
are other efforts to define representations of verified claims in the industry, including
<a href="https://w3c.github.io/vc-data-model/" rel="noreferrer" target="_blank">https://w3c.github.io/vc-data-model/</a>, that take this more general approach, but propose much more complicated data representations that are not based on JWTs. It would be highly
beneficial to have a simple general JWT-based “verified data” representation that is general-purpose. Indeed, that’s the possibility that excites me about this work. Don’t get me wrong – I believe that all the particulars for verified people data can and
should remain. The main concrete change needed is to rename “verified_person_data” to “verified_data”.
<br>
<br>
I think “verified_claims” would fit even better. What do you think?<br>
<br>
best regards,<br>
Torsten. <br>
<br>
<u></u><u></u></p>
</div>
</div>
</div>
</div>
_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net" rel="noreferrer" target="_blank">Openid-specs-ab@lists.openid.net</a><br>
<a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.openid.net%2Fmailman%2Flistinfo%2Fopenid-specs-ab&data=02%7C01%7Ctonynad%40microsoft.com%7Cc0b190309bb142bc31df08d6f1025a7b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636961389757361746&sdata=CWslAGBkNNR%2FtK9MGiEBOpOmInmd0jfZiFTEEwEKWg0%3D&reserved=0" rel="noreferrer noreferrer" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
</blockquote>
</div>
</div>
</div>
</blockquote></div>