Re: [arch-d] Updates on IAB mailing lists

Christopher Wood <caw@heapingbits.net> Tue, 21 April 2020 21:24 UTC

Return-Path: <caw@heapingbits.net>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D0CE3A0A96 for <architecture-discuss@ietfa.amsl.com>; Tue, 21 Apr 2020 14:24:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=heapingbits.net header.b=WB0RBSUT; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=KxzwY4Ec
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 E0Q1Gq7fYkrR for <architecture-discuss@ietfa.amsl.com>; Tue, 21 Apr 2020 14:24:05 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B98043A0A93 for <architecture-discuss@ietf.org>; Tue, 21 Apr 2020 14:24:05 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id EB9B95C0129 for <architecture-discuss@ietf.org>; Tue, 21 Apr 2020 17:24:04 -0400 (EDT)
Received: from imap7 ([10.202.2.57]) by compute1.internal (MEProxy); Tue, 21 Apr 2020 17:24:04 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heapingbits.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type:content-transfer-encoding; s=fm1; bh=dqzik B6ZTo747GcmKaSOnGv2bYXIoSS0DUcJ5Ik4KPM=; b=WB0RBSUTNlfR49UjH8uGl rN4YEUlah9RVP+DIzpsG1RH9u43SHtNzCcYw1YF47JJn+zLAB3fefswVa1SlUQiq BwaImZOyZgkbFlvntP5QeJDfytV32G8bS8fo+1GX+Hd14vPUdoOF0037AtP1exZa UW3azs+FW0O2FrycE69gHh17FvbWmAzfpXLVhQ/EAYNL6nzhWkMYu36/5eLwpYnY 26s9Rlbzo8unajj6Bd/1aTum/rWN+7daFOselLSrWLodhj6d9qbVt1mi7dFRfyIb Aewmpdw+q30nHqB6aJmNpZnQBdqHbj4zaWKdKcdFtn9Vp5t4CcEMiG/+n7lRNdnL A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=dqzikB6ZTo747GcmKaSOnGv2bYXIoSS0DUcJ5Ik4K PM=; b=KxzwY4EcnW1idWn6Ru5KgSCUy1OkhHVDgo8uqb+R3hLG8HfFHG0a9IMJu RcQ4N7UXkeUCtaboiWoXrKM2W+TuHLENcankZJwESsTXnrib7O0s5TgLxUfqayFh Yv5IfetF8/AKubrcc78G33TKkHPCvG9Jk93NhTls/wbykvntUSOFgUrLIjOvbYGu Pkin2PNkJQlJ4EGV3WuRIEnAJ8D1ENTXPHG6YDMrAEeWdaFiQ5ZHuTfP4KLThG9k iVFi4KsynG7819X2Fm43H4zO7qzSYRwciUohuMzxZ2dkEGzewvX1gfxTmMVdNASe D0pfu4d8R8RW6V4jsWa7gTs4T4M1w==
X-ME-Sender: <xms:dGSfXk5UtpuNJRg-LZwPEdJpgqckpCkT7O6-qiVk2V5pfuImRDOynA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrgeehgdduiedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtgfesth hqredtreerjeenucfhrhhomhepfdevhhhrihhsthhophhhvghrucghohhougdfuceotggr fieshhgvrghpihhnghgsihhtshdrnhgvtheqnecuffhomhgrihhnpehirggsrdhorhhgne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheptggrfies hhgvrghpihhnghgsihhtshdrnhgvth
X-ME-Proxy: <xmx:dGSfXnaVKTuhT4xmiLKuoGMIcs_-emuDSN4-qWhfv-KFEoi_vIayhg> <xmx:dGSfXhGAasxd2JTaD0f2TB5UceT9KsTyOomKcsBSv9YjarFG7l45tA> <xmx:dGSfXgmA05I_XGsvHzqXHnMo2FVxAB855X_uaC5GgQpPHKog_AHPwQ> <xmx:dGSfXiqCoLM3yGqpWoh6PbCkxHjEe2SE5_itGNq4vK7rM40RyEiW7Q>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 5870A180091; Tue, 21 Apr 2020 17:24:04 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-351-g9981f4f-fmstable-20200421v1
Mime-Version: 1.0
Message-Id: <fc6fd055-6a9f-4108-a7c8-05ac6b1d4f9a@www.fastmail.com>
In-Reply-To: <303F494F-F06C-4E6A-99E5-089798EB56DB@apple.com>
References: <303F494F-F06C-4E6A-99E5-089798EB56DB@apple.com>
Date: Tue, 21 Apr 2020 14:23:32 -0700
From: "Christopher Wood" <caw@heapingbits.net>
To: architecture-discuss@ietf.org
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/c2Mem0y2kRPiy6MMmHUUcMuku0U>
Subject: Re: [arch-d] Updates on IAB mailing lists
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2020 21:24:08 -0000

On Mon, Apr 20, 2020, at 9:08 AM, Tommy Pauly wrote:
> Hello architecture-discuss,
> 
> We’d like to share a few updates about IAB mailing lists, and solicit 
> the community’s feedback on some new text.
> 
> First, Tommy Pauly will be joining Stephen Farrell on the (existing, 
> but rarely employed) sergeants-at-arms team to help moderate the list.

Thank you both for your service!

> Second, we’d like to clarify the sergeants-at-arms roles for the lists. 
> The current description on https://www.iab.org/iab-mailing-lists/ does 
> mention that the lists use a sergeant-at-arms model for moderation, but 
> does not describe what this role entails. It also does not specify if 
> this role applies to all of the lists on the page, such as program 
> lists.
> 
> We’re proposing adding the following text to 
> https://www.iab.org/iab-mailing-lists/, largely based on the IETF list 
> SAA. We’d love to hear feedback on this approach!
> 
> ====
> 
> IAB mailing lists have sergeants-at-arms, whose role is ensure there 

nit: "whose role is ensure"

> are no inappropriate postings. Inappropriate postings consist of: spam 
> and bulk e-mail; announcements of conferences or activities that are 
> not sponsored or endorsed by the Internet Society, the IETF, or the 
> IAB; unprofessional commentary, regardless of subject; and discussion 
> of subjects unrelated to IAB policy, programs, activities, or technical 
> concerns.
> 
> The sergeants-at-arms are empowered to restrict posting by a person or 
> of a thread when the content is inappropriate and represents a pattern 
> of abuse. Complaints regarding a decision should be referred to the IAB 
> chair.
> 
> The current sergeants-at-arms for “architecture-discuss@ietf.org 
> <mailto:architecture-discuss@iab.org>” are Stephen Farrell and Tommy 
> Pauly. For program-specific lists, the program chairs act as 
> moderators. The "rfc-interest@rfc-editor.org” list is moderated by the 
> Temporary RFC Series Project Manager.
> 
> ====

This seems like a fine addition to me.

> Third, we have many lists that are enumerated on the website that are 
> for closed programs or past workshops. We checked the activity on these 
> lists, and we believe that we can close the following lists. Any 
> further discussion on these topics is welcome on architecture-discuss.
> 
> - caris-attendees@iab.org
> - emserv-discuss@iab.org
> - i18n-discuss@iab.org
> - inip-discuss@iab.org
> - internetgovtech@iab.org
> - iotsi@iab.org
> - iotsu@iab.org
> - marnew@iab.org
> - privsec-discuss@iab.org
> - stackevo-discuss@iab.org
> 
> The remaining lists will be:
> 
> - architecture-discuss@ietf.org
> - chirp@iab.org
> - model-t@iab.org
> - rfced-future@iab.org

And this seems like a sensible way to consolidate ongoing discussions. 

Thanks for clearing and cleaning things up!

Best,
Chris