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-11-10 
• Logistics for upcoming meetings (calendar) and 2016 roadmap check-in
  • Dec8/9: no meetings (consider meeting Wed afternoon or something?)
  • Dec 15/16: meet as usual
  • Dec 22: meet as usual; RSVP – Dec 23: no meeting
  • FYI: End game for V2 specs looks like this:
    • WG vote to publish Draft Recommendations (consider this an "implementers' draft"?)
    • 45-day Public Review
    • If no changes, LC votes to certify Draft Recommendations for All-Member Ballot
    • Ballot takes 14+ days
    • If no changes, Recommendations are prepared for publication and published
    • Total: if no changes, up to 90 days
• Work on UMA.next issues – Core is up to 09 and RReg is up to 02 – please review changes ahead of time if possible
  • Core: token profiling, rhetorical
  • To discuss specifically:
    • Set math (see forthcoming email for discussion points)
    • Remove policy-specific resource/scope description properties from RReg and add as extensions in Core?
    • AATs could be used for "stateful trust elevation"/step-up authentication; do we have any equivalent now, and if not, is this lack okay?
    • claim_token_profiles_supported: Provide real profiles for OIDC and maybe SAML?
    • uma_profiles_supported: What to do with the extensibility profiles?
    • Need to have IANA registry entries for both old uma-configuration and uma2-configuration?
    • Shoebox endpoint
    • Claims hashing
    • Other issue backlog review/cleanup
• See the latest swimlane
• AOB