Re: [jose] A modest proposal for JSON-izing JW*

"Matt Miller (mamille2)" <mamille2@cisco.com> Wed, 06 February 2013 19:38 UTC

Return-Path: <mamille2@cisco.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 8D29721F8A4A for <jose@ietfa.amsl.com>; Wed, 6 Feb 2013 11:38:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.432
X-Spam-Level:
X-Spam-Status: No, score=-10.432 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eFK+-9YT5KD2 for <jose@ietfa.amsl.com>; Wed, 6 Feb 2013 11:38:45 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id B7DDF21F8A42 for <jose@ietf.org>; Wed, 6 Feb 2013 11:38:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5119; q=dns/txt; s=iport; t=1360179525; x=1361389125; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=kWG9eCYvX0VIHHW0NzCmzKUzHoeZYtraxtmAFJ9QWhs=; b=XDspE13Gi3g+fmYrwxzcXvhRjvQDwW8EUBeiuvchA6QMHW6wrQNjVIZ1 Ea8/QPumfQVTTf/8988QSfU+7JoQplG0YXNJBOIMg8ndE//VKg5/Sv0zJ Ti3FWCxZGWSrvsCQKY8cURShUSqgCMKw8RGavkUGGF1VJWMkfR119tpBK Y=;
X-Files: smime.p7s : 2283
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAJOwElGtJXG+/2dsb2JhbABFwEwWc4IfAQEBAwEBAQFrCwULAgEIDhQkAiULJQIEDgUIBod9Bgy8PQSQeGEDjxOBJZY7gn6CJA
X-IronPort-AV: E=Sophos; i="4.84,617,1355097600"; d="p7s'?scan'208"; a="174124422"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-2.cisco.com with ESMTP; 06 Feb 2013 19:38:45 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r16Jcjic022005 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 6 Feb 2013 19:38:45 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.138]) by xhc-rcd-x04.cisco.com ([173.37.183.78]) with mapi id 14.02.0318.004; Wed, 6 Feb 2013 13:38:45 -0600
From: "Matt Miller (mamille2)" <mamille2@cisco.com>
To: Richard Barnes <rlb@ipv.sx>
Thread-Topic: [jose] A modest proposal for JSON-izing JW*
Thread-Index: AQHOBKAyWv2CiOmrVUCizdZ2D4G3sphtnnoA
Date: Wed, 6 Feb 2013 19:38:44 +0000
Message-ID: <BF7E36B9C495A6468E8EC573603ED94115110EFB@xmb-aln-x11.cisco.com>
References: <CAL02cgQt8cj26KunfDvez+TBKgpvsdfN6Oe1XFTbkyWuSxPA9Q@mail.gmail.com>
In-Reply-To: <CAL02cgQt8cj26KunfDvez+TBKgpvsdfN6Oe1XFTbkyWuSxPA9Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.129.24.55]
Content-Type: multipart/signed; boundary="Apple-Mail=_F53F8035-A47F-4423-8620-CD26C2E8FA50"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: "<jose@ietf.org>" <jose@ietf.org>
Subject: Re: [jose] A modest proposal for JSON-izing JW*
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 06 Feb 2013 19:38:46 -0000

+1


- m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.

On Feb 6, 2013, at 12:28 PM, Richard Barnes <rlb@ipv.sx> wrote:

> Dear JOSE,
> 
> tl;dr: Let's please add a simple JSON encoding to the base JW* specs.
> 
> I've been complaining for a while that the JW* documents aren't JSON, and
> that the JSON serialization documents are too complex (because of the
> integrity check issues).  So I thought it was about time that I made an
> actual proposal for encoding the base JOSE object as JSON objects.  The
> approach would be essentially the same as in the JSON serialization
> documents, except with a focus on single objects.
> 
> JWE and JWS objects currently have the following form
> 
> jws = header.data.signature
> jwe = header.key.iv.ciphertext.mac
> 
> The JSON encoding of a JWE/JWS would just take each of these Base64-encoded
> pieces and assign them a name in a JSON structure.
> 
> jws = {
>    "header": header,
>    "data": data,
>    "signature": signature
> }
> 
> jwe = {
>    "header": header,
>    "key": key,
>    "iv": iv,
>    "data": ciphertext,
>    "mac": mac
> }
> 
> It seems to me that these encodings are simple enough that they could be
> handled in a short section, in parallel to what I would call the "text
> serialization" in the current documents.  So I would like to propose that
> they be added to the base JWE and JWS documents.
> 
> Thanks,
> --Richard
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose