Re: [jose] I-D Action: draft-ietf-jose-use-cases-05.txt
"Jim Schaad" <ietf@augustcellars.com> Fri, 04 October 2013 20:52 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 1AB6F21F9CAF for <jose@ietfa.amsl.com>; Fri, 4 Oct 2013 13:52:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.298
X-Spam-Level:
X-Spam-Status: No, score=-3.298 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_21=0.6, 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 WWNxaIWKoWja for <jose@ietfa.amsl.com>; Fri, 4 Oct 2013 13:52:13 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id 5133621F9E40 for <jose@ietf.org>; Fri, 4 Oct 2013 13:52:12 -0700 (PDT)
Received: from Philemon (winery.augustcellars.com [206.212.239.129]) (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 56C2438F30; Fri, 4 Oct 2013 13:52:10 -0700 (PDT)
From: Jim Schaad <ietf@augustcellars.com>
To: 'Richard Barnes' <rlb@ipv.sx>, 'Sean Turner' <turners@ieca.com>
References: <20130905154742.11450.63345.idtracker@ietfa.amsl.com> <5232594E.4040709@ieca.com> <CAL02cgQxQnGRFVC9i3bYBStSDwJ=tbBk4go7ArrRG+kx3Lnrzg@mail.gmail.com>
In-Reply-To: <CAL02cgQxQnGRFVC9i3bYBStSDwJ=tbBk4go7ArrRG+kx3Lnrzg@mail.gmail.com>
Date: Fri, 04 Oct 2013 13:50:56 -0700
Message-ID: <016f01cec143$6c9ab190$45d014b0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0170_01CEC108.C03D1210"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLSyY7/jZqdAE9rkAeMrS3KCPX56gJ+K1gOAP/5WFKXwQJYMA==
Content-Language: en-us
Cc: jose@ietf.org
Subject: Re: [jose] I-D Action: draft-ietf-jose-use-cases-05.txt
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: Fri, 04 Oct 2013 20:52:18 -0000
I have already responded on item 3. 1 & 2 should be deal with as part of either AD comments or IETF last comments. Id on't see these as blocking right now. Jim From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Richard Barnes Sent: Friday, October 04, 2013 10:14 AM To: Sean Turner Cc: jose@ietf.org Subject: Re: [jose] I-D Action: draft-ietf-jose-use-cases-05.txt Chairs/AD: Should I go ahead and rev this, or handle these along with IETF LC comments? On Thu, Sep 12, 2013 at 8:16 PM, Sean Turner <turners@ieca.com> wrote: I'm just nitting for now: 1) s2 OLD: The JOSE working group charter calls for the group to define three basic JSON object formats: NEW: Three basic JSON object formats are initially defined, with more possibly defined later: 2) s2 OLD: The JOSE working group items intended to describe these formats are JSON Web Signature (JWS), JSON Web Encryption (JWE), and JSON Web Key (JWK), respectively [I-D.ietf-jose-json-web-signature] [I-D.ietf-jose-json-web-encryption] [I-D.ietf-jose-json-web-key]. NEW: The JSON Web Signature (JWS), JSON Web Encryption (JWE), and JSON Web Key (JWK) specifications, respectively [I-D.ietf-jose-json-web-signature] [I-D.ietf-jose-json-web-encryption] [I-D.ietf-jose-json-web-key], define these formats. 3) s3: Not sure the following is entirely correct for DH-based algs: o The JOSE encrypted object format must support object encryption in the case where the sender has only a public key for the receiver. Shouldn't this also include the case where the sender has their own public key and the receiver's public key. spt _______________________________________________ jose mailing list jose@ietf.org https://www.ietf.org/mailman/listinfo/jose
- Re: [jose] I-D Action: draft-ietf-jose-use-cases-… Richard Barnes
- [jose] I-D Action: draft-ietf-jose-use-cases-05.t… internet-drafts
- Re: [jose] I-D Action: draft-ietf-jose-use-cases-… Mike Jones
- Re: [jose] I-D Action: draft-ietf-jose-use-cases-… Sean Turner
- Re: [jose] I-D Action: draft-ietf-jose-use-cases-… Jim Schaad
- Re: [jose] I-D Action: draft-ietf-jose-use-cases-… Sean Turner
- Re: [jose] I-D Action: draft-ietf-jose-use-cases-… Richard Barnes
- Re: [jose] I-D Action: draft-ietf-jose-use-cases-… Jim Schaad
- Re: [jose] I-D Action: draft-ietf-jose-use-cases-… Richard Barnes