IETF Logo Mail Archive

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

Robin Berjon <robin@berjon.com> Wed, 26 October 2022 13:07 UTC

Return-Path: <robin@berjon.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 74499C1524AD for <dispatch@ietfa.amsl.com>; Wed, 26 Oct 2022 06:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.606
X-Spam-Level:
X-Spam-Status: No, score=-2.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=messagingengine.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 0eE8RuWFAoJX for <dispatch@ietfa.amsl.com>; Wed, 26 Oct 2022 06:07:07 -0700 (PDT)
Received: from new4-smtp.messagingengine.com (new4-smtp.messagingengine.com [66.111.4.230]) (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 ietfa.amsl.com (Postfix) with ESMTPS id D6A30C14F724 for <dispatch@ietf.org>; Wed, 26 Oct 2022 06:07:07 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailnew.nyi.internal (Postfix) with ESMTP id 14ABE58020B; Wed, 26 Oct 2022 09:07:03 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 26 Oct 2022 09:07:03 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1666789623; x=1666796823; bh=1 2uSjNLemRVHGy9pfWW2DeULG5iaigzQSay/qBsD4sU=; b=SAYTAH/h69XxybQAA 3tSLBoiPPPbW1aZtnIy7my3zDKx+WkeL1AzyCh3bCrpJE4vb9yCzGQaPxnjnN5Nd q8pQuIY+HoXoiLQGXBjCwZ0r5EJByXvf9r9wLAyN4ruHjDuKJmyKXsJeBs2EHEho zBE/ed5Dy7FlIhQuqX+d9g+mwzhUQab4cN1DNISoayDrAu83qJ6VK2QsNpEOvBFI HegHv+7ZWJW02tIenbTF+uWohLFVOrqtbsY4ENXvKWc9mKpouiRsc1RAz8LeUs1K biPFTimHLGOLkkj5tycB9VicVP3HbfhCVAHfCeb/ciSRidEK+D+VOf20hmnUabNx 8DOVg==
X-ME-Sender: <xms:9jBZY-pY9XaC3ItQSSCmtV259Gc3oS_1I9IX1ra7adQk0_Cy81dvPA> <xme:9jBZY8ozB0DzNC5m81NC0Hk7FsjnnDOsIBgWTLfVpCDehvAe5t2vT09tLLC2CFhg5 NaVgze2njDYCA>
X-ME-Received: <xmr:9jBZYzPhMJ3PBG3oOJ6h_X45MP4gMHT-e4Y0TBoXKtk-GwhlwDKCKx6D7xn1vih0OTq3fXqBnanaVCgiaMJAXLeVgOWugcKwwg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvgedrtddvgdeitdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfhffvvegjufgtgfesthekre dttdefjeenucfhrhhomheptfhosghinhcuuegvrhhjohhnuceorhhosghinhessggvrhhj ohhnrdgtohhmqeenucggtffrrghtthgvrhhnpefghfdtleekudeljeeiffffudeivdekle ejteehhedujedutefgveelfefhvdejffenucffohhmrghinhepsggvrhhjohhnrdgtohhm necuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprhhosg hinhessggvrhhjohhnrdgtohhm
X-ME-Proxy: <xmx:9jBZY94gC_LMESyfaakjlIQJDLH5Ne4GShR35eNZmqRNOARjI0ESFA> <xmx:9jBZY942MBt2De59_JcA8_ilb-IxRUTDJCV1p602A1PYJYDojj9MjQ> <xmx:9jBZY9hsYX5rJyigtn-ZAqoQayDN2KoMQOj_xlVojpDie1vbcsSc3w> <xmx:9zBZY-VVDhx5Y7w7ACdIgJXzPSmV8PvM0MApK8XXwYUorJGvH7dFIw>
Feedback-ID: i38c44178:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 26 Oct 2022 09:07:02 -0400 (EDT)
Message-ID: <ca072ab0-e303-53ba-bde8-fcb193af85c9@berjon.com>
Date: Wed, 26 Oct 2022 14:07:01 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.3.2
From: Robin Berjon <robin@berjon.com>
To: ben@bengo.co
Cc: dispatch@ietf.org
Content-Language: en-US
In-Reply-To: : <3A23DD0B-1BCB-47BC-8316-33F08C6101FA@bengo.co>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/R9TetVL4BATQ7vEmSkay-Q2mhRI>
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: Wed, 26 Oct 2022 13:07:13 -0000

On Sat, 20 Aug 2022, Ben wrote:
> +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 too am prepared to support Manu in working on these specs. This 
includes editing, researching, and producing tests where needed.

I do believe that a registry would be valuable. I am not sure what the 
process is for setting one up but I would be happy to look into that. 
Would we be able to reuse the protocol registries stuff that mnot operates?

-- 
Robin Berjon
https://berjon.com/

v2.23.0 | Report a Bug | By Email