IETF Logo Mail Archive

Re: [Multiformats] IETF Multiformats WG charter proposal

Melvin Carvalho <melvincarvalho@gmail.com> Fri, 14 July 2023 13:43 UTC

Return-Path: <melvincarvalho@gmail.com>
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 F3CDCC151AE5 for <multiformats@ietfa.amsl.com>; Fri, 14 Jul 2023 06:43:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.094
X-Spam-Level:
X-Spam-Status: No, score=-7.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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=gmail.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 YFd5bFdE4K5T for <multiformats@ietfa.amsl.com>; Fri, 14 Jul 2023 06:43:56 -0700 (PDT)
Received: from mail-yw1-x1134.google.com (mail-yw1-x1134.google.com [IPv6:2607:f8b0:4864:20::1134]) (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 29332C151AE4 for <multiformats@ietf.org>; Fri, 14 Jul 2023 06:43:56 -0700 (PDT)
Received: by mail-yw1-x1134.google.com with SMTP id 00721157ae682-57a551ce7e9so17721197b3.3 for <multiformats@ietf.org>; Fri, 14 Jul 2023 06:43:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689342235; x=1691934235; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=vN78sd6wDJ7vGkciiMKDGNsunlWzeVOmXICVI1a7qTk=; b=aK9x2WJ+a2Tgb/UU5FypFnoM1TmTDORriZhxrKycLbF+hMFBJE9ir4XbvoHxQPKIci FYAeD83j6rc0yVsE5TjzLze44iswPj+DTlgqUk3QvAamA3RtlEeUjS9y6sSFwCAt0CLR 7skkBP9GOJ5ndDoefjjLx86WpnB8ow1A2lxRuQMkqyV3OnN0wWAYyvWz8TAP8lFumR2q fJBnXIdvnoSN6ixrCM1wyl4t6wvoBeYro5vWIYmP7XTtDf1mQiooeVFDGlwaE0B/l5WZ 9hXL1lqj6Fk3t3QEfCc7YCN5GlnpQcXZQOsECOEpF6JtBA/5sUvcVrcDUFOZuPQpdaFQ xG7g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689342235; x=1691934235; 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=vN78sd6wDJ7vGkciiMKDGNsunlWzeVOmXICVI1a7qTk=; b=MFsSdltAYp8K3Ui3M/03neyuarrb4azFo8X0C/xjG7nCUKrUH1fAA5O39daFsmTozG wFlB/TSCBPL+0VG9CvAvnh+kSZfRZKzIgjiOOk8KZ0uypFt8pwesNFiqTKmqiEfTwIv0 DVRrF5X5Bd2OVfWPbWKRO9uGvc1WusBC+KsISG/YCNwyUXyGoPUsFLTUUNfXtHCCR9nZ zk89JWDIGrDs4OzHpgVmGGHz/ap143a3gYTwmoteItlTOpaiDo7mrJ2nUnwG1vDaRAIc rpmSLZAGtTcUeEz9vsas//1WRJOaDBl86j1jDp0qGJ/wSsMeYW/T8o952ACGrf1zwiuj +MmQ==
X-Gm-Message-State: ABy/qLZJojzRfvm8vBTBmwAhydFpLgrohoRl6qJHRhvd3eLJ6Jle/5Tb t/YwfQsaqhGBbM/nAStRyq/CLnVIk0piy9t5OdvJLcoo
X-Google-Smtp-Source: APBJJlHE5rQ9EyTu8WUp8IY/V+EwKQh+lPYp81SZVv7IEukvJs04t4s/dkgP613NB03MhhH+2Ky/eXG/p5UGBVD/tOY=
X-Received: by 2002:a0d:c802:0:b0:577:1533:ea95 with SMTP id k2-20020a0dc802000000b005771533ea95mr5116004ywd.28.1689342234826; Fri, 14 Jul 2023 06:43:54 -0700 (PDT)
MIME-Version: 1.0
References: <CAMBN2CR+=pT7cbOkn_uhJdZXuZ+C63VU=rrNZisvKuuQYzRrrQ@mail.gmail.com>
In-Reply-To: <CAMBN2CR+=pT7cbOkn_uhJdZXuZ+C63VU=rrNZisvKuuQYzRrrQ@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Fri, 14 Jul 2023 15:43:42 +0200
Message-ID: <CAKaEYhLTgdOJRwgJbqO5ro32+o4p2E4wU-+zLkYZ4+EAfcis1A@mail.gmail.com>
To: Manu Sporny <msporny@digitalbazaar.com>
Cc: multiformats@ietf.org
Content-Type: multipart/alternative; boundary="000000000000cf9cd0060072a38e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multiformats/AjdDheiiaCY_pZc8w7jg-9Muw3U>
Subject: Re: [Multiformats] IETF Multiformats WG charter proposal
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: Fri, 14 Jul 2023 13:44:00 -0000

pá 14. 7. 2023 v 15:38 odesílatel Manu Sporny <msporny@digitalbazaar.com>
napsal:

> There have been a number of discussions (both on this mailing list and
> with the Multiformats community) regarding whether or not an IETF
> Multiformats WG should be created to process the Multibase and
> Multihash specifications. At this time, it seems as if we have broad
> agreement that a Multiformats WG would be necessary in order to
> process some of the open questions raised during IETF 116.
>
> In that vein, a draft charter has been prepared for an IETF
> Multiformats WG and the Area Directors have been notified:
>
> https://hackmd.io/@hJJkLrHaTo6aD-KUDiwCvw/H1xOICbZ2
>
> During IETF 116 dispatch, it was proposed that we could proceed with a
> "no BOF required, straight to WG" path if that is what the community
> desired, and that seems to be what the community desires at this point
> in time.
>
> We have a few volunteers from the community that are willing to serve
> as Chairs for an IETF Multiformats WG; Robin, Ben, and Juan, though
> that doesn't preclude others from volunteering to Chair.
>
> A few of us will be at IETF 117 and plan to discuss this with the ADs
> and each other during the course of the week, though prefer for the
> discussion to be reflected on this mailing list such that remote
> participants can engage in the discussion as well.
>

LGTM

My interest is in the widely deployed CID format used in IPFS.  So that CID
as identifiers can be used, but not necessarily closely coupled to any
particular tranport or DHT.

Looking at the text, that seems to be indicated, but just wanted to
confirm.  So you'll be able to have mh://<cid> or something like that.


>
> -- manu
>
> --
> Manu Sporny - https://www.linkedin.com/in/manusporny/
> Founder/CEO - Digital Bazaar, Inc.
> https://www.digitalbazaar.com/
>
> --
> Multiformats mailing list
> Multiformats@ietf.org
> https://www.ietf.org/mailman/listinfo/multiformats
>

v2.23.0 | Report a Bug | By Email