Re: [jose] Call for adoption

Richard Barnes <rlb@ipv.sx> Thu, 14 February 2013 03:23 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 E517921E8047 for <jose@ietfa.amsl.com>; Wed, 13 Feb 2013 19:23:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.21
X-Spam-Level:
X-Spam-Status: No, score=-2.21 tagged_above=-999 required=5 tests=[AWL=0.766, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 NTW7dXrKrw+r for <jose@ietfa.amsl.com>; Wed, 13 Feb 2013 19:23:56 -0800 (PST)
Received: from mail-oa0-f50.google.com (mail-oa0-f50.google.com [209.85.219.50]) by ietfa.amsl.com (Postfix) with ESMTP id 102C721E80C8 for <jose@ietf.org>; Wed, 13 Feb 2013 19:23:56 -0800 (PST)
Received: by mail-oa0-f50.google.com with SMTP id l20so2097324oag.9 for <jose@ietf.org>; Wed, 13 Feb 2013 19:23:55 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=ZAdLyFHF4T9IOf61Spn2qbNtUVXKNGJq5lg2T7BJtEw=; b=cwwN3kFIlO4uU6Q6ivIRVvfPlKBaaZvtMALJ+yT1Z6IYquFPCq5BZIOyzXLEQ8SJjZ X2eI23vNTZ5uLp1jkzBcK8daCAQb/hlfRUgnISvWLnCY4daVO/+bY4mVnYQP57o+ns9j MybYasp5zcMyXSemwpx3hZLQM8iMInN85NwfyFuXLvhtF5n/1CcNdrfawMbjtRpsNDhO HK4W1Gn48d5U69Ci8OBSMA6O/EyJr4CRqB24gFxf1JyEb3WDtde7sS6W8WTOczoclZLL jF06/2v/Rt5tzhQzgUCBjh5Fzs/GVDuhI6tAw/4vJcZ8CGOtEsyUE2eBlQmfeJcIt8m6 oW1g==
MIME-Version: 1.0
X-Received: by 10.60.1.129 with SMTP id 1mr18123332oem.93.1360812235300; Wed, 13 Feb 2013 19:23:55 -0800 (PST)
Received: by 10.60.59.163 with HTTP; Wed, 13 Feb 2013 19:23:55 -0800 (PST)
X-Originating-IP: [108.18.40.68]
In-Reply-To: <02b601ce0a17$db6c3370$92449a50$@augustcellars.com>
References: <02b601ce0a17$db6c3370$92449a50$@augustcellars.com>
Date: Wed, 13 Feb 2013 22:23:55 -0500
Message-ID: <CAL02cgSFe=Sphj9PL-GF56-F_G_1JtpZ2OzMW3JiFgzRCUkxTA@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary=e89a8fb1f4f4e41ea204d5a6c936
X-Gm-Message-State: ALoCoQnsJcMwXOI3s4cXeuTOyL0mfOQ7s0tPs0dUpkKNfb6B/xDhSwzivG241Q4qCBHbTvfmCZIs
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Call for adoption
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: Thu, 14 Feb 2013 03:23:57 -0000

I support the adoption of the use cases draft.  Clearer use cases will help
this group refine a lot of the ideas that are floating around.

I do not support the adoption of the JSON serialization documents.  A JSON
serialization should be part of the base documents. I have already made a
proposal to the list for how to do this, which is essentially the same as
the one in the JSON serialization documents.  It would have a small impact
on the base specs, and make the base format much more usable.
http://www.ietf.org/mail-archive/web/jose/current/msg01465.html

--Richard



On Wednesday, February 13, 2013, Jim Schaad wrote:

> The chairs of the JOSE working group have dropped the ball on this (really
> me).****
>
> ** **
>
> At the last face-to-face meeting there was a call for the following
> documents to become working group documents:****
>
> ** **
>
> Draft-barnes-jose-use-cases<http://www.myfitnesspal.com/foohttp:/datatracker.ietf.org/doc/draft-barnes-jose-use-cases/>– Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)
> ****
>
> ** **
>
> Draft-jones-jose-jwe-json-serialization<http://datatracker.ietf.org/doc/draft-jones-jose-jwe-json-serialization/>– JSON Web Encryption JSON Serialization (JWE-JS)
> ****
>
> ** **
>
> Draft-jones-jose-jws-json-serialization<http://datatracker.ietf.org/doc/draft-jones-jose-jws-json-serialization/>– JSON Web Signature JSON Serialization (JWS-JS)
> ****
>
> ** **
>
> ** **
>
> The chairs are going to assume that the working group wants to adopt these
> three documents as that was the overwhelming response in Atlanta.  Thus you
> only need to reply if you object to these documents being adopted.  This
> call will end 27 February.****
>
> ** **
>
> (Note that we will be looking at the private key drafts during the Orlando
> meeting and issuing an adoption call shortly after that meeting.)****
>
> ** **
>
> Jim****
>
> ** **
>