IETF Logo Mail Archive

Re: [jose] Document Action: 'Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)' to Informational RFC (draft-ietf-jose-use-cases-06.txt)

Mike Jones <Michael.Jones@microsoft.com> Wed, 15 January 2014 07:00 UTC

Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35B081AE2ED for <jose@ietfa.amsl.com>; Tue, 14 Jan 2014 23:00:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sZvFgb23wy5p for <jose@ietfa.amsl.com>; Tue, 14 Jan 2014 22:59:59 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0150.outbound.protection.outlook.com [207.46.163.150]) by ietfa.amsl.com (Postfix) with ESMTP id 24B831AE2F9 for <jose@ietf.org>; Tue, 14 Jan 2014 22:59:58 -0800 (PST)
Received: from BL2PR03CA022.namprd03.prod.outlook.com (10.141.66.30) by BL2PR03MB243.namprd03.prod.outlook.com (10.255.231.23) with Microsoft SMTP Server (TLS) id 15.0.847.13; Wed, 15 Jan 2014 06:59:46 +0000
Received: from BN1AFFO11FD040.protection.gbl (2a01:111:f400:7c10::170) by BL2PR03CA022.outlook.office365.com (2a01:111:e400:c1b::30) with Microsoft SMTP Server (TLS) id 15.0.847.13 via Frontend Transport; Wed, 15 Jan 2014 06:59:46 +0000
Received: from mail.microsoft.com (131.107.125.37) by BN1AFFO11FD040.mail.protection.outlook.com (10.58.52.251) with Microsoft SMTP Server (TLS) id 15.0.847.12 via Frontend Transport; Wed, 15 Jan 2014 06:59:46 +0000
Received: from TK5EX14MBXC286.redmond.corp.microsoft.com ([169.254.1.67]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi id 14.03.0158.002; Wed, 15 Jan 2014 06:58:58 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Richard Barnes <rlb@ipv.sx>
Thread-Topic: [jose] Document Action: 'Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)' to Informational RFC (draft-ietf-jose-use-cases-06.txt)
Thread-Index: AQHPEU6vNrtIJJ4KqUCnvhduZC211ZqFW3Xg
Date: Wed, 15 Jan 2014 06:58:58 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739437CDB0EFC@TK5EX14MBXC286.redmond.corp.microsoft.com>
References: <20140114173143.16309.25761.idtracker@ietfa.amsl.com>
In-Reply-To: <20140114173143.16309.25761.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.35]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009001)(779001)(679001)(689001)(377454003)(199002)(189002)(164054003)(13464003)(49866001)(74876001)(81542001)(23726002)(50986001)(47736001)(47976001)(2656002)(77982001)(46406003)(44976005)(76482001)(33656001)(81816001)(74706001)(87936001)(83322001)(81686001)(19580395003)(19580405001)(4396001)(6806004)(85306002)(31966008)(53806001)(93516001)(56776001)(54356001)(93136001)(80976001)(87266001)(77096001)(54316002)(85806002)(65816001)(59766001)(79102001)(15188555004)(15975445006)(46102001)(81342001)(55846006)(47446002)(51856001)(50466002)(74662001)(74502001)(74366001)(56816005)(85852003)(90146001)(80022001)(15202345003)(92566001)(20776003)(83072002)(69226001)(47776003)(66066001)(92726001)(63696002)(76796001)(76786001); DIR:OUT; SFP:1101; SCL:1; SRVR:BL2PR03MB243; H:mail.microsoft.com; CLIP:131.107.125.37; FPR:; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en;
X-O365ENT-EOP-Header: Message processed by - O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 00922518D8
X-OriginatorOrg: microsoft.com
Cc: jose chair <jose-chairs@tools.ietf.org>, jose mailing list <jose@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Re: [jose] Document Action: 'Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)' to Informational RFC (draft-ietf-jose-use-cases-06.txt)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.15
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, 15 Jan 2014 07:00:01 -0000

Are the issues identified in http://www.ietf.org/mail-archive/web/jose/current/msg03817.html being addressed as RFC Editor notes?  If so, can you please point the working group to the editing instructions, so they can be reviewed by the working group?

				Thanks,
				-- Mike

-----Original Message-----
From: jose [mailto:jose-bounces@ietf.org] On Behalf Of The IESG
Sent: Tuesday, January 14, 2014 9:32 AM
To: IETF-Announce
Cc: jose chair; jose mailing list; RFC Editor
Subject: [jose] Document Action: 'Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)' to Informational RFC (draft-ietf-jose-use-cases-06.txt)

The IESG has approved the following document:
- 'Use Cases and Requirements for JSON Object Signing and Encryption
   (JOSE)'
  (draft-ietf-jose-use-cases-06.txt) as Informational RFC

This document is the product of the Javascript Object Signing and Encryption Working Group.

The IESG contact persons are Sean Turner and Stephen Farrell.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-jose-use-cases/




Technical Summary

   This document defines a set of use cases and requirements
   for a secure object format encoded using JavaScript Object Notation
   (JSON), drawn from a variety of application security mechanisms
   currently in development.

Working Group Summary

   The document represents the consuses of the working group.
   The document was not controversial during the working group
   discussions.

Document Quality

  The document has not had a large amount of review outside of
  the JOSE working group.  As such it is possible that the group
  has missed or mis-represented the set of use cases that the
  JOSE working group needs to address when generating the
  specifications in the group.  The OAUTH working group views
  are well presented, but it does not have sufficient apps area review.

Personnel

   Document Shepherd is Jim Schaad
   Area Director is Sean Turner
_______________________________________________
jose mailing list
jose@ietf.org
https://www.ietf.org/mailman/listinfo/jose

v2.23.0 | Report a Bug | By Email