[Openid-specs-fapi] Ticket #60 (was Re: Starting the WGLC for FAPI Part 2)
nat at sakimura.org
Sat May 6 18:52:03 UTC 2017
I have just replied to the ticket.
In essence, TB is for the future. Google etc. are betting on it so I
expect wider support in a few years time that would make the life of
developers easier. For now, we should use MTLS. (I have proposed another
method in IETF, which is truly end-to-end, and Tony supported it in the
last meeting but I need more support. Of course - that one is not
channel-bound and thus it has its own downside. )
Maybe John B. can chime in here as the chair of TB WG while he is in
transit to Munich.
Research Fellow, Nomura Research Institute
Chairman of the Board, OpenID Foundation
On 2017-05-07 01:06, Tom Jones wrote:
> i believe issue #60 needs to be addressed first. ..tomj
> On Fri, May 5, 2017 at 10:50 PM, Nat Sakimura via Openid-specs-fapi
> <openid-specs-fapi at lists.openid.net> wrote:
>> I am happy to inform you that we are starting the one-week WG last
>> call for FAPI Part 2.
>> The URL is
>> The normative content has been stable for more than a month except
>> the introduction of new clause 7, Request object registration
>> endpoint. Please review at your earliest convenience and file issues
>> if there are.
>> If there is no sustainable objection, I will take it as a consensus
>> and submit it to the OIDF secretary to start the all member ballot.
>> Nat Sakimura
>> Research Fellow, Nomura Research Institute
>> Chairman of the Board, OpenID Foundation
>> Openid-specs-fapi mailing list
>> Openid-specs-fapi at lists.openid.net
>> http://lists.openid.net/mailman/listinfo/openid-specs-fapi 
>  http://lists.openid.net/mailman/listinfo/openid-specs-fapi
More information about the Openid-specs-fapi