Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-08 HTTP syntax comments

2011-09-26 Thread Mike Jones
: Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-08 HTTP syntax comments On 2011-09-24 02:13, Mike Jones wrote: Thanks for your comments, Julian. Responses to them, which reflect the content of draft 09, follow inline. Thanks! ... 2.1. The Authorization Request Header Field

Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-08 HTTP syntax comments

2011-09-26 Thread William Mills
...@microsoft.com To: Julian Reschke julian.resc...@gmx.de Cc: oauth@ietf.org oauth@ietf.org Sent: Monday, September 26, 2011 12:03 PM Subject: Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-08 HTTP syntax comments Thanks for your note, Julian.  Responses follow inline

Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-08 HTTP syntax comments

2011-09-26 Thread Julian Reschke
On 2011-09-26 21:03, Mike Jones wrote: ... No, b64token isn’t always there; the syntax specifies that either a b64token OR one or more auth-params will be present. Yes, that’s intended. OK then; just checking :-) ... This was the working group decision at the interim meeting and is used in

Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-08 HTTP syntax comments

2011-09-26 Thread Julian Reschke
On 2011-09-26 22:10, Mike Jones wrote: Getting rid of the b64token would be an unnecessary breaking change. ... You're at draft state, right? If you want to keep b64token *and* be able to use params, then you'll need an alternate syntax that puts the token into param (which, arguably, would

Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-08 HTTP syntax comments

2011-09-24 Thread Julian Reschke
On 2011-09-24 02:13, Mike Jones wrote: Thanks for your comments, Julian. Responses to them, which reflect the content of draft 09, follow inline. Thanks! ... 2.1. The Authorization Request Header Field The Authorization request header field is used by clients to make authenticated requests

Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-08 HTTP syntax comments

2011-09-23 Thread Mike Jones
Of Peter Saint-Andre Sent: Tuesday, August 09, 2011 11:58 AM To: Julian Reschke Cc: OAuth WG (oauth@ietf.org) Subject: Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-08 HTTP syntax comments On 8/9/11 6:06 AM, Julian Reschke wrote: 1.1. Notational Conventions ... This document uses

Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-08 HTTP syntax comments

2011-09-23 Thread Mike Jones
Reschke Sent: Tuesday, August 09, 2011 5:07 AM To: OAuth WG (oauth@ietf.org) Subject: [OAUTH-WG] draft-ietf-oauth-v2-bearer-08 HTTP syntax comments Hi there, below a few comments on dependencies to HTTPbis, and the actual header field syntax. Best regards, Julian -- snip -- 1.1

[OAUTH-WG] draft-ietf-oauth-v2-bearer-08 HTTP syntax comments

2011-08-09 Thread Julian Reschke
Hi there, below a few comments on dependencies to HTTPbis, and the actual header field syntax. Best regards, Julian -- snip -- 1.1. Notational Conventions ... This document uses the Augmented Backus-Naur Form (ABNF) notation of [I-D.ietf-httpbis-p1-messaging], which is based

Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-08 HTTP syntax comments

2011-08-09 Thread Peter Saint-Andre
On 8/9/11 6:06 AM, Julian Reschke wrote: 1.1. Notational Conventions ... This document uses the Augmented Backus-Naur Form (ABNF) notation of [I-D.ietf-httpbis-p1-messaging], which is based upon the Augmented Backus-Naur Form (ABNF) notation of [RFC5234]. Additionally, the