IETF Logo Mail Archive

Re: [OAUTH-WG] Reminder: OAuth Security Workshop

Mike Jones <Michael.Jones@microsoft.com> Mon, 16 May 2016 11:25 UTC

Return-Path: <Michael.Jones@microsoft.com>
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 815C312D168 for <oauth@ietfa.amsl.com>; Mon, 16 May 2016 04:25:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
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 6Px0UNV3MN2t for <oauth@ietfa.amsl.com>; Mon, 16 May 2016 04:25:33 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0719.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:719]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDAE4127058 for <oauth@ietf.org>; Mon, 16 May 2016 04:25:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=3F/DJbx4cXNTr2Yjda4phufWrvXnZ+s3/zMfGC7RNPw=; b=RvYMK0+thui2pTPpjtP1R/YU4OY5VI0EpDnpjNoIH2B8eh+57WmA7q1uysBshX540M+rjeaYyUfZayheRvhHhrGtI6cV7JA5RmfO+Faw/91NssZSqocQOBwzo9Mli0Kk6subZON5iy9tzWGJr//3zwR9tfuRSz9Kt+OrVEAjOIo=
Received: from SN1PR0301MB1645.namprd03.prod.outlook.com (10.162.130.139) by SN1PR0301MB1646.namprd03.prod.outlook.com (10.162.130.140) with Microsoft SMTP Server (TLS) id 15.1.497.12; Mon, 16 May 2016 11:25:12 +0000
Received: from SN1PR0301MB1645.namprd03.prod.outlook.com ([10.162.130.139]) by SN1PR0301MB1645.namprd03.prod.outlook.com ([10.162.130.139]) with mapi id 15.01.0497.017; Mon, 16 May 2016 11:25:13 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, "oauth@ietf.org" <oauth@ietf.org>, Daniel Fett <fett@uni-trier.de>
Thread-Topic: [OAUTH-WG] Reminder: OAuth Security Workshop
Thread-Index: AQHRr14B+gAMWUiT20WKCNYPTnp8CZ+7acxA
Date: Mon, 16 May 2016 11:25:12 +0000
Message-ID: <SN1PR0301MB16459A61A685BD55B18A0B48F5770@SN1PR0301MB1645.namprd03.prod.outlook.com>
References: <5739A146.2070505@gmx.net>
In-Reply-To: <5739A146.2070505@gmx.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmx.net; dkim=none (message not signed) header.d=none;gmx.net; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [64.134.96.176]
x-ms-office365-filtering-correlation-id: da4f8a22-a2ce-4b3a-b9b2-08d37d7cbf69
x-microsoft-exchange-diagnostics: 1; SN1PR0301MB1646; 5:JJQW/GHPY4xOW1rmkC79Juuxr+GydhhE+S/AnM2anZ+4mX907LvzHZ7PIFxjWpx4O3AdAe0mgyARXeWW02CCQkNkCrKco7YVmy+4mpqTGg9W5p/p1kCSPt0JQt4O7rpbaqfo5uW0fBql8jnw/50DFg==; 24:N2XBIf8FUCHMVCdkOiUaQo17JKi/hsJsleqc+YsG0M5UUKbvdftncksCV5sDEOG4Kd3f5eIg3TwDhQm9oIHKajsl31yOZt0fK46TSe3IhUQ=; 7:tpfV/PbJ5xmdnMaxY+U07LE2qWXS1k6oCISYbn55mume5NZWchJBDFUxqngRAMPOCDlMaY5ZrIg4dZWdjbHIv+bXvXZjhROfk6J20fbMOzAphycsMFs2Vlbug3SuVo5Lh/jEtr2DfU+88VO5v3lYJqLv89FZNKTOtiA8Fk/J3fOGehGQRnZcL3pzVU3RY/H6cIpw+SKopppAm0zSpu53kw==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SN1PR0301MB1646;
x-microsoft-antispam-prvs: <SN1PR0301MB1646AFCFBCC8079872C1A7CEF5770@SN1PR0301MB1646.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026)(61426038)(61427038); SRVR:SN1PR0301MB1646; BCL:0; PCL:0; RULEID:; SRVR:SN1PR0301MB1646;
x-forefront-prvs: 09443CAA7E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(377454003)(13464003)(53754006)(122556002)(10290500002)(586003)(102836003)(3846002)(6116002)(99286002)(19580405001)(10400500002)(19580395003)(1220700001)(87936001)(5005710100001)(81166006)(66066001)(15975445007)(8936002)(8676002)(2950100001)(86612001)(33656002)(2900100001)(77096005)(86362001)(5008740100001)(74316001)(3660700001)(5001770100001)(3280700002)(50986999)(54356999)(76176999)(107886002)(2906002)(76576001)(9686002)(15650500001)(10090500001)(5004730100002)(189998001)(92566002)(106116001)(5002640100001); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR0301MB1646; H:SN1PR0301MB1645.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 May 2016 11:25:12.7978 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR0301MB1646
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/GVtJYgtV6QAKcKCHDG-TBom9or8>
Subject: Re: [OAUTH-WG] Reminder: OAuth Security Workshop
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 16 May 2016 11:25:35 -0000

I'm planning to submit a position paper to the OAuth security workshop.  I couldn't find any guidance on what the program committee is looking for in the papers.  I could imagine anything from submitting a paragraph or two describing the conversations I'd like to lead to a 10-page paper suitable for peer-reviewed publication, or anything in between.  What were you looking for?

Also, will the position papers be published in a workshop proceedings or will they be used only for determining who will be invited to participate?

				Thanks,
				-- Mike

-----Original Message-----
From: OAuth [mailto:oauth-bounces@ietf.org] On Behalf Of Hannes Tschofenig
Sent: Monday, May 16, 2016 3:31 AM
To: oauth@ietf.org
Subject: [OAUTH-WG] Reminder: OAuth Security Workshop

Hi all,

this is a reminder that the call for position paper deadline for the OAuth Security Workshop is getting closer.

Here is the link to the info:
https://infsec.uni-trier.de/events/osw2016

Ciao
Hannes

v2.23.0 | Report a Bug | By Email