These issues will be closed, with/without action as indicated. (Scrambling to edit specs and put together the agenda for tomorrow! Stay tuned...) *Eve Maler*Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl On Fri, Jan 6, 2017 at 5:33 PM, Eve Maler <eve@xmlgrrl.com> wrote:

If we went all the way to next Thursday, I couldn't incorporate any relevant changes into the next spec rev for consideration. So let's please make the deadline next Tuesday, January 10 vs. next Thursday, January 12. That will allow me to assess whether to put anything on the agenda, change what goes into the spec, etc.

As a reminder, this week's agenda listed these as what I'm calling "easy issues":

- 261 <https://github.com/KantaraInitiative/wg-uma/issues/261>: Caching token inspection results (take the action recommended) - 249 <https://github.com/KantaraInitiative/wg-uma/issues/249>: Is there a way to elevate trust in Client Operators further, with a claims-like mechanism? (take no action) - 108 <https://github.com/KantaraInitiative/wg-uma/issues/108>: Protection and authorization scopes implicit/recommended vs. MUST? (take no action)

And I've just put up a fourth one that falls into this category as well:

- 268 <https://github.com/KantaraInitiative/wg-uma/issues/268>: Fix cascading error around client authentication (take the action recommended)

*Eve Maler*Cell +1 425.345.6756 <(425)%20345-6756> | Skype: xmlgrrl | Twitter: @xmlgrrl