[jose] JOSE/JSON Charter Issues

Anders Rundgren <anders.rundgren.net@gmail.com> Sun, 01 November 2015 08:27 UTC

Return-Path: <anders.rundgren.net@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF5C41B72BA for <jose@ietfa.amsl.com>; Sun, 1 Nov 2015 01:27:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 6hd_-mQ98Teb for <jose@ietfa.amsl.com>; Sun, 1 Nov 2015 01:27:02 -0700 (PDT)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 5A90E1B72B9 for <jose@ietf.org>; Sun, 1 Nov 2015 01:27:02 -0700 (PDT)
Received: by wmeg8 with SMTP id g8so37894783wme.0 for <jose@ietf.org>; Sun, 01 Nov 2015 01:27:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=2GDoAppDseDucrqagZ6a7yiX79UXmvJODPSLafJznm4=; b=LKJrkGn8cnyugx+1tMk+4ofGgRypB1p9MNkXuv+ltqgV3/djuyiS/aFd9zFuCPIhRl VNGBTjPSZii2h9RSzJVnagQSfpdf71Mi5B6XEPs3CSbtNzy94mimkX0vYgylce41wHtp UsewHD0z28NIB3fy/BMTWdLFZgFFRFwRwqD/djAGqo1fgeQ7NcGFPsFXqK2yRJbfs4TW SvWG9qodoufu1N6Ix9PAlVrsSe2CqLLvHKXDVgPB9AxKNQ2826YbiMN6QyAy6eAitCdA QKEoFIWG7uL07dm4wdCjIGB+30mnWdn2DcpMM+129cHCLFrDiEaDMdhSU9+nbJiV+Ukx pVKw==
X-Received: by 10.28.216.196 with SMTP id p187mr7604034wmg.14.1446366421030; Sun, 01 Nov 2015 01:27:01 -0700 (PDT)
Received: from [192.168.1.79] (148.198.130.77.rev.sfr.net. [77.130.198.148]) by smtp.googlemail.com with ESMTPSA id cr5sm15892203wjb.16.2015.11.01.01.26.59 for <jose@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 01 Nov 2015 01:26:59 -0700 (PDT)
To: "jose@ietf.org" <jose@ietf.org>
References: <56313082.1090809@gmail.com> <CABzCy2CB58sQVzxREvmLTiVqZAHJ9vjYM8QZqNrtG_QfY2akPA@mail.gmail.com> <5635A4B5.7040806@gmail.com> <CABzCy2DQTKr6tiJ+pdMg5easxEuZcf2iaOsRuigb3u36MYN+Tw@mail.gmail.com> <5635AA88.9050908@gmail.com>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
Message-ID: <5635CCCA.8030405@gmail.com>
Date: Sun, 01 Nov 2015 09:26:50 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <5635AA88.9050908@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/jose/AQ1qu-cxsciLbrwX0Kx5bpoKt8Q>
Subject: [jose] JOSE/JSON Charter Issues
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 01 Nov 2015 08:27:04 -0000

   "JavaScript Object Notation (JSON) is a text format for the serialization
    of structured data described in RFC 4627. The JSON format is often used
    for serializing and transmitting structured data over a network
    connection. With the increased usage of JSON in protocols in the IETF and
    elsewhere, there is now a desire to offer security services, which use
    encryption, digital signatures, message authentication codes (MACs)
    algorithms, that carry their data in JSON format"

AFAICT, JWS has about the same relation to data in JSON or JavaScript format
as most other signature formats including CMS have; that is, none.  What JWS
does though is getting away from ASN.1 although this is also a bit of a
stretch since some constructs still rely on ASN.1 like "x5c" headers.

Regarding JavaScript ("The mother of JSON"), it has recently been upgraded
w.r.t. serialization which means the majority of JSON tools do not necessarily
interoperate well with JavaScript as implemented in browsers.

IMO, it is a bit premature closing the JOSE and JSON WGs.

Anders