Re: IETF meat grinder

Richard Barnes <rlb@ipv.sx> Mon, 03 October 2022 14:15 UTC

Return-Path: <rlb@ipv.sx>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60292C14EB1E for <wgchairs@ietfa.amsl.com>; Mon, 3 Oct 2022 07:15:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20210112.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XibHEq8jWYsU for <wgchairs@ietfa.amsl.com>; Mon, 3 Oct 2022 07:15:43 -0700 (PDT)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58589C1524A4 for <wgchairs@ietf.org>; Mon, 3 Oct 2022 07:15:43 -0700 (PDT)
Received: by mail-lj1-x235.google.com with SMTP id u14so1980658ljk.4 for <wgchairs@ietf.org>; Mon, 03 Oct 2022 07:15:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=aipNPx6Pku7eeJ495LQ0AU3bXtJGzsPVFPVACbO684Q=; b=50GpbafxUItxYVWGNVMq565jLThkobZR8Gb8fsSZ1QPhf+xJeX0DFUnYREcI8KeJqw Tp8MXFgVQa/KMUl2eNMBaHcQiUk7dop9SH+5Ldg1/ZVhUzAI/GoOaDLYaYUjHCajnWe+ Eogbs17c2D0mM7UeP9/YW9tsFbitebZd+AWjL1vbIodfrTF0hm/iFs3iwzWtxIQlb4tB NafiH32TAj3QTskyI0O/fFMeN6XPoP8Jt5/HiVthDwrnnzD4Fok47YJdQCr7Ns1JUivP hh2IqQanS75Hbh3XUUDDhvThmlNfFp/AC7AxdK1ZfFnew8s0EFzOfvKjElGLmwTWNQFD Whvw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=aipNPx6Pku7eeJ495LQ0AU3bXtJGzsPVFPVACbO684Q=; b=rQOq71qPtgvCPZsCGk5PTGhkxJbk3KvWxHBPnrhBJ07nzhYvrdkwq9hQxFLcx1++p0 4Nscngs+MS0zRZAMaW7LmG2qr9QeVThGTROZCk0ImNytnw5iAGvHLZmXMg9DYmEGXuf3 JdSy+6ivlRTPevlrt1Y/2vMrkA6sZbkLcCOISoA9yCPyHEvhBKOcTe+bT22R18cTwjb3 6PYZP+Q0/tprWlzotD9wi6Xq2EpQJs4mK5dme+49Nue540Es5m3wUDSZDrDiOL9kp6XV anYfyTspnjOAHM6ttPSYiVbV9qaLv2efNfjsS1XMIs89xLqpNwXBu9zpNb6m0zegv3jN Bq6A==
X-Gm-Message-State: ACrzQf32N6tWaYlv4xgTdBXXjOhxx6T/NbXZ/LnYVmzU48F65r8PxSwt UvGPxhJv+YFNZWRP/a/IIhAFogvuUh2GbZARX8gcXBpGqTQBEA==
X-Google-Smtp-Source: AMsMyM5+un9NaeUWKrjhGBzGR8YKzPnourcZE59/f3dpAIY3E1iDG/Xflh8XStldiHHUlkDELLC0oh8MngVgyQ1bmaM=
X-Received: by 2002:a05:651c:a0e:b0:26b:e22c:5e71 with SMTP id k14-20020a05651c0a0e00b0026be22c5e71mr6188101ljq.15.1664806541143; Mon, 03 Oct 2022 07:15:41 -0700 (PDT)
MIME-Version: 1.0
References: <967194.1664711915@dooku> <24b49f319c79415bb792729b3b5b9dfe@akamai.com> <1185265.1664717360@dooku>
In-Reply-To: <1185265.1664717360@dooku>
From: Richard Barnes <rlb@ipv.sx>
Date: Mon, 3 Oct 2022 10:15:30 -0400
Message-ID: <CAL02cgRxM4=_3SmzFJY8NCKBJZAL+torgKTGequB_17=SxDA3g@mail.gmail.com>
Subject: Re: IETF meat grinder
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000081482b05ea21fa1d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/edn3oGkDZYEkq3ZckYQfPLNqdaQ>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Oct 2022 14:15:44 -0000

Similar feedback to Rich here...

In the MLS WG, which is similarly 95% not habitual IETF offenders, we have
proceeded mainly by doing work in the style the folks doing the work are
used to doing, and accommodating the IETF to the degree necessary.  So
largely working on GitHub, with Wire chat for easy coordination, and video
calls [1].  It has been amusing coaching people through all the IETF's
ridiculous idiosyncrasies, especially when it comes to the final approval
steps.

Your subject line, "IETF meat grinder" seems like the wrong approach -- we
as insiders should not be subjecting/inuring newcomers to the process, we
should be making it easy to participate while meeting the IETF's goals of
transparency / consensus / etc.


On Sun, Oct 2, 2022 at 9:29 AM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote:
>     > At its start, HTTPAPI had half its membership as IETF newcomers.
> The approach I took, and recommend, is that you have a block diagram
>     > wg -> iesg -> publication
>     > Inside WG is
>     > draft-> issues->fix->repeat
>     > Don't spend much time on the first slide.  Go into more detail as
> you get to those phases.
>
> Good advice, and basically what I was looking for.
>
> I like the flow with cycles in it idea.
> I think that there are some tools that create new diagrams like that.
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>