Shepherd writeup for "OAuth 2.0 Token Introspection"
<draft-ietf-oauth-introspection-07>
As required by RFC 4858, this is the current template for the Document
Shepherd Write-Up.
(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?
Standards Track
(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:
Technical Summary
The "OAuth 2.0 Token Introspection" specification defines a method
for a protected resource to query an OAuth 2.0 authorization server
to determine the active state of an OAuth 2.0 token and to determine
meta-information about this token. OAuth 2.0 deployments can use
this method to convey information about the authorization context
of the token from the authorization server to the protected resource.
Working Group Summary
Was there anything in WG process that is worth noting? For
example, was there controversy about particular points or
were there decisions where the consensus was particularly
rough?
There was no controversy. When the specification was brought
to the working group the concept was already well established and
in use.
Document Quality
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?
There are multiple implementations of this specification:
* MITREid Connect:
https://github.com/mitreid-connect/OpenID-Connect-Java-Spring-Server/
* WSO2 suite:
http://pzf.fremantle.org/2013/11/oauth2-introspection-with-wso2-esb-and.html
* PHP AS:
https://github.com/fkooman/php-oauth-as
As well as any compliant UMA implementation (so, CloudIdentity, Gluu oxAuth, etc.).
Personnel
Who is the Document Shepherd? Who is the Responsible Area
Director?
Hannes Tschofenig is the document shepherd and Kathleen Moriarty is
the responsible area director.
(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 IESG.
The shepherd has reviewed the document and posted review comments
to the mailing list. Those comments have been addressed.
(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed?
The document shepherd has no concerns regarding the depth and breadth
of the 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
took place.
Review from the IETF security community would be appreciated but no
other particular review activities are otherwise necessary.
(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
concerns here.
There are no concerns with this 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.
Justin Richer, the document author, has confirmed full conformance with the
provisions of BCP 78 and BCP 79:
https://www.ietf.org/mail-archive/web/oauth/current/msg14106.html
(8) Has an IPR disclosure been filed that references this document?
If so, summarize any WG discussion and conclusion regarding the IPR
disclosures.
No IPR disclosures have been filed.
(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?
The working group has consensus to publish this document as a
Standards Track specification.
(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.)
No appeal / extreme discontent has been raised.
(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
thorough.
The shepherd checked nits.
(12) Describe how the document meets any required formal review
criteria, such as the MIB Doctor, media type, and URI type reviews.
No such formal reviews are needed.
(13) Have all references within this document been identified as
either normative or informative?
Yes; references are separated into informative and normative.
(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?
All normative references are published RFC documents / W3C specifications.
(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 no downward normative references. There is only a reference to
a W3C document, namely HTML5.
(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 any existing RFCs.
(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).
The IANA consideration section defines a new registry, called
"OAuth Token Introspection Response Registry", and populates this
registry with 12 values. The IANA consideration section is
consistent with the main body of the document.
(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.
The OAuth Token Introspection Response Registry is a new registry
and it requires expert review. The following persons would be
adequate experts for this registry: Mike Jones, Brian Campbell,
John Bradley, and Justin Richer.
(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.
The shepherd has verified the JSON code with JSONLint.