IETF Logo Mail Archive

Re: [Wpack] WPACK side meeting at IETF105

Phillip Hallam-Baker <phill@hallambaker.com> Tue, 09 July 2019 14:41 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: wpack@ietfa.amsl.com
Delivered-To: wpack@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97566120440 for <wpack@ietfa.amsl.com>; Tue, 9 Jul 2019 07:41:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.126
X-Spam-Level:
X-Spam-Status: No, score=-0.126 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.247, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mi17zDnkTWEb for <wpack@ietfa.amsl.com>; Tue, 9 Jul 2019 07:41:52 -0700 (PDT)
Received: from mail-ot1-f50.google.com (mail-ot1-f50.google.com [209.85.210.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A83612042D for <wpack@ietf.org>; Tue, 9 Jul 2019 07:41:52 -0700 (PDT)
Received: by mail-ot1-f50.google.com with SMTP id z23so20143647ote.13 for <wpack@ietf.org>; Tue, 09 Jul 2019 07:41:52 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=oYhRHzV042g4dwMYcTuSKGNboMRUI7F8ut/ggR3X9B0=; b=tQzkdTzr6SHNuqRhfJ5MT/FJU+V1mx32K5xD83WmkWIXBF4yMlezc+pt9JGOIPDlDk VaLw//bW/oK2DKGxCQbY3XpEkWdA1RbOZcqHW2TbR+s6p8NSNccMDe+CD88fnNap7zBt iGYdvKh+DGy0GKj/CAeqVMu4O1Y30vA16LT7GoNBQ8pA/ORG7N0RbR1wPQnsKT7u/ZqW aON/rA3H4/eXtUSHOOJPOZhKdDLNYHuEJGk1MImQKXPHoP4/+qamKNasph1AhyA9bjWM jVUhajb9kDfCl5vvCvGTVCybwcFH526XI860J14ReDF91Uq0mkL3MoFDXPkUEyfdYR0t XdLQ==
X-Gm-Message-State: APjAAAVxBoAI/4mmR9o3Pvt0saaLkSm6SBui8Ss74vnqptXFfAaqMjS2 ClcVqH791zpz/DTDkgJsis1/00DZgNid14duv/c=
X-Google-Smtp-Source: APXvYqxnUuHkhjxBfdifn2lH8wsToeEQJ+kNHKQ6Ckrpxery5fLy0voSeETlJghlBdQf+8VuzhybFibWZuRet2j/p04=
X-Received: by 2002:a05:6830:1206:: with SMTP id r6mr19713428otp.37.1562683311512; Tue, 09 Jul 2019 07:41:51 -0700 (PDT)
MIME-Version: 1.0
References: <CANh-dX=C=eZOFGiZqYsnJGOJg=0boUUxE+Qj-f-=xuNpNpCO2g@mail.gmail.com>
In-Reply-To: <CANh-dX=C=eZOFGiZqYsnJGOJg=0boUUxE+Qj-f-=xuNpNpCO2g@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Tue, 09 Jul 2019 10:41:40 -0400
Message-ID: <CAMm+LwhRJUYxeB80bUvihrPM+Q_Q_iFQnio+bMJ3Z3b86=csyQ@mail.gmail.com>
To: Jeffrey Yasskin <jyasskin=40google.com@dmarc.ietf.org>
Cc: wpack@ietf.org
Content-Type: multipart/alternative; boundary="000000000000addf8f058d408f17"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wpack/9hhltIvsUo_VPV9UG123FBfBVQ4>
Subject: Re: [Wpack] WPACK side meeting at IETF105
X-BeenThere: wpack@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Web Packaging <wpack.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wpack>, <mailto:wpack-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wpack/>
List-Post: <mailto:wpack@ietf.org>
List-Help: <mailto:wpack-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wpack>, <mailto:wpack-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jul 2019 14:41:55 -0000

I have a packing technology that supports all the traditional capabilities
of ZIP (incremental updates, compression) plus new cryptographic
capabilities that are currently unique.

The two packing scenarios that are relevant to escape type considerations
are use as a software distribution format (it has Merkle tree
authentication) and to support confidentiality (incremental and threshold
encryption are supported).
Threshold encryption is important in my view because most of the data
breaches we are seeing today are breaches of data at rest. Existing CRM
systems that are sold are based on the Ford-Wiener key release scheme which
works for DRM because it isn't a confidentiality problem. The contents of
the Lord of the Rings movie are not confidential, the concern is preventing
onward distribution.

With threshold encryption, the private key is split in two so the cloud
service does not have the ability to decrypt the document by itself. If the
key is split into n pieces, it takes n breaches.

I submitted this as Internet Drafts but they are written according to the
new HTML with diagrams format which is not yet supported by the IETF
tooling. My tooling supports it so I recommend reading the document version
here:

http://mathmesh.com/Documents/draft-hallambaker-mesh-dare.html
http://mathmesh.com/Documents/draft-hallambaker-mesh-cryptography.html



On Fri, Jun 28, 2019 at 7:30 PM Jeffrey Yasskin <jyasskin=
40google.com@dmarc.ietf.org> wrote:

> I'd like to schedule a time for this group to chat about the state of web
> packaging in Montreal. We'll have just finished the ESCAPE workshop (
> https://www.iab.org/activities/workshops/escape-workshop/), and I can
> discuss the progress in the specifications and Chromium's implementation.
>
> Would anyone have trouble attending the 8:30-9:45am slot on Tuesday
> <https://datatracker.ietf.org/meeting/105/agenda.html#2019-07-23-080000>?
>
> I'd also like to invite folks from this group to present their thoughts on
> the subject. Let me know if you want time and how much, and I'll put an
> agenda together.
>
> Thanks,
> Jeffrey
> _______________________________________________
> Wpack mailing list
> Wpack@ietf.org
> https://www.ietf.org/mailman/listinfo/wpack
>

v2.23.0 | Report a Bug | By Email