Subject: Re: Oauth blog post
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A0BC7@DC-US1MBEX4.global.avaya.com>
Date: Sun, 29 Jul 2012 13:35:44 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C3C66C81-4FC8-4B26-94D4-C35407A3E265@gmx.net>
References: <501531F7.5040404@gmail.com>
 <6.2.5.6.2.20120729073422.06d8fe10@resistor.net>
 <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net>,
 <1343593068.9245.0.camel@gwz-laptop>
 <CD5674C3CD99574EBA7432465FC13C1B22726A0BC7@DC-US1MBEX4.global.avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Precedence: list

Eran, the editor of a specification in the OAuth working group, had =
decided to step down from his editor-role because the group did not =
agree with certain design decisions (particularly with a security design =
decision). That happens also in other groups. Nothing uncommon so far.=20=


He then wrote a blog post about his decision and made various claims =
about lack of interoperability, etc. =20
This blog post got picked up by the media and various people (who have =
in many cases not been involved in the IETF OAuth group) turned it into =
bashing the IETF overall.=20

On Jul 29, 2012, at 1:18 PM, Worley, Dale R (Dale) wrote:

> Watching a play starting with the third act is always interesting but =
not informative.
>=20
> If there's a dispute worthy of attention by the *whole IETF =
membership*, could someone please summarize it (in a reasonably unbiased =
way) to bring the rest of us up to speed?
>=20
> Dale