[Asrg] Re: BATV + SPF roadmap

Frank Ellermann <nobody@xyzzy.claranet.de> Wed, 06 September 2006 00:49 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GKlbp-0002X5-KO; Tue, 05 Sep 2006 20:49:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GKlbn-0002TA-Sb for asrg@ietf.org; Tue, 05 Sep 2006 20:49:39 -0400
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKlbh-0003Ay-8s for asrg@ietf.org; Tue, 05 Sep 2006 20:49:39 -0400
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GKlbZ-0005bI-Lc for asrg@ietf.org; Wed, 06 Sep 2006 02:49:25 +0200
Received: from pd9fba8f5.dip0.t-ipconnect.de ([217.251.168.245]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <asrg@ietf.org>; Wed, 06 Sep 2006 02:49:25 +0200
Received: from nobody by pd9fba8f5.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <asrg@ietf.org>; Wed, 06 Sep 2006 02:49:25 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: asrg@ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Wed, 06 Sep 2006 02:48:05 +0200
Organization: <URL:http://purl.net/xyzzy>
Lines: 28
Message-ID: <44FE1AC5.573D@xyzzy.claranet.de>
References: <Pine.LNX.4.62.0609050824140.11524@sokol.elan.net> <20060905163814.82599.qmail@simone.iecc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: pd9fba8f5.dip0.t-ipconnect.de
X-Mailer: Mozilla 3.0 (OS/2; U)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Subject: [Asrg] Re: BATV + SPF roadmap
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=subscribe>
Errors-To: asrg-bounces@ietf.org

John Levine wrote:
 
> BATV came first under some other name that I forget now

Maybe one of VERP, SRS, DMP, DRIP. FSV, ...  the name doesn't
matter, and who invented what is mainly a historic question -
unless somebody else claims to have "patented" it.  Unrelated:
http://www.ietf.org/ietf/IPR/rsa-ipr-draft-jennings-sip-hashcash-00.txt

> BATV is deliberately simple and works unilaterally, without
> recipient hosts needing to know anything about it.

Yes, that's not good enough.  Receiving hosts wishing to know
something about it should get what they need to reject forged
Return-Paths.

Ignorant hosts would still create backscatter, and BATV would
still catch most of it, that's no issue.  More interesting, if
receiving hosts can identify it, then spammers would also know
which Return-Paths they better don't forge, like they can know
which Return-Paths are SPF FAIL protected.

And the non-ignorant hosts would know which Return-Paths they
can accept "on probation", where later bounces won't get them
blacklisted as ignorants, like they know it today for SPF PASS.

Frank



_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg