As side-effect that should be clarified (was: Re: IETF 107 Vancouver In-Person Meeting Cancelled)
John C Klensin <john-ietf@jck.com> Tue, 10 March 2020 22:57 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 00D0F3A086D for <ietf@ietfa.amsl.com>; Tue, 10 Mar 2020 15:57:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 He-y8ceXwPj3 for <ietf@ietfa.amsl.com>; Tue, 10 Mar 2020 15:57:13 -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 8E5303A0859 for <ietf@ietf.org>; Tue, 10 Mar 2020 15:57:13 -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 1jBnoG-000Jan-5P; Tue, 10 Mar 2020 18:57:12 -0400
Date: Tue, 10 Mar 2020 18:57:06 -0400
From: John C Klensin <john-ietf@jck.com>
To: iesg@ietf.orb
cc: ietf@ietf.org
Subject: As side-effect that should be clarified (was: Re: IETF 107 Vancouver In-Person Meeting Cancelled)
Message-ID: <661DBF3506C649AE7F8BE838@PSB>
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/BRpOpgWiZRugxUyOtfPCXKxkbro>
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: Tue, 10 Mar 2020 22:57:22 -0000
Hi. While I share the appreciation of others for what must have been a difficult decision and support it (whether I would have made the same decision or not is irrelevant, especially because I don't have the information the IESG clearly solicited and obtained), my recollection is that we have a series of dates and actions tied to the first IETF meeting of the year (see RFC 8713 for an example). The turnover dates for the IESG, IAB, etc., are (therefore) tied to that meeting. If the meeting is "cancelled", rather than, e.g., being replaced with a virtual one, the first meeting of 2020 would be the one in Madrid at the end of July. Assuming our intention is not to delay the changeover of assorted Nomcom-selected bodies, I hope someone has looked at the appropriate specifications and started working on workarounds or will do so soon. Yes, this is a procedural nit, but it is one that could come back to haunt us if it, and the transition, were not handled in an orderly way. thanks, john
- As side-effect that should be clarified (was: Re:… John C Klensin
- Re: As side-effect that should be clarified (was:… Eric Vyncke (evyncke)
- Re: As side-effect that should be clarified (was:… Adam Roach
- Re: As side-effect that should be clarified (was:… John C Klensin