[Wpack] DARE Envelope and Sequence
Phillip Hallam-Baker <phill@hallambaker.com> Wed, 06 November 2019 20:11 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 B583B120058 for <wpack@ietfa.amsl.com>; Wed, 6 Nov 2019 12:11:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.304
X-Spam-Level:
X-Spam-Status: No, score=-1.304 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.082, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 el5x0B8Qlv1C for <wpack@ietfa.amsl.com>; Wed, 6 Nov 2019 12:11:54 -0800 (PST)
Received: from mail-ot1-f48.google.com (mail-ot1-f48.google.com [209.85.210.48]) (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 1D3FB12004A for <wpack@ietf.org>; Wed, 6 Nov 2019 12:11:54 -0800 (PST)
Received: by mail-ot1-f48.google.com with SMTP id b16so21962356otk.9 for <wpack@ietf.org>; Wed, 06 Nov 2019 12:11:54 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=tS0ha43RKeb522csbSwTxbnCM8vs/Ko27/inccDo0wA=; b=CK84E2+O0AVk+mJsDFMpWjSKNUemdG8JiTKd+R2ixbFD5CIZSRzwjfMfDjBOXJWDwc ZceXDL1HwzcLiJLBT8hShRSeNdnQ+LT0KK+6i0ywVHHNhiynz7m6bSgSflPtS07P1H28 QoHZc93l72j/DPj2ztBuU2DStOWVrH4q8B4tNOyuvzlp4npI6OPhTDPxHZA0bfExE05o AuPcF+5lPsipNb+fqp3eVQ9ntUfvzt7eq1WniBmg42cbzj8KsjnE8AM8ok1Yj6Kp2g3k 0y/W7sUTI1Rb+CriP4VMdp+s0S46+ysqDS7aGku9RGkfalm42+HSQUuai7xeUYLK/Bbs c3Yg==
X-Gm-Message-State: APjAAAUgYIK1qqAN7jEKtiDwlfpzeu6gMc2QxJMVcx4iEhmzNsE+4YME r3AgnTWgamSyXWwrVKscOrl56QmTW5cuF7a4vOyk2wdf
X-Google-Smtp-Source: APXvYqy2HKGhTSg1pqvQtvQQ1RlYeOuCyLpJR9c4cXC6PONXsY5sgDoakXpySAc/feHfyUDRiAm16l3T9HbLShtIu4g=
X-Received: by 2002:a9d:6b90:: with SMTP id b16mr1263257otq.37.1573071112912; Wed, 06 Nov 2019 12:11:52 -0800 (PST)
MIME-Version: 1.0
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 06 Nov 2019 15:11:42 -0500
Message-ID: <CAMm+Lwg8X0hfsa+0v4UCcesW5Kzkd_BSXDq8fzRv+sx60+bkTQ@mail.gmail.com>
To: wpack@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e443dc0596b32884"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wpack/rE06eI88l4SwRwDQ8aH-t5e63YM>
Subject: [Wpack] DARE Envelope and Sequence
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: Wed, 06 Nov 2019 20:11:56 -0000
It seems to me that there are two possible ways forward for WPACK The first is to reuse ZIP, the second is to do a completely new packaging format. It is not clear which people prefer. If you are going to be going down the 'new format' route, I would ask that the DARE format be considered. This will be discussed in part in the MATHMESH BOF on the Monday: http://mathmesh.com/Documents/draft-hallambaker-mesh-dare.html DARE and DARE Sequence were designed to address a different set of requirements. The idea of DARE Envelope is to provide a JSON/JOSE equivalent to PCKS#7 with the necessary hooks to support DARE Sequence which is an append only log file format with incremental encryption and authentication capabilities (i.e. it supports Blockchain type capabilities if you want to use that name). The chief concern in the design of DARE Sequence is to support encrypted persistence stores. But it was tested as an archive format as a design check. I understand that some believe WPACK scope should be narrower, but the DARE solution is not complex and I find it very difficult to believe that encryption won't end up being added to any new format as an extension. So I think it better to accept that from the start. We should at any rate discuss the possibility of a common approach. I can't drop my requirement for encryption because the whole point of the Mesh is to be able to use threshold cryptography to provide true end to end encryption of stored data. So one use of a DARE sequence might be to record encrypted comments on an encrypted Web page that neither the Web Server nor the key service nor any other cloud service has the ability to decrypt. For those of you who prefer a video presentation, the DARE format is described here https://www.youtube.com/watch?v=mLsEhzBpfNA&list=PLK2hHAOxepEgGUx4SitfD4pIPHi86KHpi&index=9&t=2s https://www.youtube.com/watch?v=T5fRneFOueM&list=PLK2hHAOxepEjcU9yXCqV39B0VB-gB7Abj&index=11&t=2s The DARE archive format is described here (available Friday) https://www.youtube.com/watch?v=9ZDUa6wvDkY&list=PLK2hHAOxepEjcU9yXCqV39B0VB-gB7Abj&index=8&t=4s
- [Wpack] DARE Envelope and Sequence Phillip Hallam-Baker