Re: WG Review: Stay Home Meet Only Online (shmoo)

Mirja Kuehlewind <ietf@kuehlewind.net> Wed, 08 July 2020 15:29 UTC

Return-Path: <ietf@kuehlewind.net>
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 55ECD3A0E49; Wed, 8 Jul 2020 08:29:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.076
X-Spam-Level:
X-Spam-Status: No, score=0.076 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 mbj5j6hRv3jj; Wed, 8 Jul 2020 08:29:43 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2807B3A0E1E; Wed, 8 Jul 2020 08:29:40 -0700 (PDT)
Received: from p200300dee7007a003d8b8bffd80b599d.dip0.t-ipconnect.de ([2003:de:e700:7a00:3d8b:8bff:d80b:599d]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1jtC0o-0007uc-Bz; Wed, 08 Jul 2020 17:29:30 +0200
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: WG Review: Stay Home Meet Only Online (shmoo)
From: Mirja Kuehlewind <ietf@kuehlewind.net>
In-Reply-To: <CA+9kkMCG6WKVqVgkwuJCh8-WNqqxSijr-Nt_JAtE65U5ED2=Sw@mail.gmail.com>
Date: Wed, 08 Jul 2020 17:29:29 +0200
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>, S Moonesamy <sm+ietf@elandsys.com>, IESG <iesg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C3C80E03-E4B5-4464-94C2-AA4852EA799C@kuehlewind.net>
References: <159318840162.4951.12569119165623562334@ietfa.amsl.com> <6.2.5.6.2.20200627023025.0b145350@elandnews.com> <07A3985F-1FB0-4F88-8651-249F443144EA@kuehlewind.net> <CA+9kkMCG6WKVqVgkwuJCh8-WNqqxSijr-Nt_JAtE65U5ED2=Sw@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1594222181;4fb76e97;
X-HE-SMSGID: 1jtC0o-0007uc-Bz
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LrNK2qhua_CepGhA_021HS8JGSE>
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, 08 Jul 2020 15:29:50 -0000

Hi Ted, hi all,

Yes, that is very true. Charters are sent to the IAB in the internal review phase and member can comment then already as well. What I meant is that there is no formal step that “requires” feedback from the IAB (like a ballot position in the datatracker or something). 

Mirja



> On 8. Jul 2020, at 17:21, Ted Hardie <ted.ietf@gmail.com> wrote:
> 
> Hi Mirja
> 
> On Wed, Jul 8, 2020 at 3:24 AM Mirja Kuehlewind <ietf@kuehlewind.net> wrote:
> Hi,
> 
> On this point:
> 
> > One of reasons for not to tackling a topic is if there isn't any expertise in the IETF to work on that.  It is the responsibility of the Internet Architecture Board (IAB) to provide advice on that and it is up to the Internet Engineering Steering Group (IESG) to give its approval for the work to proceed.  The latest IAB minutes, which are dated May 27, does not show any review of the proposed charter.  Will the IAB review the proposed charter before it is approved by the IESG?
> 
> IAB members can review proposed charters during community review process but there is no formal step for the IAB to review all proposed charters.
> 
> There is a difference between IAB review and community review, as the IAB review takes place during the "internal review" phase, rather than the "external review" phase, at least according to this process:
> 
> As of the time of writing, all proposed working group charters are sent to the IAB (“sent for Internal Review”) before being sent to the broader community (“sent for External Review”). When a proposed charter is sent for External Review, it goes via the IETF-Announce mailing list to the entire IETF community and via the New-Work mailing list to a number of other SDOs that have liaison relationships with IETF, so External Review is very public.
> 
>  (from https://www.iab.org/documents/correspondence-reports-documents/2012-2/iab-member-roles-in-evaluating-new-work-proposals/).
> 
> While that may not be a "formal step", it's probably worth keeping in mind, as some elements of a proposal may change during internal review.
> 
> regards,
> 
> Ted Hardie
> 
> I'm not sure why you may think this is especially needed in this case given meeting planning lies in responsibility of the IESG (or LCC with respect to financial and contractual aspects)…?
> 
> Mirja
> 
> 
> 
> > On 27. Jun 2020, at 14:30, S Moonesamy <sm+ietf@elandsys.com> wrote:
> > 
> > Dear Internet Engineering Steering Group,
> > At 09:20 AM 26-06-2020, The IESG wrote:
> >> A new IETF WG has been proposed in the General Area. The IESG has not made
> >> any determination yet. The following draft charter was submitted, and is
> >> provided for informational purposes only. Please send your comments to the
> > 
> > I would like to thank Mr Kaduk for taking the time to respond to my comment [1] about the proposed charter.
> > 
> > I read an extract of a book about "shmoo" after seeing a comment [2] about it.  The cultural reference to class issues is quite interesting for an organization which advertizes itself as a "large open international community".  The proposed charter was discussed on a mailing list which is described as: "a design team list to identify issues that would arise should an IETF meeting ever be held with O(1000) 'remote' participants".     Was there any public report from the design team?
> > 
> > It is unfortunate that the "design team" has decided not to consider the potential impact of maintaining two classes of "participants".  The disregard for the topic is a good indicator of whether words such as "inclusiveness" can be taken seriously.
> > 
> > One of reasons for not to tackling a topic is if there isn't any expertise in the IETF to work on that.  It is the responsibility of the Internet Architecture Board (IAB) to provide advice on that and it is up to the Internet Engineering Steering Group (IESG) to give its approval for the work to proceed.  The latest IAB minutes, which are dated May 27, does not show any review of the proposed charter.  Will the IAB review the proposed charter before it is approved by the IESG?
> > 
> > The proposed charter has "TBD" under "milestones".  That is not compliant with the contract which the proposed working group is seeking.
> > 
> > Will the "high-level principles" be about hopes or ambitions to achieve something?
> > 
> > The "experience of handling meeting planning" is something internal to the IESG.  Is that documented anywhere?  Is that even relevant given that the proposed group was not involved in meeting planning?
> > 
> > Why is the proposed group proposing to work on "functional requirements"?  Isn't that the work of the IETF Administration LLC?
> > 
> > Some parts of the proposed charter such as "cadence of meeting scheduling ..." sounds like MTGVENUE-bis as that (concluded) group previously worked on that.  The group was closed in March.  Does that mean that the previous work caused some issues which was only noticed three months after the MTGVENUE working group was closed?
> > 
> > Does the cadence of meeting scheduling affect NomCom eligibility?  Did meeting planning have an impact on NomCom eligibility?
> > 
> > Regards,
> > S. Moonesamy
> > 
> > 1. https://mailarchive.ietf.org/arch/msg/manycouches/-KT9e9MkDgDpHS57La9f5IxMSNI/
> > 2. https://mailarchive.ietf.org/arch/msg/manycouches/uQdAjhubeYVoIOP_CWd4O_xSYkQ/ 
> > 
>