Re: [Txauth] Name criteria

Yaron Sheffer <yaronf.ietf@gmail.com> Tue, 28 April 2020 13:31 UTC

Return-Path: <yaronf.ietf@gmail.com>
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 C9FE53A151D for <txauth@ietfa.amsl.com>; Tue, 28 Apr 2020 06:31:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.128
X-Spam-Level:
X-Spam-Status: No, score=-0.128 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MALFORMED_FREEMAIL=1.968, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 VfUhA5XodSKr for <txauth@ietfa.amsl.com>; Tue, 28 Apr 2020 06:31:15 -0700 (PDT)
Received: from mail-wm1-x32f.google.com (mail-wm1-x32f.google.com [IPv6:2a00:1450:4864:20::32f]) (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 A70293A1751 for <txauth@ietf.org>; Tue, 28 Apr 2020 06:29:30 -0700 (PDT)
Received: by mail-wm1-x32f.google.com with SMTP id u16so2848282wmc.5 for <txauth@ietf.org>; Tue, 28 Apr 2020 06:29:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version; bh=hAuVhVPUJX8r2y+AW5j9fNuW7riWKH2x1Rfl1FN7Gk4=; b=WE928wfYveIVQ0IO6asFAU1hDAi+LmPHKVZWqVmBR0moGFythkaQKB3sKoLSiQ5aGM 8ijZU5XR3i0CVkfady1YbYH49s7IBZpCVVj6WV+u87umpreDXtO9X8Eu6q+TmSe2jOW1 E4Mn6a8FyfkK+JCt0XjBSHr6rRDm+ojAQkZKdi6gXhZmxdmL6cKEoE8rWe3JLCf+j2pR Mo60sIrBU3vMDTMXgVbDdHqOfNXzoRYvBmhPpavLFI/Q6reLqVKWr0wmy1znnQUZpq5F iiW3RPnnJK302+skNx9PMkZAiE0feeedcRD8VANz8kOkwIcQ69+aWX+jYpWJpqLrINLu HGzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version; bh=hAuVhVPUJX8r2y+AW5j9fNuW7riWKH2x1Rfl1FN7Gk4=; b=idp3VL7yQ/+Fc4xVAvR7nqp4eUiSH11HuyOns5OuAMnkz0LFELr3mUYIhyY7hSmwC4 iT2V/OsFyJBW3VXZ/gsM8loJeBshCSS+xeYA4/ZxRDtf8kDZy6qzUvofNIe4SlwXyqsW Mj5RnVloADONZPBtUW07vCcMSacpEWzakoM5+cU8PtqY/9cGkQIkFMfLQaFK78XND14s ORxurhbgSDiIj669ubJO9uzL9WrHvCbtTNDoOI70xBlNr5FrxM0acKrhqnVSTaXDBL5b 73xHZmTkz/LV6ciIRGauvXhXOufqaqVkkLUIvWbPKQE8Tq1tca1K0eRbY6T+mekP82hB 0sHQ==
X-Gm-Message-State: AGi0PuYAfHTHyeJah2hPEAAKbg+7RI4oQMkTYi2CZ4HfkzJJtJwTl62q 7MFbrMnzybslzfLgfbG0KSU=
X-Google-Smtp-Source: APiQypI4jMHtBzvPEn3toCejBJ43qMIlt3rHcAdzOwTPZmmRXULh9xgZmUn1r9KJbJPUASpPnq50XQ==
X-Received: by 2002:a1c:99d3:: with SMTP id b202mr4840833wme.126.1588080569069; Tue, 28 Apr 2020 06:29:29 -0700 (PDT)
Received: from [10.0.0.139] (bzq-79-179-96-118.red.bezeqint.net. [79.179.96.118]) by smtp.gmail.com with ESMTPSA id e13sm16060402wrp.15.2020.04.28.06.29.27 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Apr 2020 06:29:28 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/16.36.20041300
Date: Tue, 28 Apr 2020 16:29:27 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
To: Dick Hardt <dick.hardt@gmail.com>, Mike Jones <Michael.Jones@microsoft.com>
CC: "txauth@ietf.org" <txauth@ietf.org>, Justin Richer <jricher@mit.edu>
Message-ID: <CDB1365F-D192-4B49-B379-65ECF32F9AA9@gmail.com>
Thread-Topic: [Txauth] Name criteria
References: <CH2PR00MB06781CD67118A28C36F78B27F5AC0@CH2PR00MB0678.namprd00.prod.outlook.com> <CAD9ie-v1O1781w5=V-d9oBk4_RtbeVWy=VnrRbgvMN-Jbs5Fkw@mail.gmail.com>
In-Reply-To: <CAD9ie-v1O1781w5=V-d9oBk4_RtbeVWy=VnrRbgvMN-Jbs5Fkw@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3670936168_484667561"
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/-sve8QKs50nOMmi6VtMsf9Dmxxg>
Subject: Re: [Txauth] Name criteria
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: Tue, 28 Apr 2020 13:31:17 -0000

Please add to point #1: No confusion … or an IETF/IRTF WG.

 

Now you guys can go back to counting letters 😊

 

From: Txauth <txauth-bounces@ietf.org> on behalf of Dick Hardt <dick.hardt@gmail.com>
Date: Tuesday, April 28, 2020 at 06:57
To: Mike Jones <Michael.Jones@microsoft.com>
Cc: "txauth@ietf.org" <txauth@ietf.org>, Justin Richer <jricher@mit.edu>
Subject: Re: [Txauth] Name criteria

 

I pick 6 chars since all the protocols I could think of were <= 6 chars in their short form, but I'm fine just stack ranking them.

 

Would we agree that all other things being equal, shorter is better?

 

The related dimension would be number of syllables. A smaller number of syllables makes it easier to say.

 

... and to argue with Mike ... because it is fun ... :)

 

