[Uri-review] Re: Provisional URI scheme registration request: "nostr"

alex@alexgleason.me Thu, 23 July 2026 19:01 UTC

Return-Path: <alex@alexgleason.me>
X-Original-To: uri-review@mail2.ietf.org
Delivered-To: uri-review@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id D09CD11DA6CCC for <uri-review@mail2.ietf.org>; Thu, 23 Jul 2026 12:01:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784833317; bh=DN5Yx69WVYCDZpuZ5j2lmOz0czevZYpTOOglvUg7Y7M=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=CGV9fBnVoiRqGybN+gyxe+D0ZLYdJzT0avOe+hkR0VQqNDT7/gaU7ppaR5SV2UxCA /lCbX1jHTOCYQ5jrddEjzIopMM6xe6YaogtejFM/yf3NPnoSpzwfpRm34+3JHaWi5p 0j9qgxfB2DnoJzMYzKwBDzNB0+bx377ZShfbpCKs=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.306
X-Spam-Level:
X-Spam-Status: No, score=-1.306 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, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=alexgleason.me
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sQZ-hsPX0kv5 for <uri-review@mail2.ietf.org>; Thu, 23 Jul 2026 12:01:57 -0700 (PDT)
Received: from box.alexgleason.me (unknown [138.197.233.88]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 8DBE811DA69EA for <uri-review@ietf.org>; Thu, 23 Jul 2026 12:01:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alexgleason.me; s=mail; t=1784833263; bh=DN5Yx69WVYCDZpuZ5j2lmOz0czevZYpTOOglvUg7Y7M=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=RfxSF0hObDEyJTke4j5D8gz/C4W5pUfghE7LtPXRgrvCVHw3M5U5tA2Z6F+S99Btd y/nJgjw5RV5tdyow4SfTHqlhqUvgS4+M//lXj3D5yziYnxkcGKmtnYph6kE6o+WIuL /2neqdvJq/S5G0Z2mA3leuoUbPMfJP1EMlPeNC5AD4yTeBe5Ms4664wUF9OFrm/laf 2dfUrXBnj9kwXCEntnMQPXnjf+HukFPpaaeILAg6Cnq/dEyOIDWKseo6492gWZyp1/ cQMR+s+1ll2ZsgHsHnX9EMVnfdEXHkpxEFZaEL9o6TAwgYwrbs09dTNRZxJeizkZoB XGxri91qXm1cQ==
Received: from authenticated-user (box.alexgleason.me [138.197.233.88]) (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 box.alexgleason.me (Postfix) with ESMTPSA id B0E43417EE; Thu, 23 Jul 2026 19:01:03 +0000 (UTC)
MIME-Version: 1.0
From: alex@alexgleason.me
To: Melvin Carvalho <melvincarvalho@gmail.com>
In-Reply-To: <CAKaEYhJKY8-E3uj4YwcfLt18L3iphwijz5xck7OL5RHUPLmynw@mail.gmail.com>
References: <a6f233fa20651a0e7f883b159cd7d9a2@alexgleason.me> <CAKaEYhJKY8-E3uj4YwcfLt18L3iphwijz5xck7OL5RHUPLmynw@mail.gmail.com>
Message-ID: <036237df475f10ac40b1a6d30e877721@alexgleason.me>
X-Sender: alex@alexgleason.me
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
X-MailFrom: alex@alexgleason.me
X-Mailman-Rule-Hits: nonmember-moderation
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-uri-review.ietf.org-0
Message-ID-Hash: WALISCZHBU2WPOJ6G2ITVR2VA5ZNFVUE
X-Message-ID-Hash: WALISCZHBU2WPOJ6G2ITVR2VA5ZNFVUE
X-Mailman-Approved-At: Sat, 25 Jul 2026 06:12:07 -0700
CC: iana@iana.org, uri-review@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Uri-review] Re: Provisional URI scheme registration request: "nostr"
List-Id: Proposed URI Schemes <uri-review.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/uri-review/TQNsbtFYT1Nb1R3zmS6uL6oAHIw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uri-review>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Owner: <mailto:uri-review-owner@ietf.org>
List-Post: <mailto:uri-review@ietf.org>
List-Subscribe: <mailto:uri-review-join@ietf.org>
List-Unsubscribe: <mailto:uri-review-leave@ietf.org>
Date: Thu, 23 Jul 2026 19:01:58 -0000
X-Original-Date: Thu, 23 Jul 2026 19:01:03 +0000

Hey Melvin!

Good to hear from you, and sorry I didn't give you a heads up before
submitting this. Should have.

Quick answers: the bech32 form is intentional. NIP-19 recommends hex
for storage and the wire protocol, but URIs are the display and
sharing case bech32 was made for (checksum, self-describing prefix).
Clients compare by decoding to the underlying key or id, not by
comparing strings. You are right that NIP-21 should say that
explicitly and I'll propose it upstream.

On did:nostr, I see them as complementary layers rather than competing,
but I'd like to get the mapping right. Want to work out the text 
together
in the did:nostr repo or the NIPs repo, whichever fits better?

Best,
Alex