UMA telecon 2016-01-07

Date and Time

• Thu Jan 7, 9-10am PT
  • Voice: Skype: +99051000000481 or US +1-805-309-2350 (international dial-in lines), room code 178-2540#
  • Screen sharing: http://join.me/findthomas - NOTE: IGNORE the join.me dial-in line shown here in favor of the dial-in info above (Kantara "line C" and the Skype line)
  • UMA calendar: http://kantarainitiative.org/confluence/display/uma/Calendar

Agenda

• Roll call
• Approve minutes of UMA telecon 2015-09-24, UMA telecon 2015-11-05, and UMA telecon 2015-12-17 if quorum
• Briefly review upcoming meeting schedule
• Recommendation ballot passed!
  • Status of publication of Recommendations and IETF I-Ds
• Discuss candidate charter revisions and 2016 roadmap priorities based on proposed technical and legal efforts
  • See notes from UMA telecon 2015-12-17 and list discussions for proposed technical efforts – summarizing:
    • Use cases: IoT, API security (AS-RS tight), federated authorization (AS-RS loose), RS needs to apply mandatory access controls for higher "LOA", RO needs to preserve right of access, wide ecosystems, RO needs to ensure RS respects insufficient authorization data
    • Technical issues: AAT burden, multi-resource-set permission registration, client-to-AS-first efficiency, validation of self-contained tokens
    • Also see issue backlog
  • Proposed legal efforts are to be discussed more fully on Friday, but we can review
• AOB

Minutes

Roll call

Quorum was reached.

Approve minutes of UMA telecon 2015-09-24, UMA telecon 2015-11-05, and UMA telecon 2015-12-17

MOTION: Andi moves, Thomas seconds: Approve minutes of UMA telecon 2015-09-24, UMA telecon 2015-11-05, and UMA telecon 2015-12-17. APPROVED by unanimous consent.

Briefly review upcoming meeting schedule

The Jan 21 WG meeting is canceled. The APAC-friendly fortnightly sync meetings have been rescheduled, starting in the last week of January. The legal subgroup will be discussing tomorrow whether to restart weekly meetings.

Recommendation ballot passed!

Status of publication of Recommendations and IETF I-Ds: We got about 25 Yes votes and no No votes – a healthy response. We're still working on publishing the new Recommendations.

Regarding the email about the workflow for creating new Recommendations and drafts, Maciej has a new suggestion: creating new GitHub branches. It's a relatively infrequent step, though, so it may be overkill. He'll write that suggestion up.

AI: Andi: We should do a Kantara blog post about the new Recommendations and maybe share how many issues were closed, the number of votes, etc.

AI: Thomas: Create two new I-Ds, changed to Informational, for UMA Core and OAuth RSR, that just have abstract, first intro paragraph, and second paragraph that normatively links to the respective final Kantara Recommendation.

sdf

Discuss candidate charter revisions and 2016 roadmap priorities based on proposed technical and legal efforts

See notes from UMA telecon 2015-12-17 and list discussions for proposed technical efforts – summarizing:

Use cases: IoT, API security (AS-RS tight), federated authorization (AS-RS loose), RS needs to apply mandatory access controls for higher "LOA", RO needs to preserve right of access, wide ecosystems, RO needs to ensure RS respects insufficient authorization data

Technical issues: AAT burden, multi-resource-set permission registration, client-to-AS-first efficiency, validation of self-contained tokens

Also see issue backlog

Proposed legal efforts are to be discussed more fully on Friday, but we can review

Attendees

As of 18 Dec 2015, quorum is 6 of 11. (Evariste, François, Domenico, Sal, Thomas, Andi, Robert, Maciej, Eve, Søren, Mike)

1. Eve
2. Domenico
3. Sal
4. Mike
5. Andi
6. Thomas
7. Maciej
8. François

Non-voting participants:

• Katie
• Ishan
• Jin
• Jim