<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I wonder if there have been thoughts or considerations of the NFC
protocol for SIOPv2 to interact with RPs?</p>
<p>Especially given the adopted use cases 2.1 and 2.2?</p>
<p>
<blockquote type="cite">
<h3 id="name-resilience-against-sudden-o">
<a
href="https://openid.net/specs/openid-connect-self-issued-v2-1_0-06.html#section-2.1"
class="section-number selfRef">2.1. </a><a
href="https://openid.net/specs/openid-connect-self-issued-v2-1_0-06.html#name-resilience-against-sudden-o"
class="section-name selfRef">Resilience against Sudden or
Planned Hosted OP Unavailability</a> </h3>
<p id="section-2.1-1">A hosted third-party provided OP's
infrastructure may become unavailable or even destroyed due to
natural disasters such as hurricanes, tsunamis and fires, or
may be removed from service as a planned business decision.
End-Users using Self-Issued OPs local to their environment,
have lower chances of being simultaneously affected by such
events.</p>
<h3 id="name-authentication-at-the-edge">
<a
href="https://openid.net/specs/openid-connect-self-issued-v2-1_0-06.html#section-2.2"
class="section-number selfRef">2.2. </a><a
href="https://openid.net/specs/openid-connect-self-issued-v2-1_0-06.html#name-authentication-at-the-edge"
class="section-name selfRef">Authentication at the Edge</a>
</h3>
As internet-connected smartphones have risen in availability,
traditionally in-person interactions and services have begun to
be optimized with digital alternatives. These services often
have requirements for digital authentication and for other
identity credentials. Self-Issued OPs can provide this
authentication directly, without needing to delegate to remote,
hosted OPs. This potentially allows for increased efficiency as
well as allowing for authentication in environments which may
have reduced connectivity.</blockquote>
<br>
</p>
<p>~ Vladimir<br>
</p>
<pre class="moz-signature" cols="72">--
Vladimir Dzhuvinov</pre>
</body>
</html>