Re: IETF WG meetings and remote participation

John C Klensin <john-ietf@jck.com> Sun, 16 February 2020 20:06 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 6D1CF120033 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2020 12:06:30 -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, 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 8HI0VpGfjjSX for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2020 12:06:29 -0800 (PST)
Received: from bsa3.jck.com (bsa3.jck.com [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5872012001B for <ietf@ietf.org>; Sun, 16 Feb 2020 12:06:29 -0800 (PST)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1j3QBL-0001ii-I7; Sun, 16 Feb 2020 15:06:23 -0500
Date: Sun, 16 Feb 2020 15:06:18 -0500
From: John C Klensin <john-ietf@jck.com>
To: Marc Petit-Huguenin <petithug@acm.org>, "Joel M. Halpern" <jmh@joelhalpern.com>
cc: IETF <ietf@ietf.org>
Subject: Re: IETF WG meetings and remote participation
Message-ID: <FE57BFD64915786AC9FCF248@JcK-HP5.jck.com>
In-Reply-To: <f8ec912f-1fbb-c774-0985-c1e83f3620b1@acm.org>
References: <CAOj+MMEMY1gxtj70+5wPOG+XHsk_nX8af4kbXD30_ULDmHMyQg@mail.gmail.com> <666CACAD-F8D4-43A1-8336-3CC9BBCC4B08@puck.nether.net> <5CBB6602066BF4A674D4D092@PSB> <CAOj+MMH_mA0+0maq+oYJZ=_GcGk5BVU9N4v0mG7hs+_f7WUiqw@mail.gmail.com> <d7196dbe-80fd-cea0-be27-e9b4aade22f9@network-heretics.com> <CAOj+MMFjhxOCOrUqzL=pbuRmPFa4-w==7=3rufR+-JX7dq+vPw@mail.gmail.com> <f68a8e6f-1bb6-2edb-86f1-d5f2f867120d@joelhalpern.com> <f8ec912f-1fbb-c774-0985-c1e83f3620b1@acm.org>
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
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-CYiNoTkX6TLJXR5Urh-aIQ4M9s>
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: Sun, 16 Feb 2020 20:06:30 -0000


--On Saturday, 15 February, 2020 14:18 -0800 Marc Petit-Huguenin
<petithug@acm.org> wrote:

>...
> I agree that material should be posted before the meeting
> starts, but I'd like to point out that at least twice I sent
> my slides at least a day ahead of time, but the chairs posted
> them just a few minutes before the session started.  And I
> remember of at least one presentation where slides were posted
> after the presentation.

Have you tried protesting to those chairs about that behavior?
If you have and gotten no useful response, have you brought this
to the attention of the relevant ADs and asked them to either
get the problem fixed or to fire the WG Chair(s) and start over?

We have had rules (or at least really strong recommendations)
for many years that require that meeting materials be posted
well before the IETF meeting starts for multiple reasons
including that having slides and other materials available in
advance helps not only some remote participants but some people
whose first language is not English.  I've seen people told that
they can't present if the materials are not posted early enough
to be useful.  If people in leadership roles are frustrating
early posting, rather than insisting on them except in very
unusual circumstances, we have a problem that needs fixing.

>...

   john