IETF Logo Mail Archive

Re: [jose] RFC 7165 on Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)

Mike Jones <Michael.Jones@microsoft.com> Tue, 15 April 2014 21:02 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 353F71A038C for <jose@ietfa.amsl.com>; Tue, 15 Apr 2014 14:02:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 JWnaetsfNy7E for <jose@ietfa.amsl.com>; Tue, 15 Apr 2014 14:02:02 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0141.outbound.protection.outlook.com [207.46.163.141]) by ietfa.amsl.com (Postfix) with ESMTP id 87BB41A01F8 for <jose@ietf.org>; Tue, 15 Apr 2014 14:02:02 -0700 (PDT)
Received: from BY2PR03CA055.namprd03.prod.outlook.com (10.141.249.28) by BY2PR03MB443.namprd03.prod.outlook.com (10.141.141.152) with Microsoft SMTP Server (TLS) id 15.0.918.8; Tue, 15 Apr 2014 21:01:58 +0000
Received: from BN1AFFO11FD007.protection.gbl (2a01:111:f400:7c10::165) by BY2PR03CA055.outlook.office365.com (2a01:111:e400:2c5d::28) with Microsoft SMTP Server (TLS) id 15.0.918.8 via Frontend Transport; Tue, 15 Apr 2014 21:01:58 +0000
Received: from mail.microsoft.com (131.107.125.37) by BN1AFFO11FD007.mail.protection.outlook.com (10.58.52.67) with Microsoft SMTP Server (TLS) id 15.0.918.6 via Frontend Transport; Tue, 15 Apr 2014 21:01:57 +0000
Received: from TK5EX14MBXC286.redmond.corp.microsoft.com ([169.254.1.232]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.03.0174.002; Tue, 15 Apr 2014 21:01:19 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Richard Barnes <rlb@ipv.sx>
Thread-Topic: [jose] RFC 7165 on Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)
Thread-Index: AQHPWGdkX1zr4jU5pEuVweSdYFaYdZsTKsfw
Date: Tue, 15 Apr 2014 21:01:18 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739439A1598F2@TK5EX14MBXC286.redmond.corp.microsoft.com>
References: <20140415045818.3282518000D@rfc-editor.org>
In-Reply-To: <20140415045818.3282518000D@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.74]
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:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009001)(6009001)(438001)(377454003)(189002)(199002)(13464003)(84676001)(6806004)(86362001)(83072002)(23726002)(19580395003)(83322001)(19580405001)(92726001)(44976005)(97736001)(92566001)(97756001)(81542001)(77982001)(85852003)(76482001)(85806002)(79102001)(15202345003)(81342001)(66066001)(15975445006)(20776003)(80976001)(47776003)(33656001)(86612001)(80022001)(87936001)(4396001)(76176999)(2656002)(50466002)(19300405004)(46102001)(50986999)(31966008)(54356999)(74662001)(2009001)(99396002)(55846006)(46406003)(74502001)(562404015); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR03MB443; H:mail.microsoft.com; FPR:EC05D0BB.9BD656D3.37E43F83.88E2C36D.20353; MLV:sfv; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en;
X-O365ENT-EOP-Header: Message processed by - O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0182DBBB05
Received-SPF: Pass (: domain of microsoft.com designates 131.107.125.37 as permitted sender) receiver=; client-ip=131.107.125.37; helo=mail.microsoft.com;
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: http://mailarchive.ietf.org/arch/msg/jose/m80xSVt_L0Yk-GU3nvIjN2hWgk4
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] RFC 7165 on Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)
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: Tue, 15 Apr 2014 21:02:08 -0000

Congratulations on fishing this, Richard!

-----Original Message-----
From: jose [mailto:jose-bounces@ietf.org] On Behalf Of rfc-editor@rfc-editor.org
Sent: Monday, April 14, 2014 9:58 PM
To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
Cc: drafts-update-ref@iana.org; jose@ietf.org; rfc-editor@rfc-editor.org
Subject: [jose] RFC 7165 on Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7165

        Title:      Use Cases and Requirements for 
                    JSON Object Signing and Encryption (JOSE) 
        Author:     R. Barnes
        Status:     Informational
        Stream:     IETF
        Date:       April 2014
        Mailbox:    rlb@ipv.sx
        Pages:      25
        Characters: 58324
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-jose-use-cases-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7165.txt

Many Internet applications have a need for object-based security mechanisms in addition to security mechanisms at the network layer or transport layer.  For many years, the Cryptographic Message Syntax
(CMS) has provided a binary secure object format based on ASN.1.
Over time, binary object encodings such as ASN.1 have become less common than text-based encodings, such as the JavaScript Object Notation (JSON).  This document defines a set of use cases and requirements for a secure object format encoded using JSON, drawn from a variety of application security mechanisms currently in development.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
jose mailing list
jose@ietf.org
https://www.ietf.org/mailman/listinfo/jose

v2.23.0 | Report a Bug | By Email