UMA telecon 2010-01-14

Date and Time

• Day: Thursday, 14 Jan 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)

...

Regrets:

• Iain Henderson

Agenda

• Roll call
• Approve minutes of UMA telecon 2009-12-17, UMA telecon 2010-01-07
• Action item review
• Webinar planning
• Lexicon discussion
• Consider UMA logo idea
• Scenarios and use cases
  • Opportunity to provide scenarios as input to the OAuth process
  • Review scenario docket
  • Custodian
  • E-commerce
  • Walk through personal loan wireframes
• Spec review
• AOB

Minutes

Roll call

Quorum was reached.

Approve minutes of UMA telecon 2009-12-17, UMA telecon 2010-01-07

Motion to accept minutes APPROVED.

Action item review

• Eve: Add terms-negotiation scenarios to Scenarios document: Some more work has been done on these, particularly the requester identification scenario, but it's still in progress.
• Webinar team: Draft slide deck for group review: Eve is on the hook to produce a first draft by this weekend.
• Eve: Propose a requirement or design principle about constraining our V1 scope to "full-blown" sites: Eve sent a query to the list about this. Pending.
• Webinar team/WG: Publicize the webinar through blogging, tweeting, etc.: It will be time to do this very soon.
• Joe: Submit a protected-inbox scenario: Done.

...

The OAuth telecons are scheduled. The current plan is for us to submit information about our approved UMA scenarios in email to convey our key use cases (endpoints, parties, actions, etc.). Does this have to be in I-D form to be effective? It might not be quite as effective if just in a plain email, but there may be IPR questions around the I-D approach. Let's do the email approach for now, and see how it goes.

Review scenario docket

Eve's goal is to get all the awaiting-submission scenarios submitted by next Thursday.

• The Iain/Joe car-buying line item should be struck; we'll incorporate references to it on a case-by-case basis.
• Maciej's higher-ed scenario will show a person who uses many different systems for "lifelong learning", with one university serving as a locus of control.
• In the health data scenario, there's almost a "profile" of UMA in that it uses UMA for two different purposes – the first being a way to protect access to an XRD-based discovery service for both adding entries and reading entries.
• Mike M. may be able to submit a scenario on information card integration; he'll check. George wonders if cards can be employed to any protocol, not just UMA, for provisioning URLs of resources of various types. The bigger question is around how identity "flows" through UMA in general.
• Can we add the ACL/PoCo aspect to the custodian use case? Let's discuss below.

Custodian

Should we add an ACL aspect to this scenario? Yes. George notes that AOL does a lot of both ACLs and parental control already. ACL management is a nightmare today because it can't be shared or factored out from multiple control points.

...

• Protecting "discovery" information
• Open identity token
• Open identity token and personal discovery service

E-commerce

This is getting closer. Hopefully the people who have commented on it in the past, at least, can review it closely and decide if it has a clean bill of health.

...

Deferred. Please do this on your own time and send any thoughts to the list.

New action items

New AIs:

...