IETF Logo Mail Archive

Re: [107all] Update on IETF 107 Vancouver and COVID-19

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 05 March 2020 03:46 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EECE63A0AB7; Wed, 4 Mar 2020 19:46:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, 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=gmail.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 96ad5x0JT2EQ; Wed, 4 Mar 2020 19:46:16 -0800 (PST)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) (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 0DA683A0AB6; Wed, 4 Mar 2020 19:46:15 -0800 (PST)
Received: by mail-lj1-x230.google.com with SMTP id w1so4435239ljh.5; Wed, 04 Mar 2020 19:46:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hMZPC5g/ys/CRidV/POU16nqGcBhalKPZWKzbKK3zvs=; b=Te+Sr8dZaPf1Pbs4AElZ483zuyyF9GXI14Kx8FhigsCqm57aEGJGsMOzzCB6a+Mz+j S6n6LzPUaOKrCbAzL/6IBmiiMKnbklK/anZtyOZWJJEwfFMmMA4bHELUjHlyh4R1Z/fr kpWOHQNPRM1J4hUK+jNFD85LblK5Z/CgIb1dTWTCFv9AQrbAEF0Sc0vh1ePexjQxxUnJ 3YYBb+p17gI79PnAH1AoKxIeghxs23Zm29KyncetG1H/jwWwQeMtey1VZnzo7dIWMHHz JLSWh0RRGrW8SPpwuDVjkyW60YxcEfNOZeqpUSiXQGAaE2FOKnNPIit4kZXBGkb9qTBd K++w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hMZPC5g/ys/CRidV/POU16nqGcBhalKPZWKzbKK3zvs=; b=ILawmhQy8Oa7yEBB0hSW5o1MCrlRwA8936XFuGFRBtGWCpuoQgOuDr62+PeyKHEMnT 5/+PPJXHOD1zUGXYjWLmembSERggK3TnV6eWCs3d4wDr2H0dWHdiYl4sqPcqhaPEDx// yq5/XOUPDckaPwSPmzlJpR2q3PoB+1OqbaVqkrSFEtjB8FhzxBMnvo/JxIJy9W/eo4is QTdmSGTGsBRe31f9Xj+NNMZImSBOOq7460VIQNOowFHMZLIFxSJK+fuEsk8cqECYa55S /cYVyFIuPPdLv8M4Jpp6vjw36okg9M7oolvVKUA8mPDNlC2U/e0Lq/Bjuqa6cfJ0BuKE amIw==
X-Gm-Message-State: ANhLgQ0DlKeYFhQGs+akvRPNiqXLgyPJ82JFggBw6tm4kDU3+I5+Xn9B cpqovZLZk3mlw6Wmh/v93Eb8Uuj22dhT9/LmHciiMizyjQw=
X-Google-Smtp-Source: ADFU+vurfgKCwfl5Ep4YZfXVW+VnXgMDJFv57g8pJfUdolmT/+VQrkK4kYt/QGtWgtBh8c8TjB3Z3fMEct8jvM0vyBY=
X-Received: by 2002:a2e:3517:: with SMTP id z23mr807755ljz.237.1583379974281; Wed, 04 Mar 2020 19:46:14 -0800 (PST)
MIME-Version: 1.0
References: <158335136585.29295.1109218817393181187@ietfa.amsl.com> <D4FDE701-CE29-44BE-877A-B45266FEFF08@cisco.com> <CAOj+MMG+OhM9_G3+ikfGxXSqi6PMO0EJeZ=vCC3Wne=YWHLLhg@mail.gmail.com> <CAHw9_i+yuojs6gkX+GmP8xCxPZn_MBvZH66YHf42bM6Xsip4-Q@mail.gmail.com> <653F4F12-E11B-4843-90AD-EBD35D19E21D@nohats.ca>
In-Reply-To: <653F4F12-E11B-4843-90AD-EBD35D19E21D@nohats.ca>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 04 Mar 2020 21:45:48 -0600
Message-ID: <CAKKJt-dzUPvBAxo7RP_QCMwX=DgS2NJrzK1r9ucdjgUji8+nhw@mail.gmail.com>
Subject: Re: [107all] Update on IETF 107 Vancouver and COVID-19
To: Paul Wouters <paul@nohats.ca>
Cc: Warren Kumari <warren@kumari.net>, IETF <ietf@ietf.org>, "exec-director@ietf.org" <exec-director@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e95f8905a013606d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Nc8ovFALwaLhzIgmuAVPeg_rNaU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Mar 2020 03:46:18 -0000

Warren,

I'm seeing "I can help" messages on this list, which is admirable but may
not be the best way to meet this need. Could you chat with our friends on
the IESG and ask how they want to handle chairs who (potentially suddenly)
need onsite help?

It seems like we need something where everyone can keep track of who is
helping who, and something we can keep up to date throughout the week. Even
a wiki page would be an improvement over mail messages with an off-topic
subject line.

Best,

Spencer

On Wed, Mar 4, 2020 at 9:17 PM Paul Wouters <paul@nohats.ca> wrote:

> L
> On Mar 4, 2020, at 19:33, Warren Kumari <warren@kumari.net> wrote:
>
>
>
>
> Simply because the chairs cannot make it does not automatically mean that
> the WG meeting is cancelled -- WGs chairs can ask the WG secretary, or
> appoint a temporary secretary or just ask an in-person participant to do
> the physical onsite things, like bluesheets, pushing the big red button,
> etc.
>
>
> I agree and I will happily volunteer to chair a meeting where needed.
>
> Paul
>

v2.23.0 | Report a Bug | By Email