draft-ietf-oauth-dyn-reg-management-00.txt   draft-ietf-oauth-dyn-reg-management-01.txt 
OAuth Working Group J. Richer OAuth Working Group J. Richer
Internet-Draft The MITRE Corporation Internet-Draft The MITRE Corporation
Intended status: Standards Track M. Jones Intended status: Standards Track M. Jones
Expires: August 10, 2014 Microsoft Expires: November 23, 2014 Microsoft
J. Bradley J. Bradley
Ping Identity Ping Identity
M. Machulak M. Machulak
Newcastle University Newcastle University
P. Hunt P. Hunt
Oracle Corporation Oracle Corporation
February 6, 2014 May 22, 2014
OAuth 2.0 Dynamic Client Registration Management Protocol OAuth 2.0 Dynamic Client Registration Management Protocol
draft-ietf-oauth-dyn-reg-management-00 draft-ietf-oauth-dyn-reg-management-01
Abstract Abstract
This specification defines methods for management of dynamic OAuth This specification defines methods for management of dynamic OAuth
2.0 client registrations. 2.0 client registrations.
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.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 August 10, 2014. This Internet-Draft will expire on November 23, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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
skipping to change at page 2, line 26 skipping to change at page 2, line 26
1.4.1. Credential Rotation . . . . . . . . . . . . . . . . . 6 1.4.1. Credential Rotation . . . . . . . . . . . . . . . . . 6
2. Client Configuration Endpoint . . . . . . . . . . . . . . . . 7 2. Client Configuration Endpoint . . . . . . . . . . . . . . . . 7
2.1. Forming the Client Configuration Endpoint URL . . . . . . 7 2.1. Forming the Client Configuration Endpoint URL . . . . . . 7
2.2. Client Read Request . . . . . . . . . . . . . . . . . . . 8 2.2. Client Read Request . . . . . . . . . . . . . . . . . . . 8
2.3. Client Update Request . . . . . . . . . . . . . . . . . . 8 2.3. Client Update Request . . . . . . . . . . . . . . . . . . 8
2.4. Client Delete Request . . . . . . . . . . . . . . . . . . 11 2.4. Client Delete Request . . . . . . . . . . . . . . . . . . 11
3. Responses . . . . . . . . . . . . . . . . . . . . . . . . . . 12 3. Responses . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.1. Client Information Response . . . . . . . . . . . . . . . 12 3.1. Client Information Response . . . . . . . . . . . . . . . 12
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
5. Security Considerations . . . . . . . . . . . . . . . . . . . 13 5. Security Considerations . . . . . . . . . . . . . . . . . . . 13
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 6. Normative References . . . . . . . . . . . . . . . . . . . . . 14
6.1. Normative References . . . . . . . . . . . . . . . . . . . 14
6.2. Informative References . . . . . . . . . . . . . . . . . . 15
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 15 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 15
Appendix B. Document History . . . . . . . . . . . . . . . . . . 15 Appendix B. Document History . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
In order for an OAuth 2.0 client to utilize an OAuth 2.0 In order for an OAuth 2.0 client to utilize an OAuth 2.0
authorization server, the client needs specific information to authorization server, the client needs specific information to
interact with the server, including an OAuth 2.0 Client ID to use at interact with the server, including an OAuth 2.0 client identifier to
that server. The OAuth 2.0 Dynamic Client Registration Core Protocol use at that server. The OAuth 2.0 Dynamic Client Registration
[OAuth.Registration] specification describes how an OAuth 2.0 client Protocol [OAuth.Registration] specification describes how an OAuth
can be dynamically registered with an authorization server to obtain 2.0 client can be dynamically registered with an authorization server
this information and how metadata about the client can be registered to obtain this information and how metadata about the client can be
with the server. registered with the server.
This specification extends the core registration specification by This specification extends the core registration specification by
defining a set of methods for management of dynamic OAuth 2.0 client defining a set of methods for management of dynamic OAuth 2.0 client
registrations beyond those defined in the core registration registrations beyond those defined in the core registration
specification. specification.
1.1. Notational Conventions 1.1. Notational Conventions
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT',
'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and 'OPTIONAL' in this 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and 'OPTIONAL' in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
Unless otherwise noted, all the protocol parameter names and values Unless otherwise noted, all the protocol parameter names and values
are case sensitive. are case sensitive.
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",
"Response Type", and "Token Endpoint" defined by OAuth 2.0 [RFC6749] "response type", and "token endpoint" defined by OAuth 2.0 [RFC6749]
and the terms defined by the OAuth 2.0 Client Dynamic Registration and the terms defined by the OAuth 2.0 Client Dynamic Registration
Core Protocol [OAuth.Registration]. Protocol [OAuth.Registration].
This specification defines the following terms: This specification defines the following terms:
Client Configuration Endpoint OAuth 2.0 endpoint through which Client Configuration Endpoint
registration information for a registered client can be managed. OAuth 2.0 endpoint through which registration information for a
This URL for this endpoint is returned by the authorization server registered client can be managed. This URL for this endpoint is
in the client information response. returned by the authorization server in the client information
response.
Registration Access Token OAuth 2.0 bearer token issued by the Registration Access Token
authorization server through the client registration endpoint that OAuth 2.0 bearer token issued by the authorization server through
is used to authenticate the caller when accessing the client's the client registration endpoint that is used to authenticate the
registration information at the client configuration endpoint. caller when accessing the client's registration information at the
This access token is associated with a particular registered client configuration endpoint. This access token is associated
client. with a particular registered client.
1.3. Protocol Flow 1.3. Protocol Flow
This extends the flow in the OAuth 2.0 Dynamic Client Registration This extends the flow in the OAuth 2.0 Dynamic Client Registration
Core Protocol [OAuth.Registration] specification as follows: Protocol [OAuth.Registration] specification as follows:
+--------(A)- Initial Access Token (OPTIONAL) +--------(A)- Initial Access Token (OPTIONAL)
| |
| +----(B)- Software Statement (OPTIONAL) | +----(B)- Software Statement (OPTIONAL)
| | | |
v v v v
+-----------+ +---------------+ +-----------+ +---------------+
| |--(C)- Client Registration Request -->| Client | | |--(C)- Client Registration Request -->| Client |
| | | Registration | | | | Registration |
| |<-(D)- Client Information Response ---| Endpoint | | |<-(D)- Client Information Response ---| Endpoint |
skipping to change at page 5, line 49 skipping to change at page 5, line 49
three different classes of credentials in play, each with different three different classes of credentials in play, each with different
properties and targets. properties and targets.
o The initial access token is optionally used by the client or o The initial access token is optionally used by the client or
developer at the registration endpoint. This is an OAuth 2.0 developer at the registration endpoint. This is an OAuth 2.0
token that is used to authorize the initial client registration token that is used to authorize the initial client registration
request. The content, structure, generation, and validation of request. The content, structure, generation, and validation of
this token are out of scope for this specification. The this token are out of scope for this specification. The
authorization server can use this token to verify that the authorization server can use this token to verify that the
presenter is allowed to dynamically register new clients. This presenter is allowed to dynamically register new clients. This
token may be shared between multiple instances of a client to token may be shared among multiple instances of a client to allow
allow them to each register separately, thereby letting the them to each register separately, thereby letting the
authorization server use this token to tie multiple instances of authorization server use this token to tie multiple instances of
registered clients (each with their own distinct client registered clients (each with their own distinct client
identifier) back to the party to whom the initial access token was identifier) back to the party to whom the initial access token was
issued, usually an application developer. This token should be issued, usually an application developer. This token should be
used only at the client registration endpoint. used only at the client registration endpoint.
o The registration access token is used by the client or developer o The registration access token is used by the client or developer
at the client configuration endpoint and represents the holder's at the client configuration endpoint and represents the holder's
authorization to manage the registration of a client. This is an authorization to manage the registration of a client. This is an
OAuth 2.0 bearer token that is issued from the client registration OAuth 2.0 bearer token that is issued from the client registration
skipping to change at page 9, line 7 skipping to change at page 9, line 7
MUST return an HTTP 403 Forbidden. MUST return an HTTP 403 Forbidden.
2.3. Client Update Request 2.3. Client Update Request
This operation updates a previously-registered client with new This operation updates a previously-registered client with new
metadata at the authorization server. This request is authenticated metadata at the authorization server. This request is authenticated
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 [RFC7159] 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 client metadata fields as returned to This request MUST include all client metadata fields as returned to
the client from a previous registration, read, or update operation. the client from a previous registration, read, or update operation.
The client MUST NOT include the "registration_access_token", The client MUST NOT include the "registration_access_token",
"registration_client_uri", "client_secret_expires_at", or "registration_client_uri", "client_secret_expires_at", or
"client_id_issued_at" fields described in Section 3.1. "client_id_issued_at" fields described in Section 3.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.
skipping to change at page 10, line 19 skipping to change at page 10, line 19
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
{ {
"client_id":"s6BhdRkqt3", "client_id":"s6BhdRkqt3",
"client_secret": "cf136dc3c1fc93f31185e5885805d", "client_secret": "cf136dc3c1fc93f31185e5885805d",
"redirect_uris":[ "redirect_uris":[
"https://client.example.org/callback", "https://client.example.org/callback",
"https://client.example.org/alt"], "https://client.example.org/alt"],
"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", "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" "logo_uri#fr":"https://client.example.org/fr/newlogo.png"
} }
This example uses client metadata values defined both in This example uses client metadata values defined in
[OAuth.Registration] and [OAuth.Registration.Metadata]. [OAuth.Registration].
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 Section 3.1. Some values in the response, payload, as described in Section 3.1. Some values in the response,
including the "client_secret" and r"egistration_access_token", MAY be including the "client_secret" and r"egistration_access_token", MAY be
different from those in the initial registration response. If the different from those in the initial registration response. If the
authorization server includes a new client secret and/or registration authorization server includes a new client secret and/or registration
access token in its response, the client MUST immediately discard its access token in its response, the client MUST immediately discard its
previous client secret and/or registration access token. The value previous client secret and/or registration access token. The value
of the "client_id" MUST NOT change from the initial registration of the "client_id" MUST NOT change from the initial registration
skipping to change at page 12, line 24 skipping to change at page 12, line 24
This specification extends the client information response defined in This specification extends the client information response defined in
OAuth 2.0 Core Client Dynamic Registration. The response contains OAuth 2.0 Core Client Dynamic Registration. The response contains
the client identifier as well as the client secret, if the client is the client identifier as well as the client secret, if the client is
a confidential client. The response also contains the fully a confidential client. The response also contains the fully
qualified URL of the client configuration endpoint for this specific qualified URL of the client configuration endpoint for this specific
client that the client may use to obtain and update information about client that the client may use to obtain and update information about
itself. The response also contains a registration access token that itself. The response also contains a registration access token that
is to be used by the client to perform subsequent operations at the is to be used by the client to perform subsequent operations at the
client configuration endpoint. client configuration endpoint.
client_id REQUIRED. The unique client identifier, MUST NOT be client_id
currently valid for any other registered client. REQUIRED. OAuth 2.0 client identifier.
client_secret OPTIONAL. The client secret. If issued, this MUST be client_secret
unique for each "client_id". This value is used by confidential OPTIONAL. OAuth 2.0 client secret.
clients to authenticate to the token endpoint as described in
OAuth 2.0 [RFC6749] Section 2.3.1.
client_id_issued_at OPTIONAL. Time at which the Client Identifier client_id_issued_at
was issued. The time is represented as the number of seconds from OPTIONAL. Time at which the client identifier was issued, as
1970-01-01T0:0:0Z as measured in UTC until the date/time. defined by [OAuth.Registration].
client_secret_expires_at REQUIRED if "client_secret" is issued. client_secret_expires_at
Time at which the "client_secret" will expire or 0 if it will not REQUIRED if "client_secret" is issued. Time at which the
expire. The time is represented as the number of seconds from "client_secret" will expire, as defined by [OAuth.Registration].
1970-01-01T0:0:0Z as measured in UTC until the date/time.
registration_access_token REQUIRED. Access token that is used at registration_access_token
the client configuration endpoint to perform subsequent operations REQUIRED. Access token used at the client configuration endpoint
upon the client registration. to perform subsequent operations upon the client registration.
registration_client_uri registration_client_uri
REQUIRED. The fully qualified URL of the client configuration REQUIRED. Fully qualified URL of the client configuration
endpoint for this client. The client MUST use this URL as given endpoint for this client.
when communicating with the client configuration endpoint.
Additionally, the Authorization Server MUST return all registered Additionally, the Authorization Server MUST return all registered
metadata about this client, including any fields provisioned by the metadata about this client, including any fields provisioned by the
authorization server itself. The authorization server MAY reject or authorization server itself. The authorization server MAY reject or
replace any of the client's requested metadata values submitted replace any of the client's requested metadata values submitted
during the registration or update requests and substitute them with during the registration or update requests and substitute them with
suitable values. 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 [RFC7159].
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",
skipping to change at page 13, line 32 skipping to change at page 13, line 29
"client_id":"s6BhdRkqt3", "client_id":"s6BhdRkqt3",
"client_secret": "cf136dc3c1fc93f31185e5885805d", "client_secret": "cf136dc3c1fc93f31185e5885805d",
"client_id_issued_at":2893256800, "client_id_issued_at":2893256800,
"client_secret_expires_at":2893276800, "client_secret_expires_at":2893276800,
"client_name":"My Example Client", "client_name":"My Example Client",
"client_name#ja-Jpan-JP": "client_name#ja-Jpan-JP":
"\u30AF\u30E9\u30A4\u30A2\u30F3\u30C8\u540D", "\u30AF\u30E9\u30A4\u30A2\u30F3\u30C8\u540D",
"redirect_uris":[ "redirect_uris":[
"https://client.example.org/callback", "https://client.example.org/callback",
"https://client.example.org/callback2"], "https://client.example.org/callback2"],
"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"
} }
4. IANA Considerations 4. IANA Considerations
This specification makes no requests of IANA. This specification makes no requests of IANA.
skipping to change at page 14, line 30 skipping to change at page 14, line 25
If a client is deprovisioned from a server, any outstanding If a client is deprovisioned from a server, any outstanding
registration access token for that client MUST be invalidated at the registration access token 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. To prevent accidental because the client is no longer valid. To prevent accidental
disclosure from such an erroneous situation, the authorization server disclosure from such an erroneous situation, the authorization server
MUST treat all such requests as if the registration access token was MUST treat all such requests as if the registration access token was
invalid (by returning an HTTP 401 Unauthorized error, as described). invalid (by returning an HTTP 401 Unauthorized error, as described).
6. References 6. Normative References
6.1. Normative References
[OAuth.Registration] [OAuth.Registration]
Richer, J., Jones, M., Bradley, J., Machulak, M., and P. Richer, J., Jones, M., Bradley, J., Machulak, M., and P.
Hunt, "OAuth 2.0 Dynamic Client Registration Core Hunt, "OAuth 2.0 Dynamic Client Registration Protocol",
Protocol", draft-ietf-oauth-dyn-reg (work in progress), draft-ietf-oauth-dyn-reg (work in progress), May 2014.
February 2014.
[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.
[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
JavaScript Object Notation (JSON)", RFC 4627, July 2006.
[RFC6749] Hardt, D., "The OAuth 2.0 Authorization Framework", [RFC6749] Hardt, D., "The OAuth 2.0 Authorization Framework",
RFC 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.
6.2. Informative References [RFC7159] Bray, T., "The JavaScript Object Notation (JSON) Data
Interchange Format", RFC 7159, March 2014.
[OAuth.Registration.Metadata]
Richer, J., Jones, M., Bradley, J., Machulak, M., and P.
Hunt, "OAuth 2.0 Dynamic Client Registration Metadata",
draft-ietf-oauth-dyn-reg-metadata (work in progress),
February 2014.
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, Derek Atkins, to various versions of this document: Amanda Anganes, Derek Atkins,
Tim Bray, Domenico Catalano, Donald Coffin, Vladimir Dzhuvinov, Tim Bray, Domenico Catalano, Donald Coffin, Vladimir Dzhuvinov,
George Fletcher, Thomas Hardjono, Phil Hunt, William Kim, Torsten George Fletcher, Thomas Hardjono, Phil Hunt, William Kim, Torsten
Lodderstedt, Eve Maler, Josh Mandel, Nov Matake, Tony Nadalin, Nat Lodderstedt, Eve Maler, Josh Mandel, Nov Matake, Tony Nadalin, Nat
Sakimura, Christian Scholz, and Hannes Tschofenig. Sakimura, Christian Scholz, and Hannes Tschofenig.
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 ]]
-01
o Addressed issues that arose from last call comments on
draft-ietf-oauth-dyn-reg and draft-ietf-oauth-dyn-reg-metadata.
-00 -00
o Created from draft-jones-oauth-dyn-reg-management-00. o Created from draft-jones-oauth-dyn-reg-management-00.
Authors' Addresses Authors' Addresses
Justin Richer Justin Richer
The MITRE Corporation The MITRE Corporation
Email: jricher@mitre.org Email: jricher@mitre.org
 End of changes. 28 change blocks. 
73 lines changed or deleted 60 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/