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

Ted Hardie <ted.ietf@gmail.com> Wed, 08 July 2020 15:21 UTC

Return-Path: <ted.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 BAEFC3A0DD1; Wed, 8 Jul 2020 08:21:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.124
X-Spam-Level:
X-Spam-Status: No, score=-0.124 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, 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=no 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 AkrZocF5hrcW; Wed, 8 Jul 2020 08:21:30 -0700 (PDT)
Received: from mail-oi1-x22f.google.com (mail-oi1-x22f.google.com [IPv6:2607:f8b0:4864:20::22f]) (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 1268B3A0DCC; Wed, 8 Jul 2020 08:21:30 -0700 (PDT)
Received: by mail-oi1-x22f.google.com with SMTP id r8so38102931oij.5; Wed, 08 Jul 2020 08:21:30 -0700 (PDT)
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=QTkDDo8I7QK1xDPNvSCHOKF3Dyglc0jNEXPxvApzagg=; b=fm4ZhvUDrrtLmHIDz+m+bKdKc7QthWEKs2u9EaYyr5y9S2fDaGONTPHHWGtDQpX6OR H3wzDGB1SbR25cPXEehcb7TwXaGakc3qVyyWq/PW1bXHROppsWxrATqcUQVvh9hXhPcf M76KhxTBOD9lLNpJiNSUqcPkRE4PGPFPUc9zZopy4d4CPHQMtRo8m4kEqSF+PilrPtzF EapIg4D8vOC7CIgtfvI/JOtvqeYuIytTwFDQR3eACpS052f/J2JzzlZ8RHqo7i0gztBG w6oR7B7yTBO1OV5HwKCeHHg1k8orL4114x4iNaGsWDU33QASX/VQ2sWjzLBtuGj4UMhh XkRw==
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=QTkDDo8I7QK1xDPNvSCHOKF3Dyglc0jNEXPxvApzagg=; b=H7eyZYidxjoaf/o6a3MYuIQSpW90Reg/kodhsxBlxZBVljz//CQzudISJ1tFI6Jqr9 Qas3Yl/nqnBWeDZLlyK9LEXUVXPUX9O9vBLNUpFb+2c0p/frx+NSF+1U7k2j0PfRca72 Es1OpBIjaE+JDueGw2jDDAa7f74tcbcXrfs4/psMWifv5YIYESez3YuRBaRPA7dLd4yS hjlpYsbdLTIDr2Mh8SPfRfBH4aeynMSnVbJJ+j2F9/VrcT8RuEm8ObaowY2dXxi0/0y1 wpGzg8ot9xYrjYNbXT2byGce2/qAzPNgrZuhFAt/AS41sPjtxKSjaAnArqJNT1lOmbNI B2uA==
X-Gm-Message-State: AOAM530QZHYWk+s1C0n49JDs1TYF746DLZg/sdvkTDe19tcnBkqew1Mn qEuR/hHtp9HJOUo3wpqI7Bc1Oh/FDL3L0twsm1I=
X-Google-Smtp-Source: ABdhPJzr//AFtqyCZIkfyVBpQWRE49Gvf6mtCNllbTEx2qYp4GkgeKk31s2qMyQ3ddGQnkBHdPUimTuI4KwHs+KT90o=
X-Received: by 2002:aca:445:: with SMTP id 66mr7592059oie.35.1594221689285; Wed, 08 Jul 2020 08:21:29 -0700 (PDT)
MIME-Version: 1.0
References: <159318840162.4951.12569119165623562334@ietfa.amsl.com> <6.2.5.6.2.20200627023025.0b145350@elandnews.com> <07A3985F-1FB0-4F88-8651-249F443144EA@kuehlewind.net>
In-Reply-To: <07A3985F-1FB0-4F88-8651-249F443144EA@kuehlewind.net>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 08 Jul 2020 08:21:03 -0700
Message-ID: <CA+9kkMCG6WKVqVgkwuJCh8-WNqqxSijr-Nt_JAtE65U5ED2=Sw@mail.gmail.com>
Subject: Re: WG Review: Stay Home Meet Only Online (shmoo)
To: Mirja Kuehlewind <ietf@kuehlewind.net>
Cc: S Moonesamy <sm+ietf@elandsys.com>, IAB <iab@iab.org>, IESG <iesg@ietf.org>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007baf5f05a9efa960"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/c628xjLANlzANiIwFvqkd8jQ0vg>
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:21:32 -0000

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/
> >
>
>