Re: IESG Statement on Spam Control on IETF Mailing Lists

"TS Glassey" <tglassey@earthlink.net> Tue, 15 April 2008 14:38 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 31DA628C420; Tue, 15 Apr 2008 07:38:37 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E328528C425 for <ietf@core3.amsl.com>; Tue, 15 Apr 2008 07:38:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.402
X-Spam-Level:
X-Spam-Status: No, score=-3.402 tagged_above=-999 required=5 tests=[AWL=-1.404, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G1YC2BAvxuRN for <ietf@core3.amsl.com>; Tue, 15 Apr 2008 07:38:35 -0700 (PDT)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by core3.amsl.com (Postfix) with ESMTP id 04AC828C41E for <ietf@ietf.org>; Tue, 15 Apr 2008 07:38:34 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=MAyCuH0LuXoZ8xTqzolaQqwDq5kOYW/LM3rGpYDEjJAcomOHxC+feMHizO4b4Q/I; h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [24.23.176.93] (helo=tsg1) by elasmtp-curtail.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1JlmJP-0005La-7n; Tue, 15 Apr 2008 10:39:07 -0400
Message-ID: <001001c89f06$a4e04340$6501a8c0@tsg1>
From: TS Glassey <tglassey@earthlink.net>
To: "Tom.Petch" <sisyphus@dial.pipex.com>, Eliot Lear <lear@cisco.com>
References: <20080414153938.0A5153A6D4D@core3.amsl.com> <2788466ED3E31C418E9ACC5C316615572EF8A7@mou1wnexmb09.vcorp.ad.vrsn.com><20080414172440.7E8943A6D83@core3.amsl.com><48039EC3.6010108@cisco.com> <04b701c89efa$19f29500$0601a8c0@allison>
Subject: Re: IESG Statement on Spam Control on IETF Mailing Lists
Date: Tue, 15 Apr 2008 07:38:17 -0700
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec795948a00cfd55a51c062990cf938cd687350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 24.23.176.93
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

----- Original Message ----- 
From: "Tom.Petch" <sisyphus@dial.pipex.com>
To: "Eliot Lear" <lear@cisco.com>
Cc: "IETF Discussion" <ietf@ietf.org>
Sent: Tuesday, April 15, 2008 6:09 AM
Subject: Re: IESG Statement on Spam Control on IETF Mailing Lists


> ----- Original Message -----
> From: "Eliot Lear" <lear@cisco.com>
> To: "Russ Housley" <housley@vigilsec.com>
> Cc: "IETF Discussion" <ietf@ietf.org>
> Sent: Monday, April 14, 2008 8:13 PM
> Subject: Re: IESG Statement on Spam Control on IETF Mailing Lists
>
>>
>> Russ,
>>
>> > When IETF lists are housed somewhere other than ietf.org, they are
>> > supposed to include an archive recipient so that there is an archive
>> > available at ietf.org (perhaps in addition to the one kept at the
>> > place where the list is housed).
>> >
>>
>> I'll agree with Phill's conclusion on this one.
>>
>> I think there is probably convenience value to housing the mailing lists
>> at the IETF.  It allows for a single whitelist, reduction in those
>> annoying monthly messages that we eventually all filter into the
>> bitbucket.
>
> Err, no!  I have been silently discarded from IETF lists on a number of
> occasions - v6ops is the worst offender - and that monthly message is an
> invaluable check as to whether I have been discarded again or whether the 
> list
> has been dormant.

That is addressable though tom. The real issue is the legal controls which 
the IETF is obligated by its creation under the ISOC Charter to put in 
place.  These include managing the electronic archive and legal culpability 
for changes (authorized or not) to that content as well as dealing with 
instances where individuals were 'quietly edited out' of various WG's


>
> Tom Petch
>
>> Also, it  probably is easier to effect and audit policy
>> (such as we have any) in terms of message retention, uniform access, etc.
>>
>> Regards,
>>
>> Eliot
>>
>>
>> _______________________________________________
>> IETF mailing list
>> IETF@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>
> _______________________________________________
> IETF mailing list
> IETF@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf 

_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf