draft-ietf-oauth-use-cases-00.txt   draft-ietf-oauth-use-cases-01.txt 
OAUTH WG G. Fletcher OAUTH WG G. Fletcher
Internet-Draft AOL Internet-Draft AOL
Intended status: Informational T. Lodderstedt Intended status: Informational T. Lodderstedt
Expires: November 24, 2012 Deutsche Telekom AG Expires: January 17, 2013 Deutsche Telekom AG
Z. Zeltsan Z. Zeltsan
Alcatel-Lucent Alcatel-Lucent
May 23, 2012 July 16, 2012
OAuth Use Cases OAuth Use Cases
draft-ietf-oauth-use-cases-00 draft-ietf-oauth-use-cases-01
Abstract Abstract
This document lists the OAuth use cases. The provided list is based This document lists the OAuth use cases. The provided list is based
on the Internet-Drafts of the OAUTH working group and discussions on on the Internet Drafts of the OAUTH working group and discussions on
the group's mailing list. the group's mailing list.
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 24, 2012. This Internet-Draft will expire on January 17, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Notational Conventions . . . . . . . . . . . . . . . . . . . . 3 2. OAuth use cases . . . . . . . . . . . . . . . . . . . . . . . 3
3. OAuth use cases . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Web server . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Web server . . . . . . . . . . . . . . . . . . . . . . . . 3 2.2. User-agent . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. User-agent . . . . . . . . . . . . . . . . . . . . . . . . 5 2.3. In-App-Payment (based on Native Application) . . . . . . . 6
3.3. In-App-Payment (based on Native Application) . . . . . . . 6 2.4. Native Application . . . . . . . . . . . . . . . . . . . . 9
3.4. Native Application . . . . . . . . . . . . . . . . . . . . 9 2.5. Device . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.5. Device . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.6. Client password (shared secret) credentials . . . . . . . 11
3.6. Client password (shared secret) credentials . . . . . . . 11 2.7. Assertion . . . . . . . . . . . . . . . . . . . . . . . . 12
3.7. Assertion . . . . . . . . . . . . . . . . . . . . . . . . 12 2.8. Content manager . . . . . . . . . . . . . . . . . . . . . 13
3.8. Content manager . . . . . . . . . . . . . . . . . . . . . 13 2.9. Access token exchange . . . . . . . . . . . . . . . . . . 14
3.9. Access token exchange . . . . . . . . . . . . . . . . . . 14 2.10. Multiple access tokens . . . . . . . . . . . . . . . . . . 16
3.10. Multiple access tokens . . . . . . . . . . . . . . . . . . 16 2.11. Gateway for browser-based VoIP applets . . . . . . . . . . 17
3.11. Gateway for browser-based VoIP applets . . . . . . . . . . 17 2.12. Signed Messages . . . . . . . . . . . . . . . . . . . . . 18
3.12. Signed Messages . . . . . . . . . . . . . . . . . . . . . 18 2.13. Signature with asymmetric secret . . . . . . . . . . . . . 20
3.13. Signature with asymmetric secret . . . . . . . . . . . . . 20 3. Authors of the use cases . . . . . . . . . . . . . . . . . . . 22
4. Authors of the use cases . . . . . . . . . . . . . . . . . . . 22 4. Security considerations . . . . . . . . . . . . . . . . . . . 22
5. Security considerations . . . . . . . . . . . . . . . . . . . 22 5. IANA considerations . . . . . . . . . . . . . . . . . . . . . 22
6. IANA considerations . . . . . . . . . . . . . . . . . . . . . 22 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 23
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 23 7. Normative References . . . . . . . . . . . . . . . . . . . . . 23
8. Normative References . . . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23
1. Introduction 1. Introduction
The need for documenting the OAuth use cases was discussed at the This document describes the use cases that have been discussed on the
oauth WG virtual meetings, on the group's mailing list, and at the oauth WG mailing list and introduced by the Internet Drafts submitted
IETF 77 and IETF 78. This Internet-Draft describes such use cases. to the group. The selected use cases illustrate the use of the OAuth
The objective of the draft is to document the discussed OAuth use flows by the clients of the various profiles and types. The document
cases and identify the use cases supported by the OAuth also includes those cases that are not directly supported by the
specifications. The following section provides the abbreviated OAuth 2.0 protocol, but were considered during its development. The
descriptions of the use cases. document provides a list of the requirements derived from the use
cases. The use cases supported by OAuth 2.0 are indicated.
The document's objective is to help with understanding of the OAuth
2.0 protocol design.
Note: The use of the string ".example.com" in the URLs of the example Note: The use of the string ".example.com" in the URLs of the example
entities does not mean that the entities belong to the same entities does not mean that the entities belong to the same
organization. organization.
2. Notational Conventions The following section provides the abbreviated descriptions of the
use cases.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
3. OAuth use cases 2. OAuth use cases
This section lists the use cases that have been discussed by the This section lists the use cases that have been discussed by the
oauth WG. oauth WG.
3.1. Web server 2.1. Web server
Description: Description:
Alice accesses an application running on a web server at Alice accesses an application running on a web server at
www.printphotos.example.com and instructs it to print her photographs www.printphotos.example.com and instructs it to print her photographs
that are stored on a server www.storephotos.example.com. The that are stored on a server www.storephotos.example.com. The
application at www.printphotos.example.com receives Alice's application at www.printphotos.example.com receives Alice's
authorization for accessing her photographs without learning her authorization for accessing her photographs without learning her
authentication credentials with www.storephotos.example.com. authentication credentials with www.storephotos.example.com.
skipping to change at page 5, line 27 skipping to change at page 5, line 27
o Application at www.storephotos.example.com must invalidate the o Application at www.storephotos.example.com must invalidate the
authorization code after its first use authorization code after its first use
o Alice's manual involvement in the OAuth authorization procedure o Alice's manual involvement in the OAuth authorization procedure
(e.g., entering an URL or a password) should not be required. (e.g., entering an URL or a password) should not be required.
(Alice's authentication to www.storephotos.example.com is not in (Alice's authentication to www.storephotos.example.com is not in
the OAuth scope. Her registration with the OAuth scope. Her registration with
www.storephotos.example.com is required as a pre-condition) www.storephotos.example.com is required as a pre-condition)
3.2. User-agent 2.2. User-agent
Description: Description:
Alice has installed on her computer a gaming application. She keeps Alice has installed on her computer a gaming application. She keeps
her scores in a database of a social site at www.fun.example.com. In her scores in a database of a social site at www.fun.example.com. In
order to upload Alice's scores, the application gets access to the order to upload Alice's scores, the application gets access to the
database with her authorization. database with her authorization.
Pre-conditions: Pre-conditions:
skipping to change at page 6, line 39 skipping to change at page 6, line 39
o Application running at www.fun.example.com must be able to o Application running at www.fun.example.com must be able to
describe to Alice the request made by the gaming application describe to Alice the request made by the gaming application
running on her computer and obtain Alice's authorization for or running on her computer and obtain Alice's authorization for or
denial of the requested access denial of the requested access
o After obtaining Alice's authorization the application running at o After obtaining Alice's authorization the application running at
www.fun.example.com must respond with an access token and redirect www.fun.example.com must respond with an access token and redirect
Alice's browser to a web server (e.g., www.help.example.com) that Alice's browser to a web server (e.g., www.help.example.com) that
is capable of retrieving an access token from an URL is capable of retrieving an access token from an URL
3.3. In-App-Payment (based on Native Application) 2.3. In-App-Payment (based on Native Application)
Description: Description:
Alice has installed on her computer a gaming application (e.g., Alice has installed on her computer a gaming application (e.g.,
running as native code or as a widget). At some point she wants to running as native code or as a widget). At some point she wants to
play the next level of the game and needs to purchase an access to play the next level of the game and needs to purchase an access to
the advanced version of the game from her service provider at the advanced version of the game from her service provider at
www.sp.example.com. With Alice's authorization the application www.sp.example.com. With Alice's authorization the application
accesses her account at www.sp.example.com and enables her to make accesses her account at www.sp.example.com and enables her to make
the payment. the payment.
skipping to change at page 9, line 12 skipping to change at page 9, line 12
o Alice's manual involvement in the OAuth authorization procedure o Alice's manual involvement in the OAuth authorization procedure
(e.g., entering an URL or a password) should not be required. (e.g., entering an URL or a password) should not be required.
(Alice's authentication to www.sp.example.com is not in the OAuth (Alice's authentication to www.sp.example.com is not in the OAuth
scope) scope)
* The requirements denoted by '*' are not common for the Native * The requirements denoted by '*' are not common for the Native
Application use cases, but are specific to the In-App-Payment use Application use cases, but are specific to the In-App-Payment use
case case
3.4. Native Application 2.4. Native Application
Description: Description:
Alice wants to upload (or download) her photographs to (or from) Alice wants to upload (or download) her photographs to (or from)
storephotos.example.com using her smartphone. She downloads and storephotos.example.com using her smartphone. She downloads and
installs a photo app on her smartphone. In order to enable the app installs a photo app on her smartphone. In order to enable the app
to access her photographs, Alice needs to authorize the app to access to access her photographs, Alice needs to authorize the app to access
the web site on her behalf. The authorization shall be valid for a the web site on her behalf. The authorization shall be valid for a
prolonged duration (e.g. several months), so that Alice does not need prolonged duration (e.g. several months), so that Alice does not need
to authenticate and authorize access on every execution of the app. to authenticate and authorize access on every execution of the app.
skipping to change at page 10, line 21 skipping to change at page 10, line 21
o The application at storephotos.example.com provides a capability o The application at storephotos.example.com provides a capability
to view and delete the apps' authorizations. This implies that to view and delete the apps' authorizations. This implies that
the different installations of the same app on the different the different installations of the same app on the different
devices can be distinguished (e.g., by a device name or a devices can be distinguished (e.g., by a device name or a
telephone number) telephone number)
o The app must provide Alice an option to logout. The logout must o The app must provide Alice an option to logout. The logout must
result in the revocation of the refresh token on the authorization result in the revocation of the refresh token on the authorization
server server
3.5. Device 2.5. Device
Description: Description:
Alice has a device, such as a game console, that does not support an Alice has a device, such as a game console, that does not support an
easy data-entry method. She also has an access to a computer with a easy data-entry method. She also has an access to a computer with a
browser. The application running on the Alice's device gets browser. The application running on the Alice's device gets
authorized access to a protected resource (e.g., photographs) stored authorized access to a protected resource (e.g., photographs) stored
on a server at www.storephotos.example.com on a server at www.storephotos.example.com
Pre-conditions: Pre-conditions:
skipping to change at page 11, line 35 skipping to change at page 11, line 35
o Alice's authentication with www.storephotos.example.com is o Alice's authentication with www.storephotos.example.com is
required required
o After authentication with www.storephotos.example.com Alice, if o After authentication with www.storephotos.example.com Alice, if
she wishes to approve the request, which is described in her she wishes to approve the request, which is described in her
browser's window, must enter the user code. (The user code is browser's window, must enter the user code. (The user code is
also displayed on her game console along with the verification also displayed on her game console along with the verification
URL) URL)
3.6. Client password (shared secret) credentials 2.6. Client password (shared secret) credentials
Description: Description:
The company GoodPay prepares the employee payrolls for the company The company GoodPay prepares the employee payrolls for the company
GoodWork. In order to do that the application at GoodWork. In order to do that the application at
www.GoodPay.example.com gets authenticated access to the employees' www.GoodPay.example.com gets authenticated access to the employees'
attendance data stored at www.GoodWork.example.com. attendance data stored at www.GoodWork.example.com.
Pre-conditions: Pre-conditions:
skipping to change at page 12, line 28 skipping to change at page 12, line 28
o The authentication method must be based on the identifier and o The authentication method must be based on the identifier and
shared secret, which the application running at shared secret, which the application running at
www.GoodPay.example.com submits to the application at www.GoodPay.example.com submits to the application at
www.GoodWork.example.com in the initial HTTP request www.GoodWork.example.com in the initial HTTP request
o Because in this use case GoodPay gets access to GoodWork's o Because in this use case GoodPay gets access to GoodWork's
sensitive data, GoodWork shall have a pre-established trust with sensitive data, GoodWork shall have a pre-established trust with
GoodPay on the security policy and the authorization method's GoodPay on the security policy and the authorization method's
implementation implementation
3.7. Assertion 2.7. Assertion
Description: Description:
Company GoodPay prepares the employee payrolls for the company Company GoodPay prepares the employee payrolls for the company
GoodWork. In order to do that the application at GoodWork. In order to do that the application at
www.GoodPay.example.com gets authenticated access to the employees' www.GoodPay.example.com gets authenticated access to the employees'
attendance data stored at www.GoodWork.example.com. attendance data stored at www.GoodWork.example.com.
This use case describes an alternative solution to the one described This use case describes an alternative solution to the one described
by the use case Client password credentials. by the use case Client password credentials.
skipping to change at page 13, line 25 skipping to change at page 13, line 25
the application at www.GoodWork.example.com is required the application at www.GoodWork.example.com is required
o The application running at www.GoodWork.example.com must be o The application running at www.GoodWork.example.com must be
capable of validating assertion presented by the application capable of validating assertion presented by the application
running at www.GoodPay.example.com running at www.GoodPay.example.com
o Because in this use case GoodPay gets access to GoodWork's o Because in this use case GoodPay gets access to GoodWork's
sensitive data, GoodWork shall establish trust with GoodPay on the sensitive data, GoodWork shall establish trust with GoodPay on the
security policy and the authorization method's implementation security policy and the authorization method's implementation
3.8. Content manager 2.8. Content manager
Description: Description:
Alice and Bob are having a chat conversation using a content manager Alice and Bob are having a chat conversation using a content manager
application running on a web server at application running on a web server at
www.contentmanager.example.com. Alice notifies Bob that she wants to www.contentmanager.example.com. Alice notifies Bob that she wants to
share some photographs at www.storephotos.example.com and instructs share some photographs at www.storephotos.example.com and instructs
the application at www.contentmanager.example.com to enable Bob's the application at www.contentmanager.example.com to enable Bob's
access to the photographs. The application at access to the photographs. The application at
www.contentmanager.example.com, after Alice's authorization, obtains www.contentmanager.example.com, after Alice's authorization, obtains
skipping to change at page 14, line 25 skipping to change at page 14, line 25
and the application at www.contentmanager.example.com and the application at www.contentmanager.example.com
o The authorization server is required to obtain Alice's o The authorization server is required to obtain Alice's
authorization for issuing an access token to authorization for issuing an access token to
www.contentmanager.example.com on Bob's behalf www.contentmanager.example.com on Bob's behalf
o Authorization server must be able to identify to Alice the scope o Authorization server must be able to identify to Alice the scope
of access that www.contentmanager.example.com has requested on of access that www.contentmanager.example.com has requested on
Bob's behalf while asking for Alice's authorization Bob's behalf while asking for Alice's authorization
3.9. Access token exchange 2.9. Access token exchange
Description: Description:
Alice uses an application running on www.printphotos.example.com for Alice uses an application running on www.printphotos.example.com for
printing her photographs that are stored on a server at printing her photographs that are stored on a server at
www.storephotos.example.com. The application running on www.storephotos.example.com. The application running on
www.storephotos.example.com, while serving the request of the www.storephotos.example.com, while serving the request of the
application at www.printphotos.example.com, discovers that some of application at www.printphotos.example.com, discovers that some of
the requested photographs have been moved to the requested photographs have been moved to
www.storephotos1.example.com. The application at www.storephotos1.example.com. The application at
skipping to change at page 16, line 21 skipping to change at page 16, line 21
www.storephotos.example.com to obtain the token. www.storephotos.example.com to obtain the token.
o The application at www.storephotos.example.com must be able to o The application at www.storephotos.example.com must be able to
validate an access token presented by the application running at validate an access token presented by the application running at
www.printphotos.example.com www.printphotos.example.com
o The application at www.storephotos1.example.com must be able to o The application at www.storephotos1.example.com must be able to
validate the access token presented by the application running at validate the access token presented by the application running at
www.storephotos.example.com www.storephotos.example.com
3.10. Multiple access tokens 2.10. Multiple access tokens
Description: Description:
Alice uses a communicator application running on a web server at Alice uses a communicator application running on a web server at
www.communicator.example.com to access her email service at www.communicator.example.com to access her email service at
www.email.example.com and her voice over IP service at www.email.example.com and her voice over IP service at
www.voip.example.com. Email addresses and telephone numbers are www.voip.example.com. Email addresses and telephone numbers are
obtained from Alice's address book at www.contacts.example.com. obtained from Alice's address book at www.contacts.example.com.
Those web sites all rely on the same authorization server, so the Those web sites all rely on the same authorization server, so the
application at www.communicator.example.com can receive a single application at www.communicator.example.com can receive a single
skipping to change at page 17, line 40 skipping to change at page 17, line 40
o A callback URL of the application running at o A callback URL of the application running at
www.communicator.example.com must be known to the authorization www.communicator.example.com must be known to the authorization
server server
o The authorization server must be able to issue the separate o The authorization server must be able to issue the separate
service-specific tokens (with different, scope, permissions, and service-specific tokens (with different, scope, permissions, and
expiration dates) for access to the requested services (such as expiration dates) for access to the requested services (such as
email and VoIP) email and VoIP)
3.11. Gateway for browser-based VoIP applets 2.11. Gateway for browser-based VoIP applets
Description: Description:
Alice accesses a social site on a web server at Alice accesses a social site on a web server at
www.social.example.com. Her browser loads a VoIP applet that enables www.social.example.com. Her browser loads a VoIP applet that enables
her to make a VoIP call using her SIP server at her to make a VoIP call using her SIP server at
www.sipservice.example.com. The application at www.sipservice.example.com. The application at
www.social.example.com gets Alice's authorization to use her account www.social.example.com gets Alice's authorization to use her account
with www.sipservice.example.com without learning her authentication with www.sipservice.example.com without learning her authentication
credentials with www.sipservice.example.com. credentials with www.sipservice.example.com.
skipping to change at page 18, line 47 skipping to change at page 18, line 47
o Application at www.sipservice.example.com must be able to o Application at www.sipservice.example.com must be able to
authenticate the application at www.social.example.com and authenticate the application at www.social.example.com and
validate the access token validate the access token
o Alice's manual involvement in the OAuth authorization procedure o Alice's manual involvement in the OAuth authorization procedure
(e.g., entering an URL or a password) should not be required. (e.g., entering an URL or a password) should not be required.
(Alice's authentication to www.sipservice.example.com is not in (Alice's authentication to www.sipservice.example.com is not in
the OAuth scope) the OAuth scope)
3.12. Signed Messages 2.12. Signed Messages
Description: Description:
Alice manages all her personal health records in her personal health Alice manages all her personal health records in her personal health
data store at a server at www.myhealth.example.com, which manages data store at a server at www.myhealth.example.com, which manages
authorization of access to Alice's participating health systems. authorization of access to Alice's participating health systems.
Alice's Primary Care Physician (PCP), which has a Web site at Alice's Primary Care Physician (PCP), which has a Web site at
www.pcp.example.com, recommends her to see a sleep specialist www.pcp.example.com, recommends her to see a sleep specialist
(www.sleepwell.example.com). Alice arrives at the sleep specialist's (www.sleepwell.example.com). Alice arrives at the sleep specialist's
office and authorizes it to access her basic health data at her PCP's office and authorizes it to access her basic health data at her PCP's
skipping to change at page 20, line 43 skipping to change at page 20, line 43
verifying the signature of the authorization token verifying the signature of the authorization token
o The application at www.pcp.example.com must be capable of parsing o The application at www.pcp.example.com must be capable of parsing
the authorization token and verifying that this token was issued the authorization token and verifying that this token was issued
to the application at www.sleepwell.com to the application at www.sleepwell.com
o The application at www.pcp.example.com must be capable of o The application at www.pcp.example.com must be capable of
retrieving the requested data and returning it to the application retrieving the requested data and returning it to the application
at www.sleepwell.example.com at www.sleepwell.example.com
3.13. Signature with asymmetric secret 2.13. Signature with asymmetric secret
Description: Description:
Alice accesses an application running on a web server at Alice accesses an application running on a web server at
www.printphotos.example.com and instructs it to print her photographs www.printphotos.example.com and instructs it to print her photographs
that are stored on a server www.storephotos.example.com. The that are stored on a server www.storephotos.example.com. The
application at www.printphotos.example.com, which does not have a application at www.printphotos.example.com, which does not have a
shared secret with www.storephotos.example.com, receives Alice's shared secret with www.storephotos.example.com, receives Alice's
authorization for accessing her photographs without learning her authorization for accessing her photographs without learning her
authentication credentials with www.storephotos.example.com. authentication credentials with www.storephotos.example.com.
skipping to change at page 22, line 18 skipping to change at page 22, line 18
www.storephotos.example.com) www.storephotos.example.com)
o The application at www.storephotos.example.com must be capable of o The application at www.storephotos.example.com must be capable of
issuing the HTTP redirect requests to Alice's browser issuing the HTTP redirect requests to Alice's browser
o Alice's manual involvement in the OAuth authorization procedure o Alice's manual involvement in the OAuth authorization procedure
(e.g., entering an URL or a password) should not be required. (e.g., entering an URL or a password) should not be required.
(Alice's authentication to www.storephotos.example.com is not in (Alice's authentication to www.storephotos.example.com is not in
the OAuth scope) the OAuth scope)
4. Authors of the use cases 3. Authors of the use cases
The major contributors of the use cases are as follows: The major contributors of the use cases are as follows:
W. Beck, Deutsche Telekom AG W. Beck, Deutsche Telekom AG
G. Brail, Sonoa Systems G. Brail, Sonoa Systems
B. de hOra B. de hOra
B. Eaton, Google B. Eaton, Google
S. Farrell, NewBay Software S. Farrell, NewBay Software
G. Fletcher, AOL G. Fletcher, AOL
Y. Goland, Microsoft Y. Goland, Microsoft
skipping to change at page 22, line 41 skipping to change at page 22, line 41
D. Hardt D. Hardt
R. Krikorian, Twitter R. Krikorian, Twitter
T. Lodderstedt, Deutsche Telekom T. Lodderstedt, Deutsche Telekom
E. Maler, PayPal E. Maler, PayPal
D. Recordon, Facebook D. Recordon, Facebook
L. Shepard, Facebook L. Shepard, Facebook
A. Tom, Yahoo! A. Tom, Yahoo!
B. Vrancken, Alcatel-Lucent B. Vrancken, Alcatel-Lucent
Z. Zeltsan, Alcatel-Lucent Z. Zeltsan, Alcatel-Lucent
5. Security considerations 4. Security considerations
TBD TBD
6. IANA considerations 5. IANA considerations
This Internet Draft includes no request to IANA. This Internet Draft includes no request to IANA.
7. Acknowledgements 6. Acknowledgements
The authors thank Igor Faynberg and Hui-Lan Lu for their invaluable The authors thank Igor Faynberg and Hui-Lan Lu for their invaluable
help with preparing this document. Special thanks are to the draft help with preparing this document. Special thanks are to the draft
reviewers Thomas Hardjono and Melinda Shore, whose suggestions have reviewers Thomas Hardjono and Melinda Shore, whose suggestions have
helped to improve the draft. helped to improve the draft.
8. Normative References 7. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997.
[I-D.draft-ietf-oauth-v2] [I-D.draft-ietf-oauth-v2]
Hammer-Lahav, E., Recordon, D., and D. Hardt, "The OAuth Hammer-Lahav, E., Recordon, D., and D. Hardt, "The OAuth
2.0 Authorization Protocol". 2.0 Authorization Protocol".
Authors' Addresses Authors' Addresses
George Fletcher George Fletcher
AOL AOL
 End of changes. 27 change blocks. 
59 lines changed or deleted 56 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/