Re: [jose] Barry Leiba's No Objection on draft-ietf-jose-json-web-encryption-32: (with COMMENT)

"Jim Schaad" <ietf@augustcellars.com> Sun, 19 October 2014 22:22 UTC

Return-Path: <ietf@augustcellars.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 C8CAE1A0276; Sun, 19 Oct 2014 15:22:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 zVzux06oz9K8; Sun, 19 Oct 2014 15:22:37 -0700 (PDT)
Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D0E01A026E; Sun, 19 Oct 2014 15:22:36 -0700 (PDT)
Received: from Philemon (winery.augustcellars.com [206.212.239.129]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp2.pacifier.net (Postfix) with ESMTPSA id 09B6B2C9F3; Sun, 19 Oct 2014 15:22:35 -0700 (PDT)
From: Jim Schaad <ietf@augustcellars.com>
To: 'Mike Jones' <Michael.Jones@microsoft.com>, 'Barry Leiba' <barryleiba@computer.org>
References: <4E1F6AAD24975D4BA5B16804296739439BB0D0F1@TK5EX14MBXC286.redmond.corp.microsoft.com> <009a01cfeb00$cbe93760$63bba620$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739439BB18D9B@TK5EX14MBXC286.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739439BB18D9B@TK5EX14MBXC286.redmond.corp.microsoft.com>
Date: Sun, 19 Oct 2014 15:19:58 -0700
Message-ID: <014f01cfebea$d1af6080$750e2180$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHRbn4WKO0CODvu7FfLW3wKJeStsQHsOV0/A27swDScCh9QAA==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/jose/ttXqFdvCAUUgoZ8N1hpOIuSa1rA
Cc: draft-ietf-jose-json-web-encryption@tools.ietf.org, jose-chairs@tools.ietf.org, 'The IESG' <iesg@ietf.org>, jose@ietf.org
Subject: Re: [jose] Barry Leiba's No Objection on draft-ietf-jose-json-web-encryption-32: (with COMMENT)
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: <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: Sun, 19 Oct 2014 22:22:40 -0000


> -----Original Message-----
> From: Mike Jones [mailto:Michael.Jones@microsoft.com]
> Sent: Saturday, October 18, 2014 3:28 PM
> To: Jim Schaad; 'Barry Leiba'
> Cc: draft-ietf-jose-json-web-encryption@tools.ietf.org; jose-
> chairs@tools.ietf.org; 'The IESG'; jose@ietf.org
> Subject: RE: [jose] Barry Leiba's No Objection on
draft-ietf-jose-json-web-
> encryption-32: (with COMMENT)
> 
> > > The intent is b.  I propose that the words "This member MUST be
> > > present, even if the array elements contain only the empty JSON
> > > object "{}"" be changed to "This member MUST be present with exactly
> > > one array element per recipient, even if some or all of the array
> > > element values are the empty JSON object {}".  Would that be clearer?
> >
> > I think that would have helped me.  Again, another small point.
> >
> > OK
> >
> > [JLS]  I think that this language may not be correct.  Did you mean to
imply
> that the following is a legal value for the "recipients" property. 
"[{},{}]"
> > It appears that there can be any number of empty array elements can be
> present.
> >
> > If this is not the case I will try and look at proposing some text.
> 
> The full text about the recipients array at
http://tools.ietf.org/html/draft-
> ietf-jose-json-web-encryption-35#section-7.2 is:
> 
>    recipients
>       The "recipients" member value MUST be an array of JSON objects.
>       Each object contains information specific to a single recipient.
>       This member MUST be present with exactly one array element per
>       recipient, even if some or all of the array element values are the
>       empty JSON object "{}" (which can happen when all Header Parameter
>       values are shared between all recipients and when no encrypted key
>       is used, such as when doing Direct Encryption).
> 
> So it's not that any number of empty array elements can be present.  It's
that
> exactly one JSON object must be present in the array per recipient, some
of
> which may be empty because of the parameter choices made.

This does not answer my question.  Is it a legal value?

Jim

> 
> 				-- Mike