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

Tommy Pauly <tpauly@apple.com> Mon, 20 April 2020 21:05 UTC

Return-Path: <tpauly@apple.com>
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 1C3513A0FDE for <architecture-discuss@ietfa.amsl.com>; Mon, 20 Apr 2020 14:05:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level:
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=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=apple.com
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 HlERbE53WjfY for <architecture-discuss@ietfa.amsl.com>; Mon, 20 Apr 2020 14:04:59 -0700 (PDT)
Received: from nwk-aaemail-lapp01.apple.com (nwk-aaemail-lapp01.apple.com [17.151.62.66]) (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 67E173A0FDC for <architecture-discuss@ietf.org>; Mon, 20 Apr 2020 14:04:59 -0700 (PDT)
Received: from pps.filterd (nwk-aaemail-lapp01.apple.com [127.0.0.1]) by nwk-aaemail-lapp01.apple.com (8.16.0.42/8.16.0.42) with SMTP id 03KL2ZSa013731; Mon, 20 Apr 2020 14:04:44 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=EnvfA/gT8Sy1Ml6Q6Q4XN+hqdbw1C2gKNPgVHre+pY4=; b=bFFvLf5HCVq05gROwZWLJP+lfnoKpjFRSJEkElLlfY3KvKLyYoaWeLPcfZ7lxyRuy3nc 0PNQLhRf+M10iEOTMgVFl6vsiwmMjuUbuLFPT9Nouek7JSPKWADlqbyJ0jbYIjVmzXtv m8XE/igDAhEAFJLzU+J5WA6ZZScpA6eHcv4TJTg7d9ChwZloDBUcHDkr3pRor5coyblq ucAq9wtwtYf3Q94snVwStIQJ1o7TSpHKes/mCEPZGzY8tSPQe25+uFz8D8Nvn5Rmcf1C wr3qppe09ztr1EcOELqdpYEvVxIM6CWOjBjBkWQ9ngz6KQNGS/XJjgVvuzORr5M+4Sd0 rg==
Received: from rn-mailsvcp-mta-lapp02.rno.apple.com (rn-mailsvcp-mta-lapp02.rno.apple.com [10.225.203.150]) by nwk-aaemail-lapp01.apple.com with ESMTP id 30hj7214h8-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 20 Apr 2020 14:04:44 -0700
Received: from rn-mailsvcp-mmp-lapp02.rno.apple.com (rn-mailsvcp-mmp-lapp02.rno.apple.com [17.179.253.15]) by rn-mailsvcp-mta-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.5.20200312 64bit (built Mar 12 2020)) with ESMTPS id <0Q9300MM0UJVTWA0@rn-mailsvcp-mta-lapp02.rno.apple.com>; Mon, 20 Apr 2020 14:04:43 -0700 (PDT)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp02.rno.apple.com by rn-mailsvcp-mmp-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.5.20200312 64bit (built Mar 12 2020)) id <0Q9300N00UB73200@rn-mailsvcp-mmp-lapp02.rno.apple.com>; Mon, 20 Apr 2020 14:04:43 -0700 (PDT)
X-Va-A:
X-Va-T-CD: 9ef1c94aca2a985c968936d4baa34f4e
X-Va-E-CD: 9cf9b30cf458d3b18920c7b9603d62bd
X-Va-R-CD: 940e86883ca42bcfe4e4c9b965eae3b0
X-Va-CD: 0
X-Va-ID: 3b7e4876-c747-483d-98f3-e0811d3434d1
X-V-A:
X-V-T-CD: 9ef1c94aca2a985c968936d4baa34f4e
X-V-E-CD: 9cf9b30cf458d3b18920c7b9603d62bd
X-V-R-CD: 940e86883ca42bcfe4e4c9b965eae3b0
X-V-CD: 0
X-V-ID: 08e6e9a7-0a3a-4082-985d-e69f6ee36dc2
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.676 definitions=2020-04-20_08:2020-04-20, 2020-04-20 signatures=0
Received: from [17.234.48.87] (unknown [17.234.48.87]) by rn-mailsvcp-mmp-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.5.20200312 64bit (built Mar 12 2020)) with ESMTPSA id <0Q9300HCGUJTM100@rn-mailsvcp-mmp-lapp02.rno.apple.com>; Mon, 20 Apr 2020 14:04:43 -0700 (PDT)
From: Tommy Pauly <tpauly@apple.com>
Message-id: <91AA234A-7375-4A04-872B-5B1AB3FA79FF@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_6DEFFDD1-0794-4C04-B8DE-E0CFA28BF6D8"
MIME-version: 1.0 (Mac OS X Mail 13.4 \(3608.80.7.2.3\))
Date: Mon, 20 Apr 2020 14:04:41 -0700
In-reply-to: <6.2.5.6.2.20200420124357.12e4b868@elandnews.com>
Cc: architecture-discuss@ietf.org
To: S Moonesamy <sm+ietf@elandsys.com>
References: <303F494F-F06C-4E6A-99E5-089798EB56DB@apple.com> <6.2.5.6.2.20200420124357.12e4b868@elandnews.com>
X-Mailer: Apple Mail (2.3608.80.7.2.3)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.676 definitions=2020-04-20_08:2020-04-20, 2020-04-20 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/_qrYiT5BHZtpyoy-_1Yel9JleZ4>
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: Mon, 20 Apr 2020 21:05:04 -0000

Hi S. Moonesamy,

Thanks for your response!

> On Apr 20, 2020, at 1:54 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:
> 
> Dear Mr Pauly,
> At 09:08 AM 20-04-2020, Tommy Pauly wrote:
>> 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.
>> 
>> 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!
> 
> I would like to thank the Internet Architecture Board for requesting feedback about the architecture-discuss@ietf.org mailing list.  Given the domain name in that email address, isn't it a mailing list which falls under the Internet Engineering Task Force?

This mailing list is, in fact, an IAB-sponsored activity. The email address is confusing for historical reasons. architecture-discuss@iab.org <mailto:architecture-discuss@iab.org> is an alias for the same list.

> 
> There was an announcement about the moderators some time ago.  I don't recall seeing them  described as "sergeant-at-arms".  I looked up the term and I found this: "in feudal England a sergeant at arms was an armed officer of a lord and was often one of a special body required to be in immediate attendance on the king's person, to arrest traitors and other offenders".  Given some recent interventions on the ietf@ mailing list, I would not suggest the sergeant at arms as a model to follow.

The SAA role for the mailing list already existed, and the goal of this text is to clarify what the role is on the public website. It is primarily a way to moderate spam and ensure that a mailing list is a respectful and productive space. If there are particular suggestions for the content and scope of the role in terms of the textual description, I’d be happy to hear them.

Thanks,
Tommy
> 
> Regards,
> S. Moonesamy