Re: [113attendees] IETF 113 Update: 2022-02-10

Warren Kumari <warren@kumari.net> Thu, 17 February 2022 01:46 UTC

Return-Path: <warren@kumari.net>
X-Original-To: 113attendees@ietfa.amsl.com
Delivered-To: 113attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEF303A0FB8 for <113attendees@ietfa.amsl.com>; Wed, 16 Feb 2022 17:46:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari.net
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 0pGqjh8Ma5gn for <113attendees@ietfa.amsl.com>; Wed, 16 Feb 2022 17:46:28 -0800 (PST)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 363693A0FB9 for <113attendees@ietf.org>; Wed, 16 Feb 2022 17:46:28 -0800 (PST)
Received: by mail-io1-xd32.google.com with SMTP id c18so1524235ioh.0 for <113attendees@ietf.org>; Wed, 16 Feb 2022 17:46:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WQci1mJjZHkwv3l8K8O0Tiwx6ESmZB473WKk6+7qm0g=; b=UrIfoFATqstpn0PsH74QbYTiKICOYcjnFUFpSZGjiQpBSl9RuLCr7yHorPrSV2ct6u nSf9PMzdtexY93T1dRs9kz7nJ7owVrtfu4s1vQufGI+wFGcZSrXHPlDTxSa6xP7aWtiN ZyVA/03T+YZZTBgHvUdoTwoXerUeajk35S4fTYfwOuPyt607KgnhZcn7xMk/N4V0R7HQ YXsobbYiTmLbHMe7oNJZ6CpSkwr1ElwwSZCmJ4YmecxLmfNYWJJ2W7JKeGi9MaiU9AJR Mb+dDakBHlO+QNqKoHX0l984ZVUIj56arxDNgMImptg+8/ibyRWA3OUhrjHpR/fyS5qW KzNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WQci1mJjZHkwv3l8K8O0Tiwx6ESmZB473WKk6+7qm0g=; b=wGve3eA/WvlilO5vULtYGEo2HJdmauFEFE8H0IqhvORQXegnl2buaZOdQwSixzMl08 7HDpqCddK2qKS4inGsKzzjgjDwHZ0Qvob3yUASQUbcu6rYnoapAyEp1z0jVrMq8tLYkM ZD5LQDvJCCEyc4NEovLf6UaI5lQL3XxEw97T93iMIipbxuucQ9fJczvkP/QzBfKXI+ai AewGICe4yAE9X31vklZJy+qSH09dWesWD5JHnCejZBe9BdP0GN29pc/Pl5OD1edALHi/ s/1mSz6upr8PDrKbu0fY20nXQ2cv/QIj0SCL3rctYDJk/yuNhslM4tPuSuoZRjizvwN2 d+9w==
X-Gm-Message-State: AOAM530xGbagtZlp/T5y20SCtvKnHw2F4ig6sMg1g9kk04FvP8ymuHBF vKdNSr9dFXFDqI1WYU32qMtBoggWQN25/leqNLyc4YZpjsk=
X-Google-Smtp-Source: ABdhPJydDqH2/gWRH9XKtewnR3DQUwSl3eT1TemLlH5YhpGLHMijvxFejjsAtpPQdUV1jVWV18olOlKd7aFAHJVICZo=
X-Received: by 2002:a5e:a60b:0:b0:612:ad5e:c946 with SMTP id q11-20020a5ea60b000000b00612ad5ec946mr387707ioi.35.1645062386935; Wed, 16 Feb 2022 17:46:26 -0800 (PST)
MIME-Version: 1.0
References: <9989E0B6-A0F6-4A4C-A681-FDB6C046455D@staff.ietf.org> <718578905.42881.1645007735648@appsuite-gw2.open-xchange.com> <E9A51103-58DB-47ED-A2D6-D83932150754@gmail.com> <LOYP265MB2094A4F9FD7386914BB06819C2359@LOYP265MB2094.GBRP265.PROD.OUTLOOK.COM> <c0928f11-b5a4-7d27-1d66-e641009f93f4@joelhalpern.com> <656A62B6-4C21-4A37-B92C-4B5B967D7894@cisco.com>
In-Reply-To: <656A62B6-4C21-4A37-B92C-4B5B967D7894@cisco.com>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 16 Feb 2022 19:45:50 -0600
Message-ID: <CAHw9_iJf-qmHGiPqPKs=Uas23VbkzEqB6Kv7+2FvdQydJonGKw@mail.gmail.com>
To: "Eric Vyncke (evyncke)" <evyncke=40cisco.com@dmarc.ietf.org>
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, Andrew Campling <andrew.campling@419.consulting>, Bob Hinden <bob.hinden@gmail.com>, Greg Wood <ghwood@staff.ietf.org>, "113attendees@ietf.org" <113attendees@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000034fbc005d82cef06"
Archived-At: <https://mailarchive.ietf.org/arch/msg/113attendees/x8yqu6V-oE9r_zLTS2D6xUiQtOE>
Subject: Re: [113attendees] IETF 113 Update: 2022-02-10
X-BeenThere: 113attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 113 attendees <113attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/113attendees>, <mailto:113attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/113attendees/>
List-Post: <mailto:113attendees@ietf.org>
List-Help: <mailto:113attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/113attendees>, <mailto:113attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2022 01:46:33 -0000

