My concern with BFF is that the common meaning is what the document calls Full BFF -- so what many readers will assume is BFF is not what the document is referring to. ᐧ
On Tue, May 4, 2021 at 8:03 AM Aaron Parecki <aa...@parecki.com> wrote: > I support adoption. I'm also fine with the BFF acronym since it's common > in the software development world already. If anything, the TMI acronym is > the least strong of the two as it's missing a letter from the full name of > the draft. > > Aaron > > > > > On Tue, May 4, 2021 at 7:40 AM Dick Hardt <dick.ha...@gmail.com> wrote: > >> I'm supportive -- but am concerned with the BFF acronym. >> ᐧ >> >> On Mon, May 3, 2021 at 3:00 PM Rifaat Shekh-Yusef < >> rifaat.s.i...@gmail.com> wrote: >> >>> All, >>> >>> This is a call for adoption for the *Token Mediating and Session >>> Information Backend for Frontend* as a WG document: >>> https://datatracker.ietf.org/doc/draft-bertocci-oauth2-tmi-bff/ >>> >>> Please, provide your feedback on the mailing list by *May 17th*. >>> >>> Regards, >>> Rifaat & Hannes >>> _______________________________________________ >>> OAuth mailing list >>> OAuth@ietf.org >>> https://www.ietf.org/mailman/listinfo/oauth >>> >> _______________________________________________ >> OAuth mailing list >> OAuth@ietf.org >> https://www.ietf.org/mailman/listinfo/oauth >> > -- > --- > Aaron Parecki > https://aaronparecki.com > >
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
