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

Benjamin Goering <ben@bengo.co> Sat, 20 August 2022 17:42 UTC

Return-Path: <ben@bengo.co>
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 E28E6C14CE45 for <dispatch@ietfa.amsl.com>; Sat, 20 Aug 2022 10:42:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.904
X-Spam-Level:
X-Spam-Status: No, score=-6.904 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_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=bengo-co.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 c2qj9CGvliF0 for <dispatch@ietfa.amsl.com>; Sat, 20 Aug 2022 10:42:41 -0700 (PDT)
Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) (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 6B64AC14CE34 for <dispatch@ietf.org>; Sat, 20 Aug 2022 10:42:41 -0700 (PDT)
Received: by mail-pj1-x1030.google.com with SMTP id w7so310033pjq.5 for <dispatch@ietf.org>; Sat, 20 Aug 2022 10:42:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bengo-co.20210112.gappssmtp.com; s=20210112; h=to:date:message-id:subject:mime-version:from:from:to:cc; bh=2IrfmE/lWFeWV3mOyMF6NODF0U/UnSFn5u0yYy2rPE8=; b=LsrK3zL9DHMhdxJrDKjJurGwnJLYZRB3WobhojzictaTsH5Pc9Rf44FpRM14bnnhcO 5Tmluyk2frFEmoM8sYbh0zo7tK9sLHulJ0NbzKbdMKv49bgPeXUfMcy1G4CVIPxhL9A9 jkiYsjiL01HbQfAskiE2Peg0AlmnPoS8fmsnpcTdFTq+o1Y85Kn6o4a+yTFxrp3HzSPb JudmNSzJDCKzkM3Tesz0pvcXaTA1ppbbEHprQIUo7rYAyiu+JsSZ/gPXoej3nTVK3IlQ Ouc/2e5oLWzCFUgL1mhSPRPmDPvuyMdEfsu+lxJHCBMTuqygDD6EWrIygb991IbSThhn yMYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:date:message-id:subject:mime-version:from:x-gm-message-state :from:to:cc; bh=2IrfmE/lWFeWV3mOyMF6NODF0U/UnSFn5u0yYy2rPE8=; b=J4AqcPTdSWF9LIRqun6VsQqQx+4LMZDMZJZ38lMCZJcHymSh07LifGklplNaLAzz+G jStL7xw3+AXiUq9YgrH0nHGvAC+eKv4Rwog2GzpEBiX/UCU+SnmuF2if3yUBVyKDUK6R yvJHx1WNdsTxvTQih5DtAKO8GGQPNt3OiFtsV7XwCJHaczUKhdCXXzDOSLfQ984U8+Cv VG/kw3t64O5ExNurhTVb0CqO0mmDJAzKlZDn7mgtVdpO0DeriifnTgQ6hhZJJ3dFCIpv lERjjGo8bBqYv8DOchE327wPcGo8odQQaTUGAVSOcKHjL/oxyrOni+u3lTPwQSzxRYRh WCDg==
X-Gm-Message-State: ACgBeo0+dMpMCoNnqAei6s4D2Di1V6h4cNOzqXsJrBE31t5hGtYQJSB0 QL18DJ0tY8BQN32d0aTgY9ALaflxY6Wz7w==
X-Google-Smtp-Source: AA6agR4WKP3++pYeumnOA6ZikGKbipxl+Lhhsf53eZNs6x5XMiELZSTU9Qul739wyXKe2ULtXt04jA==
X-Received: by 2002:a17:90b:1e08:b0:1f5:1f0d:3736 with SMTP id pg8-20020a17090b1e0800b001f51f0d3736mr20317076pjb.58.1661017360516; Sat, 20 Aug 2022 10:42:40 -0700 (PDT)
Received: from smtpclient.apple (52-119-116-148.PUBLIC.monkeybrains.net. [52.119.116.148]) by smtp.gmail.com with ESMTPSA id bn20-20020a056a02031400b00419ab8f8d2csm4577790pgb.20.2022.08.20.10.42.39 for <dispatch@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 20 Aug 2022 10:42:39 -0700 (PDT)
From: Benjamin Goering <ben@bengo.co>
Content-Type: multipart/alternative; boundary="Apple-Mail=_CDC12D7C-086C-4ACF-8AD4-350724C88BE8"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
Message-Id: <3A23DD0B-1BCB-47BC-8316-33F08C6101FA@bengo.co>
Date: Sat, 20 Aug 2022 10:42:38 -0700
To: dispatch@ietf.org
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/ZK5ZHVtOwXBPGIQ6OpEGP1tapsQ>
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: Sat, 20 Aug 2022 17:43:30 -0000

+1 Manu. I’m willing to work towards this goal of publishing Multiformats specs at IETF RFCs.  I’m authenticating Manu putting my name in the byline :)

I’m will help with any editorial tasks that need to do be done. I’m new to the way of doing things around IETF, but will learn motivated by excitement to build with and benefit from systems that interoperate using did-core and VCs, including those specs’ normative dependencies of Multiformats. If any support from Multiformats.io <http://multiformats.io/> or https://github.com/multiformats/ <https://github.com/multiformats/> operators would be useful, I can also help chase down answers or actions from colleagues there.

To bemasc@google.com <mailto:bemasc@google.com>’s question about whether there could be an open registry for appending new values: Like Manu, I also expect that this would be useful and should be created. I asked some other colleagues who’ve worked on Multiformats for longer and they agreed.

Manu had previously asked:

> What are the benefits of just documenting an existing practice for now?

I find myself wondering the same question?

I would be happy if we can work on this within a WG as a Proposed Standard.

Is anyone else making use of any of the specs linked to in Manu’s original post <https://mailarchive.ietf.org/arch/msg/dispatch/Q9aUoF01Upbvl7STjJvjoU8hlHM/> and think they could be improved by standardizing here the Multiformats they make use of? 

PS: Sorry if this message breaks threading. I looked for a ‘reply’ button on mailarchive.ietf.org <http://mailarchive.ietf.org/> but couldn’t find one.

- ben@bengo.co , bengo@protocol.ai