UMA telecon 2010-02-25
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Date and Time
- Day: Thursday, 25 Feb 2010
- Time: 9:00-10:30am PST | 12:00-1:30pm EST | 17:00-18:30 UTC (time chart)
- Dial-In:
- Skype: +9900827042954214
- US: +1-201-793-9022 | Room Code: 295-4214 (other local country numbers available on request)
Agenda
- Roll call
- Any missing next week due to RSA?
- Approve minutes of UMA telecon 2010-02-18
- Action item review
- Spec review
- Expect a new draft by Wednesday night; please review carefully before the call if possible
- Report from spec editors' meeting
- Review new spec changes
- Lexicon discussion
- Establish need (if any) for legal dimension
- Establish need (if any) for custodial dimension
- Custodian scenario review
- AOB
Attendees
As of 19 Feb 2010, quorum is 9 of 16.
...
(TomH and Paul send regrets for next week.)
Minutes
New AI summary
Eve | Closed | Revise the lexicon according to today's discussion. |
| |
Maciej | Open | Revise the custodian scenario according to today's discussion and email feedback. |
|
Roll call
Quorum was not reached.
(Anybody who has to miss next week due to RSA? No.)
Approve minutes of UMA telecon 2010-02-18
Deferred due to lack of quorum.
Action item review
- 2009-12-03-04 Eve Open Add terms-negotiation scenarios to Scenarios document. Delayed while we sort through requester concepts.
- 2010-01-28-2 Joe Open Edit protected inbox scenario in response to telecon and email discussion. Still pending.
- 2010-02-11-1 Paul Open Develop new core spec draft. See below.
...
We have a spec editing team meeting next Wednesday, where we will carry forward this last (hopefully) major refit of the protocol. Paul now knows what direction to take in the spec and will produce it before then.
Lexicon discussion
The new policy definition is: "A policy is an instruction an authorizing user gives an AM to govern its calculation of access authorization decisions. A policy may involve dictating a requirement for a requester to provide one or more claims." The group accepts it.
...
Let's discuss "primary resource user" as part of the custodian scenario; maybe it shouldn't be defined in the protocol spec itself. (Later...) We agreed not to put this term into the spec but to keep it in the lexicon.
Custodian scenario review
Maciej's scenario focuses specifically on an underage person who must delegate authorization control to a responsible adult in her life. Paul questioned how liability would work in this circumstance. The parent, in creating an account at the AM, presumably would have to be verified as to their age and other credentials. The host would have to whitelist trusted AMs that check for this. Regarding introducing the authorizing user into the picture, the host would have to manage this. These seemed to be the biggest outstanding issues.
...