UMA telecon 2010-09-23

Date and Time

• WG telecon on Thursday, 23 Sep 2010, at 9-10:30am PT (time chart)
  • Skype line "C": +9900827042954214
  • US: +1-201-793-9022 | Room Code: 295-4214

Agenda

• Administrative
  • Roll call
  • Approve minutes of 2010-09-16 meeting
  • Action item review
  • Updates from the wider UMA world
    • Review progress on dynamic registration
  • Paris F2F planning
• Scenarios and use cases
  • Review new scenario template and other changes
  • Discuss any changes needed to location scenario to support spec and implementation work
• Protocol work
  • Discuss "scope flow" in protocol (email) and UX (PDF)
  • Discuss need to further profile existing OAuth profiles
• AOB

...

• Herve Ganem

Minutes

New AI summary

Roll call

Quorum was reached.

Sal's company, IDmachines, provides identity services to government and enterprise. He is involved in the US government's initiative around identity verification (such as PIV-I). He was formerly involved in CoreStreet.

Approve minutes of 2010-09-16 meeting

Minutes of 2010-09-16 meeting APPROVED.

Action item review

• 2010-08-26-4 Eve, Domenico Open Write up generic Alice/Bob trust framework scenario. In progress. To be distributed and discussed more thoroughly next week.
• 2010-08-26-6 Eve Open Ping Denise Tayloe of Privo to see if she has interest in taking custodian scenario forward. Pending Scenario doc edits.
• 2010-09-02-1 Thomas Open Categorize all existing scenarios by their distinctive aspects. Well under way.
• 2010-09-16-1 Mark Open Update main trunk of the Legal Considerations document with Legal subteam input.
• 2010-09-16-2 Eve, Thomas, Mario Closed Meet to discuss sharing Scenario document editing duties.
• 2010-09-16-3 Christian Closed Update core spec with Step 3 text.

...

• Review new scenario template and other changes (doc)
• Discuss any changes needed to location scenario to support spec and implementation work

Thomas has enhanced the Introduction and Instructions section to include a template of "dimensions" and "building-block features" for which each scenario should provide a description. So far we have scope, cardinality, nature of host, dynamism vs. staticness, resource discovery, nature of access to protected resources, and person-to-self.

Eve wonders if the scope and nature of access to host ones can be combined somehow. And perhaps the person-to-self one can be renamed end-to-end or something.

The location scenario has been revised to include answers to the template.

...

• Step 3
  • Requester attempts access, this time with token, allowing host to infer required suitable scope(s)
  • (Host conveys token to AM for validation)
  • *Assuming token is valid, AM returns applicable scopes for it
  • Host maps applicable scopes to scope of attempted access

Next Meetings

• WG telecon on Thursday, 30 Sep 2010, at 9-10:30am PT (time chart) on line C