Shepherd Write-Up for "JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens"
(1) What type of RFC is being requested (BCP, Proposed Standard,
Internet Standard, Informational, Experimental, or Historic)? Why
is this the proper type of RFC? Is this type of RFC indicated in the
title page header?
This specification is proposed as a 'Standards Track' document. The
type of RFC is indicated.
(2) The IESG approval announcement includes a Document Announcement
Write-Up. Please provide such a Document Announcement Write-Up. Recent
examples can be found in the "Action" announcements for approved
documents. The approval announcement contains the following sections:
This specification defines a profile for issuing OAuth 2.0 access
tokens in JSON web token (JWT) format. Authorization servers and
resource servers from different vendors can leverage this profile to
issue and consume access tokens in interoperable manner.
Working Group Summary
The OAuth working group has defined an encoding format for access
tokens in RFC 7519. This document takes deployment practice and
summarizes it in this document with regards to the content
in the JWT access token.
Are there existing implementations of the protocol? Have a
significant number of vendors indicated their plan to
implement the specification? Are there any reviewers that
merit special mention as having done a thorough review,
e.g., one that resulted in important changes or a
conclusion that the document had no substantive issues? If
there was a MIB Doctor, Media Type or other expert review,
what was its course (briefly)? In the case of a Media Type
review, on what date was the request posted?
The JWT access token is widely used in industry.
Here is a list of implementations based on feedback on the mailing list:
Node.js project oidc-provider (https://github.com/panva/node-oidc-provider) has an
option to issue Access Tokens conforming to this profile.
IdentityServer implements this functionality:
Connect2id server implements this specification:
Glewlwyd's OIDC plugin implements an earlier version of the specification:
The working group has received feedback from the deployment community
and there is consensus on the content of the document.
Who is the Document Shepherd? Who is the Responsible Area
Hannes Tschofenig is the document shepherd and the responsible area
director is Roman Danyliw.
(3) Briefly describe the review of this document that was performed by
the Document Shepherd. If this version of the document is not ready
for publication, please explain why the document is being forwarded to
The document shepherd was involved in the working group review process.
(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed?
There are no concerns regarding the document reviews.
(5) Do portions of the document need review from a particular or from
broader perspective, e.g., security, operational complexity, AAA, DNS,
DHCP, XML, or internationalization? If so, describe the review that
There are no other reviews needed.
(6) Describe any specific concerns or issues that the Document Shepherd
has with this document that the Responsible Area Director and/or the
IESG should be aware of? For example, perhaps he or she is uncomfortable
with certain parts of the document, or has concerns whether there really
is a need for it. In any event, if the WG has discussed those issues and
has indicated that it still wishes to advance the document, detail those
The document shepherd has no concerns with the document.
(7) Has each author confirmed that any and all appropriate IPR
disclosures required for full conformance with the provisions of BCP 78
and BCP 79 have already been filed. If not, explain why.
The authors have confirmed full conformance with the provisions of BCP 78
and BCP 79:
(8) Has an IPR disclosure been filed that references this document?
If so, summarize any WG discussion and conclusion regarding the IPR
No IPR disclosures have been filed for this document.
(9) How solid is the WG consensus behind this document? Does it
represent the strong concurrence of a few individuals, with others
being silent, or does the WG as a whole understand and agree with it?
There is solid consensus in the working group for publishing this
(10) Has anyone threatened an appeal or otherwise indicated extreme
discontent? If so, please summarise the areas of conflict in separate
email messages to the Responsible Area Director. (It should be in a
separate email because this questionnaire is publicly available.)
Denis Pinkas has raised concerns about the design decisions on the mailing list.
These concerns relate to the way how the OAuth 2.0 architecture handles access
tokens. In particular, Denis expressed discomfort that the OAuth client does
not take a more active role in requesting the use of this profile and the
ability to inspect the access token content.
(11) Identify any ID nits the Document Shepherd has found in this
document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
Checklist). Boilerplate checks are not enough; this check needs to be
The shepherd checked the document.
(12) Describe how the document meets any required formal review
criteria, such as the MIB Doctor, media type, and URI type reviews.
No formal review is needed.
(13) Have all references within this document been identified as
either normative or informative?
Yes. The references are split into normative and informative references.
(14) Are there normative references to documents that are not ready for
advancement or are otherwise in an unclear state? If such normative
references exist, what is the plan for their completion?
There are no normative references that prevent advancement of this document.
(15) Are there downward normative references references (see RFC 3967)?
If so, list these downward references to support the Area Director in
the Last Call procedure.
There are no downward normative references. There is, however, a reference
to a non-IETF RFC, namely to
[OpenID.Core] Sakimura, N., Bradley, J., Jones, M., Medeiros, B., and C.
Mortimore, "OpenID Connect Core 1.0", November 2014.
(16) Will publication of this document change the status of any
existing RFCs? Are those RFCs listed on the title page header, listed
in the abstract, and discussed in the introduction? If the RFCs are not
listed in the Abstract and Introduction, explain why, and point to the
part of the document where the relationship of this document to the
other RFCs is discussed. If this information is not in the document,
explain why the WG considers it unnecessary.
This document does not change the status of an existing RFC.
(17) Describe the Document Shepherd's review of the IANA considerations
section, especially with regard to its consistency with the body of the
document. Confirm that all protocol extensions that the document makes
are associated with the appropriate reservations in IANA registries.
Confirm that any referenced IANA registries have been clearly
identified. Confirm that newly created IANA registries include a
detailed specification of the initial contents for the registry, that
allocations procedures for future registrations are defined, and a
reasonable name for the new registry has been suggested (see RFC 5226).
This document requires a new media type to be registered and also adds
new claims to the JWT claims registry. The relevant registries are clearly
(18) List any new IANA registries that require Expert Review for future
allocations. Provide any public guidance that the IESG would find
useful in selecting the IANA Experts for these new registries.
This document does not create new registries.
(19) Describe reviews and automated checks performed by the Document
Shepherd to validate sections of the document written in a formal
language, such as XML code, BNF rules, MIB definitions, etc.
There is no text in formal languages in the document.