JSON Web Key (JWK)
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org>
To: IETF-Announce <email@example.com>
Cc: RFC Editor <firstname.lastname@example.org>,
jose mailing list <email@example.com>,
jose chair <firstname.lastname@example.org>
Subject: Protocol Action: 'JSON Web Key (JWK)' to Proposed Standard (draft-ietf-jose-json-web-key-41.txt)
The IESG has approved the following document:
- 'JSON Web Key (JWK)'
(draft-ietf-jose-json-web-key-41.txt) as Proposed Standard
Encryption Working Group.
The IESG contact persons are Kathleen Moriarty and Stephen Farrell.
A URL of this Internet Draft is:
This document, JSON Web Encryption (JWE), represents encrypted content using
Working Group Summary
The document has clear working group consensus for publication, and has been
reviewed by several WG participants since its initial adoption as a working group
This document has been reviewed and revised many times. There are multiple
implementations of this document. Some of these are listed at:
https://openid.net/developers/libraries/ (see the JWT/JWS/JWE/JWK/JWA
The IETF last call reviews were mostly addressed, but there are a few items
that should be addressed in the next revision that were agreed to already in the
The discussion on duplicate member names applies to this draft and is unresolved.
WG consensus has been to leave the text as-is, although new options have surfaced.
Opinions are welcome.
Karen O'Donoghue is acting as the Document Shepherd. Kathleen Moriarty is the
Responsible Area Director.
'The registries use the 5226 'Specification Required'
RFC Editor Note:
This draft is part of a set of drafts that cross 2 working groups. I am
working through the reviews (shepherd just confirmed them for the OAuth
ones) and would like them processed as a set. The JOSE drafts will
hopefully be ready shortly as well. The set includes (in order):
RFC Editor Note