Re: [jose] Keys in the documents

"Jim Schaad" <ietf@augustcellars.com> Tue, 25 June 2013 06:19 UTC

Return-Path: <ietf@augustcellars.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 0CDC021F9F60 for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 23:19:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 O443bqIE1vzH for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 23:19:08 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id 2C73621F8B33 for <jose@ietf.org>; Mon, 24 Jun 2013 23:19:07 -0700 (PDT)
Received: from Philemon (ip-64-134-138-86.public.wayport.net [64.134.138.86]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id F2CBF38EE8; Mon, 24 Jun 2013 23:19:05 -0700 (PDT)
From: Jim Schaad <ietf@augustcellars.com>
To: 'Mike Jones' <Michael.Jones@microsoft.com>
References: <4E1F6AAD24975D4BA5B16804296739436787EB2A@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436787EB2A@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Mon, 24 Jun 2013 23:18:07 -0700
Message-ID: <019f01ce716b$c40e6480$4c2b2d80$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01A0_01CE7131.17B24BA0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFu1YhbhvKKzJg8MhN51L4B2pAQtJoFK2Dw
Content-Language: en-us
Cc: draft-ietf-jose-json-web-encryption@tools.ietf.org, jose@ietf.org
Subject: Re: [jose] Keys in the documents
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: Tue, 25 Jun 2013 06:19:14 -0000

I have gone through the process of trying to use this, and I have also sat
down to think about how I would like to use the examples and I would suggest
the following:

 

There be one or two JWK sets that are defined at the start of appendix A.  

 

.         All of the keys (public, private and secret) be included in the
JWK sets

.         We assign, for testing purposes, a URL to each of the JWK sets
defined

.         Each example then either has the necessary data to find the key
from the correct JWK Set (and possibly the correct JWK Set via a jku) or the
text defines which of the keys is to be used.

.         There should be examples of many (most? All?) of the key location
methods between the JWS and JWE drafts.

 

Jim

 

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Friday, June 21, 2013 8:58 AM
To: Matt Miller (mamille2); Richard Barnes
Cc: Jim Schaad; draft-ietf-jose-json-web-encryption@tools.ietf.org;
jose@ietf.org
Subject: RE: [jose] Keys in the documents

 

Will do.

  _____  

From: Matt Miller (mamille2)
Sent: 6/21/2013 6:06 AM
To: Richard Barnes
Cc: Jim Schaad; draft-ietf-jose-json-web-encryption@tools.ietf.org;
jose@ietf.org
Subject: Re: [jose] Keys in the documents

+1

On Jun 20, 2013, at 8:48 PM, Richard Barnes <rlb@ipv.sx>
wrote:

> +1
> 
> On Thursday, June 20, 2013, Jim Schaad wrote:
> 
>> Is there any reason not to provide the public and private keys in the
>> appendixes as JWK objects?  This would make them easier to understand and
>> put them into a format that one expects to be understood by JOSE
systems.*
>> ***
>> 
>> ** **
>> 
>> Jim****
>> 
>> ** **
>> 

- m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.