The short form for OpenID Connect is OIDC ... and the previous version is just OpenID ... and while rarely used, SCIM is System for Cross-domain Identity Management (which as we all know was made up to match the acronym which originally was Simple Cloud Identity Management)

 

TCP/IP is the common term used for the wire transport. (6 chars)

 

 

 

 

 

On Mon, Apr 27, 2020 at 6:57 PM Mike Jones <Michael.Jones@microsoft.com> wrote:

I agree with Justin that the “short” criteria is overly restrictive.  Remember too, that many protocols have a short and a long name, but some don’t.  Some common ones with both long and short names are:

              Internet Protocol (IP)

              Transmission Control Protocol (TCP)

An example without a short name is:

              OpenID Connect

An example that effectively only has a short name is:

              SCIM

 

All of these kinds of reasonable names should be eligible for consideration, not all of which are short.

 

                                                       -- Mike

 

From: Txauth <txauth-bounces@ietf.org> On Behalf Of Justin Richer
Sent: Monday, April 27, 2020 6:37 PM
To: Dick Hardt <dick.hardt@gmail.com>
Cc: txauth@ietf..org
Subject: Re: [Txauth] Name criteria

 

I think the 6-character length requirement is more under “desirable” than “required”. Shorter names are often better, but that doesn’t make a longer name off limits for consideration. 

 

 — Justin

 

On Apr 27, 2020, at 7:19 PM, Dick Hardt <dick.hardt@gmail.com> wrote:

 

Riffing on the work done to name Perl6, here are the name criteria I propose:

 

Required:

No confusion with another protocol or major software project
no existing registered trademarks in related classes
Less than 1M results in Google
Short (<=6 chars)
Descriptive of protocol (this criteria is subjective)
Desirable:

Straightforward to pronounce
Easy to spell 
Easy to read
 

 

 

-- 
Txauth mailing list
Txauth@ietf.org
https://www.ietf.org/mailman/listinfo/txauth

 

-- Txauth mailing list Txauth@ietf.org https://www.ietf.org/mailman/listinfo/txauth