[Multiformats] Wordsmithing the proposed charter before official review

Bumblefudge <bumblefudge@learningproof.xyz> Mon, 07 August 2023 09:19 UTC

Return-Path: <bumblefudge@learningproof.xyz>
X-Original-To: multiformats@ietfa.amsl.com
Delivered-To: multiformats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37461C151555 for <multiformats@ietfa.amsl.com>; Mon, 7 Aug 2023 02:19:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_TEMPERROR=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=learningproof.xyz
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 w-JhUamyfPeP for <multiformats@ietfa.amsl.com>; Mon, 7 Aug 2023 02:19:32 -0700 (PDT)
Received: from outbound-smtp.skiff.com (outbound-smtp.skiff.com [35.81.193.184]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A372AC151551 for <multiformats@ietfa.amsl.com>; Mon, 7 Aug 2023 02:19:32 -0700 (PDT)
Received: (Haraka outbound); Mon, 07 Aug 2023 09:19:32 +0000
Authentication-Results: outbound-smtp.skiff.com; auth=pass (cram-md5)
Mime-Version: 1.0
From: Bumblefudge <bumblefudge@learningproof.xyz>
To: multiformats@ietfa.amsl.com
Message-Id: <e7685859-2824-47ee-a348-1e71fae92f59@mail.skiff.com>
References:
X-Skiff-Message-Id: b158e780-66cd-4a27-acb4-8a0dffbeff72
Date: Mon, 07 Aug 2023 09:19:31 +0000
Feedback-Id: 40ca9614-451c-4274-999c-e9f9e8cfdd07:SkiffMail
Content-Type: multipart/alternative; boundary="7bfd2e69733a8939f69eb2742deb14640a850019b46e1832c2544d83f12f"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=learningproof.xyz; s=skiff1; h=subject:subject:from:from:to:to:date:date:message-id:message-id:reply-to:resent-date:resent-from:resent-to:resent-cc:in-reply-to:references:references:list-id:list-help:list-unsubscribe:list-subscribe:list-post:list-owner:list-archive:feedback-id:feedback-id:content-type:content-type:content-transfer-encoding:content-disposition:mime-version:mime-version:sender:resent-message-id:resent-sender:content-description:content-id; bh=YG/6E9hYZEoj6Bg1J+e0D4p7G6OlJy8QWYAfxHIDWKg=; t=1691399972; x=1691403572; b=JNMatWtZP8BK4bLXPcuw/jtBgLUdGY4yNnAB8VlC+056D4eAnquctIQMjWrTRM9FiVdWCcfnf6 FV9BtQ7GW5V31RoToA/tvkSenKV4eXudK2vjtvd/TPVQNlEvySZkqWzs9Sd2RtKA25zwcgEYIvvN zP421AHC5vOBABnciTBQpXflyMclLdD64vVEjS6b6pex2nlTX211R0XqHk7A+0XYr+ElgXRkFhQ7 iHUN8FCSXOpfx1bfz/oPew3l7Q728aTVfwKnTIh7RVaO4lesPYeJu77H0SfjiLrbhyq503gDfnON mgWe8lr03pUzSkngcR6RyJoLpnfHOJawTo6+1qpQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/multiformats/Ac-yj5YH0pZQx4pYLgFaUDdGAR4>
Subject: [Multiformats] Wordsmithing the proposed charter before official review
X-BeenThere: multiformats@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion related to the various Multiformats data formats <multiformats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multiformats>, <mailto:multiformats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multiformats/>
List-Post: <mailto:multiformats@ietf.org>
List-Help: <mailto:multiformats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multiformats>, <mailto:multiformats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Aug 2023 09:19:38 -0000

Dear Multiformats enthusiasts:After consulting with some maintainers and the tribally knowledgeable Designated Experts on today's multicodec table, I have proposed [a few tweaks to the charter][1]. These edits mostly just set the stage more explicitly for clearer and more explicit multibase and multihash specs, and a tidier order-of-operations for the future working group, such as breaking down the intended deliverables into individual RFCs and numbering them in chronological order. The only substantial change in scope is that the first order of business will be finalizing an IETF RFC for unsigned_varint, since having this be very explicitly specified will make all the other registries and specifications easier to codify. A few +1s here on the list or there on the PR would be appreciated, as would change-requests or timely shouts of "sacrilege! blasphemy!"Thank you,__bumblefudge / juan[1]: https://github.com/msporny/charter-ietf-multiformats/pull/1/files		----bumblefudgejanit
 or @Chain Agnostic Standards Alliancecontractable via learningProof UGmostly berlin-based		Secured by Skiff Mail.