<html><head><style id="pgp_css" type="text/css"><!----></style><style id="css_styles" type="text/css"><!--blockquote.cite { margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc }
blockquote.cite2 {margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc; margin-top: 3px; padding-top: 0px; }
a img { border: 0px; }
li[style='text-align: center;'], li[style='text-align: center; '], li[style='text-align: right;'], li[style='text-align: right; '] { list-style-position: inside;}
body { font-family: Segoe UI; font-size: 12pt; }
.quote { margin-left: 1em; margin-right: 1em; border-left: 5px #ebebeb solid; padding-left: 0.3em; }--></style></head><body><div>If it is offline then it is not SIOP, unless I am missing something.</div><div><br /></div><div>A QR to set up a local BLE or Ultra wideband connection is a separate thing, and not subject to the same sort of Phishing attack.</div><div><br /></div><div>John B.</div>
<div>------ Original Message ------</div>
<div>From: "Tom Jones" <<a href="mailto:thomasclinganjones@gmail.com">thomasclinganjones@gmail.com</a>></div>
<div>To: "John Bradley" <<a href="mailto:ve7jtb@ve7jtb.com">ve7jtb@ve7jtb.com</a>>; "Artifact Binding/Connect Working Group" <<a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a>></div>
<div>Cc: "Kristina Yasuda" <<a href="mailto:kristina.yasuda@microsoft.com">kristina.yasuda@microsoft.com</a>></div>
<div>Sent: 7/12/2021 7:33:57 PM</div>
<div>Subject: Re: [Openid-specs-ab] DHS mDL RFI response from OpenID Foundation</div><div><br /></div>
<div id="x2be860ff1073457"><blockquote cite="CAK2Cwb4sugq+WpYbh2R=Wz2oRgQRVPyVjyXriQ1C1sQMCFrw-A@mail.gmail.com" type="cite" class="cite2">
<div dir="ltr">I don't think that the DHS or ISO imagined that the QR would be used in a fully on-line scenario. The issue is off-line support. Inclusion is important for state issued identification.<div><br clear="all" /><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>..tom</div></div></div></div><br /></div></div><br /><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jul 12, 2021 at 4:28 PM John Bradley via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net">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><div>There may be limited cases where the device presenting a QR code is trusted, but any general system using a QR code presented in the browser or CIBA opens a huge Phishing opportunity.</div><div><br /></div><div>The attacker only needs to reverse proxy the QR code and will wind up capturing the session once the user authenticates in the back channel.</div><div><br /></div><div>I would not recommend this as a general cross device solution. </div><div><br /></div><div>John B.</div>
<div><br /></div>
<div>------ Original Message ------</div>
<div>From: "Torsten Lodderstedt via Openid-specs-ab" <<a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a>></div>
<div>To: "Kristina Yasuda" <<a href="mailto:kristina.yasuda@microsoft.com">kristina.yasuda@microsoft.com</a>></div>
<div>Cc: "Torsten Lodderstedt" <<a href="mailto:torsten@lodderstedt.net">torsten@lodderstedt.net</a>>; "<a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a>" <<a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a>></div>
<div>Sent: 6/30/2021 4:06:28 PM</div>
<div>Subject: Re: [Openid-specs-ab] DHS mDL RFI response from OpenID Foundation</div><div><br /></div>
<div id="gmail-m_4865740571424174926x33402571a3e44f2" style="overflow-wrap: break-word;"><blockquote cite="http://E72722D2-CB88-44DB-AE4D-5BECEC730378@lodderstedt.net" type="cite" class="gmail-m_4865740571424174926cite2">
Hi Kristina,<br /><div><br /><blockquote type="cite" class="cite"><div>Am 29.06.2021 um 18:48 schrieb Kristina Yasuda <<a href="mailto:kristina.yasuda@microsoft.com">kristina.yasuda@microsoft.com</a>>:</div><br /><div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI";border:1pt none windowtext;padding:0mm;background-color:white">Hi Torsten, </span><span lang="EN-US"><u></u><u></u></span></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI";border:1pt none windowtext;padding:0mm;background-color:white"><br />> Can you please elaborate? SIOP as it Stands today is tied to the response type<span> </span></span><span style="font-size:10.5pt;font-family:"Yu Gothic UI";border:1pt none windowtext;padding:0mm;background-color:white">„<span lang="EN-US">id_token</span>“<span lang="EN-US">, i.e. the RP sends the user agent to the SIOP on the same device. Transaction integrity is ensured by binding the nonce in the request to a cookie in this user agent. How do you envision to cross the boundary between devices and what are the consequences on the security of the flow? Can you share a sequence diagram?</span></span><span lang="EN-US" style="font-family:Calibri,sans-serif"><u></u><u></u></span></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI";border:1pt none windowtext;padding:0mm;background-color:white"><br />The cross device flow could look like this:</span><span lang="EN-US" style="font-family:Calibri,sans-serif"><u></u><u></u></span></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI";border:1pt none windowtext;padding:0mm;background-color:white">1/ The user browses to the RP website</span><span lang="EN-US" style="font-family:Calibri,sans-serif"><u></u><u></u></span></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI";border:1pt none windowtext;padding:0mm;background-color:white">2/ The RP displays a QR code with request_uri in the user browser on device A</span><span lang="EN-US" style="font-family:Calibri,sans-serif"><u></u><u></u></span></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI";border:1pt none windowtext;padding:0mm;background-color:white">(deeplink will be used in same-device flow)</span><span lang="EN-US" style="font-family:Calibri,sans-serif"><u></u><u></u></span></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI";border:1pt none windowtext;padding:0mm;background-color:white">3/ The user uses device B (Mobile Wallet) to scan the QR code, dereference it and fetch SIOP request object from the request_uri</span><span lang="EN-US" style="font-family:Calibri,sans-serif"><u></u><u></u></span></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI";border:1pt none windowtext;padding:0mm;background-color:white">(processes like DID resolution can occur in-between)</span><span lang="EN-US" style="font-family:Calibri,sans-serif"><u></u><u></u></span></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI";border:1pt none windowtext;padding:0mm;background-color:white">4/ Mobile wallet sends ID Token (with embedded VP when VP is returned) in HTTP POST request to the RP</span><span lang="EN-US" style="font-family:Calibri,sans-serif"><u></u><u></u></span></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI";border:1pt none windowtext;padding:0mm;background-color:white">Sequence diagram of the implementation can be found here (note that some element of the flow might have changed from Dec. 2020):</span><span lang="EN-US" style="font-family:Calibri,sans-serif"><u></u><u></u></span></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI";border:1pt none windowtext;padding:0mm;background-color:white"><a href="https://www.google.com/url?q=https://us02web.zoom.us/rec/play/BRBDWWUtB9HsmE88cJQwC9OH4k-QM9cdg8UYJXm6wwj-Yt54f7QMPPFqmQn-vtGAVNJgV9fGBeGN3eZR.QYMKFKYkJzdmdyaG&source=gmail-imap&ust=1625590112000000&usg=AOvVaw1_bCqMWMvMUEJk1Ap7exgk" style="color:blue;text-decoration:underline">https://us02web.zoom.us/rec/play/BRBDWWUtB9HsmE88cJQwC9OH4k-QM9cdg8UYJXm6wwj-Yt54f7QMPPFqmQn-vtGAVNJgV9fGBeGN3eZR.QYMKFKYkJzdmdyaG</a><br />It is a presentation at DIF Interoperability WG.</span></div></div></div></blockquote><div><br /></div>That’s an interesting flow, but not a standard SIOP flow for the following reasons: </div><div><br /></div><div>- the RP needs to distinguish on device and split device flow. A standard OIDC RP should just send the request (with or w/o request object) to the SIOP on the same device via redirect. </div><div>- will most likely be received by the backend of the RP, whereas in the post respond mode, the OP is supposed to send the response to the RP through the front channel. Why is this important? Well, it allows the RP to (directly or indirectly) pick up the nonce from a Cookie and compare that to the nonce in the ID Token. This would ensure transaction integrity and prevents replay attacks, which is impossible in this flow simply because the RP does not have access to any data on the originating device.</div><div><br /></div><div>Question: is the user supposed to scan a QR code shown on the device of the police officer when presenting her mDL? </div><div><br /></div><div><blockquote type="cite" class="cite"><div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI""><u></u><u></u></span></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI""><u></u> <u></u></span></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI";border:1pt none windowtext;padding:0mm;background-color:white">> I think the SIOP should expose a CIBA style interface to allow direct engagement from the verifier with the reader. The device engagement data could be used to share the endpoint location and so on.</span><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI""><u></u><u></u></span></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI""><u></u> <u></u></span></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI";border:1pt none windowtext;padding:0mm;background-color:white">Interesting. Do you mean holder sending a request direcly to the reader's Backchannel Authentication Endpoint? I am not very familiar with CIBA flows but we should probably explore more (cc: Tony)</span></div></div></div></blockquote><div><br /></div>yes. That’s what I mean. </div><div><br /></div><div>best regards,</div><div>Torsten. </div><div><br /><blockquote type="cite" class="cite"><div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI""><u></u><u></u></span></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US"><u></u> <u></u></span></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI";border:1pt none windowtext;padding:0mm;background-color:white">Thank you,<u></u><u></u></span></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white;vertical-align:baseline"><span lang="EN-US" style="font-size:10.5pt;font-family:"Yu Gothic UI";border:1pt none windowtext;padding:0mm;background-color:white">Kristina<u></u><u></u></span></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-size:11pt;font-family:"Noto Sans CJK JP Medium",sans-serif;color:rgb(68,114,196)"><u></u> <u></u></span></div><div><div style="border-style:solid none none;border-top-width:1pt;border-top-color:rgb(225,225,225);padding:3pt 0mm 0mm"><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><b><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif">From:</span></b><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif"><span> </span>Torsten Lodderstedt <<a href="mailto:torsten@lodderstedt.net" style="color:blue;text-decoration:underline">torsten@lodderstedt.net</a>><span> </span><br /><b>Sent:</b><span> </span>Saturday, June 26, 2021 1:35 AM<br /><b>To:</b><span> </span>Kristina Yasuda <<a href="mailto:Kristina.Yasuda@microsoft.com" style="color:blue;text-decoration:underline">Kristina.Yasuda@microsoft.com</a>><br /><b>Cc:</b><span> </span><a href="mailto:Openid-specs-ab@lists.openid.net" style="color:blue;text-decoration:underline">Openid-specs-ab@lists.openid.net</a><br /><b>Subject:</b><span> </span>Re: [Openid-specs-ab] DHS mDL RFI response from OpenID Foundation<u></u><u></u></span></div></div></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US"><u></u> <u></u></span></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US">Hi Kristina,<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US"><br /><br /><u></u><u></u></span></div><blockquote style="margin-top:5pt;margin-bottom:5pt"><p class="MsoNormal" style="margin:0mm 0mm 12pt;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US">Am 26.06.2021 um 04:32 schrieb Kristina Yasuda <<a href="mailto:Kristina.Yasuda@microsoft.com" style="color:blue;text-decoration:underline">Kristina.Yasuda@microsoft.com</a>>:<u></u><u></u></span></p></blockquote></div><blockquote style="margin-top:5pt;margin-bottom:5pt"><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Tahoma,sans-serif"></span><span lang="EN-US"><u></u><u></u></span></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Calibri,sans-serif">Thank you for the feedback, Torsten. Please find comments in-line below.<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Calibri,sans-serif">@Everyone, I am attaching the current version of the response. Kind reminder that we set the new deadline for comments to be<span> </span><b>June 30th</b>.<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></div></div><div><div><div style="margin:0mm;background-color:white"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(32,31,30)">- the example on p7 uses „verified_claims“ syntax, so it might be worthwhile mentioning OpenID Connect 4 Identity Assurance in the document<u></u><u></u></span></div><div style="margin:0mm;background-color:white"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(32,31,30)">-> I added the following text after the example on p7. Let me know if you want it changed. <u></u><u></u></span></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(32,31,30)">"The “verified_claims” container element used in the example above is taken from OpenID Connect for Identity Assurance 1.0 specification (ekyc-ida) in OpenID Foundation. The usage of “verified_claims” container element allows to include information how the identity of a natural person has been verified in compliance with a certain law."<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(32,31,30)">Note that the Annex part has been submitted to the ISO mDL WG prior to this DHS response document, and this change will be proposed in the ISO document in the next revision cycle.<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";background-color:white"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(32,31,30)"><u></u> <u></u></span></div></div></div><div><div style="margin:0mm;background-color:white"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(32,31,30)">- section 7.1.3.4.4: how is the request sent from the reader to the SIOP? I’m asking since I thought those parties would live on different devices<u></u><u></u></span></div><div style="margin:0mm;background-color:white"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(32,31,30)">->"Over the Internet", to borrow the terminology used in ISO. RP does not have to be on the same device as SIOP.<u></u><u></u></span></div></div></div></div></blockquote><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US"><u></u> <u></u></span></div></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US">Can you please elaborate? SIOP as it Stands today is tied to the response type „id_token“, i.e. the RP sends the user agent to the SIOP on the same device. Transaction integrity is ensured by binding the nonce in the request to a cookie in this user agent. How do you envision to cross the boundary between devices and what are the consequences on the security of the flow? Can you share a sequence diagram?<u></u><u></u></span></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US"><br /><br /><u></u><u></u></span></div><blockquote style="margin-top:5pt;margin-bottom:5pt"><div><div><div><div style="margin:0mm;background-color:white"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(32,31,30)">The question made me think that mDL specification does have a specific "device engagement" step during which registration/discovery information is passed in CBOR over NFC or QR code, so maybe we can leverage that for SIOP discovery/registration - need to think more.<u></u><u></u></span></div></div></div></div></blockquote><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US"><u></u> <u></u></span></div></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US">I think the SIOP should expose a CIBA style interface to allow direct engagement from the verifier with the reader. The device engagement data could be used to share the endpoint location and so on.<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US"><br /><br /><u></u><u></u></span></div><blockquote style="margin-top:5pt;margin-bottom:5pt"><div><div><div><div style="margin:0mm;background-color:white"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(32,31,30)"><u></u> <u></u></span></div></div><div><div style="margin:0mm;background-color:white"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(32,31,30)">- Generally: would it be possible to share more context with the WG? It seems like a lot of knowledge about ISO/IEC 18013-5 is required to understand the proposal<u></u><u></u></span></div><div style="margin:0mm;background-color:white"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(32,31,30)">-> Currently, OIDC in mDL is used for the verifier to talk to the Issuing authority to retrieve mDL data using the access token received from the user. This direct path to the Issuing Authority has raised concerns from verifiers and resulted in the need for "over the internet" solution directly between user and the verifier, so the SIOP was proposed. <u></u><u></u></span></div><div style="margin:0mm;background-color:white"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(32,31,30)"><u></u> <u></u></span></div></div><div><div style="margin:0mm;background-color:white"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(32,31,30)">- typo on p2 2nd paragraph: "OpenII Connect“ -> OpenID Connect <u></u><u></u></span></div><div style="margin:0mm;background-color:white"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(32,31,30)">-> corrected.<u></u><u></u></span></div></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></div></div></div></blockquote><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US"><br />best regards,<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US">Torsten.<br /><br /><u></u><u></u></span></div><blockquote style="margin-top:5pt;margin-bottom:5pt"><div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Calibri,sans-serif">Best,<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Calibri,sans-serif">Kristina<u></u><u></u></span></div></div><div class="MsoNormal" align="center" style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af";text-align:center"><span lang="EN-US"><hr size="2" width="98%" align="center" /></span></div><div id="gmail-m_4865740571424174926divRplyFwdMsg"><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><b><span style="font-size:11pt">差出人</span></b><b><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif">:</span></b><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif"><span> </span>Torsten Lodderstedt <<a href="mailto:torsten@lodderstedt.net" style="color:blue;text-decoration:underline">torsten@lodderstedt.net</a>><br /></span><b><span style="font-size:11pt">送信日時</span></b><b><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif">:</span></b><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif"><span> </span>2021</span><span style="font-size:11pt">年</span><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif">6</span><span style="font-size:11pt">月</span><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif">14</span><span style="font-size:11pt">日</span><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif"><span> </span>1:43<br /></span><b><span style="font-size:11pt">宛先</span></b><b><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif">:</span></b><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif"><span> </span>Artifact Binding/Connect Working Group <<a href="mailto:openid-specs-ab@lists.openid.net" style="color:blue;text-decoration:underline">openid-specs-ab@lists.openid.net</a>><br /><b>CC:</b><span> </span>Kristina Yasuda <<a href="mailto:Kristina.Yasuda@microsoft.com" style="color:blue;text-decoration:underline">Kristina.Yasuda@microsoft.com</a>><br /></span><b><span style="font-size:11pt">件名</span></b><b><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif">:</span></b><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif"><span> </span>Re: [Openid-specs-ab] DHS mDL RFI response from OpenID Foundation</span><span lang="EN-US"><u></u><u></u></span></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US"> <u></u><u></u></span></div></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US">Hi, <span> </span><u></u><u></u></span></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US"><u></u> <u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US">thanks for sharing the draft response. <u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US"><u></u> <u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US">Here are my comments:<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US"><u></u> <u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US">- the example on p7 uses „verified_claims“ syntax, so it might be worthwhile mentioning OpenID Connect 4 Identity Assurance in the document<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US">- section 7.1.3.4.4: how is the request sent from the reader to the SIOP? I’m asking since I thought those parties would live on different devices<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US">- Generally: would it be possible to share more context with the WG? It seems like a lot of knowledge about ISO/IEC 18013-5 is required to understand the proposal<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US">- typo on p2 2nd paragraph: "OpenII Connect“ -> OpenID Connect <u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US"><u></u> <u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US">best regards,<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US">Torsten. <u></u><u></u></span></div></div><div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US"><br /><br /><u></u><u></u></span></div><blockquote style="margin-top:5pt;margin-bottom:5pt"><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US">Am 14.06.2021 um 09:32 schrieb Kristina Yasuda via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net" style="color:blue;text-decoration:underline">openid-specs-ab@lists.openid.net</a>>:<u></u><u></u></span></div></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US"><u></u> <u></u></span></div><div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Calibri,sans-serif">Dear All,<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Calibri,sans-serif">As discussed during the last Connect WG call, circulating the draft response from OpenID Foundation to<span> </span><span style="background-color:white">DHS RFI on mDL (mobile Driving License)</span>.<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Calibri,sans-serif">We wrote it with Tony and Tom Jones, and it has been reviewed by Gail, Mike and Nat.<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Calibri,sans-serif">If you have any comments please send them<span> </span><b><u>by June 16th</u></b><span> </span>to the ML, so that we have time to reflect them before the submission deadline on June 18th.<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Calibri,sans-serif">Apologies for circulating last minute. We can also discuss the questions and comments at tomorrow's Pacific Connect WG call.<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></div></div><div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Calibri,sans-serif">Below are links to the original RFI from DHS:</span><span lang="EN-US" style="font-size:9pt;font-family:Helvetica,sans-serif"><u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Calibri,sans-serif">- <a href="https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://nam06.safelinks.protection.outlook.com/?url%253Dhttps%25253A%25252F%25252Fwww.google.com%25252Furl%25253Fq%25253Dhttps%25253A%25252F%25252Fwww.govinfo.gov%25252Fcontent%25252Fpkg%25252FFR-2021-04-19%25252Fpdf%25252F2021-07957.pdf%252526source%25253Dgmail-imap%252526ust%25253D1624260775000000%252526usg%25253DAOvVaw1aQ3sHxbIfB3aUEbHijNiu%2526data%253D04%25257C01%25257CKristina.Yasuda%252540microsoft.com%25257Ce30e241796ab495de8d708d92f10778b%25257C72f988bf86f141af91ab2d7cd011db47%25257C1%25257C0%25257C637592570519543639%25257CUnknown%25257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%25253D%25257C1000%2526sdata%253D1m5%25252BWMnsfw2%25252FthhyDTIMmjQ1kcFMESE1HYl2AYyzNG4%25253D%2526reserved%253D0%26source%3Dgmail-imap%26ust%3D1625279576000000%26usg%3DAOvVaw25ODNKS8bcom3UuBgSzHm_&source=gmail-imap&ust=1625590112000000&usg=AOvVaw1YlLh-3clOQc3phpnjy2vF" style="color:blue;text-decoration:underline">https://www.govinfo.gov/content/pkg/FR-2021-04-19/pdf/2021-07957.pdf</a></span><span lang="EN-US" style="font-size:9pt;font-family:Helvetica,sans-serif"><u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-size:9pt;font-family:Helvetica,sans-serif">- <a href="https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://nam06.safelinks.protection.outlook.com/?url%253Dhttps%25253A%25252F%25252Fwww.google.com%25252Furl%25253Fq%25253Dhttps%25253A%25252F%25252Fwww.aamva.org%25252F21_4_19-Legislative-Alert-DHS-Requests-Information-for-REAL-ID-Mobile-Drivers-License-Rulemaking%25252F%252526source%25253Dgmail-imap%252526ust%25253D1624260775000000%252526usg%25253DAOvVaw2bNG6F2m2_TGCHTp7Q4ykE%2526data%253D04%25257C01%25257CKristina.Yasuda%252540microsoft.com%25257Ce30e241796ab495de8d708d92f10778b%25257C72f988bf86f141af91ab2d7cd011db47%25257C1%25257C0%25257C637592570519553602%25257CUnknown%25257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%25253D%25257C1000%2526sdata%253DvvUYqsUJGAqbo1dfdTphxDzcc65B%25252BxJwUFiZdbQIJ3c%25253D%2526reserved%253D0%26source%3Dgmail-imap%26ust%3D1625279576000000%26usg%3DAOvVaw3tYuhjE_rs-z1J6wxOAJt8&source=gmail-imap&ust=1625590112000000&usg=AOvVaw0Qat_vFb0I0UHzHlT9Z_Ge" style="color:blue;text-decoration:underline"><span style="font-size:12pt;font-family:Calibri,sans-serif">https://www.aamva.org/21_4_19-Legislative-Alert-DHS-Requests-Information-for-REAL-ID-Mobile-Drivers-License-Rulemaking/</span></a><u></u><u></u></span></div></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-size:9pt;font-family:Helvetica,sans-serif"><u></u> <u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Calibri,sans-serif">Kindest Regards,<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Calibri,sans-serif">Kristina<u></u><u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></div></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US"><Draft DHS RFI Response - mDL_v01.pdf></span><span lang="EN-US" style="font-size:9pt;font-family:Helvetica,sans-serif">_______________________________________________<br />Openid-specs-ab mailing list<br /></span><span lang="EN-US"><a href="mailto:Openid-specs-ab@lists.openid.net" style="color:blue;text-decoration:underline"><span style="font-size:9pt;font-family:Helvetica,sans-serif">Openid-specs-ab@lists.openid.net</span></a></span><span lang="EN-US" style="font-size:9pt;font-family:Helvetica,sans-serif"><br /></span><span lang="EN-US"><a href="https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://nam06.safelinks.protection.outlook.com/?url%253Dhttps%25253A%25252F%25252Fwww.google.com%25252Furl%25253Fq%25253Dhttp%25253A%25252F%25252Flists.openid.net%25252Fmailman%25252Flistinfo%25252Fopenid-specs-ab%252526source%25253Dgmail-imap%252526ust%25253D1624260775000000%252526usg%25253DAOvVaw2b8TMjt7LljoUVyGDrXZOz%2526data%253D04%25257C01%25257CKristina.Yasuda%252540microsoft.com%25257Ce30e241796ab495de8d708d92f10778b%25257C72f988bf86f141af91ab2d7cd011db47%25257C1%25257C0%25257C637592570519563554%25257CUnknown%25257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%25253D%25257C1000%2526sdata%253D83eU9%25252FL%25252FtJznWQyuB0uyK3Thh%25252FrNJoB5Ef0Lr7buzI8%25253D%2526reserved%253D0%26source%3Dgmail-imap%26ust%3D1625279576000000%26usg%3DAOvVaw1SJcRdEpSQPS2MOiNBmSol&source=gmail-imap&ust=1625590112000000&usg=AOvVaw1blbDFPs71NhRC1z4Le5UZ" style="color:blue;text-decoration:underline"><span style="font-size:9pt;font-family:Helvetica,sans-serif">https://www.google.com/url?q=http://lists.openid.net/mailman/listinfo/openid-specs-ab&source=gmail-imap&ust=1624260775000000&usg=AOvVaw2b8TMjt7LljoUVyGDrXZOz</span></a><u></u><u></u></span></div></div></blockquote></div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US"><u></u> <u></u></span></div></div></div><div><div style="margin:0mm;font-size:12pt;font-family:"\00ff2d\00ff33 \00ff30\0030b4\0030b7\0030c3\0030af""><span lang="EN-US"><Draft DHS RFI Response - mDL_v02.docx></span></div></div></div></blockquote></div></div></div></blockquote></div><br /></blockquote></div>
</div>_______________________________________________<br />
Openid-specs-ab mailing list<br />
<a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a><br />
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" rel="noreferrer">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br />
</blockquote></div>
</blockquote></div>
</body></html>