[OAUTH-WG] Ben Campbell's Yes on draft-ietf-oauth-jwsreq-12: (with COMMENT)

Ben Campbell has entered the following ballot position for draft-ietf-oauth-jwsreq-12: Yes When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.i

[OAUTH-WG] Stephen Farrell's No Objection on draft-ietf-oauth-jwsreq-12: (with COMMENT)

Stephen Farrell has entered the following ballot position for draft-ietf-oauth-jwsreq-12: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to h

Re: [OAUTH-WG] Last Call: (The OAuth 2.0 Authorization Framework: JWT Secured Authorization Request (JAR)) to Proposed Standard

Hi Denis, Thought John's response went to you as well but apparently not. My replies inline: On Fri, Feb 10, 2017 at 6:15 AM, Denis wrote: > Hi Nat, > > My replies to your proposed disposition of comments are embedded in the > text. > [snip] > Section 4 states: >> >> >> >> >> * A Request O

Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsreq-12.txt

Hi Denis, Your Feb. 9 mail came too late for this round of edit as all the edits except dates were done by Feb. 8. Since then, I am continuously travelling and has been a bit challenging to send out the response apart from doing a routine posting of the draft. Will respond to your Feb. 9 mail

Re: [OAUTH-WG] Clarification about compatibility between rfc6750 and rfc7662

These specs cover two different connections: 6750 is client to RS, 7662 is RS to AS. When the authorization server and the resource server are the same box, it will know exactly why the token isn't any good and it can react accordingly. The client doesn't actually care: note that the error re

[OAUTH-WG] Alexey Melnikov's No Record on draft-ietf-oauth-jwsreq-12: (with COMMENT)

Alexey Melnikov has entered the following ballot position for draft-ietf-oauth-jwsreq-12: No Record When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to http