Re: [dispatch] IETF 116 - do you have something for DISPATCH?

Anders Rundgren <> Mon, 06 March 2023 07:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8F9D5C15155E for <>; Sun, 5 Mar 2023 23:30:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Status: No, score=-7.096 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, NICE_REPLY_A=-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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id VXI8x4vTZvuA for <>; Sun, 5 Mar 2023 23:30:10 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::334]) (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 (Postfix) with ESMTPS id 134C7C1516E2 for <>; Sun, 5 Mar 2023 23:30:10 -0800 (PST)
Received: by with SMTP id o38-20020a05600c512600b003e8320d1c11so5095965wms.1 for <>; Sun, 05 Mar 2023 23:30:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; t=1678087808; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=nYJyt8b+zYMQICvCzl1USew6uaUFhEeZzDWMGZ8gVGE=; b=g5aq76J56P7X53ssYolpzA6zuUItmHOEq5uEE8GIGGgwXGW/+Qlzv7PULU0I8TA2ma B06r77s7VPduIa98MTgBu8F0wkDNX9PIHQ62I+G0X4SxqdERij8BhPAMVMoamcgNFL7a NanLId/IAJ7fDnXmZo2HORuIVy75vPpkNuL0q8dxR193dNhF99iQklgCkrszeEseAXN3 JpM0o15yENVrz1IjEkX121hpTwRph5f5LZtkNMW7wXH4n8R5MNGGE1mGv50mmdr0eLzy 1KGa3M7y0w6Le9bRhx220XpPGEgEISKQBP/7Z0vh7TCE9CFyIBBuuhflaDitzv/1LsiB cscg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; t=1678087808; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=nYJyt8b+zYMQICvCzl1USew6uaUFhEeZzDWMGZ8gVGE=; b=UqyyHucreRO1wTZVMtxrtdLYoEVnUpXyUnTYujxx8EVAfRDC0NAEd/uQmfJSnp1GaJ EdJSu/I5X2rPZ3UVCxO/MPiU0geaqxLIyo8nq6955ktyejbTeLTK2l53WkWJB8Dl6cn6 2vGb7E0MX541UU4aEaKVT5ddaHcveEde9jFVgwczo8pu8sihrC5fJ405mLFpiZ/QHtGU nwbhYeVVzDeJJfNfxjw1EkzZ/GzQ9NT7SJSp+XGUL/SzsC6VWF/5ja2SUfQd3GhJnMTw NDMjhr0o8ZUJQ5wf5wqtz4aiESDekChnw1vaeG98fdLAjpysWqnYu4rAfcTy4eXhO9MH AVQg==
X-Gm-Message-State: AO0yUKXWboZpicAgoFIDqIvwdhHfsHQSac9QSQrcP3dRiZhPu6YOSltK dUn/4dWw7stBcUx7gJnPa8U=
X-Google-Smtp-Source: AK7set/9U7/apFucpOUQimdy6endQ0kPDNJ3MKlACF5l28w+F6e14BBilVpdLn94ND/gUwnqXsF5Pw==
X-Received: by 2002:a05:600c:5126:b0:3ea:f6c4:3060 with SMTP id o38-20020a05600c512600b003eaf6c43060mr8219250wms.18.1678087807915; Sun, 05 Mar 2023 23:30:07 -0800 (PST)
Received: from ?IPV6:2a01:e34:ec4e:5670:2439:9550:6ec8:51ee? ([2a01:e34:ec4e:5670:2439:9550:6ec8:51ee]) by with ESMTPSA id n37-20020a05600c3ba500b003e2052bad94sm14293173wms.33.2023. (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 05 Mar 2023 23:30:07 -0800 (PST)
Message-ID: <>
Date: Mon, 06 Mar 2023 08:30:06 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0
Content-Language: en-US
To: "Pengshuping (Peng Shuping)" <>, Christopher Allen <>, "" <>
References: <> <> <>
From: Anders Rundgren <>
In-Reply-To: <>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <>
Subject: Re: [dispatch] IETF 116 - do you have something for DISPATCH?
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 06 Mar 2023 07:30:13 -0000

On 2023-03-06 2:48, Pengshuping (Peng Shuping) wrote:
> Hi Anders,

Hi Shuping,

> Shall I consider that you are asking for a slot to present D-CBOR in this DISPATCH meeting?

I would like to but since there are two slightly different definitions [*] on the table, I pass on this and hope that we end-up with a unified approach.

Best regards,

*] floating point and integer serializations should be distinct or not.

> Best Regards,
> Shuping
> -----Original Message-----
> From: dispatch [] On Behalf Of Anders Rundgren
> Sent: Sunday, March 5, 2023 3:52 PM
> To: Christopher Allen <>;
> Subject: Re: [dispatch] IETF 116 - do you have something for DISPATCH?
> On 2023-03-02 6:02, Christopher Allen wrote:
>> On Tue, 21 Feb 2023 06:40:27 +0000 "Pengshuping (Peng Shuping)" < <>> wrote:
>>      It's that time again - we're calling for agenda topics for our next meeting at IETF 116 (25 - 31 Mar 2023). No matter how big or small, if you have something you'd like dispatching or that you think will be of interest to the ART AREA, get in touch and get involved.
>> My name is Christopher Allen. I’ve worked with IETF previously as the editor of the TLS 1.0 standard, but it’s been a number of years since I've been actively involved with IETF — most of my recent standards work has been with the W3C.
>> I’m now the Principal Architect of Blockchain Commons, and I would love to join your agenda for Dispatching a new project.
>> Blockchain Commons is working on Gordian Envelope, a “smart document” that supports the secure, reliable, and deterministic storage and transmission of data such as seeds, keys, decentralized identifiers, and verifiable credentials in a way that enables privacy while preserving structure.
>> We’ve submitted it as an IETF Draft (and plan to have -01 submitted before the I-D deadline this month):
>> <>
>> Here are some general thoughts:
>> PROBLEM STATEMENT: Current document formats don’t focus on a user’s ability to use elision, encryption, herd privacy, and other methods to preserve the privacy of their data in a granular way.
>> EXISTING INTEREST: Several companies have seen the need for these capabilities and have been participating in regular meetings on the topic. ( <>)
>> INTENDED DELIVERABLE: We want to produce a revised draft with more community input to ensure that the specification meets the requirements of a larger community.
>> We’d like to present on Gordian Envelope to Dispatch and get the best advice on how to move forward. We would obviously like to work with groups who might want to make use of Envelope for its privacy-preserving document format. We also think we have critical mass on the US west coast to justify a BOF there and would like to see if Dispatch would be interested in supporting that.
>> As part of our work on the Gordian Envelope, we embraced deterministic CBOR (dCBOR), which is the foundation of Envelope. dCBOR is an optional variant of CBOR that lies in the CBOR spec but hasn’t been widely used. Because determinism is very important for the hashing that we use at the center of the Envelope format, we’ve created and released what we believe are the only reference libraries focused on dCBOR as part of our intersectional work on the topic. We’d love to get advice from Dispatch on how to work with other CBOR-focused groups who might be interested in the work we’ve done to support the deterministic subset defined in the IETF CBOR specification. (We’ve tried to contact some on our own, but we appear to getting stuck in email filters.)
> The definition of a usable subset of CBOR supporting deterministic serialization would IMO qualify as a separate DISPATCH work item:
>> Finally, we would like advice from Dispatch on the best way to register our cryptographic-focused CBOR tags used in Envelope with IANA, namely whether we should do so now, or whether we should wait for later in the IETF process.
> Before you do, I would not rule out
> which I hereby propose as a DISPATCH work item.
> Anders
>> Thank you very much for your advice and support. Please let us know of anything else we can tell you and what else we’d need to do in order to schedule a presentation with Dispatch.
>> -- Christopher Allen
>>      Blockchain Commons
>> _______________________________________________
>> dispatch mailing list
> _______________________________________________
> dispatch mailing list