Re: As side-effect that should be clarified (was: Re: IETF 107 Vancouver In-Person Meeting Cancelled)

John C Klensin <john-ietf@jck.com> Wed, 11 March 2020 04:52 UTC

Return-Path: <john-ietf@jck.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 38A633A1137 for <ietf@ietfa.amsl.com>; Tue, 10 Mar 2020 21:52:26 -0700 (PDT)
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, SPF_HELO_NONE=0.001, SPF_NONE=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 h6kPi6_HmMPf for <ietf@ietfa.amsl.com>; Tue, 10 Mar 2020 21:52:25 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DE963A1134 for <ietf@ietf.org>; Tue, 10 Mar 2020 21:52:25 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1jBtLy-000KMR-6l; Wed, 11 Mar 2020 00:52:22 -0400
Date: Wed, 11 Mar 2020 00:52:16 -0400
From: John C Klensin <john-ietf@jck.com>
To: Adam Roach <adam@nostrum.com>, iesg@ietf.orb
cc: ietf@ietf.org
Subject: Re: As side-effect that should be clarified (was: Re: IETF 107 Vancouver In-Person Meeting Cancelled)
Message-ID: <CF75103C3ABA2731FE32C963@PSB>
In-Reply-To: <de74a674-8ffb-7b3c-d78e-5ef591db8634@nostrum.com>
References: <661DBF3506C649AE7F8BE838@PSB> <de74a674-8ffb-7b3c-d78e-5ef591db8634@nostrum.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/30NON0DztLyaRCXuWTmWifxknBE>
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: Wed, 11 Mar 2020 04:52:26 -0000


--On Tuesday, March 10, 2020 19:24 -0500 Adam Roach
<adam@nostrum.com> wrote:

> On 3/10/2020 5:57 PM, John C Klensin wrote:
>> If the meeting is "cancelled", rather than, e.g., being
>> replaced with a virtual one...
> 
> 
> John --
> 
> Please refer back to the original message in this thread, an
> excerpt of which is quoted below. Thanks.
> 
> 
> On 3/10/2020 2:10 PM, The IESG wrote:
>> The IESG is working on an alternative all-virtual agenda for
>> the week of March 21-27 with a limited schedule adapted to
>> accommodate the time zones of as many participants as
>> possible.

Adam,

I did read that.  I also read the subject line of the
announcement (quoted above), which I believe contains the words
"cancelled" and did not say, for example, "IETF 107 will be held
without an in-person meeting in Vancouver".  I'm glad the IESG
has this under control on behalf of the community, but I hope
you can understand the concern resulting from that terminology.

thanks,
   john