<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Orie<div><br></div><div>I think I’m still struggling with the use case / protocol flow here. Am I correct to understand the kind of flow you’re suggesting is not an OAuth based flow? If so what are the usual mechanisms that link verifier & wallet sessions together being replaced with or why are they not applicable in this situation? How does the wallet know the RP wants a credential?</div><div><br></div><div>Thanks</div><div><br></div><div>Joseph</div><div><br></div><div><br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On 16 Feb 2024, at 00:38, Orie Steele via Openid-specs-digital-credentials-protocols <openid-specs-digital-credentials-protocols@lists.openid.net> wrote:</div><br class="Apple-interchange-newline"><div><div dir="auto">I initially said assume the endpoint is negotiated out of band.<div dir="auto"><br></div><div dir="auto">I'd assume the wallet would process the response of the post body to know what to do next.</div><div dir="auto"><br></div><div dir="auto">The response is another place where the RP might demand extra information, for example, providing a fresh nonce and asking for a new presentation... And possibly requiring a different presentation endpoint.</div><div dir="auto"><br></div><div dir="auto">One obvious place where the wallet might initially learn of the presentation endpoint, would be when it requests a nonce for a scope / purpose.</div><div dir="auto"><br></div><div dir="auto">If folks want to build negotiation into this layer, that seems fine to me.</div><div dir="auto"><br></div><div dir="auto">But in order to keep things simple I think it's best to focus only on the presentation endpoint.</div><div dir="auto"><br></div><div dir="auto">What http methods does it support?</div><div dir="auto"><br></div><div dir="auto">What content types? </div><div dir="auto"><br></div><div dir="auto">What query parameters?</div><div dir="auto"><br></div><div dir="auto">Which http headers?</div><div dir="auto"><br></div><div dir="auto">I'd say the simplest solution looks like this:</div><div dir="auto"><br></div><div dir="auto">POST <a href="https://rp.example/presentations">https://rp.example/presentations</a></div><div dir="auto">--content-type application/sd-jwt / mDoc / cwt</div><div dir="auto">--accept application/json </div><div dir="auto">body (the sd-jwt / mdoc / cwt)</div><div dir="auto"><br></div><div dir="auto">This way it's obvious what media type the client is sending, and what media type the client is requesting as a response.</div><div dir="auto"><br></div><div dir="auto">Query parameters and headers are still available to handle state management and authorization.</div><div dir="auto"><br></div><div dir="auto">Complexity can be layered on later... For many cases, the complexity might be unavoidable.</div><div dir="auto"><br></div><div dir="auto">But for simple cases, like a wallet that only stores a single credential type, and a relying party that only accepts a single claim from a single credential type, it will be trivial to present credentials.</div><div dir="auto"><br></div><div dir="auto">As a concrete use case imagine relying parties that only care about over 18, and wallets that only store age verification credentials... Being forced to implement an open ended arbitrary claims query language just to support this is massive overkill.</div><div dir="auto"><br></div><div dir="auto">Having a simple way to present credentials to an RP doesn't preclude a complex query system, it just doesn't require it / enforce it as a barrier to adoption.</div><div dir="auto"><br></div><div dir="auto">OS</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Thu, Feb 15, 2024, 6:04 PM Brian Campbell <<a href="mailto:bcampbell@pingidentity.com">bcampbell@pingidentity.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">How does a wallet (or user of a wallet) know to send a presentation to this endpoint? Or know the endpoint? What happens after, i.e., what's the response have? </div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 15, 2024, 3:03 PM Orie Steele via Openid-specs-digital-credentials-protocols <<a href="mailto:openid-specs-digital-credentials-protocols@lists.openid.net" target="_blank" rel="noreferrer">openid-specs-digital-credentials-protocols@lists.openid.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div><div class="gmail_quote"><div dir="ltr" class="gmail_attr"><br></div><div dir="ltr"><div>( I signed the contributor agreement in docusign ).<br><br></div><div>My ideal flow:<br><br>GET relying-party.example/nonce<br>POST relying-party.example/presentations<br><br>If the RP wants to demand extra state commitments from the wallet, that's fine, but if the wallet just wants a nonce to make a presentation, the wallet should be able to just get a nonce.<br><br>Once the wallet has used the nonce, the wallet wants to send the presentation to the RP.<br><br>If the RP wants to demand extra state commitments from the wallet, that's fine, but if the wallet just wants to send a presentation, the wallet should be able to just send a presentation.<br><br>In other words, all the parameters that are "not a nonce" and "not a presentation" are getting in the way of a simple spec.<br><br>We have a proposal for a simple endpoint for getting nonces:<br><br><a href="https://datatracker.ietf.org/doc/draft-demarco-oauth-nonce-endpoint/" rel="noreferrer noreferrer noreferrer" target="_blank">https://datatracker.ietf.org/doc/draft-demarco-oauth-nonce-endpoint/</a><br><br>I want a simple endpoint for sending presentations.<br><br>Assume an api gateway will filter out anything it does not recognize as being encrypted to an internal verifier, or as a well formed signed presentation.<br>Assume the nonce is negotiated out of band.<br>Assume credential types are negotiated out of band.<br>Assume credential claims are negotiated out of band.<br>Assume the presentation endpoint is negotiated out of band.<br><br>How does a wallet submit a presentation?<br><br>Regards,<br><br>OS<br><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><span><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><br></div><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt; padding: 10pt 0pt;"><span style="font-size:10pt;font-family:Arial;color:rgb(32,18,77);background-color:transparent;font-weight:700;vertical-align:baseline;white-space:pre-wrap">ORIE STEELE</span><span style="font-size:10pt;font-family:Arial;color:rgb(32,18,77);background-color:transparent;font-weight:700;vertical-align:baseline;white-space:pre-wrap"><br></span><span style="font-size:10pt;font-family:Arial;color:rgb(32,18,77);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">Chief Technology Officer</span><span style="font-size:10pt;font-family:Arial;color:rgb(32,18,77);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><br></span><span style="font-size:8pt;font-family:Arial;color:rgb(32,18,77);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">www.transmute.industries</span></div><div style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt; padding: 0pt 0pt 10pt;"><a href="https://transmute.industries/" rel="noreferrer noreferrer noreferrer" target="_blank"><img width="96" height="22" src="https://ci3.googleusercontent.com/mail-sig/AIorK4xqtkj5psM1dDeDes_mjSsF3ylbEa5EMEQmnz3602cucAIhjLaHod-eVJq0E28BwrivrNSBMBc"></a><br></div></span></div></div></div></div></div></div></div>
</div></div></div>
-- <br>
Openid-specs-digital-credentials-protocols mailing list<br>
<a href="mailto:Openid-specs-digital-credentials-protocols@lists.openid.net" rel="noreferrer noreferrer" target="_blank">Openid-specs-digital-credentials-protocols@lists.openid.net</a><br>
<a href="https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols</a><br>
</blockquote></div>
<br>
<i style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;background:rgb(255,255,255);font-family:proxima-nova-zendesk,system-ui,-apple-system,system-ui,"Segoe UI",Roboto,Oxygen-Sans,Ubuntu,Cantarell,"Helvetica Neue",Arial,sans-serif;color:rgb(85,85,85)"><span style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;background:transparent;font-family:proxima-nova-zendesk,system-ui,-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Oxygen-Sans,Ubuntu,Cantarell,"Helvetica Neue",Arial,sans-serif;font-weight:600"><font size="2">CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you.</font></span></i></blockquote></div></div>
-- <br>Openid-specs-digital-credentials-protocols mailing list<br>Openid-specs-digital-credentials-protocols@lists.openid.net<br>https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols<br></div></blockquote></div><br></div></body></html>