IETF Logo Mail Archive

Re: [oauth] OAuth Charter Finalized

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 04 March 2009 10:49 UTC

Return-Path: <alexey.melnikov@isode.com>
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 0099A3A6814 for <oauth@core3.amsl.com>; Wed, 4 Mar 2009 02:49:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level:
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599]
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 bIzHhaBdOX5i for <oauth@core3.amsl.com>; Wed, 4 Mar 2009 02:49:46 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id E2B453A67BD for <oauth@ietf.org>; Wed, 4 Mar 2009 02:49:45 -0800 (PST)
Received: from [172.16.2.184] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <Sa5c4wA054jL@rufus.isode.com>; Wed, 4 Mar 2009 10:50:12 +0000
Message-ID: <49AE5CD5.2080308@isode.com>
Date: Wed, 04 Mar 2009 10:49:57 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
References: <004901c99a6e$6b96e120$0201a8c0@nsnintra.net>
In-Reply-To: <004901c99a6e$6b96e120$0201a8c0@nsnintra.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sat, 07 Mar 2009 18:15:46 -0800
Cc: chris.newman@sun.com, oauth@ietf.org, 'Lisa Dusseault' <Lisa.Dusseault@messagingarchitects.com>
Subject: Re: [oauth] OAuth Charter Finalized
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Oauth bof discussion <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: Wed, 04 Mar 2009 10:49:47 -0000

Hi,
I have a quick question about the proposed Charter (please excuse me if 
this was discussed on the mailing list):

Hannes Tschofenig wrote:

>After delivering OAuth, the Working Group may consider defining additional
>functions and/or extensions, for example (but not limited
>to):
>  
>
WG charters typically say that work on such extra work items require WG 
rechartering.
What is the intent in this case?

> * Discovery of OAuth configuration, e.g., http://oauth.net/discovery/1.0.
> * Comprehensive message integrity, e.g.,
>http://oauth.googlecode.com/svn/spec/ext/body_hash/1.0/drafts/1/spec.html.
> * Recommendations regarding the structure of the token.
> * Localization, e.g.,
>http://oauth.googlecode.com/svn/spec/ext/language_preference/1.0/drafts/2/sp
>ec.html.
> * Session-oriented tokens, e.g.,
>http://oauth.googlecode.com/svn/spec/ext/session/1.0/drafts/1/spec.html.
> * Alternate token exchange profiles, e.g.,
>draft-dehora-farrell-oauth-accesstoken-creds-00.
>  
>

v2.23.0 | Report a Bug | By Email