IETF Logo Mail Archive

RE: Oauth blog post

"Worley, Dale R (Dale)" <dworley@avaya.com> Sun, 29 July 2012 20:20 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DB9821F856D for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 13:20:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.737
X-Spam-Level:
X-Spam-Status: No, score=-102.737 tagged_above=-999 required=5 tests=[AWL=-0.138, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fMh6acPRe7s0 for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 13:20:25 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 4C5FB21F855F for <ietf@ietf.org>; Sun, 29 Jul 2012 13:20:25 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAEKaFVDGmAcF/2dsb2JhbABFuV6BB4IhAQEEEihPAgEIDSkQMiUBAQQbGodrnGicJJFSYAObRooQgns
X-IronPort-AV: E=Sophos;i="4.77,675,1336363200"; d="scan'208";a="20191547"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 29 Jul 2012 16:15:05 -0400
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 29 Jul 2012 16:16:06 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Sun, 29 Jul 2012 16:20:23 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Sun, 29 Jul 2012 16:18:40 -0400
Subject: RE: Oauth blog post
Thread-Topic: Oauth blog post
Thread-Index: Ac1tx0oBOtLj/WSaSjqY6zNySfmucwAAA290
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0BC7@DC-US1MBEX4.global.avaya.com>
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>
In-Reply-To: <1343593068.9245.0.camel@gwz-laptop>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Jul 2012 20:20:26 -0000

Watching a play starting with the third act is always interesting but not informative.

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?

Dale

v2.40.3 | Report a Bug | By Email | System Status