The consensus is to obsolete the original community drafts for 1.0 and 1.0a and point visitors to the new draft. This will be done as soon as the RFC is approved and published. I will post a few blog posts about the transition and guides for developers on how to make the necessary changes.
Given my personal focus is on OAuth 2.0, I am going to take a break from this list. If you need to get my attention, please do so on the IETF list (oa...@ietf.org) or in directly (e...@hueniverse.com). EHL On Nov 23, 11:39 pm, Eran Hammer-Lahav <e...@hueniverse.com> wrote: > How do people feel about adding a note at the top of: > > http://oauth.net/core/1.0http://oauth.net/core/1.0a > > Pointing visitors to the OAuth Core 1.0 RFC draft (pending IESG approval): > > http://tools.ietf.org/html/draft-hammer-oauth > > The new draft is significantly better and easier to read. We can't switch the > content at the two URIs above because they are linked to the IPR agreements. > We also shouldn't because those specs represent a community product that > should be kept for future documentation and many existing links point there. > > For those not paying attention, the new draft also contains a few protocol > changes and clarifications which may have a small impact in existing > libraries. For the list of changes: > > http://tools.ietf.org/html/draft-hammer-oauth-07#appendix-A > > Comments? > > EHL -- You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to oa...@googlegroups.com. To unsubscribe from this group, send email to oauth+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/oauth?hl=en.
