Re: [dispatch] ALLDISPATCH - Call for topics

[Christopher Allen <[e-mail]>]

On Mon, Jan 22, 2024 at 8:23 AM Rifaat Shekh-Yusef <[e-mail]>
wrote:

> 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 (
https://datatracker.ietf.org/doc/draft-mcnally-deterministic-cbor/) and
Gordian Envelope (https://datatracker.ietf.org/doc/draft-mcnally-envelope/)
for discussion.

The Dispatch 116 Outcome (
https://mailarchive.ietf.org/arch/msg/dispatch/iOGkPUHMDRLyL41Ici6CxPu358w/)
was:
>  * 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.

https://datatracker.ietf.org/doc/draft-appelcline-hashed-elision/
>  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
Considerations.

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 (
https://www.blockchaincommons.com/introduction/Gordian-Envelope-Use-Cases/)
and how it proves an architecture for data minimization and privacy is
possible.

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