IETF Logo Mail Archive

Re: [jose] I-D Action: draft-ietf-jose-use-cases-05.txt

Richard Barnes <rlb@ipv.sx> Mon, 07 October 2013 19:37 UTC

Return-Path: <rlb@ipv.sx>
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 52A5D21E81BA for <jose@ietfa.amsl.com>; Mon, 7 Oct 2013 12:37:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.776
X-Spam-Level:
X-Spam-Status: No, score=-2.776 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 lb2iz8atOFbc for <jose@ietfa.amsl.com>; Mon, 7 Oct 2013 12:37:19 -0700 (PDT)
Received: from mail-oa0-f48.google.com (mail-oa0-f48.google.com [209.85.219.48]) by ietfa.amsl.com (Postfix) with ESMTP id 9580621E81C4 for <jose@ietf.org>; Mon, 7 Oct 2013 12:37:18 -0700 (PDT)
Received: by mail-oa0-f48.google.com with SMTP id m6so6628168oag.7 for <jose@ietf.org>; Mon, 07 Oct 2013 12:37:18 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=AW8GqFOCSrnxqZwRTFYj3fpyBYG7cF8myUmz+raI7yk=; b=D5jYTRJAfLPE1MwVAS7WKi3JsMrr9f5i1Klye0JjoPX2ieZeeRIOQw5Lob5IMCtVpN CNCrFAzKKHuzDoLKogciXUEu2hHdNCDua+Q/T8e5L8bcMpeYVT97UYiEv2rF+yLTdRWJ 58y4lO7lzDmMTo+eita/jtwKxSqf40DFaGH3yt/Vb7DqEp1imV2+zjZUJIGX0qHLaHdx sOAEwTC1B9qarVOjfnIBYBEZNYdPM1dA48jkkPG6SJPNuvjolEMn5DnLgyfZB3Eeb6ho AzXffHkIdvYFV9Xwi55jZvJGU5d48AkaWS7/friRpBqekG1dqNzD8iebjXWr21Z6ckJM GGkg==
X-Gm-Message-State: ALoCoQn1NBmqt1w050ztlOr/iYxLZcaHddtaOnLkptabJ2vk9esh6ubeQ7ZOEWvReV0swLGI/aK1
MIME-Version: 1.0
X-Received: by 10.60.95.229 with SMTP id dn5mr47787887oeb.26.1381174638094; Mon, 07 Oct 2013 12:37:18 -0700 (PDT)
Received: by 10.60.31.74 with HTTP; Mon, 7 Oct 2013 12:37:18 -0700 (PDT)
In-Reply-To: <016f01cec143$6c9ab190$45d014b0$@augustcellars.com>
References: <20130905154742.11450.63345.idtracker@ietfa.amsl.com> <5232594E.4040709@ieca.com> <CAL02cgQxQnGRFVC9i3bYBStSDwJ=tbBk4go7ArrRG+kx3Lnrzg@mail.gmail.com> <016f01cec143$6c9ab190$45d014b0$@augustcellars.com>
Date: Mon, 07 Oct 2013 15:37:18 -0400
Message-ID: <CAL02cgTtn_z00LGPd63_7-FSR9b682xw==-7qXFFD=iuPm=kcQ@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary="089e0118470aad4ab404e82bc792"
Cc: Sean Turner <turners@ieca.com>, "jose@ietf.org" <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: Mon, 07 Oct 2013 19:37:23 -0000

OK, I'm going to plan to handle these along with IETF LC comments, and not
take any action right now.
--Richard


On Fri, Oct 4, 2013 at 4:50 PM, Jim Schaad <ietf@augustcellars.com> wrote:

> 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****
>
> ** **
>

v2.29.0 | Report a Bug | By Email | System Status