Re: IETF meat grinder

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 02 October 2022 13:29 UTC

Return-Path: <mcr@sandelman.ca>
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 58BD1C1524B7 for <wgchairs@ietfa.amsl.com>; Sun, 2 Oct 2022 06:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 bqkVTnWWyIWL for <wgchairs@ietfa.amsl.com>; Sun, 2 Oct 2022 06:29:22 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52236C1522BB for <wgchairs@ietf.org>; Sun, 2 Oct 2022 06:29:22 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [185.143.153.46]) by relay.sandelman.ca (Postfix) with ESMTPS id 04EF81F459; Sun, 2 Oct 2022 13:29:21 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 9922B1A0758; Sun, 2 Oct 2022 15:29:20 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: Re: IETF meat grinder
In-reply-to: <24b49f319c79415bb792729b3b5b9dfe@akamai.com>
References: <967194.1664711915@dooku> <24b49f319c79415bb792729b3b5b9dfe@akamai.com>
Comments: In-reply-to "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org> message dated "Sun, 02 Oct 2022 13:16:18 -0000."
X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 27.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Sun, 02 Oct 2022 15:29:20 +0200
Message-ID: <1185265.1664717360@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/xB5zlsCIwiuE1eg1cNZP-EL3JaM>
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: Sun, 02 Oct 2022 13:29:24 -0000

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