Re: [OAUTH-WG] Proposed OAuth Extensions
Igor Faynberg <igor.faynberg@alcatel-lucent.com> Tue, 14 June 2011 05:06 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 B172B1F0C82 for <oauth@ietfa.amsl.com>; Mon, 13 Jun 2011 22:06:05 -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 5lTz3NeMtJDA for <oauth@ietfa.amsl.com>; Mon, 13 Jun 2011 22:06:02 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 2F8FA1F0C35 for <oauth@ietf.org>; Mon, 13 Jun 2011 22:06:01 -0700 (PDT)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id p5E55hgG011017 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 14 Jun 2011 00:05:46 -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 p5E55hUh031436 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 14 Jun 2011 00:05:43 -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 p5E55art010323; Tue, 14 Jun 2011 00:05:38 -0500 (CDT)
Message-ID: <4DF6EC1F.4020703@alcatel-lucent.com>
Date: Tue, 14 Jun 2011 01:05:35 -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: Barry Leiba <barryleiba@computer.org>
References: <DDDF3DB6-03F5-464B-92F1-14F059C97A6D@mac.com> <4DF3198C.8080901@lodderstedt.net> <BANLkTinzzPA1ue9MdxpZDxvWqGXSgMQ4Vg@mail.gmail.com>
In-Reply-To: <BANLkTinzzPA1ue9MdxpZDxvWqGXSgMQ4Vg@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Cc: 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: Tue, 14 Jun 2011 05:06:05 -0000
Barry, I think there has been a confusion. I also thought that the rechartering was to be discussed at the July meeting; the IETF call for rechartering was issued on May 31. My question: has the rechartering discussion been closed in the WG? (If so, I guess I missed the point when it happened.) Igor Barry Leiba wrote: > On Sat, Jun 11, 2011 at 3:30 AM, Torsten Lodderstedt > <torsten@lodderstedt.net> wrote: > >> 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. >> > > A reminder: We won't be discussing rechartering until we have the > currently chartered documents in to the IESG, which means successfully > through working-group last call. > > So those who want to talk about extensions and additions -- and > rechartering -- should have a good bit of enthusiasm to ensure that we > get those documents done tout de suite. > > Barry, as chair > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth >
- Re: [OAUTH-WG] Proposed OAuth Extensions Barry Leiba
- [OAUTH-WG] Proposed OAuth Extensions Paul Tarjan
- Re: [OAUTH-WG] Proposed OAuth Extensions Shane B Weeden
- Re: [OAUTH-WG] Proposed OAuth Extensions John Bradley
- Re: [OAUTH-WG] Proposed OAuth Extensions Torsten Lodderstedt
- Re: [OAUTH-WG] Proposed OAuth Extensions Igor Faynberg
- Re: [OAUTH-WG] Proposed OAuth Extensions Igor Faynberg
- Re: [OAUTH-WG] Proposed OAuth Extensions Barry Leiba
- Re: [OAUTH-WG] Proposed OAuth Extensions Stephen Farrell
- [OAUTH-WG] issuing multiple tokens Manger, James H
- Re: [OAUTH-WG] issuing multiple tokens Eran Hammer-Lahav
- Re: [OAUTH-WG] issuing multiple tokens Phil Hunt
- Re: [OAUTH-WG] issuing multiple tokens Eran Hammer-Lahav
- Re: [OAUTH-WG] issuing multiple tokens Phil Hunt
- Re: [OAUTH-WG] issuing multiple tokens William J. Mills
- Re: [OAUTH-WG] issuing multiple tokens Manger, James H
- Re: [OAUTH-WG] issuing multiple tokens Eran Hammer-Lahav
- Re: [OAUTH-WG] issuing multiple tokens Torsten Lodderstedt
- Re: [OAUTH-WG] issuing multiple tokens Eran Hammer-Lahav
- Re: [OAUTH-WG] issuing multiple tokens Justin Richer
- Re: [OAUTH-WG] issuing multiple tokens David Recordon
- Re: [OAUTH-WG] issuing multiple tokens Justin Richer
- Re: [OAUTH-WG] issuing multiple tokens Phil Hunt
- Re: [OAUTH-WG] issuing multiple tokens William J. Mills
- Re: [OAUTH-WG] issuing multiple tokens Phil Hunt
- Re: [OAUTH-WG] issuing multiple tokens Marius Scurtescu
- Re: [OAUTH-WG] issuing multiple tokens Torsten Lodderstedt