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

Ted Hardie <ted.ietf@gmail.com> Mon, 08 May 2023 09:54 UTC

Return-Path: <ted.ietf@gmail.com>
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 60452C1519A0 for <uri-review@ietfa.amsl.com>; Mon, 8 May 2023 02:54:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level:
X-Spam-Status: No, score=-2.093 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 JkxcC-AsTDbP for <uri-review@ietfa.amsl.com>; Mon, 8 May 2023 02:54:22 -0700 (PDT)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 A246FC151990 for <uri-review@ietf.org>; Mon, 8 May 2023 02:54:22 -0700 (PDT)
Received: by mail-ed1-x529.google.com with SMTP id 4fb4d7f45d1cf-50bcb00a4c2so6809815a12.1 for <uri-review@ietf.org>; Mon, 08 May 2023 02:54:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683539661; x=1686131661; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=54plqXeKHnZiWhG6T1n3IQ+W9jjPY1VPmvjjDsbILF4=; b=aJt/F7ZoKiGVd1pGnM4Zl5piiQ7xfsharMTz5qoGUTQNmilenjgtLa5La0fs0YiFJF p312SX9D6G478df51WeyLC5cTSOrdPEoKm5Ka0qIRKggEXyex3aIXExB/ZOtnxOa+FkJ VZf7LKD98C0gO/fVTfl3I8JptujtAdCrcasH9TbYoYVBVfWxPJoRwox9cnf6Fkg4pkXF V2lWzCIMlkLENJP6SywpX8axOaXbvb1GrPzAZyK9cdBe+U1oD0fIeNvN86GMBZArDTvC MZxJpQmYXMebLeZOKoLEy1dNtxfTVrdjYEj0cdoQe6YJ1GmyxYtLnAHyk3ft9WcHew9I 9bCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683539661; x=1686131661; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=54plqXeKHnZiWhG6T1n3IQ+W9jjPY1VPmvjjDsbILF4=; b=DZ+q2HATZ1VuBXuxgk/ehM0Q558FqK4FaujOUNPhpn/gm08F2FAmwNt30zsGYKKvF/ pHiQcSfDICnord33h4vtxB3SUuKRTlSDjkScly+yzElNOUSrs5e0mXn9cppjCj5HTgiF 5ksOrM6umiWEyqh5CVt1sU2/SzsEeFwBub4TCxK7D6+Khfo4ytJBkIQWqPrDZnM/2eJB vwNaP+6B/96d606WaDPrTGI4OIkeZCAbULerTuc3jytG0eUMdpsl2zuF1STUXfQN1KVy 6RQIwbeHu8pe2wIQBR7BWymNLsx6DzIdr2sfaTg5rVE1aQ3H4YZIO2VVxkwQTdA/CC3g tUQA==
X-Gm-Message-State: AC+VfDww+YEIMwsolj79f8uftBNdLybWbrAxFlGv83xQK6Iu0YW4ArMm B1LEP037jEmMmImVFxx3UxpO2nuWWdQIH9/hWgU=
X-Google-Smtp-Source: ACHHUZ4jFYc0/OGoL7nxfB9865+G4v7sOk9JyxG+XfDIL9m8hgwoFYyZVbhIV1Ekqw/W1+FIp/8tqlUy4rQKM86fPjA=
X-Received: by 2002:a17:907:72c3:b0:94a:7b2c:205e with SMTP id du3-20020a17090772c300b0094a7b2c205emr7850085ejc.72.1683539660839; Mon, 08 May 2023 02:54:20 -0700 (PDT)
MIME-Version: 1.0
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> <54504db-83d3-c2e3-7820-3275323d5bd@robocracy.org> <ee6f60d9-5f19-3344-bd26-e87f881aa5a6@lear.ch>
In-Reply-To: <ee6f60d9-5f19-3344-bd26-e87f881aa5a6@lear.ch>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Mon, 08 May 2023 10:53:54 +0100
Message-ID: <CA+9kkMC6Azu+TxYOxYjycXwR8w0k5RBXYCK+oSj==dkA+Qjqbg@mail.gmail.com>
To: Eliot Lear <lear@lear.ch>
Cc: bnewbold@robocracy.org, Paul Frazee <pfrazee@gmail.com>, Devin Ivy <devin@blueskyweb.xyz>, uri-review@ietf.org, Jay Graber <jay@blueskyweb.xyz>, Bryan Newbold <bryan@blueskyweb.xyz>
Content-Type: multipart/alternative; boundary="000000000000732b6e05fb2b9fc3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/uri-review/MjORJyBxVVg3UsqG2AzE8UMfYqQ>
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: Mon, 08 May 2023 09:54:23 -0000

I agree with Eliot here.  The registry is first-come-first-served because
we want to avoid collisions; having a single namespace for this is pretty
much a requirement for the overall system to function properly.   But, as
you can tell, there is a period after a string is minted internally and
starts turning up in code before it shows up at the registry (or even on
this list).  Very short strings and strings with mnemonic significance
(like the wordplay that led you to "at") are at increased risk for
collision.

Your repo refers to this consistently as atproto, and atproto or even atp
is less like likely to create a later collision; my advice (and it is just
advice) is to consider using one of those.

regards,

Ted Hardie


On Mon, May 8, 2023 at 9:18 AM Eliot Lear <lear@lear.ch> wrote:

> Hi Bryan,
>
> As Alex mentioned, I wasn't referring to URI schemes, but rather that the
> word "at" is not descript, reused in many different contexts, from Austria
> to a preposition, to a scheduling command in UNIX to various other acronym
> expansions.  My understanding is that the registry is FCFS, and so this is
> *advice*.  Whatever you choose you'll be stuck with.  If you even added
> an extra character or two that could make more clear what this is, you may
> find it helpful later on.
>
> Eliot
> On 08.05.23 00:14, bnewbold@robocracy.org wrote:
>
>
> 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.
>
> _______________________________________________
> Uri-review mailing list
> Uri-review@ietf.org
> https://www.ietf.org/mailman/listinfo/uri-review
>