IETF Logo Mail Archive

Re: [dispatch] Finding a home for Multibase and Multihash

Tim Bray <tbray@textuality.com> Fri, 12 August 2022 15:52 UTC

Return-Path: <tbray@textuality.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 876A0C15A747 for <dispatch@ietfa.amsl.com>; Fri, 12 Aug 2022 08:52:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=textuality-com.20210112.gappssmtp.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 FY3gNMB4hECq for <dispatch@ietfa.amsl.com>; Fri, 12 Aug 2022 08:52:30 -0700 (PDT)
Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (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 859B2C157B3E for <dispatch@ietf.org>; Fri, 12 Aug 2022 08:52:23 -0700 (PDT)
Received: by mail-ed1-x530.google.com with SMTP id a89so1843366edf.5 for <dispatch@ietf.org>; Fri, 12 Aug 2022 08:52:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=QJxnuZ18TBgY2SxzYJcoDFPSBcybXpOaA6tYVVk5HDs=; b=UKVSgxFYPZz7O61NEiRxucHt8JPySs++CltDsZG1BNodJBojcmKTfBpX0VJ2T4P1eq 2TWzx1mq0Vwue6tlSntsb5TpOpyAyMOqs7vr1zuKijAC0ML1TiHt7xeZyGNO+HJp7LHP 2M/UXFwhyCvqjovN6sU9RSuzdwkBuUJhPrl4k4ViHRqaPZBCrLouzcuF9RvwFtLnXHwm CYw9/wUIbFGKDL5Tl0765p/9MrJARDdz6W1FuhPOhC4Wv3vT9s9NNuXZw/0F3mJvVTYy M5xLDNs+jGUjTOnFB2WfLEz5gmf4u7Xo+OEz3kNNAj74lEyf8Syf0EnryWx47EoGeLKY 6aTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=QJxnuZ18TBgY2SxzYJcoDFPSBcybXpOaA6tYVVk5HDs=; b=14QKnJDiDCJVlZsJvVpfYgBD7crRbJQ4x+0+eTIXShRJ8VqeMz0B1f27JO7iZfGWpt JzhtEaIY/XiimWzJCtZ2ctZJ27THbo7Z/FdWGAc94aQVJPTx/7TqPInaA2ewjjNEtFBf MNzaMGjfSVfo+3rCmr0xZfmlIiW0Dwr8duaKC4XCTQgdP2PGfHbqCXRPSWZ7O/3MBHIQ fnKijv3yWP/DxYFRAfex/8frZn2MY8qekZxGBWVvJpY1W+1ryn9DId2KWBZjEsSgHIKI 1JWn17t7RBWHEdTnKImp9XK6J9axLc344wwoCIBQNU/Nu4xNhN+6rNXzdAx7TJzQ2Hrn 9E9Q==
X-Gm-Message-State: ACgBeo3IxPfrrU/scY71i8YOWULcL+81WVBuAyT5CMi+S068a+uwSQf+ O5GOTII0cLQGpOn7z80RzGn7YMiT9u4fegV4QjZfRZepUAs=
X-Google-Smtp-Source: AA6agR5iFhNAtEy6i4ZRDrZHTAbbYYgWDzk/BWz3AeB8y7SIVGgCZBhJUBJrNd840TWNRKtPpNC7Ne8hupFbxTXwQ6s=
X-Received: by 2002:a05:6402:28c4:b0:43a:cdde:e047 with SMTP id ef4-20020a05640228c400b0043acddee047mr4226347edb.368.1660319541418; Fri, 12 Aug 2022 08:52:21 -0700 (PDT)
MIME-Version: 1.0
References: <CAMBN2CT8=V5diio=UwJO-rFiGPO1v3n7gp6_e4s7kENSBMLUmg@mail.gmail.com> <CAHbrMsBTQSyr8vdbS36YML7KLzByO=NjBiPUjbnhnea7eYB6rQ@mail.gmail.com> <CAMBN2CQ1YzG0ow14oH4tEjohS8TiM5469hNX3i7QoUd7ruigjQ@mail.gmail.com>
In-Reply-To: <CAMBN2CQ1YzG0ow14oH4tEjohS8TiM5469hNX3i7QoUd7ruigjQ@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
Date: Fri, 12 Aug 2022 08:52:10 -0700
Message-ID: <CAHBU6isnk2gXYUF32s8YcsRQP9ZJ7=X91aH0CVApkUT3D7sn9g@mail.gmail.com>
To: Manu Sporny <msporny@digitalbazaar.com>
Cc: Ben Schwartz <bemasc@google.com>, Dispatch WG <dispatch@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007aef7105e60d442b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/wkPWfpeLla3Qdktw-wnWdM4LsPU>
Subject: Re: [dispatch] Finding a home for Multibase and Multihash
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2022 15:52:32 -0000

On Fri, Aug 12, 2022 at 5:46 AM Manu Sporny <msporny@digitalbazaar.com>
wrote:

>
> We could just document existing practice for now if that is an easier
> path. I'll note that there are at least two W3C WGs that would like to
> normatively reference these specifications, and I'm uncertain if the
> "document existing practice" path allows for that to happen. What are
> the benefits of just documenting an existing practice for now?
>

All RFCs, including informational RFCs, are guaranteed stable and equally
cite-able, so I don't think that should be a problem for the W3C.

Even creating an informational RFC is a bit of work, someone has to operate
the draft-generation tools and there is a certain amount of process.  But
not, I think, unreasonable.


>

v2.23.0 | Report a Bug | By Email