IETF Logo Mail Archive

Re: [jose] updated draft charter text incorporating AD's comments

Mike Jones <Michael.Jones@microsoft.com> Fri, 05 April 2013 15:19 UTC

Return-Path: <Michael.Jones@microsoft.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 CA9F021F9783 for <jose@ietfa.amsl.com>; Fri, 5 Apr 2013 08:19:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Level:
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083, 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 juwtsMd3nNFX for <jose@ietfa.amsl.com>; Fri, 5 Apr 2013 08:19:04 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0209.outbound.protection.outlook.com [207.46.163.209]) by ietfa.amsl.com (Postfix) with ESMTP id C173521F9724 for <jose@ietf.org>; Fri, 5 Apr 2013 08:19:01 -0700 (PDT)
Received: from BL2FFO11FD001.protection.gbl (10.173.161.202) by BL2FFO11HUB035.protection.gbl (10.173.161.115) with Microsoft SMTP Server (TLS) id 15.0.664.0; Fri, 5 Apr 2013 15:10:05 +0000
Received: from TK5EX14HUBC104.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD001.mail.protection.outlook.com (10.173.160.101) with Microsoft SMTP Server (TLS) id 15.0.664.0 via Frontend Transport; Fri, 5 Apr 2013 15:10:04 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.224]) by TK5EX14HUBC104.redmond.corp.microsoft.com ([157.54.80.25]) with mapi id 14.02.0318.003; Fri, 5 Apr 2013 15:10:04 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Barry Leiba <barryleiba@computer.org>
Thread-Topic: [jose] updated draft charter text incorporating AD's comments
Thread-Index: AQHOHbsFzhPDcbJYm0e4TO3t5oFBJZjHttqAgAAMlKCAABdMgIAAB+EQ
Date: Fri, 05 Apr 2013 15:10:02 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943675B7AF1@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <513CCD31.8050408@isoc.org> <515EC38F.2060703@ieca.com> <4E1F6AAD24975D4BA5B1680429673943675B77BC@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAC4RtVBw6Nqmcd5STHuq+LJJLP16FpKzHu+ONUd2HcxYu-Zj-w@mail.gmail.com>
In-Reply-To: <CAC4RtVBw6Nqmcd5STHuq+LJJLP16FpKzHu+ONUd2HcxYu-Zj-w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.36]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(164054002)(13464002)(51704002)(377454001)(47976001)(54316002)(81342001)(31966008)(20776003)(50986001)(55846006)(74662001)(47776003)(59766001)(33656001)(23726001)(5343655001)(69226001)(77982001)(51856001)(56816002)(65816001)(53806001)(81542001)(79102001)(15202345001)(49866001)(46406002)(54356001)(74502001)(46102001)(44976002)(80022001)(50466001)(76482001)(66066001)(47446002)(56776001)(47736001)(16406001)(4396001)(63696002); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB035; H:TK5EX14HUBC104.redmond.corp.microsoft.com; LANG:en;
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 08076ABC99
Cc: Sean Turner <turners@ieca.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] updated draft charter text incorporating AD's comments
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, 05 Apr 2013 15:19:05 -0000

Thanks Barry.

How about "representing integrity-protected data using JSON-based data structures" and "representing encrypted data using JSON-based data structures"?  That would read better than the original and still not be able to be misconstrued to say that what the working group has produced doesn't meet the charter goals.

				Thanks,
				-- Mike

-----Original Message-----
From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Barry Leiba
Sent: Friday, April 05, 2013 7:37 AM
To: Mike Jones
Cc: Sean Turner; jose@ietf.org
Subject: Re: [jose] updated draft charter text incorporating AD's comments

> For that reason, I believe we would be FAR better off to leave the 
> first two charter items exactly as they are at 
> http://datatracker.ietf.org/wg/jose/charter/ than to accept the new wording.
> The current wording is:
>
> 1) A Standards Track document specifying how to apply JSON-structured  
> integrity protection to data, including (but not limited to) JSON data  
> structures. "Integrity protection" includes public-key digital  
> signatures as well as symmetric-key MACs.
>
> 2) A Standards Track document specifying how to apply a 
> JSON-structured  encryption to data, including (but not limited to) JSON data structures.

The problem is that I do not understand what you mean by "JSON-structured integrity protection" and "JSON-structured encryption".  Sean's suggested wording is intended to say this in an understandable way; if it's not correct, please try to come up with an alternative.  The existing text doesn't work, because I don't understand how to apply the modifier "JSON-structured" to the noun "encryption" and get anything sensible out of it.  What does it mean for *encryption* to be "JSON-structured"?

> So yes, I strongly object to the new wording, as I don't want to open 
> the door for the current representations to be rejected on charter 
> grounds later.  If it helps, you can reassure objectors that we ARE 
> producing pure JSON representations too, but that they're not the only 
> JSON-based representations for integrity protected and encrypted content.

To be clear: what you're producing is not the issue.  It's an issue of the wording in the charter.

Barry
_______________________________________________
jose mailing list
jose@ietf.org
https://www.ietf.org/mailman/listinfo/jose

v2.23.0 | Report a Bug | By Email