UMA telecon 2010-10-28
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Date and Time
- WG telecon on Thursday, 28 Oct 2010, at 9-10:30am PT (time chart)
- Skype line "C": +9900827042954214
- US: +1-201-793-9022 | Room Code: 295-4214
Agenda
- Roll call
- Approve minutes of 2010-10-14 and 2010-10-20 meetings
- Action item review
- Brief updates from the wider UMA world
- Review action and discussion items from Paris F2F
- Resource registration (see new draft from Maciej, coming shortly)
- Agenda-bashing for IIW F2F
- AOB
...
- Kevin Cox
- Thomas Hardjono
- Torsten Lodderstedt
Minutes
New AI summary
Eve | Open | Work with Sal and George to put together a set of flow options/user stories for review at the IIW F2F. |
Quorum was reached.
Approve minutes of 2010-10-14 and 2010-10-20 meetings
Minutes of 2010-10-14 and 2010-10-20 meetings APPROVED.
Action item review
- 2010-09-30-1 Eve Open Incorporate Fraunhofer's input on the location scenario into the Scenario document. (Mario's document is here.) Eve suggests that we treat Mario's document on a separate track, seeing it as an "advanced" person-to-person/mobile app location scenario vs. Eve's "basic" one. Treat this AI as OBE.
...
Maciej comments that people were worried about the protocol's complexity from the perspective of a user. Some suggested that the entire flow should be possible to initiate only when a user wants to share a resource. Eve wonders if we can map out a set of canonical UX flows through the entire protocol, choosing a different entry point each time. George comments that this would flush out the precise requirements and constraints on dynamicism across all the pairwise relationships that need to be set up. Where could conventions and defaults simplify the complexity of a user's experience? From a protocol level we need to support ultimate dynamicism, but there will be many cases where we don't need that flexibility.
The newly updated basic location scenario describes, for starters, a "host-initiated" flow. And Maciej's new resource registration draft selects the host as an initiation point for setting up sharing/protected/policy. The SMART project folks have also seen that people would want to start at the AM to protect/share things, but since the AM would be visited less often, he decided not to cover it in his draft. Eve sees the usefulness of an AM-initiated protection flow if a person is trying to protect/share several things using the same policy (such as a "family" ACL).
...
Regarding scopes, Eve's new location scenario work highlights a question about how the OAuth system of scopes matches with UMA's system of user-dictated scopes. Do we need to have a claim communications cycle that explicitly collects acknowledgment from the requester that a particular set of scopes is all they'll get an access token for, or should we leave scope management entirely to the OAuth layer? We'll ask this question next week.
...
- User stories/tasks/flows
- Resource/scope registration
Next Meetings
- WG F2F on Monday, 1 Nov 2010, at 11am-5pm PT (time chart) - no dial-in, and no telecon this week
- WG telecon on Thursday, 11 Nov 2010, at 9-10:30am PT (time chart) - Maciej to chair?