Re: [OAUTH-WG] [oauth] #15: Consensus for new Client Registration section (2)

#15: Consensus for new Client Registration section (2) Changes (by barryleiba@…): * status: new = closed * resolution: = fixed -- -+-- Reporter: barryleiba@… |Owner:

Re: [OAUTH-WG] [oauth] #16: Consensus for revised Redirection URI section (3.1.2)

#16: Consensus for revised Redirection URI section (3.1.2) Changes (by barryleiba@…): * status: new = closed * resolution: = fixed -- -+-- Reporter: barryleiba@… |Owner:

Re: [OAUTH-WG] [oauth] #17: Consensus for new token endpoint Client Authentication section (3.2.1)

#17: Consensus for new token endpoint Client Authentication section (3.2.1) Changes (by barryleiba@…): * status: new = closed * resolution: = fixed -- -+-- Reporter: barryleiba@… |Owner:

Re: [OAUTH-WG] Proposed change to section 8.4. Defining New Authorization Endpoint Response Types

Looks like we have consensus for the new text. I'd like to ask the chairs to close issue 18 (or note it resolved until the I-D freeze is over and I can push a revised draft). I agree; it looks like folks are happy with this text. I'll close this one as well. If there's a problem in the -19

Re: [OAUTH-WG] [oauth] #18: Consensus for new authorization endpoint response type extensibility (8.4)

#18: Consensus for new authorization endpoint response type extensibility (8.4) Changes (by barryleiba@…): * status: new = closed * resolution: = fixed -- -+-- Reporter: barryleiba@… |Owner:

Re: [OAUTH-WG] [oauth] #18: Consensus for new authorization endpoint response type extensibility (8.4)

#18: Consensus for new authorization endpoint response type extensibility (8.4) Description changed by barryleiba@…: Old description: New description: Fix will be in -19 version of the draft. -- -- -+-- Reporter:

Re: [OAUTH-WG] Call For Agenda Items for IETF#81

Having not received any slides yet, I'm repeating this: Presenters will be asked to have presentation slides in to the chairs by the end of the day Saturday, 23 July, so we can post them to the meeting materials page with plenty of time for all participants to review them. Meeting materials

Re: [OAUTH-WG] Request to close issues

What about my comments? http://www.ietf.org/mail-archive/web/oauth/current/msg07030.html http://www.ietf.org/mail-archive/web/oauth/current/msg07031.html http://www.ietf.org/mail-archive/web/oauth/current/msg07032.html -Ursprüngliche Nachricht- Von: Barry Leiba

Re: [OAUTH-WG] Request to close issues

What about my comments? http://www.ietf.org/mail-archive/web/oauth/current/msg07030.html http://www.ietf.org/mail-archive/web/oauth/current/msg07031.html http://www.ietf.org/mail-archive/web/oauth/current/msg07032.html Sorry; I have asked Eran off list about them. What doesn't get addressed

Re: [OAUTH-WG] Request to close issues

What about my comments? http://www.ietf.org/mail-archive/web/oauth/current/msg07030.html http://www.ietf.org/mail-archive/web/oauth/current/msg07031.html http://www.ietf.org/mail-archive/web/oauth/current/msg07032.html Sorry; I have asked Eran off list about them.  What doesn't get

Re: [OAUTH-WG] Issue 15, new client registration

-Original Message- From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf Of Torsten Lodderstedt Sent: Wednesday, July 20, 2011 1:59 PM To: OAuth WG Subject: Re: [OAUTH-WG] Issue 15, new client registration 2.1 Client types I'm struggeling with the new

Re: [OAUTH-WG] Issue 15, new client registration

Would protected and open work? Protected clients have protected credentials, while open clients don't. Huilan -Original Message- From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf Of Eran Hammer-Lahav Sent: Friday, July 22, 2011 5:12 PM To: Torsten Lodderstedt;