Re: [Txauth] WG name brainstorming - please participate!

Justin Richer <jricher@mit.edu> Mon, 04 May 2020 13:40 UTC

Return-Path: <jricher@mit.edu>
X-Original-To: txauth@ietfa.amsl.com
Delivered-To: txauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4B043A08AB for <txauth@ietfa.amsl.com>; Mon, 4 May 2020 06:40:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 HEt8AH2ZKjHT for <txauth@ietfa.amsl.com>; Mon, 4 May 2020 06:40:39 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 950963A08A6 for <txauth@ietf.org>; Mon, 4 May 2020 06:40:39 -0700 (PDT)
Received: from [192.168.1.13] (static-71-174-62-56.bstnma.fios.verizon.net [71.174.62.56]) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 044DeadZ018190 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 4 May 2020 09:40:37 -0400
From: Justin Richer <jricher@mit.edu>
Message-Id: <ED189FCF-B3EC-408E-A5CA-15F4ED73DF11@mit.edu>
Content-Type: multipart/alternative; boundary="Apple-Mail=_947623C1-06E2-4CB1-A6FF-80358EC67E13"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Mon, 04 May 2020 09:40:36 -0400
In-Reply-To: <CAD9ie-vVxPcdm6A=LVBX5yzEoQDMn0BQWbDfj45ih9PRdxuZXQ@mail.gmail.com>
Cc: txauth@ietf.org
To: Dick Hardt <dick.hardt@gmail.com>
References: <CAD9ie-skQf0UtZJ65+oEXKxhPb7Xarhp=h22jocypo52mef7_w@mail.gmail.com> <D28BD01A-8895-4EB5-9ECA-FDAF87FA89BE@mit.edu> <CAD9ie-vVxPcdm6A=LVBX5yzEoQDMn0BQWbDfj45ih9PRdxuZXQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/yRLss0h_cZgL40sIw29C24EdOsE>
Subject: Re: [Txauth] WG name brainstorming - please participate!
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <txauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/txauth>, <mailto:txauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/txauth/>
List-Post: <mailto:txauth@ietf.org>
List-Help: <mailto:txauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/txauth>, <mailto:txauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 May 2020 13:40:42 -0000


> On May 2, 2020, at 1:33 PM, Dick Hardt <dick.hardt@gmail.com> wrote:
> 
> Hi Justin
> 
> I'm confused why you would suggest that TxAuth stands for transactional authn as we just did have a discussion that made it clear that there is more support against "transactional" then there is for it. It seems that you are not respecting decisions that have been made in the group. I hope this is not indicative of how you will interact with the group going forward as it is counter productive.
> 
> What would you like your proposal of TxAuth to represent? (I don't think it can not expand into something. OAuth is unique as it was a strong brand prior to the work in the IETF, and Tx is known to stand for either "transmission", or "transaction")
> 

As I said in my email below, and in many emails prior, I’m also happy with the “Tx” expanding to something else. I’m also happy with it expanding into nothing, which I don’t think we should dismiss as an option.

> Suggestion: I think that the extensibility of the protocol is a key aspect. If there is a word that the T (besides transactional) that is descriptive of the work, then TXAuth could be a great name. T_____ eXtensible Authorization or something like that.

Thank you for agreeing with what I said in my email below.

> 
> wrt. your question on providing feedback on other proposals, we are in brainstorming mode of a name and expansion. Per my email, "We won't be judging or ranking names at this time"

Which is in interesting given the first half of your response was providing feedback on my proposal.

> 
> As to your comment on disqualifying XAuth that it "fails the first required parameter below pretty badly", I would not consider the xauth program to control X server to be a "major software project", but I was never a big X server user, so happy to be told otherwise by anyone on the group that may be regularly using the xauth program and would find it confusing. 
> 

I’ve been a unix/linux user for over two decades, and xauth is an established program in that space. Especially considering it’s a security utility for a network protocol (x11), I don’t think we should be stepping on it with another security effort for another network protocol. It’s not only the same name but it’s a similar-ish function.

I have many other comments about xauth as a name, and the rationale given for it, but as requested I will provide those when we are discussing things if this is still a relevant option.

In the mean time I’ll continue to submit ideas to the brainstorm process,

Thanks,
 — Justin

> /Dick
> 
> On Sat, May 2, 2020 at 7:25 AM Justin Richer <jricher@mit.edu <mailto:jricher@mit.edu>> wrote:
> Dick,
> 
> Thanks for kicking this off. I’m going to submit that we keep the current name of the mailing list:
> 
> TxAuth
> 
>  - Either “Transactional Authn” or “The neXt Authn” or any number of other things. Or just “TxAuth” without an expansion, like the “O” in OAuth today doesn’t officially expand into anything (it’s officially the Web Authorization Protocol Framework, not “Open Authorization” as it might have been at one point). Considering the only push against TxAuth that I’ve heard is that some people don’t like “transactional” in the name, I think that’s easy enough to work around.
> 
> Not only does it have <1M hits on google, most of them point to this working group or writings about this working group. It’s a brand we already own and control, and we are the ones who can decide what it means.
> 
> 
> 
> 
> Are we providing feedback inline for other proposals while we’re at it? Because “XAuth” fails the first required parameter below pretty badly:
> 
> https://www.x.org/archive/X11R6.8.1/doc/xauth.1.html <https://www.x.org/archive/X11R6.8.1/doc/xauth.1.html>
> 
> 
>  — Justin
> 
>> On May 1, 2020, at 5:08 PM, Dick Hardt <dick.hardt@gmail.com <mailto:dick.hardt@gmail.com>> wrote:
>> 
>> We now have our criteria for names, and we can now start the next step in our process, brainstorming names!
>> 
>> Here is the criteria again:
>> 
>> Required:
>> No confusion with another protocol, major software project, or IETF/IRTF WG name
>> no existing registered trademarks in related classes
>> Less than 1M results in Google
>> Descriptive of protocol (this criteria is subjective)
>> Not an offensive meaning to a member of the mail list
>> Desirable:
>> Straightforward to pronounce
>> Easy to spell
>> Easy to read
>> Shortish
>> We won't be judging or ranking names at this time -- we are brainstorming names that are descriptive of the protocol.
>> We are hoping we can get the WG approved in the telechat May 21, 
>> so ideally we would have rough consensus on the name by May 18.
>> 
>> Let's brainstorm for a week, and then we can stack rank them on our objective criteria, and then vote on the top candidates.
>> 
>> I'll start by submitting my favorite:
>> 
>> XAuth - Extensible delegated Authorization and Authentication protocol, or just view the X as a placeholder and XAuth is OAuth ++
>> 
>> -- 
>> Txauth mailing list
>> Txauth@ietf.org <mailto:Txauth@ietf.org>
>> https://www.ietf.org/mailman/listinfo/txauth <https://www.ietf.org/mailman/listinfo/txauth>
>