If the working group decides to merge these specs, I'd be happy to do the
editorial work to do so.
Best wishes,
-- Mike
-Original Message-
From: Anthony Nadalin
Sent: Saturday, April 05, 2014 4:06 PM
To: Mike Jones; Hannes
The core spec actually already does speak to this question, Bill.
http://tools.ietf.org/html/draft-ietf-oauth-dyn-reg-16#section-3 says:
In some cases, authorization servers MAY choose to accept a software
statement value directly as a Client ID in an authorization request,
without a pr
To me the fundamental question of whether a client has to be registered in each
place it is used is quite significant. We don't address the problem and have
not discussed it enough.
-bill
On Friday, April 4, 2014 11:39 PM, Torsten Lodderstedt
wrote:
Hi Bill,
which scalability problem are y
If these are going to be combined then a draft should be produced and then a
decision should be made once everyone has a chance to review
-Original Message-
From: OAuth [mailto:oauth-boun...@ietf.org] On Behalf Of Mike Jones
Sent: Friday, April 4, 2014 5:49 PM
To: Hannes Tschofenig; oauth
Hi Bill,
I believe Torsten is right. Most of the discussion in London was focused
on the management API rather than the core/meta-data docs.
Unfortunately, in our agenda we lumped both of these topics together.
There wasn't much disagreement on the core/meta-data docs.
As I wrote on the mailing l
