Re: [jose] Suggestion for new term: JSON Web Object (JWO) or JSON Web Message (JWM)

"Vladimir Dzhuvinov / NimbusDS" <vladimir@nimbusds.com> Fri, 01 June 2012 11:45 UTC

Return-Path: <vladimir@nimbusds.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 CE63821F8659 for <jose@ietfa.amsl.com>; Fri, 1 Jun 2012 04:45:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ehp2GnA1wORi for <jose@ietfa.amsl.com>; Fri, 1 Jun 2012 04:45:33 -0700 (PDT)
Received: from n1plwbeout07-02.prod.ams1.secureserver.net (n1plsmtp07-02-02.prod.ams1.secureserver.net [188.121.52.107]) by ietfa.amsl.com (Postfix) with SMTP id 853B421F8501 for <jose@ietf.org>; Fri, 1 Jun 2012 04:45:32 -0700 (PDT)
Received: (qmail 26427 invoked from network); 1 Jun 2012 11:45:29 -0000
Received: from unknown (HELO localhost) (188.121.52.245) by n1plwbeout07-02.prod.ams1.secureserver.net with SMTP; 1 Jun 2012 11:45:29 -0000
Received: (qmail 25212 invoked by uid 99); 1 Jun 2012 11:45:28 -0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Originating-IP: 46.10.79.251
User-Agent: Workspace Webmail 5.6.18
Message-Id: <20120601044527.cc40c4f3d92d2001859047cd8cabb9ab.306925200a.wbe@email07.europe.secureserver.net>
From: Vladimir Dzhuvinov / NimbusDS <vladimir@nimbusds.com>
To: jose@ietf.org
Date: Fri, 01 Jun 2012 04:45:27 -0700
Mime-Version: 1.0
Subject: Re: [jose] Suggestion for new term: JSON Web Object (JWO) or JSON Web Message (JWM)
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: Fri, 01 Jun 2012 11:45:34 -0000

> > After a bit of brain storming two favourites emerged:
> > 
> > JSON Web Object (JWO)
> > 
> > and
> > 
> > JSON Web Message (JWM).
> 
> 
> JWO and JWM are both missing the security angle, which is the primary reason for JOSE.
> 
> How about "JWsec", and I would call the spec "JSON Web Message Security Format".

Sounds good. I need to digest it a bit though :)

To me an ideal name is one that is meaningful, concise and can result in
a reasonably short acronym or abbreviation.


> I don't think we will need separate acronyms for specific modes once we have a nickname for the top-level structure. For instance, say "signed JWsec" and "encrypted JWsec", instead of JWS and JWE.

Yes, once we have a common name/acronym for these messages, there would
be less of a need to have the current set of acronyms (JWS, JWE, JWA,
JWK).

However, when we put "signed" etc in front of "JWsec" the phrase becomes
a bit awkward. An acronym that still makes sense when unrolled with an
adjective in front of it would fit better.

To illustrate - "signed JWsec" -> "signed JSON Web Message Security
Format".

How about having JWsec refer to the format and JWM refer to the
resulting messages?

We would then have:

* JSON Web Message (JWM) - A message that follows the JSON Web Message
Security Format (JWsec).

* signed JWM - signed JSON Web Message

* encrypted JWM - encrypted JSON Web Message

* plain/unprotected JWM - ...

* JWM key - ...

* JWM algorithm - ...


What do you guys think?


Vladimir