Re: [Lake] Attending IETF 113 in person?

Mališa Vučinić <malisa.vucinic@inria.fr> Tue, 22 February 2022 09:51 UTC

Return-Path: <malisa.vucinic@inria.fr>
X-Original-To: lake@ietfa.amsl.com
Delivered-To: lake@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E5E13A0BC9 for <lake@ietfa.amsl.com>; Tue, 22 Feb 2022 01:51:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 SNV5KiUHoBtC for <lake@ietfa.amsl.com>; Tue, 22 Feb 2022 01:51:22 -0800 (PST)
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 966783A0BB9 for <lake@ietf.org>; Tue, 22 Feb 2022 01:51:21 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.88,387,1635199200"; d="scan'208";a="22608452"
Received: from wifi-pro-82-243.paris.inria.fr (HELO smtpclient.apple) ([128.93.82.243]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Feb 2022 10:51:19 +0100
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Mališa Vučinić <malisa.vucinic@inria.fr>
In-Reply-To: <51236611-b45c-4a44-2cc7-a4bce5d5e443@cs.tcd.ie>
Date: Tue, 22 Feb 2022 10:51:18 +0100
Cc: lake@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <8C21E961-F0A9-4F58-87D7-CA27791AC4A0@inria.fr>
References: <E2A500AF-898F-469A-92EA-262227150411@inria.fr> <51236611-b45c-4a44-2cc7-a4bce5d5e443@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lake/cteBqhQ-DdDucVjRliIc9doJ2_E>
Subject: Re: [Lake] Attending IETF 113 in person?
X-BeenThere: lake@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Lightweight Authenticated Key Exchange <lake.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lake>, <mailto:lake-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lake/>
List-Post: <mailto:lake@ietf.org>
List-Help: <mailto:lake-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lake>, <mailto:lake-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2022 09:51:26 -0000

A kind reminder: please let the chairs know if you plan on attending the IETF 113 meeting in person. Stephen and myself plan on being there in person so we'd hate to be alone with the projector :-).

Mališa

> On 26 Jan 2022, at 13:31, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
> 
> Hi all,
> 
> On 25/01/2022 18:14, Mališa Vučinić wrote:
>> Dear all,
>> As just discussed during the interim, the IETF 113 meeting will take
>> place in Vienna, Austria in a hybrid format from 19-25 March 2022. If
>> you plan on attending the meeting in person, please let us know at
>> lake-chairs@ietf.org.
> I filled in an initial request for a 1 hour session at
> IETF 113. The form has some new options for the hybrid
> meeting allowing us to ask to not be scheduled at various
> times (e.g. "please try avoid Monday afternoon" and
> similar). Of course there are no guarantees but seems
> like no harm to try get a slot that matches our active
> participants if we can.
> 
> It'll really help us fill that in if you (especially
> those of you actively working on this topic) can let us
> know (offlist is fine) your current plans wrt attending in
> person or not. ("Planning to be there in person", "I plan
> to be remote" or "don't know" are all good information).
> I think we can guess most of the timezones involved for
> folks we need who'll be remote but no harm to let us know
> that too.
> 
> Cheers,
> S.
> <OpenPGP_0x5AB2FAF17B172BEA.asc>