IETF Logo Mail Archive

Re: [OAUTH-WG] Meeting Minutes

Antonio Sanso <asanso@adobe.com> Tue, 25 November 2014 09:44 UTC

Return-Path: <asanso@adobe.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 695521A0099 for <oauth@ietfa.amsl.com>; Tue, 25 Nov 2014 01:44:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7aXOHsIZ6q0I for <oauth@ietfa.amsl.com>; Tue, 25 Nov 2014 01:44:26 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0057.outbound.protection.outlook.com [207.46.100.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63B9B1A0076 for <oauth@ietf.org>; Tue, 25 Nov 2014 01:44:26 -0800 (PST)
Received: from CO1PR02MB206.namprd02.prod.outlook.com (10.242.165.144) by CO1PR02MB205.namprd02.prod.outlook.com (10.242.165.139) with Microsoft SMTP Server (TLS) id 15.1.26.15; Tue, 25 Nov 2014 09:44:24 +0000
Received: from CO1PR02MB206.namprd02.prod.outlook.com ([169.254.8.208]) by CO1PR02MB206.namprd02.prod.outlook.com ([169.254.8.208]) with mapi id 15.01.0026.003; Tue, 25 Nov 2014 09:44:24 +0000
From: Antonio Sanso <asanso@adobe.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Thread-Topic: [OAUTH-WG] Meeting Minutes
Thread-Index: AQHP/7fjz6ylOLlk2kiZ87Mq+ura6pxxKmaA
Date: Tue, 25 Nov 2014 09:44:24 +0000
Message-ID: <826F00DA-131F-42D7-B07B-3ABE949985E0@adobe.com>
References: <54657179.2010303@gmx.net>
In-Reply-To: <54657179.2010303@gmx.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [192.147.117.11]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:CO1PR02MB205;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:CO1PR02MB205;
x-forefront-prvs: 040655413E
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(24454002)(189002)(199003)(377454003)(53754006)(51704005)(52604005)(19580395003)(19580405001)(110136001)(122556002)(46102003)(95666004)(99286002)(99396003)(107046002)(120916001)(106356001)(106116001)(33656002)(105586002)(97736003)(15202345003)(40100003)(31966008)(66066001)(36756003)(64706001)(20776003)(92726001)(101416001)(86362001)(92566001)(21056001)(54356999)(87936001)(83716003)(82746002)(4396001)(50986999)(2656002)(76176999)(62966003)(77096003)(77156002)(15975445006)(104396001); DIR:OUT; SFP:1101; SCL:1; SRVR:CO1PR02MB205; H:CO1PR02MB206.namprd02.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
Content-Type: text/plain; charset="us-ascii"
Content-ID: <29DB230DE8E2F74EBB83F8040784556E@namprd02.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: adobe.com
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/CaH4sUaBvu3iujRwH9F7PndbQZs
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Meeting Minutes
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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, 25 Nov 2014 09:44:28 -0000

hi Hannes ,

thanks for sharing the minutes.

about

======
John reported a security problem where a 302 redirect without user interaction causes security problems. 
Do we want to say somthing about this?  Implementation guidance somewhere?

Chairs: Is this written up?

John: Yes, on mailing list.

Justin: This might be a good example for the oauth.net article section because it's implementation advice, not a change to the protocol.
=====

I assume (maybe wrong) this might be about [0].
My question is there any timeline/action plan for this topic?
I am more than happy if I could contribute or try to help out

regards

antonio

[0] http://www.ietf.org/mail-archive/web/oauth/current/msg13367.html


On Nov 14, 2014, at 4:05 AM, Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:

> Hi all,
> 
> here is a draft version of the meeting minutes:
> http://www.ietf.org/proceedings/91/minutes/minutes-91-oauth
> 
> Thanks to Brian Rosen for taking notes.
> 
> Comments are welcome!
> 
> Ciao
> Hannes & Derek
> 
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email