IETF Logo Mail Archive

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

Eric Rescorla <ekr@rtfm.com> Wed, 26 October 2022 15:58 UTC

Return-Path: <ekr@rtfm.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 3BF82C14F74B for <dispatch@ietfa.amsl.com>; Wed, 26 Oct 2022 08:58:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, 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=rtfm-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 3u2VRQA-q1Om for <dispatch@ietfa.amsl.com>; Wed, 26 Oct 2022 08:58:02 -0700 (PDT)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 91521C14F734 for <dispatch@ietf.org>; Wed, 26 Oct 2022 08:58:02 -0700 (PDT)
Received: by mail-io1-xd2b.google.com with SMTP id p141so862843iod.6 for <dispatch@ietf.org>; Wed, 26 Oct 2022 08:58:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Jy33nzDNhVw97VS4d+5hDyTGKwwX2vONsFyW5feSwEE=; b=4WQ04Dh6+xvzvi7F6T3Sw/Nk0k/DABruOiwzVgKado2sC3or5vkCb81u2YiKbQl/Ri srvBlib64QvQ6JUzUu4A+7B3zv6FTGfxMFDufrsqu9L+48FPiW8jJprxeG3DJ2iyvoSF N4rS2wvzmuX49kVydWPyMp32zl011VwVB9KleLyd0V35sLB6wFiqQHAcdrnJTfF729Nq J0yhNeFEbkStQ16TA5GRPc4yKnKYVJkDLvenXxF7HVyamYf9enFXtYoDAJ7ZAyMJKeE4 vNP3f6qyzaItiZJd22EHaePh2qhiSyp7X2Gq9L24zXPScRWWfK356J0V5jRxuB1vxMln pNIQ==
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:subject:date:message-id :reply-to; bh=Jy33nzDNhVw97VS4d+5hDyTGKwwX2vONsFyW5feSwEE=; b=i7W0vZKC1uKiKKliIpbfMyZ0qvPDkFF8jZldtoyleVMcHmfICtgr9AROC9cx6b8hxn Iopib7agFzlBNv5i9NbcwI60szAoaGmJ2RwUWNRUVzddKxubKv8nMF8y+PPWKZVRBsbX 1Zx5V056RCwDN8YiGJ5fId5q38am+wg+6ulKSBMkj2yTQ1ycKMK7LLnJDjmhWiAf33ij QE4QKbSWaJLbKeVFLZbfJnOWeQhzLGn/5hGymh/VPV9+hPuXUR3oGKvKxIpH1DeyXUkH 9Z482XgIlddU5oDO5Wye59QiFM7qcVb3FrJeiWj2r1w1bXYEJu8/vktWfIItHsIy0FUV SQEw==
X-Gm-Message-State: ACrzQf0pKqTmWX6FX2LMBMZuPC/HYwkCt7WZCSRq/op1NGscnCxCyPy5 XNdczybOWPHOQOuzrkOUrWtnOljZvzpLPn3mfVf0ZDgPYI0=
X-Google-Smtp-Source: AMsMyM69iJRunzMBfN5tXVy2KNFUtT2nJ8srnUP8M02U9/1BJBURzMs16Tez0qc5AnOLWMLxmOV6wVExGZRmldFmhIA=
X-Received: by 2002:a05:6638:1394:b0:374:798:98a1 with SMTP id w20-20020a056638139400b00374079898a1mr8958093jad.61.1666799881854; Wed, 26 Oct 2022 08:58:01 -0700 (PDT)
MIME-Version: 1.0
References: <3A23DD0B-1BCB-47BC-8316-33F08C6101FA@bengo.co> <ca072ab0-e303-53ba-bde8-fcb193af85c9@berjon.com>
In-Reply-To: <ca072ab0-e303-53ba-bde8-fcb193af85c9@berjon.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 26 Oct 2022 08:57:25 -0700
Message-ID: <CABcZeBPGcGOwAhawiBKQdzsC+e7CnSEzCPwv947rSr1eN3iZ1g@mail.gmail.com>
To: Robin Berjon <robin@berjon.com>
Cc: ben@bengo.co, dispatch@ietf.org
Content-Type: multipart/alternative; boundary="000000000000debf4405ebf21684"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/Imc13-H5P-v7ZcxUM-bm2HrLLy0>
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 15:58:06 -0000

I think the preliminary question is whether the proposal is to give change
control over the normative aspects of this to the IETF.

If not, then you might publish these as informational but the IETF
shouldn't pick them up as part of its standards process.

-Ekr


On Wed, Oct 26, 2022 at 6:07 AM Robin Berjon <robin@berjon.com> wrote:

> 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/
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>

v2.23.0 | Report a Bug | By Email