IETF Logo Mail Archive

Re: [jose] Feedback request on jose tracker issue #15: Should at least on key indicator be mandatory

Mike Jones <Michael.Jones@microsoft.com> Mon, 15 April 2013 15:26 UTC

Return-Path: <Michael.Jones@microsoft.com>
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 483F021F93B1 for <jose@ietfa.amsl.com>; Mon, 15 Apr 2013 08:26:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 ZyPY8Fnyx9Dj for <jose@ietfa.amsl.com>; Mon, 15 Apr 2013 08:26:21 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0237.outbound.protection.outlook.com [207.46.163.237]) by ietfa.amsl.com (Postfix) with ESMTP id C2A8021F8E6A for <jose@ietf.org>; Mon, 15 Apr 2013 08:26:21 -0700 (PDT)
Received: from BY2FFO11FD002.protection.gbl (10.1.15.202) by BY2FFO11HUB013.protection.gbl (10.1.14.85) with Microsoft SMTP Server (TLS) id 15.0.664.0; Mon, 15 Apr 2013 15:26:51 +0000
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD002.mail.protection.outlook.com (10.1.14.124) with Microsoft SMTP Server (TLS) id 15.0.675.0 via Frontend Transport; Mon, 15 Apr 2013 15:26:20 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.224]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.02.0318.003; Mon, 15 Apr 2013 15:24:43 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: "odonoghue@isoc.org" <odonoghue@isoc.org>
Thread-Topic: [jose] Feedback request on jose tracker issue #15: Should at least on key indicator be mandatory
Thread-Index: AQHONxCooSd2LAEBTkqzIVwx4JWauZjSDFgAgANa7oCAAgFzQA==
Date: Mon, 15 Apr 2013 15:24:41 +0000
Message-ID: <4E1F6AAD24975D4BA5B168042967394367641294@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <51674E63.3050809@isoc.org> <4E1F6AAD24975D4BA5B168042967394367615F37@TK5EX14MBXC283.redmond.corp.microsoft.com> <AB5C7306-21DE-40FA-BBC6-114BCD3DADFD@adm.umu.se>
In-Reply-To: <AB5C7306-21DE-40FA-BBC6-114BCD3DADFD@adm.umu.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.35]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(5383001)(377454001)(189002)(13464002)(199002)(63696002)(54316002)(65816001)(47976001)(50466001)(31966008)(81542001)(20776003)(69226001)(56816002)(81342001)(5343635001)(5343655001)(47736001)(50986001)(46406003)(56776001)(66066001)(76482001)(47776003)(79102001)(49866001)(55846006)(77982001)(16406001)(80022001)(4396001)(53806001)(59766001)(33656001)(46102001)(51856001)(74662001)(47446002)(54356001)(15202345002)(74502001)(23726002)(44976003); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB013; H:TK5EX14MLTC102.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en;
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 0817737FD1
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Feedback request on jose tracker issue #15: Should at least on key indicator be mandatory
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 15 Apr 2013 15:26:22 -0000

1.  Yes - Use cases where key information is exchanged by means other than the JWS and JWE headers ARE important.

-----Original Message-----
From: Roland Hedberg [mailto:roland.hedberg@adm.umu.se] 
Sent: Sunday, April 14, 2013 1:33 AM
To: odonoghue@isoc.org
Cc: jose@ietf.org; Mike Jones
Subject: Re: [jose] Feedback request on jose tracker issue #15: Should at least on key indicator be mandatory

I support 1 as defined by Mike.

12 apr 2013 kl. 07:25 skrev Mike Jones <Michael.Jones@microsoft.com>:

> 1.  Yes - Use cases where key information is exchanged by means other than the JWS and JWE headers ARE important

-- Roland

From: Mike Jones 
Sent: Thursday, April 11, 2013 10:25 PM
To: 'odonoghue@isoc.org'; jose@ietf.org
Subject: RE: [jose] Feedback request on jose tracker issue #15: Should at least on key indicator be mandatory

Reading this question, I believe that there's a possibility for the question to be misinterpreted, since the sense of the question in the subject is opposite of the sense of the question in the body.  I believe that the intent of 1 and 2 were as follows:

1.  Yes - Use cases where key information is exchanged by means other than the JWS and JWE headers ARE important.
2.  No - Use cases where key information is exchanged by means other than the JWS and JWE headers ARE NOT important.

Maybe people could reply with 1 and 2 as above, so that their answers to the question of whether these use cases are important are not are unambiguous.

                                                            -- Mike

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Karen O'Donoghue
Sent: Thursday, April 11, 2013 5:00 PM
To: jose@ietf.org
Subject: [jose] Feedback request on jose tracker issue #15: Should at least on key indicator be mandatory

Issue #15 http://trac.tools.ietf.org/wg/jose/trac/ticket/15. suggests requiring that a key indicator, such as a "kid" field, be required in all JWS and JWE headers. Are use cases where key information is exchanged by means other than the JWS or JWE headers important? 
Which of these best describes your preferences on this issue?
1.  Yes.
2.   No. 
0.  I need more information to decide.
 
Your reply is requested by Friday, April 19th (or earlier).

v2.23.0 | Report a Bug | By Email