Re: [Txauth] Name criteria

[Mike Jones <[e-mail]>]

Arguing with Dick in reply (because it’s fun ;-) )…

“Facebook Connect” is the descriptive name of a successful well-known protocol with no short name.  (“OIDC” is not used in any of the OpenID Connect specs either.)  My point is not to exclude consideration of names without a short form.

And it would be a safe bet that you had to look up the bacronym for “SCIM”, because it doesn’t exactly roll off the tongue!

                                                       Cheers,
                                                       -- Mike

From: Yaron Sheffer <[e-mail]>
Sent: Tuesday, April 28, 2020 6:29 AM
To: Dick Hardt <[e-mail]>; Mike Jones <[e-mail]>
Cc: [e-mail]; Justin Richer <[e-mail]>
Subject: Re: [Txauth] Name criteria

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

Now you guys can go back to counting letters 😊

From: Txauth <[e-mail]<mailto:[e-mail]>> on behalf of Dick Hardt <[e-mail]<mailto:[e-mail]>>
Date: Tuesday, April 28, 2020 at 06:57
To: Mike Jones <[e-mail]<mailto:[e-mail]>>
Cc: "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>, Justin Richer <[e-mail]<mailto:[e-mail]>>
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 <[e-mail]<mailto:[e-mail]>> 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 <[e-mail]<mailto:[e-mail]>> On Behalf Of Justin Richer
Sent: Monday, April 27, 2020 6:37 PM
To: Dick Hardt <[e-mail]<mailto:[e-mail]>>
Cc: txauth@ietf..org<mailto:[e-mail]>
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 <[e-mail]<mailto:[e-mail]>> wrote:

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

Required:

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

  1.  Straightforward to pronounce
  2.  Easy to spell
  3.  Easy to read



--
Txauth mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/txauth

-- Txauth mailing list [e-mail]<mailto:[e-mail]> https://www.ietf.org/mailman/listinfo/txauth