[Secdispatch] Re: [saag] Re: Re: draft-yossif-psea-0 2 posted — re-scoped as an EAT token profile (diff)

--===============0439370900514857013==
Content-Type: multipart/alternative;
 boundary="----=_NextPart_26279011.236034731989"

------=_NextPart_26279011.236034731989
Content-Type: text/plain;
 charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Songbo, thank you =E2=80=94 your boundary summary is exactly right, and=C2=
=A0keeping that line explicit is the intent.=C2=A0
I'd very much welcome a=C2=A0focused pass on the verifier-side text, especi=
ally fail-closed
behavior and action-binding validation.=C2=A0
Whatever wording you can=C2=A0share would be valuable.

Best,
Mohamad Khalil-Yossif
On 11/06/2026 04:50:15, Songbo Bu <[email protected]> wrote:
Hi Mohamad, Rich, all,

I read -02 as a much more concrete document than the earlier model
draft. Framing it as an EAT profile with action-payload binding and
verifier rules makes the dispatch question easier to discuss.

My quick review reaction is that the strongest path is to keep the
document very explicit about what it does and does not prove:

- it proves that a named action payload was approved through a
user-verification-gated authenticator path;
- it gives the verifier/relying party fail-closed checks for replay,
action mismatch, and cross-context reuse;
- it does not by itself solve WYSIWYS, establish a specific human
identity, or define the surrounding OAuth / step-up policy.

That boundary seems important because it lets the work complement
OAuth step-up and RATS/EAT without trying to become either of them.

If useful, I can do a focused pass on the verifier-side text and send
concrete wording, especially around fail-closed behavior and
action-binding validation.

Best,
Songbo Bu

On Tue, 09 Jun 2026 19:01:19 +0300, Mohamad Khalil-Yossif
wrote:
> Understood, and thanks =E2=80=94 both for the candor and the signature ti=
p.
>
> I'll trim it down.
>
> Mohamad Khalil-Yossif
>
> On 09/06/2026 18:48:23, Salz, Rich wrote:
>
> I am not criticizing, I am trying to understand the community that exists=
 around this and I appreciate your honesty. It seems the answer is =E2=80=
=9Cnone yet.=E2=80=9D
>
> -

>
> If there are specific WGs or people you think should weigh in on whether =
the need is real, I'd welcome the pointer.
>
> Sorry, I have no suggestions. But while I=E2=80=99m here, I do suggest th=
at you consider stripping down your email signature; four images and a few =
text lines seems a little excessive. :)

------=_NextPart_26279011.236034731989
Content-Type: text/html;
 charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<div id=3D"__MailbirdStyleContent" style=3D"font-size: 10pt;font-family: Ca=
scadia Code;color: #1A1A1A;text-align: left" dir=3D"ltr"><div><span style=
=3D"font-size: 13.3333px">Songbo, thank you =E2=80=94 your boundary summary=
 is exactly right, and&nbsp;</span>keeping that line explicit is the intent=
.&nbsp;</div><div><span style=3D"font-size: 13.3333px">I'd very much welcom=
e a&nbsp;</span>focused pass on the verifier-side text, especially fail-clo=
sed</div><div><span style=3D"font-size: 13.3333px">behavior and action-bind=
ing validation.&nbsp;</span></div><div><span style=3D"font-size: 13.3333px"=
>Whatever wording you can&nbsp;</span>share would be valuable.</div><div><s=
pan style=3D"font-size: 13.3333px"><br></span></div><div><span style=3D"fon=
t-size: 13.3333px">Best,</span></div><div><span style=3D"font-size: 13.3333=
px">Mohamad Khalil-Yossif</span></div><div class=3D"mb_sig"></div>
                                        
                                        <blockquote class=3D"history_contai=
ner" type=3D"cite" style=3D"border-left-style: solid;border-width: 1px;marg=
in-top: 20px;margin-left: 0px;padding-left: 10px;min-width: 500px">
                        <p style=3D"color: #AAAAAA; margin-top: 10px;">On 1=
1/06/2026 04:50:15, Songbo Bu &lt;[email protected]&gt; wrote:</p><div s=
tyle=3D"font-family:Arial,Helvetica,sans-serif">Hi Mohamad, Rich, all,
<br>
<br>I read -02 as a much more concrete document than the earlier model
<br>draft. Framing it as an EAT profile with action-payload binding and
<br>verifier rules makes the dispatch question easier to discuss.
<br>
<br>My quick review reaction is that the strongest path is to keep the
<br>document very explicit about what it does and does not prove:
<br>
<br>- it proves that a named action payload was approved through a
<br>user-verification-gated authenticator path;
<br>- it gives the verifier/relying party fail-closed checks for replay,
<br>action mismatch, and cross-context reuse;
<br>- it does not by itself solve WYSIWYS, establish a specific human
<br>identity, or define the surrounding OAuth / step-up policy.
<br>
<br>That boundary seems important because it lets the work complement
<br>OAuth step-up and RATS/EAT without trying to become either of them.
<br>
<br>If useful, I can do a focused pass on the verifier-side text and send
<br>concrete wording, especially around fail-closed behavior and
<br>action-binding validation.
<br>
<br>Best,
<br>Songbo Bu
<br>
<br>On Tue, 09 Jun 2026 19:01:19 +0300, Mohamad Khalil-Yossif
<br><[email protected]> wrote:
<br>&gt; Understood, and thanks =E2=80=94 both for the candor and the signa=
ture tip.
<br>&gt;
<br>&gt; I'll trim it down.
<br>&gt;
<br>&gt; Mohamad Khalil-Yossif
<br>&gt;
<br>&gt; On 09/06/2026 18:48:23, Salz, Rich <[email protected]=
f.org> wrote:
<br>&gt;
<br>&gt; I am not criticizing, I am trying to understand the community that=
 exists around this and I appreciate your honesty. It seems the answer is =
=E2=80=9Cnone yet.=E2=80=9D
<br>&gt;
<br>&gt; -
<br>
<br>&gt;
<br>&gt; If there are specific WGs or people you think should weigh in on w=
hether the need is real, I'd welcome the pointer.
<br>&gt;
<br>&gt; Sorry, I have no suggestions. But while I=E2=80=99m here, I do sug=
gest that you consider stripping down your email signature; four images and=
 a few text lines seems a little excessive. :)
<br></[email protected]></[email protected]=
etf.org></div></blockquote></div>
------=_NextPart_26279011.236034731989--


--===============0439370900514857013==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KU2VjZGlzcGF0
Y2ggbWFpbGluZyBsaXN0IC0tIHNlY2Rpc3BhdGNoQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNl
bmQgYW4gZW1haWwgdG8gc2VjZGlzcGF0Y2gtbGVhdmVAaWV0Zi5vcmcK

--===============0439370900514857013==--