IETF Logo Mail Archive

Re: [OAUTH-WG] Proposed OAuth Extensions

Igor Faynberg <igor.faynberg@alcatel-lucent.com> Mon, 13 June 2011 17:42 UTC

Return-Path: <igor.faynberg@alcatel-lucent.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 225BA11E80AC for <oauth@ietfa.amsl.com>; Mon, 13 Jun 2011 10:42:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ndDIOiQ5bZqP for <oauth@ietfa.amsl.com>; Mon, 13 Jun 2011 10:42:12 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 86DBB11E80A9 for <oauth@ietf.org>; Mon, 13 Jun 2011 10:42:12 -0700 (PDT)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id p5DHgBj7018006 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 13 Jun 2011 12:42:11 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p5DHgA4n015098 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 13 Jun 2011 12:42:10 -0500
Received: from [135.244.25.71] (faynberg.lra.lucent.com [135.244.25.71]) by umail.lucent.com (8.13.8/TPES) with ESMTP id p5DHg9rt012323; Mon, 13 Jun 2011 12:42:09 -0500 (CDT)
Message-ID: <4DF64BF3.7010602@alcatel-lucent.com>
Date: Mon, 13 Jun 2011 13:42:11 -0400
From: Igor Faynberg <igor.faynberg@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Torsten Lodderstedt <torsten@lodderstedt.net>
References: <DDDF3DB6-03F5-464B-92F1-14F059C97A6D@mac.com> <4DF3198C.8080901@lodderstedt.net>
In-Reply-To: <4DF3198C.8080901@lodderstedt.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Cc: John Bradley <jbradley@mac.com>, OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Proposed OAuth Extensions
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: igor.faynberg@alcatel-lucent.com
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: Mon, 13 Jun 2011 17:42:13 -0000

+1

Igor

Torsten Lodderstedt wrote:
> Hi,
>
> I also see the need to request and issue multiple tokens in a single 
> authorization process. There has already been some discussion about 
> this topic roughly a year ago:
> - http://www.ietf.org/mail-archive/web/oauth/current/msg02688.html.
> - http://www.ietf.org/mail-archive/web/oauth/current/msg03639.html
>
> We at Deutsche Telekom have implemented an OAuth 2.0 extension 
> supporting that use case. It's called "bulk authorization".
>
> Would that be an interessting topic we could discuss at IETF-81 for 
> the re-chartering?  I could present our approach there.
>
> regards,
> Torsten.
>
> Am 10.06.2011 21:08, schrieb John Bradley:
>> We have identified the need to request multiple tokens as one issue 
>> that we would have to extend.
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email