Re: [OAUTH-WG] Shepherd Update for AS Server Metadata

2017-03-26 Thread Mike Jones
Actually, there are IANA actions – creating and populating a registry. Please update the shepherd review accordingly. Other than that, it looks good. Thanks, -- Mike From: Hannes Tschofenig Sent: Sunday, March 26, 2017 3:12 PM To: oauth@ietf.org

[OAUTH-WG] Milestones changed for oauth WG

2017-03-26 Thread IETF Secretariat
Changed milestone "Submit 'OAuth 2.0 Device Flow' to the IESG", set due date to April 2017 from July 2017. Changed milestone "Submit 'OAuth 2.0 Token Exchange' to the IESG for consideration as a Proposed Standard", set due date to May 2017 from July 2017. URL: https://datatracker.ietf.org/wg/oaut

[OAUTH-WG] Shepherd Update for AS Server Metadata

2017-03-26 Thread Hannes Tschofenig
Hi all, I have updated the shepherd writeup for version -06 of the "OAuth 2.0 Authorization Server Metadata" draft in preparation for the meeting. If everything goes well then we will submit this document to the IESG during the IETF meeting week. Comments appreciated! Here is the most recent ve

Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-token-exchange-07.txt

2017-03-26 Thread Torsten Lodderstedt
Hi Brian, thanks for the clarification around resource, audience and scope. Here are my comments on the draft: In section 2.1 it states: „Multiple "resource" parameters may be used to indicate that the issued token is intended to be used at the multiple resources listed.“ Can you

[OAUTH-WG] Milestones changed for oauth WG

2017-03-26 Thread IETF Secretariat
Changed milestone "Submit 'OAuth 2.0 for Native Apps' to the IESG", resolved as "Done". Changed milestone "Submit 'OAuth 2.0 Authorization Server Discovery Metadata' to the IESG", set due date to March 2017 from April 2016. Changed milestone "Submit 'OAuth 2.0 Mix-Up Mitigation'to the IESG", set

Re: [OAUTH-WG] oauth - Requested sessions have been scheduled for IETF 98

2017-03-26 Thread Nat Sakimura
Hi Denis, Thanks. Is it possible to file these separately at https://bitbucket.org/Nat/oauth-rjwtprof/issues?status=new&status=open so that each issue can be closed separately? (You need to login to bitbucket to do so.) Pull request would be nice, too, but we are going to do a bit of surgery on t