Re: Recent threads concerning sergeants-at-arms

Michael StJohns <mstjohns@comcast.net> Tue, 03 September 2019 03:06 UTC

Return-Path: <mstjohns@comcast.net>
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 42C7512001E for <ietf@ietfa.amsl.com>; Mon, 2 Sep 2019 20:06:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.697
X-Spam-Level:
X-Spam-Status: No, score=-2.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=comcast.net
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 tXeF62A9uMJJ for <ietf@ietfa.amsl.com>; Mon, 2 Sep 2019 20:06:42 -0700 (PDT)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 870731200B1 for <ietf@ietf.org>; Mon, 2 Sep 2019 20:06:42 -0700 (PDT)
Received: from resomta-ch2-20v.sys.comcast.net ([69.252.207.116]) by resqmta-ch2-08v.sys.comcast.net with ESMTP id 4z6TipA1o28I74z9Vih5uG; Tue, 03 Sep 2019 03:06:41 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1567480001; bh=VGJxaPjoL73QYyMTMKGpQxGadQtUKgHbAfrUYZte7rM=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=PwgR9ZMYaNJx/WOFpYEtgQ357WkY/aDcYyiHP68IBH9MfWoqyHcE0BS834762E+P1 7wcOLxmhdvrACtUfY1TPXSoCiK1G0G6pm9OxeVJ9p27wjEwzZgSr4XaOslKAdayVZS UXDHu9hpR/nLkHmiTvxJmtFlBXrVmg0UagG4esGaozHGIRZt0gC14CIJGy0dgu87wS Nr66dXwHHiESdhqUtFrH+CvnCK+ZZv7i1IXB/BxjHLwARzzr0618I1McMPONnMlJTg owmKUDz20psnLkAYwJeFxdlvW08opgXiUiuyuCkMc9jJqtzRbtl6WY+lZDgAEL7L2J oQ66Npbbxp94A==
Received: from [IPv6:2601:152:4400:437c:208d:2fda:9bb0:ed54] ([IPv6:2601:152:4400:437c:208d:2fda:9bb0:ed54]) by resomta-ch2-20v.sys.comcast.net with ESMTPSA id 4z9UiT8yrs8qC4z9Vibzd0; Tue, 03 Sep 2019 03:06:41 +0000
X-Xfinity-VMeta: sc=0;st=legit
Subject: Re: Recent threads concerning sergeants-at-arms
To: ietf@ietf.org
References: <2D3C4495-F61A-4616-82B7-4A7AF36EC282@cooperw.in>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <b042dfef-1bfe-8967-e723-a7cf532ef0c8@comcast.net>
Date: Mon, 02 Sep 2019 23:06:39 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <2D3C4495-F61A-4616-82B7-4A7AF36EC282@cooperw.in>
Content-Type: multipart/alternative; boundary="------------A9565774433197C85E8ED56A"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hffcq1PLyN7PNrFuzNo4SybXxHM>
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, 03 Sep 2019 03:06:45 -0000

On 9/2/2019 9:51 PM, Alissa Cooper wrote:

Hi Alissa - I appreciate you have a particular point of view about what 
you think is appropriate discussion on the IETF mailing list, but I 
think you're missing the point that what's important is the topic and 
its important to more than RFC format geeks  ( :-) )that hang out on the 
rfc-interest mailing list.  I also think you're mis-reading 3005. I 
don't think we're quite ready to discuss the technical aspects of the 
RFC series - and that's the appropriate set of discussions for 
rfc-interest, not the philosophy of the oversight of the RFC series and 
process.

>
> Matthew made a suggestion to use a mailing list controlled by the RFC 
> Series Editor for discussion about an RFC Series-related SOW, based on 
> the charter of this list described in RFC 3005. 

As SAA, it's rare that such a posting would be considered just a 
suggestion.    I myself didn't actually take it as just a suggestion.  
Eliot beat me in providing pushback.

> It would be great if people decide to follow his suggestion, as some 
> have already. If not, I am confident that the RSOC and the IAB will 
> take into account what they read here between now and September 14 
> when the SOW comment period closes and I am optimistic that the 
> discussion on rfc-interest, on this list, and everywhere in the IETF 
> can remain respectful. My hope is that people will use the next 12 
> days to contemplate the email Sarah sent and provide their feedback.

Neither Matthew nor you appear to be reading the same things out of 3005 
as the rest of us - I'd be interested in how you interpret this topic in 
a manner to suggest that its an inappropriate topic for the IETF list.

> RFC3005: In addition to the topics noted above, appropriate postings include:
>
>      - Last Call discussions of proposed protocol actions
>      - Discussion of technical issues that are candidates for IETF work,
>        but do not yet have an appropriate e-mail venue
>      - Discussion of IETF administrative policies
>      - Questions and clarifications concerning IETF meetings
>      - Announcements of conferences, events, or activities that are
>        sponsored or endorsed by the Internet Society or IETF.
>
>     Inappropriate postings include:
>
>      - Unsolicited bulk e-mail
>      - Discussion of subjects unrelated to IETF policy, meetings,
>        activities, or technical concerns
>      - Unprofessional commentary, regardless of the general subject
>      - Announcements of conferences, events, or activities that are not
>        sponsored or endorsed by the Internet Society or IETF.

Later, Mike




>
> Cheers,
> Alissa Cooper
> IETF Chair
>
> [1] https://mailarchive.ietf.org/arch/msg/ietf/Q3f9FnFcrWKRySD-DqQCgI6lbCw
> [2] https://mailarchive.ietf.org/arch/msg/ietf/-3M3WswGZ_0zvYvDMO4f_J58qtQ
> [3] https://mailarchive.ietf.org/arch/msg/ietf/M2d85XpOOR4tm78yGyh205iJWJc
> [4] See slides 14 to 18 of 
> https://datatracker.ietf.org/meeting/105/materials/slides-105-ietf-sessa-all-slides-ietf-105-administrativeoperations-plenary