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

bnewbold@robocracy.org Thu, 25 May 2023 01:36 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 2A58DC15109D for <uri-review@ietfa.amsl.com>; Wed, 24 May 2023 18:36:36 -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 fMDcCIE2kqHR for <uri-review@ietfa.amsl.com>; Wed, 24 May 2023 18:36:34 -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)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAFAAC151090 for <uri-review@ietf.org>; Wed, 24 May 2023 18:36:33 -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 180959C89A; Thu, 25 May 2023 01:36:33 +0000 (UTC)
Date: Thu, 25 May 2023 01:36:32 +0000
From: bnewbold@robocracy.org
To: Melvin Carvalho <melvincarvalho@gmail.com>
cc: Paul Frazee <pfrazee@gmail.com>, Devin Ivy <devin@blueskyweb.xyz>, uri-review@ietf.org, Bryan Newbold <bryan@blueskyweb.xyz>, Jay Graber <jay@blueskyweb.xyz>
In-Reply-To: <CAKaEYhKhiKNAVqxj-2sebwvdT=w7F+Qy-eFhLcCewqbTMgzo1g@mail.gmail.com>
Message-ID: <a351df8d-a047-190-835b-a1a3241c42d9@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> <54504db-83d3-c2e3-7820-3275323d5bd@robocracy.org> <ee6f60d9-5f19-3344-bd26-e87f881aa5a6@lear.ch> <e53bf99a-012b-40b7-742b-f9f5c56e876c@ninebynine.org> <CAD4FMei=03TAnaC=d6qtnP1Kt6eAJhxZUWXvSnpyKLscKj3F6g@mail.gmail.com> <CAKaEYhKhiKNAVqxj-2sebwvdT=w7F+Qy-eFhLcCewqbTMgzo1g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="8323329-722932105-1684978593=:954016"
Archived-At: <https://mailarchive.ietf.org/arch/msg/uri-review/toVi2mcx7yPe5RH1c7kAZDo4tnI>
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: Thu, 25 May 2023 01:36:36 -0000

Somewhat off-topic, but we are indeed planning to use an HTTP(S) 
.well-known path as a mechanism for resolving “handle” to DID.

This doesn’t help with the AT URI use case of referencing specific records 
within a repository.

--bryan

On Wed, 10 May 2023, Melvin Carvalho wrote:

> I've noticed similarities between Webfinger, which aimed to return JSON
> from a DNS-like identifier with an "@" symbol, and your current situation.
> Webfinger eventually established the acct: URI scheme. However, in 2012,
> Mark Nottingham suggested an alternative lookup method, such as
> ".well-known/webfinger?user=bob@host".
>
> You might consider registering an "atprotocol" under .well-known and use
> the following format: ".well-known/atprotocol?user=<atproto_identifier>".
> If the dereferencing is handled by the BGS rather than individual hosts,
> perhaps a simple lookup would suffice, eliminating the need for a new URI
> scheme.