Re: [OAUTH-WG] Virtual OAuth Security Workshop 2020, July 21-24

Daniel Fett <> Sun, 31 May 2020 16:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 358C43A08A5 for <>; Sun, 31 May 2020 09:12:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_NONE=0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id AJu-Uyj-L2DB for <>; Sun, 31 May 2020 09:12:38 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 38E413A089C for <>; Sun, 31 May 2020 09:12:38 -0700 (PDT)
Received: from authenticated-user (PRIMARY_HOSTNAME [PUBLIC_IP]) by (Postfix) with ESMTPA id 70DE364C9 for <>; Sun, 31 May 2020 16:12:34 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=dkim; t=1590941554; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=0pg9wp5zZOcLbxmGI1Aju+k8lXCKo+OrriAeWVNuW90=; b=p82B5WNjxozJy5LVq5BZCXu+Ue/VLX6Be17EFTYykOZ1VNKolXP8gWKXpa1V9AHWdehUgC O0BNWlGCWt+KDUukNo5tmOIc8/Od2bJ5e9VC0UEqVtffdQGrU74J98S247dFP2WXfJwFWr G4ntQKdFZYxXnAL37NtjqpvxDUd3Rbg=
From: Daniel Fett <>
To: "" <>
References: <>
Message-ID: <>
Date: Sun, 31 May 2020 18:12:33 +0200
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: multipart/alternative; boundary="------------1BF0E45514DE469B29F9B68F"
Content-Language: en-US
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=dkim; t=1590941555; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=0pg9wp5zZOcLbxmGI1Aju+k8lXCKo+OrriAeWVNuW90=; b=qQPbYMbWoZHS5pfR/dcU9DwoM4/o2OUa+JJxYySIxYOmiWpcvcBAsK02Dmw2TIJf3KEXdm exdkcTYWmc5FfYu0SsKP8cNprhugox53+Cc3cXVXdxkdrorApKM4lKi9dofy3QnyG0UWdN s2DyYwarBm1fF57oK4dB96C4wQfq44o=
ARC-Seal: i=1; s=dkim;; t=1590941555; a=rsa-sha256; cv=none; b=QT1FwOLWd09Jf3Na0n80qy3Lo7lLwp/yNn8lAX30eGpMe2EH+PlIZdFxfIs59zY8PvPrTV rBOGjTHaS+FMOF2l3H5gReMbZOgvcqFyv5WX3QsVw2G9AH60R66AulO2us+cuVp2bgE4C9 faFYZ7c/KP/9+QjvwjOSq9e0Z3Nj+5w=
ARC-Authentication-Results: i=1;; auth=pass
X-Spamd-Bar: ++
Authentication-Results:; auth=pass
Archived-At: <>
Subject: Re: [OAUTH-WG] Virtual OAuth Security Workshop 2020, July 21-24
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OAUTH WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 31 May 2020 16:12:40 -0000

Hi all,

I hope that many of you can make it to the virtual OSW!

While the official call is closed, we can easily fit some more
tutorials/workshops or talks into the schedule. If you are interested to
host a session, please contact me.

Finding good start and end times for an event with participants from all
over the world is not easy. To find out which time zones we need to
accommodate for and when people in these time zones are usually working,
I took the mails from this mailing list as a guide line. I used a python
script to scrape and analyze the mails from the past 17 months. If you
are interested in the results, please see this sheet:

In the end, the schedule ended up very close to the one of IETF 108,
which hopefully works for many attendees.


Am 31.05.20 um 17:52 schrieb Daniel Fett:
> Website:
> Registration:
> Twitter:
> The OAuth Security Workshop 2020 will be held as a virtual event on July
> 21 to 24. As Zoom Fatigue is a real thing, the workshop will be spread
> over four days (compared to the originally planned three days).
> As in 2019, the OSW will be a mix of pre-scheduled tutorials and talks,
> and an unconference part where every participant can propose and conduct
> a session. Sessions in the unconference are often driven by recent
> discussions in the community, but can also be used to deep-dive into
> topics from the talks and tutorials, or to discuss or work on any
> OAuth-related topic.
> The event will be free of charge. A prior registration is required:
> Schedule outline:
> July 21 (Tutorials/Workshops day): On the first day, we will have two
> tutorial slots with up to 3 hours each. If needed, multiple tutorials
> can run in parallel.
> July 22 (Talks day): The second day starts with the official opening of
> the workshop, followed by two parallel tracks of talks with eight talk
> slots each. Each talk is 25 minutes.
> July 23 and July 24 (Unconference days): At the beginning of each of the
> two days, sessions are proposed and scheduled in the plenum. Sessions
> can be anything from talks to open discussions or tutorials. We will
> have up to three parallel session tracks with five slots each (four plus
> closing on the last day), 45 minutes each.
> The precise times in various time zones can be found on the website:
> The full schedule for talks and workshops will be published in June.
> Session proposals for the unconference part can be submitted ahead of
> time on the registration website.
> If you have any questions, feel free to contact me (
> -Daniel
> _______________________________________________
> OAuth mailing list