IETF Logo Mail Archive

Re: [jose] #69: Section 3.1 - "kty" (Key Type) Parameter

"jose issue tracker" <trac+jose@trac.tools.ietf.org> Tue, 05 November 2013 02:02 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 EDE8F11E814B for <jose@ietfa.amsl.com>; Mon, 4 Nov 2013 18:02:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.594
X-Spam-Level:
X-Spam-Status: No, score=-102.594 tagged_above=-999 required=5 tests=[AWL=0.005, 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 yYe1Qjnbif4y for <jose@ietfa.amsl.com>; Mon, 4 Nov 2013 18:02:03 -0800 (PST)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id AFF5021E810A for <jose@ietf.org>; Mon, 4 Nov 2013 18:02:02 -0800 (PST)
Received: from localhost ([127.0.0.1]:43711 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 1VdVxw-00057c-9Y; Tue, 05 Nov 2013 03:02:00 +0100
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: Tue, 05 Nov 2013 02:02:00 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/69#comment:1
Message-ID: <076.b8f30db07b0caad74c660411e6b84a1d@trac.tools.ietf.org>
References: <061.37657b5db32452128b768634914cde03@trac.tools.ietf.org>
X-Trac-Ticket-ID: 69
In-Reply-To: <061.37657b5db32452128b768634914cde03@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: <20131105020202.AFF5021E810A@ietfa.amsl.com>
Resent-Date: Mon, 04 Nov 2013 18:02:02 -0800
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #69: Section 3.1 - "kty" (Key Type) 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: Tue, 05 Nov 2013 02:02:04 -0000

#69: Section 3.1 - "kty" (Key Type) Parameter

Description changed by ietf@augustcellars.com:

Old description:

> A. Para #1 - Remove reference on the registry that is not where the
> registry is.
>
> B. Para #1 - s/use of this member is REQUIRED./The 'kty' member MUST be
> present in a JWK./
>    This is a more affirmative statement of what needs to be done by the
> user and makes it easier to write the test cases at a later point.
>
> C. Para #2 - Potentially remove the 'where is the initial registry'
> comment
>
> D. Para #3 - Clarification is needed on what the additional members used
> with "kty" values are.
>
> E. Need to discuss that some kty values will require or recommend that
> specific members be present in the JWK.  Also need to discuss how an
> implementation is supposed to know this (i.e. is it part of the registry
> entry?).

New description:

 A. Para #1 - Remove reference on the registry that is not where the
 registry is.

 * WON'T FIX - My personal peeve

 B. Para #1 - s/use of this member is REQUIRED./The 'kty' member MUST be
 present in a JWK./
    This is a more affirmative statement of what needs to be done by the
 user and makes it easier to write the test cases at a later point.

 C. Para #2 - Potentially remove the 'where is the initial registry'
 comment

 * WON'T FIX

 D. Para #3 - Clarification is needed on what the additional members used
 with "kty" values are.

 E. Need to discuss that some kty values will require or recommend that
 specific members be present in the JWK.  Also need to discuss how an
 implementation is supposed to know this (i.e. is it part of the registry
 entry?).

--

-- 
-------------------------+-------------------------------------------------
 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/69#comment:1>
jose <http://tools.ietf.org/jose/>

v2.23.0 | Report a Bug | By Email