Re: [jose] #2: No key management for MAC

"jose issue tracker" <trac+jose@trac.tools.ietf.org> Mon, 25 February 2013 18:56 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 0BE9421F937C for <jose@ietfa.amsl.com>; Mon, 25 Feb 2013 10:56:54 -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 hPMJrcCNbx1j for <jose@ietfa.amsl.com>; Mon, 25 Feb 2013 10:56:53 -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 56FA221F9374 for <jose@ietf.org>; Mon, 25 Feb 2013 10:56:38 -0800 (PST)
Received: from localhost ([127.0.0.1]:59463 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 1UA3Dv-0001tU-Hj; Mon, 25 Feb 2013 19:56:27 +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-signature@tools.ietf.org, sakimura@gmail.com
X-Trac-Project: jose
Date: Mon, 25 Feb 2013 18:56:27 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/2#comment:1
Message-ID: <069.43038b5c16720bcf6399d1df980ae80b@trac.tools.ietf.org>
References: <054.c651e93bb72d1b02087aa116318b8d94@trac.tools.ietf.org>
X-Trac-Ticket-ID: 2
In-Reply-To: <054.c651e93bb72d1b02087aa116318b8d94@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-signature@tools.ietf.org, sakimura@gmail.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, n-sakimura@nri.co.jp, ve7jtb@ve7jtb.com
Resent-Message-Id: <20130225185643.56FA221F9374@ietfa.amsl.com>
Resent-Date: Mon, 25 Feb 2013 10:56:38 -0800
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #2: No key management for MAC
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: Mon, 25 Feb 2013 18:56:54 -0000

#2: No key management for MAC


Comment (by sakimura@gmail.com):

 I believe this is the same issue as http://www.ietf.org/mail-
 archive/web/jose/current/msg01220.html which is closed.
 If it is not, pleae clarify.

 Here is the copied text from the mail:

 ----

 [jose] CLOSED: Add other than pre-shared MAC key

 From: Karen O'Donoghue <odonoghue at isoc.org>
 To: jose at ietf.org
 Date: Wed, 24 Oct 2012 06:35:37 -0400
 In-reply-to: <4E1F6AAD24975D4BA5B168042967394366877989 at
 TK5EX14MBXC285.redmond.corp.microsoft.com>
 References: <4E1F6AAD24975D4BA5B168042967394366877989 at
 TK5EX14MBXC285.redmond.corp.microsoft.com>
 List-id: Javascript Object Signing and Encryption <jose.ietf.org>
 Folks,

 The results of this poll were:
 4 YES - We should add the ability to have a randomly generated MAC key
 protected by a different key
 13 NO - We should not add the ability to have a randomly generated MAC key
 protected by a different key
 4 DISCUSS - More discussion is needed

 Based upon these results, I am making a consensus call that we should not
 add the ability to
 have a randomly generated MAC key protected by a different key.  This
 issue is now closed.

 Thanks to all who participated in this poll.

 Karen O'Donoghue (writing as working group co-chair)

 -----Original Message-----
 From: jose-bounces at ietf.org [mailto:jose-bounces at ietf.org] On Behalf
 Of Jim Schaad
 Sent: Friday, August 17, 2012 12:07 AM
 To: jose at ietf.org
 Subject: [jose] POLL: Add other than pre-shared MAC key

 <CHAIR>

 If you voted at the face-2-face please do not vote again.  If you want to
 provide comments please change the title from POLL to DISCUSS.

 Should we add the ability to have a randomly generated MAC key protected
 by a different key?  The other key could be either a pre-shared symmetric
 key or a public key.



 Room vote:  3 yes, 5 no, 3 discuss


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

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

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/2#comment:1>
jose <http://tools.ietf.org/jose/>