UMA telecon 2014-11-20

Date and Time

...

• Roll call
• Minutes approval if quorum
  • Sample motion: Approve the minutes of UMA telecon 2014-1011-13 and read into today's minutes the notes of ad hoc WG meetings held since 2014-1011-13.
• Interop testing status and meeting schedule review
• Review of FT-impacting issues on V1.0 docket
  • 108: make "protection" and "authorization" scopes able to be implicit: does our Monday conclusion still sit well?
  • 92: trust elevation: can we come to a conclusion based on progress from Friday and Monday?
  • 110: RSR location URI for registration of discovery info? 
  • 84: UMA endpoint names vs. OAuth endpoint names: do we have to change user_endpoint to authorization_endpoint, and then do we have to change our authorization_request_endpoint to something else?
  • 94: start_at for permission validity
  • Review issues newly added
• AOB

...

MOTION: Moved by Andi: Approve the minutes of UMA telecon 2014-1011-13 and read into today's minutes the notes of ad hoc WG meetings held since 2014-1011-13. APPROVED by unanimous consent.

...

AI: Eve: Ask Roland which Monday he might be available for the next interop planning session.

In 2014, we have three more (long) Thursday meetings after today, plus Mondays and any other ad hoc meetings.

108: scope implicitness

Any update from Marcelo on scope mapping best practices?

...

AI: Eve: Update issue #108.

92: trust el

Our status to date is that our rough consensus has moved us beyond a mere need_claims response from the AS to an elevate_trust response, where its embedded error_details has the option to provide hints to the client about what's required next, and where our own specs have the option to standardize hint options and third parties can provide their own above and beyond those. Our standardized options of interest are need_claims and need_reauthentication.

...