IETF Logo Mail Archive

Re: [OAUTH-WG] Revised Section 3

Dick Hardt <dick.hardt@gmail.com> Sat, 23 April 2011 01:25 UTC

Return-Path: <dick.hardt@gmail.com>
X-Original-To: oauth@ietfc.amsl.com
Delivered-To: oauth@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id CA432E06C6 for <oauth@ietfc.amsl.com>; Fri, 22 Apr 2011 18:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ncs0ALsdRIUy for <oauth@ietfc.amsl.com>; Fri, 22 Apr 2011 18:25:34 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by ietfc.amsl.com (Postfix) with ESMTP id 09D67E06C0 for <oauth@ietf.org>; Fri, 22 Apr 2011 18:25:33 -0700 (PDT)
Received: by pvh1 with SMTP id 1so685644pvh.31 for <oauth@ietf.org>; Fri, 22 Apr 2011 18:25:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to:x-mailer; bh=dCm6slZ4cqw6zAcXM+afWCTmIgzjzCqUlCHlIPN1ms4=; b=kAV+tvWD1hqr/sTFhdp3j5PRl1XPNj9AdQAIwY8MDSO1/LXSwnM/ZcqlSG6tricewy TEqSbBbHegRCglmkoQunrV/kjomMOYeecwjVFwuUe1bVG6uN0+FLzOpRkzrQWUvoY51v ArBT+V1ITrMp8ZbFE74OB8SSiYIHivEAAxkV0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer; b=GQM9XEpBo/Gjkr2gdtBsfKx6jf4wqX7CpAPl79fq6anjsCmSlqxqexdOf1dwk0suuD b/xUd43P9ZI6J8TUebb4q2Yd6LJAL+dNf2CBnv268f1MIRNo+nNHK4KYnyLSngQVaJhw RwvmlpJ/D2Oy8cIg9tgxWH+ABq9xCHLg/3nYg=
Received: by 10.68.36.199 with SMTP id s7mr2652800pbj.131.1303521933470; Fri, 22 Apr 2011 18:25:33 -0700 (PDT)
Received: from [192.168.1.16] (c-24-5-83-209.hsd1.ca.comcast.net [24.5.83.209]) by mx.google.com with ESMTPS id r5sm2326254pbe.101.2011.04.22.18.25.30 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 22 Apr 2011 18:25:32 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary="Apple-Mail-6-944698505"
From: Dick Hardt <dick.hardt@gmail.com>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E723447535BBFA8@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Date: Fri, 22 Apr 2011 18:25:29 -0700
Message-Id: <3F9C736A-3DA6-4712-AFD1-93BFD7648CA8@gmail.com>
References: <B26C1EF377CB694EAB6BDDC8E624B6E71A480C92@CH1PRD0302MB115.namprd03.prod.outlook.com> <C9D748FE.11633%eran@hueniverse.com> <B26C1EF377CB694EAB6BDDC8E624B6E71A480CF1@CH1PRD0302MB115.namprd03.prod.outlook.com> <90C41DD21FB7C64BB94121FBBC2E723447535BBF8F@P3PW5EX1MB01.EX1.SECURESERVER.NET> <B26C1EF377CB694EAB6BDDC8E624B6E71A480D35@CH1PRD0302MB115.namprd03.prod.outlook.com> <90C41DD21FB7C64BB94121FBBC2E723447535BBFA8@P3PW5EX1MB01.EX1.SECURESERVER.NET>
To: Eran Hammer-Lahav <eran@hueniverse.com>
X-Mailer: Apple Mail (2.1084)
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Revised Section 3
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Apr 2011 01:25:35 -0000

On 2011-04-22, at 5:18 PM, Eran Hammer-Lahav wrote:

> Are you kidding me? “Not the best spelled out feature”?
>  
> It is not spelled at all. Not using a single character! Maybe Dick was using magic ink for this section.

No magic ink was used. :)

Tony: I looked over your last emails and while I can guess what you want, a *clear* description of the flow you are looking for would enable me to bridge the gap between WRAP and OAuth 2.0.

-- Dick

v2.23.0 | Report a Bug | By Email