Re: [jose] Using Jose as an encrypted document container.
Martin Thomson <martin.thomson@gmail.com> Tue, 03 January 2017 02:33 UTC
Return-Path: <martin.thomson@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16CF9129521 for <jose@ietfa.amsl.com>; Mon, 2 Jan 2017 18:33:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 AAjZWOQlRYJP for <jose@ietfa.amsl.com>; Mon, 2 Jan 2017 18:33:41 -0800 (PST)
Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::234]) (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 12C0A126BF6 for <jose@ietf.org>; Mon, 2 Jan 2017 18:33:41 -0800 (PST)
Received: by mail-qt0-x234.google.com with SMTP id c47so452697274qtc.2 for <jose@ietf.org>; Mon, 02 Jan 2017 18:33:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CZNrmN8HocOEOLRRpBZUaqZfdBhb6xqwtIau2Dykg8Y=; b=mgQo15czMkQD7qFJBP9rcljNFsraEHShcrPJK1oKNVinz8gBqrnoQb8aLy4v0Obo8x HHJQXnz74JQRm1ChlGfi3kW4lnrnvAvOHuyASHkZQVhEDPHPirC7Y7oNKUcqTXEaekkC NUvcGxS+iH5UgENXCOPzxwV8F5+fQqxPPkxPIsRWfBMBWfivqhRgJR2z8LeWJZgMMPVG jKR4Z9tEQu66P3YTLSmudzdrdeiGrMFwNPluikKLArYj/heTRJmOEGOc8WcUb78NW4Nx WcUV8nsbuMBWZ5lVQLDRU2hPlpIJGPIej2RxD6hpLTQs3MGH83KwyTUQiMZKngpo8m2V fNqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CZNrmN8HocOEOLRRpBZUaqZfdBhb6xqwtIau2Dykg8Y=; b=JCtvc59/ke+9wbN1wnW25QSerfMNvwsRXMqvlSiQsE4rkJWYvZLUN+QmQqcVrKC3Tw QacO0Itfd96KrLHqogszIKQqUeCMId7ck5qN7AFJVK/9/WWukqC9r6vM8zRUscPNtWR5 9IeQW1hG/mxznDvQFHWbs40dOACQuXrMGCYX6re7iXitwr6NC09v9EVqMpgNji0jMdZA B5oQPXeLJDFFMzc29FI60+1B2AbrUwXIPelVBfLcmphUrixrYrYeIwSa3wQ0aU5uJq5/ lfcLq7i2Cy7+bKuPEF0SlePKxBgfTwPne8tZnzMjofkxGfHhjw0JdAVbPtPb7T3xrNfL Heyw==
X-Gm-Message-State: AIkVDXJFpT1baX/nM5JPlYiFs0xB4mVggSN6UROHKBYmWod89H5LaFpSNfO4dSxmR2HTN4cx7Ga9rAs4PTHxog==
X-Received: by 10.237.44.161 with SMTP id g30mr56430694qtd.144.1483410820199; Mon, 02 Jan 2017 18:33:40 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.38.233 with HTTP; Mon, 2 Jan 2017 18:33:39 -0800 (PST)
In-Reply-To: <CAMm+Lwiq-pJb3n=_y_o6fbszhvrbeRXTYKCVN6GTv+uOfxSQsw@mail.gmail.com>
References: <CAMm+Lwiq-pJb3n=_y_o6fbszhvrbeRXTYKCVN6GTv+uOfxSQsw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 03 Jan 2017 13:33:39 +1100
Message-ID: <CABkgnnXftPx0T_Xa82DYJujGjB1dBg1Qb4irDobCXHCiATZZRg@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jose/KtlNYT53NUZ0axHzniJDhfql_Q8>
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Using Jose as an encrypted document container.
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jose>, <mailto:jose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jose/>
List-Post: <mailto:jose@ietf.org>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jose>, <mailto:jose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jan 2017 02:33:42 -0000
On 29 December 2016 at 08:33, Phillip Hallam-Baker <phill@hallambaker.com> wrote: > To meet these needs I need to modify Jose to support the following > additional requirements that the RFCs currently don't. > > 1) Single pass processing for encoding and decoding operations. > 1a) Bounded state > 1b) Support streaming, i.e. length not known in advance > > 2) Reduce complexity and number of options. > > 3) Efficient encoding of bodies, i.e. no Base64 overhead. That's a set of requirements that are addressed by draft-ietf-httpbis-encryption-encoding The relationship to JOSE is described in an appendix.
- [jose] Using Jose as an encrypted document contai… Phillip Hallam-Baker
- Re: [jose] Using Jose as an encrypted document co… Sergey Beryozkin
- Re: [jose] Using Jose as an encrypted document co… Phillip Hallam-Baker
- Re: [jose] Using Jose as an encrypted document co… Martin Thomson