Re: [Uri-review] Registration request for "at" URI scheme

bnewbold@robocracy.org Sun, 07 May 2023 22:14 UTC

Return-Path: <bnewbold@robocracy.org>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCAACC14CF0C for <uri-review@ietfa.amsl.com>; Sun, 7 May 2023 15:14:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xlnoCWelKZXa for <uri-review@ietfa.amsl.com>; Sun, 7 May 2023 15:14:41 -0700 (PDT)
Received: from mail.robocracy.org (adze.robocracy.org [IPv6:2600:3c03::f03c:91ff:feb0:af1f]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36062C14CEFE for <uri-review@ietf.org>; Sun, 7 May 2023 15:14:40 -0700 (PDT)
Received: from adze.robocracy.org (adze.robocracy.org [IPv6:2600:3c03::f03c:91ff:feb0:af1f]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: bnewbold) by mail.robocracy.org (Postfix) with ESMTPSA id DE7DF9C85B; Sun, 7 May 2023 22:14:37 +0000 (UTC)
Date: Sun, 07 May 2023 22:14:37 +0000
From: bnewbold@robocracy.org
To: Eliot Lear <lear@lear.ch>
cc: Melvin Carvalho <melvincarvalho@gmail.com>, Bryan Newbold <bryan@blueskyweb.xyz>, Paul Frazee <pfrazee@gmail.com>, uri-review@ietf.org, Devin Ivy <devin@blueskyweb.xyz>, Jay Graber <jay@blueskyweb.xyz>
In-Reply-To: <81587de4-d623-01d2-9a68-0f797a1eec6b@lear.ch>
Message-ID: <54504db-83d3-c2e3-7820-3275323d5bd@robocracy.org>
References: <f456a86-b079-2bec-f698-f2fc4fb7e76b@robocracy.org> <CAKaEYhKaB9=NVGY_eQk3vq4zGEy_N7FNy9yj02wdz0DuHS2wqw@mail.gmail.com> <CABFYohi+CD33Hn9SnPk3Fk+_W3=8pwtnHeGF1KWVQZG4bV_hnA@mail.gmail.com> <CAKaEYhK=snie3_nAz3CdJoMDh=fx6zmGwbcc9m_jESdjV2ym3w@mail.gmail.com> <81587de4-d623-01d2-9a68-0f797a1eec6b@lear.ch>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="8323329-1757420687-1683496901=:3820568"
Content-ID: <f669d228-de4-65e4-c1eb-23c462ec44c@robocracy.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/uri-review/aWs_HppPsAMN_jT5aeKYCAREnTs>
Subject: Re: [Uri-review] Registration request for "at" URI scheme
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uri-review/>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 May 2023 22:14:45 -0000

Hi Eliot,

We did do both some general search, and checked against the URI schema 
registry when starting work on the protocol, and are not aware of any 
problematic existing use or conflicts the the use of the URI scheme name.

The closest confusion we are aware of with 'at' is the Hayes AT command 
originally used with modems. We are unaware of any URI scheme specifically 
for the Hayes AT command set, and while that command set is still in 
broad use, it does not seem likely to start using one now.

"at" matches our protocol name ("AT" stands for "Authenticated Transfer"). 
There is a bit of wordplay going on with "@" (the "at symbol"), which is 
used as a prefix convention in social media to indicate a user handle. AT 
Protocol is primarily used for social media applications (at least, that 
is the focus at present).

As precedent, there are several other two-character URI schemes in the 
current registry.

URIs starting with "at://" are already being used by several 
implementations of the AT Protocol. At this point it seems like a change 
would only add to confusion.

--bryan

On Sun, 7 May 2023, Eliot Lear wrote:

> As another casual observer, can I suggest that you use a slightly more 
> descriptive scheme name?  "at" is heavily overloaded, and a name that 
> provides at least a guess what this is will serve the user better.