The OASIS Cloud Authorization (CloudAuthZ) TC  members have recently approved a Committee Note Draft (CND) and submitted it for 30-day public review:
Cloud Authorization Use Cases Version 1.0
Committee Note Draft 01 / Public Review Draft 01
17 March 2014
With the release we are testing a convenience option for submitting comments to the Technical Committee. Please see the details under ‘Public Review Period’ below.
This Committee Note provides a set of representative use cases that examine the requirements on Cloud Authorization using commonly defined cloud deployment and service models. These use cases are intended to be used for further analysis to determine if functional gaps exist in current identity management standards that additional open standards activities could address.
The CloudAuthZ TC develops enhanced models for managing authorizations and entitlements in SaaS, PaaS, and IaaS contexts. CloudAuthZ enables contextual attributes and contextual entitlements sets to be delivered to Policy Enforcement Points in real time. With CloudAuthZ, authorization decisions can be informed by data such as where users are, what they are doing, which device they are using, etc.
The TC welcomes contributions of relevant use cases for authorization and entitlements. Existing standards (e.g. XACML, OAuth, etc.) will be used wherever possible.
Public Review Period:
The public review starts 27 March 2014 at 00:00 GMT and ends 26 April 2014 at 23:59 GMT.
This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.
With this public review, we are testing a new convenience feature for sending comments to the Technical Committee. The file
contains the HTML version of the draft with a “[comment?]” link next to each section heading. Clicking on this link will launch your email application and begin a message to firstname.lastname@example.org with the specific section number and title in the subject line. (For example, “Public review comment for CloudAuthZ-usecases-v1.0-cnprd01: 1.1 Normative References.”) Simply enter your comment and click send.
You must be subscribed to the email@example.com mailing list in order to send your comments. Instructions on how to subscribe can be found at https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=cloudauthz.
Note that the Table of Contents doesn’t work in this version. That is one of the items we need fix before making this more broadly available. Please feel free to let us know if you find this feature helpful. We plan to refine it and make it a part of our normal public review process.
The prose specification document and related files are available here:
Editable Source (Authoritative):
ZIP distribution file (complete):
For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:
Additional information about the specification and the CloudAuthZ TC can be found at the TC’s public home page:
Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC’s “Send A Comment” page, or directly at:
Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:
All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of “Cloud Authorization Use Cases Version 1.0”, we call your attention to the OASIS IPR Policy  applicable especially  to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.
OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.
========== Additional references:
 OASIS Cloud Authorization (CloudAuthZ) Technical Committee