UMA 1.0 core protocol specification
...
http://docs.kantarainitiative.org/uma/draft-uma-core.html
...
This is the pretty-printed latest version, available on the Kantara site.
http://tools.ietf.org/html/draft-hardjono-oauth-umacore
...
This is the latest version contributed as IETF I-D. (It may be out of date with respect to the version linked above. We don't submit I-D revisions for every little edit.)
https://github.com/xmlgrrl/UMA-Specifications
...
This is the GitHub repository for the spec and issues.
https://github.com/xmlgrrl/UMA-Specifications/issues
You can use This is a direct link to the issues list.
http://tinyurl.com/umav1
This is a short link you can use to direct people back to this page.
Goals in 2012
Our main 2012Q1 spec goal is was to revise the IETF I-D in time for consideration at the IETF 83 meeting 25-30 March 2012, incorporating resolutions to as many open issues as possible. We also know of several active implementers and want wanted to resolve outstanding major spec issues as quickly as possible to support interop activities in 2012H1.the several active implementers we're aware of. Though IETF 83 did not take up every one of the major issues presented by UMA, concentrating (from the UMA WG's perspective) on just the charter inclusion of authorization server/resource server separation and dynamic client registration, the UMA WG met its goals of resolving issues and publishing new spec revs.
Our main 2012Q2 spec goal is to support interop activities among UMA protocol implementers and to support efforts to use and deploy UMA. As part of this goal, we will continue to burn down issues and revise the spec, along with refining our trust model document and collecting new use cases.
Recent breaking changes
Following is a catalog of breaking changes made since the 18 Jan 2012 rev.
...