On Wed, Feb 16, 2022 at 3:03 PM Eric Vyncke (evyncke) <evyncke=
40cisco.com@dmarc.ietf.org> wrote:

> A delegate on site would indeed be preferred and it can be decided the
> week before IETF-113.
>
> As an AD, I intend to check with all the chairs before and we will try to
> get a delegate who will be in Vienna. And I am sure that it will be the
> process for all ADs and for all WGs.
>

Yup. For at least one of my WGs, the chairs have already let me know that
they will not be able to make it to Vienna, and asked if I could please sit
in the monkey chair and do the button clickin' and mic wranglin'.
I've done this in the past, and can probably still manage it, but I figured
that it's a good opportunity for some others to experience a small bit of
what chairing is like, and so will either have someone join me, or will
have both chair seats filled with non-chairs....



>
> As we all know for 2 years :-(, the situation is always in flux. So, let's
> plan for the worst but hope for the best.
>
> Situation is not easy, but the IETF community should be able to manage it
> by being flexible.
>

Yup. I'm hoping it can even be a useful experience,
W


>
> Stay safe
>
> -éric
>
>
> On 16/02/2022, 18:12, "113attendees on behalf of Joel M. Halpern" <
> 113attendees-bounces@ietf.org on behalf of jmh@joelhalpern.com> wrote:
>
>     Given that the room needs to be observed / managed, I had assumed that
>     at least one chair or their delegate will need to be on site.
>
>     Yours,
>     Joel
>
>     On 2/16/2022 12:09 PM, Andrew Campling wrote:
>     >> On Feb 16, 2022, at 16:45, Bob Hinden <bob.hinden@gmail.com> wrote:
>     >> Further, a decision may be needed for each working group.  For
> example, if the chair(s) and responsible AD are not going to be in Vienna,
> it might be better to not hold a hybrid w.g. meeting and make it all
> virtual.
>     >
>     > Having a mixture of hybrid and virtual sessions within the meeting
> would not be a great way forward.  The meeting FAQs at
> https://www.ietf.org/how/meetings/113/faq/ already addresses remote
> participation by chairs.
>     >
>     > "Will session chairs be required to participate in person?
>     > No. Onsite participation is not required for anyone, including
> session chairs. Chairs will be able to use Meetecho to chair their sessions
> remotely. Training sessions and online guides will be available ahead of
> the meeting for remote chairs, and advance preparation is highly
> encouraged. More information will be provided as details are set."
>     >
>     >
>     > Andrew
>     >
>
>     --
>     113attendees mailing list
>     113attendees@ietf.org
>     https://www.ietf.org/mailman/listinfo/113attendees
>
> --
> 113attendees mailing list
> 113attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/113attendees
>


-- 
The computing scientist’s main challenge is not to get confused by the
complexities of his own making.
  -- E. W. Dijkstra