IETF Logo Mail Archive

Re: [jose] Key Identifier

Mike Jones <Michael.Jones@microsoft.com> Wed, 28 November 2012 06:01 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 F1CA921F8788 for <jose@ietfa.amsl.com>; Tue, 27 Nov 2012 22:01:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.099
X-Spam-Level:
X-Spam-Status: No, score=-4.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 vYaTbL-2bl37 for <jose@ietfa.amsl.com>; Tue, 27 Nov 2012 22:01:21 -0800 (PST)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe004.messaging.microsoft.com [213.199.154.142]) by ietfa.amsl.com (Postfix) with ESMTP id 93EC621F8763 for <jose@ietf.org>; Tue, 27 Nov 2012 22:01:20 -0800 (PST)
Received: from mail102-db3-R.bigfish.com (10.3.81.234) by DB3EHSOBE009.bigfish.com (10.3.84.29) with Microsoft SMTP Server id 14.1.225.23; Wed, 28 Nov 2012 06:01:19 +0000
Received: from mail102-db3 (localhost [127.0.0.1]) by mail102-db3-R.bigfish.com (Postfix) with ESMTP id 6979120107; Wed, 28 Nov 2012 06:01:19 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:131.107.125.8; KIP:(null); UIP:(null); IPV:NLI; H:TK5EX14HUBC104.redmond.corp.microsoft.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: VS-23(zz9371I542M14ffIzz1de0h1202h1d1ah1d2ahzz1033IL8275dhz2fh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h15d0l1155h)
Received-SPF: pass (mail102-db3: domain of microsoft.com designates 131.107.125.8 as permitted sender) client-ip=131.107.125.8; envelope-from=Michael.Jones@microsoft.com; helo=TK5EX14HUBC104.redmond.corp.microsoft.com ; icrosoft.com ;
Received: from mail102-db3 (localhost.localdomain [127.0.0.1]) by mail102-db3 (MessageSwitch) id 1354082477654498_12767; Wed, 28 Nov 2012 06:01:17 +0000 (UTC)
Received: from DB3EHSMHS015.bigfish.com (unknown [10.3.81.244]) by mail102-db3.bigfish.com (Postfix) with ESMTP id 9CD3642005B; Wed, 28 Nov 2012 06:01:17 +0000 (UTC)
Received: from TK5EX14HUBC104.redmond.corp.microsoft.com (131.107.125.8) by DB3EHSMHS015.bigfish.com (10.3.87.115) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 28 Nov 2012 06:01:17 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.240]) by TK5EX14HUBC104.redmond.corp.microsoft.com ([157.54.80.25]) with mapi id 14.02.0318.003; Wed, 28 Nov 2012 06:01:03 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, "jose@ietf.org" <jose@ietf.org>
Thread-Topic: [jose] Key Identifier
Thread-Index: AQHNy8d0ku6cn6XRzEmtwuiZq1B1wJf+w3/Q
Date: Wed, 28 Nov 2012 06:01:02 +0000
Message-ID: <4E1F6AAD24975D4BA5B168042967394366905D5D@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <0DC3825F-D600-4239-8283-FB7E2CAC4514@gmx.net> <4354D3B0-62A3-45A2-ABDB-9A006C6C7263@gmx.net>
In-Reply-To: <4354D3B0-62A3-45A2-ABDB-9A006C6C7263@gmx.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.37]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
Subject: Re: [jose] Key Identifier
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: Wed, 28 Nov 2012 06:01:22 -0000

It may contain the key ID, or like many things OAuth, it may know which key to use by other means.  For instance, it may be supplied via dynamic registration.

				-- Mike

-----Original Message-----
From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Hannes Tschofenig
Sent: Monday, November 26, 2012 3:16 AM
To: jose@ietf.org
Cc: Hannes Tschofenig
Subject: [jose] Key Identifier

Hi all, 

In Appendix A.1 of the JWS document there is an example with an HMAC SHA-256 keyed message digest.

I would have assumed that the header contains the key id so that the receipient can actually verify it.

Ciao
Hannes

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

v2.23.0 | Report a Bug | By Email