Return-Path: 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 BC8DB11E80C7 for ; Fri, 1 Jul 2011 18:35:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.148 X-Spam-Level: X-Spam-Status: No, score=-2.148 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001] 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 FocdnLdABaZf for ; Fri, 1 Jul 2011 18:35:05 -0700 (PDT) Received: from smtprelay02.ispgateway.de (smtprelay02.ispgateway.de [80.67.18.14]) by ietfa.amsl.com (Postfix) with ESMTP id DB1E811E8099 for ; Fri, 1 Jul 2011 18:35:04 -0700 (PDT) Received: from [79.253.51.135] (helo=[192.168.71.31]) by smtprelay02.ispgateway.de with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.68) (envelope-from ) id 1Qcp6o-0004pD-SE; Sat, 02 Jul 2011 03:34:58 +0200 References: <4E0E39EA.7040809@lodderstedt.net> <4E0E41C9.3090608@alcatel-lucent.com> User-Agent: K-9 Mail for Android In-Reply-To: <4E0E41C9.3090608@alcatel-lucent.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----RU4KKPIDFKWNKXQFH47HIICXSD3MJ6" From: Torsten Lodderstedt Date: Sat, 02 Jul 2011 03:34:54 +0200 To: igor.faynberg@alcatel-lucent.com,oauth@ietf.org Message-ID: <86a5198d-702c-4850-832b-f6c317bbf6de@email.android.com> X-Df-Sender: torsten@lodderstedt-online.de Subject: Re: [OAUTH-WG] Deutsche Telekom launched OAuth 2.0 support X-BeenThere: oauth@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OAUTH WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2011 01:35:05 -0000 ------RU4KKPIDFKWNKXQFH47HIICXSD3MJ6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Hi Igor, if this information is of broader interest - why not. Let's talk about this in Quebec. regards, Torsten. Igor Faynberg schrieb: Torsten, With many thanks for the note, I think it would be great if you documented the implementation report in an Informational RFC. In particular, the SIM-based authentication part is of particular interest here--we had this discussion on this list recently-- as it naturally extends the use of the Internet protocols in the telecom environment. I also think that such an implementation report would influence positively the OAuth profiling work that is taking place in ITU-T, OMA and other places. Igor On 7/1/2011 5:19 PM, Torsten Lodderstedt wrote: > Hi all, > > I would like to announce that we recently launched OAuth 2.0 support > in our Security Token Service. It will be used in upcoming consumer > products (e.g. Smartphone apps). > > The current implementation supports draft 10 (but is also inline with > the latest text on native apps). It has the following additional > features: > - Issuance of multiple tokens for different services in single > authorization process (Bulk User Authorization) > - Token revocation > (http://datatracker.ietf.org/doc/draft-lodderstedt-oauth-revocation/) > - custom grant types for token exchange and SIM card authentication > - Token replacement > - Parameter to explicitely request refresh token for "Resource Owner > Password Credentials" grant type > > regards, > Torsten. >_____________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth _____________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth ------RU4KKPIDFKWNKXQFH47HIICXSD3MJ6 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Hi Igor,

if this information is of broader interest - why not. Let's talk about this in Quebec.

regards,
Torsten.



Igor Faynberg <igor.faynberg@alcatel-lucent.com> schrieb:
Torsten,

With many thanks for the note, I think it would be great if you 
documented the implementation report in an Informational RFC.  In 
particular, the SIM-based authentication part is of particular interest 
here--we had this discussion on this list recently-- as it naturally 
extends the use of the Internet protocols in the telecom environment.

I also think that such an implementation report would influence 
positively  the OAuth profiling work that is taking  place in ITU-T, OMA 
and other places.

Igor

On 7/1/2011 5:19 PM, Torsten Lodderstedt wrote:
> Hi all,
>
> I would like to announce that we recently launched OAuth 2.0 support 
> in our Security Token Service. It will be used in upcoming consumer 
> products (e.g. Smartphone apps).
>
> The current implemen
 tation
supports draft 10 (but is also inline with 
> the latest text on native apps). It has the following additional 
> features:
> - Issuance of multiple tokens for different services in single 
> authorization process (Bulk User Authorization)
> - Token revocation 
> (http://datatracker.ietf.org/doc/draft-lodderstedt-oauth-revocation/)
> - custom grant types for token exchange and SIM card authentication
> - Token replacement
> - Parameter to explicitely request refresh token for "Resource Owner 
> Password Credentials" grant type
>
> regards,
> Torsten.
>

> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
------RU4KKPIDFKWNKXQFH47HIICXSD3MJ6--