http://kantarainitiative.org/confluence/display/uma/UMA+telecon+2017-01-19 Date and Time - *Thursdays,* *special meeting times through Feb 9: 8:30-10am PT* - Skype: +99051000000481 / US +1-805-309-2350 / international lines <https://www.turbobridge.com/join.html> / web calling interface <https://panel.turbobridge.com/webcall/> / code 1782540 - Screen sharing: http://join.me/findthomas - NOTE: do not use the join.me dial-in line - UMA calendar: http://kantarainitiative.org/confluence/display/uma/Calendar Agenda - Roll call - Approve minutes of UMA telecon 2017-01-12 <http://kantarainitiative.org/confluence/display/uma/UMA+telecon+2017-01-12> - Logistics: - Meeting countdown: Jan 19 (today – week 0), Jan 26 (next week – week 1), Feb 2 (the week after – week 2), Feb 9 (*WG Draft and Public Review vote* – week 4) - We should strive for issue burndown and substantially complete specs by Feb 2 if possible – I may be calling on specific people to help close nitsy but not-very-substantial issues - No meeting Feb 16 because of RSAC - UMA V2.0 work - 2016 roadmap <http://kantarainitiative.org/confluence/display/uma/UMA+Roadmap+for+2016> / GitHub issues for V2.0 <https://github.com/KantaraInitiative/wg-uma/issues?q=is%3Aopen+is%3Aissue+label%3AV2.0> (all issues to be kept here for the duration!) / dynamic swimlane <http://www.websequencediagrams.com/files/render?link=Pu0sP0Oe2kjKc2WgdKZd> - Core is up to 12 <https://docs.kantarainitiative.org/uma/ed/uma-core-2.0-12.html> (updated) and RReg is up to 04 <http://docs.kantarainitiative.org/uma/ed/oauth-resource-reg-2.0-04.html> (no change) - Set math and UMA grant vs. authorization interface updates; figure 3 removed - 266 <https://github.com/KantaraInitiative/wg-uma/issues/266>: Set math - Critique new wording (Core Sec 1.4.2, Sec 9.4, and impacts on Sec 3.6) and ensure it's sufficiently specified – e.g., the AS knows about resource IDs but the client doesn't, and the permission ticket can refer to multiple resource IDs, so is everything clear from that perspective? - Decide whether we need to be specific about AS implementation details (George's email <https://groups.google.com/forum/#!topic/kantara-initiative-uma-wg/6Wx5NmXuLSo> ) - Account for "previous RPT" logic - Shoebox: 246 <https://github.com/KantaraInitiative/wg-uma/issues/246>: Endpoint for collection of "receipts" and notifications of RS action in case of extraordinary behavior / 245 <https://github.com/KantaraInitiative/wg-uma/issues/245>: Location Constraints / 224 <https://github.com/KantaraInitiative/wg-uma/issues/224>: RS Notifies AS or RO of Access / 63 <https://github.com/KantaraInitiative/wg-uma/issues/63>: Audit logs to support legal enforceability / 24 <https://github.com/KantaraInitiative/wg-uma/issues/24>: Possible to audit host's compliance in giving access based on a legitimate active permission from the AM? - How many use cases? - Which are in our scope for V2.0 or out (e.g., separate modular specs that a V2.x could call out as an optional or required endpoint as part of the protection API or something)? - AIs for next steps? - 260 <https://github.com/KantaraInitiative/wg-uma/issues/260>: Cascading authorization servers - Is this in scope for V2.0 or out (e.g., a third-party extension that we could consider for a V2.x), considering the additional detail provided in email <https://groups.google.com/forum/#!topic/kantara-initiative-uma-wg/cUHEEQNAjg8> ? - AIs for next steps? (don't do heavy design today) - "Dipstick check" on the RReg issues: - 269 <https://github.com/KantaraInitiative/wg-uma/issues/269>, 270 <https://github.com/KantaraInitiative/wg-uma/issues/270>, 271 <https://github.com/KantaraInitiative/wg-uma/issues/271>, 272 <https://github.com/KantaraInitiative/wg-uma/issues/272> - Easy issues to close by *Tue Jan 24* if no comment by then: - 256 <https://github.com/KantaraInitiative/wg-uma/issues/256>: Naming and concepts - Proposal: Define "claim token" in the spec - AOB *Eve Maler* Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl