IETF Logo Mail Archive

[OAUTH-WG] I-D: multiple access tokens

Torsten Lodderstedt <torsten@lodderstedt.net> Sat, 10 July 2010 17:08 UTC

Return-Path: <torsten@lodderstedt.net>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5093C3A67CF for <oauth@core3.amsl.com>; Sat, 10 Jul 2010 10:08:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.352
X-Spam-Level:
X-Spam-Status: No, score=0.352 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p4Eh-weMFu7k for <oauth@core3.amsl.com>; Sat, 10 Jul 2010 10:07:52 -0700 (PDT)
Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.31.28]) by core3.amsl.com (Postfix) with ESMTP id ACCE43A6A2F for <oauth@ietf.org>; Sat, 10 Jul 2010 10:07:47 -0700 (PDT)
Received: from p4fff30bf.dip.t-dialin.net ([79.255.48.191] helo=[127.0.0.1]) by smtprelay01.ispgateway.de with esmtpa (Exim 4.68) (envelope-from <torsten@lodderstedt.net>) id 1OXdWp-0004AS-1h; Sat, 10 Jul 2010 19:07:51 +0200
Message-ID: <4C38A8DA.4010105@lodderstedt.net>
Date: Sat, 10 Jul 2010 19:07:38 +0200
From: Torsten Lodderstedt <torsten@lodderstedt.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5
MIME-Version: 1.0
To: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
References: <4BFAA6AB.8040809@lodderstedt.net> <4BFC3142.6010506@lodderstedt.net> <AANLkTilRireowt1v8SidOiMJ-7ilBfvSqAiNfecA7uwR@mail.gmail.com> <4BFC371A.5040109@lodderstedt.net> <AANLkTikF1wk5eqme-N4RHviB5M7HzGYzy0p1mGuaux5g@mail.gmail.com> <4C07F407.4050305@lodderstedt.net> <1275663845.7068.94.camel@localhost.localdomain> <4C09732B.5040800@lodderstedt.net> <4C0F6A9C.2060607@lodderstedt.net> <4C1108C4.9040501@lodderstedt.net> <AANLkTils4bwYtv5u9yXJycqTQ_NFt0BUtA7P0kBTITpX@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343B3EAF7473@P3PW5EX1MB01.EX1.SECURESERVER.NET>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72343B3EAF7473@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Content-Type: multipart/mixed; boundary="------------000208050506090706060308"
X-Df-Sender: 141509
Subject: [OAUTH-WG] I-D: multiple access tokens
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 10 Jul 2010 17:08:06 -0000

I just finished the first version of my I-D on "multiple access tokens" 
and would like to initiate a discussion whether the WG sees this as a 
potential WG item.

Due to the pre-meeting cutoff date for submitting new drafts, I cannot 
submit it to the IETF site now. Since I don't want to lose weeks, I 
attached the document to this mail. I will upload the document to the 
IETF site after 2010-07-26.

I would appreciate any feedback on the I-D.

regards,
Torsten.

Am 11.06.2010 01:02, schrieb Eran Hammer-Lahav:
> I strongly believe that it should be first presented as an I-D. This is true in general for most proposed changes of this size. It is hard to tell how big of an impact a change like this will have without some actual text. Once proposed, the WG can decide if this is of interest as a WG item. If it is, we discuss the technical details. Then, we can have a chat about editorial work and how to best fit it within the OAuth specifications framework.
>
> Hope this helps.
>
> EHL

v2.23.0 | Report a Bug | By Email