Re: [oauth] OAuth Charter Finalized

["Hannes Tschofenig" <[e-mail]>]

Hi Alexey, 

I prefer to avoid re-charting unless the scope of the work significantly
changes. 
The reason for this is efficiency. Discussing the new charter (as we can see
with this exercise) takes a lot of time that could be used more
productively. 

See also the document I recently wrote about my impression on how to reduce
delays: 
http://www.ietf.org/internet-drafts/draft-tschofenig-rai-reducing-delays-00.
txt
(written with a focus on RAI but to some extend also applicable to other
areas)

Ciao
Hannes


>-----Original Message-----
>From: Alexey Melnikov [mailto:[e-mail]] 
>Sent: 04 March, 2009 12:50
>To: Hannes Tschofenig
>Cc: 'Lisa Dusseault'; [e-mail]; 'Blaine Cook'; 
>[e-mail]
>Subject: Re: OAuth Charter Finalized
>
>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.
>>  
>>
>