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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 16 July 2020 14:40 UTC

Return-Path: <spencerdawkins.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 DF2FC3A0978 for <ietf@ietfa.amsl.com>; Thu, 16 Jul 2020 07:40:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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=ham 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 48wTcodNzryA for <ietf@ietfa.amsl.com>; Thu, 16 Jul 2020 07:40:49 -0700 (PDT)
Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (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 AF07A3A0974 for <ietf@ietf.org>; Thu, 16 Jul 2020 07:40:48 -0700 (PDT)
Received: by mail-lj1-x22e.google.com with SMTP id d17so7470149ljl.3 for <ietf@ietf.org>; Thu, 16 Jul 2020 07:40:48 -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=pGa7D+4Dqh95+m3tLgrt9vtIDscPcTdFzF/K2cVXkCA=; b=W9dJWhzhOh5K25K5Iu0ycEUTYc9WJEqPV3fUVb+ivuNpH/CA3P2bUptFS1WNCjQxEE GV+KExUHLve7JhsO+rSVW91a0GkHJQovW0NSqMUrii5u0rNZEDFoCmdVs8Vl25qqpNHt RBrcUPuQedI6v1oEZ4JWq4WEfaqXPzj9tdtIr1fkiObKXbeaczJbDENaoqLuxRxKcLk/ egGQNN0bjjsFAbSjGN3AkQQZ2wvFO4cAcDfV6dHIHSo24ISfU4zyF4Z1W7V40dhnZnuQ ju25Dv4axgnAaQ8gtOfLna7gvcuOK1/fvJOUNZiflF/gywEL1Z5b0LJE9zqOIeoiib5o FZtw==
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=pGa7D+4Dqh95+m3tLgrt9vtIDscPcTdFzF/K2cVXkCA=; b=mrSvwLJkkYxhIgPwqGzWmpgbBUkH7QdWHf2In8UDVrwxcCDvIzbcCDd7u5xuk5x/0Y HZPdgDzTr/NYVZMZ24FN+TbGbwk8X2VTfJ3AGBCVcEtHbbh57ZvrTFAsAi5O0+dYGFWO 2X4+cXCHzbIQpFru5PRr+KcPKVSuMpHAKAPPMLXpM/Z74xiXKDDfn/4X3c+FdImijtre 9MRhP1T7+1PqaHgHANxqyn24riGHinPXhDWicX3vvEp6pGZi8Q3xD1HizfboU6Txuizl 1BWd7HDfqn6lJthHjp0ESjX7WTybzrCqvC0MvBi3oUNYdtIIJYVFjpibq7BnyqioAQmG HexA==
X-Gm-Message-State: AOAM532hPDJgTQNRmCPxbO26q2wM2L6ofT8JXOqv2G6SsZKqwmbY1WUG Hjv7oF3tVJwg5RJRzTlFcToC1b3uShOYftTcvC7ADQ==
X-Google-Smtp-Source: ABdhPJyzVx2gf4asZ9wbowPiaUJSBhMGI8MmNvx2KMVqMtyzv2QZRNSs/8rxwddR2lQ4rShHmmQS2NwgszVTXarOEMc=
X-Received: by 2002:a2e:81d7:: with SMTP id s23mr2106357ljg.398.1594910446672; Thu, 16 Jul 2020 07:40:46 -0700 (PDT)
MIME-Version: 1.0
References: <159318840162.4951.12569119165623562334@ietfa.amsl.com> <6.2.5.6.2.20200627023025.0b145350@elandnews.com> <5C58F041-9991-49DA-98B6-6700499DFBC9@cooperw.in> <6.2.5.6.2.20200709132444.098ec410@elandnews.com> <CALaySJJbNHu=ktzeUX+k5Rj2bt2UQkx262mvD7wHLzEVXw3VxQ@mail.gmail.com> <6.2.5.6.2.20200710102806.0b084a90@elandnews.com> <CALaySJJwTLKgcEyWwmhPin3sX1C9kAMdj+ukMi2wfdAh399m7Q@mail.gmail.com> <6.2.5.6.2.20200710113940.0ac68208@elandnews.com> <6.2.5.6.2.20200712111856.0a815438@elandnews.com> <C30D52D7-376C-4599-93E8-48D16BDB262A@cooperw.in> <6.2.5.6.2.20200713124426.0b87c770@elandnews.com> <7F116050-D36E-4B78-80CD-48DEC24E32F1@cooperw.in> <6.2.5.6.2.20200714093250.0b840660@elandnews.com>
In-Reply-To: <6.2.5.6.2.20200714093250.0b840660@elandnews.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 16 Jul 2020 09:40:34 -0500
Message-ID: <CAKKJt-ctB3dKtNGi=4LdgV8D-yJHS8w5SaG-+YxCp=A7ZAQcsA@mail.gmail.com>
Subject: Re: WG Review: Stay Home Meet Only Online (shmoo)
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: Alissa Cooper <alissa@cooperw.in>, IETF list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009f5f7b05aa90065a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rEEvcsSI0z6zsF0lnEyU-JmKjWQ>
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: Thu, 16 Jul 2020 14:40:51 -0000

Hi, SM,

On Tue, Jul 14, 2020, 17:52 S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hi Alissa,
> At 06:22 AM 14-07-2020, Alissa Cooper wrote:
> >Suresh Krishnan, Russ Housley, and myself. See
> ><
> https://mailarchive.ietf.org/arch/msg/manycouches/Qls9UHKkG4kE9KKK4WQ-KBc0oLg/
> >.
> >
> > >
> > >  2. Who approved the draft charter?
> >
> >The IESG.
>
> I find it awkward to broach the following subject as you are an Area
> Director.  You may have noticed that I have zero support.
>

I'm only replying to these two sentences.

Area Directors are not nearly as exalted as this sounds. Like the rest of
Nomcom-reviewed position holders, Area Directors *serve the community*. If
we did an accurate org chart, the IESG (made up of ADs) would be toward the
BOTTOM of the "IETF hierarchy", and individual participants like you would
be at the top.

Fred Baker (1996-2001) said repeatedly, "I know I'm the IETF Chair, because
everyone sits on me". Five IETF Chairs later, that's still the way it
should be.

If we are doing the IETF correctly, the only thing that matters in a
discussion is the quality of a person's input. That's been clear to me
since the late 1990s, and if that is no longer true, the community needs to
have a broader conversation.

This is why ADs don't write all the documents :-)

I understand that this seems unnatural to many people - I am working for a
company from a culture where age and white hair are given deference, and I
have to remind younger colleagues that they are supposed to tell me when
I'm wrong, confused, or simply don't understand. Our success at that
company depends on hearing the best inputs from each person, and the IETF
is no different.

My current intern was delighted to discover that HE could give ME work
assignments. The IETF is like that.

As for "zero support", I wouldn't worry about that, at all. You're still
engaged in a conversation, and you can't know what other people are
thinking. You might eventually be "in the rough", or you might change our
minds for the better. But we're listening.

Please help us to "get it right", when you see something you need to ask
about.

Best,

Spencer

A person cannot be both judge and jury.  Within an IETF context, a
> person cannot be both the author and reviewer of a document; an Area
> Director cannot sponsor his/her own draft.  The reason is that it
> would create a conflict of interest.  In my opinion, writing the
> draft charter and approving it creates a potential conflict of interest.
>
> >There didn't seem to be any outstanding requests for changes to the
> >charter text that would prevent its approval.
>
> The definition of a charter is that it is a contract between a
> working group and the IETF to perform a set of tasks.  The milestones
> are part of the charter text.
>
> > >  4. Are the milestones listed at
> >
> https://mailarchive.ietf.org/arch/msg/manycouches/UB3zrC22s1B89PEwAOM-Y488TRs/
> > >     compliant with RFC 2418?
> >
> >Yes.
>
> I read RFC 2418 again.  It states that the basis for forming a
> working group is when the prospective Chair(s) and Area Director are
> satisfied with the charter form and content.  The RFC also states
> that milestones shall consist of deliverables that can be qualified
> as showing specific achievement.  A deliverable is a result.  In this
> case, it would be the result(s) produced by the working group, e.g.
> send draft to IESG by December 2020.  In my opinion, the milestones
> and the draft charter are not compliant with RFC 2418.
>
> It does not make sense to go ahead with the working group approval
> while the draft charter for that working group is under (formal)
> dispute.  It is as if the decision is/will be valid even though there
> is a dispute about that decision.
>
> Regards,
> S. Moonesamy
>
>