Re: [OAUTH-WG] [oauth] #5: Separate scheme names for bearer tokens, request signing, and delegation

2011-04-15 Thread oauth issue tracker
#5: Separate scheme names for bearer tokens, request signing, and delegation Changes (by barryleiba@…): * component: v2 => z-dead -- -+-- Reporter: james@… |Owner: Type: defect

Re: [OAUTH-WG] [oauth] #5: Separate scheme names for bearer tokens, request signing, and delegation

2011-04-15 Thread oauth issue tracker
#5: Separate scheme names for bearer tokens, request signing, and delegation Changes (by barryleiba@…): * status: new => closed * resolution: => dead -- -+-- Reporter: james@… |Owner:

Re: [OAUTH-WG] [oauth] #6: Make automated self-registration of unique clients possible

2011-04-15 Thread oauth issue tracker
#6: Make automated self-registration of unique clients possible Changes (by barryleiba@…): * status: new => closed * resolution: => dead -- -+-- Reporter: eve@…|Owner: Type: enhanc

Re: [OAUTH-WG] Consensus process

2011-04-15 Thread Barry Leiba
Hi, Phil. I'm glad you brought up this question, because it gives me a good opportunity to clear up some points of IETF process. > I want to thank you for the re-introduction of the issues tracker. This will > greatly assist in tracking issues and building consensus. We hope it will. But, as yo

[OAUTH-WG] Consensus process

2011-04-15 Thread Phil Hunt
Chairs, I want to thank you for the re-introduction of the issues tracker. This will greatly assist in tracking issues and building consensus. Below is an example of a case where I thought consensus had been achieved, but arguably where the Tony and Mike continued to disagree. We always hope to

[OAUTH-WG] [oauth] #14: Restoring Client Assertion Credentials to the framework specification

2011-04-15 Thread oauth issue tracker
#14: Restoring Client Assertion Credentials to the framework specification There was no clear consensus on the list to remove this. -- +--- Reporter: Tony Nadalin| Owner: Type:

[OAUTH-WG] [oauth] #13: Description of how native applications can use OAuth 2.0

2011-04-15 Thread oauth issue tracker
#13: Description of how native applications can use OAuth 2.0 This was a description that was important to developers and deployers that was present in the specification and was removed without consensus to do so. -- +---

Re: [OAUTH-WG] [oauth] #11: 10.3. The OAuth Extensions Error Registry

2011-04-15 Thread oauth issue tracker
#11: 10.3. The OAuth Extensions Error Registry Description changed by barryleiba@…: Old description: > Pending Consensus: > > 10.3. The OAuth Extensions Error Registry > > This specification establishes the OAuth extensions error registry. > > Additional error codes used together with other prot

[OAUTH-WG] [oauth] #12: Restore WWW-Authenticate response to the framework specification

2011-04-15 Thread oauth issue tracker
#12: Restore WWW-Authenticate response to the framework specification This is a capability that was present in WRAP and earlier OAuth drafts that was removed without consensus to do so. The result has been that there is different and incompatible WWW-Authenticate response functionality in mul

Re: [OAUTH-WG] [oauth] #7: Incorporate Security Considerations draft into OAuth base

2011-04-15 Thread oauth issue tracker
#7: Incorporate Security Considerations draft into OAuth base Changes (by barryleiba@…): * milestone: => Deliver OAuth 2.0 spec -- +--- Reporter: Barry Leiba | Owner: Type:

Re: [OAUTH-WG] [oauth] #8: 4.1.2.1 and 4.2.2.1, text for 4xx or 5xx HTTP status code (was: 4.1.2.1, text for 4xx or 5xx HTTP status code)

2011-04-15 Thread oauth issue tracker
#8: 4.1.2.1 and 4.2.2.1, text for 4xx or 5xx HTTP status code -- +--- Reporter: Eran Hammer-Lahav | Owner: Type: suggested change| Status: new Priority:

[OAUTH-WG] [oauth] #11: 10.3. The OAuth Extensions Error Registry

2011-04-15 Thread oauth issue tracker
#11: 10.3. The OAuth Extensions Error Registry Pending Consensus: 10.3. The OAuth Extensions Error Registry This specification establishes the OAuth extensions error registry. Additional error codes used together with other protocol extensions (i.e. extension grant types, access token type

[OAUTH-WG] [oauth] #10: 8.4. Defining Additional Error Codes

2011-04-15 Thread oauth issue tracker
#10: 8.4. Defining Additional Error Codes Pending Consensus: 8.4. Defining Additional Error Codes In cases where protocol extensions (i.e. access token types, extension parameters, or extension grant types) require additional error codes to be used with the authorization code grant error re

[OAUTH-WG] [oauth] #9: 5.2, text for non-400 & 401 error conditions

2011-04-15 Thread oauth issue tracker
#9: 5.2, text for non-400 & 401 error conditions Pending Consensus: If the authorization server encounters an error condition other than the 400 (Bad Request) and 401 (Unauthorized) responses described above (e.g. the service is temporarily unavailable), the authorization server SHOULD includ

[OAUTH-WG] [oauth] #8: 4.1.2.1, text for 4xx or 5xx HTTP status code

2011-04-15 Thread oauth issue tracker
#8: 4.1.2.1, text for 4xx or 5xx HTTP status code Pending Consensus: The authorization server MAY set the "error" parameter value to a numerical HTTP status code from the 4xx or 5xx range, with the exception of the 400 (Bad Request) and 401 (Unauthorized) status codes. For example, if the ser

[OAUTH-WG] [oauth] #7: Incorporate Security Considerations draft into OAuth base

2011-04-15 Thread oauth issue tracker
#7: Incorporate Security Considerations draft into OAuth base -- +--- Reporter: Barry Leiba | Owner: Type: task| Status: new Priority: blocker | Milestone:

Re: [OAUTH-WG] 3rd oauth co-chair - Barry Leiba

2011-04-15 Thread Barry Leiba
> After chatting with Hannes and Blaine in Prague we figured that > it might help to get a 3rd co-chair for oauth to get the wg over > the line with the base spec and thereafter. Well, we got lucky, > so I'm glad to say Barry Leiba has agreed to take on the role > alongside Hannes and Blaine. ... >