RE: [Asrg] Consent Proposal

Yakov Shafranovich <research@solidmatrix.com> Sun, 29 June 2003 05:13 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10301 for <asrg-archive@odin.ietf.org>; Sun, 29 Jun 2003 01:13:39 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5T5DAk18636 for asrg-archive@odin.ietf.org; Sun, 29 Jun 2003 01:13:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WUUw-0004qT-7Q for asrg-web-archive@optimus.ietf.org; Sun, 29 Jun 2003 01:13:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10291; Sun, 29 Jun 2003 01:13:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WUUt-0007EE-00; Sun, 29 Jun 2003 01:13:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19WUUn-0007EB-00; Sun, 29 Jun 2003 01:13:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WUUm-0004ni-Un; Sun, 29 Jun 2003 01:13:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WUUU-0004n7-Tc for asrg@optimus.ietf.org; Sun, 29 Jun 2003 01:12:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10287 for <asrg@ietf.org>; Sun, 29 Jun 2003 01:12:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WUUS-0007Dz-00 for asrg@ietf.org; Sun, 29 Jun 2003 01:12:40 -0400
Received: from 000-254-303.area7.spcsdns.net ([68.27.233.50] helo=68.27.233.50) by ietf-mx with smtp (Exim 4.12) id 19WUUG-0007Dw-00 for asrg@ietf.org; Sun, 29 Jun 2003 01:12:29 -0400
Message-Id: <5.2.0.9.2.20030629010744.00ba8600@std5.imagineis.com>
X-Sender: research@solidmatrix.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
To: Barry Shein <bzs@world.std.com>, Peter Kay <peter@titankey.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Subject: RE: [Asrg] Consent Proposal
Cc: asrg@ietf.org
In-Reply-To: <16124.52439.895213.913633@world.std.com>
References: <DD198B5D07F04347B7266A3F35C42B0B0FD07E@io.cybercom.local> <DD198B5D07F04347B7266A3F35C42B0B0FD07E@io.cybercom.local>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-MimeHeaders-Plugin-Info: v2.03.00
X-GCMulti: 1
Sender: asrg-admin@ietf.org
Errors-To: asrg-admin@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
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>
List-Archive: <https://www1.ietf.org/pipermail/asrg/>
Date: Sun, 29 Jun 2003 01:12:06 -0400

At 07:01 PM 6/27/2003 -0400, Barry Shein wrote:


>How is any of this consent/filtering related to the usual IETF purpose
>such as protocol documents (RFCs, etc), network engineering, and not
>just some ad hoc User Interface Engineering?
>
>It seems to me the consent proposals (getting any attention) thus far
>require no change to any existing protocols or standards, and don't
>seem to imply any new protocols or standards.
>
>Where in the stack would any of this fit and why does this group need
>to be involved?

As I mentioned before there are two models here - network abuse model which 
you are proposing and consent model which is defined in the charter. The 
network abuse model as you propose would seek to find ways to detect and 
stop spammers from using the Internet for abusive behavior (i.e. spam) It 
may also include viruses, worms, etc. as a side benefit.

Both models in my opinion are equally good. However, they call for 
different solutions and approaches. Both models will involve changing 
existing protocols (i.e. SMTP) and defining new ones (like CRI). That is 
where IETF gets involved.

The consent model specifically is not limited to the MUAs, but can be 
enforced by MTAs on ISP level as well. In order to do so a framework and 
various protocols must be worked out. I will be posting a document sometime 
later on this week laying out both models in detail.

Yakov 


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