This is our last telecon of the year. We got only a couple of regrets from voting participants last week for this meeting -- hope we can get good representation, and raise a virtual cup of egg nog while solving lots of open issues in this last session of 2016. :-)

Date and Time

• Thursdays, 9-10am PT
  • Skype: +99051000000481 / US +1-805-309-2350 / international lines / web calling interface / 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 2016-12-01

• Logistics

  • This is our last meeting of the year
  • Refer to telecon 2016-12-01 minutes to see how voting/balloting process goes

• UMA V2.0 workAOB

  • 2016 roadmap
  • Core is up to 09 and RReg is up to 02 (no changes from last meeting)
  • Dynamic swimlane
  • Complete set math decisions today: see email proposal
  • Proposal for "the rest of the issues to consider/take out of the backlog"; let's decide the final list by our first meeting in January and figure out our completion roadmap:
    • Use Cases for FHIR Security Authorization with Patient Consent ("cascading authorization servers")
    • Shoebox endpoint/"audit whether RS gave access per permissions" (issues 24, 224)
    • Hashed claims discovery (issue 254)
    • Issues that came up in editing:
      • What is the proper way to complete the specification of the UMA grant? e.g., how do the client's credentials actually get used in the flow?
      • Remove policy-specific resource/scope description properties from RReg and add as extensions in Core?
      • claim_token_profiles_supported: Provide real profiles for OIDC and maybe SAML?
      • What to do with the extensibility profiles?
      • Need to have IANA registry entries for both old uma-configuration and uma2-configuration?