draft-ietf-oauth-dyn-reg-10.txt   draft-ietf-oauth-dyn-reg-11.txt 
OAuth Working Group J. Richer, Ed. OAuth Working Group J. Richer, Ed.
Internet-Draft The MITRE Corporation Internet-Draft The MITRE Corporation
Intended status: Standards Track J. Bradley Intended status: Standards Track J. Bradley
Expires: November 06, 2013 Ping Identity Expires: November 25, 2013 Ping Identity
M.B. Jones M. Jones
Microsoft Microsoft
M. Machulak M. Machulak
Newcastle University Newcastle University
May 05, 2013 May 24, 2013
OAuth 2.0 Dynamic Client Registration Protocol OAuth 2.0 Dynamic Client Registration Protocol
draft-ietf-oauth-dyn-reg-10 draft-ietf-oauth-dyn-reg-11
Abstract Abstract
This specification defines an endpoint and protocol for dynamic This specification defines an endpoint and protocol for dynamic
registration of OAuth 2.0 Clients at an Authorization Server and registration of OAuth 2.0 Clients at an Authorization Server and
methods for the dynamically registered client to manage its methods for the dynamically registered client to manage its
registration. registration.
Status of This Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 06, 2013. This Internet-Draft will expire on November 25, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Notational Conventions . . . . . . . . . . . . . . . . . 3 1.1. Notational Conventions . . . . . . . . . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Client Metadata . . . . . . . . . . . . . . . . . . . . . . . 4 1.3. Registration Tokens and Credentials . . . . . . . . . . . 4
2.1. Relationship Between Grant Types and Response Types . . . 7 1.4. Client Lifecycle . . . . . . . . . . . . . . . . . . . . . 5
2.2. Human Readable Client Metadata . . . . . . . . . . . . . 8 1.4.1. Open Registration . . . . . . . . . . . . . . . . . . 6
3. Client Registration Endpoint . . . . . . . . . . . . . . . . 9 1.4.2. Protected Registration . . . . . . . . . . . . . . . . 7
3.1. Client Registration Request . . . . . . . . . . . . . . . 10 1.4.3. Developer Automation . . . . . . . . . . . . . . . . . 8
3.2. Client Registration Response . . . . . . . . . . . . . . 11 2. Client Metadata . . . . . . . . . . . . . . . . . . . . . . . 10
4. Client Configuration Endpoint . . . . . . . . . . . . . . . . 11 2.1. Relationship Between Grant Types and Response Types . . . 13
4.1. Forming the Client Configuration Endpoint URL . . . . . . 12 2.2. Human Readable Client Metadata . . . . . . . . . . . . . . 14
4.2. Client Read Request . . . . . . . . . . . . . . . . . . . 12 3. Client Registration Endpoint . . . . . . . . . . . . . . . . . 15
4.3. Client Update Request . . . . . . . . . . . . . . . . . . 13 3.1. Client Registration Request . . . . . . . . . . . . . . . 16
4.4. Client Delete Request . . . . . . . . . . . . . . . . . . 14 3.2. Client Registration Response . . . . . . . . . . . . . . . 18
5. Responses . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4. Client Configuration Endpoint . . . . . . . . . . . . . . . . 18
5.1. Client Information Response . . . . . . . . . . . . . . . 15 4.1. Forming the Client Configuration Endpoint URL . . . . . . 18
5.2. Client Registration Error Response . . . . . . . . . . . 17 4.2. Client Read Request . . . . . . . . . . . . . . . . . . . 19
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 4.3. Client Update Request . . . . . . . . . . . . . . . . . . 19
7. Security Considerations . . . . . . . . . . . . . . . . . . . 18 4.4. Client Delete Request . . . . . . . . . . . . . . . . . . 22
8. Normative References . . . . . . . . . . . . . . . . . . . . 20 5. Responses . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 21 5.1. Client Information Response . . . . . . . . . . . . . . . 23
Appendix B. Document History . . . . . . . . . . . . . . . . . . 21 5.2. Client Registration Error Response . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
6.1. OAuth Token Endpoint Authentication Methods Registry . . . 25
6.1.1. Registration Template . . . . . . . . . . . . . . . . 26
6.1.2. Initial Registry Contents . . . . . . . . . . . . . . 26
7. Security Considerations . . . . . . . . . . . . . . . . . . . 27
8. Normative References . . . . . . . . . . . . . . . . . . . . . 28
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 29
Appendix B. Document History . . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33
1. Introduction 1. Introduction
In some use-case scenarios, it is desirable or necessary to allow In some use-case scenarios, it is desirable or necessary to allow
OAuth 2.0 clients to obtain authorization from an OAuth 2.0 OAuth 2.0 clients to obtain authorization from an OAuth 2.0
authorization server without requiring the two parties to interact authorization server without requiring the two parties to interact
beforehand. Nevertheless, in order for the authorization server to beforehand. Nevertheless, for the authorization server to accurately
accurately and securely represent to end-users which client is and securely represent to end-users which client is seeking
seeking authorization to access the end-user's resources, a method authorization to access the end-user's resources, a method for
for automatic and unique registration of clients is needed. The automatic and unique registration of clients is needed. The OAuth
OAuth 2.0 authorization framework does not define how the 2.0 authorization framework does not define how the relationship
relationship between the Client and the Authorization Server is between the Client and the Authorization Server is initialized, or
initialized, or how a given client is assigned a unique Client how a given client is assigned a unique Client Identifier.
Identifier. Historically, this has happened out-of-band from the Historically, this has happened out-of-band from the OAuth 2.0
OAuth 2.0 protocol. This draft provides a mechanism for a client to protocol. This draft provides a mechanism for a client to register
register itself with the Authorization Server, which can be used to itself with the Authorization Server, which can be used to
dynamically provision a Client Identifier, and optionally a Client dynamically provision a Client Identifier, and optionally a Client
Secret. Secret.
As part of the registration process, this specification also defines As part of the registration process, this specification also defines
a mechanism for the client to present the Authorization Server with a a mechanism for the client to present the Authorization Server with a
set of metadata, such as a display name and icon to be presented to set of metadata, such as a display name and icon to be presented to
the user during the authorization step. This draft also provides a the user during the authorization step. This draft also provides a
mechanism for the Client to read and update this information after mechanism for the Client to read and update this information after
the initial registration action. the initial registration action.
skipping to change at page 3, line 31 skipping to change at page 4, line 5
1.2. Terminology 1.2. Terminology
This specification uses the terms "Access Token", "Refresh Token", This specification uses the terms "Access Token", "Refresh Token",
"Authorization Code", "Authorization Grant", "Authorization Server", "Authorization Code", "Authorization Grant", "Authorization Server",
"Authorization Endpoint", "Client", "Client Identifier", "Client "Authorization Endpoint", "Client", "Client Identifier", "Client
Secret", "Protected Resource", "Resource Owner", "Resource Server", Secret", "Protected Resource", "Resource Owner", "Resource Server",
and "Token Endpoint" defined by OAuth 2.0 [RFC6749]. and "Token Endpoint" defined by OAuth 2.0 [RFC6749].
This specification defines the following additional terms: This specification defines the following additional terms:
o Client Registration Endpoint: The OAuth 2.0 Endpoint through which Client Registration Endpoint OAuth 2.0 Endpoint through which a
a Client can request new registration. The means of the Client Client can be registered at an Authorization Server. The means by
obtaining the URL for this endpoint are out of scope for this which the URL for this endpoint are obtained are out of scope for
specification. this specification.
o Client Configuration Endpoint: The OAuth 2.0 Endpoint through Client Configuration Endpoint OAuth 2.0 Endpoint through which
which a specific Client can manage its registration information, registration information for a registered Client can be managed.
provided by the Authorization Server to the Client. This URL for This URL for this endpoint is returned by the Authorization Server
this endpoint is communicated to the client by the Authorization in the Client Information Response.
Server in the Client Information Response.
o Registration Access Token: An OAuth 2.0 Bearer Token issued by the Registration Access Token OAuth 2.0 Bearer Token issued by the
Authorization Server through the Client Registration Endpoint Authorization Server through the Client Registration Endpoint that
which is used by the Client to authenticate itself during read, is used to authenticate the caller when accessing the Client's
update, and delete operations. This token is associated with a registration information at the Client Configuration Endpoint.
particular Client. This Access Token is associated with a particular registered
Client.
Initial Access Token An OAuth 2.0 Access Token optionally issued by
an Authorization Server granting access to its Client Registration
Endpoint.
1.3. Registration Tokens and Credentials
Throughout the course of the Dynamic Registration protocol, there are
three different classes of credentials in play, each with different
properties and targets.
o The Initial Access Token is optionally used by the Client or
Developer at the Registration Endpoint. This is an OAuth 2.0
Bearer Token that is used to authorize the initial Client
Registration Request. The content, structure, generation, and
validation of this token are out of scope for this specification.
The Authorization Server can use this token to verify that the
presenter is allowed to dynamically register new clients. The
Authorization Server can also use this token to tie multiple
instances of registered clients (each with their own distinct
Client Identifier) back to the party to whom the Initial Access
Token was issued, usually an application developer. This token
may be shared between multiple instances of a Client to allow them
to each register separately. This token should be used only at
the Client Registration Endpoint.
o The Registration Access Token is used by the Client or Developer
at the Client Configuration Endpoint and represents the holder's
authorization to manage the registration of a Client. This is an
OAuth 2.0 Bearer Token that is issued from the Client Registration
Endpoint in response to a Client Registration Request and is
returned in a Client Information Response. The Registration
Access Token is uniquely bound to the Client Identifier and is
required to be presented with all calls to the Client
Configuration Endpoint. The Registration Access Token should be
protected and should not be shared between instances of a client
(otherwise, one instance could change or delete registration
values for all instances of the client). The Registration Access
Token can be rotated through the use of the client read and update
methods on the Client Configuration Endpoint. The Registration
Access Token should be used only at the Client Configuration
Endpoint.
o The Client Credentials (such as "client_secret") are optional
depending on the type of Client and are used to retrieve OAuth
tokens. Client Credentials are usually bound to particular
instances of a Client and should not be shared between instances.
Since not all types of Clients have Client Credentials, they
cannot be used to manage client registrations. The Client
Credentials can be rotated through the use of the client read and
update methods on the Client Configuration Endpoint. The Client
Credentials should not be used for authentication at the Client
Registration Endpoint or at the Client Configuration endpoint.
1.4. Client Lifecycle
In the OAuth 2.0 specification [RFC6749], a Client is identified by
its own unique Client Identifier ("client_id") at each Authorization
Server that it associates with. Dynamic Registration as defined in
this document is one way for a Client to get a Client Identifier and
associate a set of metadata with that identifier. Lack of such a
Client Identifier is the expected trigger for a client registration
operation.
In many cases, this Client Identifier is a unique, pairwise
association between a particular running instance of a piece of
Client software and a particular running instance of an Authorization
Server software. In particular:
o A single instance of Client software (such as a Web server)
talking to multiple Authorization Servers will need to register
with each Authorization Server separately, creating a distinct
Client Identifier with each Authorization Server. The Client can
not make any assumption of correlation on the part of the
Authorization Server without further specifications, profiles, and
extensions to this specification document.
o Multiple instances of Client software (such as a native
application installed on multiple devices simultaneously) talking
to the same Authorization Server will need to each register with
that Authorization Server separately, creating a distinct Client
Identifier for each copy of the application. The Authorization
Server cannot make any assumption of correlation between these
clients without further specifications, profiles, and extensions
to this specification document.
A Client Identifier (and its associated credentials) could also be
shared between multiple instances of a Client. Mechanisms for
sharing Client Identifiers between multiple instances of a piece of
software (either Client or Authorization Server) are outside the
scope of this specification, as it is expected that every successful
registration request (Section 3.1) results in the issuance of a new
Client Identifier.
There are several patterns of OAuth Client registration that this
protocol can enable. The following non-normative example lifecycle
descriptions are not intended to be an exhaustive list. It is
assumed that the Authorization Server supports the Dynamic
Registration protocol and that all necessary discovery steps (which
are out of scope for this specification) have already been performed.
1.4.1. Open Registration
Open Registration, with no authentication on the Registration
Endpoint, works as follows:
a. A Client needs to get OAuth 2.0 tokens from an Authorization
Server, but the Client does not have a Client Identifier for that
Authorization Server.
b. The Client sends an HTTP POST request to the Client Registration
Endpoint at the Authorization Server and includes its metadata.
c. The Authorization Server issues a Client Identifier and returns
it to the Client along with a Registration Access Token and a
reference to the Client's Client Configuration Endpoint.
d. The Client stores the returned response from the Authorization
Server. At a minimum, it should know the values of "client_id",
"client_secret" (if present), "registration_access_token", and
"registration_client_uri".
e. The Client uses the its "client_id" and "client_secret" (if
provided) to request OAuth 2.0 tokens using any valid OAuth 2.0
flow.
f. If the Client's "client_secret" expires or otherwise stops
working, the Client sends an HTTP GET request to the
"registration_client_uri" with the "registration_access_token" as
its authorization. This response will contain the Client's
refreshed "client_secret" along with any changed metadata values.
Its "client_id" will remain the same.
g. If the Client needs to update its configuration on the
Authorization Server, it sends an HTTP PUT request to the
"registration_client_uri" with the "registration_access_token" as
its authorization. This response will contain the Client's
changed metadata values. Its "client_id" will remain the same.
h. If the Client is uninstalled or otherwise deprovisioned, it can
send an HTTP DELETE request to the "registration_client_uri" with
the "registration_access_token" as its authorization. This will
effectively deprovision the client from the Authorization Server.
1.4.2. Protected Registration
An Authorization Server may require an Initial Access Token for
requests to its Registration Endpoint. While the method by which a
Client receives this Initial Access Token and the method by which the
Authorization Server validates this Initial Access Token are out of
scope for this specification, a common approach is for the Developer
to use a manual pre-registration portal at the Authorization Server
that issues an Initial Access Token to the Developer. This allows
the Developer to package the Initial Access Token with different
instances of the application. While each copy of the application
would get its own Client Identifier (and Registration Access Token),
all instances of the application would be tied back to the Developer
by their use of this initial registration token.
a. A Developer is creating a Client to use an Authorization Server
and knows that instances of the Client will dynamically register
at runtime, but that the Authorization Server requires
authorization the registration endpoint.
b. The Developer visits a manual pre-registration page at the
Authorization Server and is issued an Initial Access Token in the
form of an OAuth 2.0 Bearer Token [RFC6750].
c. The Developer packages that token with all instances of the
Client application.
d. The Client needs to get OAuth 2.0 tokens from an Authorization
Server, but the Client does not have a Client Identifier for that
Authorization Server.
e. The Client sends an HTTP POST request to the Client Registration
Endpoint at the Authorization Server with its metadata, and the
Initial Access Token as its authorization.
f. The Authorization Server issues a Client Identifier and returns
it to the Client along with a Registration Access Token and a
reference to the Client's Client Configuration Endpoint.
g. The Client stores the returned response from the Authorization
Server. At a minimum, it should know the values of "client_id",
"client_secret" (if present), "registration_access_token", and
"registration_client_uri".
h. The Client uses the its "client_id" and "client_secret" (if
provided) to request OAuth 2.0 tokens using any supported OAuth
2.0 flow.
i. If the Client's "client_secret" expires or otherwise stops
working, the Client sends an HTTP GET request to the
"registration_client_uri" with the "registration_access_token" as
its authorization. This response will contain the Client's
refreshed "client_secret" along with any metadata values
registered to that client, some of which may have changed. Its
"client_id" will remain the same.
j. If the Client needs to update its configuration on the
Authorization Server, it sends an HTTP PUT request to the
"registration_client_uri" with the "registration_access_token" as
its authorization. The response will contain the Client's
changed metadata values. Its "client_id" will remain the same.
k. If the Client is uninstalled or otherwise deprovisioned, it can
send an HTTP DELETE request to the "registration_client_uri" with
the "registration_access_token" as its authorization. This will
effectively deprovision the client from the Authorization Server.
1.4.3. Developer Automation
The Dynamic Registration protocol can also be used in place of a
manual registration portal, for instance as part of an automated
build and deployment process. An Authorization Server may require an
Initial Access Token for requests to its Registration Endpoint, as
described in Protected Registration (Section 1.4.2). However, in
this scenario, the Developer manages the Client's registration
instead of the Client itself. Therefore, the initial registration
token and Registration Access Token all remain with the Developer.
The Developer packages the Client Identifier with the Client as part
of its build process.
a. A Developer is creating a Client to use an Authorization Server
and knows that instances of the Client will not dynamically
register at runtime.
b. If required for registrations at the Authorization Server, the
Developer visits a manual pre-registration page at the
Authorization Server and is issued an Initial Access Token in the
form of an OAuth 2.0 Bearer Token [RFC6750].
c. The Developer configures his build environment to send an HTTP
POST request to the Client Registration Endpoint at the
Authorization Server with the Client's metadata, using the
Initial Access Token obtained the previous step as an OAuth 2.0
Bearer Token [RFC6750], if needed.
d. The Authorization Server issues a Client Identifier and returns
it to the Developer along with a Registration Access Token and a
reference to the Client's Client Configuration Endpoint.
e. The Developer packages the Client Identifier with the Client and
stores the "registration_access_token", and
"registration_client_uri" in the deployment system.
f. The Client uses the its "client_id" and "client_secret" (if
provided) to request OAuth 2.0 tokens using any supported OAuth
2.0 flow.
g. If the Client's "client_secret" expires or otherwise stops
working, the Developer's deployment system sends an HTTP GET
request to the "registration_client_uri" with the
"registration_access_token" as its authorization. This response
will contain the Client's refreshed "client_secret" along with
any changed metadata values. Its "client_id" will remain the
same. These new values will then be packaged and shipped to or
retrieved by instances of the Client, if necessary.
h. If the Developer needs to update its configuration on the
Authorization Server, the deployment system sends an HTTP PUT
request to the "registration_client_uri" with the
"registration_access_token" as its authorization. This response
will contain the Client's changed metadata values. Its
"client_id" will remain the same. These new values will then be
packaged and shipped to or retrieved by instances of the Client,
if necessary.
i. If the Client is deprovisioned, the Developer's deployment system
can send an HTTP DELETE request to the "registration_client_uri"
with the "registration_access_token" as its authorization. This
will effectively deprovision the client from the Authorization
Server and prevent any instances of the client from functioning.
2. Client Metadata 2. Client Metadata
Clients generally have an array of metadata associated with their Clients generally have an array of metadata associated with their
unique Client Identifier at the Authorization Server. These can unique Client Identifier at the Authorization Server. These can
range from human-facing display strings, such as a client name, to range from human-facing display strings, such as a client name, to
items that impact the security of the protocol, such as the list of items that impact the security of the protocol, such as the list of
valid redirect URIs. valid redirect URIs.
The client metadata values serve two parallel purposes in the overall The client metadata values serve two parallel purposes in the overall
skipping to change at page 4, line 41 skipping to change at page 10, line 43
Extensions and profiles of this specification MAY expand this list, Extensions and profiles of this specification MAY expand this list,
but Authorization Servers MUST accept or ignore all parameters on but Authorization Servers MUST accept or ignore all parameters on
this list. The Authorization Server MUST ignore any additional this list. The Authorization Server MUST ignore any additional
parameters sent by the Client that it does not understand. parameters sent by the Client that it does not understand.
redirect_uris redirect_uris
Array of redirect URIs for use in redirect-based flows such as the Array of redirect URIs for use in redirect-based flows such as the
Authorization Code and Implicit grant types. It is RECOMMENDED Authorization Code and Implicit grant types. It is RECOMMENDED
that clients using these flows register this parameter, and an that clients using these flows register this parameter, and an
Authorization Server SHOULD require registration of valid redirect Authorization Server SHOULD require registration of valid redirect
URIs for all clients that use these grant types in order to URIs for all clients that use these grant types to protect against
protect against token and credential theft attacks. token and credential theft attacks.
client_name client_name
Human-readable name of the Client to be presented to the user. If Human-readable name of the Client to be presented to the user. If
omitted, the Authorization Server MAY display the raw "client_id" omitted, the Authorization Server MAY display the raw "client_id"
value to the user instead. It is RECOMMENDED that clients always value to the user instead. It is RECOMMENDED that clients always
send this field. The value of this field MAY be internationalized send this field. The value of this field MAY be internationalized
as described in Human Readable Client Metadata (Section 2.2). as described in Human Readable Client Metadata (Section 2.2).
client_uri client_uri
URL of the homepage of the Client. If present, the server SHOULD URL of the homepage of the Client. If present, the server SHOULD
display this URL to the end user in a clickable fashion. It is display this URL to the end user in a clickable fashion. It is
RECOMMENDED that clients always send this field. The value of RECOMMENDED that clients always send this field. The value of
this field MAY be internationalized as described in Human Readable this field MUST point to a valid Web page. The value of this
field MAY be internationalized as described in Human Readable
Client Metadata (Section 2.2). Client Metadata (Section 2.2).
logo_uri logo_uri
URL that references a logo for the Client. If present, the server URL that references a logo for the Client. If present, the server
SHOULD display this image to the end user during approval. The SHOULD display this image to the end user during approval. The
value of this field MAY be internationalized as described in Human value of this field MUST point to a valid image file. The value
of this field MAY be internationalized as described in Human
Readable Client Metadata (Section 2.2). Readable Client Metadata (Section 2.2).
contacts contacts
Array of email addresses for people responsible for this Client. Array of email addresses for people responsible for this Client.
The Authorization Server MAY make these addresses available to end The Authorization Server MAY make these addresses available to end
users for support requests for the Client. An Authorization users for support requests for the Client. An Authorization
Server MAY use these email addresses as identifiers for an Server MAY use these email addresses as identifiers for an
administrative page for this client. administrative page for this client.
tos_uri tos_uri
URL that points to a human-readable Terms of Service for the URL that points to a human-readable Terms of Service document for
the Client. The Authorization Server SHOULD display this URL to
the End-User if it is given. The Terms of Service usually
describe a contractual relationship between the End-User and the
Client that the End-User accepts when authorizing the Client. The
value of this field MUST point to a valid Web page. The value of
this field MAY be internationalized as described in Human Readable
Client Metadata (Section 2.2).
policy_uri
URL that points to a human-readable Policy document for the
Client. The Authorization Server SHOULD display this URL to the Client. The Authorization Server SHOULD display this URL to the
End-User if it is given. The value of this field MAY be End-User if it is given. The Policy usually describes how an End-
User's data will be used by the Client. The value of this field
MUST point to a valid Web page. The value of this field MAY be
internationalized as described in Human Readable Client Metadata internationalized as described in Human Readable Client Metadata
(Section 2.2). (Section 2.2).
token_endpoint_auth_method token_endpoint_auth_method
The requested authentication type for the Token Endpoint. Valid The requested authentication method for the Token Endpoint.
values are: Values defined by this specification are:
* "none": this is a public client as defined in OAuth 2.0 and * "none": The client is a public client as defined in OAuth 2.0
does not have a client secret and does not have a client secret.
* "client_secret_post": the client uses the HTTP POST parameters * "client_secret_post": The client uses the HTTP POST parameters
defined in OAuth 2.0 section 2.3.1 defined in OAuth 2.0 section 2.3.1.
* "client_secret_basic": the client uses HTTP Basic defined in * "client_secret_basic": the client uses HTTP Basic defined in
OAuth 2.0 section 2.3.1 OAuth 2.0 section 2.3.1
* "client_secret_jwt": the client uses the JWT Assertion Additional values can be defined via the IANA OAuth Token Endpoint
[OAuth.JWT] profile with a symmetric signature using the Authentication Methods registry Section 6.1. Absolute URIs can
"client_secret" issued by the server also be used as values for this parameter. If unspecified or
omitted, the default is "client_secret_basic", denoting HTTP Basic
* "private_key_jwt": the client uses the JWT Assertion Authentication Scheme as specified in Section 2.3.1 of OAuth 2.0.
[OAuth.JWT] profile with its own private key, usually with its
public key location indicated by the "jwks_uri" field
Other authentication methods may be defined by extension. If
unspecified or omitted, the default is "client_secret_basic",
denoting HTTP Basic Authentication Scheme as specified in
Section 2.3.1 of OAuth 2.0. Other authentication methods MAY be
supported by using an absolute URI as the value of this parameter.
scope scope
Space separated list of scope values (as described in OAuth 2.0 Space separated list of scope values (as described in OAuth 2.0
Section 3.3 [RFC6749]) that the client can use when requesting Section 3.3 [RFC6749]) that the client can use when requesting
access tokens. The semantics of values in this list is service access tokens. The semantics of values in this list is service
specific. If omitted, an Authorization Server MAY register a specific. If omitted, an Authorization Server MAY register a
Client with a default set of scopes. Client with a default set of scopes.
grant_types grant_types
Array of OAuth 2.0 grant types that the Client may use. These Array of OAuth 2.0 grant types that the Client may use. These
grant types are defined as follows: grant types are defined as follows:
* "authorization_code": The Authorization Code Grant described in * "authorization_code": The Authorization Code Grant described in
OAuth 2.0 Section 4.1 OAuth 2.0 Section 4.1
* "implicit": The Implicit Grant described in OAuth 2.0 * "implicit": The Implicit Grant described in OAuth 2.0 Section
Section 4.2 4.2
* "password": The Resource Owner Password Credentials Grant * "password": The Resource Owner Password Credentials Grant
described in OAuth 2.0 Section 4.3 described in OAuth 2.0 Section 4.3
* "client_credentials": The Client Credentials Grant described in * "client_credentials": The Client Credentials Grant described in
OAuth 2.0 Section 4.4 OAuth 2.0 Section 4.4
* "refresh_token": The Refresh Token Grant described in OAuth 2.0 * "refresh_token": The Refresh Token Grant described in OAuth 2.0
Section 6. Section 6.
skipping to change at page 7, line 8 skipping to change at page 13, line 16
grant type extensions to OAuth 2.0. The extension process is grant type extensions to OAuth 2.0. The extension process is
described in OAuth 2.0 Section 2.5, and the value of this described in OAuth 2.0 Section 2.5, and the value of this
parameter MUST be the same as the value of the "grant_type" parameter MUST be the same as the value of the "grant_type"
parameter passed to the Token Endpoint defined in the extension. parameter passed to the Token Endpoint defined in the extension.
response_types response_types
Array of the OAuth 2.0 response types that the Client may use. Array of the OAuth 2.0 response types that the Client may use.
These response types are defined as follows: These response types are defined as follows:
* "code": The Authorization Code response described in OAuth 2.0 * "code": The Authorization Code response described in OAuth 2.0
Section 4.1 Section 4.1.
* "token": The Implicit response described in OAuth 2.0 * "token": The Implicit response described in OAuth 2.0 Section
Section 4.2 4.2.
Authorization Servers MAY allow for other values as defined in Authorization Servers MAY allow for other values as defined in
response type extensions to OAuth 2.0. The extension process is response type extensions to OAuth 2.0. The extension process is
described in OAuth 2.0 Section 2.5, and the value of this described in OAuth 2.0 Section 2.5, and the value of this
parameter MUST be the same as the value of the "response_type" parameter MUST be the same as the value of the "response_type"
parameter passed to the Authorization Endpoint defined in the parameter passed to the Authorization Endpoint defined in the
extension. extension.
policy_uri
A URL location that the Client provides to the End-User to read
about the how the profile data will be used. The Authorization
Server SHOULD display this URL to the End-User if it is given.
The value of this field MAY be internationalized as described in
Human Readable Client Metadata (Section 2.2).
jwks_uri jwks_uri
URL for the Client's JSON Web Key Set [JWK] document that is used URL for the Client's JSON Web Key Set [JWK] document representing
for signing requests, such as requests to the Token Endpoint using the client's public keys. The value of this field MUST point to a
the "private_key_jwt" assertion client credential. The keys MAY valid JWK Set. These keys MAY also be used for higher level
also be used for higher level protocols that require signing or protocols that require signing or encryption.
encryption.
2.1. Relationship Between Grant Types and Response Types 2.1. Relationship Between Grant Types and Response Types
The "grant_types" and "response_types" values described above are The "grant_types" and "response_types" values described above are
partially orthogonal, as they refer to arguments passed to different partially orthogonal, as they refer to arguments passed to different
endpoints in the OAuth protocol. However, they are related in that endpoints in the OAuth protocol. However, they are related in that
the "grant_types" available to a client influence the the "grant_types" available to a client influence the
"response_types" that the client is allowed to use, and vice versa. "response_types" that the client is allowed to use, and vice versa.
For instance, a "grant_types" value that includes For instance, a "grant_types" value that includes
"authorization_code" implies a "response_types" value that includes "authorization_code" implies a "response_types" value that includes
skipping to change at page 8, line 12 skipping to change at page 14, line 15
+-----------------------------------------------+-------------------+ +-----------------------------------------------+-------------------+
| grant_types value includes: | response_types | | grant_types value includes: | response_types |
| | value includes: | | | value includes: |
+-----------------------------------------------+-------------------+ +-----------------------------------------------+-------------------+
| authorization_code | code | | authorization_code | code |
| implicit | token | | implicit | token |
| password | (none) | | password | (none) |
| client_credentials | (none) | | client_credentials | (none) |
| refresh_token | (none) | | refresh_token | (none) |
| urn:ietf:params:oauth:grant-type:jwt-bearer | (none) | | urn:ietf:params:oauth:grant-type:jwt-bearer | (none) |
| urn:ietf:params:oauth:grant-type:saml2-bearer | (none) |
+-----------------------------------------------+-------------------+ +-----------------------------------------------+-------------------+
Extensions and profiles of this document that introduce new values to Extensions and profiles of this document that introduce new values to
either the "grant_types" or "response_types" parameter MUST document either the "grant_types" or "response_types" parameter MUST document
all correspondences between the parameter types. all correspondences between these two parameter types.
2.2. Human Readable Client Metadata 2.2. Human Readable Client Metadata
Human-readable Client Metadata values and Client Metadata values that Human-readable Client Metadata values and Client Metadata values that
reference human-readable values MAY be represented in multiple reference human-readable values MAY be represented in multiple
languages and scripts. For example, the values of fields such as languages and scripts. For example, the values of fields such as
"client_name", "tos_uri", "policy_uri", "logo_uri", and "client_uri" "client_name", "tos_uri", "policy_uri", "logo_uri", and "client_uri"
might have multiple locale-specific values in some Client might have multiple locale-specific values in some Client
registrations. registrations.
skipping to change at page 8, line 46 skipping to change at page 14, line 50
case insensitive, implementations SHOULD interpret the language tag case insensitive, implementations SHOULD interpret the language tag
values supplied in a case insensitive manner. Per the values supplied in a case insensitive manner. Per the
recommendations in BCP47, language tag values used in Metadata member recommendations in BCP47, language tag values used in Metadata member
names should only be as specific as necessary. For instance, using names should only be as specific as necessary. For instance, using
"fr" might be sufficient in many contexts, rather than "fr-CA" or "fr" might be sufficient in many contexts, rather than "fr-CA" or
"fr-FR". "fr-FR".
For example, a Client could represent its name in English as For example, a Client could represent its name in English as
""client_name#en": "My Client"" and its name in Japanese as ""client_name#en": "My Client"" and its name in Japanese as
""client_name#ja-Jpan-JP": ""client_name#ja-Jpan-JP":
"クライアント名"" within "\u30AF\u30E9\u30A4\u30A2\u30F3\u30C8\u540D"" within the same
the same registration request. The Authorization Server MAY display registration request. The Authorization Server MAY display any or
any or all of these names to the Resource Owner during the all of these names to the Resource Owner during the authorization
authorization step, choosing which name to display based on system step, choosing which name to display based on system configuration,
configuration, user preferences or other factors. user preferences or other factors.
If any human-readable field is sent without a language tag, parties If any human-readable field is sent without a language tag, parties
using it MUST NOT make any assumptions about the language, character using it MUST NOT make any assumptions about the language, character
set, or script of the string value, and the string value MUST be used set, or script of the string value, and the string value MUST be used
as-is wherever it is presented in a user interface. To facilitate as-is wherever it is presented in a user interface. To facilitate
interoperability, it is RECOMMENDED that clients and servers use a interoperability, it is RECOMMENDED that clients and servers use a
human-readable field without any language tags in addition to any human-readable field without any language tags in addition to any
language-specific fields, and it is RECOMMENDED that any human- language-specific fields, and it is RECOMMENDED that any human-
readable fields sent without language tags contain values suitable readable fields sent without language tags contain values suitable
for display on a wide variety of systems. for display on a wide variety of systems.
skipping to change at page 9, line 34 skipping to change at page 15, line 36
accessed using the JavaScript syntax "j["client_name#en-us"]". accessed using the JavaScript syntax "j["client_name#en-us"]".
3. Client Registration Endpoint 3. Client Registration Endpoint
The Client Registration Endpoint is an OAuth 2.0 Endpoint defined in The Client Registration Endpoint is an OAuth 2.0 Endpoint defined in
this document that is designed to allow a Client to register itself this document that is designed to allow a Client to register itself
with the Authorization Server. The Client Registration Endpoint MUST with the Authorization Server. The Client Registration Endpoint MUST
accept HTTP POST messages with request parameters encoded in the accept HTTP POST messages with request parameters encoded in the
entity body using the "application/json" format. The Client entity body using the "application/json" format. The Client
Registration Endpoint MUST be protected by a transport-layer security Registration Endpoint MUST be protected by a transport-layer security
mechanism, and the server MUST support TLS 1.2 RFC 5246 [RFC5246] and mechanism, and the server MUST support TLS 1.2 RFC 5246 [RFC5246]
/or TLS 1.0 [RFC2246] and MAY support additional transport-layer and/or TLS 1.0 [RFC2246] and MAY support additional transport-layer
mechanisms meeting its security requirements. When using TLS, the mechanisms meeting its security requirements. When using TLS, the
Client MUST perform a TLS/SSL server certificate check, per RFC 6125 Client MUST perform a TLS/SSL server certificate check, per RFC 6125
[RFC6125]. [RFC6125].
The Client Registration Endpoint MAY accept an initial authorization The Client Registration Endpoint MAY accept an Initial Access Token
credential in the form of an OAuth 2.0 [RFC6749] access token in in the form of an OAuth 2.0 [RFC6749] access token to limit
order to limit registration to only previously authorized parties. registration to only previously authorized parties. The method by
The method by which this access token is obtained by the registrant which the Initial Access Token is obtained by the registrant is
is generally out-of-band and is out of scope of this specification. generally out-of-band and is out of scope of this specification.
In order to support open registration and facilitate wider To support open registration and facilitate wider interoperability,
interoperability, the Client Registration Endpoint SHOULD allow the Client Registration Endpoint SHOULD allow initial registration
initial registration requests with no authentication. These requests requests with no authentication. These requests MAY be rate-limited
MAY be rate-limited or otherwise limited to prevent a denial-of- or otherwise limited to prevent a denial-of-service attack on the
service attack on the Client Registration Endpoint. Client Registration Endpoint.
In order to facilitate registered clients updating their information, To facilitate registered clients updating their information, the
the Client Registration Endpoint issues a Request Access Token for Client Registration Endpoint issues a Request Access Token for
clients to securely identify themselves in future connections to the clients to securely identify themselves in future connections to the
Client Configuration Endpoint (Section 4). As such, the Client Client Configuration Endpoint (Section 4). As such, the Client
Configuration Endpoint MUST accept requests with OAuth 2.0 Bearer Configuration Endpoint MUST accept requests with OAuth 2.0 Bearer
Tokens [RFC6750] for these operations, whether or not the initial Tokens [RFC6750] for these operations, whether or not the initial
registration call requires authentication of some form. registration call requires authentication of some form.
The Client Registration Endpoint MUST ignore all parameters it does The Client Registration Endpoint MUST ignore all parameters it does
not understand. not understand.
3.1. Client Registration Request 3.1. Client Registration Request
skipping to change at page 10, line 47 skipping to change at page 17, line 17
POST /register HTTP/1.1 POST /register HTTP/1.1
Content-Type: application/json Content-Type: application/json
Accept: application/json Accept: application/json
Host: server.example.com Host: server.example.com
{ {
"redirect_uris":["https://client.example.org/callback", "redirect_uris":["https://client.example.org/callback",
"https://client.example.org/callback2"] "https://client.example.org/callback2"]
"client_name":"My Example Client", "client_name":"My Example Client",
"client_name#ja-Jpan-JP":
"\u30AF\u30E9\u30A4\u30A2\u30F3\u30C8\u540D",
"token_endpoint_auth_method":"client_secret_basic", "token_endpoint_auth_method":"client_secret_basic",
"scope":"read write dolphin", "scope":"read write dolphin",
"logo_uri":"https://client.example.org/logo.png", "logo_uri":"https://client.example.org/logo.png",
"jwks_uri":"https://client.example.org/my_public_keys.jwks" "jwks_uri":"https://client.example.org/my_public_keys.jwks"
} }
Alternatively, if the client has been provisioned with an initial
authorization credential, it could send the following registration Alternatively, if the developer or the client has been provisioned
request to the Client Registration Endpoint: with an Initial Access Token, he or it sends the following
registration request to the Client Registration Endpoint. The method
by which the Initial Access Token is obtained is out of scope for
this specification.
Following is a non-normative example request (with line wraps for Following is a non-normative example request (with line wraps for
display purposes only): display purposes only):
POST /register HTTP/1.1 POST /register HTTP/1.1
Content-Type: application/json Content-Type: application/json
Accept: application/json Accept: application/json
Authorization: Bearer ey23f2.adfj230.af32-developer321 Authorization: Bearer ey23f2.adfj230.af32-developer321
Host: server.example.com Host: server.example.com
{ {
"redirect_uris":["https://client.example.org/callback", "redirect_uris":["https://client.example.org/callback",
"https://client.example.org/callback2"] "https://client.example.org/callback2"]
"client_name":"My Example Client", "client_name":"My Example Client",
"client_name#ja-Jpan-JP":
"\u30AF\u30E9\u30A4\u30A2\u30F3\u30C8\u540D",
"token_endpoint_auth_method":"client_secret_basic", "token_endpoint_auth_method":"client_secret_basic",
"scope":"read write dolphin", "scope":"read write dolphin",
"logo_uri":"https://client.example.org/logo.png", "logo_uri":"https://client.example.org/logo.png",
"jwks_uri":"https://client.example.org/my_public_keys.jwks" "jwks_uri":"https://client.example.org/my_public_keys.jwks"
} }
3.2. Client Registration Response 3.2. Client Registration Response
Upon successful registration, the Authorization Server generates a Upon successful registration, the Authorization Server generates a
new Client Identifier for the client. This Client Identifier MUST be new Client Identifier for the client. This Client Identifier MUST be
skipping to change at page 11, line 42 skipping to change at page 18, line 20
server responds with an HTTP 201 Created code and a body of type server responds with an HTTP 201 Created code and a body of type
"application/json" with content described in Client Information "application/json" with content described in Client Information
Response (Section 5.1). Response (Section 5.1).
Upon an unsuccessful registration, the Authorization Server responds Upon an unsuccessful registration, the Authorization Server responds
with an error as described in Client Registration Error with an error as described in Client Registration Error
(Section 5.2). (Section 5.2).
4. Client Configuration Endpoint 4. Client Configuration Endpoint
The Client Configuration Endpoint is an OAuth 2.0 protected endpoint The Client Configuration Endpoint is an OAuth 2.0 protected resource
that is provisioned by the server for a specific client to be able to that is provisioned by the server for a specific client to be able to
view and update its registered information. The Client MUST include view and update its registered information. The location of this
its Registration Access Token in all calls to this endpoint as an endpoint is communicated to the Client through the
OAuth 2.0 Bearer Token [RFC6750]. "registration_client_uri" member of the Client Information Response
(Section 5.1). The Client MUST use its Registration Access Token in
all calls to this endpoint as an OAuth 2.0 Bearer Token [RFC6750].
Operations on this endpoint are switched through the use of different Operations on this endpoint are switched through the use of different
HTTP methods [RFC2616]. HTTP methods [RFC2616].
4.1. Forming the Client Configuration Endpoint URL 4.1. Forming the Client Configuration Endpoint URL
The Authorization Server MUST provide the client with the fully The Authorization Server MUST provide the client with the fully
qualified URL in the "registration_client_uri" element of the Client qualified URL in the "registration_client_uri" element of the Client
Information Response (Section 5.1). The Authorization Server MUST Information Response (Section 5.1). The Authorization Server MUST
NOT expect the client to construct or discover this URL on its own. NOT expect the client to construct or discover this URL on its own.
The Client MUST use the URL as given by the server and MUST NOT The Client MUST use the URL as given by the server and MUST NOT
construct this URL from component pieces. construct this URL from component pieces.
Depending on deployment characteristics, the Client Configuration Depending on deployment characteristics, the Client Configuration
Endpoint URL may take any number of forms. It is RECOMMENDED that Endpoint URL may take any number of forms. It is RECOMMENDED that
this endpoint URL be formed through the use of a server-constructed this endpoint URL be formed through the use of a server-constructed
URL string which combines the Client Registration Endpoint's URL and URL string which combines the Client Registration Endpoint's URL and
the issued client_id for this Client, with the latter as either a the issued "client_id" for this Client, with the latter as either a
path parameter or a query parameter. For example, a Client with the path parameter or a query parameter. For example, a Client with the
Client ID "s6BhdRkqt3" could be given a Client Configuration Endpoint Client ID "s6BhdRkqt3" could be given a Client Configuration Endpoint
URL of "https://server.example.com/register/s6BhdRkqt3" (path URL of "https://server.example.com/register/s6BhdRkqt3" (path
parameter) or of "https://server.example.com/ parameter) or of
register?client_id=s6BhdRkqt3" (query parameter). In both of these "https://server.example.com/register?client_id=s6BhdRkqt3" (query
cases, the client simply follows the URL as given. parameter). In both of these cases, the client simply uses the URL
as given.
These common patterns can help the Server to more easily determine These common patterns can help the Server to more easily determine
the client to which the request pertains, which MUST be matched the client to which the request pertains, which MUST be matched
against the client to which the Registration Access Token was issued. against the client to which the Registration Access Token was issued.
If desired, the server MAY simply return the Client Registration If desired, the server MAY simply return the Client Registration
Endpoint URL as the Client Configuration Endpoint URL and change Endpoint URL as the Client Configuration Endpoint URL and change
behavior based on the authentication context provided by the behavior based on the authentication context provided by the
Registration Access Token. Registration Access Token.
4.2. Client Read Request 4.2. Client Read Request
In order to read the current configuration of the Client on the To read the current configuration of the Client on the Authorization
Authorization Server, the Client makes an HTTP GET request to the Server, the Client makes an HTTP GET request to the Client
Client Configuration Endpoint, authenticating with its Registration Configuration Endpoint, authenticating with its Registration Access
Access Token. Token.
Following is a non-normative example request (with line wraps for Following is a non-normative example request (with line wraps for
display purposes only): display purposes only):
GET /register/s6BhdRkqt3 HTTP/1.1 GET /register/s6BhdRkqt3 HTTP/1.1
Accept: application/json Accept: application/json
Host: server.example.com Host: server.example.com
Authorization: Bearer reg-23410913-abewfq.123483 Authorization: Bearer reg-23410913-abewfq.123483
Upon successful read of the information for a currently active Upon successful read of the information for a currently active
Client, the Authorization Server responds with an HTTP 200 OK with Client, the Authorization Server responds with an HTTP 200 OK with
content type of "application/json" and a payload as described in content type of "application/json" and a payload as described in
Client Information Response (Section 5.1). Client Information Response (Section 5.1). Some values in the
response, including the "client_secret" and
"registration_access_token", MAY be different from those in the
initial registration response. If the Authorization Server includes
a new Client Secret and/or Registration Access Token in its response,
the Client MUST immediately discard its previous Client Secret and/or
Registration Access Token. The value of the "client_id" MUST NOT
change from the initial registration response.
If the client does not exist on this server, the server MUST respond If the client does not exist on this server, the server MUST respond
with HTTP 401 Unauthorized and the Registration Access Token used to with HTTP 401 Unauthorized and the Registration Access Token used to
make this request SHOULD be immediately revoked. make this request SHOULD be immediately revoked.
If the Client does not have permission to read its record, the server If the Client does not have permission to read its record, the server
MUST return an HTTP 403 Forbidden. MUST return an HTTP 403 Forbidden.
4.3. Client Update Request 4.3. Client Update Request
skipping to change at page 13, line 28 skipping to change at page 20, line 13
by the Registration Access Token issued to the client. by the Registration Access Token issued to the client.
The Client sends an HTTP PUT to the Client Configuration Endpoint The Client sends an HTTP PUT to the Client Configuration Endpoint
with a content type of "application/json". The HTTP Entity Payload with a content type of "application/json". The HTTP Entity Payload
is a JSON [RFC4627] document consisting of a JSON object and all is a JSON [RFC4627] document consisting of a JSON object and all
parameters as top- level members of that JSON object. parameters as top- level members of that JSON object.
This request MUST include all fields described in Client Metadata This request MUST include all fields described in Client Metadata
(Section 2) as returned to the Client from a previous register, read, (Section 2) as returned to the Client from a previous register, read,
or update operation. The Client MUST NOT include the or update operation. The Client MUST NOT include the
"registration_access_token", "registration_client_uri", "expires_at", "registration_access_token", "registration_client_uri",
or "issued_at" fields described in Client Information Response "client_secret_expires_at", or "client_id_issued_at" fields described
(Section 5.1). in Client Information Response (Section 5.1).
Valid values of Client Metadata fields in this request MUST replace, Valid values of Client Metadata fields in this request MUST replace,
not augment, the values previously associated with this Client. not augment, the values previously associated with this Client.
Omitted fields MUST be treated as null or empty values by the server. Omitted fields MUST be treated as null or empty values by the server.
The Client MUST include its "client_id" field in the request, and it The Client MUST include its "client_id" field in the request, and it
MUST be the same as its currently-issued Client Identifier. If the MUST be the same as its currently-issued Client Identifier. If the
client includes the "client_secret" field in the request, the value client includes the "client_secret" field in the request, the value
of this field MUST match the currently-issued Client Secret for that of this field MUST match the currently-issued Client Secret for that
Client. The Client MUST NOT be allowed to overwrite its existing Client. The Client MUST NOT be allowed to overwrite its existing
skipping to change at page 14, line 23 skipping to change at page 21, line 22
{ {
"client_id":"s6BhdRkqt3", "client_id":"s6BhdRkqt3",
"client_secret": "cf136dc3c1fc93f31185e5885805d", "client_secret": "cf136dc3c1fc93f31185e5885805d",
"redirect_uris":["https://client.example.org/callback", "redirect_uris":["https://client.example.org/callback",
"https://client.example.org/alt"], "https://client.example.org/alt"],
"scope": "read write dolphin", "scope": "read write dolphin",
"grant_types": ["authorization_code", "refresh_token"] "grant_types": ["authorization_code", "refresh_token"]
"token_endpoint_auth_method": "client_secret_basic", "token_endpoint_auth_method": "client_secret_basic",
"jwks_uri": "https://client.example.org/my_public_keys.jwks" "jwks_uri": "https://client.example.org/my_public_keys.jwks"
"client_name":"My New Example", "client_name":"My New Example",
"client_name#fr":"Mon Nouvel Exemple",
"logo_uri":"https://client.example.org/newlogo.png" "logo_uri":"https://client.example.org/newlogo.png"
"logo_uri#fr":"https://client.example.org/fr/newlogo.png"
} }
Upon successful update, the Authorization Server responds with an Upon successful update, the Authorization Server responds with an
HTTP 200 OK Message with content type "application/json" and a HTTP 200 OK Message with content type "application/json" and a
payload as described in Client Information Response (Section 5.1). payload as described in Client Information Response (Section 5.1).
The Authorization Server MAY include a new Client Secret and/or Some values in the response, including the "client_secret" and
Registration Access Token in its response. If so, the Client MUST r"egistration_access_token", MAY be different from those in the
immediately discard its previous Client Secret and/or Registration initial registration response. If the Authorization Server includes
Access Token. a new Client Secret and/or Registration Access Token in its response,
the Client MUST immediately discard its previous Client Secret and/or
Registration Access Token. The value of the "client_id" MUST NOT
change from the initial registration response.
If the client does not exist on this server, the server MUST respond If the client does not exist on this server, the server MUST respond
with HTTP 401 Unauthorized, and the Registration Access Token used to with HTTP 401 Unauthorized, and the Registration Access Token used to
make this request SHOULD be immediately revoked. make this request SHOULD be immediately revoked.
If the Client is not allowed to update its records, the server MUST If the Client is not allowed to update its records, the server MUST
respond with HTTP 403 Forbidden. respond with HTTP 403 Forbidden.
If the Client attempts to set an invalid metadata field and the If the Client attempts to set an invalid metadata field and the
Authorization Server does not set a default value, the Authorization Authorization Server does not set a default value, the Authorization
Server responds with an error as described in Client Registration Server responds with an error as described in Client Registration
Error Response (Section 5.2). Error Response (Section 5.2).
4.4. Client Delete Request 4.4. Client Delete Request
In order to deprovision itself on the Authorization Server, the To deprovision itself on the Authorization Server, the Client makes
Client makes an HTTP DELETE request to the Client Configuration an HTTP DELETE request to the Client Configuration Endpoint. This
Endpoint. This request is authenticated by the Registration Access request is authenticated by the Registration Access Token issued to
Token issued to the client. the client.
Following is a non-normative example request (with line wraps for Following is a non-normative example request (with line wraps for
display purposes only): display purposes only):
DELETE /register/s6BhdRkqt3 HTTP/1.1 DELETE /register/s6BhdRkqt3 HTTP/1.1
Accept: application/json Accept: application/json
Host: server.example.com Host: server.example.com
Authorization: Bearer reg-23410913-abewfq.123483 Authorization: Bearer reg-23410913-abewfq.123483
A successful delete action will invalidate the client_id, A successful delete action will invalidate the "client_id",
client_secret, and registration_access_token for this client, thereby "client_secret", and "registration_access_token" for this client,
preventing the client_id from being used at either the Authorization thereby preventing the "client_id" from being used at either the
Endpoint or Token Endpoint of the Authorization Server. The Authorization Endpoint or Token Endpoint of the Authorization Server.
Authorization Server SHOULD immediately invalidate all existing The Authorization Server SHOULD immediately invalidate all existing
authorization grants and currently-active tokens associated with this authorization grants and currently-active tokens associated with this
Client. Client.
If a Client has been successfully deprovisioned, the Authorization If a Client has been successfully deprovisioned, the Authorization
Server responds with an HTTP 204 No Content message. Server responds with an HTTP 204 No Content message.
If the server does not support the delete method, the server MUST If the server does not support the delete method, the server MUST
respond with an HTTP 405 Not Supported. respond with an HTTP 405 Not Supported.
If the client does not exist on this server, the server MUST respond If the client does not exist on this server, the server MUST respond
skipping to change at page 16, line 22 skipping to change at page 23, line 26
client_id client_id
REQUIRED. The unique Client identifier, MUST NOT be currently REQUIRED. The unique Client identifier, MUST NOT be currently
valid for any other registered Client. valid for any other registered Client.
client_secret client_secret
OPTIONAL. The Client secret. If issued, this MUST be unique for OPTIONAL. The Client secret. If issued, this MUST be unique for
each "client_id". This value is used by confidential clients to each "client_id". This value is used by confidential clients to
authenticate to the Token Endpoint as described in OAuth 2.0 authenticate to the Token Endpoint as described in OAuth 2.0
Section 2.3.1. Section 2.3.1.
expires_at client_id_issued_at
OPTIONAL. Time at which the Client Identifier was issued. The
time is represented as the number of seconds from 1970-01-
01T0:0:0Z as measured in UTC until the date/time.
client_secret_expires_at
REQUIRED if "client_secret" is issued. Time at which the REQUIRED if "client_secret" is issued. Time at which the
"client_secret" will expire or 0 if it will not expire. The time "client_secret" will expire or 0 if it will not expire. The time
is represented as the number of seconds from 1970-01-01T0:0:0Z as is represented as the number of seconds from 1970-01-01T0:0:0Z as
measured in UTC until the date/time. measured in UTC until the date/time.
issued_at
OPTIONAL. Time at which the Client Identifier was issued. The
time is represented as the number of seconds from
1970-01-01T0:0:0Z as measured in UTC until the date/time.
registration_access_token registration_access_token
REQUIRED. The Access token to be used by the client to perform REQUIRED. Access Token that is used at the Client Configuration
actions on the Client Configuration Endpoint. Endpoint to perform subsequent operations upon the Client
registration.
registration_client_uri registration_client_uri
REQUIRED. The fully qualified URL of the Client Configuration REQUIRED. The fully qualified URL of the Client Configuration
Endpoint for this client. The Client MUST use this URL as given Endpoint for this client. The Client MUST use this URL as given
when communicating with the Client Configuration Endpoint. when communicating with the Client Configuration Endpoint.
Additionally, the Authorization Server MUST return all registered Additionally, the Authorization Server MUST return all registered
metadata (Section 2) about this client, including any fields metadata (Section 2) about this client, including any fields
provisioned by the Authorization Server itself. The Authorization provisioned by the Authorization Server itself. The Authorization
Server MAY reject or replace any of the client's requested metadata Server MAY reject or replace any of the client's requested metadata
skipping to change at page 17, line 6 skipping to change at page 24, line 10
metadata (Section 2) about this client, including any fields metadata (Section 2) about this client, including any fields
provisioned by the Authorization Server itself. The Authorization provisioned by the Authorization Server itself. The Authorization
Server MAY reject or replace any of the client's requested metadata Server MAY reject or replace any of the client's requested metadata
values submitted during the registration or update requests and values submitted during the registration or update requests and
substitute them with suitable values. substitute them with suitable values.
The response is an "application/json" document with all parameters as The response is an "application/json" document with all parameters as
top-level members of a JSON object [RFC4627]. top-level members of a JSON object [RFC4627].
Following is a non-normative example response: Following is a non-normative example response:
HTTP/1.1 200 OK HTTP/1.1 200 OK
Content-Type: application/json Content-Type: application/json
Cache-Control: no-store Cache-Control: no-store
Pragma: no-cache Pragma: no-cache
{ {
"registration_access_token": "reg-23410913-abewfq.123483", "registration_access_token": "reg-23410913-abewfq.123483",
"registration_client_uri": "registration_client_uri":
"https://server.example.com/register/s6BhdRkqt3", "https://server.example.com/register/s6BhdRkqt3",
"client_id":"s6BhdRkqt3", "client_id":"s6BhdRkqt3",
"client_secret": "cf136dc3c1fc93f31185e5885805d", "client_secret": "cf136dc3c1fc93f31185e5885805d",
"expires_at":2893276800 "client_id_issued_at":2893256800
"client_secret_expires_at":2893276800
"client_name":"My Example Client",
"client_name#ja-Jpan-JP":
"\u30AF\u30E9\u30A4\u30A2\u30F3\u30C8\u540D",
"redirect_uris":["https://client.example.org/callback", "redirect_uris":["https://client.example.org/callback",
"https://client.example.org/callback2"] "https://client.example.org/callback2"]
"scope": "read write dolphin", "scope": "read write dolphin",
"grant_types": ["authorization_code", "refresh_token"] "grant_types": ["authorization_code", "refresh_token"]
"token_endpoint_auth_method": "client_secret_basic", "token_endpoint_auth_method": "client_secret_basic",
"logo_uri": "https://client.example.org/logo.png", "logo_uri": "https://client.example.org/logo.png",
"jwks_uri": "https://client.example.org/my_public_keys.jwks" "jwks_uri": "https://client.example.org/my_public_keys.jwks"
} }
5.2. Client Registration Error Response 5.2. Client Registration Error Response
skipping to change at page 18, line 30 skipping to change at page 25, line 40
Pragma: no-cache Pragma: no-cache
{ {
"error":"invalid_redirect_uri", "error":"invalid_redirect_uri",
"error_description":"The redirect URI of http://sketchy.example.com "error_description":"The redirect URI of http://sketchy.example.com
is not allowed for this server." is not allowed for this server."
} }
6. IANA Considerations 6. IANA Considerations
This document makes no requests of IANA. 6.1. OAuth Token Endpoint Authentication Methods Registry
This specification establishes the OAuth Token Endpoint
Authentication Methods registry.
Additional values for use as "token_endpoint_auth_method" metadata
values are registered with a Specification Required ([RFC5226]) after
a two-week review period on the oauth-ext-review@ietf.org mailing
list, on the advice of one or more Designated Experts. However, to
allow for the allocation of values prior to publication, the
Designated Expert(s) may approve registration once they are satisfied
that such a specification will be published.
Registration requests must be sent to the oauth-ext-review@ietf.org
mailing list for review and comment, with an appropriate subject
(e.g., "Request to register token_endpoint_auth_method value:
example").
Within the review period, the Designated Expert(s) will either
approve or deny the registration request, communicating this decision
to the review list and IANA. Denials should include an explanation
and, if applicable, suggestions as to how to make the request
successful.
IANA must only accept registry updates from the Designated Expert(s)
and should direct all requests for registration to the review mailing
list.
6.1.1. Registration Template
Token Endpoint Authorization Method name:
The name requested (e.g., "example"). This name is case
sensitive. Names that match other registered names in a case
insensitive manner SHOULD NOT be accepted.
Change controller:
For Standards Track RFCs, state "IETF". For others, give the name
of the responsible party. Other details (e.g., postal address,
email address, home page URI) may also be included.
Specification document(s):
Reference to the document(s) that specify the token endpoint
authorization method, preferably including a URI that can be used
to retrieve a copy of the document(s). An indication of the
relevant sections may also be included but is not required.
6.1.2. Initial Registry Contents
The OAuth Token Endpoint Authentication Methods registry's initial
contents are:
o Token Endpoint Authorization Method name: "none"
o Change controller: IETF
o Specification document(s): [[ this document ]]
o Token Endpoint Authorization Method name: "client_secret_post"
o Change controller: IETF
o Specification document(s): [[ this document ]]
o Token Endpoint Authorization Method name: "client_secret_basic"
o Change controller: IETF
o Specification document(s): [[ this document ]]
7. Security Considerations 7. Security Considerations
Since requests to the Client Registration Endpoint result in the Since requests to the Client Registration Endpoint result in the
transmission of clear-text credentials (in the HTTP request and transmission of clear-text credentials (in the HTTP request and
response), the server MUST require the use of a transport-layer response), the server MUST require the use of a transport-layer
security mechanism when sending requests to the Registration security mechanism when sending requests to the Registration
Endpoint. The server MUST support TLS 1.2 RFC 5246 [RFC5246] and/or Endpoint. The server MUST support TLS 1.2 RFC 5246 [RFC5246] and/or
TLS 1.0 [RFC2246] and MAY support additional transport-layer TLS 1.0 [RFC2246] and MAY support additional transport-layer
mechanisms meeting its security requirements. When using TLS, the mechanisms meeting its security requirements. When using TLS, the
Client MUST perform a TLS/SSL server certificate check, per RFC 6125 Client MUST perform a TLS/SSL server certificate check, per RFC 6125
[RFC6125]. [RFC6125].
As this endpoint is an OAuth 2.0 Protected Resource, requests to the As this endpoint is an OAuth 2.0 Protected Resource, requests to the
Registration Endpoint SHOULD have some rate limiting on failures to Registration Endpoint SHOULD have some rate limiting on failures to
prevent the Registration Access Token from being disclosed though prevent the Registration Access Token from being disclosed though
repeated access attempts. repeated access attempts.
For clients that use redirect-based grant types such as Authorization For clients that use redirect-based grant types such as Authorization
Code and Implicit, Authorization Servers SHOULD require clients to Code and Implicit, Authorization Servers SHOULD require clients to
pre-register their "redirect_uris". Requiring Clients to do so can register their "redirect_uris". Requiring Clients to do so can help
help mitigate attacks where rogue actors inject and impersonate a mitigate attacks where rogue actors inject and impersonate a validly
validly registered client and intercept its authorization code or registered client and intercept its authorization code or tokens
tokens through an invalid redirect URI. through an invalid redirect URI.
The authorization server MUST treat all client metadata as self- The authorization server MUST treat all client metadata as self-
asserted. A rogue Client might use the name and logo for the asserted. A rogue Client might use the name and logo for the
legitimate Client, which it is trying to impersonate. An legitimate Client, which it is trying to impersonate. An
Authorization Server needs to take steps to mitigate this phishing Authorization Server needs to take steps to mitigate this phishing
risk, since the logo could confuse users into thinking they're risk, since the logo could confuse users into thinking they're
logging in to the legitimate Client. For instance, an Authorization logging in to the legitimate Client. For instance, an Authorization
Server could warn if the domain/site of the logo doesn't match the Server could warn if the domain/site of the logo doesn't match the
domain/site of redirect URIs. An Authorization Server can also domain/site of redirect URIs. An Authorization Server can also
present warning messages to end users about untrusted Clients in all present warning messages to end users about untrusted Clients in all
cases, especially if such clients have been dynamically registered cases, especially if such clients have been dynamically registered
and have not been trusted by any users at the Authorization Server and have not been trusted by any users at the Authorization Server
before. before.
In a situation where the Authorization Server is supporting open In a situation where the Authorization Server is supporting open
Client registration, it must be extremely careful with any URL Client registration, it must be extremely careful with any URL
provided by the Client that will be displayed to the user (e.g. provided by the Client that will be displayed to the user (e.g.
"logo_uri" and "policy_uri"). A rogue Client could specify a "logo_uri" and "policy_uri"). A rogue Client could specify a
registration request with a reference to a drive-by download in the registration request with a reference to a drive-by download in the
"policy_uri". The Authorization Server should check to see if the "policy_uri". The Authorization Server SHOULD check to see if the
"logo_uri" and "policy_uri" have the same host as the hosts defined "logo_uri" and "policy_uri" have the same host as the hosts defined
in the array of "redirect_uris". in the array of "redirect_uris" and that all of these resolve to
valid Web pages.
While the Client Secret can expire, the Registration Access Token While the Client Secret can expire, the Registration Access Token
should not expire while a client is still actively registered. If should not expire while a client is still actively registered. If
this token were to expire, a Client could be left in a situation this token were to expire, a developer or Client could be left in a
where it has no means of updating itself and must register itself situation where they have no means of retrieving the Client's
anew. As the Registration Access Tokens are long-term credentials, registration information or updating it. Were that the case, a new
and since the Registration Access Token is a Bearer token and acts as registration would be required, thereby getting a new Client
the sole authentication for use at the Client Configuration Endpoint, Identifier. However, Registration Access Tokens MAY be rotated when
it MUST be protected by the Client as described in OAuth 2.0 Bearer the developer or client does a read or update operation on its Client
[RFC6750]. Configuration Endpoint, and the developer or Client MUST use this new
Registration Access Token. As the Registration Access Tokens are
long-term credentials, and since the Registration Access Token is a
Bearer token and acts as the sole authentication for use at the
Client Configuration Endpoint, it MUST be protected by the developer
or Client as described in OAuth 2.0 Bearer [RFC6750].
If a Client is deprovisioned from a server, any outstanding If a Client is deprovisioned from a server, any outstanding
Registration Access Tokens for that client MUST be invalidated at the Registration Access Tokens for that client MUST be invalidated at the
same time. Otherwise, this can lead to an inconsistent state wherein same time. Otherwise, this can lead to an inconsistent state wherein
a Client could make requests to the Client Configuration Endpoint a Client could make requests to the Client Configuration Endpoint
where the authentication would succeed but the action would fail where the authentication would succeed but the action would fail
because the Client is no longer valid. because the Client is no longer valid.
8. Normative References 8. Normative References
[IANA.Language] [IANA.Language]
Internet Assigned Numbers Authority (IANA), "Language Internet Assigned Numbers Authority (IANA), "Language
Subtag Registry", 2005. Subtag Registry", 2005.
[JWK] Jones, M.B., "JSON Web Key (JWK)", draft-ietf-jose-json- [JWK] Jones, M., "JSON Web Key (JWK)",
web-key (work in progress), April 2013. draft-ietf-jose-json-web-key (work in progress), May 2013.
[OAuth.JWT] [OAuth.JWT]
Jones, M.B., Campbell, B., and C. Mortimore, "JSON Web Jones, M., Campbell, B., and C. Mortimore, "JSON Web Token
Token (JWT) Bearer Token Profiles for OAuth 2.0", draft- (JWT) Bearer Token Profiles for OAuth 2.0",
ietf-oauth-jwt-bearer (work in progress), March 2013. draft-ietf-oauth-jwt-bearer (work in progress),
March 2013.
[OAuth.SAML2] [OAuth.SAML2]
Campbell, B., Mortimore, C., and M.B. Jones, "SAML 2.0 Campbell, B., Mortimore, C., and M. Jones, "SAML 2.0
Bearer Assertion Profiles for OAuth 2.0", draft-ietf- Bearer Assertion Profiles for OAuth 2.0",
oauth-saml2-bearer (work in progress), March 2013. draft-ietf-oauth-saml2-bearer (work in progress),
March 2013.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2246] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0", [RFC2246] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0",
RFC 2246, January 1999. RFC 2246, January 1999.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[RFC4627] Crockford, D., "The application/json Media Type for [RFC4627] Crockford, D., "The application/json Media Type for
JavaScript Object Notation (JSON)", RFC 4627, July 2006. JavaScript Object Notation (JSON)", RFC 4627, July 2006.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, August 2008. (TLS) Protocol Version 1.2", RFC 5246, August 2008.
[RFC5646] Phillips, A. and M. Davis, "Tags for Identifying [RFC5646] Phillips, A. and M. Davis, "Tags for Identifying
Languages", BCP 47, RFC 5646, September 2009. Languages", BCP 47, RFC 5646, September 2009.
[RFC6125] Saint-Andre, P. and J. Hodges, "Representation and [RFC6125] Saint-Andre, P. and J. Hodges, "Representation and
Verification of Domain-Based Application Service Identity Verification of Domain-Based Application Service Identity
within Internet Public Key Infrastructure Using X.509 within Internet Public Key Infrastructure Using X.509
(PKIX) Certificates in the Context of Transport Layer (PKIX) Certificates in the Context of Transport Layer
Security (TLS)", RFC 6125, March 2011. Security (TLS)", RFC 6125, March 2011.
[RFC6749] Hardt, D., "The OAuth 2.0 Authorization Framework", RFC [RFC6749] Hardt, D., "The OAuth 2.0 Authorization Framework",
6749, October 2012. RFC 6749, October 2012.
[RFC6750] Jones, M. and D. Hardt, "The OAuth 2.0 Authorization [RFC6750] Jones, M. and D. Hardt, "The OAuth 2.0 Authorization
Framework: Bearer Token Usage", RFC 6750, October 2012. Framework: Bearer Token Usage", RFC 6750, October 2012.
Appendix A. Acknowledgments Appendix A. Acknowledgments
The authors thank the OAuth Working Group, the User-Managed Access The authors thank the OAuth Working Group, the User-Managed Access
Working Group, and the OpenID Connect Working Group participants for Working Group, and the OpenID Connect Working Group participants for
their input to this document. In particular, the following their input to this document. In particular, the following
individuals have been instrumental in their review and contribution individuals have been instrumental in their review and contribution
to various versions of this document: Amanda Anganes, Tim Bray, to various versions of this document: Amanda Anganes, Tim Bray,
Domenico Catalano, George Fletcher, Torsten Lodderstedt, Eve Maler, Domenico Catalano, George Fletcher, Thomas Hardjono, Phil Hunt,
Nov Matake, Thomas Hardjono, Nat Sakimura, and Christian Scholz. Torsten Lodderstedt, Eve Maler, Nov Matake, Nat Sakimura, and
Christian Scholz.
Appendix B. Document History Appendix B. Document History
[[ to be removed by the RFC editor before publication as an RFC ]] [[ to be removed by the RFC editor before publication as an RFC ]]
-11
o Added localized text to registration request and response
examples.
o Removed "client_secret_jwt" and "private_key_jwt".
o Clarified "tos_uri" and "policy_uri" definitions.
o Added the OAuth Token Endpoint Authentication Methods registry for
registering "token_endpoint_auth_method" metadata values.
o Removed uses of non-ASCII characters, per RFC formatting rules.
o Changed "expires_at" to "client_secret_expires_at" and "issued_at"
to "client_id_issued_at" for greater clarity.
o Added explanatory text for different credentials (Initial Access
Token, Registration Access Token, Client Credentials) and what
they're used for.
o Added Client Lifecycle discussion and examples.
o Defined Initial Access Token in Terminology section.
-10 -10
o Added language to point out that scope values are service-specific o Added language to point out that scope values are service-specific
o Clarified normative language around client metadata o Clarified normative language around client metadata
o Added extensibility to token_endpoint_auth_method using absolute o Added extensibility to token_endpoint_auth_method using absolute
URIs URIs
o Added security consideration about registering redirect URIs o Added security consideration about registering redirect URIs
skipping to change at page 24, line 32 skipping to change at page 34, line 10
-00 -00
o Imported original UMA draft specification o Imported original UMA draft specification
Authors' Addresses Authors' Addresses
Justin Richer (editor) Justin Richer (editor)
The MITRE Corporation The MITRE Corporation
Phone:
Fax:
Email: jricher@mitre.org Email: jricher@mitre.org
URI:
John Bradley John Bradley
Ping Identity Ping Identity
Email: ve7jtb@ve7jtb.com Email: ve7jtb@ve7jtb.com
Michael B. Jones Michael B. Jones
Microsoft Microsoft
Email: mbj@microsoft.com Email: mbj@microsoft.com
URI: http://self-issued.info/
Maciej Machulak Maciej Machulak
Newcastle University Newcastle University
Email: m.p.machulak@ncl.ac.uk Email: m.p.machulak@ncl.ac.uk
URI: http://ncl.ac.uk/ URI: http://ncl.ac.uk/
 End of changes. 69 change blocks. 
186 lines changed or deleted 593 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/