Re: [marf] Misuse of ARF by spam-friendly ISPs

"J.D. Falk" <jdfalk-lists@cybernothing.org> Wed, 03 August 2011 19:36 UTC

Return-Path: <jdfalk-lists@cybernothing.org>
X-Original-To: marf@ietfa.amsl.com
Delivered-To: marf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B682721F8B9F for <marf@ietfa.amsl.com>; Wed, 3 Aug 2011 12:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kJbw54oSqe3T for <marf@ietfa.amsl.com>; Wed, 3 Aug 2011 12:36:15 -0700 (PDT)
Received: from ocelope.disgruntled.net (ocelope.disgruntled.net [97.107.131.76]) by ietfa.amsl.com (Postfix) with ESMTP id 1914D21F8B9B for <marf@ietf.org>; Wed, 3 Aug 2011 12:36:07 -0700 (PDT)
Received: from [192.168.11.41] (c-76-126-154-212.hsd1.ca.comcast.net [76.126.154.212]) (authenticated bits=0) by ocelope.disgruntled.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p73JaHMb013413 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <marf@ietf.org>; Wed, 3 Aug 2011 12:36:19 -0700
X-DKIM: Sendmail DKIM Filter v2.6.0 ocelope.disgruntled.net p73JaHMb013413
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybernothing.org; s=fudge; t=1312400179; bh=yRfGAqgueCxSaqWhfQCobFTOuBSD5nRi1FsAS1vd/ rM=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date: Content-Transfer-Encoding:Message-Id:References:To; b=Alr/b5RGAhgR 8Ai6gT5sznkgYb0BZtJ1vO1j96Flj7XvlFkuwZ0nem/9KjKrT/rNi1NKWoDFL1NAEWk BBl0XFtl6YZjNmrL2LnhGwU4/1zQeix00fW8AJHiWIMSGlpQyslbP/BGAmfHhWchhEn 2FhWkSKpE7/6FomU7jVrYQKog=
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1084)
From: "J.D. Falk" <jdfalk-lists@cybernothing.org>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF520@EXCH-C2.corp.cloudmark.com>
Date: Wed, 03 Aug 2011 12:36:16 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B939F531-7586-4FDC-B20B-624ACA2B2B46@cybernothing.org>
References: <35734E6B-4579-4EF4-A139-7BFB4FA4573F@wordtothewise.com> <E41787825008234A9B8BB93D603C8B0F1707F7@bobo1.bobotek.net> <953887BF-E8AB-4246-8075-7EB50A7BF916@wordtothewise.com> <F5833273385BB34F99288B3648C4F06F13512DF4CD@EXCH-C2.corp.cloudmark.com> <A6F08584-07DB-4000-B5EB-0AD02AFD44E2@cybernothing.org> <4E391CA5.6010803@tana.it> <F5833273385BB34F99288B3648C4F06F13512DF520@EXCH-C2.corp.cloudmark.com>
To: Message Abuse Report Format working group <marf@ietf.org>
X-Mailer: Apple Mail (2.1084)
Subject: Re: [marf] Misuse of ARF by spam-friendly ISPs
X-BeenThere: marf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Message Abuse Report Format working group discussion list <marf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/marf>, <mailto:marf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/marf>
List-Post: <mailto:marf@ietf.org>
List-Help: <mailto:marf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/marf>, <mailto:marf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 19:36:16 -0000

On Aug 3, 2011, at 6:33 AM, Murray S. Kucherawy wrote:

>> What is the meaning of a list of non-addressed use cases?  Possibly
>> suggest that they are not worth being addressed in general?
> 
> It's referring to a list of use cases that the ARF was not designed to handle.  There's no intent that I can see to state that those use cases aren't interesting to handle.

Actually, what I meant was that draft-jdfalk-marf-as and draft-jdfalk-maawg-cfblbcp only fully address the complaint feedback loop use case.  There are other cases that ARF can handle, such as spam traps or (maybe) virus/malware reports, which I'd think we should discuss in a separate AS or BCP.

Either way, though, I think that bitching at a single ISP about their abuse@ policy is out of scope for any IETF document.  If that practice becomes common, maybe a "considered harmful" draft could be appropriate.  So far, though, there is one (1) example, which just happens to be a big ISP that some people love to hate.  It would be inappropriate, unprofessional, and somewhat silly to try to use the IETF as a weapon against them.

>> Hmm...
>> that's quite strange, especially considering that everyone likes the
>> monkey butter.
> 
> That's a new one on me.  What does it mean?

http://www.jwz.org/gruntle/monkeybutter.html

--
J.D. Falk
the leading purveyor of industry counter-rhetoric solutions