IETF Logo Mail Archive

[jose] #5: Unclear instructions for key management

"jose issue tracker" <trac+jose@trac.tools.ietf.org> Fri, 18 January 2013 23:24 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 C4B5921F8698 for <jose@ietfa.amsl.com>; Fri, 18 Jan 2013 15:24:04 -0800 (PST)
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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ct53zZiEXYMx for <jose@ietfa.amsl.com>; Fri, 18 Jan 2013 15:24:04 -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 3277421F869F for <jose@ietf.org>; Fri, 18 Jan 2013 15:24:04 -0800 (PST)
Received: from localhost ([127.0.0.1]:39104 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 1TwLHx-0007RG-KZ; Sat, 19 Jan 2013 00:23:57 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
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-encryption@tools.ietf.org, rbarnes@bbn.com
X-Trac-Project: jose
Date: Fri, 18 Jan 2013 23:23:57 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/5
Message-ID: <054.f240878e1815afe10f9256d1163853c9@trac.tools.ietf.org>
X-Trac-Ticket-ID: 5
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-encryption@tools.ietf.org, rbarnes@bbn.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: ekr@rtfm.com, jhildebr@cisco.com, mbj@microsoft.com
Resent-Message-Id: <20130118232404.3277421F869F@ietfa.amsl.com>
Resent-Date: Fri, 18 Jan 2013 15:24:04 -0800
Resent-From: trac+jose@trac.tools.ietf.org
X-Mailman-Approved-At: Fri, 18 Jan 2013 15:43:29 -0800
Cc: jose@ietf.org
Subject: [jose] #5: Unclear instructions for key management
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: Fri, 18 Jan 2013 23:24:04 -0000

#5: Unclear instructions for key management

 The document uses the phrases “When key agreement is employed...” and
 “When key wrapping, key encryption, or key agreement with wrapping are
 employed...” without telling the recipient how to tell which case he’s in.
 Apparently this should be based on the "alg" parameter, but nowhere is it
 specified which "alg" values fall into which bin.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |      Owner:  draft-ietf-jose-json-web-
  rbarnes@bbn.com        |  encryption@tools.ietf.org
     Type:  defect       |     Status:  new
 Priority:  major        |  Milestone:
Component:  json-web-    |    Version:
  encryption             |   Keywords:
 Severity:  Active WG    |
  Document               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/5>
jose <http://tools.ietf.org/jose/>

v2.23.0 | Report a Bug | By Email