[jose] December 27, 2012 JOSE Release
Mike Jones <Michael.Jones@microsoft.com> Sat, 29 December 2012 01:07 UTC
Return-Path: <Michael.Jones@microsoft.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 B5C3A21F8E2B for <jose@ietfa.amsl.com>; Fri, 28 Dec 2012 17:07:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level:
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[AWL=-0.013, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 XjeinvEG283n for <jose@ietfa.amsl.com>; Fri, 28 Dec 2012 17:07:41 -0800 (PST)
Received: from NA01-BY2-obe.outbound.protection.outlook.com (na01-by2-obe.ptr.protection.outlook.com [207.46.100.25]) by ietfa.amsl.com (Postfix) with ESMTP id B115721F8E2A for <jose@ietf.org>; Fri, 28 Dec 2012 17:07:41 -0800 (PST)
Received: from BY2FFO11FD016.protection.gbl (10.1.15.203) by BY2FFO11HUB019.protection.gbl (10.1.14.178) with Microsoft SMTP Server (TLS) id 15.0.586.12; Sat, 29 Dec 2012 01:07:21 +0000
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD016.mail.protection.outlook.com (10.1.14.132) with Microsoft SMTP Server (TLS) id 15.0.586.12 via Frontend Transport; Sat, 29 Dec 2012 01:07:20 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.59]) by TK5EX14HUBC103.redmond.corp.microsoft.com ([157.54.86.9]) with mapi id 14.02.0318.003; Sat, 29 Dec 2012 01:07:12 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: "jose@ietf.org" <jose@ietf.org>
Thread-Topic: December 27, 2012 JOSE Release
Thread-Index: Ac3lYNFRxgEleyiFSlaREDgDQTnutg==
Date: Sat, 29 Dec 2012 01:07:11 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943669B0A09@TK5EX14MBXC283.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.34]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B1680429673943669B0A09TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(50986001)(54316002)(49866001)(51856001)(77982001)(33656001)(5343635001)(47976001)(5343665001)(56816002)(4396001)(47736001)(76482001)(5343655001)(16406001)(53806001)(74662001)(55846006)(54356001)(56776001)(74502001)(59766001)(46102001)(512954001)(47446002)(15202345001)(16236675001)(44976002)(31966008)(6606295001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB019; LANG:en;
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 07106EF9B9
Subject: [jose] December 27, 2012 JOSE Release
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: Sat, 29 Dec 2012 01:07:43 -0000
New versions of the JOSE specs have been released incorporating feedback since IETF 85 in Atlanta. The highlight of this release is the new JSON Private and Symmetric Key spec<http://tools.ietf.org/html/draft-jones-jose-json-private-and-symmetric-key-00>, which extends JWKs to be able to represent private and symmetric keys. These sensitive keys can then be protected for transmission and storage by JWE encryption of their JWK representations. One new feature added to JWK is the ability to optionally specify which specific algorithm the key is intended to be used with. (This is already existing practice for keys in X.509 format.) For instance, a symmetric key might be annotated to say that it is to be used with the "HS256" algorithm. Because the natural field name for this functionality is "alg", the "alg" name is now used for this purpose (matching JWS and JWE) and the key type (formerly "alg") is now denoted by the "kty" field. This release incorporates editorial improvements suggested by Jeff Hodges and Hannes Tschofenig in their reviews of the JWT specification. Many of these simplified the terminology usage. See the Document History section of each specification for more details about the changes made. This release is part of a coordinated release of JOSE, OAuth, and OpenID Connect specifications. You can read about the other releases here: OAuth Release Notes<http://self-issued.info/?p=916>, OpenID Connect Release Notes<http://self-issued.info/?p=918>. The new specification versions are: * http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-08 * http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-08 * http://tools.ietf.org/html/draft-ietf-jose-json-web-key-08 * http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-08 * http://tools.ietf.org/html/draft-jones-jose-jws-json-serialization-04 * http://tools.ietf.org/html/draft-jones-jose-jwe-json-serialization-04 * http://tools.ietf.org/html/draft-jones-jose-json-private-and-symmetric-key-00 HTML formatted versions are available at: * http://self-issued.info/docs/draft-ietf-jose-json-web-signature-08.html * http://self-issued.info/docs/draft-ietf-jose-json-web-encryption-08.html * http://self-issued.info/docs/draft-ietf-jose-json-web-key-08.html * http://self-issued.info/docs/draft-ietf-jose-json-web-algorithms-08.html * http://self-issued.info/docs/draft-jones-jose-jws-json-serialization-04.html * http://self-issued.info/docs/draft-jones-jose-jwe-json-serialization-04.html * http://self-issued.info/docs/draft-jones-jose-json-private-and-symmetric-key-00.html -- Mike
- [jose] December 27, 2012 JOSE Release Mike Jones
- Re: [jose] December 27, 2012 JOSE Release Vladimir Dzhuvinov / NimbusDS