Thanks! This is less invasive than one might have expected. :-) I hadn't
yet gotten to the ticket rotation and such, so special thanks for that.
Given the consensus we've achieved so far, I think we're at a point where
we should be able to merge changes back in (this is something Maciej and I
talked about a few weeks back). I've got a sort of pen-and-paper
concordance of spec instructions in meeting minutes + issue numbers +
roadmap items, and will take a look through this to check things off and
see what rhetorical stuff we wanted to cover in addition around these
topics. Will also publish a real -02 in HTML by Monday.
Still some heavy lifting ahead, but we're definitely making progress.
*Eve Maler*Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl
On Fri, Sep 23, 2016 at 3:57 PM, Justin Richer
As requested on the last call, I’ve taken an axe to the UMA specification and incorporated text and concepts from the MPD proposal sets. The new spec text (still rough in many spots) is available here:
https://github.com/jricher/wg-uma/commits/mpd-rewrite
Specifically, this difference set:
https://github.com/jricher/wg-uma/commit/ae82fe797229827e0cd3dfc2264268 ea36b31929
I added language on PCT’s (based on the model I outlined in the other thread), I changed the “scopes” parameter to “permission_scopes” as in the MPD implementation, I changed the interaction and examples to use the token endpoint for the RPT request, I moved the discovery document to .well-known/uma2-configuration and fixed a couple parameters, and I incorporated the rotating ticket mechanism from the security extension we wrote this spring.
Sorry it’s all in one commit, but I found it easier on my end to just plow through the whole spec.
— Justin
_______________________________________________ WG-UMA mailing list WG-UMA@kantarainitiative.org http://kantarainitiative.org/mailman/listinfo/wg-uma