IETF Logo Mail Archive

Re: [dispatch] Demonstration of Implementer Support for Multibase and Multihash at IETF (was: Re: Finding a home for Multibase and Multihash)

Ross Finlayson <finlayson@live555.com> Mon, 03 April 2023 17:34 UTC

Return-Path: <finlayson@live555.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 09FBFC14CF1E for <dispatch@ietfa.amsl.com>; Mon, 3 Apr 2023 10:34:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 gLrOjFSTSFCW for <dispatch@ietfa.amsl.com>; Mon, 3 Apr 2023 10:34:47 -0700 (PDT)
Received: from us.live555.com (us.live555.com [52.8.240.222]) (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 C13DBC14CF1B for <dispatch@ietf.org>; Mon, 3 Apr 2023 10:34:47 -0700 (PDT)
Received: from smtpclient.apple (localhost.live555.com [IPv6:0:0:0:0:0:0:0:1]) by us.live555.com (8.16.1/8.16.1) with ESMTP id 333HYkJN032667 for <dispatch@ietf.org>; Mon, 3 Apr 2023 10:34:47 -0700 (PDT) (envelope-from finlayson@live555.com)
From: Ross Finlayson <finlayson@live555.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
Date: Tue, 04 Apr 2023 03:34:36 +1000
References: <c9e0219c-0bca-32ab-56b4-ead9427e7578@gmail.com> <CAMBN2CQ7ogxW3YA-i7bg6KHEuBGpWcgcOssnGPoxvzNmesa4Pw@mail.gmail.com> <e62bd6c6-99b1-233e-06fe-057bf48bf7f6@it.aoyama.ac.jp> <CAMBN2CT=zgYX0zYnfSCgC+s95pGLUGkNdZrrBg8U=iCJFPYw0Q@mail.gmail.com>
To: dispatch@ietf.org
In-Reply-To: <CAMBN2CT=zgYX0zYnfSCgC+s95pGLUGkNdZrrBg8U=iCJFPYw0Q@mail.gmail.com>
Message-Id: <39658573-5403-4EFE-94D2-382532A48159@live555.com>
X-Mailer: Apple Mail (2.3731.500.231)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/dGNFfIZc1zmnDtV8WiRjdNgf5xM>
Subject: Re: [dispatch] Demonstration of Implementer Support for Multibase and Multihash at IETF (was: Re: 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: Mon, 03 Apr 2023 17:34:50 -0000


> On Apr 4, 2023, at 12:02 AM, Manu Sporny <msporny@digitalbazaar.com> wrote:
> 
> "discussion in Github should not be seen as final" is starting to
> feel like it's at the cusp of being an antiquated idea. If we look at
> the volume of where conversations are happening now at places like
> W3C... the vast majority is done via Github issue trackers, Slack, and
> Signal channels.
> 
> Sadly, these are proprietary tools

This is more significant than just being “sad”.  (Not to mention the fact that there is more than one of these tools, and they don’t appear to be interoperable.)

Until this gets fixed (does anyone know of a standards organization that could do this? :-), having a mailing list acting as ’the truth’ remains a necessity.

	Ross.

v2.27.8 | Report a Bug | By Email | System Status