Re: [OAUTH-WG] Registration: Endpoint Definition (& operation parameter)

2013-02-16 Thread Nat Sakimura
+1 2013/2/13 Torsten Lodderstedt : > > Am 12.02.2013 um 15:57 schrieb Justin Richer : > >> >> I think that's a very important difference. > > I fully agree. > ___ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth --

Re: [OAUTH-WG] Registration: Endpoint Definition (& operation parameter)

2013-02-12 Thread Torsten Lodderstedt
Am 12.02.2013 um 15:57 schrieb Justin Richer : > > I think that's a very important difference. I fully agree. ___ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth

Re: [OAUTH-WG] Registration: Endpoint Definition (& operation parameter)

2013-02-12 Thread Justin Richer
re's a useful OAuth precedent for doing things this way. -- Mike -Original Message- From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf Of Justin Richer Sent: Monday, February 11, 2013 1:15 PM To: oauth@ietf.org Subject: [OAUTH-WG] Registra

Re: [OAUTH-WG] Registration: Endpoint Definition (& operation parameter)

2013-02-12 Thread Sergey Beryozkin
tf.org <mailto:oauth-boun...@ietf.org>__] On Behalf Of Justin Richer Sent: Monday, February 11, 2013 1:15 PM To: oauth@ietf.org <mailto:oauth@ietf.org> Subject: [OAUTH-WG] Registration: Endpoint Definition (& operation parame

Re: [OAUTH-WG] Registration: Endpoint Definition (& operation parameter)

2013-02-12 Thread John Bradley
cess tokens - with the operations > being distinguished by whether a refresh_token parameter is present. So > there's a useful OAuth precedent for doing things this way. > > -- Mike > > -Original Message----- > From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org]

Re: [OAUTH-WG] Registration: Endpoint Definition (& operation parameter)

2013-02-12 Thread Justin Richer
[mailto:oauth-boun...@ietf.org] On Behalf Of Justin Richer Sent: Monday, February 11, 2013 1:15 PM To: oauth@ietf.org Subject: [OAUTH-WG] Registration: Endpoint Definition (& operation parameter) Draft -05 of OAuth Dynamic Client Registration [1] defines three fundamental operations that a clie

Re: [OAUTH-WG] Registration: Endpoint Definition (& operation parameter)

2013-02-12 Thread Tim Bray
gt;> >> -Original Message- >> From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org**] On Behalf >> Of Justin Richer >> Sent: Monday, February 11, 2013 1:15 PM >> To: oauth@ietf.org >> Subject: [OAUTH-WG] Registration: Endpoint Definition (& oper

Re: [OAUTH-WG] Registration: Endpoint Definition (& operation parameter)

2013-02-12 Thread Sergey Beryozkin
n...@ietf.org] On Behalf Of Justin Richer Sent: Monday, February 11, 2013 1:15 PM To: oauth@ietf.org Subject: [OAUTH-WG] Registration: Endpoint Definition (& operation parameter) Draft -05 of OAuth Dynamic Client Registration [1] defines three fundamental operations that a client can undertake:

Re: [OAUTH-WG] Registration: Endpoint Definition (& operation parameter)

2013-02-11 Thread Torsten Lodderstedt
Behalf Of > Justin Richer > Sent: Monday, February 11, 2013 1:15 PM > To: oauth@ietf.org > Subject: [OAUTH-WG] Registration: Endpoint Definition (& operation parameter) > > Draft -05 of OAuth Dynamic Client Registration [1] defines three fundamental > operations that a client

Re: [OAUTH-WG] Registration: Endpoint Definition (& operation parameter)

2013-02-11 Thread Mike Jones
To: oauth@ietf.org Subject: [OAUTH-WG] Registration: Endpoint Definition (& operation parameter) Draft -05 of OAuth Dynamic Client Registration [1] defines three fundamental operations that a client can undertake: Client Registration, Client Update, and Secret Rotation. Each of these actions

[OAUTH-WG] Registration: Endpoint Definition (& operation parameter)

2013-02-11 Thread Justin Richer
Draft -05 of OAuth Dynamic Client Registration [1] defines three fundamental operations that a client can undertake: Client Registration, Client Update, and Secret Rotation. Each of these actions needs to be differentiated *somehow* by the client and server as part of the protocol. Draft -00 de