Almost forgot, for completeness's sake in this thread: Mike S put in issue #288 <https://github.com/KantaraInitiative/wg-uma/issues/288> about using OpenAPI for RReg, and I just remembered to label it properly. *Eve Maler*Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl On Sun, Mar 5, 2017 at 11:50 PM, Eve Maler <eve@xmlgrrl.com> wrote:

Folks, I apologize for getting this ad hoc into the calendar only now; if you recall, we agreed on Thursday that we'd meet on Monday (tomorrow!) 8:30-10am Pacific. I *may* get dragged away sooner than that because of my delay... (Long story.)

For tomorrow, let's switch back to the open Core issues, and then go back to the open RReg issues, in this order:

#284 <https://github.com/KantaraInitiative/wg-uma/issues/284> if George has any further input; otherwise we can make this a last-call thing #282 <https://github.com/KantaraInitiative/wg-uma/issues/282> to see (briefly) if there's sufficient support for the suggestion, as we've been discussing it for a while #254 <https://github.com/KantaraInitiative/wg-uma/issues/254> (hashed claim discovery) #267 <https://github.com/KantaraInitiative/wg-uma/issues/267> (extensibility profiles) #263 <https://github.com/KantaraInitiative/wg-uma/issues/263> and #119 <https://github.com/KantaraInitiative/wg-uma/issues/119> (claim token profiling) #260 <https://github.com/KantaraInitiative/wg-uma/issues/260> if anyone wants to argue for pulling cascading authorization servers forward into V2.0 at this time #270 <https://github.com/KantaraInitiative/wg-uma/issues/270> (making "uri" an array, and possibly a wildcard) ...

Looking at the kinds of issues we have open at this point, one of the things to consider -- given that we'll be asking people to *join the group in order to give feedback* -- is whether we feel comfortable considering cutting loose a WG draft with "must-fix" issues closed, but keep working on tiny other ones, or what.

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