Re: Status of this memo

Phillip Hallam-Baker <phill@hallambaker.com> Tue, 27 April 2021 16:30 UTC

Return-Path: <hallam@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 73C5A3A15D4 for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 09:30:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level:
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 HKrXIlw2OvrV for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 09:30:51 -0700 (PDT)
Received: from mail-yb1-f181.google.com (mail-yb1-f181.google.com [209.85.219.181]) (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 0A2153A15D2 for <ietf@ietf.org>; Tue, 27 Apr 2021 09:30:50 -0700 (PDT)
Received: by mail-yb1-f181.google.com with SMTP id j84so449217ybj.9 for <ietf@ietf.org>; Tue, 27 Apr 2021 09:30:50 -0700 (PDT)
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=plNrrIpZ5+oSlCQiRDixuIMbsNwyReIPShRnhgJsAlA=; b=HNkcrSRaqF1iUak7adQnvoTAtw5n8NzMxpnk8h8ItkIqFalJOWH991YcZENlquWRc4 qCWsQXELrSiaMfmZgS/oL9lYGWEgk/mEb1b0PrnCHhaHK78fHtev3djgD3Yt0FjSAnxX JuhOUWi8528UyWmNQXdAG5718CNUBRKzqoJMP4ga6oeN+XYN7oAz6oWrKpxX3irjs0pV lE7vTOWSU9FJ1fLR8nt+B/Mj5s2D9C+WYl2pKsPLRk0n2weGh8dBLIbmDX5nG10Yvjqz yn3GCKFUG2hl4sdKzTMJa3bne4aozdZ4AvbGvykMXUfL4Ys6Vn28A+ZB6V+9I/2DsOZP h7WQ==
X-Gm-Message-State: AOAM531Ll4rKLFuu/h/2/NwLRQcYqpgjMuKih96GOKy7/DoFQOaUJ9Ju QvLjaW75Kvu2XfjiKYx6q0KWsQcR3dW5TIU/wqE=
X-Google-Smtp-Source: ABdhPJwZk0RlHtM0CJnUHZldh4DpiTK5yWK4eQwvDxQ+zqpyHjWJoKm04YFQtxC2cVnGFTz2ICk0xYR9t+GNtFn5G/c=
X-Received: by 2002:a25:4b83:: with SMTP id y125mr32467984yba.172.1619541049981; Tue, 27 Apr 2021 09:30:49 -0700 (PDT)
MIME-Version: 1.0
References: <376f83f0-89a3-cd0e-1792-c8434bd8a5d2@gmail.com> <9ACE59FA-30B6-475A-AF6B-4B874E4A2788@eggert.org> <1804294246.5904.1619512137931@appsuite-gw2.open-xchange.com> <D653D3B2-7666-409A-B856-2A4B1BA958CA@eggert.org> <3DBB64B1-40B8-4BC3-B66C-7F9B7F395874@akamai.com> <b5210c71-9500-3dba-05d2-4ae1c6ad16e9@network-heretics.com> <CAA=duU1VJs2vCE=uCF=fXO7FNedn9yPAaZWTgcaAiHTexA8uWA@mail.gmail.com> <2c48c55c-fd37-6ced-e025-707eb145a27b@nokia.com> <2D1F890C-1BC3-4E19-85C3-EEA522577275@tzi.org>
In-Reply-To: <2D1F890C-1BC3-4E19-85C3-EEA522577275@tzi.org>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Tue, 27 Apr 2021 12:30:40 -0400
Message-ID: <CAMm+LwhOFVoi=22SU=O4fq4pRFaxvYqBvuw5c4N-Gu4J_=ZacQ@mail.gmail.com>
Subject: Re: Status of this memo
To: Carsten Bormann <cabo@tzi.org>
Cc: Martin Vigoureux <martin.vigoureux@nokia.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fbbfa905c0f6c8d2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6CPpMcCdLQqEH-yZyXTrYyYKNLo>
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: Tue, 27 Apr 2021 16:30:55 -0000

On Tue, Apr 27, 2021 at 12:18 PM Carsten Bormann <cabo@tzi.org> wrote:

>
> I think Keith is recollecting some experience with WGs where the chairs
> used the WG document process to run the show without much regard to the
> WG’s opinions.  In that case, I’d say: get new chairs!  We don’t need to
> make the process capable of coping with this abuse.
>
> Grüße, Carsten
>

That is not always possible. While I am not aware of any AD being a WG
chair at present and there are cases where it makes sense for General area
WGs to be chaired by IETF chair, there have been occasions where an AD of
one area was WG chair in another which made it impossible for that other
area to remove him in a case where he was clearly abusing his position.

I would like to see explicit policy prohibiting this practice. It is futile
to expect IESG members to risk taking on another IESG member on account of
malpractice as a WG chair.


As for the documents, I really can't see how a WG can come to consensus on
a document before they see the document. There are some cases where edits
can be agreed upon and a nice paper trail created. But those changes aren't
the ones that take the time when editing. Change mechanism A to mechanism B
is an easy change. The ones that take time are 'section 3 is unclear'
because you often end up having to make changes in every other section to
fix it.