Re: [OAUTH-WG] Call for adoption - TMI BFF

Brian Campbell <bcampbell@pingidentity.com> Wed, 12 May 2021 19:01 UTC

Return-Path: <bcampbell@pingidentity.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC2863A0D96 for <oauth@ietfa.amsl.com>; Wed, 12 May 2021 12:01:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=pingidentity.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dG-8lYWxTe0e for <oauth@ietfa.amsl.com>; Wed, 12 May 2021 12:01:03 -0700 (PDT)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92D263A0D43 for <oauth@ietf.org>; Wed, 12 May 2021 12:01:03 -0700 (PDT)
Received: by mail-lj1-x233.google.com with SMTP id y9so30937469ljn.6 for <oauth@ietf.org>; Wed, 12 May 2021 12:01:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gfR0hbPAllYmT4q1Iq5d5tesSnSRZ5PMPJ+1oTtpeSU=; b=YmIhuF9BrNNuNG9jVkiQrKZKfd7cKmAME+9X7s60qVn96aaXPCCRtt0Kge3qsPr03F oT4qVoHh+HrmYhSN/4HY6SIRHV/xedGD2NHG+GctD+LmeYpbXLMo0ga1/8gv5Y3rK7HP f5eMEYYEJRuA60681KCbvvEKaeI5TkmgE1O3AhUFVAQ0Jm/ahxNQvaWMfMRD/efl1l/a 1xngB3LUygiMVVkBB3Qq/suw6VBwU+R2Kw8wIGLTUqp1w68fIfUMRpqGIJx9ZGLV/EkW c2z0BPc/LRQ35wRrP/05/svkL+2eYP+L6m40YwPldJaNGjyHXX7+lLwIlqgZNf82L0Vf furQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gfR0hbPAllYmT4q1Iq5d5tesSnSRZ5PMPJ+1oTtpeSU=; b=kI8ykr4Iz1pK+PMASwSeDVwaZWSUykliAS8p/UMxff1FoaGXOiQETLDNAJDuGtCtPN Tnp8dgKKTDNufcnFkU1noIT/0tfYU7SnTvEEEzwKO/T69hhvwvg0iT3Mqw3gHI4wEbY2 7zNJhTd1nSNso4Af3Nq4QUssoB/GV/n2qYATsz9izYY84vkxsYqbVlm9DaNYGvt6st84 PrIq3MWJtdgqZrqnBEIWH83ieP0MRgr7Eq0h2QLoOWAgwsIz05ZgEOQwQuj1E8S9AtWM e3V7S3B3zOWmH1Rdy040aJdAl8wGug7NJvwHR2emNtbedV1I8LDgNgDLGp3AYs/Cexvu yi8Q==
X-Gm-Message-State: AOAM532C2IJfeX/1nAp/XaQno+RKTrOFnBHdGmQss8JVnzdyJEC5eqfu vs3hdUGadIMN4WZ0fDW96+QTCbw6VLk907SLatxuX2iQWtoqFM6EJ0ARKSrH5B/QyA0f3u4IHRW ymjHCYaSIKbqCuw==
X-Google-Smtp-Source: ABdhPJxxEM9nvDkK0D1bkOCKzb0ItaDWCiTikKtEJHA7ftycOu5UjQfKok8Z5Iw+jCAof4LR+6qdkDQSgqMOEl1F+gs=
X-Received: by 2002:a2e:7f0f:: with SMTP id a15mr4656267ljd.387.1620846061432; Wed, 12 May 2021 12:01:01 -0700 (PDT)
MIME-Version: 1.0
References: <CADNypP9wV6=T-AU+j_hrXT7zH9c8OdKone_0Arq+yPu+aAupNQ@mail.gmail.com> <CAD9ie-uhLf_d0=GpftqoRAZ7_=wEBLBHyUjkR1bomz6xcM_dzQ@mail.gmail.com> <CAGBSGjo=fko9Tc+fbcA3P74xH9bZbg6t6x__-KR7XSfh6A5Evg@mail.gmail.com> <CAD9ie-uBK8yhXY1a8nW1Q=62guk_hjJv8WCzzSKrn3MiwWKVqQ@mail.gmail.com> <09226cd8-8880-4906-f745-98780d0d1bef@manicode.com> <CAGBSGjrfiK=efSTc6Ho7v1sfa0oa-==Jh7XTYpb_QpC=CVHv4Q@mail.gmail.com>
In-Reply-To: <CAGBSGjrfiK=efSTc6Ho7v1sfa0oa-==Jh7XTYpb_QpC=CVHv4Q@mail.gmail.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Wed, 12 May 2021 13:00:35 -0600
Message-ID: <CA+k3eCRwzt8Lfa7PExUtiT_mA3Yim7Powh=vmSOoMgoLyofkHg@mail.gmail.com>
To: Aaron Parecki <aaron@parecki.com>
Cc: Jim Manico <jim@manicode.com>, oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ba4c2d05c226a1a3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/nSgY4UCbA6Sbpl9q-Rgzwv9JjSw>
Subject: Re: [OAUTH-WG] Call for adoption - TMI BFF
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 May 2021 19:01:17 -0000

While I admit to being somewhat partial to the acronym, it's not for any
sound technical or informational reason. To be honest, before I became
enamored with my own perceived cleverness of TMI-BFF, I also thought the
use of "BFF" in the context of the draft wasn't quite appropriate.

At this point, I propose that Vittorio and I step back and rework the draft
a bit and then resume the call for adoption after we spin a new revision.
We'll eliminate the problematic use of BFF and address some of the more
straightforward feedback from the interim.



On Tue, May 4, 2021 at 3:03 PM Aaron Parecki <aaron@parecki.com> wrote:

> Okay, I have come around to this idea and agree that we shouldn't use
> "BFF" to refer to this pattern. The only reason I am continuing the
> discussion in this thread is that if we agree we should avoid the term BFF
> for this draft, I would like to see it renamed before it is adopted, to
> avoid any confusion at the start.
>
> Aaron
>
>
> On Tue, May 4, 2021 at 10:28 AM Jim Manico <jim@manicode.com> wrote:
>
>> +1 Mr. Hardt. BFF aims to avoid access tokens in UA's so TMI-BFF is a
>> badly branded name that will add confusion.
>>
>> - Jim
>> On 5/4/21 11:25 AM, Dick Hardt wrote:
>>
>> 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 <aaron@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.hardt@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.ietf@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 listOAuth@ietf.orghttps://www.ietf.org/mailman/listinfo/oauth
>>
>> --
>> Jim Manico
>> Manicode Securityhttps://www.manicode.com
>>
>> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>

-- 
_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._