UMA telecon 2012-12-20

UMA telecon 2012-12-20

Date and Time

• All-hands meeting on Thursday, 20 Dec 2012, at 9am PT (time chart) – legal, all topics
  
  • Skype: +99051000000481
  • US: +1-805-309-2350 (other international dial-in lines available) | Room Code: 178-2540

Agenda

• Activate join.me with code to be supplied on mailing list
• Roll call
• Consider reading into today's minutes several past all-hands meetings
  
  • UMA telecon 2012-11-29
  • UMA telecon 2012-10-25
  • UMA telecon 2012-09-27 (quorate)
  • UMA telecon 2012-08-16
  • UMA telecon 2012-08-02 (quorate)
• Meeting schedule review
  
  • NO MEETINGS for the rest of 2012 – happy new year/end-of-the-world!
  • Anyone want to do an ad hoc meeting next week to review/walk through the massive spec modularization we're undertaking (assuming the world doesn't end)?
• Action item review
• Legal/business rules discussion
  
  • Further review of Binding Obligations and tie-ins to the technical spec
  • AOB
• Review current OAuth introduction/resource registration/discovery proposal
• Demo of Gluu's OX UMA support if Mike et al. are available
• AOB

Minutes

Roll call

Quorum was reached.

MOTION: Moved by Keith: Consider reading into today's minutes the following past all-hands meetings: UMA telecon 2012-11-29, UMA telecon 2012-10-25, UMA telecon 2012-09-27 (quorate), UMA telecon 2012-08-16, and UMA telecon 2012-08-02 (quorate). PASSED by unanimous consent.

Meeting schedule review

NO MEETING next week – happy new year/end-of-the-world!

Eve and Thomas will get together at the "normal" UMA WG hour to continue some spec editing work.

Action item review

The SMART team action to propose a discovery solution is now OBE.

Review new spec drafts

draft-oauth-resource-reg spec: We reviewed the new/prospective features. The SMART team's resource set type property is simply called "type". They had experimented with the "implicit" idea, but found all solutions to be imperfect. What sort of namespace should the value of this property use? Should impose any namespace at all? Using a string is probably the safest course for now, if we want this to be appealing to a wide IETF-friendly audience.

Consensus: Let's call this property "type", make its value a string, and remove the "implicit" idea for now. Let's leave the language "scope type (description)" while keeping the property name of "scopes".

Legal/business rules discussion

Eve: Update section references in the Binding Obligations doc.

Dazza presented his concept of "Terms of Authorization" as alternative to today's terms of service that are entirely disconnected from application access management underneath profile pages on specific apps' sites. He's conducting an MIT hackathon Jan 28-Feb 1 on this, and he's using UMA-friendly standardized scope type descriptions that convey contractual rights. EverNote's recent TOS update did a good job of this. Eve will send out a link to Dazza's slides.

Attendees

As of 27 Nov 2012, quorum is 6 of 10.

1. Catalano, Domenico
2. Hardjono, Thomas
3. Hazelton, Keith
4. Machulak, Maciej
5. Maler, Eve
6. Mohammad, Alam
7. Moren, Lukasz

Non-voting participants:

• Cox, Kevin
• Greenwood, Dazza

Regrets:

• Sal

Next Meetings

• NO MEETINGS for the rest of 2012 – happy new year/end-of-the-world!

Assuming the world doesn't end...

• Focus meeting on Thursday, 3 Jan 2013, at 9am PT (time chart) – technical, educational (security considerations, terminology changeover plan, OX demo)