IETF Logo Mail Archive

Re: [OAUTH-WG] Security Considerations Section Proposal -02

Eran Hammer-Lahav <eran@hueniverse.com> Thu, 07 April 2011 14:08 UTC

Return-Path: <eran@hueniverse.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 E903828C128 for <oauth@core3.amsl.com>; Thu, 7 Apr 2011 07:08:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.649
X-Spam-Level:
X-Spam-Status: No, score=-2.649 tagged_above=-999 required=5 tests=[AWL=-0.050, 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 5Npw2yer+StE for <oauth@core3.amsl.com>; Thu, 7 Apr 2011 07:08:31 -0700 (PDT)
Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by core3.amsl.com (Postfix) with SMTP id 249F828C0FB for <oauth@ietf.org>; Thu, 7 Apr 2011 07:08:29 -0700 (PDT)
Received: (qmail 14287 invoked from network); 7 Apr 2011 14:10:13 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.19) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 7 Apr 2011 14:10:11 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.19]) by P3PW5EX1HT001.EX1.SECURESERVER.NET ([72.167.180.19]) with mapi; Thu, 7 Apr 2011 07:10:08 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Torsten Lodderstedt <torsten@lodderstedt.net>, OAuth WG <oauth@ietf.org>
Date: Thu, 07 Apr 2011 07:10:01 -0700
Thread-Topic: [OAUTH-WG] Security Considerations Section Proposal -02
Thread-Index: Acv09T9GhyV08uv6RkqVOcIesRwQ0AAOBwcQ
Message-ID: <90C41DD21FB7C64BB94121FBBC2E7234465664E1A1@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <4D9D6759.3070904@lodderstedt.net>
In-Reply-To: <4D9D6759.3070904@lodderstedt.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] Security Considerations Section Proposal -02
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <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: Thu, 07 Apr 2011 14:08:32 -0000

I think it would be best to publish -16 immediately with this text, mark it as pending consensus, and continue with a single document. This will make it easier for new readers as well as for everyone else.

I will push it out in a couple of hours.

EHL

> -----Original Message-----
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf
> Of Torsten Lodderstedt
> Sent: Thursday, April 07, 2011 12:27 AM
> To: OAuth WG
> Subject: [OAUTH-WG] Security Considerations Section Proposal -02
> 
> Hi all,
> 
> I just posted a new revision of the proposed text for the core draft's security
> considerations section (http://tools.ietf.org/html/draft-lodderstedt-oauth-
> securityconsiderations-02).
> 
> The text makes some strong statements wrt client secrets/authentication,
> HTTPS, refresh tokens and other topics. This is to facilitate a clear and
> understandable specification while also considering (and supporting) _all_
> relevant use cases (e.g. native apps).
> 
> Since this is the last major building block of the draft, we would like to include
> this text as soon as possible.
> 
> So please give your feedback soon!
> 
> thanks in advance,
> Torsten.
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email