Coming right after IETF-80 in -15. EHL
From: Freeman, Tim [mailto:tim.free...@hp.com] Sent: Friday, March 25, 2011 5:16 PM To: Eran Hammer-Lahav; OAuth WG Subject: What's up with the secuity considerations? (was RE: Preview of -14) What's the plan for filling in the security considerations? In the draft below I see: >9. Security Considerations > > [[ TBD ]] Tim Freeman Email: tim.free...@hp.com<mailto:tim.free...@hp.com> Desk in Palo Alto: (650) 857-2581 Home: (408) 774-1298 Cell: (408) 348-7536 From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf Of Eran Hammer-Lahav Sent: Friday, March 25, 2011 12:53 AM To: OAuth WG Subject: [OAUTH-WG] Preview of -14 https://github.com/hueniverse/draft-ietf-oauth/raw/master/draft-ietf-oauth-v2.txt This includes all the feedback received until now. My queue is now empty except for the need to propose a new error code extensibility solution to accommodate the needs of protocol extensions. I replied back to all feedback, and unless your suggestions were purely editorial or accepted in which case I ignored them in my response, I clearly indicated why they were rejected. Feel free to reply back. However, if your request was rejected due to past consensus (or lack of), you should talk to the chairs and try to get the subject back on the WG's agenda. -14 does not include any normative changes, no new features, and no changes to existing code compliant with -13. While anything can happen between now and publication as RFC, OAuth 2.0 can be considered done. I will publish this once the queue is open again. EHL
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
