Re: New proposal/New SOW comment period

Michael Richardson <mcr@sandelman.ca> Fri, 13 September 2019 15:03 UTC

Return-Path: <mcr@sandelman.ca>
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 B856312081A for <ietf@ietfa.amsl.com>; Fri, 13 Sep 2019 08:03:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 So_RykZ_UKum for <ietf@ietfa.amsl.com>; Fri, 13 Sep 2019 08:03:40 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 813151200DF for <ietf@ietf.org>; Fri, 13 Sep 2019 08:03:40 -0700 (PDT)
Received: from [10.207.226.131] (unknown [80.233.34.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by tuna.sandelman.ca (Postfix) with ESMTPSA id 5520A3897C for <ietf@ietf.org>; Fri, 13 Sep 2019 11:02:04 -0400 (EDT)
Date: Fri, 13 Sep 2019 17:03:35 +0200
User-Agent: K-9 Mail for Android
In-Reply-To: <394203C8F4EF044AA616736F@PSB>
References: <394203C8F4EF044AA616736F@PSB>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: New proposal/New SOW comment period
To: ietf@ietf.org
From: Michael Richardson <mcr@sandelman.ca>
Message-ID: <CAB5C7F9-36DA-46FD-843E-1A24C1282128@sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Yd9VmGJJvkG2RlCZgIyIdrTunlM>
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: Fri, 13 Sep 2019 15:03:43 -0000



On September 13, 2019 4:44:46 PM GMT+02:00, John C Klensin <john-ietf@jck.com> wrote:
>
>At least one short-term consequence is that members of the
>community who should be participating in the discussion wonder
>if it is all a charade, note the volume of traffic and such
>things as the dispute about the list on which the discussions
>are held, and tune out.  And others wonder whether that was by
>design (whether effective or not).


Wow. John have you been reading my mind? (again? Because the psycorp has rules about that).  I certainly have been deleting entire threads at a time, and I guess others have too. I am reading your email by fluke on my phone, while waiting on the tarmac at Schipol for a computer swap on this plane.

>   So I suggest
>that you ask (and, if necessary, plead and beg) Heather to
>extend her commitment to the IETF and the RFC Editor function
>for an extra six months (or whatever other period she and you


Wow very good idea, and good backup plan too.


>other side.   Being told that the procedures prevent us from
>using a creative and credible approach would, in the current
>climate, certainly cause many members of the community that all
>of this is about maintaining or expanding leadership body (or
>personal) control, power, and/or authority.

>[1] Well, I can, but I'm not aware of a reliable process for
>consulting Jon Postel, Joyce Reynolds, or Bob Braden.

Telnet 1.2.3.4


-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.