Re: [jose] #72: Section 3.3 - "alg" (Algorithm) Parameter
"jose issue tracker" <trac+jose@trac.tools.ietf.org> Thu, 10 October 2013 06:48 UTC
Return-Path: <trac+jose@trac.tools.ietf.org>
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 6CD1821E80DB for <jose@ietfa.amsl.com>; Wed, 9 Oct 2013 23:48:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 kWAqIOtFPck8 for <jose@ietfa.amsl.com>; Wed, 9 Oct 2013 23:48:20 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 9DB2D11E8132 for <jose@ietf.org>; Wed, 9 Oct 2013 23:48:19 -0700 (PDT)
Received: from localhost ([127.0.0.1]:43210 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1VUA2j-0002mP-CO; Thu, 10 Oct 2013 08:48:17 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: jose issue tracker <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-key@tools.ietf.org, ietf@augustcellars.com
X-Trac-Project: jose
Date: Thu, 10 Oct 2013 06:48:17 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/72#comment:1
Message-ID: <076.0634e60a623276e7a78d70955dc9fdcb@trac.tools.ietf.org>
References: <061.0bb69719dcf9135e026a439b92bb09f3@trac.tools.ietf.org>
X-Trac-Ticket-ID: 72
In-Reply-To: <061.0bb69719dcf9135e026a439b92bb09f3@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-key@tools.ietf.org, ietf@augustcellars.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: mbj@microsoft.com
Resent-Message-Id: <20131010064819.9DB2D11E8132@ietfa.amsl.com>
Resent-Date: Wed, 09 Oct 2013 23:48:19 -0700
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #72: Section 3.3 - "alg" (Algorithm) Parameter
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 10 Oct 2013 06:48:21 -0000
#72: Section 3.3 - "alg" (Algorithm) Parameter Description changed by ietf@augustcellars.com: Old description: > A. This should not be tied to specific fields in the JWS and JWE > structures. If I define a new item then I want it to apply to that item > as well. > > B. Registry is not in JWA - it is on iana.org > > C. Use of member is OPTIONAL does not convey sufficient information. For > whom is it optional? > > D. What happens if use is absent is not covered in the document. > > E. John Bradley made a big deal at the Berlin meeting about the fact that > this needs to be a single value rather than a multi-value field. The > reasoning behind this was that allowing for multiple values was an evil > thing. This would imply that this is not an optional field but is, at a > minimum a SHOULD field with heavy language about when one would not > specify a value. all uses (absent) is worse than some usages (multi) is > worse than one usage (single). > > F. Need a statement if the alg is not a known algorithm by the consumer > of the JWK > > G. Need a statement if there are other members that must be included if > an alg is specfied > > H. Need a statement if there are members missing that must be included > about what to do with this JWK. New description: A. This should not be tied to specific fields in the JWS and JWE structures. If I define a new item then I want it to apply to that item as well. * FIXXED B. Registry is not in JWA - it is on iana.org C. Use of member is OPTIONAL does not convey sufficient information. For whom is it optional? * FIXED D. What happens if use is absent is not covered in the document. * WON'T FIX - probably implicit as any can be used. E. John Bradley made a big deal at the Berlin meeting about the fact that this needs to be a single value rather than a multi-value field. The reasoning behind this was that allowing for multiple values was an evil thing. This would imply that this is not an optional field but is, at a minimum a SHOULD field with heavy language about when one would not specify a value. all uses (absent) is worse than some usages (multi) is worse than one usage (single). F. Need a statement if the alg is not a known algorithm by the consumer of the JWK G. Need a statement if there are other members that must be included if an alg is specfied H. Need a statement if there are members missing that must be included about what to do with this JWK. -- -- -------------------------+------------------------------------------------- Reporter: | Owner: draft-ietf-jose-json-web- ietf@augustcellars.com | key@tools.ietf.org Type: defect | Status: new Priority: major | Milestone: Component: json-web- | Version: key | Resolution: Severity: - | Keywords: | -------------------------+------------------------------------------------- Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/72#comment:1> jose <http://tools.ietf.org/jose/>
- [jose] #72: Section 3.3 - "alg" (Algorithm) Param… jose issue tracker
- Re: [jose] #72: Section 3.3 - "alg" (Algorithm) P… jose issue tracker
- Re: [jose] #72: Section 3.3 - "alg" (Algorithm) P… jose issue tracker
- Re: [jose] #72: Section 3.3 - "alg" (Algorithm) P… jose issue tracker