Re: [dispatch] ALLDISPATCH - Call for topics

Christopher Allen <> Fri, 02 February 2024 00:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DD466C14F684 for <>; Thu, 1 Feb 2024 16:26:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Status: No, score=-6.906 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id z0nSmU_x881w for <>; Thu, 1 Feb 2024 16:26:20 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::52f]) (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 36E8DC14F686 for <>; Thu, 1 Feb 2024 16:26:20 -0800 (PST)
Received: by with SMTP id 4fb4d7f45d1cf-55fbbfbc0f5so2020604a12.0 for <>; Thu, 01 Feb 2024 16:26:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20230601; t=1706833578; x=1707438378;; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=6RWE9xiRFUewWSer0q7/iQ+pDyDla3wq/kDl1DJu9e0=; b=LlyA+kaa2gUuaqYhS7ZwqX7vV1opgW6z53Zr7wlbaO0WXIOgHgX+MAgcsfv32YLeH3 Csyro8hzhHcjjIP5VLJvRL2WKUtl4PqVZ1aBg2L/7LlVbSimFtAj2GQTM2ARFyZn22sW U5jOQ5z50D010o1tQeJG6nzC1EaqKPUR4CVmax5E7TwhAmQQm6heWBIpYejtz9Mtop9t u3+EdZTan9cUZq1IEleU0qwCP2Hu+o0EL1a7aqtip+nX4kk65E7MlG/UFRbaY9UDITmP cEeSaxJWUHx9faZO9GNZ9BJIxHiKUx1HFzYxTyz2+rMk690EZ1jHdoEfue8GbXjjOJz3 vtaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20230601; t=1706833578; x=1707438378; 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=6RWE9xiRFUewWSer0q7/iQ+pDyDla3wq/kDl1DJu9e0=; b=GSiEVAUQbNi09UrogNIxjjQRcUu11iTKuci6Ifv5+Kdv00Ye7epn3DmN8jzEvYpOWi CohJKPUfuMNby73/MgDoPUBzvzSRB1I7Y87EeGvj2enkqPRP4veiKihYJ6ivhbVEBCfy 09LyeysSC6kDWVZaU4vgIwcEJdTRcDLstdUG1x7wK6rPkeJhgZVJ9h+0kwELi9s0Z/CL mdHU+/boOfUbJ6w7BBlC6dxOZGGo8VFcIWKXPoYc4CYUgInloOHf6oVK3oCIDIfiz5Ws pvWWviu4mqfQB7s2Bg5fF5Y1LqCPfJfK4b/A8SXNuNZpvA2/y/K3ZpRWtlHoWxD6fDdO AAbg==
X-Gm-Message-State: AOJu0YybLFRPJyXyzkNCS3fo+4w2s3HGiZ7EcgfOq11fafdkTKez7XmF u1MUfQxAJr8yd2bdq2QyD3Zi9lInKopXEyvY02j8NCPH/4FDM32Qn1TLkgcQzuVhaOYokxmkkm4 LDSyN0xc90qb5jR06IgcxdKOLZfugRNgQOygl
X-Google-Smtp-Source: AGHT+IHh/MjA4TeF2AvIQ8n6gXFLE5HdIuJpZCA5O9vbI/TVfMMyIuhTnOgdeLFMmqv5ZWf6yjay+b3W203hMrvxgeA=
X-Received: by 2002:a17:907:7e9c:b0:a37:60e:3cfc with SMTP id qb28-20020a1709077e9c00b00a37060e3cfcmr152556ejc.0.1706833578178; Thu, 01 Feb 2024 16:26:18 -0800 (PST)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Christopher Allen <>
Date: Thu, 01 Feb 2024 16:26:07 -0800
Message-ID: <>
To: Rifaat Shekh-Yusef <>
Cc:,, secdispatch <>,, Kirsty Paine <>, Jim Fenton <>, Carsten Bormann <>, Wolf McNally <>, Shannon Appelcline <>, Shigeya Suzuki <>, Jon Callas <>
Content-Type: multipart/alternative; boundary="0000000000001e4d3006105b290e"
Archived-At: <>
X-Mailman-Approved-At: Thu, 01 Feb 2024 17:19:00 -0800
Subject: Re: [dispatch] ALLDISPATCH - Call for topics
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: Fri, 02 Feb 2024 00:26:24 -0000

On Mon, Jan 22, 2024 at 8:23 AM Rifaat Shekh-Yusef <>

> We're calling for agenda topics for our next meeting at IETF 119 (16 - 22
> March2024). 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 or SEC or GEN
> areas or elsewhere in the IETF, get in touch and get involved.
> If you would like time at the meeting to discuss your work or ideas,
> please email the chairs. We're keen to hear from you!

At IETF Dispatch 116, we presented both dCBOR ( and
Gordian Envelope (
for discussion.

The Dispatch 116 Outcome (
>  * Dispatch dCBOR parts of this work to CBOR WG and refine the envelopes
part (create a requirements-and-use-cases draft, and potentially bring back
for a BoF).

We have successfully moved forward dCBOR I-D (now -07) in the CBOR WG,
Carsten Bormann has joined as a co-author, and though it has not officially
been accepted by the CBOR WG for RFC track, it looks well on its way.

We also have shared the Gordian Envelope with the CBOR WG, and a number of
improvements have been made based on their input (the I-D is now -05).
However, though there is some interest in CBOR standards for graph and
structured data, largely they believe it is out-of-scope and should be
pushed up to the application layer and thus ART.

Thus we have created an internet-draft "Problem Statement and Areas of
Work" for  "Deterministic Hashed Data Elision" for consideration by
Dispatch 119 for a possible BOF at IETF 120.
>  This document discusses the privacy and human rights benefits of data
minimization via the methodology of hashed data elision and how it can help
protocols to fulfill the guidelines of RFC 6973: Privacy Considerations for
Internet Protocols and RFC 8280: Research into Human Rights Protocol

Gordian Envelope also addresses a number of requirements for interchange of
graph and structured data, but believe that the primary benefit of Gordian
Envelope is leveraging elision/redaction for privacy. Thus Gordian Envelope
demonstrates the benefits of hashed-based elision for applications.  As the
only cryptographic algorithm is SHA256 based merkle-tree, we'd like to see
this "Problem Statement and Areas of Work" I-D and potential BOF be
considered under ART.

Note that there is elision/redaction & cryptographic selective disclosure
specification work also happening at ISO and W3C, and IETF should have a
voice in these requirements.

At Dispatch, we'd like to present both:
* WHY elision/redaction is important and more IETF standards and apps
should add data minimization through elision as REQUIRED, not MAY.
* HOW An introduction Gordian Envelope and its privacy use cases (
and how it proves an architecture for data minimization and privacy is

As these topics would likely have two Q&As, if there is time available we'd
like to have 30 minutes. However, if time is tight we can try to fit both
in 15-20m.

Let us know if there is anything else you need.

-- Christopher Allen, Wolf McNally, Shannon Appelcline