From owner-ietf@ietf.org  Thu May  1 01:00:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07001;
	Thu, 1 May 2003 01:00:54 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19B455-00014k-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 22:45:55 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19B3xx-0000yt-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 22:38:33 -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 WAA03420
	for <ietf@ietf.org>; Wed, 30 Apr 2003 22:34:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19B3wN-0005Va-00
	for ietf@ietf.org; Wed, 30 Apr 2003 22:36:55 -0400
Received: from conure.mail.pas.earthlink.net ([207.217.120.54])
	by ietf-mx with esmtp (Exim 4.12)
	id 19B3wH-0005VV-00
	for ietf@ietf.org; Wed, 30 Apr 2003 22:36:49 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by conure.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19B3w9-00001M-00; Wed, 30 Apr 2003 19:36:41 -0700
Date: Wed, 30 Apr 2003 22:35:35 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Stephen Sprunk" <stephen@sprunk.org>
Cc: moore@cs.utk.edu, mat@cisco.com, john-ietf@jck.com,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: My thoughts on local-use addresses
Message-Id: <20030430223535.5dd95ad6.moore@cs.utk.edu>
In-Reply-To: <010101c30f64$c7792f20$93b58742@ssprunk>
References: <20030426060420.GA93218@lethargic.dyndns.org>
	<20030426164255.GA98043@lethargic.dyndns.org>
	<20030426130211.321b0a4d.moore@cs.utk.edu>
	<13367010.1051372503@p3.JCK.COM>
	<20030430135832.1a645f93.moore@cs.utk.edu>
	<16048.5557.124583.930323@thomasm-u1.cisco.com>
	<20030430151648.3c3d352e.moore@cs.utk.edu>
	<16048.13708.414125.689623@thomasm-u1.cisco.com>
	<20030430165930.3b7af536.moore@cs.utk.edu>
	<010101c30f64$c7792f20$93b58742@ssprunk>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > nope, the app.  the stack doesn't know whether the app prefers stability
> > or efficiency, unless the app tells it which it prefers.  but at least
> > the app probably has an idea which one is better.
> 
> The app developer often doesn't know these things either -- if the app
> understands this new API at all, I think it'd most often end up as a user
> knob, meaning we could just call it a stack option and leave the app out of
> things entirely.

at least some apps do know these things.  a web browser, for instance, 
understands that its TCP connections are ephemeral, and it knows how to 
recover from broken connections.  same thing for an SMTP MTA or a mail
reader.  OTOH an interactive login using ssh is probably better off
using stable addresses, as is an NFS mount.

however if the API exists then nothing prevents the app from having a knob
that lets the user override the default.

> Which is harder, having the stack give the app a list of source and
> destination addresses and then expect the app to figure out which to use, or
> have the stack attempt various combinations of source and destination
> addresses and just notify the application which one(s) worked?

from experience, the delay in the latter case is often unacceptable,
and even if it isn't, the stack often makes the wrong choice for the app.

> Something tells me the latter is both easier and more likely to be
> implemented correctly.

you're simply wrong about that.

Keith



From owner-ietf@ietf.org  Thu May  1 01:00:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07022;
	Thu, 1 May 2003 01:00:55 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19B4AS-00018t-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 22:51:28 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19B44b-00014L-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 22:45:25 -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 WAA03554
	for <ietf@ietf.org>; Wed, 30 Apr 2003 22:42:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19B43V-0005X4-00
	for ietf@ietf.org; Wed, 30 Apr 2003 22:44:17 -0400
Received: from avocet.mail.pas.earthlink.net ([207.217.120.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19B43P-0005Wz-00
	for ietf@ietf.org; Wed, 30 Apr 2003 22:44:11 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by avocet.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19B43I-0005nj-00; Wed, 30 Apr 2003 19:44:05 -0700
Date: Wed, 30 Apr 2003 22:43:03 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, sbwoodside@yahoo.com, mat@cisco.com, randy@psg.com,
        cos@aaaaa.org, ietf@ietf.org
Subject: Re: site-local != NAT
Message-Id: <20030430224303.2ea73585.moore@cs.utk.edu>
In-Reply-To: <07ff01c30f72$d91a8c70$261e4104@eagleswings>
References: <7550A6A0-7B52-11D7-8B42-000393414368@yahoo.com>
	<07ff01c30f72$d91a8c70$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> My point was that there are topology locators that are only viable
> within a scope defined by the local network manager. 

yes, we know this.  it's a bad idea, and we need to stop pretending it's
a legitimate thing to do.  that way, when the network manager does this, it's
his fault when things break.

network managers do have legitimate needs that must be respected.
this is not one of them.

Keith



From owner-ietf@ietf.org  Thu May  1 01:00:58 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07032;
	Thu, 1 May 2003 01:00:58 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19B4QN-0001N6-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 23:07:55 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19B4JF-0001EW-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 23:00:33 -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 WAA03740
	for <ietf@ietf.org>; Wed, 30 Apr 2003 22:56:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19B4Ht-0005b3-00
	for ietf@ietf.org; Wed, 30 Apr 2003 22:59:09 -0400
Received: from snipe.mail.pas.earthlink.net ([207.217.120.62])
	by ietf-mx with esmtp (Exim 4.12)
	id 19B4Ho-0005ay-00
	for ietf@ietf.org; Wed, 30 Apr 2003 22:59:04 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by snipe.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19B4Hw-0004iM-00; Wed, 30 Apr 2003 19:59:13 -0700
Date: Wed, 30 Apr 2003 22:58:12 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, cos@aaaaa.org, ietf@ietf.org
Subject: Re: what the "scope" disagreement is about
Message-Id: <20030430225812.481e47f4.moore@cs.utk.edu>
In-Reply-To: <07ed01c30f57$87835b50$261e4104@eagleswings>
References: <20030430150922.F574@thwip.polyamory.org>
	<07ed01c30f57$87835b50$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Given a list of addresses for a target, how would an application pick
> one that is assured to work at the receiver? Answer: it can't without
> knowing the topology. The only way to keep the app from knowing
> topology, and make the app work in the presence of a list is to pass the
> label that was used to get the initial list, so the receiver can get its
> own that is topologically appropriate. 

Tony, 

What you are essentially claiming is that an application that doesn't know
about network topology should defer choices that must be based on topology to
some other application.  Of course, it's not any easier for that other 
application to know about topology, and it's also less reliable and less
efficient.  It might seem reasonable to isolate the topology-selection stuff
into a single application, but it's not - different applications have 
different needs in this regard.  Again this is from experience with an app
that needed to choose the closest of several alternate URLs for a resource -
doing all of the DNS lookups on all of the URLs and then trying to find the
closest one of those was just too slow.  Finally, if you want any app -
even this "special" app, to be aware of topology, then the first thing you
need is globally scoped labels for points in the topology - which is exactly
what exposing site locals to applications denies you.

Keith



From owner-ietf@ietf.org  Thu May  1 03:53:27 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01618;
	Thu, 1 May 2003 03:53:27 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19B69h-0004ib-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 00:58:49 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19B62B-0004bI-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 00:51:03 -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 AAA06810
	for <ietf@ietf.org>; Thu, 1 May 2003 00:47:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19B614-00061K-00
	for ietf@ietf.org; Thu, 01 May 2003 00:49:54 -0400
Received: from web10902.mail.yahoo.com ([216.136.131.38])
	by ietf-mx with smtp (Exim 4.12)
	id 19B60y-000612-00
	for ietf@ietf.org; Thu, 01 May 2003 00:49:48 -0400
Message-ID: <20030501044927.84860.qmail@web10902.mail.yahoo.com>
Received: from [12.237.229.250] by web10902.mail.yahoo.com via HTTP; Wed, 30 Apr 2003 21:49:27 PDT
Date: Wed, 30 Apr 2003 21:49:27 -0700 (PDT)
From: Spencer Dawkins <spencer_dawkins@yahoo.com>
Subject: Re: My thoughts on local-use addresses
To: ipng@sunroof.eng.sun.com, ietf@ietf.org
In-Reply-To: <010101c30f64$c7792f20$93b58742@ssprunk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Steve Deering had a nice set of slides in London about the
horrible things that we were doing to "the wasp waist" (IP), but
that doesn't mean that "wasp waists" don't have real advantages.

We like to say in TSV that having applications handle congestion
control is wrong because if 19 applications out of 20 do it
correctly, the guy who hoses it up, hoses it for everyone.

Although the potential for disaster on interface selection is
limited, what we're trying to do isn't trivial, and the chances
a stack can do a better job than a random application seem
pretty large to me. I'd vote for Stephen's "latter".

Spencer

--- Stephen Sprunk <stephen@sprunk.org> wrote:
> 
> Which is harder, having the stack give the app a list of
> source and
> destination addresses and then expect the app to figure out
> which to use, or
> have the stack attempt various combinations of source and
> destination
> addresses and just notify the application which one(s) worked?
> 
> Something tells me the latter is both easier and more likely
> to be
> implemented correctly.



From owner-ietf@ietf.org  Thu May  1 07:49:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05765;
	Thu, 1 May 2003 07:49:08 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19B9rX-0006ah-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 04:56:19 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19B9hB-0006WG-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 04:45:38 -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 EAA02386
	for <ietf@ietf.org>; Thu, 1 May 2003 04:42:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19B9fm-0007OJ-00
	for ietf@ietf.org; Thu, 01 May 2003 04:44:10 -0400
Received: from mailhost.iprg.nokia.com ([205.226.5.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 19B9fb-0007Nx-00
	for ietf@ietf.org; Thu, 01 May 2003 04:44:00 -0400
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id BAA23623;
	Thu, 1 May 2003 01:43:34 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h418hXq18682;
	Thu, 1 May 2003 01:43:33 -0700
X-mProtect: <200305010843> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (172.18.5.137, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdkmtRks; Thu, 01 May 2003 01:43:30 PDT
Message-ID: <3EB0DE53.60002@iprg.nokia.com>
Date: Thu, 01 May 2003 01:44:03 -0700
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: alh-ietf@tndh.net
CC: ietf@ietf.org
Subject: Re: site-local != NAT
References: <07f301c30f6b$87a28c00$261e4104@eagleswings>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hello Tony,

Your example is very interesting:

Tony Hain wrote:

>>I have not heard any compelling operational requirement for 
>>ambiguous addresses in IPv6.
>>    
>>
>
>According to the definition above, anycast is one such case. Given that
>anycast is in daily operational use, there must be a requirement for
>addresses to refer to different physical devices in different parts of
>the network.
>  
>
For anycast, the application would be satisfied no matter which of the
several physical devices would respond.  Maybe we can say that
addresses should only be ambiguous when it is known by definition
that the ambiguity can never affect the applications using the address.

Regards,
Charlie P.





From owner-ietf@ietf.org  Thu May  1 09:07:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07952;
	Thu, 1 May 2003 09:07:08 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BBSj-0007RJ-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 06:38:49 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BBSZ-0007P0-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 06:38:39 -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 GAA04843
	for <ietf@ietf.org>; Thu, 1 May 2003 06:34:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BBR9-00008G-00
	for ietf@ietf.org; Thu, 01 May 2003 06:37:11 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BBR3-000087-00
	for ietf@ietf.org; Thu, 01 May 2003 06:37:05 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h41AbGtU016931;
	Thu, 1 May 2003 06:37:17 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h41AbGYs016930;
	Thu, 1 May 2003 06:37:16 -0400
Date: Thu, 1 May 2003 06:37:16 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200305011037.h41AbGYs016930@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: My thoughts on local-use addresses
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: Keith Moore <moore@cs.utk.edu>

    > .. I don't see a significant market for IPv6 if it doesn't support
    > applications that cannot be run on NATted IPv4. Yes, there may still be
    > some small advantage of IPv6 for some groups of users if this doesn't
    > happen, but not for the Internet community as a whole.
    > ...
    > In order to create a significant advantage, there need to be so few
    > NATs in IPv6 that application developers can write applications that
    > will fail in the presence of NATs ..
    > I agree that there's a requirement for PI addresses

The irony here is pretty striking.

IPv6 (you reckon) won't succeed in taking off unless it can get rid of NAT's,
but people have NAT's (in part) because they want identifiers for their
machines that are independent of their location in the connectivity topology.
Clearly, you can't have a single label which is both location-independent (so
it's provider independent) and location-dependent (so that the routing
works). Which is why people use NAT's to do this... but you claim IPv6 will
fail to take off if it can't get rid of NAT's.

The irony is that in the architectural discussion phase (such as it was) of
IPng, it was proposed that these two functions (location and identification)
be split, but this concept was fiercely resisted by the IPv6 designers; it
will be extremely piquant if this decision results in continued desire for
NAT's, and therefore (if you're right) the failure of IPv6 to take off...

	Noel



From owner-ietf@ietf.org  Thu May  1 14:16:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26606;
	Thu, 1 May 2003 14:16:10 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BIS6-00055A-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 14:06:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BIIg-0004yG-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 13:56:54 -0400
Received: from tndh.net (evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net [4.65.19.240])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25148
	for <ietf@ietf.org>; Thu, 1 May 2003 13:53:23 -0400 (EDT)
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26DB5> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 01 May 2003 10:48:07 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Keith Moore'" <moore@cs.utk.edu>
Cc: <cos@aaaaa.org>, <ietf@ietf.org>
Subject: RE: what the "scope" disagreement is about
Date: Thu, 1 May 2003 10:48:07 -0700
Message-ID: <086301c31009$d3251a00$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030430225812.481e47f4.moore@cs.utk.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA26606

Keith Moore wrote:
> ... Finally, if you want 
> any app - even this "special" app, to be aware of topology, 
> then the first thing you need is globally scoped labels for 
> points in the topology - which is exactly what exposing site 
> locals to applications denies you.

What ???  Yes we need a way to differentiate them, but eliminating the
local one doesn't accomplish that. The labels FEC0::/10 vs. 2::/3
provide exactly the scoping differentiator this statement claims to
need. Your comment appears to be so focused on the 'local' aspect of one
of the labels, that it missed the point that the other label is global. 

Making all labels global only works if the routing is in fact globally
flat. We know it isn't, so we should provide a simple way to figure it
out for processes that care. We should not be eliminating the only means
we have to figure it out. Yes, we need to complete the work on making
the 38 bits globally unique, but that can't happen if we start by
eliminating the first 10.

Tony






From owner-ietf@ietf.org  Thu May  1 14:17:25 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26788;
	Thu, 1 May 2003 14:17:25 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BIS7-00055G-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 14:06:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BIIg-0004yH-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 13:56:54 -0400
Received: from tndh.net (evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net [4.65.19.240])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25147
	for <ietf@ietf.org>; Thu, 1 May 2003 13:53:23 -0400 (EDT)
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26DB3> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 01 May 2003 10:47:59 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Keith Moore'" <moore@cs.utk.edu>
Cc: <sbwoodside@yahoo.com>, <mat@cisco.com>, <randy@psg.com>, <cos@aaaaa.org>,
        <ietf@ietf.org>
Subject: RE: site-local != NAT
Date: Thu, 1 May 2003 10:47:59 -0700
Message-ID: <086101c31009$ce4abb20$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030430224303.2ea73585.moore@cs.utk.edu>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore wrote:
> > My point was that there are topology locators that are only viable 
> > within a scope defined by the local network manager.
> 
> yes, we know this.  it's a bad idea, and we need to stop 
> pretending it's a legitimate thing to do.  that way, when the 
> network manager does this, it's his fault when things break.
> 
> network managers do have legitimate needs that must be 
> respected. this is not one of them.

So your position is that network managers are required to route all
prefixes in the global table, and access controls are to be removed ...

Tony




From owner-ietf@ietf.org  Thu May  1 14:22:46 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27261;
	Thu, 1 May 2003 14:22:46 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BIS7-00055M-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 14:06:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BIIw-0004yK-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 13:57: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 NAA25203
	for <ietf@ietf.org>; Thu, 1 May 2003 13:53:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BIHf-0004aZ-00
	for ietf@ietf.org; Thu, 01 May 2003 13:55:51 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19BIHZ-0004aP-00
	for ietf@ietf.org; Thu, 01 May 2003 13:55:45 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26DB4> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 01 May 2003 10:48:03 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Theodore Ts'o'" <tytso@mit.edu>
Cc: "'Ofer Inbar'" <cos@aaaaa.org>, <ietf@ietf.org>
Subject: RE: what the "scope" disagreement is about
Date: Thu, 1 May 2003 10:48:03 -0700
Message-ID: <086201c31009$d0b356b0$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030501120516.GA5120@think>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA27261

Theodore Ts'o wrote:
>> The real network is not a single flat routing space.
> 
> And this is where we disagree.  For better or for worse, the 
> market is demanding that IP addresses that can be treated as 
> belong to a single flat routing space.  

The market demand is for stable addresses that can be routed globally.
That does not mean that the network manager wants to globally route
every prefix.

> How else do you 
> explain the demand for provider independent addresses, and 
> people punching holes in CIDR blocks so they can have have 
> multihoming support for reliable network service?

The market demand is for address space that is STABLE. This stability
must isolate the network manager from the whims of any ISP, as well as
prevent the network manager from being locked into a provider to avoid
the cost of renumbering. That does not equate to a demand that every
prefix be globally routed, or that every node be globally accessible.
The network manager demands the control to decide that. 

The IETF app community is demanding that to keep their view of the world
pristine and simple, they get to define the world as a flat routing
space, and claim they are passing around opaque data structures, at the
same time they fully intend for the receiver to use the opaque object as
a topology locator. 

> 
> One solution for that would be to not do multihoming, and 
> simply have servers live on multiple IP addresses belonging 
> to multiple ISP's, and use multiple DNS 'A' records in order 
> to provide reachability.  I suspect that would be Tony's 
> solution about what we should be doing today. 

That scenario is inconsistent. You start with 'not do multihoming', but
then describe multihomed servers. 

> This is 
> perhaps workable for short-term http connections, but it's 
> absolutely no good for long-term TCP connections, which won't 
> survive a service outage since TCP commits the "sin" of using 
> IP addresses to identify its endpoints, instead of using DNS 
> addresses....  

I did not say that using an IP address was a sin, just that doing so
without understanding the topology that you are describing is a broken
model.

> But whether this is the reason, or the whether 
> there are other reasons why the "solution" of killing off 
> provider independent addresses and letting the DNS sort it 
> out has been perceived as unacceptable, it's pretty clear 
> that the market is spoken.  Even as people have been wagging 
> their fingers and saying "horrible, horrible", customers are 
> demanding it, and ISP's are providing it.  This is the 
> situation in IPv4, and I very much doubt the situation is 
> going to change much in IPv6.

I agree that PI is in market demand, and have a couple of personal
drafts on the topic. I saw this as a failing in the current PA or
Private, allocation model and figured we needed to get it dealt with.

> 
> It's certainly true that having a reliable end-point 
> identifier is critical.  But I don't think the DNS is it. 

One of my points awhile back was that the current DNS is not up to the
task, and neither are the other name resolution services. Those need to
be addressed at the same time as the applications that insist in doing
the work for themselves.
 
> The DNS has been abused in many different ways, and very 
> often, thanks to split DNS games, and CNAMES, and all the 
> rest, the name which the user supplies to the application is 
> also not guaranteed to be a name which can be utilizable by C 
> when B wants to tell C to connect to A:
> 
> >      ---- A ----
> >        |      I
> >        |      n
> >        |      t
> >        I      e ---- C
> >        2      r
> >        |      n
> >        |      e
> >        |      t
> >      ---- B ----
> 
> Tony is basically saying, "IP addresses don't work for this, 
> so let's bash application writers by saying they are broken, 
> and tell them to use DNS addresses instead".  

I am saying that the app either needs to learn the topology, or pass the
task off to a service that has the means to learn it. Passing around
addresses that are useless is not an approach to solving the problem.

> Well, I'm here 
> to point out that DNS addresses don't work either.  
> Applications get names such as "eddie.eecs", and even when 
> they get a fully qualified domain name, thanks to a very 
> large amount of variability in how system administrators have 
> set up split-DNS, there is no gauarantee that a particular 
> DNS name is globally available, or even globally points at 
> the same end point.  So if IP addresses are not a flat 
> routing space, DNS names are not a flat naming space, either.  

Which simply points out we have work to do, that won't get done by
avoiding the issue.

> 
> I struggled for a while to come up with ways of coming up 
> with a "canonical DNS name" which could be passed around to 
> multiple hosts many years ago when I was trying to come up 
> with a convenient way to construct canonicalized, globally 
> usable Kerberos principal names from host specifiers that 
> were supplied by the user on the command line. We ran up 
> against the same problem.  Fundamentally, the DNS wasn't and 
> isn't designed to do this.

So the IESG needs to task the DNS community with fixing it. The reality
of the deployed network is that the topology is inconsistent from
different perspectives. If all the 'identifier to topology' resolving
processes expect the world to be flat, they are simply broken.

> 
> Now, I suppose you could say that the people who "broke" DNS 
> are fault, but there are also people who would say that the 
> people who broken the flat routing space assumption (which 
> while not universally true was true enough for engineering 
> purposes) are a fault instead. Perhaps a more constructive 
> thing to say is that the original Internet architecture --- 
> and here I mean everything in the entire protocol stack, from 
> link layer protocols to application level protocols --- were 
> not well engineered to meet the requirements that we see 
> being demanded of us today.

Or even 20 years ago. The issue was ignored in the past because the
demand was low enough to allow that. 

> 
> This is why I believe that ultimately 8+8 is the most 
> interesting approach.  As the old saw goes, "there is no 
> problem in computer science that cannot be solved by adding 
> an additional level of indirection".  

8+8 and similar schemes suffer one of the same problems you are
complaining about. To make them work, the network needs a very fast
converging, global, identifier to locator mapping service. Mangling the
address field in the packet only allows the app to use part of the
address for the identifier. There is no reason that the identifier has
to be part of the address.

> 
> What we need is something that sits between DNS names and 
> provider-specific IP addresses.  That is a hole in the 
> architecture which today is being fixed by using 
> provider-independent addresses, much to the discomfort of 
> router engineers.  Another solution, which has been 
> articulated by Tony, is that we should sweep all of this dirt 
> under the DNS carpet instead, and force the application 
> writers to retool all their implementations and protocols to 
> pass DNS names around instead.  But the DNS really isn't 
> suited to handle this.  What we need is something in-between.

The problem will not be solved by PI addressing. I don't care if apps
pass around addresses, as long as they are doing the work to make sure
the address is consistent with the topology the app is intentionally
describing. If the app is not going to learn about topology (and I agree
the app shouldn't) it needs to rely on a service that has the means to
do the job. We agree, the current DNS is not up to the task. 

Tony




From owner-ietf@ietf.org  Thu May  1 14:38:17 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28130;
	Thu, 1 May 2003 14:38:16 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BIrW-0006Tr-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 14:32:54 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BInE-0006Qu-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 14:28:28 -0400
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27486
	for <ietf@ietf.org>; Thu, 1 May 2003 14:24:58 -0400 (EDT)
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h41IMGv15430;
        Thu, 1 May 2003 14:22:18 -0400 (EDT)
Date: Thu, 1 May 2003 14:22:16 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: site-local != NAT
Message-Id: <20030501142216.30d7fc7c.moore@cs.utk.edu>
In-Reply-To: <086101c31009$ce4abb20$261e4104@eagleswings>
References: <20030430224303.2ea73585.moore@cs.utk.edu>
	<086101c31009$ce4abb20$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > > My point was that there are topology locators that are only viable
> > > within a scope defined by the local network manager.
> > 
> > yes, we know this.  it's a bad idea, and we need to stop 
> > pretending it's a legitimate thing to do.  that way, when the 
> > network manager does this, it's his fault when things break.
> > 
> > network managers do have legitimate needs that must be 
> > respected. this is not one of them.
> 
> So your position is that network managers are required to route all
> prefixes in the global table, and access controls are to be removed

no, I probably misunderstood what you meant by 'viable'.

my position is that 

- ambiguous addresses are harmful;

- packet filtering based on addresses, and filtering of advertised
  routes, are not very good ways to implement host security, but the
  current state of authentication is such that these crude mechanisms
  cannot be dispensed with entirely anytime soon;

- apps need to be able to pass around tokens that are reliably and
  precisely associated with hosts, and which can be used to reliably
  and efficiently send  messages to hosts (modulo access control
  limitations), and DNS cannot adequately provide this service;

- forcing hosts to make the right choice from several  (source,
  destination) address pairs in order to successfully  send packets to a
  destination is unrealistic, especially when those choices require
  information that is not readily available to hosts or applications.

Keith



From owner-ietf@ietf.org  Thu May  1 14:59:38 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29388;
	Thu, 1 May 2003 14:59:37 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BJ1C-0006zd-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 14:42:54 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BIw8-0006YM-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 14:37:40 -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 OAA28000
	for <ietf@ietf.org>; Thu, 1 May 2003 14:34:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BIuq-00053R-00
	for ietf@ietf.org; Thu, 01 May 2003 14:36:20 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BIul-000535-00
	for ietf@ietf.org; Thu, 01 May 2003 14:36:15 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h41Iahv15479;
        Thu, 1 May 2003 14:36:43 -0400 (EDT)
Date: Thu, 1 May 2003 14:36:43 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, cos@aaaaa.org, ietf@ietf.org
Subject: Re: what the "scope" disagreement is about
Message-Id: <20030501143643.3c6418f7.moore@cs.utk.edu>
In-Reply-To: <086301c31009$d3251a00$261e4104@eagleswings>
References: <20030430225812.481e47f4.moore@cs.utk.edu>
	<086301c31009$d3251a00$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > ... Finally, if you want 
> > any app - even this "special" app, to be aware of topology, 
> > then the first thing you need is globally scoped labels for 
> > points in the topology - which is exactly what exposing site 
> > locals to applications denies you.
> 
> What ???  Yes we need a way to differentiate them, but eliminating the
> local one doesn't accomplish that. The labels FEC0::/10 vs. 2::/3
> provide exactly the scoping differentiator this statement claims to
> need. 

being able to distinguish an ambiguous address from a global address
doesn't solve the problem of requiring hosts or apps to be aware of
topology in order to make address selection.  the problem here is that
an SL address is ambiguous in almost any context outside of an RA or IP
header; so there's simply no way to be confident that a particular SL
belongs to a particular section of the network. 

ambiguous addresses are both the factor that would force hosts and apps
to be more aware of topology AND the factor that make it intractable for
hosts and apps to be aware of topology.  Not only do they cause this
problem, they preclude any solution to the problem.

> Making all labels global only works if the routing is in fact globally
> flat. 

It's worked in IPv4 for 20+ years.  What has been repeatedly shown to
not work well is to try to route on non-global labels.  (anyone remember
uucp mail or easynet?)

> Yes, we need to complete the work on
> making the 38 bits globally unique, but that can't happen if we start
> by eliminating the first 10.

If we can agree on how to make the first 48 bits globally unique, does
it really matter what values are assigned to the first 10 bits? That
choice could be made strictly on the basis of compatibility issues with
existing hosts, apps, and routers, once the other technical aspects of
GUPIs had been worked out.

(yes, GUPIs, NOT SLs.  they WILL be routed between sites, for good
reasons, and we shouldn't try to stop this)

Keith



From owner-ietf@ietf.org  Thu May  1 15:28:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02999;
	Thu, 1 May 2003 15:28:43 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BJhc-0006Vx-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 15:26:44 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BJV6-0003vq-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 15:13:48 -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 PAA00565
	for <ietf@ietf.org>; Thu, 1 May 2003 15:10:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BJTZ-0005Rr-00
	for ietf@ietf.org; Thu, 01 May 2003 15:12:13 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BJTU-0005Ri-00
	for ietf@ietf.org; Thu, 01 May 2003 15:12:08 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h41JCYv15606;
        Thu, 1 May 2003 15:12:34 -0400 (EDT)
Date: Thu, 1 May 2003 15:12:34 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: moore@cs.utk.edu, ietf@ietf.org, jnc@ginger.lcs.mit.edu
Subject: Re: My thoughts on local-use addresses
Message-Id: <20030501151234.455a6707.moore@cs.utk.edu>
In-Reply-To: <200305011037.h41AbGYs016930@ginger.lcs.mit.edu>
References: <200305011037.h41AbGYs016930@ginger.lcs.mit.edu>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>     > .. I don't see a significant market for IPv6 if it doesn't
>     > support applications that cannot be run on NATted IPv4. Yes,
>     > there may still be some small advantage of IPv6 for some groups
>     > of users if this doesn't happen, but not for the Internet
>     > community as a whole....
>     > In order to create a significant advantage, there need to be so
>     > few NATs in IPv6 that application developers can write
>     > applications that will fail in the presence of NATs ..
>     > I agree that there's a requirement for PI addresses
> 
> The irony here is pretty striking.
> 
> IPv6 (you reckon) won't succeed in taking off unless it can get rid of
> NAT's, but people have NAT's (in part) because they want identifiers
> for their machines that are independent of their location in the
> connectivity topology.

People have NATs for a wide variety of reasons:

- they can't get enough global addresses for their hosts
- they are deluded into thinking they provide security
- they don't want to have to renumber
- they need to connect between multiple sites using overlapping
  address space
- they don't realize they have a NAT, they think it's a "firewall"
  or some such
- their ISPs force NATs on them

...but I doubt that a significant percentage of users think in terms
of "want[ing] identifiers for their machines that are independent of
their location in the connectivity topology".  You and I think that
way, but this is not what motivates users to purchase NATs.  Users want
their networks to be secure and easy to manage and for their apps to
work; they buy NATs because they think that under current circumstances
these conditions are better met with NATs than without.  Some of those
users may even be right, at least in the near term, and for the apps
they anticipate wanting to use.  We're more concerned about the future.

Now, I agree that location-independent identifiers would be desirable IF
they were globally scoped and globally usable, but NATs (at least,
any kind of NATs we've envisioned so far) would not provide these.
Locally scoped identifiers can be stable on the local net (though they
aren't necessarily so, even behind a NAT)  But it's becoming more
apparent that stable local identifiers are not sufficient, unless the
only apps we want to run over the global network are two-party apps with
ephemeral connections.

> Clearly, you can't have a single label which is both
> location-independent (so it's provider independent) and
> location-dependent (so that the routing works). 

It depends on what you mean by "routing".  Users don't care about the
mechanism for how those packets get there, they care whether the apps
work.  If the packets had to get redirected from a location-independent
address to a location-dependent address, that would be fine with users
as long as that operation happened quickly and reliably enough to suit
the users' apps.  Of course, our existing protocols don't really support
this (with the possible exception of mobile IP, which never seems to
get finished) but I don't think it's a matter of "clearly, you can't" do
this.

> Which is why people use NAT's to do this...

Except that NATs don't do this, unless the only apps you care about are
local apps.  And experience indicates that users don't just care about
local apps.

> The irony is that in the architectural discussion phase (such as it
> was) of IPng, it was proposed that these two functions (location and
> identification) be split,

Lots of good ideas got passed over in the IPng discussion.   Despite
that, I think that IPv6 ended up "about right" - modulo a few warts like
A6 and SL and over-reliance on address selection.  By "about right" I
mean that I think that if the warts are fixed it will become feasible to
gracefully extend the IPv6 architecture in useful ways - such as to
provide the capability to use identifiers rather than locators -
without invalidating hosts or apps that were written to the basic IPv6
model.  (there are still some other warts - e.g. wired-in assumptions
about prefix lengths - that I suspect will bite us sooner or later)

Keith





From owner-ietf@ietf.org  Thu May  1 16:18:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07580;
	Thu, 1 May 2003 16:18:35 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BGsD-000390-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 12:25:29 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BGlp-00034a-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 12:18:54 -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 MAA20183
	for <ietf@ietf.org>; Thu, 1 May 2003 12:15:25 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BGka-0003Rk-00
	for ietf@ietf.org; Thu, 01 May 2003 12:17:36 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BGkU-0003Qj-00
	for ietf@ietf.org; Thu, 01 May 2003 12:17:30 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h41GGpxj004116;
	Thu, 1 May 2003 12:16:51 -0400
Message-Id: <200305011616.h41GGpxj004116@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Ofer Inbar <cos@aaaaa.org>
Cc: ietf@ietf.org
Subject: Re: what the "scope" disagreement is about 
In-Reply-To: Your message of "Wed, 30 Apr 2003 15:09:22 EDT."
             <20030430150922.F574@thwip.polyamory.org> 
References: <16047.57167.821886.158969@thomasm-u1.cisco.com> <07c801c30f37$b859d9e0$261e4104@eagleswings> <20030430130432.2397ba40.moore@cs.utk.edu>
            <20030430150922.F574@thwip.polyamory.org>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1187828409P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 01 May 2003 12:16:51 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_1187828409P
Content-Type: text/plain; charset=us-ascii

On Wed, 30 Apr 2003 15:09:22 EDT, Ofer Inbar said:

> From what I have seen, those who think "local scope" is harmful, are
> concerned about the ambuity of addresses, as Keith says here again.

Exactly.

> They are NOT concerned about the fact that a given address may not be
> reachable from some places, or may be reachable via different routes
> from different places.  Or, rather, whether they're concerned about
> that or not, it has nothing to do with their objections to locally
> scoped addresses.

Yes, I'm concerned about reachability, and it *does* have something to
do with locally scoped addresses, but in an inverse fashion..

>                    All of their objections to locally scoped addresses
> seem to be about the fact that the addresses are ambiguous, not unique.
> They have no objections to globally unique addresses that remain
> "local" as far as routing and reachability.

The "inverse fashion" mentioned above - it's a LOT harder to diagnose a
problem when the remote end is handing you bogon debugging information.
Anybody else ever had to deal with the case where a 'traceroute' to a
dead host shows one path, but sending a TCP SYN packet gets back an
ICMP Host Unreachable from one RFC1918 space address complaining about
another 1918-space address, neither of which are in the traceroute? ;)

--==_Exmh_1187828409P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+sUhzcC3lWbTT17ARAiErAKDkRh0EN4pnc+vbWNRR7SebKhCiBQCg7geE
0FOns6/VQhEkkLYDbyOaXpk=
=8naC
-----END PGP SIGNATURE-----

--==_Exmh_1187828409P--



From owner-ietf@ietf.org  Thu May  1 16:18:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07604;
	Thu, 1 May 2003 16:18:37 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BDL1-0000P9-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 08:38:59 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BCp8-00005d-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 08:06:02 -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 IAA06246
	for <ietf@ietf.org>; Thu, 1 May 2003 08:02:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BCnh-0000S1-00
	for ietf@ietf.org; Thu, 01 May 2003 08:04:33 -0400
Received: from thunk.org ([140.239.227.29] helo=thunker.thunk.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19BCnW-0000Rm-00
	for ietf@ietf.org; Thu, 01 May 2003 08:04:22 -0400
Received: from [216.175.175.162] (helo=think.thunk.org)
	authenticated as tytso by thunker.thunk.org with asmtp 
	(tls_cipher TLSv1:DES-CBC3-SHA:168) 
	(tls_peerdn /C=US/ST=Massachusetts/L=Medford/O=Thunking Systems/OU=SMTP-client/CN=think.thunk.org/Email=tytso@thunk.org)
	 (Exim 3.35 #1 (Debian))
	id 19BCnM-0002y0-00; Thu, 01 May 2003 08:04:12 -0400
Received: from tytso authenticated as tytso by think.thunk.org with local   (Exim 3.35 #1 (Debian))
	id 19BCoP-0001fn-00; Thu, 01 May 2003 08:05:17 -0400
Date: Thu, 1 May 2003 08:05:16 -0400
From: "Theodore Ts'o" <tytso@mit.edu>
To: Tony Hain <alh-ietf@tndh.net>
Cc: "'Ofer Inbar'" <cos@aaaaa.org>, ietf@ietf.org
Subject: Re: what the "scope" disagreement is about
Message-ID: <20030501120516.GA5120@think>
References: <20030430150922.F574@thwip.polyamory.org> <07ed01c30f57$87835b50$261e4104@eagleswings>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <07ed01c30f57$87835b50$261e4104@eagleswings>
User-Agent: Mutt/1.5.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, Apr 30, 2003 at 01:31:50PM -0700, Tony Hain wrote:
> The reason I say this is about reachability is that even with unique
> addresses, applications will fail when they choose to pass 'an opaque
> identifier' around, while they simultaneously assume that the content is
> a valid topology locator at the receiver. The arguments claim the need
> for opaqueness as an application simplifier on one hand, at the same
> they insist that the topology match their perspective of a flat routing
> space. The real network is not a single flat routing space.

And this is where we disagree.  For better or for worse, the market is
demanding that IP addresses that can be treated as belong to a single
flat routing space.  How else do you explain the demand for provider
independent addresses, and people punching holes in CIDR blocks so
they can have have multihoming support for reliable network service?

One solution for that would be to not do multihoming, and simply have
servers live on multiple IP addresses belonging to multiple ISP's, and
use multiple DNS 'A' records in order to provide reachability.  I
suspect that would be Tony's solution about what we should be doing
today.  This is perhaps workable for short-term http connections, but
it's absolutely no good for long-term TCP connections, which won't
survive a service outage since TCP commits the "sin" of using IP
addresses to identify its endpoints, instead of using DNS
addresses....  But whether this is the reason, or the whether there
are other reasons why the "solution" of killing off provider
independent addresses and letting the DNS sort it out has been
perceived as unacceptable, it's pretty clear that the market is
spoken.  Even as people have been wagging their fingers and saying
"horrible, horrible", customers are demanding it, and ISP's are
providing it.  This is the situation in IPv4, and I very much doubt
the situation is going to change much in IPv6.

It's certainly true that having a reliable end-point identifier is
critical.  But I don't think the DNS is it.  The DNS has been abused
in many different ways, and very often, thanks to split DNS games, and
CNAMES, and all the rest, the name which the user supplies to the
application is also not guaranteed to be a name which can be
utilizable by C when B wants to tell C to connect to A:

>      ---- A ----
>        |      I
>        |      n
>        |      t
>        I      e ---- C
>        2      r
>        |      n
>        |      e
>        |      t
>      ---- B ----

Tony is basically saying, "IP addresses don't work for this, so let's
bash application writers by saying they are broken, and tell them to
use DNS addresses instead".  Well, I'm here to point out that DNS
addresses don't work either.  Applications get names such as
"eddie.eecs", and even when they get a fully qualified domain name,
thanks to a very large amount of variability in how system
administrators have set up split-DNS, there is no gauarantee that a
particular DNS name is globally available, or even globally points at
the same end point.  So if IP addresses are not a flat routing space,
DNS names are not a flat naming space, either.  

I struggled for a while to come up with ways of coming up with a
"canonical DNS name" which could be passed around to multiple hosts
many years ago when I was trying to come up with a convenient way to
construct canonicalized, globally usable Kerberos principal names from
host specifiers that were supplied by the user on the command line.
We ran up against the same problem.  Fundamentally, the DNS wasn't and
isn't designed to do this.

Now, I suppose you could say that the people who "broke" DNS are
fault, but there are also people who would say that the people who
broken the flat routing space assumption (which while not universally
true was true enough for engineering purposes) are a fault instead.
Perhaps a more constructive thing to say is that the original Internet
architecture --- and here I mean everything in the entire protocol
stack, from link layer protocols to application level protocols ---
were not well engineered to meet the requirements that we see being
demanded of us today.

This is why I believe that ultimately 8+8 is the most interesting
approach.  As the old saw goes, "there is no problem in computer
science that cannot be solved by adding an additional level of
indirection".  

What we need is something that sits between DNS names and
provider-specific IP addresses.  That is a hole in the architecture
which today is being fixed by using provider-independent addresses,
much to the discomfort of router engineers.  Another solution, which
has been articulated by Tony, is that we should sweep all of this dirt
under the DNS carpet instead, and force the application writers to
retool all their implementations and protocols to pass DNS names
around instead.  But the DNS really isn't suited to handle this.  What
we need is something in-between.

						- Ted



From owner-ietf@ietf.org  Thu May  1 16:18:33 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07556;
	Thu, 1 May 2003 16:18:33 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BGoZ-00035q-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 12:21:43 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BGfq-0002yE-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 12:12:42 -0400
Received: from turing-police.cc.vt.edu (turing-police.cc.vt.edu [128.173.14.107])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19730
	for <ietf@ietf.org>; Thu, 1 May 2003 12:08:28 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h41G8Dxj004081;
	Thu, 1 May 2003 12:08:13 -0400
Message-Id: <200305011608.h41G8Dxj004081@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: alh-ietf@tndh.net
Cc: "'Margaret Wasserman'" <mrw@windriver.com>,
        "'Michael Thomas'" <mat@cisco.com>, "'Randy Bush'" <randy@psg.com>,
        "'Keith Moore'" <moore@cs.utk.edu>, cos@aaaaa.org, ietf@ietf.org
Subject: Re: site-local != NAT 
In-Reply-To: Your message of "Wed, 30 Apr 2003 15:55:00 PDT."
             <07f301c30f6b$87a28c00$261e4104@eagleswings> 
References: <07f301c30f6b$87a28c00$261e4104@eagleswings>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1186939908P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 01 May 2003 12:08:13 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_1186939908P
Content-Type: text/plain; charset=us-ascii

On Wed, 30 Apr 2003 15:55:00 PDT, Tony Hain said:

I'm confoozled here...  First you say:

> The point is they don't when they claim to be passing around 'opaque
> identifiers', at the same time they are explicitly assuming the content
> of that opaque object is a valid topology object at the receiver.

Right - and the entire problem with "site local" addresses is that they are
almost by definition ambiguous if they ever escape.  The host sending the
opaque blob has no a priori way of knowing if the blob will be in the *right*
scope when you get there.

I get tons of spam that have "http://192.168.1.10/...." URLs.  Whoops.

> According to the definition above, anycast is one such case. Given that
> anycast is in daily operational use, there must be a requirement for
> addresses to refer to different physical devices in different parts of
> the network.

Again, the biggest problem with using anycast is guaranteeing that all
references to "the same" object actually look identical - for instance,
all sorts of amusement can be obtained by running an anycast root DNS server
where the various instances advertise different serial numbers on the SOA
for '.'.

Ambiguous addresses are a Bad Idea.

--==_Exmh_1186939908P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+sUZscC3lWbTT17ARAlcPAJ9PF8JtCXz6jOGtnbzrtn8f8KvyyACgtc22
1ovR7V1rI+P0Gt6Pr/9w3M4=
=DbMv
-----END PGP SIGNATURE-----

--==_Exmh_1186939908P--



From owner-ietf@ietf.org  Thu May  1 16:18:34 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07566;
	Thu, 1 May 2003 16:18:34 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BFiS-0001ir-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 11:11:20 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BFiC-0000TT-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 11:11:04 -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 LAA15770
	for <ietf@ietf.org>; Thu, 1 May 2003 11:07:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BFgO-0002To-00
	for ietf@ietf.org; Thu, 01 May 2003 11:09:12 -0400
Received: from wetware.wetware.com ([199.108.16.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BFgI-0002TQ-00
	for ietf@ietf.org; Thu, 01 May 2003 11:09:06 -0400
Received: from wetware.com([208.177.152.16]) (3011 bytes) by wetware.wetware.com
	via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp
	(sender: <jhw@wetware.com>) 
	id <m19BFfs-002zTnC@wetware.wetware.com>
	for <ietf@ietf.org>; Thu, 1 May 2003 08:08:40 -0700 (PDT)
	(Smail-3.2.0.114 2001-Aug-6 #1 built 2002-Sep-2)
Date: Thu, 1 May 2003 08:08:44 -0700
Subject: Re: My thoughts on local-use addresses
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: IETF list <ietf@ietf.org>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
From: james woodyatt <jhw@wetware.com>
In-Reply-To: <200305011037.h41AbGYs016930@ginger.lcs.mit.edu>
Message-Id: <CD28A60E-7BE6-11D7-A5C4-000393BA7EBA@wetware.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Thursday, May 1, 2003, at 03:37 US/Pacific, J. Noel Chiappa wrote:
>
> [...] IPv6 (you reckon) won't succeed in taking off unless it can get 
> rid of NAT's, but people have NAT's (in part) because they want 
> identifiers for their machines that are independent of their location 
> in the connectivity topology.  Clearly, you can't have a single label 
> which is both location-independent (so it's provider independent) and 
> location-dependent (so that the routing works). Which is why people 
> use NAT's to do this... but you claim IPv6 will fail to take off if it 
> can't get rid of NAT's. [...]

I work for a company that sells a NAT device.  Among other things, I 
maintain the ALG's in that NAT.  My code is bundled into their 
802.11b/g access point.  They also have a software version of this 
product bundled into the operating system they own for the computers 
they make.

I can assure you that the vast majority of those customers using the 
NAT in either of these products-- and I get a lot of customer feedback 
in the form of bugs and enhancement requests-- are doing so for reasons 
that are far less technical than you suggest.

They are *not* doing it because they "want identifiers for their 
machines that are independent of their location in the connectivity 
topology."  They are doing it because they want to share their Internet 
access with multiple computers.  The extent to which they are unhappy 
with the NAT function in those products is exactly the extent to which 
NAT fails to be totally transparent-- which it can never be, because of 
the Internet architecture.

If the only customers using NAT were the ones that really really really 
wanted "identifiers for their machines that are independent of their 
location in the connectivity topology," then I would feel completely 
safe writing applications that fail in the presence of NAT.  They would 
not be deployed in anywhere near the numbers they are clearly deployed 
now.  (In fact, I'd probably be extra tickled by the fact that my 
application failed on the remaining networks.  Their managers would be 
getting what they deserve, in my jaundiced view.)

Have any of you looked at the actual marketing copy that sells real 
people on why they might want to pay real money for a NAT box?  It 
might be instructive.


-- 
j h woodyatt <jhw@wetware.com>




From owner-ietf@ietf.org  Thu May  1 16:18:34 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07568;
	Thu, 1 May 2003 16:18:34 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BG7t-0002aq-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 11:37:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BFxl-0002VQ-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 11:27:09 -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 LAA16823
	for <ietf@ietf.org>; Thu, 1 May 2003 11:23:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BFwQ-0002kd-00
	for ietf@ietf.org; Thu, 01 May 2003 11:25:46 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BFwL-0002kS-00
	for ietf@ietf.org; Thu, 01 May 2003 11:25:41 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h41FPOtU018024;
	Thu, 1 May 2003 11:25:24 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h41FPOkm018023;
	Thu, 1 May 2003 11:25:24 -0400
Date: Thu, 1 May 2003 11:25:24 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200305011525.h41FPOkm018023@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: My thoughts on local-use addresses
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: james woodyatt <jhw@wetware.com>

    > I can assure you that the vast majority of those customers using the u
    > NAT in either of these products-- and I get a lot of customer feedback
    > .. -- are doing so for reasons that are far less technical than you
    > suggest.
    > They are *not* doing it because they "want identifiers for their
    > machines that are independent of their location in the connectivity
    > topology." They are doing it because they want to share their Internet
    > access with multiple computers.

Your take is not matched by what other people are saying, which is what I was
going on (but see below).

E.g. one person recently replied to a private message of mine (he can speak
for himself, if he wants), but the substance of what he said was that he
think that outside the US, almost everyone uses a NAT (not just homeowners
who want to hook up N computers when their always-on-ISP only gave them one
address), and he implied that addressing was a big issue (the example he gave
was of a university that didn't want to renumber again, after switching ISP's
once).

However, as the old aphorism goes, "the plural of anecdote is not data" - and
the situation may also have the usual statistics ("lies, damn lies, <etc>)
issues.

It may well be, for example, that the majority of NAT *boxes* sold go into
house applications where the intent is to share one address, but that a
relatively few very large NAT boxes (e.g. at companies) account for a larger
number of *users*.

I'd love to hear of some real data to sort this all out.

    > Have any of you looked at the actual marketing copy that sells real
    > people on why they might want to pay real money for a NAT box? It might
    > be instructive.

You really expect the marketing department to have clue? :-)

	Noel



From owner-ietf@ietf.org  Thu May  1 17:30:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12140;
	Thu, 1 May 2003 17:30:45 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BHVv-0004XW-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 13:06:31 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BHQc-0004Tp-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 13:01:02 -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 MAA22353
	for <ietf@ietf.org>; Thu, 1 May 2003 12:57:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BHP7-0003vG-00
	for ietf@ietf.org; Thu, 01 May 2003 12:59:29 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19BHP1-0003ub-00
	for ietf@ietf.org; Thu, 01 May 2003 12:59:23 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19BHNv-000E3i-00; Thu, 01 May 2003 11:58:15 -0500
Date: Thu, 01 May 2003 12:58:15 -0400
From: John C Klensin <john-ietf@jck.com>
To: Spencer Dawkins <spencer_dawkins@yahoo.com>
cc: "ipng@sunroof.eng.sun.com" <ipng@sunroof.eng.sun.com>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: My thoughts on local-use addresses
Message-ID: <187108337.1051793895@p3.JCK.COM>
In-Reply-To: <20030501044927.84860.qmail@web10902.mail.yahoo.com>
References:  <20030501044927.84860.qmail@web10902.mail.yahoo.com>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Wednesday, 30 April, 2003 21:49 -0700 Spencer Dawkins 
<spencer_dawkins@yahoo.com> wrote:

> Steve Deering had a nice set of slides in London about the
> horrible things that we were doing to "the wasp waist" (IP),
> but that doesn't mean that "wasp waists" don't have real
> advantages.
>
> We like to say in TSV that having applications handle
> congestion control is wrong because if 19 applications out of
> 20 do it correctly, the guy who hoses it up, hoses it for
> everyone.
>
> Although the potential for disaster on interface selection is
> limited, what we're trying to do isn't trivial, and the chances
> a stack can do a better job than a random application seem
> pretty large to me. I'd vote for Stephen's "latter".

Of course, there is an intermediate position (see my note of 
several days ago) in which we enable the applications to give 
the stack more information about the criteria on which it would 
like a selection to be made.  It is irrelevant in the "well, 
there are three addresses/topology locators/paths, but only one 
will connect" case.  But, if there are different addresses that 
can be used to establish connectivity, and, e.g., some are 
faster and higher cost while others are cheaper but are slower 
or involve more packet losses, the application is likely to be 
in a good position (with or without explicit user input) to know 
what will serve its needs best.

      john


> --- Stephen Sprunk <stephen@sprunk.org> wrote:
>>
>> Which is harder, having the stack give the app a list of
>> source and
>> destination addresses and then expect the app to figure out
>> which to use, or
>> have the stack attempt various combinations of source and
>> destination
>> addresses and just notify the application which one(s) worked?
>>
>> Something tells me the latter is both easier and more likely
>> to be
>> implemented correctly.
>







From owner-ietf@ietf.org  Thu May  1 17:31:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12214;
	Thu, 1 May 2003 17:31:23 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BLCj-0002bv-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 17:02:57 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BKaQ-0004Y6-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 16:23:22 -0400
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07833
	for <ietf@ietf.org>; Thu, 1 May 2003 16:19:51 -0400 (EDT)
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h41KMev15855;
        Thu, 1 May 2003 16:22:40 -0400 (EDT)
Date: Thu, 1 May 2003 16:22:40 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, cos@aaaaa.org, ietf@ietf.org
Subject: Re: what the "scope" disagreement is about
Message-Id: <20030501162240.5492a47d.moore@cs.utk.edu>
In-Reply-To: <088b01c3101b$351d4d20$261e4104@eagleswings>
References: <20030501143643.3c6418f7.moore@cs.utk.edu>
	<088b01c3101b$351d4d20$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > being able to distinguish an ambiguous address from a global 
> > address doesn't solve the problem of requiring hosts or apps 
> > to be aware of topology in order to make address selection.  
> 
> Ambiguity has nothing to do with the address selection problem here.

False.  It makes the address selection problem intractable.

> > > Making all labels global only works if the routing is in 
> > > fact globally flat.
> > 
> > It's worked in IPv4 for 20+ years.  What has been repeatedly 
> > shown to not work well is to try to route on non-global 
> > labels.  (anyone remember uucp mail or easynet?)
> 
> It has never worked for multi-homed systems when some of the
> participants in an app have a different view of the topology.

False, or at least an exaggeration.  Basically multi interface hosts
have worked just fine as long as the host had a distinguished address
which was reachable from each of its interfaces (whether via ARP or
routing or whatever), and that it consistently used as a source address
-- or more generally, as long as all of the addresses it used as
source addresses were routable from any of the nets to which it
connected (modulo access control), regardless of whether different
routing paths were available to different hosts.

What hasn't ever worked is requiring apps to know about routing
topology in order to successfully route packets to the destination,
where "successfully" might mean a variety of things ranging from "being
able to get the packets there at all" to "having those packets utilize
the high speed (and/or secure) link".

Note again that ambiguous addresses make this problem even harder to
solve, by changing the problem from "need more information to know
how to get there" to "can't even tell where 'there' is".

> > If we can agree on how to make the first 48 bits globally 
> > unique, does it really matter what values are assigned to the 
> > first 10 bits? That choice could be made strictly on the 
> > basis of compatibility issues with existing hosts, apps, and 
> > routers, once the other technical aspects of GUPIs had been 
> > worked out.
> 
> Which is one of my points. There have been several proposals offered
> to create probabilistically unique 38 bit values,

probabilistically unique doesn't cut it, because it's making
unreasonable assumptions about the size of the collision domain. 
remember, hosts don't have to communicate directly in order to cause a
collision between their identifiers within an application.

> that are compatible
> with shipping code that use that specific /10. In other words we have
> the technical means to take the ambiguity issue off the table. Getting
> rid of the shipping /10 doesn't accomplish the goal of removing
> ambiguity, it only delays getting there. 

the thing we should be doing is figuring out how to provide GUPIs,
not figuring out an excuse to keep using the SL prefix. 

> Your other issue about address selection doesn't go away. IPv6 nodes
> will have multiple addresses, therefore a list to select from.  

agreed, but we can minimize the degree to which the selection is
critical.

> With a distinguishing flag (upper 10 bits), it becomes possible for
> the processes that resolve names to topology locators in order to sort
> it out. 

wrong, because processes that resolve names have no idea about whether
such locators are valid in the scopes in which they will be used, much
less whether they are suitable for use by the applications.

> Without that flag there is no consistent way for that process
> to know. 

wrong.  the mere existence of this "flag" is what makes it impossible
for the app to know whether the address is valid.

> If that process is the end app (because it doesn't trust any
> other process to be fast or reliable enough), then the app needs to
> know the topology it explicitly intends to describe.

Now you're essentially arguing (without any supporting evidence) that
the network shouldn't have to know how to route packets beyond the local
link.

Keith



From owner-ietf@ietf.org  Thu May  1 17:31:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12225;
	Thu, 1 May 2003 17:31:24 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BLCe-0002Y1-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 17:02:52 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BKOP-0003G8-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 16:10:57 -0400
Received: from turing-police.cc.vt.edu (turing-police.cc.vt.edu [128.173.14.107])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06583
	for <ietf@ietf.org>; Thu, 1 May 2003 16:07:06 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h41JOQxj006990;
	Thu, 1 May 2003 15:24:26 -0400
Message-Id: <200305011924.h41JOQxj006990@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Keith Moore <moore@cs.utk.edu>
Cc: alh-ietf@tndh.net, cos@aaaaa.org, ietf@ietf.org
Subject: Re: what the "scope" disagreement is about 
In-Reply-To: Your message of "Thu, 01 May 2003 14:36:43 EDT."
             <20030501143643.3c6418f7.moore@cs.utk.edu> 
References: <20030430225812.481e47f4.moore@cs.utk.edu> <086301c31009$d3251a00$261e4104@eagleswings>
            <20030501143643.3c6418f7.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1220418075P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 01 May 2003 15:24:25 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_1220418075P
Content-Type: text/plain; charset=us-ascii

On Thu, 01 May 2003 14:36:43 EDT, Keith Moore said:

> It's worked in IPv4 for 20+ years.  What has been repeatedly shown to
> not work well is to try to route on non-global labels.  (anyone remember
> uucp mail or easynet?)

Compare-and-contrast "pathalias" and BGP's AS-path.  Include discussion
of out-of-band information needed in both cases. ;)


--==_Exmh_1220418075P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+sXRpcC3lWbTT17ARAqbkAJ9FA9SMQGhdnskcfItlRkvMe7r7IACgxkiN
OA55c/YTkLnBEfFGqy6/LOo=
=1Oos
-----END PGP SIGNATURE-----

--==_Exmh_1220418075P--



From owner-ietf@ietf.org  Thu May  1 17:41:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12875;
	Thu, 1 May 2003 17:41:50 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BLCm-0002eb-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 17:03:00 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BKox-0000L3-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 16:38:23 -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 QAA09532
	for <ietf@ietf.org>; Thu, 1 May 2003 16:34:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BKnf-0006Sg-00
	for ietf@ietf.org; Thu, 01 May 2003 16:37:03 -0400
Received: from krusty-motorsports.com ([192.94.170.8] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19BKnZ-0006SC-00
	for ietf@ietf.org; Thu, 01 May 2003 16:36:57 -0400
Received: from [24.194.112.77] (helo=skipper.averillpark.net)
	by krusty-motorsports.com with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.14)
	id 19BKnR-0001zL-TA
	for ietf@ietf.org; Thu, 01 May 2003 20:36:49 +0000
Received: from rwelty by skipper.averillpark.net with local (Exim 4.14)
	id 19BKlS-0007Zh-SB
	for ietf@ietf.org; Thu, 01 May 2003 16:34:46 -0400
Date: Thu, 1 May 2003 16:34:46 -0400 (EDT)
From: Richard Welty <rwelty@averillpark.net>
Subject: Re[2]: My thoughts on local-use addresses
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Disposition: INLINE
References: <200305011525.h41FPOkm018023@ginger.lcs.mit.edu>
In-Reply-To: <200305011525.h41FPOkm018023@ginger.lcs.mit.edu>
X-Mailer: Mahogany 0.64 'Sparc', compiled for Linux 2.4.9-13 i686
Message-Id: <E19BKlS-0007Zh-SB@skipper.averillpark.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 1 May 2003 11:25:24 -0400 "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu> wrote:
>     > Have any of you looked at the actual marketing copy that sells real
>     > people on why they might want to pay real money for a NAT box? It
> might
>     > be instructive.
 
> You really expect the marketing department to have clue? :-)

no one expects the marketing department to have even been in the same
room as a clue.

but you're misunderstanding his point. the consumers buying the product
read the box and a significant percentage of them are foolish enough to
believe what the box tells them. one of the big selling points in the
on-box marketing gibberish are foolish claims that NAT is a security
device, and some devices actually claim to be firewalls even though the
only thing that passes for security in them is the port NAT.

richard
--
Richard Welty                                         rwelty@averillpark.net
Averill Park Networking                                         518-573-7592
              Unix, Linux, IP Network Engineering, Security





From owner-ietf@ietf.org  Thu May  1 17:46:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13114;
	Thu, 1 May 2003 17:46:40 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BLdn-00044S-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 17:30:55 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BL9e-0002Us-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 16:59:46 -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 QAA10809
	for <ietf@ietf.org>; Thu, 1 May 2003 16:56:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BL8L-0006nr-00
	for ietf@ietf.org; Thu, 01 May 2003 16:58:25 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BL8F-0006lc-00
	for ietf@ietf.org; Thu, 01 May 2003 16:58:19 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h41Ksvv16007;
        Thu, 1 May 2003 16:54:58 -0400 (EDT)
Date: Thu, 1 May 2003 16:54:57 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Stephen Sprunk" <stephen@sprunk.org>
Cc: moore@cs.utk.edu, Valdis.Kletnieks@vt.edu, alh-ietf@tndh.net,
        mrw@windriver.com, mat@cisco.com, randy@psg.com, cos@aaaaa.org,
        ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: site-local != NAT
Message-Id: <20030501165457.55ad6555.moore@cs.utk.edu>
In-Reply-To: <000801c31023$818f5560$93b58742@ssprunk>
References: <07f301c30f6b$87a28c00$261e4104@eagleswings>
	<200305011608.h41G8Dxj004081@turing-police.cc.vt.edu>
	<000801c31023$818f5560$93b58742@ssprunk>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> There is no inherent requirement that SL addresses be ambiguous, and
> there are several drafts out there on how to ensure they're not. 

for that matter, there's no inherent requirement that there be any 
set of addresses that is defined in the architecture to be filtered at
some arbitrary boundary.  in other words, there's no inherent
requirement for SLs at all.  

Keith



From owner-ietf@ietf.org  Thu May  1 17:46:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13118;
	Thu, 1 May 2003 17:46:40 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BLcn-000426-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 17:29:53 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BL4X-0001fP-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 16:54:29 -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 QAA10447
	for <ietf@ietf.org>; Thu, 1 May 2003 16:50:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BL2k-0006hq-00
	for ietf@ietf.org; Thu, 01 May 2003 16:52:38 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19BL2f-0006h2-00
	for ietf@ietf.org; Thu, 01 May 2003 16:52:33 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h41KppL15747;
	Thu, 1 May 2003 15:51:52 -0500
Message-ID: <000801c31023$818f5560$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: <Valdis.Kletnieks@vt.edu>, <alh-ietf@tndh.net>
Cc: "'Margaret Wasserman'" <mrw@windriver.com>,
        "'Michael Thomas'" <mat@cisco.com>, "'Randy Bush'" <randy@psg.com>,
        "'Keith Moore'" <moore@cs.utk.edu>, <cos@aaaaa.org>, <ietf@ietf.org>,
        <ipng@sunroof.eng.sun.com>
References: <07f301c30f6b$87a28c00$261e4104@eagleswings> <200305011608.h41G8Dxj004081@turing-police.cc.vt.edu>
Subject: Re: site-local != NAT 
Date: Thu, 1 May 2003 15:48:28 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

[ Note to all:  can we please take all of these IPv6 threads off the main
IETF list?  Anyone interested can join the IPNG list ]

Thus spake <Valdis.Kletnieks@vt.edu>
> Right - and the entire problem with "site local" addresses is that they
> are almost by definition ambiguous if they ever escape.  The host
> sending the opaque blob has no a priori way of knowing if the blob
> will be in the *right* scope when you get there.

So if what we call a "site local" address is always unique, even between
sites, that would pacify you?

There is no inherent requirement that SL addresses be ambiguous, and there
are several drafts out there on how to ensure they're not.  "Site local"
just means the address is only _reachable_ from its local site.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Thu May  1 17:47:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13229;
	Thu, 1 May 2003 17:47:45 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BLqe-0005fk-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 17:44:12 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BLDd-0002fI-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 17:03:53 -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 RAA10993
	for <ietf@ietf.org>; Thu, 1 May 2003 17:00:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BLCK-0006py-00
	for ietf@ietf.org; Thu, 01 May 2003 17:02:32 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19BLCE-0006pm-00
	for ietf@ietf.org; Thu, 01 May 2003 17:02:26 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h41L2mL16073;
	Thu, 1 May 2003 16:02:48 -0500
Message-ID: <004001c31025$08661cd0$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Keith Moore" <moore@cs.utk.edu>, <alh-ietf@tndh.net>
Cc: <moore@cs.utk.edu>, <cos@aaaaa.org>, <ietf@ietf.org>,
        <ipng@sunroof.eng.sun.com>
References: <20030430225812.481e47f4.moore@cs.utk.edu><086301c31009$d3251a00$261e4104@eagleswings> <20030501143643.3c6418f7.moore@cs.utk.edu>
Subject: Re: what the "scope" disagreement is about
Date: Thu, 1 May 2003 15:58:25 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Keith Moore" <moore@cs.utk.edu>
> being able to distinguish an ambiguous address from a global address
> doesn't solve the problem of requiring hosts or apps to be aware of
> topology in order to make address selection.

A host/app needs to be similarly aware of topology (and security policy) to
make any reasonable selection between multiple global addresses.  Adding
non-globals to the mix doesn't make things significantly worse.

> > Yes, we need to complete the work on making the 38 bits globally
> > unique, but that can't happen if we start by eliminating the first 10.
>
> If we can agree on how to make the first 48 bits globally unique, does
> it really matter what values are assigned to the first 10 bits?

Yes, it does.  Having a common prefix for non-global addresses makes the job
of network managers much simpler, and thus reduces the likelihood of leaks.
Does it need to be a 10-bit prefix?  Not really, but FEC0::/10 is already
there.

> (yes, GUPIs, NOT SLs.  they WILL be routed between sites, for good
> reasons, and we shouldn't try to stop this)

Since this is the first time I've seen "GUPI" used, should I assume that
means a globally unique provider-independent prefix which isn't globally
routed?  If so, I think you're using that term in the same sense Tony uses
SL.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Thu May  1 17:56:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13824;
	Thu, 1 May 2003 17:56:45 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BLqf-0005fs-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 17:44:13 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BLEv-0002fZ-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 17:05:13 -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 RAA11044
	for <ietf@ietf.org>; Thu, 1 May 2003 17:01:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BLDO-0006qx-00
	for ietf@ietf.org; Thu, 01 May 2003 17:03:38 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BLDI-0006pz-00
	for ietf@ietf.org; Thu, 01 May 2003 17:03:32 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h41L3AtU019685;
	Thu, 1 May 2003 17:03:10 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h41L39Y7019684;
	Thu, 1 May 2003 17:03:09 -0400
Date: Thu, 1 May 2003 17:03:09 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200305012103.h41L39Y7019684@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: My thoughts on local-use addresses
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: Keith Moore <moore@cs.utk.edu>

    > I doubt that a significant percentage of users think in terms of
    > "want[ing] identifiers for their machines that are independent of their
    > location in the connectivity topology". You and I think that way

If they think "I want a NAT box so I can change ISP's", then I would say that
my formulation is indeed what they are thinking, although you're surely right
that they don't put it in those terms (just as the average person filling
their gas tank doesn't think "I'm loading in some energy stored in chemical
form, for later conversion to kinetic and potential energy").


    >> Clearly, you can't have a single label which is both
    >> location-independent (so it's provider independent) and
    >> location-dependent (so that the routing works).
 
    > It depends on what you mean by "routing".

The collection of mechanisms which establish paths, and cause packets to
travel along those paths.

    > Users don't care about the mechanism for how those packets get there
    > .. If the packets had to get redirected from a location-independent
    > address to a location-dependent address, that would be fine with users
    > as long as that operation happened quickly and reliably enough to suit
    > the users' apps. 

In which case you'd no longer have a "single label", but rather two, with a
mapping in between.

    > but I don't think it's a matter of "clearly, you can't" do this.

I see no reason here to modify my statement.

	Noel



From owner-ietf@ietf.org  Thu May  1 18:13:31 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15446;
	Thu, 1 May 2003 18:13:31 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BLqh-0005gi-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 17:44:15 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BLKb-0002kM-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 17:11:05 -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 RAA11189
	for <ietf@ietf.org>; Thu, 1 May 2003 17:07:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BLJI-0006t2-00
	for ietf@ietf.org; Thu, 01 May 2003 17:09:44 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19BLJC-0006sw-00
	for ietf@ietf.org; Thu, 01 May 2003 17:09:38 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26E3E> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 01 May 2003 14:09:53 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Keith Moore'" <moore@cs.utk.edu>
Cc: <cos@aaaaa.org>, <ietf@ietf.org>
Subject: RE: what the "scope" disagreement is about
Date: Thu, 1 May 2003 14:09:53 -0700
Message-ID: <08f401c31026$02cae980$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030501162240.5492a47d.moore@cs.utk.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA15446

Keith Moore wrote:
> ...
> > Which is one of my points. There have been several 
> proposals offered 
> > to create probabilistically unique 38 bit values,
> 
> probabilistically unique doesn't cut it, because it's making 
> unreasonable assumptions about the size of the collision domain. 
> remember, hosts don't have to communicate directly in order 
> to cause a collision between their identifiers within an application.

In other words, I was incomplete earlier. We are required to have a
single flat global routing domain, with the additional policy constraint
that only a single organization is allowed to inject a given value.
Otherwise every address is probabilistically unique. How do you know
that someone is not injecting 8/8 into routing today, and confusing some
poor soul (or just hijacking the space) in a remote corner of the net?
Given the current technology, we probably need the additional policy
constraint that any given value is only allowed to appear at a single
location, else we can't be sure it is really the authorized originator.

> 
> > that are compatible
> > with shipping code that use that specific /10. In other 
> words we have 
> > the technical means to take the ambiguity issue off the 
> table. Getting 
> > rid of the shipping /10 doesn't accomplish the goal of removing 
> > ambiguity, it only delays getting there.
> 
> the thing we should be doing is figuring out how to provide 
> GUPIs, not figuring out an excuse to keep using the SL prefix. 

No excuses, the existence and use in shipping code of a particular /10
is not preventing progress on uniqueness. 

> 
> > Your other issue about address selection doesn't go away. 
> IPv6 nodes 
> > will have multiple addresses, therefore a list to select from.
> 
> agreed, but we can minimize the degree to which the selection 
> is critical.
> 
> > With a distinguishing flag (upper 10 bits), it becomes possible for 
> > the processes that resolve names to topology locators in 
> order to sort 
> > it out.
> 
> wrong, because processes that resolve names have no idea 
> about whether such locators are valid in the scopes in which 
> they will be used, much less whether they are suitable for 
> use by the applications.
> 
> > Without that flag there is no consistent way for that 
> process to know.
> 
> wrong.  the mere existence of this "flag" is what makes it 
> impossible for the app to know whether the address is valid.
> 
> > If that process is the end app (because it doesn't trust any other 
> > process to be fast or reliable enough), then the app needs 
> to know the 
> > topology it explicitly intends to describe.
> 
> Now you're essentially arguing (without any supporting 
> evidence) that the network shouldn't have to know how to 
> route packets beyond the local link.

You have argued yourself in a full circle. You agree that the address
selection issues don't go away, then turn around and say that the
existence of a tool for distinguishing which on the list are least
likely to work for global purposes makes it impossible for apps to
choose, and end up back at the point of an app can't pass around data
that it intends for the receiver to use as topology data unless it
understands the topology. In fact the local router may not know how to
get some packets off the local link if a network manager has limited the
routing information available to that router. This is not broken, it is
the reality that global routing is not a single flat space. 

Tony





From owner-ietf@ietf.org  Thu May  1 18:17:39 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15794;
	Thu, 1 May 2003 18:17:39 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BLuF-0006JR-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 17:47:55 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BLhJ-0004Iy-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 17:34:33 -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 RAA12150
	for <ietf@ietf.org>; Thu, 1 May 2003 17:30:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BLfl-000745-00
	for ietf@ietf.org; Thu, 01 May 2003 17:32:57 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BLfg-00073s-00
	for ietf@ietf.org; Thu, 01 May 2003 17:32:52 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h41LXFv16473;
        Thu, 1 May 2003 17:33:15 -0400 (EDT)
Date: Thu, 1 May 2003 17:33:15 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Stephen Sprunk" <stephen@sprunk.org>
Cc: moore@cs.utk.edu, alh-ietf@tndh.net, cos@aaaaa.org, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: what the "scope" disagreement is about
Message-Id: <20030501173315.6daa9fec.moore@cs.utk.edu>
In-Reply-To: <004001c31025$08661cd0$93b58742@ssprunk>
References: <20030430225812.481e47f4.moore@cs.utk.edu>
	<086301c31009$d3251a00$261e4104@eagleswings>
	<20030501143643.3c6418f7.moore@cs.utk.edu>
	<004001c31025$08661cd0$93b58742@ssprunk>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Thu, 1 May 2003 15:58:25 -0500
"Stephen Sprunk" <stephen@sprunk.org> wrote:

> Thus spake "Keith Moore" <moore@cs.utk.edu>
> > being able to distinguish an ambiguous address from a global address
> > doesn't solve the problem of requiring hosts or apps to be aware of
> > topology in order to make address selection.
> 
> A host/app needs to be similarly aware of topology (and security
> policy) to make any reasonable selection between multiple global
> addresses. 

agree.

> Adding non-globals to the mix doesn't make things significantly worse.

Disagree.  First, it immediately reduces the available choices, and
thus, the potential for poor choices (since SLs are more often poor
choices than not). Second, it pushes the burden of routing back into the
network where it belongs.  Third, while it's possible (though
unattractive) for the network to supply some topology information
to hosts in a world where identifiers for points in the topology are all
are taken from the same name space, having ambiguous addresses makes
this completely infeasible.

> > If we can agree on how to make the first 48 bits globally unique,
> > does it really matter what values are assigned to the first 10 bits?
> 
> Yes, it does.  Having a common prefix for non-global addresses makes
> the job of network managers much simpler

Not clear; since it doesn't necessarily give them the flexibility they
need.  The idea that a network has only one boundary of interest is
of fairly limited applicability; it's certainly not something that is
general enough to be wired into the addressing architecture.

however, I was referring specifically to the prefix FEC0://10.  Yes,
it's already allocated, but it's also defined in such a way as to be
dysfunctional, and too many broken assumptions are wired into existing
code.  So for the sake of compatibility it seems better to allocate
another prefix for GUPIs.

> > (yes, GUPIs, NOT SLs.  they WILL be routed between sites, for good
> > reasons, and we shouldn't try to stop this)
> 
> Since this is the first time I've seen "GUPI" used, should I assume
> that means a globally unique provider-independent prefix which isn't
> globally routed? 

yes.

> If so, I think you're using that term in the same sense Tony uses SL.

IMHO, they shouldn't have any "site" or filtering assumptions wired into
them, they're just a set of prefixes that are not dependent on a
provider and can't be assumed to be globally routable.  But to make
them work we'll need a way to transparently map/forward them to routable
prefixes.

Keith



From owner-ietf@ietf.org  Thu May  1 18:21:13 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16048;
	Thu, 1 May 2003 18:21:13 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BLuH-0006LD-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 17:47:57 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BLio-00051F-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 17:36:06 -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 RAA12312
	for <ietf@ietf.org>; Thu, 1 May 2003 17:32:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BLh1-00075g-00
	for ietf@ietf.org; Thu, 01 May 2003 17:34:15 -0400
Received: from pop018pub.verizon.net ([206.46.170.212] helo=pop018.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19BLgv-00073y-00
	for ietf@ietf.org; Thu, 01 May 2003 17:34:09 -0400
Received: from earthlink.com ([4.65.81.124]) by pop018.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030501213328.TPXL17739.pop018.verizon.net@earthlink.com>;
          Thu, 1 May 2003 16:33:28 -0500
Message-ID: <3EB191BD.2012F491@earthlink.com>
Date: Thu, 01 May 2003 14:29:33 -0700
From: Peter Deutsch <pdeutsch@earthlink.com>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
CC: ietf@ietf.org
Subject: Re: My thoughts on local-use addresses
References: <200305011525.h41FPOkm018023@ginger.lcs.mit.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at pop018.verizon.net from [4.65.81.124] at Thu, 1 May 2003 16:33:28 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

g'day,

"J. Noel Chiappa" wrote:
>     > From: james woodyatt <jhw@wetware.com>
...
>     > They are *not* doing it because they "want identifiers for their
>     > machines that are independent of their location in the connectivity
>     > topology." They are doing it because they want to share their Internet
>     > access with multiple computers.
> 
> Your take is not matched by what other people are saying, which is what I was
> going on (but see below).
...
> I'd love to hear of some real data to sort this all out.

I'm with you, although there does seem to be a school of thought here
that says that because its violates the end-to-end principle, it doesn't
matter how many people are doing it. In other words "it's wrong, even if
the duck enjoys it..."

Which leads me to my latest heretical thought - given the amount of
energy being expended to unsuccessfully figure out how to make the
end-to-end axiom coexist with today's Internet, how bad would it be to
spend some time reexamining that particular axiom? Suppose rather than
listing the apps that break when addresses are NATed, and using this
list as a reason to not change things, we use that list as a starting
point to examine ways to fix them?  Everyone seems to think the problem
is not intractible, but we can't get there from here because we seem to
have a built-in conflict with our starting assumptions. So, for example,
rather than take "end-to-end" to mean "host-to-host", what happens if we
postulate it to mean "first router to last router"? What if we
postulated a hierarchy of identifiers across a network?

As you pointed out earlier, folks talked about separating out the end
point identifier in the past, maybe we should reexamine this suggesion
in light of today's impasse? Maybe what we really need here is to change
one of the axioms and see if it takes us to a non-Euclidian geometric
space?

Nah, let's just continue trying to square the circle....

This whole debate is starting to remind me of the Quebec comedian who
parodied that province's separatists as wanting "an independent Quebec
within a strong and united Canada". Personally, I wont rest until I have
ephemeral, easily changed end point identifiers that are stable and
permanent!


				- peterd



-- 

---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software


  "It is inhumane, in my opinion, to force people who have a
   genuine medical need for coffee to wait in line behind people
   who apparently view it as some kind of recreational activity."

                                        -- Dave Barry

---------------------------------------------------------------------



From owner-ietf@ietf.org  Thu May  1 18:21:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12215;
	Thu, 1 May 2003 17:31:24 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BL5s-0001iW-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 16:55:52 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BK8i-0000Lc-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 15:54:44 -0400
Received: from tndh.net (evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net [4.65.19.240])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05142
	for <ietf@ietf.org>; Thu, 1 May 2003 15:51:13 -0400 (EDT)
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26E08> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 01 May 2003 12:52:33 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Keith Moore'" <moore@cs.utk.edu>
Cc: <cos@aaaaa.org>, <ietf@ietf.org>
Subject: RE: what the "scope" disagreement is about
Date: Thu, 1 May 2003 12:52:33 -0700
Message-ID: <088b01c3101b$351d4d20$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030501143643.3c6418f7.moore@cs.utk.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA12215

Keith Moore wrote:
> > > ... Finally, if you want
> > > any app - even this "special" app, to be aware of topology, 
> > > then the first thing you need is globally scoped labels for 
> > > points in the topology - which is exactly what exposing site 
> > > locals to applications denies you.
> > 
> > What ???  Yes we need a way to differentiate them, but 
> eliminating the 
> > local one doesn't accomplish that. The labels FEC0::/10 vs. 2::/3 
> > provide exactly the scoping differentiator this statement claims to 
> > need.
> 
> being able to distinguish an ambiguous address from a global 
> address doesn't solve the problem of requiring hosts or apps 
> to be aware of topology in order to make address selection.  

Ambiguity has nothing to do with the address selection problem here.
More below.

> the problem here is that an SL address is ambiguous in almost 
> any context outside of an RA or IP header; so there's simply 
> no way to be confident that a particular SL belongs to a 
> particular section of the network. 
> 
> ambiguous addresses are both the factor that would force 
> hosts and apps to be more aware of topology AND the factor 
> that make it intractable for hosts and apps to be aware of 
> topology.  Not only do they cause this problem, they preclude 
> any solution to the problem.
> 
> > Making all labels global only works if the routing is in 
> fact globally 
> > flat.
> 
> It's worked in IPv4 for 20+ years.  What has been repeatedly 
> shown to not work well is to try to route on non-global 
> labels.  (anyone remember uucp mail or easynet?)

It has never worked for multi-homed systems when some of the
participants in an app have a different view of the topology.

> 
> > Yes, we need to complete the work on
> > making the 38 bits globally unique, but that can't happen 
> if we start 
> > by eliminating the first 10.
> 
> If we can agree on how to make the first 48 bits globally 
> unique, does it really matter what values are assigned to the 
> first 10 bits? That choice could be made strictly on the 
> basis of compatibility issues with existing hosts, apps, and 
> routers, once the other technical aspects of GUPIs had been 
> worked out.

Which is one of my points. There have been several proposals offered to
create probabilistically unique 38 bit values, that are compatible with
shipping code that use that specific /10. In other words we have the
technical means to take the ambiguity issue off the table. Getting rid
of the shipping /10 doesn't accomplish the goal of removing ambiguity,
it only delays getting there. 

Your other issue about address selection doesn't go away. IPv6 nodes
will have multiple addresses, therefore a list to select from. With a
distinguishing flag (upper 10 bits), it becomes possible for the
processes that resolve names to topology locators in order to sort it
out. Without that flag there is no consistent way for that process to
know. If that process is the end app (because it doesn't trust any other
process to be fast or reliable enough), then the app needs to know the
topology it explicitly intends to describe. If the app doesn't want to
learn topology, it must choose to hand the task off to a process with
the means to figure it out. The current DNS is not up to the task, so it
either needs to be fixed, or a replacement defined that actually
addresses the issue here.

Tony




From owner-ietf@ietf.org  Thu May  1 18:27:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16357;
	Thu, 1 May 2003 18:27:47 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BMSO-00077H-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 18:23:12 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BM0G-0007en-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 17:54:08 -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 RAA13485
	for <ietf@ietf.org>; Thu, 1 May 2003 17:50:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BLyw-0007Jg-00
	for ietf@ietf.org; Thu, 01 May 2003 17:52:46 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BLyr-0007Jd-00
	for ietf@ietf.org; Thu, 01 May 2003 17:52:41 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h41LrAv16697;
        Thu, 1 May 2003 17:53:11 -0400 (EDT)
Date: Thu, 1 May 2003 17:53:10 -0400
From: Keith Moore <moore@cs.utk.edu>
To: John C Klensin <john@jck.com>
Cc: moore@cs.utk.edu, jnc@ginger.lcs.mit.edu, ietf@ietf.org
Subject: Re: My thoughts on local-use addresses
Message-Id: <20030501175310.7afdfde5.moore@cs.utk.edu>
In-Reply-To: <202205796.1051808993@p3.JCK.COM>
References: <200305011037.h41AbGYs016930@ginger.lcs.mit.edu>
	<20030501151234.455a6707.moore@cs.utk.edu>
	<202205796.1051808993@p3.JCK.COM>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> in  many enterprise/organizational situations, and at least some 
> home networking ones, communication among hosts on the local 
> network is very important, perhaps equally important as 
> communication with outside hosts.  

I didn't claim otherwise; in fact I suspect that internal communication
is often viewed as more important than external communication.  However,
what I said was  "users don't *just* care about local apps" (emphasis
added).  Which, for instance, is why there is a demand for ALGs in NATs.

> Now, in the IPv6 "multiple addresses per host" model, it would 
> make perfect sense to assign every host on such a subnet an 
> address that was specific to that subnet (or enterprise) and, 
> for those hosts that needed external accessibility, an 
> additional, presumably globally-routable, address. 

It might seem to make perfect sense at first glance, but I'm not sure
that it holds up under analysis.  First, as long as hosts are free to
assign their own addresses, using DHCP (or RA) as a means of access
control to external links doesn't seem very robust.  Second, the
design decision to use multiple prefixes has consequences for
applications that are almost certainly unintended and undesirable.

Now having a set of addresses that are stable across provider changes
really does seem useful, but I see no inherent reason that such
addresses should be only unique (or valid) within the local network. 


> > Lots of good ideas got passed over in the IPng discussion.
> > Despite that, I think that IPv6 ended up "about right" -
> > modulo a few warts like A6 and SL and over-reliance on address
> > selection.  By "about right" I mean that I think that if the
> > warts are fixed it will become feasible to gracefully extend
> > the IPv6 architecture in useful ways - such as to provide the
> > capability to use identifiers rather than locators - without
> > invalidating hosts or apps that were written to the basic IPv6
> > model.
> 
> Keith, I think I agree with you about the "despite that" part of 
> the above (I certainly agree about the "passed over" part). 
> However, if our confusion about how to best handle multiple 
> addresses per host, and where to do so, results in our moving to 
> a "one host, one address" model and a flat, IP-level, address 
> space, I think some of the "graceful extension" potential will 
> disappear.  Indeed, if we go down that path --which I think you 
> have been advocating, although I'm not sure-- I suspect that we 
> had better have a general routing solution that is not dependent 
> on address aggregation before we move much further forward with 
> IPv6 deployment.

Frankly I don't know where this needs end up.  I don't think it ends up
with a purely "one host, one address" model, for a variety of reasons. I
do think it might end up with a model where there are "distinguished
addresses" (or if you prefer, identifiers) for hosts that are generally 
preferred over other addresses or identifiers, but can be automatically
forwarded and/or mapped to locators that can be routed by traditional
means.

I'm looking at various ways of doing this, some of which involve
site-relative locators and some of which don't.  So far I haven't seen a
case wehre relative locators are required.  They can make certain cases
easier- particularly isolated newtorks.  But they seem to make the
overall solution more complex and less robust, even when they're not
exposed to applications.  

I'm still working on understanding this landscape, so I might find a
compelling case for site-relative locators.  But I suspect not.

Keith



From owner-ietf@ietf.org  Thu May  1 18:52:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17383;
	Thu, 1 May 2003 18:52:48 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BIS6-000554-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 14:06:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BIIQ-0004yD-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 13:56:38 -0400
Received: from tndh.net (evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net [4.65.19.240])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25116
	for <ietf@ietf.org>; Thu, 1 May 2003 13:53:07 -0400 (EDT)
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26DB2> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 01 May 2003 10:47:56 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Thomas Narten'" <narten@us.ibm.com>,
        "'Erik Nordmark'" <Erik.Nordmark@Sun.COM>
Cc: <ipng@sunroof.eng.sun.com>, <ietf@ietf.org>
Subject: My point about the ambiguity of the question
Date: Thu, 1 May 2003 10:47:55 -0700
Message-ID: <086001c31009$cc4e9d00$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA17383

Thomas & Erik,

These notes illustrate my point about the ambiguity of the question. 

First, one has to question how well Ted and others were informed if
their issue is all about ambiguity. We have several proposals to remove
the ambiguity in the FEC0::/10 prefix that are compatible with existing
implementations, so were their votes really about completing that work
to remove ambiguity? If so, deprecating the prefix would not be a step
toward completing that.

But to my point. As the second note shows, part of the goal of some
votes is to disallow a network manager the ability to limit access or
visibility to some of their nodes. The IETF is not in the role of
designing networks, and limiting access and visibility is an operational
issue that the IETF doesn't get to decide. 

The question was ambiguous. Individual interpretations of the outcome
drove YES votes for architecturally divergent goals, some of which are
not in the IETFs purview to decide.

Tony



Theodore Ts'o wrote:
> I certainly agree that it's all about ambiguous addresses and 
> not about about reachability.  And it's why I have to agree 
> with Keith that Site Local addresses are a bad idea, and why 
> ditching them is absolutely the right thing.


Keith Moore wrote:
> > My point was that there are topology locators that are only viable 
> > within a scope defined by the local network manager.
> 
> yes, we know this.  it's a bad idea, and we need to stop 
> pretending it's a legitimate thing to do.  that way, when the 
> network manager does this, it's his fault when things break.
> 
> network managers do have legitimate needs that must be 
> respected. this is not one of them.




From owner-ietf@ietf.org  Thu May  1 22:56:41 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22922;
	Thu, 1 May 2003 22:56:41 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BQaa-0001Mw-00
	for ietf-list@ran.ietf.org; Thu, 01 May 2003 22:47:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BQZz-0001HD-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 22:47:19 -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 WAA22650
	for <ietf@ietf.org>; Thu, 1 May 2003 22:41:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BQWq-0001RQ-00
	for ietf@ietf.org; Thu, 01 May 2003 22:44:04 -0400
Received: from thunk.org ([140.239.227.29] helo=thunker.thunk.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19BQWg-0001RC-00
	for ietf@ietf.org; Thu, 01 May 2003 22:43:54 -0400
Received: from [216.175.175.162] (helo=think.thunk.org)
	authenticated as tytso by thunker.thunk.org with asmtp 
	(tls_cipher TLSv1:DES-CBC3-SHA:168) 
	(tls_peerdn /C=US/ST=Massachusetts/L=Medford/O=Thunking Systems/OU=SMTP-client/CN=think.thunk.org/Email=tytso@thunk.org)
	 (Exim 3.35 #1 (Debian))
	id 19BQWo-000607-00; Thu, 01 May 2003 22:44:03 -0400
Received: from tytso authenticated as tytso by think.thunk.org with local   (Exim 3.35 #1 (Debian))
	id 19BQXr-0000Ra-00; Thu, 01 May 2003 22:45:07 -0400
Date: Thu, 1 May 2003 22:45:07 -0400
From: "Theodore Ts'o" <tytso@mit.edu>
To: Tony Hain <alh-ietf@tndh.net>
Cc: "'Ofer Inbar'" <cos@aaaaa.org>, ietf@ietf.org
Subject: Re: what the "scope" disagreement is about
Message-ID: <20030502024507.GB1649@think>
References: <20030501120516.GA5120@think> <086201c31009$d0b356b0$261e4104@eagleswings>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <086201c31009$d0b356b0$261e4104@eagleswings>
User-Agent: Mutt/1.5.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, May 01, 2003 at 10:48:03AM -0700, Tony Hain wrote:
> 
> The market demand is for stable addresses that can be routed globally.
> That does not mean that the network manager wants to globally route
> every prefix.

No, but stable address that can be routed globally satifies the goal
having an address which can be passed from B to C and still be used to
reach A.   That was my point.

> > One solution for that would be to not do multihoming, and 
> > simply have servers live on multiple IP addresses belonging 
> > to multiple ISP's, and use multiple DNS 'A' records in order 
> > to provide reachability.  I suspect that would be Tony's 
> > solution about what we should be doing today. 
> 
> That scenario is inconsistent. You start with 'not do multihoming', but
> then describe multihomed servers. 

I'm saying that's what people want in the real world.   

It seems to me that you have this alternate solution which requires
using the DNS instead.  But given the choice between forcing
applications to be rewritten, or leaning on the ISP's to provide
globally routable, provider-independent addresses that *can* be passed
from B to C and used to reach A, we know what network managers have
done, successfully --- they lean on their ISP's.

> > It's certainly true that having a reliable end-point 
> > identifier is critical.  But I don't think the DNS is it. 
> 
> One of my points awhile back was that the current DNS is not up to the
> task, and neither are the other name resolution services. Those need to
> be addressed at the same time as the applications that insist in doing
> the work for themselves.

... and your solution is that IPv6 shouldn't do any of this work?
Make the the application writers modify all of their protocols and
implementations, as well as forcing the DNS to retool?  No wonder your
proposed solution is so popular.  :-)

> > This is why I believe that ultimately 8+8 is the most 
> > interesting approach.  As the old saw goes, "there is no 
> > problem in computer science that cannot be solved by adding 
> > an additional level of indirection".  
> 
> 8+8 and similar schemes suffer one of the same problems you are
> complaining about. To make them work, the network needs a very fast
> converging, global, identifier to locator mapping service. 

Yes, but at the same time it is no *more* work than that which is
required by your scheme.  Regardless of whether we put this work all
on the shoulders of the DNS and application folks, we still need to
have to provide the same solution.  So your scheme of forcing the DNS
to do all of this work isn't any easier.

> Mangling the address field in the packet only allows the app to use
> part of the address for the identifier. There is no reason that the
> identifier has to be part of the address.

Yes, applications would have to be changed to recognize that only part
of the "IPv6 address" is useful as the identifier.  But I suspect when
you compare the utility of a fixed-length identifier which is
guaranteed to be unique, as opposed to a variable-length,
often-inconsistent user-provided string,the fixed-length identifier
will be considered much superior.

The bottom line is that in order to solve the problem right, I think
everyone will have to make some changes.  Perhaps part of the problem
here is that **everyone** has been saying, "my part of the stack is
perfect --- everything else in the stack needs to change in order to
accomodate *me*".  For example, saying that nothing needs to change in
IPv6, but rather the IESG must force the DNS direct to do all sorts of
things, and that application writers must be forced to make all sorts
of changes to conform to a particular architecture, might not
necessarily been the course of success.  In fact, it probably would
just cause a general consensus to deprecate site-local addresses.  :-)

> The problem will not be solved by PI addressing. I don't care if apps
> pass around addresses, as long as they are doing the work to make sure
> the address is consistent with the topology the app is intentionally
> describing. If the app is not going to learn about topology (and I agree
> the app shouldn't) it needs to rely on a service that has the means to
> do the job. We agree, the current DNS is not up to the task. 

What if applications pass around a fixed-length identifier which they
consider to be a globally unique "address", and the IP layer contacted
some locator server (to be defined) a routable entity which it
considers an "address"?  It's the same pieces which you outlined; it's
just simply a matter of factoring the pieces slightly different, and
recognizing that there is only one IP layer, and many applications.
So modifying the IP layer to make use of the locator service is much
less work than forcing all of the applications to be changed to
contact this posited locator service.  

						- Ted



From owner-ietf@ietf.org  Fri May  2 01:56:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25335;
	Fri, 2 May 2003 01:56:14 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BTOm-0005I3-00
	for ietf-list@ran.ietf.org; Fri, 02 May 2003 01:47:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BTLT-00057D-00
	for ietf@ran.ietf.org; Fri, 02 May 2003 01:44:31 -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 BAA25197
	for <ietf@ietf.org>; Fri, 2 May 2003 01:40:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BTJq-0002AI-00
	for ietf@ietf.org; Fri, 02 May 2003 01:42:50 -0400
Received: from wetware.wetware.com ([199.108.16.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BTJk-0002A4-00
	for ietf@ietf.org; Fri, 02 May 2003 01:42:44 -0400
Received: from wetware.com([208.177.152.16]) (1982 bytes) by wetware.wetware.com
	via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp
	(sender: <jhw@wetware.com>) 
	id <m19BTJL-002zTnC@wetware.wetware.com>
	for <ietf@ietf.org>; Thu, 1 May 2003 22:42:19 -0700 (PDT)
	(Smail-3.2.0.114 2001-Aug-6 #1 built 2002-Sep-2)
Date: Thu, 1 May 2003 22:42:24 -0700
Subject: Re: My thoughts on local-use addresses
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: james woodyatt <jhw@wetware.com>
To: IETF list <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
In-Reply-To: <200305011525.h41FPOkm018023@ginger.lcs.mit.edu>
Message-Id: <D9A25C7F-7C60-11D7-B65A-000393BA7EBA@wetware.com>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Thursday, May 1, 2003, at 08:25 US/Pacific, J. Noel Chiappa wrote:
> [I wrote:]
>> Have any of you looked at the actual marketing copy that sells real
>> people on why they might want to pay real money for a NAT box? It 
>> might
>> be instructive.
>
> You really expect the marketing department to have clue? :-)

Actually, I expect the people reading the marketing copy to have at 
least enough clue to be able to decide whether the price in 
dollars/euros/yuan/Imperial-credits charged by the vendor is acceptable 
to them.

My point is that people pay real money to buy NAT devices.  Some of 
them buy retail consumer electronics appliances.  Others buy enterprise 
grade networking gear.  Still others buy licenses to software and 
integrate it into other products.  The market is large enough that it 
should *not* be hard to get a fix on why people buy them without paying 
Gallup to conduct a scientific poll.

There are many reasons people buy NAT devices.  I'm sure there are even 
some people who like having them primarily because they "want 
identifiers for their machines that are independent of their location 
in the connectivity topology," but frankly-- I think those people are 
very weird, and I doubt that very many of them are spending their own 
money to purchase their NAT devices.


-- 
j h woodyatt <jhw@wetware.com>
markets are only free to the people who own them.




From owner-ietf@ietf.org  Fri May  2 02:44:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07773;
	Fri, 2 May 2003 02:44:08 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BUBA-0004Fj-00
	for ietf-list@ran.ietf.org; Fri, 02 May 2003 02:37:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BU6t-00043z-00
	for ietf@ran.ietf.org; Fri, 02 May 2003 02:33:31 -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 CAA07498
	for <ietf@ietf.org>; Fri, 2 May 2003 02:29:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BU5T-0002cU-00
	for ietf@ietf.org; Fri, 02 May 2003 02:32:03 -0400
Received: from wetware.wetware.com ([199.108.16.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BU5O-0002cH-00
	for ietf@ietf.org; Fri, 02 May 2003 02:31:58 -0400
Received: from wetware.com([208.177.152.16]) (3286 bytes) by wetware.wetware.com
	via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp
	(sender: <jhw@wetware.com>) 
	id <m19BU5Q-002zTnC@wetware.wetware.com>
	for <ietf@ietf.org>; Thu, 1 May 2003 23:32:00 -0700 (PDT)
	(Smail-3.2.0.114 2001-Aug-6 #1 built 2002-Sep-2)
Date: Thu, 1 May 2003 23:32:05 -0700
Subject: Re: My thoughts on local-use addresses
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: james woodyatt <jhw@wetware.com>
To: IETF list <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
In-Reply-To: <3EB191BD.2012F491@earthlink.com>
Message-Id: <CAA6C436-7C67-11D7-B65A-000393BA7EBA@wetware.com>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Thursday, May 1, 2003, at 14:29 US/Pacific, Peter Deutsch wrote:
>
> [...] As you pointed out earlier, folks talked about separating out 
> the end
> point identifier in the past, maybe we should reexamine this suggesion
> in light of today's impasse? Maybe what we really need here is to 
> change
> one of the axioms and see if it takes us to a non-Euclidian geometric
> space?

I am reminded of a pleasant discussion I had on Wednesday with one of 
my colleagues, who studied under David Cheriton at Stanford.  He 
recommended Dr. Cheriton's TRIAD paper to me, which takes pretty much 
exactly the approach you suggest above, so I dutifully scurried off and 
read it.

TRIAD is a wonderful idea.  I love it.  I'm almost sold.  Almost.  
Unfortunately, while I see how the approach can be made to work without 
a mass rollout of new functionality in the routers, or even in the 
hosts, it *does* require a new infrastructure of relay agents.  In 
other words, his fix for NAT doesn't work, because the existing NAT 
deployments interfere with it.  Doh!

So I sat down with a hot cup of coffee in the atrium and sketched up an 
idea of what it would take in the hosts (and in strategically 
positioned middleboxes in the network) to work around the problem posed 
by existing NAT deployments, so that we could phase them out and get 
back the all-singing, all-dancing end-to-end goodness that is supposed 
to have existed in the ancient Internet world.

I've read RFC 3424, and I'm pretty familiar with the technical issues 
it describes, as well as the various solutions that have been tried.  
Ultimately, I ended up reinventing Christian Huitema's Teredo proposal, 
only-- the thing I was thinking about tunneling over UDP/IPv4 to solve 
the RFC 3424 problems wasn't IPv6, it was a horrible abomination cooked 
up to try to avoid deploying IPv6.  Again: doh!

For a brief moment, I thought it might be helpful to make the following 
suggestion: maybe the problem with Teredo is that the *only* thing you 
can do with it is extend IPv6 service over IPv4 through reasonably 
well-behaved NAT implementations.  What if we were to specify a 
"generic Teredo" that concentrated solely on solving the RFC 3424 
problem in a generic way and let the market decide on a profile of the 
"generic Teredo" service that it likes?

And then I sobered up and realized that an idea that seemed so 
eminently sensible to me would likely be regarded by the IAB as only 
slightly less welcome than a cholera outbreak.

> Nah, let's just continue trying to square the circle....

A fine idea.  I have my square right here.


-- 
j h woodyatt <jhw@wetware.com>
that's my village calling... no doubt, they want their idiot back.




From owner-ietf@ietf.org  Fri May  2 09:32:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13445;
	Fri, 2 May 2003 09:32:54 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BaYA-0004pM-00
	for ietf-list@ran.ietf.org; Fri, 02 May 2003 09:26:06 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BLNt-0002mV-00
	for ietf@ran.ietf.org; Thu, 01 May 2003 17:14:29 -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 RAA11193
	for <ietf@ietf.org>; Thu, 1 May 2003 17:07:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BLJX-0006t9-00
	for ietf@ietf.org; Thu, 01 May 2003 17:09:59 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19BLJR-0006sx-00
	for ietf@ietf.org; Thu, 01 May 2003 17:09:53 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19BLJR-000FEp-00; Thu, 01 May 2003 16:09:53 -0500
Date: Thu, 01 May 2003 17:09:53 -0400
From: John C Klensin <john@jck.com>
To: Keith Moore <moore@cs.utk.edu>, "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: My thoughts on local-use addresses
Message-ID: <202205796.1051808993@p3.JCK.COM>
In-Reply-To: <20030501151234.455a6707.moore@cs.utk.edu>
References: <200305011037.h41AbGYs016930@ginger.lcs.mit.edu>
 <20030501151234.455a6707.moore@cs.utk.edu>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Thursday, 01 May, 2003 15:12 -0400 Keith Moore 
<moore@cs.utk.edu> wrote:

>...
>> Which is why people use NAT's to do this...
>
> Except that NATs don't do this, unless the only apps you care
> about are local apps.  And experience indicates that users
> don't just care about local apps.

Keith, your mileage may, and probably does, differ.  But, in 
many enterprise/organizational situations, and at least some 
home networking ones, communication among hosts on the local 
network is very important, perhaps equally important as 
communication with outside hosts.  That is especially true in 
the enterprise "intranet" context, in which many users are, on a 
given day, likely to exclusively access internal web sites, 
directories, calendaring systems, etc.  Those usage patterns are 
independent of whether the addresses are global but inaccessible 
from the outside due to filtering or firewall restrictions or 
whether they are "private" space with external connectivity, if 
any, going through a NAT.

Now, in the IPv6 "multiple addresses per host" model, it would 
make perfect sense to assign every host on such a subnet an 
address that was specific to that subnet (or enterprise) and, 
for those hosts that needed external accessibility, an 
additional, presumably globally-routable, address.  If the 
subnet-specific address was appropriately obtained*, it could be 
completely independent of external providers and completely 
stable.  That would confer some small, but non-trivial 
advantages over having a single set of addresses that are 
provider-dependent.  Among other things, I can imagine several 
ways in which having one set of stable addresses that could be 
relied upon for local (intra-enterprise) host management would 
be a help in working through a provider-switch renumbering 
exercise (on the other address(es)).

Of course, none of this is dependent on whether those 
subnet-specific addresses are from a reserved "private" range 
rather than being unique addresses that no one intends to route 
outside the LAN (or enterprise/organization).

Of course, as soon as a given host has more than one address, at 
least some of the issues that Tony has been trying to describe 
become important: _something_ needs to figure out which one(s) 
to use, even if only by the trial and timeout process which, as 
you have pointed out, is much too slow (at least in the general 
case).

>> The irony is that in the architectural discussion phase (such
>> as it was) of IPng, it was proposed that these two functions
>> (location and identification) be split,
>
> Lots of good ideas got passed over in the IPng discussion.
> Despite that, I think that IPv6 ended up "about right" -
> modulo a few warts like A6 and SL and over-reliance on address
> selection.  By "about right" I mean that I think that if the
> warts are fixed it will become feasible to gracefully extend
> the IPv6 architecture in useful ways - such as to provide the
> capability to use identifiers rather than locators - without
> invalidating hosts or apps that were written to the basic IPv6
> model.

Keith, I think I agree with you about the "despite that" part of 
the above (I certainly agree about the "passed over" part). 
However, if our confusion about how to best handle multiple 
addresses per host, and where to do so, results in our moving to 
a "one host, one address" model and a flat, IP-level, address 
space, I think some of the "graceful extension" potential will 
disappear.  Indeed, if we go down that path --which I think you 
have been advocating, although I'm not sure-- I suspect that we 
had better have a general routing solution that is not dependent 
on address aggregation before we move much further forward with 
IPv6 deployment.

       john






From owner-ietf@ietf.org  Fri May  2 12:24:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19570;
	Fri, 2 May 2003 12:24:12 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Bcv4-00059u-00
	for ietf-list@ran.ietf.org; Fri, 02 May 2003 11:57:54 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BcpH-00050M-00
	for ietf@ran.ietf.org; Fri, 02 May 2003 11:51:55 -0400
Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18504
	for <ietf@ietf.org>; Fri, 2 May 2003 11:47:27 -0400 (EDT)
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by pintail.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19Bce3-0007kc-00; Fri, 02 May 2003 08:40:19 -0700
Date: Fri, 2 May 2003 11:39:14 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, narten@us.ibm.com, Erik.Nordmark@Sun.COM,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: My point about the ambiguity of the question
Message-Id: <20030502113914.16b18c95.moore@cs.utk.edu>
In-Reply-To: <086001c31009$cc4e9d00$261e4104@eagleswings>
References: <086001c31009$cc4e9d00$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Thomas & Erik,
> 
> These notes illustrate my point about the ambiguity of the question. 

What they illustrate is your persistent efforts to misconstrue and
misinterpret what other people are saying.

> First, one has to question how well Ted and others were informed if
> their issue is all about ambiguity. 

"it" depends on the context of that particular discussion, which is not
necessarily site-local as a whole.

Ambiguity is one of the issues associated with site local, not the only one. 

Even if Ted is only concerned about ambiguity, that doesn't invalidate Ted's
opinion.  Different people will place different values on different aspects of
a proposal, so they'll have different reasons for voting yes or no on a
question such as this.
 
> As the second note shows, part of the goal of some
> votes is to disallow a network manager the ability to limit access or
> visibility to some of their nodes. 

As the author of the second note, I can authoritatively say that this is
a misinterpretation. 

Keith



From owner-ietf@ietf.org  Fri May  2 13:41:06 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22465;
	Fri, 2 May 2003 13:41:05 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BeP3-0006u3-00
	for ietf-list@ran.ietf.org; Fri, 02 May 2003 13:32:57 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BeKp-0006qa-00
	for ietf@ran.ietf.org; Fri, 02 May 2003 13:28:36 -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 NAA21692
	for <ietf@ietf.org>; Fri, 2 May 2003 13:24:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BeIz-0005uG-00
	for ietf@ietf.org; Fri, 02 May 2003 13:26:41 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19BeIe-0005tw-00
	for ietf@ietf.org; Fri, 02 May 2003 13:26:20 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26F78> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Fri, 02 May 2003 10:25:36 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Theodore Ts'o'" <tytso@mit.edu>
Cc: "'Ofer Inbar'" <cos@aaaaa.org>, <ietf@ietf.org>
Subject: RE: what the "scope" disagreement is about
Date: Fri, 2 May 2003 10:25:33 -0700
Message-ID: <09cd01c310cf$d6660230$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030502024507.GB1649@think>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA22465

Theodore Ts'o wrote:
> No, but stable address that can be routed globally satifies 
> the goal having an address which can be passed from B to C 
> and still be used to
> reach A.   That was my point.

Only if there is a route from C to A for the address that was passed. If
there is a list that B can reach A by, it needs a way to tell C to get
its own list, or a way to sort out which will actually be useful to C. 

> 
> It seems to me that you have this alternate solution which 
> requires using the DNS instead.  But given the choice between 
> forcing applications to be rewritten, or leaning on the ISP's 
> to provide globally routable, provider-independent addresses 
> that *can* be passed from B to C and used to reach A, we know 
> what network managers have done, successfully --- they lean 
> on their ISP's.

I agree, but just because an address is unique does not mean it is
globally routable. If B passes an address for A that it can reach, but C
has no route to, this is not accomplishing the network manager's goal.
For some reason the network manager doesn't want C to contact A by a
particular address, so B shouldn't be passing it. 


> ... and your solution is that IPv6 shouldn't do any of this 
> work? Make the the application writers modify all of their 
> protocols and implementations, as well as forcing the DNS to 
> retool?  No wonder your proposed solution is so popular.  :-)

IPv6 didn't cause this problem, it only makes it harder to ignore. 

> 
> Yes, but at the same time it is no *more* work than that 
> which is required by your scheme.  Regardless of whether we 
> put this work all on the shoulders of the DNS and application 
> folks, we still need to have to provide the same solution.  
> So your scheme of forcing the DNS to do all of this work 
> isn't any easier.

I didn't say DNS has to do all of the work. All name resolutions
services need to as well as any other process that passes around
addresses that it intends the receiver to use as a topology locator.
This is a simple engineering function of making the data useful in the
context it is intended to be used. 

> 
> > Mangling the address field in the packet only allows the app to use 
> > part of the address for the identifier. There is no reason that the 
> > identifier has to be part of the address.
> 
> Yes, applications would have to be changed to recognize that 
> only part of the "IPv6 address" is useful as the identifier.  
> But I suspect when you compare the utility of a fixed-length 
> identifier which is guaranteed to be unique, as opposed to a 
> variable-length, often-inconsistent user-provided string,the 
> fixed-length identifier will be considered much superior.

Uniqueness does not guarantee utility, and having something that can
consistently be turned into a useful value is always superior to quickly
getting the wrong answer. 

> 
> The bottom line is that in order to solve the problem right, 
> I think everyone will have to make some changes.  Perhaps 
> part of the problem here is that **everyone** has been 
> saying, "my part of the stack is perfect --- everything else 
> in the stack needs to change in order to accomodate *me*".  
> For example, saying that nothing needs to change in IPv6, but 
> rather the IESG must force the DNS direct to do all sorts of 
> things, and that application writers must be forced to make 
> all sorts of changes to conform to a particular architecture, 
> might not necessarily been the course of success.  In fact, 
> it probably would just cause a general consensus to deprecate 
> site-local addresses.  :-)

IE: Shoot the messenger rather than deal with the issues that have been
ignored for 15+ years ... :(

> 
> > The problem will not be solved by PI addressing. I don't 
> care if apps 
> > pass around addresses, as long as they are doing the work 
> to make sure 
> > the address is consistent with the topology the app is 
> intentionally 
> > describing. If the app is not going to learn about topology (and I 
> > agree the app shouldn't) it needs to rely on a service that has the 
> > means to do the job. We agree, the current DNS is not up to 
> the task.
> 
> What if applications pass around a fixed-length identifier 
> which they consider to be a globally unique "address", and 
> the IP layer contacted some locator server (to be defined) a 
> routable entity which it considers an "address"?  It's the 
> same pieces which you outlined; it's just simply a matter of 
> factoring the pieces slightly different, and recognizing that 
> there is only one IP layer, and many applications. So 
> modifying the IP layer to make use of the locator service is 
> much less work than forcing all of the applications to be 
> changed to contact this posited locator service.  

I don't have a conceptual problem with the approach, but such a service
would have many of the same issues that DNS should be dealing with
anyway. In particular it would need to converge quickly on a global
basis, at the same time the resolution function is widely distributed to
scale appropriately. Someone would have to show me how the
fixed/variable length issue makes any difference to the hard part of
this problem.

Tony


 




From owner-ietf@ietf.org  Fri May  2 13:59:51 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23365;
	Fri, 2 May 2003 13:59:51 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BeJM-0006n2-00
	for ietf-list@ran.ietf.org; Fri, 02 May 2003 13:27:04 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BeBy-0006j1-00
	for ietf@ran.ietf.org; Fri, 02 May 2003 13:19:26 -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 NAA21384
	for <ietf@ietf.org>; Fri, 2 May 2003 13:15:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BeAD-0005rT-00
	for ietf@ietf.org; Fri, 02 May 2003 13:17:37 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BeA7-0005rQ-00
	for ietf@ietf.org; Fri, 02 May 2003 13:17:32 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h42HHkv06034;
        Fri, 2 May 2003 13:17:46 -0400 (EDT)
Date: Fri, 2 May 2003 13:17:46 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, cos@aaaaa.org, ietf@ietf.org
Subject: Re: what the "scope" disagreement is about
Message-Id: <20030502131746.7ed5ccdb.moore@cs.utk.edu>
In-Reply-To: <08f401c31026$02cae980$261e4104@eagleswings>
References: <20030501162240.5492a47d.moore@cs.utk.edu>
	<08f401c31026$02cae980$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

This discussion is looping, and Tony seems to be the only person who is
hung up about this, so I'm going to reply to this message in private
rather than on the list.

Keith
 



From owner-ietf@ietf.org  Fri May  2 14:24:56 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24248;
	Fri, 2 May 2003 14:24:56 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Bf1k-0008IJ-00
	for ietf-list@ran.ietf.org; Fri, 02 May 2003 14:12:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Bezh-0008ED-00
	for ietf@ran.ietf.org; Fri, 02 May 2003 14:10:49 -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 OAA23648
	for <ietf@ietf.org>; Fri, 2 May 2003 14:07:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BeyA-0006FL-00
	for ietf@ietf.org; Fri, 02 May 2003 14:09:14 -0400
Received: from mailhost.iprg.nokia.com ([205.226.5.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Bexz-0006ER-00
	for ietf@ietf.org; Fri, 02 May 2003 14:09:04 -0400
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id LAA24436
	for <ietf@ietf.org>; Fri, 2 May 2003 11:08:36 -0700 (PDT)
X-Delivered-For: <ietf@ietf.org>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h42I8ZM31982;
	Fri, 2 May 2003 11:08:35 -0700
X-mProtect: <200305021808> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.9.159, claiming to be "spruce.iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdlnkUWf; Fri, 02 May 2003 11:08:33 PDT
Message-Id: <4.3.2.7.2.20030502103137.037bc688@mailhost.iprg.nokia.com>
X-Sender: hinden@mailhost.iprg.nokia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 02 May 2003 11:08:13 -0700
To: ietf@ietf.org
From: Bob Hinden <hinden@iprg.nokia.com>
Subject: Barry Leiner
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA24248

Yesterday I discovered that Barry Leiner had died when I saw his obituary 
in the San Jose Mercury News:

   http://www.siliconvalley.com/mld/siliconvalley/5759432.htm

Barry was a DARPA program manager and was very involved in the early 
Internet and the organizations the evolved into the IETF.

I did a search and found the following written by Bob Kahn.  It is more 
eloquent that anything I could say.

Bob

------------------------------------------------------------------------------

http://www.dlib.org/dlib/april03/04editorial.html

Memorial Tribute to Barry Leiner

by Robert E. Kahn

Quite unexpectedly, Barry Leiner — a pioneer in the information technology 
— died in his sleep during the early morning hours of April 2, 2003. Our 
thoughts and prayers go out to his wife Ellen and their two children, Jason 
and Diedre, along with the rest of their family.

....

Let me turn my attention to a few of Barry's most important contributions. 
While he became well known in the networking community during the 1980s, a 
decade later he also became well known in the information management 
community. His background in communications made him an ideal candidate to 
take responsibility for the Internet project at DARPA. I had started the 
project in the early 1970s and Vint Cerf ran it from 1976-1982. By 1983, 
the technology had matured to the point that DARPA transitioned the ARPANET 
to the TCP/IP protocols and the operational Internet was put in place. The 
main issues here were as much organizational and social as they were 
technical and bureaucratic and required skill in all four areas. Barry 
Leiner had all four requisite skills to do the job.

.....

This was the essence of Barry Leiner as I knew him. He strove for 
accomplishment, for fairness and objectivity, for collaboration and 
organization, for supporting the community whose talents he greatly 
appreciated and for being a friend and colleague to all who knew him. Barry 
was a person you could trust. You could talk to him, ask his help or his 
advice and he would gladly give it if he could. He was truly a giving 
person. Anyone who ever knew him came away the better for the experience.

I will miss him greatly and I know his friends and colleagues will feel the 
same.







From owner-ietf@ietf.org  Fri May  2 15:17:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28034;
	Fri, 2 May 2003 15:17:59 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BfwG-0001wO-00
	for ietf-list@ran.ietf.org; Fri, 02 May 2003 15:11:20 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BfSD-0000fS-00
	for ietf@ran.ietf.org; Fri, 02 May 2003 14:40:17 -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 OAA24718
	for <ietf@ietf.org>; Fri, 2 May 2003 14:36:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BfQR-0006Q1-00
	for ietf@ietf.org; Fri, 02 May 2003 14:38:27 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BfQL-0006Pm-00
	for ietf@ietf.org; Fri, 02 May 2003 14:38:21 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h42IcZv06342;
        Fri, 2 May 2003 14:38:35 -0400 (EDT)
Date: Fri, 2 May 2003 14:38:35 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, tytso@mit.edu, cos@aaaaa.org, ietf@ietf.org
Subject: Re: what the "scope" disagreement is about
Message-Id: <20030502143835.3a00a086.moore@cs.utk.edu>
In-Reply-To: <09cd01c310cf$d6660230$261e4104@eagleswings>
References: <20030502024507.GB1649@think>
	<09cd01c310cf$d6660230$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > No, but stable address that can be routed globally satifies 
> > the goal having an address which can be passed from B to C 
> > and still be used to
> > reach A.   That was my point.
> 
> Only if there is a route from C to A for the address that was passed.
> If there is a list that B can reach A by, it needs a way to tell C to
> get its own list, or a way to sort out which will actually be useful
> to C. 

NO, Tony.  We need for the network to do routing, not the hosts.

Why is this so hard for you to understand?

Keith



From owner-ietf@ietf.org  Fri May  2 15:17:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28035;
	Fri, 2 May 2003 15:17:59 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BfwF-0001vb-00
	for ietf-list@ran.ietf.org; Fri, 02 May 2003 15:11:19 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BfNX-0000bp-00
	for ietf@ran.ietf.org; Fri, 02 May 2003 14:35:27 -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 OAA24619
	for <ietf@ietf.org>; Fri, 2 May 2003 14:31:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BfLl-0006OQ-00
	for ietf@ietf.org; Fri, 02 May 2003 14:33:37 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19BfLf-0006Nq-00
	for ietf@ietf.org; Fri, 02 May 2003 14:33:31 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26F90> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Fri, 02 May 2003 11:33:24 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Keith Moore'" <moore@cs.utk.edu>
Cc: <narten@us.ibm.com>, <Erik.Nordmark@Sun.COM>, <ipng@sunroof.eng.sun.com>,
        <ietf@ietf.org>
Subject: RE: My point about the ambiguity of the question
Date: Fri, 2 May 2003 11:33:13 -0700
Message-ID: <09d301c310d9$4a99b1c0$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030502113914.16b18c95.moore@cs.utk.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA28035

Keith Moore wrote:
> Ambiguity is one of the issues associated with site local, 
> not the only one. 
> ...
> > As the second note shows, part of the goal of some
> > votes is to disallow a network manager the ability to limit 
> access or 
> > visibility to some of their nodes.
> 
> As the author of the second note, I can authoritatively say 
> that this is a misinterpretation. 

So please explain how I misinterpreted. Everything that is not about
ambiguity is about the simple ability to consistently limit access or
visibility, and identify when that is being done. 

We don't need to deprecate SL to fix the ambiguity, so the insistence
that deprecating SL fixes other things only leads to the conclusion that
this is about limiting a network manager's ability to define how his
network is run. That is not the IETF's call, so those votes are not
valid.

Tony




From owner-ietf@ietf.org  Fri May  2 15:24:27 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28429;
	Fri, 2 May 2003 15:24:27 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Bg0t-0003NX-00
	for ietf-list@ran.ietf.org; Fri, 02 May 2003 15:16:07 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BfVs-0000ld-00
	for ietf@ran.ietf.org; Fri, 02 May 2003 14:44:04 -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 OAA24854
	for <ietf@ietf.org>; Fri, 2 May 2003 14:39:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BfTr-0006SA-00
	for ietf@ietf.org; Fri, 02 May 2003 14:41:59 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BfTl-0006S5-00
	for ietf@ietf.org; Fri, 02 May 2003 14:41:53 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h42Ig1v06366;
        Fri, 2 May 2003 14:42:01 -0400 (EDT)
Date: Fri, 2 May 2003 14:42:01 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, narten@us.ibm.com, Erik.Nordmark@Sun.COM,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: My point about the ambiguity of the question
Message-Id: <20030502144201.3dfc58c1.moore@cs.utk.edu>
In-Reply-To: <09d301c310d9$4a99b1c0$261e4104@eagleswings>
References: <20030502113914.16b18c95.moore@cs.utk.edu>
	<09d301c310d9$4a99b1c0$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Fri, 2 May 2003 11:33:13 -0700
"Tony Hain" <alh-ietf@tndh.net> wrote:

> Keith Moore wrote:
> > Ambiguity is one of the issues associated with site local, 
> > not the only one. 
> > ...
> > > As the second note shows, part of the goal of some
> > > votes is to disallow a network manager the ability to limit 
> > access or 
> > > visibility to some of their nodes.
> > 
> > As the author of the second note, I can authoritatively say 
> > that this is a misinterpretation. 
> 
> So please explain how I misinterpreted. Everything that is not about
> ambiguity is about the simple ability to consistently limit access or
> visibility, and identify when that is being done. 

False.  Forcing hosts or apps to do routing is about neither of these.
Forcing applications to be aware of topology is about neither of these.

Keith



From owner-ietf@ietf.org  Fri May  2 15:55:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29899;
	Fri, 2 May 2003 15:55:36 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BgPN-0008A8-00
	for ietf-list@ran.ietf.org; Fri, 02 May 2003 15:41:25 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BgLV-0007tr-00
	for ietf@ran.ietf.org; Fri, 02 May 2003 15:37:25 -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 PAA29099
	for <ietf@ietf.org>; Fri, 2 May 2003 15:33:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BgJy-00079c-00
	for ietf@ietf.org; Fri, 02 May 2003 15:35:50 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19BgJs-00079N-00
	for ietf@ietf.org; Fri, 02 May 2003 15:35:44 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26FB7> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Fri, 02 May 2003 12:35:44 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Keith Moore'" <moore@cs.utk.edu>
Cc: <narten@us.ibm.com>, <Erik.Nordmark@Sun.COM>, <ipng@sunroof.eng.sun.com>,
        <ietf@ietf.org>
Subject: RE: My point about the ambiguity of the question
Date: Fri, 2 May 2003 12:35:44 -0700
Message-ID: <0a0801c310e2$060d63e0$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030502144201.3dfc58c1.moore@cs.utk.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA29899

Keith Moore wrote:
> > So please explain how I misinterpreted. Everything that is 
> not about 
> > ambiguity is about the simple ability to consistently limit 
> access or 
> > visibility, and identify when that is being done.
> 
> False.  Forcing hosts or apps to do routing is about neither 
> of these. Forcing applications to be aware of topology is 
> about neither of these.

The existence of a prefix does not force host or apps to do routing or
be aware of topology. The only way to come to that conclusion is if you
mean that network managers expect apps they deploy to behave correctly
in the presence of limited access or visibility, and the defined prefix
shows there is a mechanism to do so. 

Nothing is forcing the app to do anything, after all it could rely on a
service. Eliminating a defined prefix does not remove the expectation of
the network manager that apps will behave correctly on the deployed
network. 

Voting to eliminate a defined prefix with the expectation that the
application will then see a flat routing space is an indirect effort to
prevent the network manager from deploying local scopes through routing
or access controls. 

The IETF does not design networks, or make operational decisions.

Tony






From owner-ietf@ietf.org  Fri May  2 16:05:47 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00249;
	Fri, 2 May 2003 16:05:46 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BgfM-000051-00
	for ietf-list@ran.ietf.org; Fri, 02 May 2003 15:57:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BgTP-0008Dp-00
	for ietf@ran.ietf.org; Fri, 02 May 2003 15:45:35 -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 PAA29369
	for <ietf@ietf.org>; Fri, 2 May 2003 15:41:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BgRd-0007Cy-00
	for ietf@ietf.org; Fri, 02 May 2003 15:43:45 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19BgRX-0007Cu-00
	for ietf@ietf.org; Fri, 02 May 2003 15:43:39 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26FBC> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Fri, 02 May 2003 12:44:11 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Keith Moore'" <moore@cs.utk.edu>
Cc: <tytso@mit.edu>, <cos@aaaaa.org>, <ietf@ietf.org>
Subject: RE: what the "scope" disagreement is about
Date: Fri, 2 May 2003 12:44:11 -0700
Message-ID: <0a0901c310e3$3444f1a0$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030502143835.3a00a086.moore@cs.utk.edu>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore wrote:
> NO, Tony.  We need for the network to do routing, not the hosts.
> 
> Why is this so hard for you to understand?

It is not hard to understand, because I agree there is no need for the
host or app to do routing. At the same time, the host or app doesn't
need to be passing around topology information. If any process chooses
to pass around values that are explicitly expected to be directly used
as topology locators, that process needs to understand the topology it
is describing. This isn't rocket science ...

Tony




From owner-ietf@ietf.org  Fri May  2 16:19:11 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00759;
	Fri, 2 May 2003 16:19:11 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BgfO-000066-00
	for ietf-list@ran.ietf.org; Fri, 02 May 2003 15:57:58 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BgYR-0008IZ-00
	for ietf@ran.ietf.org; Fri, 02 May 2003 15:50:47 -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 PAA29560
	for <ietf@ietf.org>; Fri, 2 May 2003 15:47:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BgWt-0007Fh-00
	for ietf@ietf.org; Fri, 02 May 2003 15:49:11 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BgWn-0007FA-00
	for ietf@ietf.org; Fri, 02 May 2003 15:49:05 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h42JnHv06611;
        Fri, 2 May 2003 15:49:17 -0400 (EDT)
Date: Fri, 2 May 2003 15:49:17 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, narten@us.ibm.com, Erik.Nordmark@Sun.COM,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: My point about the ambiguity of the question
Message-Id: <20030502154917.69c3d2d3.moore@cs.utk.edu>
In-Reply-To: <0a0801c310e2$060d63e0$261e4104@eagleswings>
References: <20030502144201.3dfc58c1.moore@cs.utk.edu>
	<0a0801c310e2$060d63e0$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > False.  Forcing hosts or apps to do routing is about neither 
> > of these. Forcing applications to be aware of topology is 
> > about neither of these.
> 
> The existence of a prefix does not force host or apps to do routing or
> be aware of topology.

as long as the prefix is never used, you're entirely correct.

> The only way to come to that conclusion is if
> you mean that network managers expect apps they deploy to behave
> correctly in the presence of limited access or visibility, and the
> defined prefix shows there is a mechanism to do so. 

the prefix doesn't help apps do that.  and the very assumptions behind
use of the prefix are what force apps to do that.

> Nothing is forcing the app to do anything, after all it could rely on
> a service. 

in other words, we could create magic pixie dust if we only had magic
pixie dust...



From owner-ietf@ietf.org  Fri May  2 16:27:00 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01178;
	Fri, 2 May 2003 16:27:00 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BgfQ-00007R-00
	for ietf-list@ran.ietf.org; Fri, 02 May 2003 15:58:00 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Bgez-0008Rt-00
	for ietf@ran.ietf.org; Fri, 02 May 2003 15:57:33 -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 PAA29807
	for <ietf@ietf.org>; Fri, 2 May 2003 15:53:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BgdC-0007JN-00
	for ietf@ietf.org; Fri, 02 May 2003 15:55:42 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Bgd6-0007JJ-00
	for ietf@ietf.org; Fri, 02 May 2003 15:55:37 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h42Ju6v06638;
        Fri, 2 May 2003 15:56:06 -0400 (EDT)
Date: Fri, 2 May 2003 15:56:06 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, tytso@mit.edu, cos@aaaaa.org, ietf@ietf.org
Subject: Re: what the "scope" disagreement is about
Message-Id: <20030502155606.318d2800.moore@cs.utk.edu>
In-Reply-To: <0a0901c310e3$3444f1a0$261e4104@eagleswings>
References: <20030502143835.3a00a086.moore@cs.utk.edu>
	<0a0901c310e3$3444f1a0$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > NO, Tony.  We need for the network to do routing, not the hosts.
> > 
> > Why is this so hard for you to understand?
> 
> It is not hard to understand, because I agree there is no need for the
> host or app to do routing. At the same time, the host or app doesn't
> need to be passing around topology information.

you're simply wrong about that, at least in the current architecture.

> If any process chooses
> to pass around values that are explicitly expected to be directly used
> as topology locators, that process needs to understand the topology it
> is describing. This isn't rocket science ...

that "process" is called IP routing, and expecting routers to understand
IP addresses and their relationship to topology is not a new idea.

Keith
 



From owner-ietf@ietf.org  Fri May  2 16:33:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01494;
	Fri, 2 May 2003 16:33:55 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Bh8o-0001ty-00
	for ietf-list@ran.ietf.org; Fri, 02 May 2003 16:28:22 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BgnY-0000Zf-00
	for ietf@ran.ietf.org; Fri, 02 May 2003 16:06:24 -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 QAA00148
	for <ietf@ietf.org>; Fri, 2 May 2003 16:02:08 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BglW-0007Ov-00
	for ietf@ietf.org; Fri, 02 May 2003 16:04:19 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BglR-0007NK-00
	for ietf@ietf.org; Fri, 02 May 2003 16:04:13 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h42K0pjs009433;
	Fri, 2 May 2003 16:00:51 -0400
Message-Id: <200305022000.h42K0pjs009433@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Keith Moore <moore@cs.utk.edu>
Cc: alh-ietf@tndh.net, tytso@mit.edu, cos@aaaaa.org, ietf@ietf.org
Subject: Re: what the "scope" disagreement is about 
In-Reply-To: Your message of "Fri, 02 May 2003 14:38:35 EDT."
             <20030502143835.3a00a086.moore@cs.utk.edu> 
References: <20030502024507.GB1649@think> <09cd01c310cf$d6660230$261e4104@eagleswings>
            <20030502143835.3a00a086.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-221112996P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 02 May 2003 16:00:51 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-221112996P
Content-Type: text/plain; charset=us-ascii

On Fri, 02 May 2003 14:38:35 EDT, Keith Moore said:

> NO, Tony.  We need for the network to do routing, not the hosts.
> 
> Why is this so hard for you to understand?

Or as the spoofed ad from a number of years ago said:

"The network is the network.  The computer is the computer.  We
apologize for any confusion." -- Sun Microsystems

--==_Exmh_-221112996P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+ss5ycC3lWbTT17ARAkh6AKDvJu36EBbn5l1lxmgVaRRB6Y8p4QCdGuG3
WVpGaYwpUjrCizxcEpQp8yQ=
=4FkY
-----END PGP SIGNATURE-----

--==_Exmh_-221112996P--



From owner-ietf@ietf.org  Fri May  2 17:09:47 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02845;
	Fri, 2 May 2003 17:09:47 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Bhbi-0003qa-00
	for ietf-list@ran.ietf.org; Fri, 02 May 2003 16:58:14 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Bg0P-0003FA-00
	for ietf@ran.ietf.org; Fri, 02 May 2003 15:15:37 -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 PAA27275
	for <ietf@ietf.org>; Fri, 2 May 2003 15:10:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Bftl-0006q2-00
	for ietf@ietf.org; Fri, 02 May 2003 15:08:45 -0400
Received: from gungnir.fnal.gov ([131.225.80.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Bftf-0006oe-00
	for ietf@ietf.org; Fri, 02 May 2003 15:08:39 -0400
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.12.8/8.12.8) with ESMTP id h42J8H2Y006828;
	Fri, 2 May 2003 14:08:17 -0500 (CDT)
Message-Id: <200305021908.h42J8H2Y006828@gungnir.fnal.gov>
To: Keith Moore <moore@cs.utk.edu>
Cc: alh-ietf@tndh.net, cos@aaaaa.org, ietf@ietf.org
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: what the "scope" disagreement is about 
In-reply-to: Your message of Fri, 02 May 2003 13:17:46 EDT.
             <20030502131746.7ed5ccdb.moore@cs.utk.edu> 
Date: Fri, 02 May 2003 14:08:17 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

Tony simply has the most patience.  Others of us unsubscribed.

> This discussion is looping, and Tony seems to be the only person who is
> hung up about this, so I'm going to reply to this message in private
> rather than on the list.





From owner-ietf@ietf.org  Fri May  2 17:21:13 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03209;
	Fri, 2 May 2003 17:21:13 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Bhbi-0003qw-00
	for ietf-list@ran.ietf.org; Fri, 02 May 2003 16:58:14 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BhE0-0002sI-00
	for ietf@ran.ietf.org; Fri, 02 May 2003 16:33:44 -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 QAA01336
	for <ietf@ietf.org>; Fri, 2 May 2003 16:29:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BhCS-0007fv-00
	for ietf@ietf.org; Fri, 02 May 2003 16:32:08 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19BhCM-0007fl-00
	for ietf@ietf.org; Fri, 02 May 2003 16:32:02 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26FD1> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Fri, 02 May 2003 13:32:34 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Matt Crawford'" <crawdad@fnal.gov>, "'Keith Moore'" <moore@cs.utk.edu>
Cc: <cos@aaaaa.org>, <ietf@ietf.org>
Subject: RE: what the "scope" disagreement is about 
Date: Fri, 2 May 2003 13:32:35 -0700
Message-ID: <0a1701c310e9$f70d8a70$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <200305021908.h42J8H2Y006828@gungnir.fnal.gov>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA03209

Matt Crawford wrote:
> 
> Tony simply has the most patience.  Others of us unsubscribed.

To be honest, my patience ran out long ago. This is such an important
architectural and operational point that it requires attention even when
I would much rather be doing other things.

Tony







From owner-ietf@ietf.org  Fri May  2 17:57:41 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03850;
	Fri, 2 May 2003 17:57:41 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19BiJI-0005YK-00
	for ietf-list@ran.ietf.org; Fri, 02 May 2003 17:43:16 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BiIi-0005Sp-00
	for ietf@ran.ietf.org; Fri, 02 May 2003 17:42:40 -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 RAA03567
	for <ietf@ietf.org>; Fri, 2 May 2003 17:38:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BiGu-0000Ns-00
	for ietf@ietf.org; Fri, 02 May 2003 17:40:48 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19BiGp-0000Nl-00
	for ietf@ietf.org; Fri, 02 May 2003 17:40:43 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26FE1> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Fri, 02 May 2003 14:40:59 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Keith Moore'" <moore@cs.utk.edu>
Cc: <tytso@mit.edu>, <cos@aaaaa.org>, <ietf@ietf.org>
Subject: RE: what the "scope" disagreement is about
Date: Fri, 2 May 2003 14:40:50 -0700
Message-ID: <0a3701c310f3$8059ec20$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030502155606.318d2800.moore@cs.utk.edu>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore wrote:
> > ... the host or app doesn't need to be 
> > passing around topology information.
> 
> you're simply wrong about that, at least in the current architecture.
> 
> > If any process chooses to pass around values 
> > that are explicitly expected to be directly used
> > as topology locators, that process needs to 
> > understand the topology it is describing. 
> 
> that "process" is called IP routing, and expecting routers to 
> understand IP addresses and their relationship to topology is 
> not a new idea.

There is nothing more to say ... 

Tony







From owner-ietf@ietf.org  Fri May  2 18:27:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05650;
	Fri, 2 May 2003 18:27:54 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Biqr-0003W7-00
	for ietf-list@ran.ietf.org; Fri, 02 May 2003 18:17:57 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BiqE-0003GO-00
	for ietf@ran.ietf.org; Fri, 02 May 2003 18:17:18 -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 SAA05256
	for <ietf@ietf.org>; Fri, 2 May 2003 18:13:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Bint-0000YE-00
	for ietf@ietf.org; Fri, 02 May 2003 18:14:53 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Binn-0000Xm-00
	for ietf@ietf.org; Fri, 02 May 2003 18:14:47 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19BinY-000MoJ-00; Fri, 02 May 2003 17:14:32 -0500
Date: Fri, 02 May 2003 18:14:31 -0400
From: John C Klensin <john-ietf@jck.com>
To: "alh-ietf@tndh.net" <alh-ietf@tndh.net>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: what the "scope" disagreement is about
Message-ID: <292482818.1051899271@p3.JCK.COM>
In-Reply-To: <0a0901c310e3$3444f1a0$261e4104@eagleswings>
References:  <0a0901c310e3$3444f1a0$261e4104@eagleswings>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony,

Having picked on Keith in public a few days ago, it is your 
turn, and I'll make the same apology in advance.  Even on the 
parts of this with which I agree, the content and style of the 
discussion is no longer helpful. So, with the understanding that 
I'm just a random member of the community who has no authority 
to tell anyone to do, or not do, anything, I want to make two 
observations and a few suggestions to you and everyone else who 
is posting to this list.  Fwiw, if I hadn't had enough 
experience working with both you and Keith to value the 
experience and perspective of both of you when you are calm and 
thinking and explaining yourselves clearly, I wouldn't bother.

First of all, you have managed to convince me and, I think most 
others who have been listening, that "get rid of SL" is an 
answer to the wrong question.  Whether it is the right answer or 
the wrong one is less important than identifying the right 
question and then sorting things out in that context.  I think 
you have been trying to identify the right question, but your 
doing so has gotten repeatedly lost in the noise.

Second, it is clear to me that you and Keith have a profound 
disagreement about the character, state, and evolution of the IP 
architecture. The precise nature of that disagreement has been 
sufficiently obscured by differences in vocabulary and arguments 
about side-issues that I imagine that most readers of the list 
can't crisply identify the disagreement.  I'm not even sure you 
and Keith can do that at this stage; I suspect, from the level 
of mis- and non-communication, that you cannot.  I can try to 
explain it, but not this week (see below).

For whatever it is worth, I'd like to encourage everyone to take 
about a week off from this.  The arguments that are being made 
today don't differ very much from those that were being made in 
late March.  Anyone who hasn't been convinced yet --one way or 
the other-- is, IMO, much more likely to be convinced by quietly 
thinking about the arguments and statements, and generally 
letting things sink in, for a week or two than by more traffic 
that repeats the arguments yet another time.

And, for several other participants... There really are some 
subtle and very important architectural issues here (a subject 
on which I think Tony and Keith agree).  _Please_ invest the 
time to try to read and understand the postings and the issues 
they are trying to address. They are not simple, or at least the 
right solutions aren't: if they were, I really hope we wouldn't 
be having discussions this lengthy or heated.   When you read a 
few sentences of a posting and then fire off a response based on 
what you think that poster, or previous ones, are suggesting -- 
and more than a few postings have clearly resulted from that 
behavior-- you mostly just add to the noise.  And the noise is 
getting seriously in the way of looking carefully at those real 
problems.

        thanks,
           john


--On Friday, 02 May, 2003 12:44 -0700 Tony Hain 
<alh-ietf@tndh.net> wrote:

> Keith Moore wrote:
>> NO, Tony.  We need for the network to do routing, not the
>> hosts.
>>
>> Why is this so hard for you to understand?
>
> It is not hard to understand, because I agree there is no need
> for the host or app to do routing. At the same time, the host
> or app doesn't need to be passing around topology information.
> If any process chooses to pass around values that are
> explicitly expected to be directly used as topology locators,
> that process needs to understand the topology it is
> describing. This isn't rocket science ...
>
> Tony




From owner-ietf@ietf.org  Mon May  5 09:00:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00528;
	Mon, 5 May 2003 09:00:57 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19CfNx-0002Ci-00
	for ietf-list@ran.ietf.org; Mon, 05 May 2003 08:48:01 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19BxXm-0005qV-00
	for ietf@ran.ietf.org; Sat, 03 May 2003 09:59:14 -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 JAA29411
	for <ietf@ietf.org>; Sat, 3 May 2003 09:55:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BxVi-0004BN-00
	for ietf@ietf.org; Sat, 03 May 2003 09:57:06 -0400
Received: from pmesmtp02.wcom.com ([199.249.20.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 19BxVO-0004B3-00
	for ietf@ietf.org; Sat, 03 May 2003 09:56:46 -0400
Received: from pmismtp01.wcomnet.com ([166.38.62.36])
 by firewall.wcom.com (Iplanet MTA )
 with ESMTP id <0HEB00D2FDDOOW@firewall.wcom.com> for ietf@ietf.org; Sat,
 03 May 2003 13:56:12 +0000 (GMT)
Received: from pmismtp01.wcomnet.com by pmismtp01.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HEB00F01DDNNL@pmismtp01.wcomnet.com> for ietf@ietf.org; Sat,
 03 May 2003 13:56:12 +0000 (GMT)
Received: from vint.mci.com ([166.50.142.107])
 by pmismtp01.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HEB00C6CDDH3W@pmismtp01.wcomnet.com> for ietf@ietf.org;
 Sat, 03 May 2003 13:56:11 +0000 (GMT)
Date: Sat, 03 May 2003 09:55:39 -0400
From: "vinton g. cerf" <vinton.g.cerf@mci.com>
Subject: Re: Barry Leiner
In-reply-to: <4.3.2.7.2.20030502103137.037bc688@mailhost.iprg.nokia.com>
X-Sender: vcerf@pop.mcilink.com
To: ietf@ietf.org
Message-id: <5.2.0.9.2.20030503095510.02dc3640@pop.mcilink.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Content-type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

folks,

also please see:

http://www.lifefiles.com/lifeLegacy.php?i_memorialid=1049731711

Vint

At 11:08 AM 5/2/2003 -0700, Bob Hinden wrote:
>Yesterday I discovered that Barry Leiner had died when I saw his obituary in the San Jose Mercury News:
>
>  http://www.siliconvalley.com/mld/siliconvalley/5759432.htm
>
>Barry was a DARPA program manager and was very involved in the early Internet and the organizations the evolved into the IETF.
>
>I did a search and found the following written by Bob Kahn.  It is more eloquent that anything I could say.
>
>Bob
>
>------------------------------------------------------------------------------






From owner-ietf@ietf.org  Mon May  5 09:02:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00596;
	Mon, 5 May 2003 09:02:21 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19CfXT-0002HB-00
	for ietf-list@ran.ietf.org; Mon, 05 May 2003 08:57:51 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19C58E-0006qf-00
	for ietf@ran.ietf.org; Sat, 03 May 2003 18:05:22 -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 RAA09596
	for <ietf@ietf.org>; Sat, 3 May 2003 17:59:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19C54z-0006Nz-00
	for ietf@ietf.org; Sat, 03 May 2003 18:02:01 -0400
Received: from natint.juniper.net ([207.17.136.129] helo=merlot.juniper.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19C54e-0006Nw-00
	for ietf@ietf.org; Sat, 03 May 2003 18:01:40 -0400
Received: from roque-bsd.juniper.net (roque-bsd.juniper.net [172.17.12.183])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id h43M1Pu34499;
	Sat, 3 May 2003 15:01:25 -0700 (PDT)
	(envelope-from roque@juniper.net)
Received: (from roque@localhost)
	by roque-bsd.juniper.net (8.11.6/8.9.3) id h43M1OP54769;
	Sat, 3 May 2003 15:01:24 -0700 (PDT)
	(envelope-from roque)
To: dean@av8.com (Dean Anderson)
Cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: The end of the world as we know it (was IPv6 address space shortages)
References: <12729734.1051619514@p3.JCK.COM> <Pine.LNX.4.44.0304291516510.1878-100000@commander.av8.net>
From: Pedro Roque Marques <roque@juniper.net>
Date: 03 May 2003 15:01:24 -0700
In-Reply-To: dean@av8.com's message of 29 Apr 03 19:28:33 GMT
Message-ID: <y4sbryj8zbf.fsf_-_@roque-bsd.juniper.net>
Lines: 86
X-Mailer: Gnus v5.4.37/XEmacs 19.16
Sender: owner-ietf@ietf.org
Precedence: bulk

dean@av8.com (Dean Anderson) writes:

> We are still not out of IPv4 address space. I don't know the projections
> for address space depletion, but I think the IPv6 problem won't be so much
> address space depletion as route space depletion. I think it will be
> unwieldy to have a million or 2 million or 10 million distinct routes.
> Aggregation won't happen the way things are currently organized.
> 

- "route space depletion" seems to be an argument postulated on the
idea that exterior routing scalability depends mostly on the number of
prefixes carried.

I tend to hold the somehow heretic view that that is not really the
case. imho, exterior routing scaling depends much more on the number
of distinct topologic information that is carried (i.e. distinct BGP
path attributes).

This much is subject to experimentation: take N distinct prefixes and
advertise them in BGP w/ the exact same path attributes; compare the
result w/ the same N advertised w/ different attributes.

I believe that you will find that using a reasonable implementation
that not only the latter consumes more memory but it also does consume
a significant higher ammount of CPU resources. I would also argue that
contrary to the pre-CIDR years, todays networking equipment is
"shorter" on CPU than on memory.

Note that topologic information (path attributes) is already the
smallest ammount of information required to express the "problem at
hand".

Thus routing information reduction should probably focus much more on
the aggregation of topology information, when possible, than reducing
the number of prefixes.

In current internet routing tables, the number of prefixes to distinct
path attributes is usually around [5-10] interval. So it is often
arguable how much effort an implementation wants to put on
concentrating on the basic information (path/topology attributes). One
can reasonably expect that if the ration of prefixes to attributes
where to increase substantially more effort would be made to
concentrate on this topologic information.

Aparently this notion that path attributes may be more relevant to
exterior routing scaling that number of prefixes is actually gaining
popularity. See for instance http://www.caida.org/projects/routing/atoms/

Of course there is a number N of prefixes that will overload your
memories, both in terms of routing and forwarding databases. But i
believe it is rather simplistic to assume this is the main scaling
factor w/ exterior routing.  

There is another point i would like to raise... today's top of the
line networking equipment has the requirement to do 40Gb of traffic on
a single line card, which should translate roughly to ~100 Mpps.
The corolary of some of the arguments applied to the routing problem
would be to say that since it is impossible to do 100Mpps using a
3-year old general purpose CPU we should all go home and declare this
packet switched experiment to be utterly unscalable.

The clever reader will point out that there is an economic value
attached to forwarding of packets while there isn't one attached to
carrying routes per se. 

But it is sort of impossible to determine the scale to which you can
engineer a given problem without considering the ammount of resources
you can throw at it...

Regardless of how you skin the cat, the discussion is going to come
back to the forum of economy and politics, be it in terms of how much
you can scale the routing systems or in terms of shifting some of the
burden to the end user networks via NAT, aggressive renumbering or any
other proposal i'm familiar with.

This rambling is rather long already, but i wouldn't want to end with
out taking my turn at the crystal ball...

Neither address or routing space exaustion seem to be realistic
enought scenarios in the medium term. There are plenty of economic
incentives for all involved (SPs, end users, vendors) to find
solutions that allow for anyone of the planet to use the main services
the internet is supposed to provide today: https and a spam-full inbox.

regards,
  Pedro.





From owner-ietf@ietf.org  Mon May  5 09:42:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01664;
	Mon, 5 May 2003 09:42:57 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Cg5L-00035S-00
	for ietf-list@ran.ietf.org; Mon, 05 May 2003 09:32:51 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19CAZh-0004uD-00
	for ietf@ran.ietf.org; Sat, 03 May 2003 23:54:05 -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 XAA13805
	for <ietf@ietf.org>; Sat, 3 May 2003 23:48:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19CAWH-0007Gr-00
	for ietf@ietf.org; Sat, 03 May 2003 23:50:33 -0400
Received: from mailout.zma.compaq.com ([161.114.64.103] helo=zmamail03.zma.compaq.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19CAVh-0007Gd-00
	for ietf@ietf.org; Sat, 03 May 2003 23:49:57 -0400
Received: from tayexg12.americas.cpqcorp.net (tayexg12.americas.cpqcorp.net [16.103.130.103])
	by zmamail03.zma.compaq.com (Postfix) with ESMTP
	id D48594239; Sat,  3 May 2003 23:49:44 -0400 (EDT)
Received: from tayexc13.americas.cpqcorp.net ([16.103.130.26]) by tayexg12.americas.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.6673);
	 Sat, 3 May 2003 23:49:44 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: My point about the ambiguity of the question
Date: Sat, 3 May 2003 23:49:44 -0400
Message-ID: <9C422444DE99BC46B3AD3C6EAFC9711B03ABD648@tayexc13.americas.cpqcorp.net>
Thread-Topic: My point about the ambiguity of the question
Thread-Index: AcMQ2agE3XRdqsc5RiqgYvZODIFj0QBFleOw
From: "Bound, Jim" <Jim.Bound@hp.com>
To: <alh-ietf@tndh.net>, "Keith Moore" <moore@cs.utk.edu>
Cc: <narten@us.ibm.com>, <Erik.Nordmark@Sun.COM>, <ipng@sunroof.eng.sun.com>,
        <ietf@ietf.org>
X-OriginalArrivalTime: 04 May 2003 03:49:44.0726 (UTC) FILETIME=[3350C360:01C311F0]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA01664

For unicast it makes it clear all we are supporting as a standards body
are globals and link-local TODAY, not forever.  That is an important
message and prudent act by the IETF.
Deprecating SLs reduces ambiguity clearly from the above premises.  
/jim

> -----Original Message-----
> From: Tony Hain [mailto:alh-ietf@tndh.net] 
> Sent: Friday, May 02, 2003 2:33 PM
> To: 'Keith Moore'
> Cc: narten@us.ibm.com; Erik.Nordmark@Sun.COM; 
> ipng@sunroof.eng.sun.com; ietf@ietf.org
> Subject: RE: My point about the ambiguity of the question
> 
> 
> Keith Moore wrote:
> > Ambiguity is one of the issues associated with site local,
> > not the only one. 
> > ...
> > > As the second note shows, part of the goal of some
> > > votes is to disallow a network manager the ability to limit
> > access or
> > > visibility to some of their nodes.
> > 
> > As the author of the second note, I can authoritatively say
> > that this is a misinterpretation. 
> 
> So please explain how I misinterpreted. Everything that is 
> not about ambiguity is about the simple ability to 
> consistently limit access or visibility, and identify when 
> that is being done. 
> 
> We don't need to deprecate SL to fix the ambiguity, so the 
> insistence that deprecating SL fixes other things only leads 
> to the conclusion that this is about limiting a network 
> manager's ability to define how his network is run. That is 
> not the IETF's call, so those votes are not valid.
> 
> Tony
> 
> 
> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page:                      http://playground.sun.com/ipng
> FTP archive:                      ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to majordomo@sunroof.eng.sun.com
> --------------------------------------------------------------------
> 





From owner-ietf@ietf.org  Mon May  5 10:13:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03428;
	Mon, 5 May 2003 10:13:50 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Cgdt-00064z-00
	for ietf-list@ran.ietf.org; Mon, 05 May 2003 10:08:33 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19CgWk-0003ZG-00
	for ietf@ran.ietf.org; Mon, 05 May 2003 10:01: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 JAA01982
	for <ietf@ietf.org>; Mon, 5 May 2003 09:55:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19CgT8-0005vP-00
	for ietf@ietf.org; Mon, 05 May 2003 09:57:26 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19CgT2-0005vI-00
	for ietf@ietf.org; Mon, 05 May 2003 09:57:20 -0400
Received: from muada.com ([3ffe:2500:310:2::1])
	by sequoia.muada.com (8.11.3/8.9.3) with ESMTP id h45DvUn10970;
	Mon, 5 May 2003 15:57:30 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Mon, 5 May 2003 15:57:32 +0200
Subject: Re: The end of the world as we know it (was IPv6 address space shortages)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: dean@av8.com (Dean Anderson), "ietf@ietf.org" <ietf@ietf.org>
To: Pedro Roque Marques <roque@juniper.net>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <y4sbryj8zbf.fsf_-_@roque-bsd.juniper.net>
Message-Id: <84ADB3B2-7F01-11D7-8744-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On zondag, mei 4, 2003, at 00:01 Europe/Amsterdam, Pedro Roque Marques 
wrote:

> - "route space depletion" seems to be an argument postulated on the
> idea that exterior routing scalability depends mostly on the number of
> prefixes carried.

> I tend to hold the somehow heretic view that that is not really the
> case. imho, exterior routing scaling depends much more on the number
> of distinct topologic information that is carried (i.e. distinct BGP
> path attributes).

> I would also argue that
> contrary to the pre-CIDR years, todays networking equipment is
> "shorter" on CPU than on memory.

Two sides of the same coin: not just because you can optimize for one 
at the expense of the other, but mainly because the memory doesn't just 
sit there inertly, it holds information that must be processed. So all 
else being equal, more memory means more information means more 
processing means more CPU usage.

> Note that topologic information (path attributes) is already the
> smallest ammount of information required to express the "problem at
> hand".

I don't necessarily agree. BGP could save a lot of overhead by 
differentiating between transit networks and leaf networks. For the 
latter, there is no need keep much information. It should be possible 
to bring this down to just a few bits.

> In current internet routing tables, the number of prefixes to distinct
> path attributes is usually around [5-10] interval.

Note that this will change for the better in IPv6 as there is no longer 
much need to keep the assignments to ISPs artificially small.

Also, in order for your assertion to be correct, it requires the 
processing that is unique for each set of path attributes to be at 
least five times as expensive as prefix processing. The former is 
mostly loop detection and AS path filtering, the latter is obviously 
prefix filtering and deleting/inserting prefixes, but also running the 
BGP path selection algorithm, which is AFAIK done per-prefix even 
though it mostly looks at the path attributes. I'm not making any 
claims either way, but I'd like to see some figures here. (Any vendors 
in the room?)

Iljitsch van Beijnum




From owner-ietf@ietf.org  Mon May  5 11:58:07 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06244;
	Mon, 5 May 2003 11:58:07 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19CiC0-00025K-00
	for ietf-list@ran.ietf.org; Mon, 05 May 2003 11:47:52 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19CiBR-00024F-00
	for ietf@ran.ietf.org; Mon, 05 May 2003 11:47:17 -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 LAA05927
	for <ietf@ietf.org>; Mon, 5 May 2003 11:42:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ci8g-0006c9-00
	for ietf@ietf.org; Mon, 05 May 2003 11:44:26 -0400
Received: from 75.5.33.65.cfl.rr.com ([65.33.5.75] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ci8V-0006c2-00
	for ietf@ietf.org; Mon, 05 May 2003 11:44:15 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19CO8n-0007m8-00; Sun, 04 May 2003 14:23:13 -0400
Date: Sun, 4 May 2003 14:23:12 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: "vinton g. cerf" <vinton.g.cerf@mci.com>
cc: ietf@ietf.org
Subject: Re: Barry Leiner
In-Reply-To: <5.2.0.9.2.20030503095510.02dc3640@pop.mcilink.com>
Message-ID: <Pine.LNX.4.44.0305041420050.28799-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 3 May 2003, vinton g. cerf wrote:

Vint,
I'm sorry about your friend.  You two must have been close.  I know how it
is when there are very few people in the world who truly understand what
you do.  It gets lonely.  My sincere condolances.

Scott



> folks,
>
> also please see:
>
> http://www.lifefiles.com/lifeLegacy.php?i_memorialid=1049731711
>
> Vint
>
> At 11:08 AM 5/2/2003 -0700, Bob Hinden wrote:
> >Yesterday I discovered that Barry Leiner had died when I saw his obituary in the San Jose Mercury News:
> >
> >  http://www.siliconvalley.com/mld/siliconvalley/5759432.htm
> >
> >Barry was a DARPA program manager and was very involved in the early Internet and the organizations the evolved into the IETF.
> >
> >I did a search and found the following written by Bob Kahn.  It is more eloquent that anything I could say.
> >
> >Bob
> >
> >------------------------------------------------------------------------------
>
>
>
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81




From owner-ietf@ietf.org  Mon May  5 21:18:01 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23717;
	Mon, 5 May 2003 21:18:00 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Cqvw-0005ED-00
	for ietf-list@ran.ietf.org; Mon, 05 May 2003 21:07:52 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Cqvm-0005DV-00
	for ietf@ran.ietf.org; Mon, 05 May 2003 21:07:42 -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 VAA23165
	for <ietf@ietf.org>; Mon, 5 May 2003 21:02:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19CqtA-0002Ks-00
	for ietf@ietf.org; Mon, 05 May 2003 21:05:00 -0400
Received: from out1.prserv.net ([32.97.166.31] helo=prserv.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Cqt4-0002KJ-00
	for ietf@ietf.org; Mon, 05 May 2003 21:04:54 -0400
Date: Tue, 6 May 2003 01:05:55 +0000 (GMT)
X-Comment: Sending client does not conform to RFC822 minimum requirements
X-Comment: Date has been added by Maillennium.
Received: from Zckflboz (slip-32-100-251-9.pr.us.prserv.net[32.100.251.9])
          by prserv.net (out1) with SMTP
          id <2003050601054120104kncfhe>; Tue, 6 May 2003 01:05:42 +0000
From: internet-drafts <internet-drafts@ietf.org>
To: ietf@ietf.org
Subject: A very  nice game
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=S1zvc39c813M0474335z07sl8O3983eR
Message-Id: <E19Cqt4-0002KJ-00@ietf-mx>
Sender: owner-ietf@ietf.org
Precedence: bulk

--S1zvc39c813M0474335z07sl8O3983eR
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>

<FONT>Hi,This is a special  nice game<br>
This game is my first work.<br>
You're the first player.<br>
I hope you would enjoy it.</FONT></BODY></HTML>

--S1zvc39c813M0474335z07sl8O3983eR
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

[Filename: demo.exe, Content-Type: application/octet-stream]
The attachment file in the message has been removed by eManager.

--S1zvc39c813M0474335z07sl8O3983eR

Content-Type: application/octet-stream;
	name=index[2].htm
Content-Transfer-Encoding: base64
Content-ID: <YL122G4bBY090032w>

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMDEgVHJhbnNpdGlv
bmFsLy9FTiI+CjxodG1sPgo8aGVhZD4KPHRpdGxlPkZMQVNIIC0gZXNxdWl6by5jb208L3Rp
dGxlPgo8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUiIGNvbnRlbnQ9InRleHQvaHRt
bDsgY2hhcnNldD1pc28tODg1OS0xIj4KPHNjcmlwdCBsYW5ndWFnZT0iSmF2YVNjcmlwdCIg
dHlwZT0idGV4dC9KYXZhU2NyaXB0Ij4KPCEtLQpmdW5jdGlvbiBNTV9vcGVuQnJXaW5kb3co
dGhlVVJMLHdpbk5hbWUsZmVhdHVyZXMpIHsgLy92Mi4wCiAgd2luZG93Lm9wZW4odGhlVVJM
LHdpbk5hbWUsZmVhdHVyZXMpOwp9Ci8vLS0+Cjwvc2NyaXB0Pgo8L2hlYWQ+Cgo8Ym9keSBv
bkxvYWQ9Ik1NX29wZW5CcldpbmRvdygnLi4vc3dmL25vd2FyLmh0bScsJ05vV2FyJywnd2lk
dGg9MTIwLGhlaWdodD02MDAnKTtNTV9vcGVuQnJXaW5kb3coJ2xpYnJvcy5odG0nLCdsaWJy
b3MnLCdzY3JvbGxiYXJzPXllcyx3aWR0aD0xMjAsaGVpZ2h0PTYwMCcpIj4KPC9ib2R5Pgo8
L2h0bWw+Cj==
--S1zvc39c813M0474335z07sl8O3983eR--



From owner-ietf@ietf.org  Tue May  6 07:40:20 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14990;
	Tue, 6 May 2003 07:40:20 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19D0gl-00084m-00
	for ietf-list@ran.ietf.org; Tue, 06 May 2003 07:32:51 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19D0fy-00083p-00
	for ietf@ran.ietf.org; Tue, 06 May 2003 07:32:02 -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 HAA14739
	for <ietf@ietf.org>; Tue, 6 May 2003 07:27:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19D0dG-000570-00
	for ietf@ietf.org; Tue, 06 May 2003 07:29:14 -0400
Received: from web20704.mail.yahoo.com ([216.136.226.177])
	by ietf-mx with smtp (Exim 4.12)
	id 19D0dA-00056x-00
	for ietf@ietf.org; Tue, 06 May 2003 07:29:08 -0400
Message-ID: <20030506112933.63293.qmail@web20704.mail.yahoo.com>
Received: from [210.118.108.254] by web20704.mail.yahoo.com via HTTP; Tue, 06 May 2003 07:29:33 EDT
Date: Tue, 6 May 2003 07:29:33 -0400 (EDT)
From: Tulip Rasputin <tulip_rasputin@yahoo.ca>
Subject: Submitting an IETF draft in a specific WG
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Folks,
I have written a draft and want to post it on a specific IETF WG, say the OSPF WG. How can i then
assure that the draft which i post gets announced to that particular WG also apart from the
general IETF announcement list.

My doubt is that if i post my draft on internet-drafts@ietf.org and specify the working group as
OSPF will this be announced to the OSPF WG. If not then how will they come to know of this draft?

I have a doubt that the drafts may be only announced in the WG if they become accepted asworking
group documents. 

Please help me clarify this.

Should i just send a mail to internet-drafts@ietf.org with my draft as an attachment then?

Regards,
Rasputin



______________________________________________________________________ 
Post your free ad now! http://personals.yahoo.ca



From owner-ietf@ietf.org  Tue May  6 09:26:06 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20433;
	Tue, 6 May 2003 09:26:06 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19D1xr-0001kQ-00
	for ietf-list@ran.ietf.org; Tue, 06 May 2003 08:54:35 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19D0xR-0008Va-00
	for ietf@ran.ietf.org; Tue, 06 May 2003 07:50:05 -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 HAA15403
	for <ietf@ietf.org>; Tue, 6 May 2003 07:45:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19D0ui-0005CT-00
	for ietf@ietf.org; Tue, 06 May 2003 07:47:16 -0400
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49] helo=albatross.tn.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19D0ud-0005CQ-00
	for ietf@ietf.org; Tue, 06 May 2003 07:47:11 -0400
Received: from esealnt612.al.sw.ericsson.se (alteon-nat1.sw.ericsson.se [153.88.254.118])
	by albatross.tn.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6a) with ESMTP id h46Blp0J025302;
	Tue, 6 May 2003 13:47:51 +0200 (MEST)
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2655.55)
	id <K1N2JK74>; Tue, 6 May 2003 13:47:48 +0200
Message-ID: <A943FD84BD9ED41193460008C7918050072E914E@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EAB)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'Tulip Rasputin'" <tulip_rasputin@yahoo.ca>, ietf@ietf.org
Subject: RE: Submitting an IETF draft in a specific WG
Date: Tue, 6 May 2003 13:35:55 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Rasputin,

You can ask "internet-drafts" to announce it on a specific list,
but if that fails you can always send a message to the WG mail list yourself, e.g. forward the announcement.

BR
/L-E


> -----Original Message-----
> From: Tulip Rasputin [mailto:tulip_rasputin@yahoo.ca]
> Sent: den 6 maj 2003 13:30
> To: ietf@ietf.org
> Subject: Submitting an IETF draft in a specific WG
> 
> 
> Folks,
> I have written a draft and want to post it on a specific IETF 
> WG, say the OSPF WG. How can i then
> assure that the draft which i post gets announced to that 
> particular WG also apart from the
> general IETF announcement list.
> 
> My doubt is that if i post my draft on 
> internet-drafts@ietf.org and specify the working group as
> OSPF will this be announced to the OSPF WG. If not then how 
> will they come to know of this draft?
> 
> I have a doubt that the drafts may be only announced in the 
> WG if they become accepted asworking
> group documents. 
> 
> Please help me clarify this.
> 
> Should i just send a mail to internet-drafts@ietf.org with my 
> draft as an attachment then?
> 
> Regards,
> Rasputin
> 
> 
> 
> ______________________________________________________________
> ________ 
> Post your free ad now! http://personals.yahoo.ca
> 



From owner-ietf@ietf.org  Tue May  6 09:27:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20486;
	Tue, 6 May 2003 09:27:18 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19D2Gf-0003LG-00
	for ietf-list@ran.ietf.org; Tue, 06 May 2003 09:14:01 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19D1T7-0003EI-00
	for ietf@ran.ietf.org; Tue, 06 May 2003 08:22:49 -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 IAA17016
	for <ietf@ietf.org>; Tue, 6 May 2003 08:17:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19D1QO-0005Y2-00
	for ietf@ietf.org; Tue, 06 May 2003 08:20:00 -0400
Received: from carwash.centive.com ([65.220.90.249] helo=carwash.centivinc.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19D1QI-0005XH-00
	for ietf@ietf.org; Tue, 06 May 2003 08:19:54 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003050608244412122
 for <ietf@ietf.org>; Tue, 06 May 2003 08:24:44 -0400
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 6 May 2003 08:16:26 -0400
Message-ID: <3EB7A79A.5080308@centive.com>
Date: Tue, 06 May 2003 08:16:26 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Submitting an IETF draft in a specific WG
References: <20030506112933.63293.qmail@web20704.mail.yahoo.com>
In-Reply-To: <20030506112933.63293.qmail@web20704.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 May 2003 12:16:26.0051 (UTC) FILETIME=[50BE5130:01C313C9]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tulip Rasputin wrote:

>My doubt is that if i post my draft on internet-drafts@ietf.org and specify the working group as
>OSPF will this be announced to the OSPF WG. If not then how will they come to know of this draft?
>
Well, the most reliable way is to tell them yourself--post to the WG 
mailing list.

-- 
/=================================================================\
|John Stracke      |jstracke@centive.com                          |
|Principal Engineer|http://www.centive.com                        |
|Centive           |My opinions are my own.                       |
|=================================================================|
|"If nobody believes what I say, I feel ineffective." "Oh, I don't|
|believe that."                                                   |
\=================================================================/





From owner-ietf@ietf.org  Tue May  6 09:55:28 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21563;
	Tue, 6 May 2003 09:55:28 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19D2Uy-00056y-00
	for ietf-list@ran.ietf.org; Tue, 06 May 2003 09:28:48 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19D2GE-0003If-00
	for ietf@ran.ietf.org; Tue, 06 May 2003 09:13:34 -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 JAA19862
	for <ietf@ietf.org>; Tue, 6 May 2003 09:08:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19D2Dj-0006d6-00
	for ietf@ietf.org; Tue, 06 May 2003 09:10:59 -0400
Received: from zydeco.netbusters.com ([66.92.86.178])
	by ietf-mx with esmtp (Exim 4.12)
	id 19D2De-0006cC-00
	for ietf@ietf.org; Tue, 06 May 2003 09:10:54 -0400
Received: by zydeco.netbusters.com (Postfix, from userid 513)
	id EA0B7B6418; Tue,  6 May 2003 13:10:40 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
	by zydeco.netbusters.com (Postfix) with ESMTP
	id E6E9E7EC1D; Tue,  6 May 2003 09:10:40 -0400 (EDT)
Date: Tue, 6 May 2003 09:10:40 -0400 (EDT)
From: Donald Eastlake 3rd <dee3@torque.pothole.com>
X-X-Sender: dee3@zydeco.netbusters.com
To: Tulip Rasputin <tulip_rasputin@yahoo.ca>
Cc: ietf@ietf.org
Subject: Re: Submitting an IETF draft in a specific WG
In-Reply-To: <20030506112933.63293.qmail@web20704.mail.yahoo.com>
Message-ID: <Pine.LNX.4.44.0305060903210.21734-100000@zydeco.netbusters.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

I don't see how this can be a problem since, if your personnal draft is
only announced on the IETF Announce list, you can just forward that
announcement to relevant working group mailing lists. But I have found
that if I include a simple request in the cover mail with the draft to
internet-drafts that the announcement also be posted to some specific
working group mailing list, that request is usually complied with.

Donald

PS: If your intent is that the draft actually become a working group
draft, be listed on the working group charter page, be under working
group change control, etc., you need to talk to the working group chair.

======================================================================
 Donald E. Eastlake 3rd                       dee3@torque.pothole.com
 155 Beaver Street              +1-508-634-2066(h) +1-508-851-8280(w)
 Milford, MA 01757 USA                   Donald.Eastlake@motorola.com

On Tue, 6 May 2003, Tulip Rasputin wrote:

> Date: Tue, 6 May 2003 07:29:33 -0400 (EDT)
> From: Tulip Rasputin <tulip_rasputin@yahoo.ca>
> To: ietf@ietf.org
> Subject: Submitting an IETF draft in a specific WG
> 
> Folks,
> I have written a draft and want to post it on a specific IETF WG, say the OSPF WG. How can i then
> assure that the draft which i post gets announced to that particular WG also apart from the
> general IETF announcement list.
> 
> My doubt is that if i post my draft on internet-drafts@ietf.org and specify the working group as
> OSPF will this be announced to the OSPF WG. If not then how will they come to know of this draft?
> 
> I have a doubt that the drafts may be only announced in the WG if they become accepted asworking
> group documents. 
> 
> Please help me clarify this.
> 
> Should i just send a mail to internet-drafts@ietf.org with my draft as an attachment then?
> 
> Regards,
> Rasputin




From owner-ietf@ietf.org  Tue May  6 17:05:00 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09029;
	Tue, 6 May 2003 17:05:00 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19D9VZ-0004lQ-00
	for ietf-list@ran.ietf.org; Tue, 06 May 2003 16:57:53 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19D9Sd-0004j7-00
	for ietf@ran.ietf.org; Tue, 06 May 2003 16:54:51 -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 QAA08175;
	Tue, 6 May 2003 16:50:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19D9Q3-0002Hb-00; Tue, 06 May 2003 16:52:11 -0400
Received: from shell4.bayarea.net ([209.128.82.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19D9Q2-0002HS-00; Tue, 06 May 2003 16:52:10 -0400
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h46Kqx930853;
	Tue, 6 May 2003 13:52:59 -0700
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Tue, 6 May 2003 13:52:57 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: ietf@ietf.org
cc: ietf-web@ietf.org
Subject: Minutes from IESG meetings
In-Reply-To: <20030505162034.1ef673c4.moore@cs.utk.edu>
Message-ID: <Pine.LNX.4.10.10305061322100.20512-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 5 May 2003, Keith Moore, in a message to the
problem-statement@alvestrand.no mailing list, wrote:
> >  We do not even get real meeting minutes of the IESG meetings. 
> 
> hmm, they used to be at [ http://ftp.ietf.org/iesg/ ]
> but it seems that they have stopped being updated...

Indeed, the most recent minutes file posted there is iesg.2003-02-06
and it appeared on 24-Feb-2003.  I have asked ietf-web@ietf.org
twice before and nothing has happened ... can we please have this
directory updated?

Thanks,

//cmh




From owner-ietf@ietf.org  Wed May  7 03:24:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19084;
	Wed, 7 May 2003 03:24:18 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19DJBY-0004mZ-00
	for ietf-list@ran.ietf.org; Wed, 07 May 2003 03:17:52 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19DJ8B-0004ks-00
	for ietf@ran.ietf.org; Wed, 07 May 2003 03:14:23 -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 DAA18813;
	Wed, 7 May 2003 03:09:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19DJ5U-0005zf-00; Wed, 07 May 2003 03:11:36 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19DJ5T-0005zC-00; Wed, 07 May 2003 03:11:36 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id CFF0B623D6; Wed,  7 May 2003 09:11:57 +0200 (CEST)
Date: Wed, 07 May 2003 09:11:57 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: "C. M. Heard" <heard@pobox.com>, ietf@ietf.org
Cc: ietf-web@ietf.org
Subject: Re: Minutes from IESG meetings
Message-ID: <1139900000.1052291517@askvoll.hjemme.alvestrand.no>
In-Reply-To: <Pine.LNX.4.10.10305061322100.20512-100000@shell4.bayarea.net>
References:  <Pine.LNX.4.10.10305061322100.20512-100000@shell4.bayarea.net>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

magic has happened - iesg.2003-04-17 appeared on May 2, and 3 preceeding 
IESG telechats appeared on May 6.

Hopefully the process bug has been fixed.

                Harald

--On tirsdag, mai 06, 2003 13:52:57 -0700 "C. M. Heard" <heard@pobox.com> 
wrote:

> On Mon, 5 May 2003, Keith Moore, in a message to the
> problem-statement@alvestrand.no mailing list, wrote:
>> >  We do not even get real meeting minutes of the IESG meetings.
>>
>> hmm, they used to be at [ http://ftp.ietf.org/iesg/ ]
>> but it seems that they have stopped being updated...
>
> Indeed, the most recent minutes file posted there is iesg.2003-02-06
> and it appeared on 24-Feb-2003.  I have asked ietf-web@ietf.org
> twice before and nothing has happened ... can we please have this
> directory updated?
>
> Thanks,
>
> //cmh
>
>
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it, which
> is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on
> what to pass are made solely by Raffaele D'Albenzio.
>





From owner-ietf@ietf.org  Thu May  8 10:51:30 2003
Received: from asgard.ietf.org ([10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25612
	for <ietf-web-archive@odin.ietf.org>; Thu, 8 May 2003 10:51:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19DmW8-0006G7-Vu
	for ietf-list@asgard.ietf.org; Thu, 08 May 2003 10:37:04 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19DmRI-0006Ek-7e
	for ietf@asgard.ietf.org; Thu, 08 May 2003 10:32:04 -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 KAA24943
	for <ietf@ietf.org>; Thu, 8 May 2003 10:29:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19DmQO-0003AU-00
	for ietf@ietf.org; Thu, 08 May 2003 10:31:08 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19DmQM-0003AM-00
	for ietf@ietf.org; Thu, 08 May 2003 10:31:07 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 4A23F62590; Thu,  8 May 2003 16:31:28 +0200 (CEST)
Date: Thu, 08 May 2003 16:31:28 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org, problem-statement@alvestrand.no
Subject: NON-WG LAST CALL on the IESG charter?????? (fwd)
Message-ID: <10600000.1052404288@askvoll.hjemme.alvestrand.no>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

FYI:
I just sent the enclosed message to the POISED list.
If you could direct comments there or to me directly, I'd be grateful.

                         Harald

---------- Forwarded Message ----------
Date: torsdag, mai 08, 2003 15:22:19 +0200
From: Harald Tveit Alvestrand <harald@Alvestrand.no>
To: poised@lists.tislabs.com
Cc:
Subject: NON-WG LAST CALL on the IESG charter??????

Folks,

apart from Dave Crocker's proposed change to the first paragraph, I have
had very few comments on version -02 of the IESG charter.

I have also heard one comment (in the nomcom WG) that the IESG charter
should have provisions for appointing an interim IETF chair in the case
where the IETF chair is unable to function, for the time before the Nomcom
completes the task of picking a new one. I suggest stating that the IESG
picks an AD from its own membership to function as the interim chair, and
make no other comment on it.

If I hear no further comments or objections, I intend to publish an -03
version with these changes, and then make an IETF-wide Last Call.

Comments?

                Harald Alvestrand





---------- End Forwarded Message ----------





From owner-ietf@ietf.org  Mon May 12 23:41:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13325
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 May 2003 23:41:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19FQQV-00064u-MU
	for ietf-list@asgard.ietf.org; Mon, 12 May 2003 23:26:03 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19FQLp-00063i-MW
	for ietf@asgard.ietf.org; Mon, 12 May 2003 23:21:13 -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 XAA12537
	for <ietf@ietf.org>; Mon, 12 May 2003 23:18:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19FQKm-0006du-00
	for ietf@ietf.org; Mon, 12 May 2003 23:20:08 -0400
Received: from web20711.mail.yahoo.com ([66.163.169.152])
	by ietf-mx with smtp (Exim 4.12)
	id 19FQKm-0006dr-00
	for ietf@ietf.org; Mon, 12 May 2003 23:20:08 -0400
Message-ID: <20030513032111.61250.qmail@web20711.mail.yahoo.com>
Received: from [210.118.108.254] by web20711.mail.yahoo.com via HTTP; Mon, 12 May 2003 23:21:11 EDT
Date: Mon, 12 May 2003 23:21:11 -0400 (EDT)
From: Tulip Rasputin <tulip_rasputin@yahoo.ca>
Subject: Time Taken to Announce Draft?
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi,
I submitted an Internet-Draft by attaching a copy of it and sending a mail to
internet-drafts@ietf.org some 5-6 days back. It has not yet been announced on the
announcement-lists OR the working group it is targetted for.

I wanted to know as to how long does it typically take to get the ID announced.

I did receive an automated reply from the IETF that they have received a copy of my paper.

In the mail to the internet-drafts@ietf.org i wrote that i would want a copy of the announcement
to be CCd to the WG mailing list also. I also wrote my copy-pasted my abstract in the mail.

The subject in the mail was kept as the filename of the draft.

Did i miss something? It'll be close to a week now and it has not yet been announced.

Thanks,
Rasputin

______________________________________________________________________ 
Post your free ad now! http://personals.yahoo.ca



From owner-ietf@ietf.org  Tue May 13 07:37:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04340
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 May 2003 07:37:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19FXuy-0007WI-I4
	for ietf-list@asgard.ietf.org; Tue, 13 May 2003 07:26:00 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19FXs8-0007Uw-H4
	for ietf@asgard.ietf.org; Tue, 13 May 2003 07:23:04 -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 HAA04013
	for <ietf@ietf.org>; Tue, 13 May 2003 07:20:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19FXr3-0001m3-00
	for ietf@ietf.org; Tue, 13 May 2003 07:21:57 -0400
Received: from unknown-1-11.windriver.com ([147.11.1.11] helo=mail.wrs.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19FXr3-0001lU-00
	for ietf@ietf.org; Tue, 13 May 2003 07:21:57 -0400
Received: from IDLEWYLDE.windriver.com ([147.11.233.27])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id EAA07163;
	Tue, 13 May 2003 04:22:25 -0700 (PDT)
Message-Id: <5.1.0.14.2.20030513071015.048795f0@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 13 May 2003 07:18:33 -0400
To: Tulip Rasputin <tulip_rasputin@yahoo.ca>
From: Margaret Wasserman <mrw@windriver.com>
Subject: Re: Time Taken to Announce Draft?
Cc: ietf@ietf.org
In-Reply-To: <20030513032111.61250.qmail@web20711.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk


Hi Rasputin,

At 11:21 PM 5/12/2003 -0400, Tulip Rasputin wrote:
>I submitted an Internet-Draft by attaching a copy of it and sending a mail to
>internet-drafts@ietf.org some 5-6 days back. It has not yet been announced 
>on the
>announcement-lists OR the working group it is targetted for.
>
>I wanted to know as to how long does it typically take to get the ID 
>announced.

It usually takes 1-2 business days, assuming that the draft meets the
criteria for submission.  However, the delay is sensitive to the number
of drafts submitted, vacations and holidays for the I-D administrator,
etc.  The I-D administrator is located on the east coast of the U.S.

Your draft should meet the "Guidelines to Authors of Internet Drafts".
The guidelines can be found at:

http://www.ietf.org/ietf/1id-guidelines.txt

If you submitted the draft as a WG draft (file name = 'draft-ietf-*"),
then it may take longer, as the I-D administrator will need to wait
for approval from your WG chairs.

>Did i miss something? It'll be close to a week now and it has not yet been 
>announced.

I would write to the internet-drafts@ietf.org address and ask what
is happening.

Margaret






From owner-ietf@ietf.org  Fri May 16 06:07:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18041
	for <ietf-web-archive@odin.ietf.org>; Fri, 16 May 2003 06:07:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19GYVz-00029V-0n
	for ietf-list@asgard.ietf.org; Fri, 16 May 2003 02:16:23 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19GYT1-0001LE-5W
	for ietf@asgard.ietf.org; Fri, 16 May 2003 02:13:19 -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 CAA13636
	for <ietf@ietf.org>; Fri, 16 May 2003 02:10:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19GYRr-0004Sy-00
	for ietf@ietf.org; Fri, 16 May 2003 02:12:07 -0400
Received: from ams-msg-core-1.cisco.com ([144.254.74.60])
	by ietf-mx with esmtp (Exim 4.12)
	id 19GYRl-0004St-00
	for ietf@ietf.org; Fri, 16 May 2003 02:12:01 -0400
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4G6ALkQ013086
	for <ietf@ietf.org>; Fri, 16 May 2003 08:10:21 +0200 (MET DST)
Received: from cisco.com (ssh-ams-1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id IAA22669
	for <ietf@ietf.org>; Fri, 16 May 2003 08:12:15 +0200 (MET DST)
Date: Fri, 16 May 2003 08:12:12 +0200
Mime-Version: 1.0 (Apple Message framework v552)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Subject: From Unicode Consortium: Proposed Update of UTR #18: Unicode Regular Expressions
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: ietf@ietf.org
Message-Id: <5529B046-8765-11D7-8624-000A959CF516@cisco.com>
X-Mailer: Apple Mail (2.552)
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id GAA18041

Information from the Unicode Consortium.

   Patrik Fältström
   Liason from IETF to Unicode Consortium

Begin forwarded message:

> Date: fre maj 16, 2003  06:26:52 Europe/Stockholm
> Subject: Proposed Update of UTR #18: Unicode Regular Expressions
>
> There is a new Proposed Update of UTR #18: Unicode Regular
> Expressions. The main changes are the following:
>
> - Now proposed as a UTS, adding Conformance and specific wording in
> each relevant section.
> - Moved hex notation for surrogates from 2.7 Surrogates into 2.1 Hex
> notation.
> - Added 4.6 Context Matching and following.
> - Updated to Unicode 4.0
> - Minor editing
> - Note: paragraphs with major changes are highlighted in this
> document; less substantive wording changes may not be.
>
> This document will be reviewed at the Unicode Technical Meeting
> starting June 10th. If you have any feedback on the proposed update,
> please submit it by June 2nd. The document describes how to submit any
> feedback.
>
> Mark Davis
>




From owner-ietf@ietf.org  Sun May 18 15:33:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15989
	for <ietf-web-archive@odin.ietf.org>; Sun, 18 May 2003 15:33:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19HTWy-0004T6-CN
	for ietf-list@asgard.ietf.org; Sun, 18 May 2003 15:09:12 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19HTWC-0004GP-A4
	for ietf@asgard.ietf.org; Sun, 18 May 2003 15:08:24 -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 PAA14784
	for <ietf@ietf.org>; Sun, 18 May 2003 15:05:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19HTUx-0004to-00
	for ietf@ietf.org; Sun, 18 May 2003 15:07:07 -0400
Received: from bovik.org ([192.220.72.218])
	by ietf-mx with smtp (Exim 4.12)
	id 19HTUw-0004tl-00
	for ietf@ietf.org; Sun, 18 May 2003 15:07:06 -0400
Received: (qmail 41415 invoked by uid 18650); 18 May 2003 19:08:18 -0000
Message-ID: <20030518190818.41413.qmail@bovik.org>
Subject: spammers harvesting RFC contact addresses
To: ietf@ietf.org
Date: Sun, 18 May 2003 12:08:18 -0700 (PDT)
From: James Salsman <james@bovik.org>
Organization: www.bovik.org
X-Mailer: ELM [version 2.5 PL6]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Today I counted that nearly half my spam was sent to the unique address 
that I gave as my contact information in RFC 2586.

It seems that spammer harvesting addresses from RFCs is on the rise.

If anyone wishes to mount a concerted campaign against this practice, 
I volunteer to forward my RFC contact address-based spams to the 
secretariat's designated assistant(s) and/or any volunteers interested 
in the effort.

RFC AUTHORS UNITE AGAINST SPAM!

Best wishes,
James



From owner-ietf@ietf.org  Sun May 18 16:22:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16676
	for <ietf-web-archive@odin.ietf.org>; Sun, 18 May 2003 16:22:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19HUXr-0007nC-Tg
	for ietf-list@asgard.ietf.org; Sun, 18 May 2003 16:14:11 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19HUOQ-0007mS-1x
	for ietf@asgard.ietf.org; Sun, 18 May 2003 16:04:26 -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 QAA16490
	for <ietf@ietf.org>; Sun, 18 May 2003 16:01:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19HUNA-00056o-00
	for ietf@ietf.org; Sun, 18 May 2003 16:03:08 -0400
Received: from dns1.vpop.net ([207.178.248.2] helo=boromir.vpop.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19HUNA-00056l-00
	for ietf@ietf.org; Sun, 18 May 2003 16:03:08 -0400
Received: from [192.168.0.10] (ppp-67-118-247-145.dialup.pltn13.pacbell.net [67.118.247.145])
	by boromir.vpop.net (Postfix) with ESMTP id 25B7E3A6930
	for <ietf@ietf.org>; Sun, 18 May 2003 13:04:21 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <a05111b05baed95aa3262@[192.168.0.10]>
In-Reply-To: <20030518190818.41413.qmail@bovik.org>
References: <20030518190818.41413.qmail@bovik.org>
Date: Sun, 18 May 2003 13:04:19 -0700
To: ietf@ietf.org
From: Ari Ollikainen <Ari@OLTECO.com>
Subject: Re: spammers harvesting RFC contact addresses
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 12:08 PM -0700 5/18/03, James Salsman wrote:
>Today I counted that nearly half my spam was sent to the unique address
>that I gave as my contact information in RFC 2586.
>
	AFAICT, your RFC 2586 contact email is the same as the one
	you've used to post to the IETF list...and other places.
	HOW do you conclude that it was"unique" and that the spammers
	have picked yours up from that RFC?
	
	A google search for "james@bovik.org" returned 180 matches.


 
           +----------------------------------------------+
           | You need only two tools: WD-40 and duct tape.|
           | If it doesn't move and it should, use WD-40. |
           | If it moves and shouldn't, use duct tape.    |
           +----------------------------------------------+




From owner-ietf@ietf.org  Wed May 21 21:39:48 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15062
	for <ietf-web-archive@odin.ietf.org>; Wed, 21 May 2003 21:39:48 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19IemI-0005AU-Oq
	for ietf-list@asgard.ietf.org; Wed, 21 May 2003 21:21:54 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Iehd-00055x-41
	for ietf@asgard.ietf.org; Wed, 21 May 2003 21:17:05 -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 VAA14714
	for <ietf@ietf.org>; Wed, 21 May 2003 21:17:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19IegH-0004BP-00
	for ietf@ietf.org; Wed, 21 May 2003 21:15:41 -0400
Received: from ohsmtp02.ogw.rr.com ([65.24.7.37])
	by ietf-mx with esmtp (Exim 4.12)
	id 19IegF-0004BM-00
	for ietf@ietf.org; Wed, 21 May 2003 21:15:40 -0400
Received: from Ehftrmpug (dhcp065-025-031-153.neo.rr.com [65.25.31.153])
	by ohsmtp02.ogw.rr.com (8.12.5/8.12.2) with SMTP id h4M1GxYU028616
	for <ietf@ietf.org>; Wed, 21 May 2003 21:16:59 -0400 (EDT)
Date: Wed, 21 May 2003 21:16:59 -0400 (EDT)
Message-Id: <200305220116.h4M1GxYU028616@ohsmtp02.ogw.rr.com>
From: anthony <anthony@atkielski.com>
To: ietf@ietf.org
Subject: W32.Klez.E removal tools
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=IET4TsSJlTuCh181r
Sender: owner-ietf@ietf.org
Precedence: bulk

--IET4TsSJlTuCh181r
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>

<FONT>Symantec give you the W32.Klez.E removal tools<br>
W32.Klez.E is a  dangerous virus that spread through email.<br>
<br>
For more information,please visit http://www.Symantec.com</FONT></BODY></HTML>

--IET4TsSJlTuCh181r
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

[Filename: install.exe, Content-Type: application/octet-stream]
The attachment file in the message has been removed by eManager.

--IET4TsSJlTuCh181r

Content-Type: application/octet-stream;
	name=x3dot[1].jpg
Content-Transfer-Encoding: base64
Content-ID: <E92X9537Ce98FL7>

/9j/4AAQSkZJRgABAgEBLAEsAAD/7QFkUGhvdG9zaG9wIDMuMAA4QklNA+0AAAAAABABLAAA
AAEAAQEsAAAAAQABOEJJTQPzAAAAAAAIAAAAAAAAAAA4QklNBAoAAAAAAAEAADhCSU0nEAAA
AAAACgABAAAAAAAAAAI4QklNA/UAAAAAAEgAL2ZmAAEAbGZmAAYAAAAAAAEAL2ZmAAEAoZma
AAYAAAAAAAEAMgAAAAEAWgAAAAYAAAAAAAEANQAAAAEALQAAAAYAAAAAAAE4QklNA/gAAAAA
AHAAAP////////////////////////////8D6AAAAAD/////////////////////////////
A+gAAAAA/////////////////////////////wPoAAAAAP//////////////////////////
//8D6AAAOEJJTQQIAAAAAAAQAAAAAQAAAkAAAAJAAAAAADhCSU0EBgAAAAAABwACAAAAAQEA
//4AJ0ZpbGUgd3JpdHRlbiBieSBBZG9iZSBQaG90b3Nob3CoIDQuMAD/7gAOQWRvYmUAZIAA
AAAB/9sAhAAIBgYGBgYIBgYIDAgHCAwOCggICg4QDQ0ODQ0QEQwMDAwMDBEMDAwMDAwMDAwM
DAwMDAwMDAwMDAwMDAwMDAwMAQkICAkKCQsJCQsOCw0LDhEODg4OEREMDAwMDBERDAwMDAwM
EQwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAz/wAARCAACAAIDASIAAhEBAxEB/90ABAAB
/8QBogAAAAcBAQEBAQAAAAAAAAAABAUDAgYBAAcICQoLAQACAgMBAQEBAQAAAAAAAAABAAID
BAUGBwgJCgsQAAIBAwMCBAIGBwMEAgYCcwECAxEEAAUhEjFBUQYTYSJxgRQykaEHFbFCI8FS
0eEzFmLwJHKC8SVDNFOSorJjc8I1RCeTo7M2F1RkdMPS4ggmgwkKGBmElEVGpLRW01UoGvLj
88TU5PRldYWVpbXF1eX1ZnaGlqa2xtbm9jdHV2d3h5ent8fX5/c4SFhoeIiYqLjI2Oj4KTlJ
WWl5iZmpucnZ6fkqOkpaanqKmqq6ytrq+hEAAgIBAgMFBQQFBgQIAwNtAQACEQMEIRIxQQVR
E2EiBnGBkTKhsfAUwdHhI0IVUmJy8TMkNEOCFpJTJaJjssIHc9I14kSDF1STCAkKGBkmNkUa
J2R0VTfyo7PDKCnT4/OElKS0xNTk9GV1hZWltcXV5fVGVmZ2hpamtsbW5vZHV2d3h5ent8fX
5/c4SFhoeIiYqLjI2Oj4OUlZaXmJmam5ydnp+So6SlpqeoqaqrrK2ur6/9oADAMBAAIRAxEA
PwDz/mzZsVf/2T==
--IET4TsSJlTuCh181r--



From owner-ietf@ietf.org  Thu May 22 15:09:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25818
	for <ietf-web-archive@odin.ietf.org>; Thu, 22 May 2003 15:09:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19IvKp-0000gU-Hs
	for ietf-list@asgard.ietf.org; Thu, 22 May 2003 15:02:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19IvER-0005xe-IN
	for ietf@asgard.ietf.org; Thu, 22 May 2003 14:56:03 -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 OAA24681
	for <ietf@ietf.org>; Thu, 22 May 2003 14:56:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19IvD4-0004GR-00
	for ietf@ietf.org; Thu, 22 May 2003 14:54:38 -0400
Received: from ip166.usw12.rb1.bel.nwlink.com ([209.20.253.166] helo=ran.psg.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19IvD4-0004GO-00
	for ietf@ietf.org; Thu, 22 May 2003 14:54:38 -0400
Received: from localhost ([127.0.0.1] helo=ran.psg.com)
	by ran.psg.com with esmtp (Exim 4.20)
	id 19IvEP-000GAb-8w
	for ietf@ietf.org; Thu, 22 May 2003 11:56:01 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 22 May 2003 11:56:00 -0700
To: ietf@ietf.org
Subject: mail loop warning to list admins
Message-Id: <E19IvEP-000GAb-8w@ran.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

very very serious mail loops today, like hundreds of messages an
hour.  the cause seems to be braja@tellium.com.  as the looper
seems to muck the headers, normal loop prevention seems not to
work.  i have commented that address out of lists, and the flood is
abating.

randy




From owner-ietf@ietf.org  Fri May 23 17:35:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26857
	for <ietf-web-archive@odin.ietf.org>; Fri, 23 May 2003 17:35:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JJcN-0002W8-Mn
	for ietf-list@asgard.ietf.org; Fri, 23 May 2003 16:58:23 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JJTe-0002PU-1A
	for ietf@asgard.ietf.org; Fri, 23 May 2003 16:49:22 -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 QAA25472;
	Fri, 23 May 2003 16:49:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JJSE-0002Te-00; Fri, 23 May 2003 16:47:54 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JJSE-0002Tb-00; Fri, 23 May 2003 16:47:54 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h4NKnJk16144;
        Fri, 23 May 2003 16:49:19 -0400 (EDT)
Date: Fri, 23 May 2003 16:49:19 -0400
From: Keith Moore <moore@cs.utk.edu>
To: iesg@ietf.org
Cc: moore@cs.utk.edu, iesg-secretary@ietf.org, ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
Message-Id: <20030523164919.164a908e.moore@cs.utk.edu>
In-Reply-To: <200305231957.PAA23163@ietf.org>
References: <200305231957.PAA23163@ietf.org>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

IMHO, this is totally unacceptable for Proposed Standard status.

1. it recommends using MIME, and presumably SMTP, as a means of
tunneling IP packets.  Even considering that a content-type for
transmitting IP over MIME might be useful for "monitoring, analysis,
debugging, or illustrative purposes", that doesn't mean that we should
standardize the use of this content-type for tunneling IP packets in
operational use.  Neither the SMTP protocol nor SMTP implementations are
designed for this purpose, and the delays and jitter involved in sending
IP over SMTP make it marginally suitable at best - certainly not
something that can be expected to scale, or to work satisfactorily over
most of the Internet.  In other words, this proposal would fail to meet
criteria that we routinely apply to standards-track documents.

Furthermore, this document makes no attempt to narrow its applicability;
rather, it specifically claims that use of IP-over-MIME as a tunneling
mechanism is within scope.

2. the Introduction recommends use of NAT, which is nonstandard and
known to often be a harmful practice.  

3. Several references cited as Informative are actually Normative -
in that you can't implement the IP over MIME protocol without them.
Among these references are the reference to IETF documents which are
not on the standards track.

If we approve this as PS we are essentially recommending a stupid
practice.  At best, it's embarassing to IETF to do so; at worst, we are
endorsing an operational practice that has little practical use other
than to circumvent existing security measures.  Even if those security
measures are poorly chosen, it is not appropriate for IETF to recommend
their circumvention.

Even assuming there is a legitimate use for this, there is no need to
standardize this content-type, since content-type definitions do not
need to be on the standards track.

Keith



From owner-ietf@ietf.org  Fri May 23 18:29:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28878
	for <ietf-web-archive@odin.ietf.org>; Fri, 23 May 2003 18:29:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JKrz-0001Td-0d
	for ietf-list@asgard.ietf.org; Fri, 23 May 2003 18:18:35 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JKn6-0008Vh-Mg
	for ietf@asgard.ietf.org; Fri, 23 May 2003 18:13:32 -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 SAA28364;
	Fri, 23 May 2003 18:13:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JKlh-00033t-00; Fri, 23 May 2003 18:12:05 -0400
Received: from ds20-1.cc.swin.edu.au ([136.186.1.150] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 19JKlg-00033q-00; Fri, 23 May 2003 18:12:04 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2/8.9.3) with ESMTP id IAA1964919;
	Sat, 24 May 2003 08:13:26 +1000 (EST)
Message-ID: <3ECE9D05.4C530F51@swin.edu.au>
Date: Sat, 24 May 2003 08:13:25 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.8 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: iesg@ietf.org
CC: ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
References: <200305231957.PAA23163@ietf.org> <20030523164919.164a908e.moore@cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Keith Moore wrote:
	[..]
> If we approve this as PS we are essentially recommending a stupid
> practice.  At best, it's embarassing to IETF to do so;

You mean this _isn't_ an April 1st I-D that somehow "got away" into
the approval pipeline?

cheers,
gja



From owner-ietf@ietf.org  Fri May 23 19:11:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29770
	for <ietf-web-archive@odin.ietf.org>; Fri, 23 May 2003 19:11:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JLPd-0002Ko-Ux
	for ietf-list@asgard.ietf.org; Fri, 23 May 2003 18:53:21 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JLL4-0002Hy-OL
	for ietf@asgard.ietf.org; Fri, 23 May 2003 18:48:38 -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 SAA29250;
	Fri, 23 May 2003 18:48:35 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JLJf-0003FM-00; Fri, 23 May 2003 18:47:11 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JLJe-0003FJ-00; Fri, 23 May 2003 18:47:10 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h4NMmXP9012389;
	Fri, 23 May 2003 18:48:33 -0400
Message-Id: <200305232248.h4NMmXP9012389@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Keith Moore <moore@cs.utk.edu>
Cc: iesg@ietf.org, iesg-secretary@ietf.org, ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard 
In-Reply-To: Your message of "Fri, 23 May 2003 16:49:19 EDT."
             <20030523164919.164a908e.moore@cs.utk.edu> 
References: <200305231957.PAA23163@ietf.org>
            <20030523164919.164a908e.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1344352038P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 23 May 2003 18:48:33 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1344352038P
Content-Type: text/plain; charset=us-ascii

On Fri, 23 May 2003 16:49:19 EDT, Keith Moore said:

(I agree with the rest of what Keith said - however, there's one
area that's still up for grabs..)

> tunneling IP packets.  Even considering that a content-type for
> transmitting IP over MIME might be useful for "monitoring, analysis,
> debugging, or illustrative purposes", that doesn't mean that we should

Do you think there *is* a use for monitoring/analysis/etc?  And if so,
does the draft address *that* need, or could it be made to do so?

Although I concur that using it for tunneling is right up there with avian
carriers, I personally could use something a bit more standard than just
attaching tcpdump or ethereal captures to an e-mail for sending around
previously captured packets.


--==_Exmh_-1344352038P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+zqVBcC3lWbTT17ARArEEAJwIrfFqcyFkqjrF7V3eJHUMwz6IuwCgvXQ5
ADQVT/Iy8q9bewWZq5+8LO4=
=gKHp
-----END PGP SIGNATURE-----

--==_Exmh_-1344352038P--



From owner-ietf@ietf.org  Fri May 23 19:16:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29932
	for <ietf-web-archive@odin.ietf.org>; Fri, 23 May 2003 19:16:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JLf2-0002bC-3q
	for ietf-list@asgard.ietf.org; Fri, 23 May 2003 19:09:16 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JLSW-0002LB-0s
	for ietf@asgard.ietf.org; Fri, 23 May 2003 18:56:20 -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 SAA29461;
	Fri, 23 May 2003 18:56:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JLR6-0003Ix-00; Fri, 23 May 2003 18:54:52 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JLR5-0003Iu-00; Fri, 23 May 2003 18:54:51 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h4NMuGk17225;
        Fri, 23 May 2003 18:56:16 -0400 (EDT)
Date: Fri, 23 May 2003 18:56:15 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Valdis.Kletnieks@vt.edu
Cc: moore@cs.utk.edu, iesg@ietf.org, iesg-secretary@ietf.org, ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
Message-Id: <20030523185615.63671468.moore@cs.utk.edu>
In-Reply-To: <200305232248.h4NMmXP9012389@turing-police.cc.vt.edu>
References: <200305231957.PAA23163@ietf.org>
	<20030523164919.164a908e.moore@cs.utk.edu>
	<200305232248.h4NMmXP9012389@turing-police.cc.vt.edu>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> (I agree with the rest of what Keith said - however, there's one
> area that's still up for grabs..)
> 
> > tunneling IP packets.  Even considering that a content-type for
> > transmitting IP over MIME might be useful for "monitoring, analysis,
> > debugging, or illustrative purposes", that doesn't mean that we
> > should
> 
> Do you think there *is* a use for monitoring/analysis/etc?  And if so,
> does the draft address *that* need, or could it be made to do so?

I expect that it does address that need.  though for
monitoring/analysis/etc you might like some other information, like the
date/time/location at which the packet was observed, and perhaps these
could go in content-type parameters.

but from looking at the parameters that are defined, it really doesn't
seem like the intended purpose of this type is monitoring/analysis/etc.




From owner-ietf@ietf.org  Fri May 23 21:34:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03125
	for <ietf-web-archive@odin.ietf.org>; Fri, 23 May 2003 21:34:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JNko-0004no-Az
	for ietf-list@asgard.ietf.org; Fri, 23 May 2003 21:23:22 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JNkS-0004ms-OB
	for ietf@asgard.ietf.org; Fri, 23 May 2003 21:23:00 -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 VAA02925;
	Fri, 23 May 2003 21:22:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JNj3-0004Hn-00; Fri, 23 May 2003 21:21:33 -0400
Received: from zydeco.netbusters.com ([66.92.86.178])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JNj2-0004Hk-00; Fri, 23 May 2003 21:21:32 -0400
Received: by zydeco.netbusters.com (Postfix, from userid 513)
	id 90DEDB63FB; Sat, 24 May 2003 01:22:58 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
	by zydeco.netbusters.com (Postfix) with ESMTP
	id 8F6857EC1E; Fri, 23 May 2003 21:22:58 -0400 (EDT)
Date: Fri, 23 May 2003 21:22:58 -0400 (EDT)
From: Donald Eastlake 3rd <dee3@torque.pothole.com>
X-X-Sender: dee3@zydeco.netbusters.com
To: Keith Moore <moore@cs.utk.edu>
Cc: iesg@ietf.org, <ietf@ietf.org>
Subject: Re: Last Call: IP over MIME to Proposed Standard
In-Reply-To: <20030523185615.63671468.moore@cs.utk.edu>
Message-ID: <Pine.LNX.4.44.0305232120540.15789-100000@zydeco.netbusters.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Keith,

Thanks for your excellent suggestions for additional parameters to 
improve this MIME type.

What would you think of Experimental status for it?

Thanks,
Donald
======================================================================
 Donald E. Eastlake 3rd                       dee3@torque.pothole.com
 155 Beaver Street              +1-508-634-2066(h) +1-508-851-8280(w)
 Milford, MA 01757 USA                   Donald.Eastlake@motorola.com

On Fri, 23 May 2003, Keith Moore wrote:

> Date: Fri, 23 May 2003 18:56:15 -0400
> From: Keith Moore <moore@cs.utk.edu>
> To: Valdis.Kletnieks@vt.edu
> Cc: moore@cs.utk.edu, iesg@ietf.org, iesg-secretary@ietf.org, ietf@ietf.org
> Subject: Re: Last Call: IP over MIME to Proposed Standard
> 
> > (I agree with the rest of what Keith said - however, there's one
> > area that's still up for grabs..)
> > 
> > > tunneling IP packets.  Even considering that a content-type for
> > > transmitting IP over MIME might be useful for "monitoring, analysis,
> > > debugging, or illustrative purposes", that doesn't mean that we
> > > should
> > 
> > Do you think there *is* a use for monitoring/analysis/etc?  And if so,
> > does the draft address *that* need, or could it be made to do so?
> 
> I expect that it does address that need.  though for
> monitoring/analysis/etc you might like some other information, like the
> date/time/location at which the packet was observed, and perhaps these
> could go in content-type parameters.
> 
> but from looking at the parameters that are defined, it really doesn't
> seem like the intended purpose of this type is monitoring/analysis/etc.
> 
> 
> 




From owner-ietf@ietf.org  Fri May 23 22:03:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03796
	for <ietf-web-archive@odin.ietf.org>; Fri, 23 May 2003 22:03:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JO8y-0005Fq-7H
	for ietf-list@asgard.ietf.org; Fri, 23 May 2003 21:48:20 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JO83-0005F0-HS
	for ietf@asgard.ietf.org; Fri, 23 May 2003 21:47:23 -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 VAA03465;
	Fri, 23 May 2003 21:47:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JO6d-0004UI-00; Fri, 23 May 2003 21:45:55 -0400
Received: from turkey.mail.pas.earthlink.net ([207.217.120.126])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JO6d-0004TA-00; Fri, 23 May 2003 21:45:55 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by turkey.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19JO67-0004oM-00; Fri, 23 May 2003 18:45:23 -0700
Date: Fri, 23 May 2003 21:44:09 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Donald Eastlake 3rd <dee3@torque.pothole.com>
Cc: moore@cs.utk.edu, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
Message-Id: <20030523214409.78c58a24.moore@cs.utk.edu>
In-Reply-To: <Pine.LNX.4.44.0305232120540.15789-100000@zydeco.netbusters.com>
References: <20030523185615.63671468.moore@cs.utk.edu>
	<Pine.LNX.4.44.0305232120540.15789-100000@zydeco.netbusters.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Thanks for your excellent suggestions for additional parameters to 
> improve this MIME type.
> 
> What would you think of Experimental status for it?

it would be a lot closer to meeting the criteria for Experimental.
oerhaps you'd like to describe the experiment?

Keith



From owner-ietf@ietf.org  Fri May 23 22:27:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04254
	for <ietf-web-archive@odin.ietf.org>; Fri, 23 May 2003 22:27:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JOc1-0005md-Gd
	for ietf-list@asgard.ietf.org; Fri, 23 May 2003 22:18:21 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JOYj-0005ik-J8
	for ietf@asgard.ietf.org; Fri, 23 May 2003 22:14: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 WAA04081;
	Fri, 23 May 2003 22:14:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JOXJ-0004gM-00; Fri, 23 May 2003 22:13:29 -0400
Received: from zydeco.netbusters.com ([66.92.86.178])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JOXJ-0004gJ-00; Fri, 23 May 2003 22:13:29 -0400
Received: by zydeco.netbusters.com (Postfix, from userid 513)
	id E7386B63FB; Sat, 24 May 2003 02:14:55 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
	by zydeco.netbusters.com (Postfix) with ESMTP
	id E62857EC1E; Fri, 23 May 2003 22:14:55 -0400 (EDT)
Date: Fri, 23 May 2003 22:14:55 -0400 (EDT)
From: Donald Eastlake 3rd <dee3@torque.pothole.com>
X-X-Sender: dee3@zydeco.netbusters.com
To: Keith Moore <moore@cs.utk.edu>
Cc: iesg@ietf.org, <ietf@ietf.org>
Subject: Re: Last Call: IP over MIME to Proposed Standard
In-Reply-To: <20030523214409.78c58a24.moore@cs.utk.edu>
Message-ID: <Pine.LNX.4.44.0305232213110.15789-100000@zydeco.netbusters.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Sure, one  experiment would be what the actual performance of an IP over 
MIME tunnel was.

Thanks,
Donald
======================================================================
 Donald E. Eastlake 3rd                       dee3@torque.pothole.com
 155 Beaver Street              +1-508-634-2066(h) +1-508-851-8280(w)
 Milford, MA 01757 USA                   Donald.Eastlake@motorola.com

On Fri, 23 May 2003, Keith Moore wrote:

> Date: Fri, 23 May 2003 21:44:09 -0400
> From: Keith Moore <moore@cs.utk.edu>
> To: Donald Eastlake 3rd <dee3@torque.pothole.com>
> Cc: moore@cs.utk.edu, iesg@ietf.org, ietf@ietf.org
> Subject: Re: Last Call: IP over MIME to Proposed Standard
> 
> > Thanks for your excellent suggestions for additional parameters to 
> > improve this MIME type.
> > 
> > What would you think of Experimental status for it?
> 
> it would be a lot closer to meeting the criteria for Experimental.
> oerhaps you'd like to describe the experiment?
> 
> Keith




From owner-ietf@ietf.org  Fri May 23 22:45:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04666
	for <ietf-web-archive@odin.ietf.org>; Fri, 23 May 2003 22:45:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JOc1-0005mw-P5
	for ietf-list@asgard.ietf.org; Fri, 23 May 2003 22:18:21 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JOaX-0005lY-IL
	for ietf@asgard.ietf.org; Fri, 23 May 2003 22:16:49 -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 WAA04125;
	Fri, 23 May 2003 22:16:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JOZ8-0004hI-00; Fri, 23 May 2003 22:15:22 -0400
Received: from ip166.usw12.rb1.bel.nwlink.com ([209.20.253.166] helo=ran.psg.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19JOZ7-0004hE-00; Fri, 23 May 2003 22:15:21 -0400
Received: from localhost ([127.0.0.1] helo=ran.psg.com)
	by ran.psg.com with esmtp (Exim 4.20)
	id 19JOa2-000MA0-Us; Fri, 23 May 2003 19:16:19 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 23 May 2003 19:16:18 -0700
To: grenville armitage <garmitage@swin.edu.au>
Cc: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
References: <200305231957.PAA23163@ietf.org>
	<20030523164919.164a908e.moore@cs.utk.edu>
	<3ECE9D05.4C530F51@swin.edu.au>
Message-Id: <E19JOa2-000MA0-Us@ran.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> You mean this _isn't_ an April 1st I-D that somehow "got away" into
> the approval pipeline?

someone started screaming that the iesg was holding up a document :-)




From owner-ietf@ietf.org  Fri May 23 22:52:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04892
	for <ietf-web-archive@odin.ietf.org>; Fri, 23 May 2003 22:52:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JP0H-0006HE-UQ
	for ietf-list@asgard.ietf.org; Fri, 23 May 2003 22:43:25 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JOrF-0006BB-S6
	for ietf@asgard.ietf.org; Fri, 23 May 2003 22:34:05 -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 WAA04467;
	Fri, 23 May 2003 22:34:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JOpp-0004oK-00; Fri, 23 May 2003 22:32:37 -0400
Received: from mallard.mail.pas.earthlink.net ([207.217.120.48])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JOpo-0004oH-00; Fri, 23 May 2003 22:32:36 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by mallard.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19JOr5-0005Hy-00; Fri, 23 May 2003 19:33:55 -0700
Date: Fri, 23 May 2003 22:32:41 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Donald Eastlake 3rd <dee3@torque.pothole.com>
Cc: moore@cs.utk.edu, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
Message-Id: <20030523223241.460dacaf.moore@cs.utk.edu>
In-Reply-To: <Pine.LNX.4.44.0305232213110.15789-100000@zydeco.netbusters.com>
References: <20030523214409.78c58a24.moore@cs.utk.edu>
	<Pine.LNX.4.44.0305232213110.15789-100000@zydeco.netbusters.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Sure, one  experiment would be what the actual performance of an IP over 
> MIME tunnel was.

sounds good.  why not specify a methodology so that the test is repeatable
and the results from various experiments are comperable, and ask people to 
report their  results to you, for you to summarize via a web page or other 
means?



From owner-ietf@ietf.org  Fri May 23 23:34:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05694
	for <ietf-web-archive@odin.ietf.org>; Fri, 23 May 2003 23:34:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JPOW-0007A5-WB
	for ietf-list@asgard.ietf.org; Fri, 23 May 2003 23:08:28 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JPHH-00071w-6k
	for ietf@asgard.ietf.org; Fri, 23 May 2003 23:00:59 -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 XAA05120;
	Fri, 23 May 2003 23:00:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JPFq-000509-00; Fri, 23 May 2003 22:59:30 -0400
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19JPFp-000501-00; Fri, 23 May 2003 22:59:29 -0400
Received: from adsl-67-126-140-113.dsl.irvnca.pacbell.net (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h4O30aN14858;
	Fri, 23 May 2003 20:00:36 -0700
Date: Fri, 23 May 2003 20:00:39 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/4) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <3034502612.20030523200039@brandenburg.com>
To: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
In-Reply-To: <3ECE9D05.4C530F51@swin.edu.au>
References: <200305231957.PAA23163@ietf.org>
 <20030523164919.164a908e.moore@cs.utk.edu> <3ECE9D05.4C530F51@swin.edu.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



guess this is another opportunity for the IETF to prevent an egregious
"mistake":

          <http://www.dtnrg.org/>

We certainly don't want to permit standardization of mechanisms to
support long-term research.

d/

ga> Keith Moore wrote:
ga>         [..]
>> If we approve this as PS we are essentially recommending a stupid
>> practice.  At best, it's embarassing to IETF to do so;

ga> You mean this _isn't_ an April 1st I-D that somehow "got away" into
ga> the approval pipeline?




d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Sat May 24 00:08:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06435
	for <ietf-web-archive@odin.ietf.org>; Sat, 24 May 2003 00:08:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JQDu-0007oh-Ki
	for ietf-list@asgard.ietf.org; Sat, 24 May 2003 00:01:34 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JQ47-0007k9-DI
	for ietf@asgard.ietf.org; Fri, 23 May 2003 23:51:27 -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 XAA06029;
	Fri, 23 May 2003 23:51:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JQ2h-0005F8-00; Fri, 23 May 2003 23:49:59 -0400
Received: from hawk.mail.pas.earthlink.net ([207.217.120.22])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JQ2g-0005F5-00; Fri, 23 May 2003 23:49:58 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by hawk.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19JQ40-0005Qh-00; Fri, 23 May 2003 20:51:20 -0700
Date: Fri, 23 May 2003 23:50:06 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: moore@cs.utk.edu, dhc2@dcrocker.net, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
Message-Id: <20030523235006.7fefae69.moore@cs.utk.edu>
In-Reply-To: <3034502612.20030523200039@brandenburg.com>
References: <200305231957.PAA23163@ietf.org>
	<20030523164919.164a908e.moore@cs.utk.edu>
	<3ECE9D05.4C530F51@swin.edu.au>
	<3034502612.20030523200039@brandenburg.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> guess this is another opportunity for the IETF to prevent an egregious
> "mistake":
> 
>           <http://www.dtnrg.org/>
> 
> We certainly don't want to permit standardization of mechanisms to
> support long-term research.

perhaps you could explain, using the criteria in RFC 2026, why Proposed
Standard is either appropriate or necessary for a research project?  



From owner-ietf@ietf.org  Sat May 24 01:17:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07490
	for <ietf-web-archive@odin.ietf.org>; Sat, 24 May 2003 01:17:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JRBf-00005B-2L
	for ietf-list@asgard.ietf.org; Sat, 24 May 2003 01:03:19 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JR2Y-0008Tm-1n
	for ietf@asgard.ietf.org; Sat, 24 May 2003 00:53:54 -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 AAA07193;
	Sat, 24 May 2003 00:53:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JR18-0005aH-00; Sat, 24 May 2003 00:52:26 -0400
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19JR17-0005aC-00; Sat, 24 May 2003 00:52:25 -0400
Received: from adsl-67-126-140-113.dsl.irvnca.pacbell.net (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h4O4rTN18622;
	Fri, 23 May 2003 21:53:29 -0700
Date: Fri, 23 May 2003 21:53:29 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/4) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <18041272266.20030523215329@brandenburg.com>
To: Keith Moore <moore@cs.utk.edu>
CC: dhc2@dcrocker.net, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
In-Reply-To: <20030523235006.7fefae69.moore@cs.utk.edu>
References: <200305231957.PAA23163@ietf.org>
 <20030523164919.164a908e.moore@cs.utk.edu> <3ECE9D05.4C530F51@swin.edu.au>
 <3034502612.20030523200039@brandenburg.com>
 <20030523235006.7fefae69.moore@cs.utk.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith,

>>           <http://www.dtnrg.org/>
>> 
>> We certainly don't want to permit standardization of mechanisms to
>> support long-term research.

KM> perhaps you could explain, using the criteria in RFC 2026, why Proposed
KM> Standard is either appropriate or necessary for a research project?


IP over foo is not exactly packet science, that's why.


d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Sat May 24 01:21:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07663
	for <ietf-web-archive@odin.ietf.org>; Sat, 24 May 2003 01:21:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JRLK-000097-PV
	for ietf-list@asgard.ietf.org; Sat, 24 May 2003 01:13:18 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JRBu-00005D-5h
	for ietf@asgard.ietf.org; Sat, 24 May 2003 01:03:34 -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 BAA07286;
	Sat, 24 May 2003 01:03:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JRAU-0005bx-00; Sat, 24 May 2003 01:02:06 -0400
Received: from falcon.mail.pas.earthlink.net ([207.217.120.74])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JRAT-0005bu-00; Sat, 24 May 2003 01:02:05 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by falcon.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19JRBm-0007JC-00; Fri, 23 May 2003 22:03:26 -0700
Date: Sat, 24 May 2003 01:02:11 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: moore@cs.utk.edu, dhc2@dcrocker.net, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
Message-Id: <20030524010211.1b7c3133.moore@cs.utk.edu>
In-Reply-To: <18041272266.20030523215329@brandenburg.com>
References: <200305231957.PAA23163@ietf.org>
	<20030523164919.164a908e.moore@cs.utk.edu>
	<3ECE9D05.4C530F51@swin.edu.au>
	<3034502612.20030523200039@brandenburg.com>
	<20030523235006.7fefae69.moore@cs.utk.edu>
	<18041272266.20030523215329@brandenburg.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> IP over foo is not exactly packet science, that's why.

nor is it standards-track material.



From owner-ietf@ietf.org  Sat May 24 09:20:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26178
	for <ietf-web-archive@odin.ietf.org>; Sat, 24 May 2003 09:20:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JYkx-0001bh-KY
	for ietf-list@asgard.ietf.org; Sat, 24 May 2003 09:08:15 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JYkM-0001aK-UM
	for ietf@asgard.ietf.org; Sat, 24 May 2003 09:07:38 -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 JAA26014
	for <ietf@ietf.org>; Sat, 24 May 2003 09:07:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JYiw-00007J-00
	for ietf@ietf.org; Sat, 24 May 2003 09:06:10 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JYiv-00007G-00
	for ietf@ietf.org; Sat, 24 May 2003 09:06:09 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h4OD7atU012939;
	Sat, 24 May 2003 09:07:36 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h4OD7Z6o012938;
	Sat, 24 May 2003 09:07:35 -0400
Date: Sat, 24 May 2003 09:07:35 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200305241307.h4OD7Z6o012938@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: Keith Moore <moore@cs.utk.edu>

    >> IP over foo is not exactly packet science, that's why.

    > nor is it standards-track material.

Anything that more than two "real user" entities are going to want to use,
and *might want to inter-operate*, is probably standards-track material.

About the only reason not to do it would be if it was decided that the
design chosen was technologically flawed. However, I think NAT should have
taught the IETF (as bridges taught me) that sometimes what seems
technologically flawed is in fact just what the market needs and wants -
usually for some reason one hasn't sufficiently appreciated.

So I would generally err very much on the side of caution, and stay with the
standard in the first paragraph. (Even if it does sound like an April 1
escapee...)

	Noel



From owner-ietf@ietf.org  Sat May 24 09:26:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26450
	for <ietf-web-archive@odin.ietf.org>; Sat, 24 May 2003 09:26:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JYud-0001eX-BR
	for ietf-list@asgard.ietf.org; Sat, 24 May 2003 09:18:15 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JYqY-0001d7-Kp
	for ietf@asgard.ietf.org; Sat, 24 May 2003 09:14:02 -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 JAA26081;
	Sat, 24 May 2003 09:14:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JYp7-00008s-00; Sat, 24 May 2003 09:12:34 -0400
Received: from [131.227.74.4] (helo=phoebe.eim.surrey.ac.uk ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19JYp7-00008p-00; Sat, 24 May 2003 09:12:33 -0400
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by phoebe.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 19JYqA-0001Ge-00; Sat, 24 May 2003 14:13:38 +0100
Date: Sat, 24 May 2003 14:13:36 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Dave Crocker <dcrocker@brandenburg.com>
cc: Keith Moore <moore@cs.utk.edu>, "" <dhc2@dcrocker.net>, "" <iesg@ietf.org>,
        "" <ietf@ietf.org>
Subject: Re: Last Call: IP over MIME to Proposed Standard
In-Reply-To: <18041272266.20030523215329@brandenburg.com>
Message-ID: <Pine.GSO.4.50.0305241412570.3705-100000@artemis.ee.surrey.ac.uk>
References: <200305231957.PAA23163@ietf.org> <20030523164919.164a908e.moore@cs.utk.edu>
 <3ECE9D05.4C530F51@swin.edu.au> <3034502612.20030523200039@brandenburg.com>
 <20030523235006.7fefae69.moore@cs.utk.edu> <18041272266.20030523215329@brandenburg.com>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-105.6 required=5.5
	tests=BAYES_10,EMAIL_ATTRIBUTION,IN_REP_TO,REFERENCES,
	      REPLY_WITH_QUOTES,USER_AGENT_PINE,USER_IN_WHITELIST
	version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
X-Scanner: exiscan *19JYqA-0001Ge-00*p.l4sx3wRO6* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 23 May 2003, Dave Crocker wrote:

> IP over foo is not exactly packet science, that's why.

Ethertype in MIME would probably be more useful than IP in MIME.

L.

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>



From owner-ietf@ietf.org  Sat May 24 10:06:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27256
	for <ietf-web-archive@odin.ietf.org>; Sat, 24 May 2003 10:06:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JZNg-0002Zj-2I
	for ietf-list@asgard.ietf.org; Sat, 24 May 2003 09:48:16 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JZMd-0002YD-4T
	for ietf@asgard.ietf.org; Sat, 24 May 2003 09:47:11 -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 JAA26705
	for <ietf@ietf.org>; Sat, 24 May 2003 09:47:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JZLC-0000Kl-00
	for ietf@ietf.org; Sat, 24 May 2003 09:45:42 -0400
Received: from mallard.mail.pas.earthlink.net ([207.217.120.48])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JZLB-0000Ki-00
	for ietf@ietf.org; Sat, 24 May 2003 09:45:42 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by mallard.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19JZMT-0005ee-00; Sat, 24 May 2003 06:47:01 -0700
Date: Sat, 24 May 2003 09:45:45 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: moore@cs.utk.edu, ietf@ietf.org, jnc@ginger.lcs.mit.edu
Subject: Re: Last Call: IP over MIME to Proposed Standard
Message-Id: <20030524094545.05de7cf6.moore@cs.utk.edu>
In-Reply-To: <200305241307.h4OD7Z6o012938@ginger.lcs.mit.edu>
References: <200305241307.h4OD7Z6o012938@ginger.lcs.mit.edu>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Anything that more than two "real user" entities are going to want to use,
> and *might want to inter-operate*, is probably standards-track material.

I disagree, and that's not the metric that has traditionally been applied. 
A protocol that doesn't work over the Internet in general, but which only
works in limited environments and for limited groups of users, has not
generally considered suitable for IETF standardization, and this is entirely
appropriate.  IETF's endorsement of a protocol is taken to mean that the
protocol has broad applicability.  IETF doesn't have the resources to 
standardize every protocol that some small group of people might want to use.
Nor would it really serve IETF's purposes for it to do so.  Small groups
of people can agree among themselves how to solve a problem, and they don't
need to require that their solutions be universally applicable; it's only
when you have large numbers of users that you need to impose the criteria
that IETF expects for standards.

> About the only reason not to do it would be if it was decided that the
> design chosen was technologically flawed. However, I think NAT should have
> taught the IETF (as bridges taught me) that sometimes what seems
> technologically flawed is in fact just what the market needs and wants -
> usually for some reason one hasn't sufficiently appreciated.

I agree that the existence of NAT should have helped us recognize legitimate
needs and wants, but that doesn't argue for standardizing NAT either.



From owner-ietf@ietf.org  Sat May 24 14:59:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01968
	for <ietf-web-archive@odin.ietf.org>; Sat, 24 May 2003 14:59:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Jdz9-0002Tb-96
	for ietf-list@asgard.ietf.org; Sat, 24 May 2003 14:43:15 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Jdxy-0002S7-Iw
	for ietf@asgard.ietf.org; Sat, 24 May 2003 14:42:02 -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 OAA01713;
	Sat, 24 May 2003 14:42:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JdwX-0001V3-00; Sat, 24 May 2003 14:40:33 -0400
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19JdwW-0001V0-00; Sat, 24 May 2003 14:40:32 -0400
Received: from ppp-67-126-240-86.dsl.irvnca.pacbell.net (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h4OIejN12415;
	Sat, 24 May 2003 11:40:46 -0700
Date: Sat, 24 May 2003 11:40:49 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/4) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <4446995696.20030524114049@brandenburg.com>
To: Keith Moore <moore@cs.utk.edu>
CC: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
In-Reply-To: <20030524010211.1b7c3133.moore@cs.utk.edu>
References: <200305231957.PAA23163@ietf.org>
 <20030523164919.164a908e.moore@cs.utk.edu> <3ECE9D05.4C530F51@swin.edu.au>
 <3034502612.20030523200039@brandenburg.com>
 <20030523235006.7fefae69.moore@cs.utk.edu>
 <18041272266.20030523215329@brandenburg.com>
 <20030524010211.1b7c3133.moore@cs.utk.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith,


>> IP over foo is not exactly packet science, that's why.
KM> nor is it standards-track material.

Besides the fact that you happen not to like the idea of IP over Mime,
what reason is there to prevent standards-track.  We make IP-over-Foo
specifications standards track all the time.  We do not make a point of
forcing them to Experimental.

So unless there is a compelling technical reason -- especially one
having to do with risk to implementations or the Internet -- then what
is the justification for withholding standards track status (as long as
the specifications is clear and complete)?

d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Sat May 24 15:22:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03708
	for <ietf-web-archive@odin.ietf.org>; Sat, 24 May 2003 15:22:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JeS9-0000jy-Dr
	for ietf-list@asgard.ietf.org; Sat, 24 May 2003 15:13:13 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JeNy-0007tx-1H
	for ietf@asgard.ietf.org; Sat, 24 May 2003 15:08:54 -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 PAA02748;
	Sat, 24 May 2003 15:08:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JeMW-0001dq-00; Sat, 24 May 2003 15:07:24 -0400
Received: from prue.eim.surrey.ac.uk ([131.227.76.5] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19JeMW-0001dn-00; Sat, 24 May 2003 15:07:24 -0400
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 19JeNg-0004hZ-00; Sat, 24 May 2003 20:08:36 +0100
Date: Sat, 24 May 2003 20:08:34 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Dave Crocker <dcrocker@brandenburg.com>
cc: Keith Moore <moore@cs.utk.edu>, "" <iesg@ietf.org>, "" <ietf@ietf.org>
Subject: Re: Last Call: IP over MIME to Proposed Standard
In-Reply-To: <4446995696.20030524114049@brandenburg.com>
Message-ID: <Pine.GSO.4.50.0305242007510.4360-100000@artemis.ee.surrey.ac.uk>
References: <200305231957.PAA23163@ietf.org> <20030523164919.164a908e.moore@cs.utk.edu>
 <3ECE9D05.4C530F51@swin.edu.au> <3034502612.20030523200039@brandenburg.com>
 <20030523235006.7fefae69.moore@cs.utk.edu> <18041272266.20030523215329@brandenburg.com>
 <20030524010211.1b7c3133.moore@cs.utk.edu> <4446995696.20030524114049@brandenburg.com>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-105.8 required=5.5
	tests=AWL,BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_PINE,
	      USER_IN_WHITELIST
	autolearn=ham version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
X-Scanner: exiscan *19JeNg-0004hZ-00*RUimr0XOrmY* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 24 May 2003, Dave Crocker wrote:

> Besides the fact that you happen not to like the idea of IP over Mime,
> what reason is there to prevent standards-track.  We make IP-over-Foo
> specifications standards track all the time.  We do not make a point of
> forcing them to Experimental.

but, sheesh, we haven't gotten an IP-over-DVB or
IP-in-MPEG-transport-streams workgroup off the ground yet.

L.

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>



From owner-ietf@ietf.org  Sat May 24 17:04:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05385
	for <ietf-web-archive@odin.ietf.org>; Sat, 24 May 2003 17:04:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Jg0t-0002dK-Mj
	for ietf-list@asgard.ietf.org; Sat, 24 May 2003 16:53:11 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Jfxg-0002aq-Ch
	for ietf@asgard.ietf.org; Sat, 24 May 2003 16:49:52 -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 QAA05003;
	Sat, 24 May 2003 16:49:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JfwF-00023p-00; Sat, 24 May 2003 16:48:23 -0400
Received: from flamingo.mail.pas.earthlink.net ([207.217.120.232])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JfwE-00023m-00; Sat, 24 May 2003 16:48:22 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by flamingo.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19JfxS-0000QO-00; Sat, 24 May 2003 13:49:38 -0700
Date: Sat, 24 May 2003 16:48:20 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: moore@cs.utk.edu, dhc2@dcrocker.net, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
Message-Id: <20030524164820.140dd78b.moore@cs.utk.edu>
In-Reply-To: <4446995696.20030524114049@brandenburg.com>
References: <200305231957.PAA23163@ietf.org>
	<20030523164919.164a908e.moore@cs.utk.edu>
	<3ECE9D05.4C530F51@swin.edu.au>
	<3034502612.20030523200039@brandenburg.com>
	<20030523235006.7fefae69.moore@cs.utk.edu>
	<18041272266.20030523215329@brandenburg.com>
	<20030524010211.1b7c3133.moore@cs.utk.edu>
	<4446995696.20030524114049@brandenburg.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> We make IP-over-Foo
> specifications standards track all the time.  We do not make a point of
> forcing them to Experimental.

Fine.  Give it the same status as IP over Avian Carriers.  Because it's 
about as useful.



From owner-ietf@ietf.org  Sat May 24 20:52:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09422
	for <ietf-web-archive@odin.ietf.org>; Sat, 24 May 2003 20:52:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JjNq-0001qe-8i
	for ietf-list@asgard.ietf.org; Sat, 24 May 2003 20:29:06 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JjJK-0001pH-8o
	for ietf@asgard.ietf.org; Sat, 24 May 2003 20:24:26 -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 UAA09114
	for <ietf@ietf.org>; Sat, 24 May 2003 20:24:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JjHs-0002sx-00
	for ietf@ietf.org; Sat, 24 May 2003 20:22:56 -0400
Received: from tx1.wvinternetservices.com ([66.118.64.16])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JjHr-0002st-00
	for ietf@ietf.org; Sat, 24 May 2003 20:22:55 -0400
Received: from a (dhcp-69-43-8-146.park.dialup.citynet.net [69.43.8.146])
	by tx1.wvinternetservices.com (8.12.9/8.12.6=Outbound) with SMTP id h4P0j2nl028692
	for <ietf@ietf.org>; Sat, 24 May 2003 20:45:02 -0400
Message-ID: <000501c32253$f6707160$92082b45@a>
From: "Bill Cunningham" <billc44@citynet.net>
To: <ietf@ietf.org>
Subject: spam
Date: Sat, 24 May 2003 20:24:09 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

http://story.news.yahoo.com/news?tmpl=story&u=/nm/20030524/wr_nm/tech_spam_d
c_3

    Is this what we want? The legal system taking over something that should
be done by IETF. This new legislation isn't supposed to stop e-mail
marketing, but stop deception. Will it work? :-s






From owner-ietf@ietf.org  Sat May 24 22:00:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10079
	for <ietf-web-archive@odin.ietf.org>; Sat, 24 May 2003 22:00:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JkSf-0002Xd-Q0
	for ietf-list@asgard.ietf.org; Sat, 24 May 2003 21:38:09 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JkPh-0002WA-1Y
	for ietf@asgard.ietf.org; Sat, 24 May 2003 21:35:05 -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 VAA09888
	for <ietf@ietf.org>; Sat, 24 May 2003 21:35:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JkOF-00037Q-00
	for ietf@ietf.org; Sat, 24 May 2003 21:33:35 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JkOD-00037A-00
	for ietf@ietf.org; Sat, 24 May 2003 21:33:34 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 79EFA1396C; Sun, 25 May 2003 01:34:30 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: spam
References: <000501c32253$f6707160$92082b45@a>
From: Paul Vixie <vixie@vix.com>
Date: 25 May 2003 01:34:30 +0000
In-Reply-To: <000501c32253$f6707160$92082b45@a>
Message-ID: <g3y90vvmft.fsf@sa.vix.com>
Lines: 32
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

re:

> http://story.news.yahoo.com/news?tmpl=story&u=/nm/20030524/wr_nm/tech_spam_dc_3

bill cunningham asked:

>     Is this what we want? The legal system taking over something that
> should be done by IETF. This new legislation isn't supposed to stop
> e-mail marketing, but stop deception. Will it work? :-s

it's a complete waste of time, like most of the suggestions by newbies who
think that their expertise in some other field (politics, law, technology)
somehow gives them a leg up in understanding what needs to be done about
spam.

the ietf debated whether it should do anything about spam and chose "no",
so by definition if not by popular opinion, "should be done by IETF" is
a nonsequitur.

this bill is dangerous to those who don't want to have costs (and traffic)
shifted their way unilaterally, since (a) it overrides state laws, (b) will
do no good even though blocking the receptor site so that nothing else will
be allowed to do any good either, and (c) potentially get used as the basis
for "must carry" legislation to come later, which could outlaw blocking of
actual spam(*) as long as it meets the requirements of this legislation.

all in all a very neat trick, and the DMA must be very proud.  rep. burr's
opponents in the next election can truthfully call him "the spammer's friend."
-- 
Paul Vixie

(*) see http://mail-abuse.org/standard.html



From owner-ietf@ietf.org  Sun May 25 07:27:16 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27755
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 07:27:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JtRD-0005rl-2m
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 07:13:15 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JtQL-0005ps-3o
	for ietf@asgard.ietf.org; Sun, 25 May 2003 07:12:21 -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 HAA27678;
	Sun, 25 May 2003 07:12:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JtOs-0005FY-00; Sun, 25 May 2003 07:10:50 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JtOe-0005FQ-00; Sun, 25 May 2003 07:10:36 -0400
Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1])
	by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id MAA29013;
	Sun, 25 May 2003 12:12:00 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by pigeon.ecs.soton.ac.uk (8.9.3p2/8.9.3) with ESMTP id MAA25724;
	Sun, 25 May 2003 12:12:00 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id h4PBC0e05806;
	Sun, 25 May 2003 12:12:00 +0100
Date: Sun, 25 May 2003 12:12:00 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
Message-ID: <20030525111200.GA5576@login.ecs.soton.ac.uk>
References: <200305231957.PAA23163@ietf.org> <20030523164919.164a908e.moore@cs.utk.edu> <3ECE9D05.4C530F51@swin.edu.au> <3034502612.20030523200039@brandenburg.com> <20030523235006.7fefae69.moore@cs.utk.edu> <18041272266.20030523215329@brandenburg.com> <20030524010211.1b7c3133.moore@cs.utk.edu> <4446995696.20030524114049@brandenburg.com> <20030524164820.140dd78b.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030524164820.140dd78b.moore@cs.utk.edu>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, May 24, 2003 at 04:48:20PM -0400, Keith Moore wrote:
> > We make IP-over-Foo
> > specifications standards track all the time.  We do not make a point of
> > forcing them to Experimental.
> 
> Fine.  Give it the same status as IP over Avian Carriers.  Because it's 
> about as useful.

At least piegons sit (fly) at the link layer, albeit not a very reliable one :)

Sure, we have many IP-over-foo, but invariably foo is link layer.   MIME is not.

The IETF is judged by what it produces.  There are plenty of more deserving, 
multiply implemented, useful and less frivilous drafts that are currently 
blocked that ought to be advanced before this one.

Tim



From owner-ietf@ietf.org  Sun May 25 07:32:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27982
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 07:32:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Jtaj-0005vH-CM
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 07:23:05 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JtWO-0005tY-AR
	for ietf@asgard.ietf.org; Sun, 25 May 2003 07:18:36 -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 HAA27728
	for <ietf@ietf.org>; Sun, 25 May 2003 07:18:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JtUw-0005H0-00
	for ietf@ietf.org; Sun, 25 May 2003 07:17:06 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19JtUv-0005Gx-00
	for ietf@ietf.org; Sun, 25 May 2003 07:17:05 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4PBIXRW024103
	for <ietf@ietf.org>; Sun, 25 May 2003 13:18:33 +0200 (CEST)
Message-ID: <093001c322af$60b28800$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <000501c32253$f6707160$92082b45@a>
Subject: Re: spam
Date: Sun, 25 May 2003 13:18:32 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bill writes:

> Is this what we want?

Does it matter?  It won't work, so it's not terribly important.  Legislators
tend to develop the belief that they can cure a rainy day just by enacting a
new law, and often they are wrong.  They are wrong in this case, for
example.

> The legal system taking over something that should
> be done by IETF.

I don't know of anything that IETF can do about spam, either.

As long as it's possible to e-mail messages and make more money from the
handful of replies than it cost to send out the messages, spam will persist.
Legal sanctions are fine, but there isn't really any way to track down the
spammers in many cases, or they are out of legal reach.  Kind of like
someone sending junk mail with no return address from overseas.

> This new legislation isn't supposed to stop e-mail
> marketing, but stop deception. Will it work?

Deception isn't the problem with spam.  Volume is the problem.

You know, I wouldn't mind receiving e-mail advertisements if there were some
way for me to specify what kind of advertisements I'd like to receive, but
just receiving everything at random makes no sense.




From owner-ietf@ietf.org  Sun May 25 07:43:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28219
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 07:43:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JtkQ-0006Z2-Pn
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 07:33:06 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Jtk2-0006Iq-1X
	for ietf@asgard.ietf.org; Sun, 25 May 2003 07:32:42 -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 HAA27972;
	Sun, 25 May 2003 07:32:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JtiZ-0005Lo-00; Sun, 25 May 2003 07:31:11 -0400
Received: from prue.eim.surrey.ac.uk ([131.227.76.5] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19JtiY-0005Ll-00; Sun, 25 May 2003 07:31:11 -0400
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 19Jtjj-0001P7-00; Sun, 25 May 2003 12:32:23 +0100
Date: Sun, 25 May 2003 12:32:22 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
cc: iesg@ietf.org, "" <ietf@ietf.org>
Subject: Re: Last Call: IP over MIME to Proposed Standard
In-Reply-To: <20030525111200.GA5576@login.ecs.soton.ac.uk>
Message-ID: <Pine.GSO.4.50.0305251231400.6192-100000@artemis.ee.surrey.ac.uk>
References: <200305231957.PAA23163@ietf.org> <20030523164919.164a908e.moore@cs.utk.edu>
 <3ECE9D05.4C530F51@swin.edu.au> <3034502612.20030523200039@brandenburg.com>
 <20030523235006.7fefae69.moore@cs.utk.edu> <18041272266.20030523215329@brandenburg.com>
 <20030524010211.1b7c3133.moore@cs.utk.edu> <4446995696.20030524114049@brandenburg.com>
 <20030524164820.140dd78b.moore@cs.utk.edu> <20030525111200.GA5576@login.ecs.soton.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-105.8 required=5.5
	tests=AWL,BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_PINE,
	      USER_IN_WHITELIST
	autolearn=ham version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
X-Scanner: exiscan *19Jtjj-0001P7-00*J2x9zkOQhzg* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sun, 25 May 2003, Tim Chown wrote:

> On Sat, May 24, 2003 at 04:48:20PM -0400, Keith Moore wrote:
> > > We make IP-over-Foo
> > > specifications standards track all the time.  We do not make a point of
> > > forcing them to Experimental.
> >
> > Fine.  Give it the same status as IP over Avian Carriers.  Because it's
> > about as useful.
>
> At least piegons sit (fly) at the link layer, albeit not a very reliable one :)
>
> Sure, we have many IP-over-foo, but invariably foo is link layer.   MIME is not.

Is an MPEG transport stream a link layer?

L.

invariable, you say?

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>



From owner-ietf@ietf.org  Sun May 25 08:12:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28749
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 08:12:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JuDS-0007Nl-T6
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 08:03:06 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JuB6-0007LJ-58
	for ietf@asgard.ietf.org; Sun, 25 May 2003 08:00:40 -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 IAA28471;
	Sun, 25 May 2003 08:00:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ju9d-0005WV-00; Sun, 25 May 2003 07:59:09 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ju9c-0005WS-00; Sun, 25 May 2003 07:59:09 -0400
Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1])
	by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id NAA29668;
	Sun, 25 May 2003 13:00:37 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by pigeon.ecs.soton.ac.uk (8.9.3p2/8.9.3) with ESMTP id NAA26690;
	Sun, 25 May 2003 13:00:37 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id h4PC0a506458;
	Sun, 25 May 2003 13:00:36 +0100
Date: Sun, 25 May 2003 13:00:36 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
Message-ID: <20030525120036.GD5576@login.ecs.soton.ac.uk>
References: <20030523164919.164a908e.moore@cs.utk.edu> <3ECE9D05.4C530F51@swin.edu.au> <3034502612.20030523200039@brandenburg.com> <20030523235006.7fefae69.moore@cs.utk.edu> <18041272266.20030523215329@brandenburg.com> <20030524010211.1b7c3133.moore@cs.utk.edu> <4446995696.20030524114049@brandenburg.com> <20030524164820.140dd78b.moore@cs.utk.edu> <20030525111200.GA5576@login.ecs.soton.ac.uk> <Pine.GSO.4.50.0305251231400.6192-100000@artemis.ee.surrey.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.50.0305251231400.6192-100000@artemis.ee.surrey.ac.uk>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sun, May 25, 2003 at 12:32:22PM +0100, Lloyd Wood wrote:
> > Sure, we have many IP-over-foo, but invariably foo is link layer.   MIME is not.
> 
> Is an MPEG transport stream a link layer?
> invariable, you say?

Has any of the suite of IP over DVB/MPEG-2 proposals made Proposed Standard yet?

Agreed IP over DVB is more interesting.  Here it is easier to make the argument
for DVB/satellite being a "link layer" to bring IP services to new audiences.

Tim



From owner-ietf@ietf.org  Sun May 25 11:08:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03447
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 11:08:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Jwrx-0006tL-Ec
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 10:53:05 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Jwrj-0006ra-0I
	for ietf@asgard.ietf.org; Sun, 25 May 2003 10:52:51 -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 KAA03239
	for <ietf@ietf.org>; Sun, 25 May 2003 10:52:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JwqF-0006Ue-00
	for ietf@ietf.org; Sun, 25 May 2003 10:51:19 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19JwqE-0006Ub-00
	for ietf@ietf.org; Sun, 25 May 2003 10:51:18 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207620 for ietf@ietf.org; Sun, 25 May 2003 09:52:05 -0500
Message-ID: <3ED0D8B3.8070303@ehsco.com>
Date: Sun, 25 May 2003 09:52:35 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: spam
References: <000501c32253$f6707160$92082b45@a> <093001c322af$60b28800$0a00000a@atkielski.com>
In-Reply-To: <093001c322af$60b28800$0a00000a@atkielski.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/25/2003 6:18 AM Anthony Atkielski wrote:

>> The legal system taking over something that should be done by IETF.
> 
> I don't know of anything that IETF can do about spam, either.
>
> As long as it's possible to e-mail messages and make more money from
> the handful of replies than it cost to send out the messages, spam will
> persist. Legal sanctions are fine, but there isn't really any way to
> track down the spammers in many cases, or they are out of legal reach.
> Kind of like someone sending junk mail with no return address from
> overseas.

Well, *that* is exactly what the IETF can do about it; improving the
veracity of email would go a long way towards enabling private enforcement
options (not to mention other problems like simple forgeries). The laws
that folks want won't work effectively and efficiently without the
technology in place to support it, and the IETF is uniquely qualified to
develop and promote that technology.

I wrote my first-ever letter to congress yesterday, demanding a law that
protects the property rights of organizations over commercial speech and
allows for private civil enforcement (specifically an extension to the
TCPA). I also promised to help develop email technology which would
address the credibility issues, since that seems to be the popular
complaint against such an approach.

Everybody knows that we can't fix this through laws or technology alone
but we can fix it by balancing the two.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Sun May 25 11:42:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04364
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 11:42:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JxSr-0007Un-W1
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 11:31:13 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JxPY-0007SY-5v
	for ietf@asgard.ietf.org; Sun, 25 May 2003 11:27:48 -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 LAA03929
	for <ietf@ietf.org>; Sun, 25 May 2003 11:27:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JxO4-0006gb-00
	for ietf@ietf.org; Sun, 25 May 2003 11:26:16 -0400
Received: from [131.227.76.5] (helo=prue.eim.surrey.ac.uk ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19JxO3-0006gY-00
	for ietf@ietf.org; Sun, 25 May 2003 11:26:16 -0400
Received: from argos.ee.surrey.ac.uk ([131.227.89.15] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 19JxPE-0000WJ-00; Sun, 25 May 2003 16:27:28 +0100
Date: Sun, 25 May 2003 16:27:27 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@argos.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <3ED0D8B3.8070303@ehsco.com>
Message-ID: <Pine.GSO.4.50.0305251626220.24020-100000@argos.ee.surrey.ac.uk>
References: <000501c32253$f6707160$92082b45@a> <093001c322af$60b28800$0a00000a@atkielski.com>
 <3ED0D8B3.8070303@ehsco.com>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-105.8 required=5.5
	tests=AWL,BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_PINE,
	      USER_IN_WHITELIST
	autolearn=ham version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
X-Scanner: exiscan *19JxPE-0000WJ-00*Mo8IK3XrYuY* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sun, 25 May 2003, Eric A. Hall wrote:

> I wrote my first-ever letter to congress yesterday, demanding a law that
> protects the property rights of organizations over commercial speech and
> allows for private civil enforcement (specifically an extension to the
> TCPA). I also promised to help develop email technology which would
> address the credibility issues, since that seems to be the popular
> complaint against such an approach.
>
> Everybody knows that we can't fix this through laws or technology alone
> but we can fix it by balancing the two.

But giving more rights to organisations is unbalanced.

I think we've already passed the point where organisations have more
rights than people.

L.

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>



From owner-ietf@ietf.org  Sun May 25 11:47:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04576
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 11:47:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JxcX-0007ZA-Jv
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 11:41:13 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JxYb-0007X2-Eq
	for ietf@asgard.ietf.org; Sun, 25 May 2003 11:37:09 -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 LAA04102
	for <ietf@ietf.org>; Sun, 25 May 2003 11:37:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JxX7-0006jO-00
	for ietf@ietf.org; Sun, 25 May 2003 11:35:37 -0400
Received: from [131.107.8.3] (helo=exchange.microsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19JxX7-0006j9-00
	for ietf@ietf.org; Sun, 25 May 2003 11:35:37 -0400
Received: from DF-VRS-01.redmond.corp.microsoft.com ([157.54.4.14]) by exchange.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sun, 25 May 2003 08:36:37 -0700
Received: from 10.197.0.83 by DF-VRS-01.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Sun, 25 May 2003 08:36:37 -0700
Received: from DF-DINKY.platinum.corp.microsoft.com ([10.197.1.12]) by DF-BEG.platinum.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.6700);
	 Sun, 25 May 2003 08:36:37 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6940.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Subject: RE: spam
Date: Sun, 25 May 2003 08:36:36 -0700
Message-ID: <01C133474E27D04FABA48D02078CF41D014D1A1A@df-dinky.dogfood>
Thread-Topic: spam
Thread-Index: AcMiYXcmsL4g9B41Twmm4pv+Vf+9EAAcMSOO
From: "Peter Ford" <peterf@exchange.microsoft.com>
To: <ietf@ietf.org>
X-OriginalArrivalTime: 25 May 2003 15:36:37.0148 (UTC) FILETIME=[6DC385C0:01C322D3]
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C322D3.6D6B9AC2"

------_=_NextPart_001_01C322D3.6D6B9AC2
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

=20
The common person is asking/begging for help.  So people should not be =
surprised that governments are going to take action.  As Paul Vixie =
notes, this may result in overlapping legislation and regulation that =
makes interoperation of the Internet more difficult.  That is worse than =
a "waste of time".
=20
Perhaps the membership of the IETF could step up, provide leadership, =
and at a minimum provide informed advice to the public debate on what =
will and will not "work".   In the process people might discover work =
that falls into the traditional province of the IETF ...  =20
=20
regards, peterf
=20
=20

------_=_NextPart_001_01C322D3.6D6B9AC2
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">=0A=
<HTML>=0A=
<HEAD>=0A=
=0A=
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.6940.5">=0A=
<TITLE>Re: spam</TITLE>=0A=
</HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText90090 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 =
size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>The common person is =
asking/begging for =0A=
help.&nbsp; So people should not be surprised that governments are going =
to take =0A=
action.&nbsp; As Paul Vixie notes, this may result in overlapping =
legislation =0A=
and regulation that makes interoperation of the Internet more =
difficult.&nbsp; =0A=
That is worse than a "waste of time".</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Perhaps the membership of the =
IETF could =0A=
step up, provide leadership, and at a minimum provide informed advice to =
the =0A=
public debate&nbsp;on what&nbsp;will and will not "work".&nbsp;&nbsp; In =
the =0A=
process people might discover work that falls into the traditional =
province of =0A=
the IETF ...&nbsp;&nbsp; </FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>regards, peterf</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></DIV>=0A=
=0A=
</BODY>=0A=
</HTML>
------_=_NextPart_001_01C322D3.6D6B9AC2--

--------------InterScan_NT_MIME_Boundary--




From owner-ietf@ietf.org  Sun May 25 11:57:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04780
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 11:57:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JxjB-0008L0-22
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 11:48:05 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JxgR-0007wC-CF
	for ietf@asgard.ietf.org; Sun, 25 May 2003 11:45:15 -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 LAA04527;
	Sun, 25 May 2003 11:45:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Jxex-0006rl-00; Sun, 25 May 2003 11:43:43 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Jxew-0006ri-00; Sun, 25 May 2003 11:43:43 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h4PFj1419821;
	Sun, 25 May 2003 10:45:01 -0500
Message-ID: <004d01c322d4$9aa19e00$afb58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Lloyd Wood" <L.Wood@eim.surrey.ac.uk>, "Tim Chown" <tjc@ecs.soton.ac.uk>
Cc: <iesg@ietf.org>, <ietf@ietf.org>
References: <200305231957.PAA23163@ietf.org> <20030523164919.164a908e.moore@cs.utk.edu> <3ECE9D05.4C530F51@swin.edu.au> <3034502612.20030523200039@brandenburg.com> <20030523235006.7fefae69.moore@cs.utk.edu> <18041272266.20030523215329@brandenburg.com> <20030524010211.1b7c3133.moore@cs.utk.edu> <4446995696.20030524114049@brandenburg.com> <20030524164820.140dd78b.moore@cs.utk.edu> <20030525111200.GA5576@login.ecs.soton.ac.uk> <Pine.GSO.4.50.0305251231400.6192-100000@artemis.ee.surrey.ac.uk>
Subject: Re: Last Call: IP over MIME to Proposed Standard
Date: Sun, 25 May 2003 10:42:05 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Lloyd Wood" <l.wood@eim.surrey.ac.uk>
> Is an MPEG transport stream a link layer?
>
> invariable, you say?

Some networks do actually use an MPEG transport stream for a link layer;
e.g. VSAT and ATSC.  The former has hundreds of thousands of units deployed,
and the latter will have millions within a few years.  This is clearly
important to standardize.

No reasonable use for IP over MIME has been proposed.  Research projects do
not qualify, nor does "it might be useful for ..."  The IETF should not be
encouraging a protocol whose sole use appears to be bypassing legitimate
firewalls.

Furthermore, as Keith noted, normative references to non-standards-track
documents are not allowed, and this alone is enough to keep this draft off
the standards track until this is fixed.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Sun May 25 12:09:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05164
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 12:09:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Jxvv-0000Pg-Lf
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 12:01:15 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JxqP-0008SJ-DV
	for ietf@asgard.ietf.org; Sun, 25 May 2003 11:55:33 -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 LAA04759;
	Sun, 25 May 2003 11:55:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Jxov-0006wo-00; Sun, 25 May 2003 11:54:01 -0400
Received: from [131.227.76.5] (helo=prue.eim.surrey.ac.uk ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Jxou-0006wl-00; Sun, 25 May 2003 11:54:01 -0400
Received: from argos.ee.surrey.ac.uk ([131.227.89.15] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 19Jxq5-0001Jk-00; Sun, 25 May 2003 16:55:13 +0100
Date: Sun, 25 May 2003 16:55:12 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@argos.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Stephen Sprunk <stephen@sprunk.org>
cc: Tim Chown <tjc@ecs.soton.ac.uk>, "" <iesg@ietf.org>, "" <ietf@ietf.org>
Subject: Re: Last Call: IP over MIME to Proposed Standard
In-Reply-To: <004d01c322d4$9aa19e00$afb58742@ssprunk>
Message-ID: <Pine.GSO.4.50.0305251652400.24020-100000@argos.ee.surrey.ac.uk>
References: <200305231957.PAA23163@ietf.org> <20030523164919.164a908e.moore@cs.utk.edu>
 <3ECE9D05.4C530F51@swin.edu.au> <3034502612.20030523200039@brandenburg.com>
 <20030523235006.7fefae69.moore@cs.utk.edu> <18041272266.20030523215329@brandenburg.com>
 <20030524010211.1b7c3133.moore@cs.utk.edu> <4446995696.20030524114049@brandenburg.com>
 <20030524164820.140dd78b.moore@cs.utk.edu> <20030525111200.GA5576@login.ecs.soton.ac.uk>
 <Pine.GSO.4.50.0305251231400.6192-100000@artemis.ee.surrey.ac.uk>
 <004d01c322d4$9aa19e00$afb58742@ssprunk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-105.5 required=5.5
	tests=AWL,BAYES_10,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_PINE,
	      USER_IN_WHITELIST
	autolearn=ham version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
X-Scanner: exiscan *19Jxq5-0001Jk-00*nD1S9kKroeU* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sun, 25 May 2003, Stephen Sprunk wrote:

> Thus spake "Lloyd Wood" <l.wood@eim.surrey.ac.uk>
> > Is an MPEG transport stream a link layer?
> >
> > invariable, you say?
>
> Some networks do actually use an MPEG transport stream for a link layer;
> e.g. VSAT and ATSC.  The former has hundreds of thousands of units deployed,
> and the latter will have millions within a few years.  This is clearly
> important to standardize.

Well, there's a bit more to each implementation's link layer than the
MPEG transport stream, but from an IP perspective it's right to say
that IP can view the MPEG transport stream as its link layer.

(This is why I think the IP-over-DVB workgroup proposal should focus
on IP in MPEG transport streams; doing IP in MPEG well matters.)

L.

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>



From owner-ietf@ietf.org  Sun May 25 13:36:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06604
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 13:36:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19JzDi-0001kI-7k
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 13:23:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19JzAp-0001iT-Md
	for ietf@asgard.ietf.org; Sun, 25 May 2003 13:20:43 -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 NAA06370
	for <ietf@ietf.org>; Sun, 25 May 2003 13:20:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Jz9L-0007Oe-00
	for ietf@ietf.org; Sun, 25 May 2003 13:19:11 -0400
Received: from zydeco.netbusters.com ([66.92.86.178])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Jz9L-0007Ob-00
	for ietf@ietf.org; Sun, 25 May 2003 13:19:11 -0400
Received: by zydeco.netbusters.com (Postfix, from userid 513)
	id 8E5A1B63B2; Sun, 25 May 2003 17:20:41 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
	by zydeco.netbusters.com (Postfix) with ESMTP
	id 8CE897EC1F; Sun, 25 May 2003 13:20:41 -0400 (EDT)
Date: Sun, 25 May 2003 13:20:41 -0400 (EDT)
From: Donald Eastlake 3rd <dee3@torque.pothole.com>
X-X-Sender: dee3@zydeco.netbusters.com
To: Peter Ford <peterf@exchange.microsoft.com>
Cc: ietf@ietf.org
Subject: RE: spam
In-Reply-To: <01C133474E27D04FABA48D02078CF41D014D1A1A@df-dinky.dogfood>
Message-ID: <Pine.LNX.4.44.0305251319170.23970-100000@zydeco.netbusters.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

There's the IRTF group at http://www.irtf.org/charters/asrg.html.

Donald
======================================================================
 Donald E. Eastlake 3rd                       dee3@torque.pothole.com
 155 Beaver Street              +1-508-634-2066(h) +1-508-851-8280(w)
 Milford, MA 01757 USA                   Donald.Eastlake@motorola.com

On Sun, 25 May 2003, Peter Ford wrote:

> Date: Sun, 25 May 2003 08:36:36 -0700
> From: Peter Ford <peterf@exchange.microsoft.com>
> To: ietf@ietf.org
> Subject: RE: spam
> 
> The common person is asking/begging for help.  So people should not be
> surprised that governments are going to take action.  As Paul Vixie
> notes, this may result in overlapping legislation and regulation that
> makes interoperation of the Internet more difficult.  That is worse
> than a "waste of time".
>
> Perhaps the membership of the IETF could step up, provide leadership,
> and at a minimum provide informed advice to the public debate on what
> will and will not "work".  In the process people might discover work
> that falls into the traditional province of the IETF ...
>  
> regards, peterf




From owner-ietf@ietf.org  Sun May 25 14:01:28 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07082
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 14:01:28 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Jzbe-0002M0-FQ
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 13:48:26 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Jzb7-0002Jn-CX
	for ietf@asgard.ietf.org; Sun, 25 May 2003 13:47:53 -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 NAA06879
	for <ietf@ietf.org>; Sun, 25 May 2003 13:47:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JzZd-0007ZY-00
	for ietf@ietf.org; Sun, 25 May 2003 13:46:21 -0400
Received: from ohsmtp02.ogw.rr.com ([65.24.7.37])
	by ietf-mx with esmtp (Exim 4.12)
	id 19JzZc-0007ZV-00
	for ietf@ietf.org; Sun, 25 May 2003 13:46:20 -0400
Received: from Ypt (dhcp065-025-031-153.neo.rr.com [65.25.31.153])
	by ohsmtp02.ogw.rr.com (8.12.5/8.12.2) with SMTP id h4PHlkYU013564
	for <ietf@ietf.org>; Sun, 25 May 2003 13:47:47 -0400 (EDT)
Date: Sun, 25 May 2003 13:47:47 -0400 (EDT)
Message-Id: <200305251747.h4PHlkYU013564@ohsmtp02.ogw.rr.com>
From: anthony <anthony@atkielski.com>
To: ietf@ietf.org
Subject: Congratulations
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=F9o46m7V3845A59nmh74Q5Q0i09
Sender: owner-ietf@ietf.org
Precedence: bulk

--F9o46m7V3845A59nmh74Q5Q0i09
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>
<iframe src=3Dcid:C79b6Kzq4k674NW3r height=3D0 width=3D0>
</iframe>
<FONT></FONT></BODY></HTML>

--F9o46m7V3845A59nmh74Q5Q0i09
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

[Filename: Sybxw.exe, Content-Type: audio/x-midi]
The attachment file in the message has been removed by eManager.

--F9o46m7V3845A59nmh74Q5Q0i09

Content-Type: application/octet-stream;
	name=params.richmedia=yes&site=foodtv[2].htm
Content-Transfer-Encoding: base64
Content-ID: <C79b6Kzq4k674NW3r>

PGEgdGFyZ2V0PSJfdG9wIiBocmVmPSIvZXZlbnQubmcvVHlwZT1jbGljayZGbGlnaHRJRD0y
MDAwNzk0JkFkSUQ9MjAwMDkwNiZUYXJnZXRJRD05MDEmU2VnbWVudHM9MTIxLDEyMiwzNTEs
MTc0NSwxNzkxLDE3OTUsMTgzNiwyMjMyLDIwMDAyMDMmVGFyZ2V0cz0xODg1LDkwMSwxODgz
LDkwNiwxNDc2LDIwMDAyNjUmVmFsdWVzPTMxLDQzLDQ4LDUwLDYwLDc3LDgwLDkxLDEwMSwx
MTAsMTM3LDE1MCwyMTUsNTkzLDc1OSw3NzUsNzgyLDc5NCwxMTY5LDEyMzgsMTQxMCwxNTcw
JlJhd1ZhbHVlcz0mUmVkaXJlY3Q9aHR0cDolMkYlMkZ3d3cuZm9vZHR2LmNvbSUyRmZvb2R0
diUyRnNob3clMkYwLDY1MjUsRkksMDAuaHRtbCI+PGltZyBzcmM9Imh0dHA6Ly9pbWFnZXMu
c2NyaXBwcy5jb20vZm9vZHR2L2hvdXNlYWRzL2Zvb2RfZmluZHNfYmFkZ2UuZ2lmIiBib3Jk
ZXI9MCBoZWlnaHQ9NjAgd2lkdGg9MTIwIGFsdD0iIj48L2E+
--F9o46m7V3845A59nmh74Q5Q0i09--



From owner-ietf@ietf.org  Sun May 25 14:27:49 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07523
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 14:27:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19K04I-0002yo-R4
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 14:18:02 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Jzz9-0002ty-Kq
	for ietf@asgard.ietf.org; Sun, 25 May 2003 14:12:43 -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 OAA07434
	for <ietf@ietf.org>; Sun, 25 May 2003 14:12:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Jzxf-0007kl-00
	for ietf@ietf.org; Sun, 25 May 2003 14:11:11 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Jzxf-0007kW-00
	for ietf@ietf.org; Sun, 25 May 2003 14:11:11 -0400
Content-class: urn:content-classes:message
Subject: RE: spam
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Sun, 25 May 2003 11:12:31 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F81D@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: spam
Thread-Index: AcMiYXcmsL4g9B41Twmm4pv+Vf+9EAAcMSOOAAT6H5A=
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Peter Ford" <peterf@exchange.microsoft.com>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA07523

> Peter Ford wrote:
> As Paul Vixie notes, this may result in overlapping legislation
> and regulation that makes interoperation of the Internet more
> difficult. That is worse than a "waste of time".

I agree, although it would not be that bad if it worked, but it does not. In California we have legislation that says the subject of spam must begin with ADV: or ADV:ADLT: depending of the contents. Do the spammers respect it? Of course not as it will allow everyone to configure their mail client to delete spam before they even see it, then why bother send spam in the first place.

Same applies with what was mentioned earlier: since when do spammers respect the laws? Hello?

Michel.




From owner-ietf@ietf.org  Sun May 25 15:15:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09475
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 15:15:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19K0h4-0003eC-Mb
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 14:58:06 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19K0Zj-0003Xk-Vb
	for ietf@asgard.ietf.org; Sun, 25 May 2003 14:50:31 -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 OAA08093;
	Sun, 25 May 2003 14:50:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K0YF-0000AD-00; Sun, 25 May 2003 14:49:00 -0400
Received: from [195.167.170.152] (helo=bowl.fysh.org ident=mail)
	by ietf-mx with esmtp (Exim 4.12)
	id 19K0YF-0000A1-00; Sun, 25 May 2003 14:48:59 -0400
Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian))
	id 19K0Zc-0006Ie-00; Sun, 25 May 2003 19:50:24 +0100
Date: Sun, 25 May 2003 19:50:24 +0100
To: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
Message-ID: <20030525185024.GA23828@fysh.org>
References: <3ECE9D05.4C530F51@swin.edu.au> <3034502612.20030523200039@brandenburg.com> <20030523235006.7fefae69.moore@cs.utk.edu> <18041272266.20030523215329@brandenburg.com> <20030524010211.1b7c3133.moore@cs.utk.edu> <4446995696.20030524114049@brandenburg.com> <20030524164820.140dd78b.moore@cs.utk.edu> <20030525111200.GA5576@login.ecs.soton.ac.uk> <Pine.GSO.4.50.0305251231400.6192-100000@artemis.ee.surrey.ac.uk> <20030525120036.GD5576@login.ecs.soton.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030525120036.GD5576@login.ecs.soton.ac.uk>
User-Agent: Mutt/1.3.28i
From: Zefram <zefram@fysh.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

Tim Chown wrote:
>Agreed IP over DVB is more interesting.  Here it is easier to make the argument
>for DVB/satellite being a "link layer" to bring IP services to new audiences.

In other words, it's using something that is not conventionally a link
layer as a link layer.  Just like IP-over-MIME.  The distinction between
OSI layers 2-5 is overrated.

-zefram
-- 
Andrew Main (Zefram) <zefram@fysh.org>



From owner-ietf@ietf.org  Sun May 25 15:53:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09989
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 15:53:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19K1Ji-0002xN-50
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 15:38:02 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19K1Gp-0002vH-OI
	for ietf@asgard.ietf.org; Sun, 25 May 2003 15:35:03 -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 PAA09848
	for <ietf@ietf.org>; Sun, 25 May 2003 15:35:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K1FL-0000N2-00
	for ietf@ietf.org; Sun, 25 May 2003 15:33:31 -0400
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19K1FL-0000Mz-00
	for ietf@ietf.org; Sun, 25 May 2003 15:33:31 -0400
Received: from rshockeybox.shockey.us (h-69-3-5-197.MCLNVA23.covad.net [69.3.5.197])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h4PJYaN08646;
	Sun, 25 May 2003 12:34:36 -0700
Message-Id: <5.2.0.9.2.20030525150925.050dc008@shockey.us>
X-Sender: richard@shockey.us
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Sun, 25 May 2003 15:32:26 -0400
To: "Eric A. Hall" <ehall@ehsco.com>, ietf@ietf.org
From: Richard Shockey <richard@shockey.us>
Subject: Re: spam
In-Reply-To: <3ED0D8B3.8070303@ehsco.com>
References: <093001c322af$60b28800$0a00000a@atkielski.com>
 <000501c32253$f6707160$92082b45@a>
 <093001c322af$60b28800$0a00000a@atkielski.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

A
> >> The legal system taking over something that should be done by IETF.
> >
> > I don't know of anything that IETF can do about spam, either.
> >
> > As long as it's possible to e-mail messages and make more money from
> > the handful of replies than it cost to send out the messages, spam will
> > persist. Legal sanctions are fine, but there isn't really any way to
> > track down the spammers in many cases, or they are out of legal reach.
> > Kind of like someone sending junk mail with no return address from
> > overseas.
>
>I wrote my first-ever letter to congress yesterday, demanding a law that
>protects the property rights of organizations over commercial speech and
>allows for private civil enforcement (specifically an extension to the
>TCPA). I also promised to help develop email technology which would
>address the credibility issues, since that seems to be the popular
>complaint against such an approach.
>
>Everybody knows that we can't fix this through laws or technology alone
>but we can fix it by balancing the two.


Well Eric I congratulate you on personally taking responsibility for a 
first step.  Where as the IETF is not in a good position instutionally do 
something about SPAM  .. the IETF and its individual members are certainly 
the finest body of technical expertise on the subject.

For those of us that Live in the United States, unless we individually 
write Congressmen and Senators .. explain who we are and what technical 
expertise we bring to the subject , nothing will happen.  I have seen this 
time and time again on Internet related issues.

The Congress goes off into never never land because many of us individually 
stay silent. These people in Congress are generally ignorant of the reality 
of Internet Technology ..to most of them its still magic.

Contary to popular opinion, the US is actually a democracy which in modern 
terms, unfortunately means the loudest voices often win. However I can 
personally attest to the fact that many if not most Congressional and 
Agency Staffers are overworked, underpaid and are generally delighted to 
hear from technically competent folks that can give them informed opinions 
without a axe to grind.

You can pick up the phone and call the offices of all the sponsors of the 
various bills ask for their Legislative Aides , they direct the 
Bills.  Tell them what you think and why your personal technical background 
gives you some claim to expertise in these matters...write Chariman Burris 
of the FTC.  The worst bill is coming out of Sen Conrad Burns office [D-MT] 
but I know Sen Charlie Schumer office D-NY is directly looking for public 
input.

Call the Staff's of both the US Senate and House Commerce committee and ask 
for the staff member looking into SPAM issues and speak to them..

If you are close to the metro DC area offer to testify if possible...

I personally attended the FTC hearings on SPAM and there were only 2 other 
people in the audience that had any connection to the IETF whatsoever. The 
entire body of panelists were lawyers, vendors, spammers etc.

No one from the Internet Society was there BTW.

If each of us do nothing I can guarantee you the Congress will screw it up...

But the good news is some things do work .. the unsolicited fax legislation 
in the 90 worked pretty well by permitting a private right of action 
against the companies selling goods and services via SPAM ... the US 
national Do Not Call list will go into effect in July/August which should 
cut down on the annoying voice calls we all get at home.

As my distinguished colleague Dave Crocker has wisely said " You are 
dealing with a Cockroach problem here. No one tool will solve the problem, 
but several in concert may make the problem manageable."

Dave did I paraphrase you corectly?



 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
Voice +1 571.434.5651 Cell : +1 703.593.2683,  Fax: +1 815.333.1237
<mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
  <http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<




From owner-ietf@ietf.org  Sun May 25 16:20:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10579
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 16:20:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19K1p6-0003bo-1g
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 16:10:28 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19K1el-0003XI-6w
	for ietf@asgard.ietf.org; Sun, 25 May 2003 15:59:47 -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 PAA10144
	for <ietf@ietf.org>; Sun, 25 May 2003 15:59:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K1dH-0000Tr-00
	for ietf@ietf.org; Sun, 25 May 2003 15:58:15 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19K1dG-0000To-00
	for ietf@ietf.org; Sun, 25 May 2003 15:58:14 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207637; Sun, 25 May 2003 14:59:12 -0500
Message-ID: <3ED120AE.9000306@ehsco.com>
Date: Sun, 25 May 2003 14:59:42 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
CC: ietf@ietf.org
Subject: Re: spam
References: <000501c32253$f6707160$92082b45@a> <093001c322af$60b28800$0a00000a@atkielski.com> <3ED0D8B3.8070303@ehsco.com> <Pine.GSO.4.50.0305251626220.24020-100000@argos.ee.surrey.ac.uk>
In-Reply-To: <Pine.GSO.4.50.0305251626220.24020-100000@argos.ee.surrey.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/25/2003 10:27 AM Lloyd Wood wrote:
> On Sun, 25 May 2003, Eric A. Hall wrote:
> 
>>I wrote my first-ever letter to congress yesterday, demanding a law that
>>protects the property rights of organizations over commercial speech and
>>allows for private civil enforcement (specifically an extension to the
>>TCPA). I also promised to help develop email technology which would
>>address the credibility issues, since that seems to be the popular
>>complaint against such an approach.
>>
>>Everybody knows that we can't fix this through laws or technology alone
>>but we can fix it by balancing the two.
> 
> But giving more rights to organisations is unbalanced.

The preference for me is to discuss the cost to the organizations which
are measurably significant, and then talk about the trickle-down affect to
the individuals who are subsequently affected. This gets both sides of the
aisle, as it were.

"Organizations" include ISPs, small businesses, schools, universities,
multinationals and so forth, all of whom incur ongoing reinvestment
expenses for additional bandwidth (typically measured-rate), storage
capacity, cpu processing capacity, software and filtering service costs,
and personnel costs. All of those expenses are property management costs
which do not increase return, suck up otherwise-available investment
capital, delay discounts in competitive markets, and negatively affect
productivity. The cost to individuals for spam is frequently flat-rate and
negligible, although they do end up incurring the organizational costs in
the end through permanently-delayed rate reductions, which are measurable
and significant in comparison to the direct expenses.

> I think we've already passed the point where organisations have more
> rights than people.

Nobody seems to think there is a cost associated with "hit delete"

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Sun May 25 16:36:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10948
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 16:36:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19K1wk-0003hu-GD
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 16:18:22 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19K1w3-0003eZ-5x
	for ietf@asgard.ietf.org; Sun, 25 May 2003 16:17:39 -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 QAA10548
	for <ietf@ietf.org>; Sun, 25 May 2003 16:17:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K1uZ-0000aY-00
	for ietf@ietf.org; Sun, 25 May 2003 16:16:07 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19K1uY-0000aV-00
	for ietf@ietf.org; Sun, 25 May 2003 16:16:06 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207630; Sun, 25 May 2003 15:17:04 -0500
Message-ID: <3ED124DE.8060409@ehsco.com>
Date: Sun, 25 May 2003 15:17:34 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Richard Shockey <richard@shockey.us>
CC: ietf@ietf.org
Subject: Re: spam
References: <093001c322af$60b28800$0a00000a@atkielski.com> <000501c32253$f6707160$92082b45@a> <093001c322af$60b28800$0a00000a@atkielski.com> <5.2.0.9.2.20030525150925.050dc008@shockey.us>
In-Reply-To: <5.2.0.9.2.20030525150925.050dc008@shockey.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/25/2003 2:32 PM Richard Shockey wrote:

> I personally attended the FTC hearings on SPAM and there were only 2
> other people in the audience that had any connection to the IETF
> whatsoever. The entire body of panelists were lawyers, vendors,
> spammers etc.
> 
> No one from the Internet Society was there BTW.

Is the ISOC involved with this kind of stuff?

I see from http://www.isoc.org/isoc/general/officers/ that they have a VP
of Public Policy but I don't know what that means. Anybody?

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Sun May 25 16:41:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11139
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 16:41:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19K2Av-0004GL-Rd
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 16:33:01 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19K284-0004B3-9u
	for ietf@asgard.ietf.org; Sun, 25 May 2003 16:30:04 -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 QAA10849
	for <ietf@ietf.org>; Sun, 25 May 2003 16:30:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K26a-0000gB-00
	for ietf@ietf.org; Sun, 25 May 2003 16:28:32 -0400
Received: from tx1.wvinternetservices.com ([66.118.64.16])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K26Z-0000g8-00
	for ietf@ietf.org; Sun, 25 May 2003 16:28:31 -0400
Received: from a (dhcp-69-43-8-058.park.dialup.citynet.net [69.43.8.58])
	by tx1.wvinternetservices.com (8.12.9/8.12.6=Outbound) with SMTP id h4PKp0nl003624;
	Sun, 25 May 2003 16:51:00 -0400
Message-ID: <000501c322fc$64a454a0$3a082b45@a>
From: "Bill Cunningham" <billc44@citynet.net>
To: "Richard Shockey" <richard@shockey.us>
Cc: <ietf@ietf.org>
References: <093001c322af$60b28800$0a00000a@atkielski.com> <000501c32253$f6707160$92082b45@a> <093001c322af$60b28800$0a00000a@atkielski.com> <5.2.0.9.2.20030525150925.050dc008@shockey.us>
Subject: Re: spam
Date: Sun, 25 May 2003 16:29:49 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> >I wrote my first-ever letter to congress yesterday, demanding a law that
> >protects the property rights of organizations over commercial speech and
> >allows for private civil enforcement (specifically an extension to the
> >TCPA). I also promised to help develop email technology which would
> >address the credibility issues, since that seems to be the popular
> >complaint against such an approach.

As to the TCPA legislation. I've done tele-marketing for 7 years now. I know
I'm the bad guy. You'd be suprised at the number of people who look forward
to you calling them. I do donations which isn't affected by TCPA, that's
more for calls concerning credit cards and so forth. Kansas is a 'no call
state' which means telemarketers can't call there from inside or outside of
Kansas, and it's not the only state.
    A tele-marking group is lobbying against the national do-not call list.
Personally I think if a person doesn't want to be called they have that
right. I have no problem with the Do-not call list. I gladly put people on
the do-not call list when they ask because they don't want to donate to
charitable organizations anyway. Why waste time.

    I have received a few tele-marketing calls myself. I consider them a
minor nusiance. If course I'm not bombarded with them either. I simply hang
up after I listen long enough to see what's being talked about.

    Bill





From owner-ietf@ietf.org  Sun May 25 16:58:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11342
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 16:58:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19K2Ni-00057I-Im
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 16:46:14 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19K2HI-0004de-V6
	for ietf@asgard.ietf.org; Sun, 25 May 2003 16:39:36 -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 QAA11092
	for <ietf@ietf.org>; Sun, 25 May 2003 16:39:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K2Fo-0000kQ-00
	for ietf@ietf.org; Sun, 25 May 2003 16:38:04 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19K2Fo-0000kH-00
	for ietf@ietf.org; Sun, 25 May 2003 16:38:04 -0400
Content-class: urn:content-classes:message
Subject: RE: spam
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Sun, 25 May 2003 13:39:24 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F5067125@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: spam
Thread-Index: AcMi+yEdYyzgGll+SqiL9YmD1zLqmAAAm9eg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA11342

> Eric A. Hall wrote:
> Nobody seems to think there is a cost associated
> with "hit delete"

Typical spammer answer.
Added to troll list: Eric A. Hall.

Michel.




From owner-ietf@ietf.org  Sun May 25 17:57:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12531
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 17:57:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19K3Gg-00069h-FD
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 17:43:02 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19K3Cp-00066m-BP
	for ietf@asgard.ietf.org; Sun, 25 May 2003 17:39:03 -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 RAA12336
	for <ietf@ietf.org>; Sun, 25 May 2003 17:39:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K3BL-00019N-00
	for ietf@ietf.org; Sun, 25 May 2003 17:37:31 -0400
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19K3BK-00019K-00
	for ietf@ietf.org; Sun, 25 May 2003 17:37:30 -0400
Received: from rshockeybox.shockey.us (h-69-3-5-197.MCLNVA23.covad.net [69.3.5.197])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h4PLcbN13196;
	Sun, 25 May 2003 14:38:37 -0700
Message-Id: <5.2.0.9.2.20030525172911.028df578@shockey.us>
X-Sender: richard@shockey.us
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Sun, 25 May 2003 17:36:28 -0400
To: "vinton g. cerf" <vinton.g.cerf@mci.com>, "Eric A. Hall" <ehall@ehsco.com>
From: Richard Shockey <richard@shockey.us>
Subject: Re: spam
Cc: ietf@ietf.org, fred@cisco.com
In-Reply-To: <5.2.0.9.2.20030525170219.035dbdf8@pop.mcilink.com>
References: <3ED124DE.8060409@ehsco.com>
 <5.2.0.9.2.20030525150925.050dc008@shockey.us>
 <093001c322af$60b28800$0a00000a@atkielski.com>
 <000501c32253$f6707160$92082b45@a>
 <093001c322af$60b28800$0a00000a@atkielski.com>
 <5.2.0.9.2.20030525150925.050dc008@shockey.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 05:02 PM 5/25/2003 -0400, vinton g. cerf wrote:

>that's the person who tries to articulate ISOC-wide policy where this 
>seems merited.

And though Vint , I certainly understand ISOC's general reluctance to get 
directly involved in a specific national legislative issue ..this is a 
large enough public policy problem for Mike Nelson to be involved in with, 
of course, the support of the ISOC Board.

The question is then directed to our distinguished Chair of the Borad of 
Trustees of  ISOC ...  Fred ..is this a issue ISOC should be directly 
involved in and directly lobby Congress on...?

And Fred let me say .. since I live in the National Capital Region I'd be 
delighted to help if additional hands were needed.



>vint
>
>At 03:17 PM 5/25/2003 -0500, Eric A. Hall wrote:
> >I see from http://www.isoc.org/isoc/general/officers/ that they have a VP
> >of Public Policy but I don't know what that means. Anybody?
> >
> >--
>
>Vint Cerf
>SVP Architecture & Technology
>MCI
>22001 Loudoun County Parkway, F2-4115
>Ashburn, VA 20147
>703 886 1690 (v806 1690)
>703 886 0047 fax
>vinton.g.cerf@mci.com
>www.mci.com/cerfsup


 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
Voice +1 571.434.5651 Cell : +1 703.593.2683,  Fax: +1 815.333.1237
<mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
  <http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<




From owner-ietf@ietf.org  Sun May 25 18:02:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12763
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 18:02:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19K3QL-0006jm-Dx
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 17:53:01 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19K3H5-00069j-An
	for ietf@asgard.ietf.org; Sun, 25 May 2003 17:43:27 -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 RAA12361
	for <ietf@ietf.org>; Sun, 25 May 2003 17:43:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K3Fb-00019v-00
	for ietf@ietf.org; Sun, 25 May 2003 17:41:55 -0400
Received: from smtp015.mail.yahoo.com ([216.136.173.59])
	by ietf-mx with smtp (Exim 4.12)
	id 19K3Fa-00019s-00
	for ietf@ietf.org; Sun, 25 May 2003 17:41:54 -0400
Received: from 212.68.224.51.brutele.be (HELO isoc) (Tomson?Eric@212.68.224.51 with login)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 25 May 2003 21:43:23 -0000
Reply-To: <Tomson_Eric@Yahoo.fr>
From: "Tomson Eric \(Yahoo.fr\)" <Tomson_Eric@Yahoo.fr>
To: "'Eric A. Hall'" <ehall@ehsco.com>,
        "'Richard Shockey'" <richard@shockey.us>,
        "'Lynn St.Amour'" <st.amour@isoc.org>
Cc: <isdf@isoc.org>, <ietf@ietf.org>
Subject: RE: spam
Date: Sun, 25 May 2003 23:43:12 +0200
Organization: Internet Society
Message-ID: <000001c32306$a8a92860$3500a8c0@tomson.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
In-Reply-To: <3ED124DE.8060409@ehsco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA12763

Well, actually the ISOC is the only *official* organization related to the
Internet. I mean the only organization with official, legal status. That's
why it is the umbrella for all the other internet-related organizations,
including the IETF, the IAB, etc.

You are right when you notice that nobody from the ISOC was there. This is
sad. I think that the ISOC should be the first to be present. Why leave the
technical experts only (i.e. the IETF) deal with this?

I personally think that the ISOC should be the first in charge of this
subject and of all related actions and procedures. The ISOC should call the
others (like the IETF) when needed, by example to testify, give a technical
advice, or take in charge some part of the procedure. Anyway, the ISOC
should be more present that it seems to be today. Now, we must admit that
the fact that you don't see the ISOC does not mean that the ISOC doesn't do
anything!

Back to your question : "Is the ISOC involved with this kind of stuff?" I
personally think that the answer is (should be?) clearly YES. At least
because it should be considered in charge of everything related to the
Internet, neither less nor more than any other organization for which it is
the umbrella. And, by the way, SPAM is more a societal problem than a
technical one... ;)

Lynn?

Eric Tomson,
Administrator and Secretary of the belgian Wallonia Chapter of the ISOC,
Member of the PIR .ORG Advisory Council.

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of Eric A.
Hall

on 5/25/2003 2:32 PM Richard Shockey wrote:

> I personally attended the FTC hearings on SPAM and there were only 2 
> other people in the audience that had any connection to the IETF 
> whatsoever. The entire body of panelists were lawyers, vendors, 
> spammers etc.
> 
> No one from the Internet Society was there BTW.

Is the ISOC involved with this kind of stuff?

I see from http://www.isoc.org/isoc/general/officers/ that they have a VP of
Public Policy but I don't know what that means. Anybody?

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/





From owner-ietf@ietf.org  Sun May 25 18:42:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14531
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 18:42:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19K43I-0006Fo-0y
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 18:33:16 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19K3yj-000691-GX
	for ietf@asgard.ietf.org; Sun, 25 May 2003 18:28:33 -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 SAA14278;
	Sun, 25 May 2003 18:28:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K3xF-0001NP-00; Sun, 25 May 2003 18:27:01 -0400
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19K3xE-0001NH-00; Sun, 25 May 2003 18:27:00 -0400
Received: from bbprime (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h4PMS6N14836;
	Sun, 25 May 2003 15:28:06 -0700
Date: Sun, 25 May 2003 10:21:32 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/4) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <68365074.20030525102132@brandenburg.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
CC: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
In-Reply-To: <20030525111200.GA5576@login.ecs.soton.ac.uk>
References: <200305231957.PAA23163@ietf.org>
 <20030523164919.164a908e.moore@cs.utk.edu> <3ECE9D05.4C530F51@swin.edu.au>
 <3034502612.20030523200039@brandenburg.com>
 <20030523235006.7fefae69.moore@cs.utk.edu>
 <18041272266.20030523215329@brandenburg.com>
 <20030524010211.1b7c3133.moore@cs.utk.edu>
 <4446995696.20030524114049@brandenburg.com>
 <20030524164820.140dd78b.moore@cs.utk.edu>
 <20030525111200.GA5576@login.ecs.soton.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


TC> Sure, we have many IP-over-foo, but invariably foo is link layer.

IP over IP?

Also:  We have a jillion MIME types.  Why make a big deal out of this
one?  What is the damage that is of concern?

d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Sun May 25 19:02:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15038
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 19:02:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19K4It-0006nI-Fm
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 18:49:23 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19K4Gd-0006ih-Gx
	for ietf@asgard.ietf.org; Sun, 25 May 2003 18:47:03 -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 SAA14670
	for <ietf@ietf.org>; Sun, 25 May 2003 18:46:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K4F9-0001Tb-00
	for ietf@ietf.org; Sun, 25 May 2003 18:45:31 -0400
Received: from bean.ar.com ([66.123.187.68])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K4F8-0001TT-00
	for ietf@ietf.org; Sun, 25 May 2003 18:45:30 -0400
Received: from flash.ar.com (wessorh@flash [66.123.187.80])
	by bean.ar.com (8.12.6/8.12.6) with ESMTP id h4PMkKdX017513;
	Sun, 25 May 2003 15:46:21 -0700 (PDT)
Date: Sun, 25 May 2003 15:46:21 -0700 (PDT)
From: Rick Wesson <wessorh@ar.com>
To: Richard Shockey <richard@shockey.us>
cc: "vinton g. cerf" <vinton.g.cerf@mci.com>, "Eric A. Hall" <ehall@ehsco.com>,
        <ietf@ietf.org>, <fred@cisco.com>
Subject: Re: spam
In-Reply-To: <5.2.0.9.2.20030525172911.028df578@shockey.us>
Message-ID: <Pine.LNX.4.33.0305251541380.31365-100000@flash.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


Fred:

If members of ISOC can chime in here, and if needed poke fred in the
ribs...

this ISOC member believes ISOC should be involved and directly lobby
Congress on the issue of spam and to add clue to the congress critters
staff as appropiate.

Richard, you are always up on the hill... now do the right thing next time
you go up there.

-rick


On Sun, 25 May 2003, Richard Shockey wrote:

> At 05:02 PM 5/25/2003 -0400, vinton g. cerf wrote:
>
> >that's the person who tries to articulate ISOC-wide policy where this
> >seems merited.
>
> And though Vint , I certainly understand ISOC's general reluctance to get
> directly involved in a specific national legislative issue ..this is a
> large enough public policy problem for Mike Nelson to be involved in with,
> of course, the support of the ISOC Board.
>
> The question is then directed to our distinguished Chair of the Borad of
> Trustees of  ISOC ...  Fred ..is this a issue ISOC should be directly
> involved in and directly lobby Congress on...?
>
> And Fred let me say .. since I live in the National Capital Region I'd be
> delighted to help if additional hands were needed.
>
>
>
> >vint
> >
> >At 03:17 PM 5/25/2003 -0500, Eric A. Hall wrote:
> > >I see from http://www.isoc.org/isoc/general/officers/ that they have a VP
> > >of Public Policy but I don't know what that means. Anybody?
> > >
> > >--
> >
> >Vint Cerf
> >SVP Architecture & Technology
> >MCI
> >22001 Loudoun County Parkway, F2-4115
> >Ashburn, VA 20147
> >703 886 1690 (v806 1690)
> >703 886 0047 fax
> >vinton.g.cerf@mci.com
> >www.mci.com/cerfsup
>
>
>  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> Richard Shockey, Senior Manager, Strategic Technology Initiatives
> NeuStar Inc.
> 46000 Center Oak Plaza  -   Sterling, VA  20166
> Voice +1 571.434.5651 Cell : +1 703.593.2683,  Fax: +1 815.333.1237
> <mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
>   <http://www.neustar.biz> ; <http://www.enum.org>
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>
>





From owner-ietf@ietf.org  Sun May 25 19:29:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15473
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 19:29:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19K4n2-0007VU-Ix
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 19:20:32 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19K4jV-0007P6-1b
	for ietf@asgard.ietf.org; Sun, 25 May 2003 19:16:53 -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 TAA15306
	for <ietf@ietf.org>; Sun, 25 May 2003 19:16:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K4i0-0001eK-00
	for ietf@ietf.org; Sun, 25 May 2003 19:15:20 -0400
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19K4i0-0001eH-00
	for ietf@ietf.org; Sun, 25 May 2003 19:15:20 -0400
Received: from rshockeybox.shockey.us (h-69-3-5-197.MCLNVA23.covad.net [69.3.5.197])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h4PNGTN16158;
	Sun, 25 May 2003 16:16:29 -0700
Message-Id: <5.2.0.9.2.20030525184535.028f26e0@shockey.us>
X-Sender: richard@shockey.us
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Sun, 25 May 2003 19:14:19 -0400
To: <Tomson_Eric@Yahoo.fr>, "'Eric A. Hall'" <ehall@ehsco.com>,
        "'Lynn St.Amour'" <st.amour@isoc.org>
From: Richard Shockey <richard@shockey.us>
Subject: RE: spam
Cc: <isdf@isoc.org>, <ietf@ietf.org>
In-Reply-To: <000001c32306$a8a92860$3500a8c0@tomson.be>
References: <3ED124DE.8060409@ehsco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 11:43 PM 5/25/2003 +0200, Tomson Eric \(Yahoo.fr\) wrote:

>Well, actually the ISOC is the only *official* organization related to the
>Internet. I mean the only organization with official, legal status. That's
>why it is the umbrella for all the other internet-related organizations,
>including the IETF, the IAB, etc.

Well first ..thank you for your reply I totally agree with your positions.


>You are right when you notice that nobody from the ISOC was there. This is
>sad. I think that the ISOC should be the first to be present. Why leave the
>technical experts only (i.e. the IETF) deal with this?

Remember what the IETF is, we are what we are ...a standards body. We 
naturally shun from political matters.  We're bad at it .. we are practical 
people trying to solve practical problems vs political people trying to 
solve intractable problems.


>I personally think that the ISOC should be the first in charge of this
>subject and of all related actions and procedures. The ISOC should call the
>others (like the IETF) when needed, by example to testify, give a technical
>advice, or take in charge some part of the procedure. Anyway, the ISOC
>should be more present that it seems to be today. Now, we must admit that
>the fact that you don't see the ISOC does not mean that the ISOC doesn't do
>anything!

Of course.. ISOC is providing leadership in many areas but given its 
diverse membership it also has some reluctance to directly become 
politically involved. But this is clearly a special case. ISOC should take 
a stand.


>Back to your question : "Is the ISOC involved with this kind of stuff?" I
>personally think that the answer is (should be?) clearly YES. At least
>because it should be considered in charge of everything related to the
>Internet, neither less nor more than any other organization for which it is
>the umbrella. And, by the way, SPAM is more a societal problem than a
>technical one... ;)
>
>Lynn?
>
>Eric Tomson,
>Administrator and Secretary of the belgian Wallonia Chapter of the ISOC,
>Member of the PIR .ORG Advisory Council.


BTW.... this issue is obviously not confined to the US ..... the European 
Commission is clearly looking into these matters and any steps taken in 
North American should be coordinated with Brussels and the Member Countries.

Everything I have said about American bureaucrats I could easily say about 
European ones.  Honest, decent, underpaid, overworked etc.


 From the US perspective it does not take a doctorate in political science 
to figure out that "something" is going to happen in the US Congress this 
session. That means by the end of fall.

We, here in the US, and like minded folks in Europe, need to make sure its 
the "right thing" and not some kludge driven by lobbyists etc..and the 
lobbyists in Brussels are at least as good as those in DC ..so I'm told :-)

It was not hard to pick up at the FTC hearings from multiple Congressmen 
and Senators at the FTC hearings that " My daughter got 4 advertisements 
for Viagra this week ..." " My grandson got a picture in his e-mail box of 
just ...filth"   In the US the anti-spam issue is up there with Mother, 
Apple Pie, and the American Flag in bi-partisan political support.

Charles Schumer in particular was adamant that " You need funding for 
enforcement ..you got it.!!!!"

http://www.senate.gov/~schumer/

Its not unlike the support the FTC (Federal Trade Commission)

http://www.ftc.gov/bcp/conline/edcams/donotcall/index.html

BTW link to the FTC SPAM workshop

http://www.ftc.gov/bcp/workshops/spam/index.html

got for the TCPA  ..Telephone Consumer Protection Act and the Do not Call 
extensions.  When you get enough Congressmen, their wives, sons, 
daughters,  husbands, cousins, uncles, aunts not to mention their 
constitutients pissed off at having unsolicited phone calls in the middle 
of dinner you will get action.

We are, in the US, now at that point with SPAM.

I certainly hope ISOC can add a voice to this on behalf of us in the IETF.

Best wishes..



 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
Voice +1 571.434.5651 Cell : +1 703.593.2683,  Fax: +1 815.333.1237
<mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
  <http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<




From owner-ietf@ietf.org  Sun May 25 19:37:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15745
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 19:37:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19K4uZ-0007eW-L3
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 19:28:19 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19K4tw-0007bN-KN
	for ietf@asgard.ietf.org; Sun, 25 May 2003 19:27:40 -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 TAA15453;
	Sun, 25 May 2003 19:27:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K4sS-0001ih-00; Sun, 25 May 2003 19:26:08 -0400
Received: from out006pub.verizon.net ([206.46.170.106] helo=out006.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19K4sR-0001iY-00; Sun, 25 May 2003 19:26:07 -0400
Received: from earthlink.net ([4.65.81.213]) by out006.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030525232707.EBPL25800.out006.verizon.net@earthlink.net>;
          Sun, 25 May 2003 18:27:07 -0500
Message-ID: <3ED15063.F33C480B@earthlink.net>
Date: Sun, 25 May 2003 16:23:15 -0700
From: Peter Deutsch <pdeutsch@earthlink.net>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dave Crocker <dcrocker@brandenburg.com>
CC: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
References: <200305231957.PAA23163@ietf.org>
	 <20030523164919.164a908e.moore@cs.utk.edu> <3ECE9D05.4C530F51@swin.edu.au>
	 <3034502612.20030523200039@brandenburg.com>
	 <20030523235006.7fefae69.moore@cs.utk.edu>
	 <18041272266.20030523215329@brandenburg.com>
	 <20030524010211.1b7c3133.moore@cs.utk.edu>
	 <4446995696.20030524114049@brandenburg.com>
	 <20030524164820.140dd78b.moore@cs.utk.edu>
	 <20030525111200.GA5576@login.ecs.soton.ac.uk> <68365074.20030525102132@brandenburg.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out006.verizon.net from [4.65.81.213] at Sun, 25 May 2003 18:27:07 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

g'day,

Dave Crocker wrote:
...
> Also:  We have a jillion MIME types.  Why make a big deal out of this
> one?  What is the damage that is of concern?

Maybe you didn't pick up on it, but Keith did write:

# 2. the Introduction recommends use of NAT, which is nonstandard and
# known to often be a harmful practice.  

Seems obvious to me - Keith smells a NAT rat trying to get its nose
under the IETF tent flap, and is on the warpath again....  ;-)



				- peterd



-- 
---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software


             "I'm no stranger to sarcasm, Sir..."

                               - Red versus Blue

---------------------------------------------------------------------



From owner-ietf@ietf.org  Sun May 25 21:17:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17006
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 21:17:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19K6JM-000142-BC
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 20:58:00 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19K6Hj-00011P-FU
	for ietf@asgard.ietf.org; Sun, 25 May 2003 20:56:19 -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 UAA16691;
	Sun, 25 May 2003 20:56:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K6GE-0002AR-00; Sun, 25 May 2003 20:54:47 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K6GE-0002AJ-00; Sun, 25 May 2003 20:54:46 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h4Q0t4FW029372;
	Sun, 25 May 2003 17:55:05 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AEM01665;
	Sun, 25 May 2003 17:55:03 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id RAA15624; Sun, 25 May 2003 17:55:03 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16081.26087.647057.483003@thomasm-u1.cisco.com>
Date: Sun, 25 May 2003 17:55:03 -0700 (PDT)
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
In-Reply-To: <68365074.20030525102132@brandenburg.com>
References: <200305231957.PAA23163@ietf.org>
	<20030523164919.164a908e.moore@cs.utk.edu>
	<3ECE9D05.4C530F51@swin.edu.au>
	<3034502612.20030523200039@brandenburg.com>
	<20030523235006.7fefae69.moore@cs.utk.edu>
	<18041272266.20030523215329@brandenburg.com>
	<20030524010211.1b7c3133.moore@cs.utk.edu>
	<4446995696.20030524114049@brandenburg.com>
	<20030524164820.140dd78b.moore@cs.utk.edu>
	<20030525111200.GA5576@login.ecs.soton.ac.uk>
	<68365074.20030525102132@brandenburg.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dave Crocker writes:
 > TC> Sure, we have many IP-over-foo, but invariably foo is link layer.
 > 
 > IP over IP?
 > 
 > Also:  We have a jillion MIME types.  Why make a big deal out of this
 > one?  What is the damage that is of concern?

   Running code?

	   Mike



From owner-ietf@ietf.org  Sun May 25 22:00:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17692
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 22:00:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19K79N-0002ZX-3y
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 21:51:45 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19K74t-0002Nz-Sv
	for ietf@asgard.ietf.org; Sun, 25 May 2003 21:47:07 -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 VAA17484;
	Sun, 25 May 2003 21:47:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K73P-0002Qk-00; Sun, 25 May 2003 21:45:35 -0400
Received: from conure.mail.pas.earthlink.net ([207.217.120.54])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K73O-0002Qh-00; Sun, 25 May 2003 21:45:34 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by conure.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19K74l-0000LP-00; Sun, 25 May 2003 18:47:00 -0700
Date: Sun, 25 May 2003 21:45:37 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: moore@cs.utk.edu, dhc2@dcrocker.net, tjc@ecs.soton.ac.uk, iesg@ietf.org,
        ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
Message-Id: <20030525214537.0ad8fc8a.moore@cs.utk.edu>
In-Reply-To: <68365074.20030525102132@brandenburg.com>
References: <200305231957.PAA23163@ietf.org>
	<20030523164919.164a908e.moore@cs.utk.edu>
	<3ECE9D05.4C530F51@swin.edu.au>
	<3034502612.20030523200039@brandenburg.com>
	<20030523235006.7fefae69.moore@cs.utk.edu>
	<18041272266.20030523215329@brandenburg.com>
	<20030524010211.1b7c3133.moore@cs.utk.edu>
	<4446995696.20030524114049@brandenburg.com>
	<20030524164820.140dd78b.moore@cs.utk.edu>
	<20030525111200.GA5576@login.ecs.soton.ac.uk>
	<68365074.20030525102132@brandenburg.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Also:  We have a jillion MIME types.

most of them aren't standards-track.



From owner-ietf@ietf.org  Sun May 25 22:39:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18377
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 22:39:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19K7iR-0003nf-Iy
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 22:27:59 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19K7ff-0003ZI-Bb
	for ietf@asgard.ietf.org; Sun, 25 May 2003 22:25:07 -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 WAA18119
	for <ietf@ietf.org>; Sun, 25 May 2003 22:25:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K7eA-0002c4-00
	for ietf@ietf.org; Sun, 25 May 2003 22:23:34 -0400
Received: from tomts8.bellnexxia.net ([209.226.175.52] helo=tomts8-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19K7eA-0002c1-00
	for ietf@ietf.org; Sun, 25 May 2003 22:23:34 -0400
Received: from yahoo.com ([65.93.189.253]) by tomts8-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030526022504.CCJR5346.tomts8-srv.bellnexxia.net@yahoo.com>
          for <ietf@ietf.org>; Sun, 25 May 2003 22:25:04 -0400
Date: Sun, 25 May 2003 22:25:03 -0400
Subject: Re: spam
Content-Type: text/plain; delsp=yes; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: S Woodside <sbwoodside@yahoo.com>
To: <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
In-Reply-To: <000501c32253$f6707160$92082b45@a>
Message-Id: <41DDF4A2-8F21-11D7-975F-000393414368@yahoo.com>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Saturday, May 24, 2003, at 08:24  PM, Bill Cunningham wrote:

> http://story.news.yahoo.com/news?tmpl=story&u=/nm/20030524/wr_nm/ 
> tech_spam_dc_3
>
>     Is this what we want? The legal system taking over something that  
> should
> be done by IETF. This new legislation isn't supposed to stop e-mail
> marketing, but stop deception. Will it work? :-s

Technical measure to stop spam scare me. They usually involve building  
new technological barriers into the internet. Better to let civil  
society deal with (un)civil society problems.

simon




From owner-ietf@ietf.org  Sun May 25 22:46:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18549
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 May 2003 22:46:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19K7s7-00044H-LN
	for ietf-list@asgard.ietf.org; Sun, 25 May 2003 22:37:59 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19K7jf-0003nh-23
	for ietf@asgard.ietf.org; Sun, 25 May 2003 22:29:15 -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 WAA18192
	for <ietf@ietf.org>; Sun, 25 May 2003 22:29:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K7iA-0002dA-00
	for ietf@ietf.org; Sun, 25 May 2003 22:27:42 -0400
Received: from tomts23.bellnexxia.net ([209.226.175.185] helo=tomts23-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19K7i9-0002d7-00
	for ietf@ietf.org; Sun, 25 May 2003 22:27:41 -0400
Received: from yahoo.com ([65.93.189.253]) by tomts23-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030526022911.MEQV13490.tomts23-srv.bellnexxia.net@yahoo.com>
          for <ietf@ietf.org>; Sun, 25 May 2003 22:29:11 -0400
Date: Sun, 25 May 2003 22:29:11 -0400
Subject: Re: spam
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: S Woodside <sbwoodside@yahoo.com>
To: "IETF Discussion" <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
In-Reply-To: <093001c322af$60b28800$0a00000a@atkielski.com>
Message-Id: <D58BF8DF-8F21-11D7-975F-000393414368@yahoo.com>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Sunday, May 25, 2003, at 07:18  AM, Anthony Atkielski wrote:

> Does it matter?  It won't work, so it's not terribly important.  
> Legislators
> tend to develop the belief that they can cure a rainy day just by 
> enacting a
> new law, and often they are wrong.  They are wrong in this case, for
> example.

Good law could work to curtail spam. Spammers do it because it's 
profitable. Remove the profit, fine the dickens out of the worst 
transgressors, and the cost/benefit ratio will sink. Spamming isn't 
like hacking, there is always a way to trace back to the person who is 
paying for the spam because they must be able to sell their product. 
Since you can identify the individuals responsible, you can hold them 
accountable with the right laws in place.

simon




From owner-ietf@ietf.org  Mon May 26 02:11:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02491
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 02:11:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KB2k-0007T0-QZ
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 02:01:10 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KAyA-0006tz-3h
	for ietf@asgard.ietf.org; Mon, 26 May 2003 01:56:26 -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 BAA21288
	for <ietf@ietf.org>; Mon, 26 May 2003 01:56:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KAwf-0003TZ-00
	for ietf@ietf.org; Mon, 26 May 2003 01:54:53 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KAwe-0003TW-00
	for ietf@ietf.org; Mon, 26 May 2003 01:54:52 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207673 for ietf@ietf.org; Mon, 26 May 2003 00:55:51 -0500
Message-ID: <3ED1AC83.1080208@ehsco.com>
Date: Mon, 26 May 2003 00:56:19 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Joint legal/technical anti-spam effort
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Below is an example of how technology and the law could work together,
with both camps bringing essential pieces of the puzzle to the table.

What should be most obvious from this exercise is that there needs to be
somebody willing to intermediate between the legislature and the
engineers. Otherwise, they will produce ineffective laws and we will
produce ineffective technologies, both in isolation.

Objectives:

  minimize the need for post-transfer spam detection

    - provide technical measures for refusing mail prior to transfer

    - provide legal backup for when the technical measures are ignored

  fundamental premise is preservation of property rights

    - my bandwidth/storage/cpu is my property

    - this extends into privacy realm; some users may choose to put
      up virtual "no trespassing" signs and those prohibitions
      should be protected under the same principles (gradeschool
      children, emergency-responder mailboxes, hermits, etc)

Technical measures:

  Short-Term

    - RCPT TO response codes signifying acceptance levels, EG:

    - 250 (default) what the law allows by default

    - 255 (stiff) no solicitations at all

    - 259 (extreme) no trespassing -- authorized senders only

    - 25x allows interoperability but other codes may be more useful,

    - especially considering different jurisdictions will likely need
      their own codes

    - organizations can set default as policy requires, or can allow
      users to set according to preference

  Medium-Term

    - improve accountability measures in email

    - possibile work areas include encouraging authentication, PTRs,
      TLS and certificates, etc.

  Long-Term

    - reinvention of mail transfer service

    - eg, recursive signatures of modernized "Received" headers allow
      path validation at any hop

    - global directory technologies for key retrieval and other uses

Legal Measures:

  Must be defined per-jurisdiction but some US examples might be:

  Definitions

    - define problem messages as any solicitation, such as for money
      or action (eg "click here")

    - some exceptions such as charities, government, others, MAYBE

    - violations after grace period (1 year?) subject to law

  Protection

    - default case, recent prior relationship is okay

    - recipients may always refuse (eg, stronger response codes)

    - recipients may opt-out even if a current relationship exists

    - no opt-in explicitly required but encouraged by penalties

  Penalties

    - recipient has private civil recourse

    - $500 per unlawful recipient, treble for willful violations

    - can file against beneficiary if invalid recipient

    - can file against bulk-mailer if response codes ignored

    - "loser pays" written into law to prevent abuses

    - state reserves felony penalties for egregious violators

    - bulk-mailers implicitly encouraged to use documented opt-ins

So who would the IETF community trust to take something like (better than)
this to their jurisdictional legislature(s) and asks for feedback?

<cynic>and have they made the right campaign contributions</cynic>

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Mon May 26 03:13:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04305
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 03:13:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KBvi-0006f6-Qe
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 02:57:58 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KBuX-0006bs-VC
	for ietf@asgard.ietf.org; Mon, 26 May 2003 02:56:45 -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 CAA04000
	for <ietf@ietf.org>; Mon, 26 May 2003 02:56:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KBt3-00041E-00
	for ietf@ietf.org; Mon, 26 May 2003 02:55:13 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KBt2-00041B-00
	for ietf@ietf.org; Mon, 26 May 2003 02:55:12 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4Q6uh4B034859
	for <ietf@ietf.org>; Mon, 26 May 2003 08:56:43 +0200 (CEST)
Message-ID: <020b01c32353$f73d18e0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <000501c32253$f6707160$92082b45@a> <093001c322af$60b28800$0a00000a@atkielski.com> <3ED0D8B3.8070303@ehsco.com> <Pine.GSO.4.50.0305251626220.24020-100000@argos.ee.surrey.ac.uk> <3ED120AE.9000306@ehsco.com>
Subject: Re: spam
Date: Mon, 26 May 2003 08:56:43 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric writes:

> Nobody seems to think there is a cost associated
> with "hit delete"

There is; however, like the cost of sending spam itself, it is very low.

Even at a hundred dollars an hour, the cost of deleting spam each day with
the delete key (and even at the current rate of hundreds of spam per day) is
only $2-$3 ... several times cheaper than the daily cost of visiting a
restroom.

This being so, the argument that deleting spam is expensive is hard to
support.  It may be irritating, but it's not costly to delete, any more than
it is costly to throw junk postal mail in the trash while looking through
one's daily mail.




From owner-ietf@ietf.org  Mon May 26 03:33:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04653
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 03:33:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KCJv-0007JR-Hs
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 03:22:59 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KCFO-0007E2-N9
	for ietf@asgard.ietf.org; Mon, 26 May 2003 03:18:18 -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 DAA04479
	for <ietf@ietf.org>; Mon, 26 May 2003 03:18:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KCDt-00048p-00
	for ietf@ietf.org; Mon, 26 May 2003 03:16:45 -0400
Received: from mrburns.nildram.co.uk ([195.112.4.54])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KCDt-00048m-00
	for ietf@ietf.org; Mon, 26 May 2003 03:16:45 -0400
Received: from hourglass (unknown [81.6.214.202])
	by mrburns.nildram.co.uk (Postfix) with ESMTP
	id 88B4B1D7BB7; Mon, 26 May 2003 08:18:14 +0100 (BST)
From: "Christian de Larrinaga" <cdel@firsthand.net>
To: "Richard Shockey" <richard@shockey.us>, "Eric A. Hall" <ehall@ehsco.com>,
        <ietf@ietf.org>
Subject: RE: spam
Date: Mon, 26 May 2003 08:18:20 +0100
Message-ID: <MABBIEBOAFJNELEGFHCKOEKCIDAA.cdel@firsthand.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <5.2.0.9.2.20030525150925.050dc008@shockey.us>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Richard Shockey wrote...
> No one from the Internet Society was there BTW.

Consider setting up a US ISOC chapter or at least a US specific activity
that works at the local level like some of the national based chapters
around the world. Technical expertise needs to be involved so IETF'rs are
very much on the hook but there is a strength in working on awareness issues
within an organisational framework that is designed to do this like ISOC.


> If each of us do nothing I can guarantee you the Congress will
> screw it up...

same is true globally.


Christian de Larrinaga




From owner-ietf@ietf.org  Mon May 26 09:15:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10882
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 09:15:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KHcu-0003Jv-0I
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 09:02:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KHYY-0003Gi-Tf
	for ietf@asgard.ietf.org; Mon, 26 May 2003 08:58:26 -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 IAA10583
	for <ietf@ietf.org>; Mon, 26 May 2003 08:58:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KHX3-0005xm-00
	for ietf@ietf.org; Mon, 26 May 2003 08:56:53 -0400
Received: from [131.227.76.5] (helo=prue.eim.surrey.ac.uk ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KHX2-0005xj-00
	for ietf@ietf.org; Mon, 26 May 2003 08:56:53 -0400
Received: from argos.ee.surrey.ac.uk ([131.227.89.15] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 19KHYE-0002lS-00; Mon, 26 May 2003 13:58:06 +0100
Date: Mon, 26 May 2003 13:58:05 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@argos.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: S Woodside <sbwoodside@yahoo.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: spam
In-Reply-To: <D58BF8DF-8F21-11D7-975F-000393414368@yahoo.com>
Message-ID: <Pine.GSO.4.50.0305261357040.28832-100000@argos.ee.surrey.ac.uk>
References: <D58BF8DF-8F21-11D7-975F-000393414368@yahoo.com>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-104.5 required=5.5
	tests=AWL,BAYES_20,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_PINE,
	      USER_IN_WHITELIST
	autolearn=ham version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
X-Scanner: exiscan *19KHYE-0002lS-00*cuYfx6iRq6s* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sun, 25 May 2003, S Woodside wrote:

> Good law could work to curtail spam. Spammers do it because it's
> profitable. Remove the profit, fine the dickens out of the worst
> transgressors, and the cost/benefit ratio will sink. Spamming isn't
> like hacking, there is always a way to trace back to the person who is
> paying for the spam because they must be able to sell their product.
> Since you can identify the individuals responsible, you can hold them
> accountable with the right laws in place.

and this has worked so well with the War on Drugs.

L.

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>



From owner-ietf@ietf.org  Mon May 26 09:44:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11653
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 09:44:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KI62-00041a-LQ
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 09:33:02 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KI1r-0003yS-20
	for ietf@asgard.ietf.org; Mon, 26 May 2003 09:28:43 -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 JAA11313
	for <ietf@ietf.org>; Mon, 26 May 2003 09:28:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KI0L-0006CD-00
	for ietf@ietf.org; Mon, 26 May 2003 09:27:09 -0400
Received: from portal.hamachi.org ([140.239.227.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KI0L-0006C8-00
	for ietf@ietf.org; Mon, 26 May 2003 09:27:09 -0400
Received: from syn.hamachi.org (localhost [127.0.0.1])
	by portal.hamachi.org (Postfix) with ESMTP
	id 3E3981793A; Mon, 26 May 2003 09:28:36 -0400 (EDT)
Received: from syn.hamachi.org (sommerfeld@localhost)
	by syn.hamachi.org (8.12.7+Sun/8.8.8) with ESMTP id h4QDSdbI001996;
	Mon, 26 May 2003 09:28:39 -0400 (EDT)
Message-Id: <200305261328.h4QDSdbI001996@syn.hamachi.org>
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
To: "Eric A. Hall" <ehall@ehsco.com>
Cc: ietf@ietf.org
Subject: Re: Joint legal/technical anti-spam effort 
In-Reply-To: Your message of "Mon, 26 May 2003 00:56:19 CDT."
             <3ED1AC83.1080208@ehsco.com> 
Reply-To: sommerfeld@orchard.arlington.ma.us
Date: Mon, 26 May 2003 09:28:39 -0400
Xender: sommerfeld@syn.hamachi.org
Sender: owner-ietf@ietf.org
Precedence: bulk

> Technical measures:
> 
>   Short-Term
> 
>     - RCPT TO response codes signifying acceptance levels, EG:
> 
>     - 250 (default) what the law allows by default
> 
>     - 255 (stiff) no solicitations at all
> 
>     - 259 (extreme) no trespassing -- authorized senders only
> 
>     - 25x allows interoperability but other codes may be more useful,
> 
>     - especially considering different jurisdictions will likely need
>       their own codes
> 
>     - organizations can set default as policy requires, or can allow
>       users to set according to preference

 - virtual "no soliciting" signs may be more appropriate in some cases.

 - allow receiver to provide an (optional) indication of the receiving
host's or users's legal jurisdiction(s), so that the spammer can't
claim they don't know which set of rules apply.

						- Bill



From owner-ietf@ietf.org  Mon May 26 09:50:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11944
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 09:50:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KIFc-00048B-Lf
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 09:42:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KI8J-00041p-Qr
	for ietf@asgard.ietf.org; Mon, 26 May 2003 09:35:23 -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 JAA11439;
	Mon, 26 May 2003 09:35:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KI6o-0006DR-00; Mon, 26 May 2003 09:33:50 -0400
Received: from 64.221.212.135.ptr.us.xo.net ([64.221.212.135] helo=ns2.vivacenetworks.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19KI6n-0006DD-00; Mon, 26 May 2003 09:33:49 -0400
Received: from AMALISXP.vivacenetworks.com ([10.122.19.101]) by vivacenetworks.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 26 May 2003 06:34:49 -0700
Message-Id: <5.2.1.1.0.20030526093342.016fff58@mail.attbi.com>
X-Sender: vivacenet\amalis@po1.vivacenetworks.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Mon, 26 May 2003 09:34:43 -0400
To: Donald Eastlake 3rd <dee3@torque.pothole.com>
From: "Andrew G. Malis" <Andy.Malis@vivacenetworks.com>
Subject: Re: Last Call: IP over MIME to Proposed Standard
Cc: Keith Moore <moore@cs.utk.edu>, iesg@ietf.org, <ietf@ietf.org>
In-Reply-To: <Pine.LNX.4.44.0305232213110.15789-100000@zydeco.netbusters
 .com>
References: <20030523214409.78c58a24.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 26 May 2003 13:34:49.0807 (UTC) FILETIME=[94A985F0:01C3238B]
Sender: owner-ietf@ietf.org
Precedence: bulk

Donald,

I suggest you add a reference to RFC 1326.

Cheers,
Andy

--------

At 5/23/2003 10:14 PM -0400, Donald Eastlake 3rd wrote:
>Sure, one  experiment would be what the actual performance of an IP over
>MIME tunnel was.
>
>Thanks,
>Donald




From owner-ietf@ietf.org  Mon May 26 09:55:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12151
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 09:55:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KIFd-00048o-JE
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 09:42:57 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KID2-00044y-Mt
	for ietf@asgard.ietf.org; Mon, 26 May 2003 09:40:16 -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 JAA11558
	for <ietf@ietf.org>; Mon, 26 May 2003 09:40:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KIBX-0006GJ-00
	for ietf@ietf.org; Mon, 26 May 2003 09:38:43 -0400
Received: from 75.5.33.65.cfl.rr.com ([65.33.5.75] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KIBW-0006GG-00
	for ietf@ietf.org; Mon, 26 May 2003 09:38:42 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19JyBu-0004c2-00; Sun, 25 May 2003 12:17:46 -0400
Date: Sun, 25 May 2003 12:17:45 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: ietf@ietf.org
Subject: Re: Joint legal/technical anti-spam effort
In-Reply-To: <3ED1AC83.1080208@ehsco.com>
Message-ID: <Pine.LNX.4.44.0305251216180.10631-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

I have a mailbox at gmx, a german isp in england.  the anti-spam measures
recently enacted there now label all posts from ietf-announce as spam.  be
careful what you wish for.

scott



On Mon, 26 May 2003, Eric A. Hall wrote:

>
> Below is an example of how technology and the law could work together,
> with both camps bringing essential pieces of the puzzle to the table.
>
> What should be most obvious from this exercise is that there needs to be
> somebody willing to intermediate between the legislature and the
> engineers. Otherwise, they will produce ineffective laws and we will
> produce ineffective technologies, both in isolation.
>
> Objectives:
>
>   minimize the need for post-transfer spam detection
>
>     - provide technical measures for refusing mail prior to transfer
>
>     - provide legal backup for when the technical measures are ignored
>
>   fundamental premise is preservation of property rights
>
>     - my bandwidth/storage/cpu is my property
>
>     - this extends into privacy realm; some users may choose to put
>       up virtual "no trespassing" signs and those prohibitions
>       should be protected under the same principles (gradeschool
>       children, emergency-responder mailboxes, hermits, etc)
>
> Technical measures:
>
>   Short-Term
>
>     - RCPT TO response codes signifying acceptance levels, EG:
>
>     - 250 (default) what the law allows by default
>
>     - 255 (stiff) no solicitations at all
>
>     - 259 (extreme) no trespassing -- authorized senders only
>
>     - 25x allows interoperability but other codes may be more useful,
>
>     - especially considering different jurisdictions will likely need
>       their own codes
>
>     - organizations can set default as policy requires, or can allow
>       users to set according to preference
>
>   Medium-Term
>
>     - improve accountability measures in email
>
>     - possibile work areas include encouraging authentication, PTRs,
>       TLS and certificates, etc.
>
>   Long-Term
>
>     - reinvention of mail transfer service
>
>     - eg, recursive signatures of modernized "Received" headers allow
>       path validation at any hop
>
>     - global directory technologies for key retrieval and other uses
>
> Legal Measures:
>
>   Must be defined per-jurisdiction but some US examples might be:
>
>   Definitions
>
>     - define problem messages as any solicitation, such as for money
>       or action (eg "click here")
>
>     - some exceptions such as charities, government, others, MAYBE
>
>     - violations after grace period (1 year?) subject to law
>
>   Protection
>
>     - default case, recent prior relationship is okay
>
>     - recipients may always refuse (eg, stronger response codes)
>
>     - recipients may opt-out even if a current relationship exists
>
>     - no opt-in explicitly required but encouraged by penalties
>
>   Penalties
>
>     - recipient has private civil recourse
>
>     - $500 per unlawful recipient, treble for willful violations
>
>     - can file against beneficiary if invalid recipient
>
>     - can file against bulk-mailer if response codes ignored
>
>     - "loser pays" written into law to prevent abuses
>
>     - state reserves felony penalties for egregious violators
>
>     - bulk-mailers implicitly encouraged to use documented opt-ins
>
> So who would the IETF community trust to take something like (better than)
> this to their jurisdictional legislature(s) and asks for feedback?
>
> <cynic>and have they made the right campaign contributions</cynic>
>
> --
> Eric A. Hall                                        http://www.ehsco.com/
> Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/
>
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81




From owner-ietf@ietf.org  Mon May 26 11:04:05 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15830
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 11:04:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KJOV-0003wW-8U
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 10:56:11 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KJGE-0003mY-2M
	for ietf@asgard.ietf.org; Mon, 26 May 2003 10:47:38 -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 KAA15137
	for <ietf@ietf.org>; Mon, 26 May 2003 10:47:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KJEi-0006x1-00
	for ietf@ietf.org; Mon, 26 May 2003 10:46:04 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KJEg-0006wy-00
	for ietf@ietf.org; Mon, 26 May 2003 10:46:03 -0400
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200305261441.XAA03510@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id XAA03510; Mon, 26 May 2003 23:40:48 +0859
Subject: Simple Internet Protocol, Again
To: ietf@ietf.org
Date: Mon, 26 May 2003 23:40:46 +0859 ()
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-ietf@ietf.org
Precedence: bulk

Attached is a very rough draft to make IPv6 more deployable.

Don't I forget to forbid some of the so many useless features
of IPv6?

Comments are welcome.

						Masataka Ohta
---





INTERNET DRAFT                                                   M. Ohta
draft-ohta-sipa-00.txt                     Tokyo Institute of Technology
                                                                May 2003

                    Simple Internet Protocol, Again

Status of this Memo

   This document is an Internet-Draft and is subject to all provisions
   of Section 10 of RFC2026.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet- Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Abstract

   IPv6 has failed to be deployed partly because of its complexity.

   IPv6 mostly is a descendant of SIP (Simple Internet Protocol) but has
   fatally bloated merging with other proposals and trying to make IPv6
   has better functionality than IPv4, which makes IPv6 unnecessarily
   complex and, thus, worse than IPv4.

   SIPA (Simple Internet Protocol, Again) is a proposal attempting to
   restore simplicity to IPv6 sticking to the real world operational
   requirements for the IPv4 Internet to make IPv6 more acceptable to
   ISPs and end users.

1. Introduction

   IPv6 has failed to be deployed partly because of its complexity.

   It is a complexity of not only coding but also operation.  It should
   be noted that, even though running code may be widely available, it
   is not because IPv6 is so simple that implementors enjoyed coding



M. Ohta               Expires on November 25, 2003              [Page 1]

INTERNET DRAFT      Simple Internet Protocol, Again             May 2003


   (which was why, in good old days, running code principle was a good
   measure of protocol quality) but because governments and vendors put
   large amount of effort and money on it.  Still, among so many IPv4
   ISPs, few operate it and ratio of IPv6 end users to IPv4 ones are
   even smaller.

   Deployment is an operational issue and IPv6 has failed and will
   continue to be failing to be deployed.

   IPv6 mostly is a descendant of SIP (Simple Internet Protocol) but has
   fatally bloated merging with other proposals and trying to make IPv6
   have better functionality than IPv4, which makes IPv6 unnecessarily
   complex and, thus, worse than IPv4.

   SIPA (Simple Internet Protocol, Again) is a proposal attempting to
   restore simplicity to IPv6 sticking to the real world operational
   requirements for the IPv4 Internet, to make IPv6 more acceptable to
   ISPs and end users.

   With SIPA, IPv6 should become easy to code and operate.

   In this memo, legacy IPv6 is called CIP (Complex IP), "the Internet"
   means one in the real world, that is, the IPv4 Internet, and a router
   is a host.

2. Requirements

   The original requirement for CIP was:

      Support large number of hosts large enough to make the IPv6
      Internet for everyone.

   which resulted in bloated CIP.

   The followings are the additional requirements to SIPA based on the
   operational reality of the Internet.

      Suppress the number of global routing table entries even if
      everyone are multihomed to the IPv6 Internet.

      Make packet format compatible to CIP to make SIPA work over legacy
      routers.

      Remove all the features of CIP against the end to end principle.

      Remove all the features of CIP not present in IPv4. No
      applications on the Internet use them.




M. Ohta               Expires on November 25, 2003              [Page 2]

INTERNET DRAFT      Simple Internet Protocol, Again             May 2003


      Remove all the features of CIP not used in IPv4 Internet. No
      applications on the Internet use them.

      Remove all the features of CIP not useful in IPv4 Internet. No
      applications on the Internet need them.

3. Removed Features

   The following subsections list features of IPv6 removed to make IPv6
   simpler and more deployable.

3.1 IP Header Options

   Optional headers are not used on the Internet and is forbidden.
   Except for an optional fragmentation header, which is used on the
   Internet, a transport header follows immediately after an IP header.

   Options visible to routers is a direct violation of the end to end
   principle and just harmful.

   Note that use of a routing header by MIPv6 is architecturally wrong,
   as a home agent is, like mail relays, an end system that it should be
   an destination option.

   In addition, except for a fragmentation header, destination option is
   still forbidden. It should be implemented at protocol (see section
   3.3, for example) or transport level.

3.2 ToS & Flow Labels

   ToS & flow labels are forbidden. RSVP is far less deployed than IPv6.
   Even if it is deployed, removal of IP header options makes it easy
   for routers access port numbers or SPI (see section 3.3) that flow
   labels are not unnecessary.

   While the field for ToS & flow labels is large enough to hold
   fragmentation information (because MTU is large) not as an optional
   header, it makes SIPA not compatible to CIP.

   So, for possible future extension (such as that ECN is proven to be
   useful over the Internet), the field should contain 0 at the source
   and ignored by routers and the destination.

3.3 IPSEC

   ESP is purely optional and should be implemented as Protocol 50. SPI
   works as port numbers for resource reservation (if any).  AH is
   forbidden because its functionality overridden by ESP and its SPI is



M. Ohta               Expires on November 25, 2003              [Page 3]

INTERNET DRAFT      Simple Internet Protocol, Again             May 2003


   not located at port number part.

3.4 Path MTU Discoverly

   Path MTU discoverly is forbidden.  It often does not work over the
   Internet for various reasons.  As the MTU of the Internet is mostly
   1500 that minimum MTU of 1280 is good enough.

   Routers are encouraged to silently drop packets lager than 1280 byte
   without generating ICMP.

3.5 Stateless Autoconfiguration

   IPv6 specific stateless autoconfiguration is ignored.  Use DHCP.

   All the possible autoconfiguration can be (and is already, for most
   of the case) implemented with DHCP over the Internet.

   The remaining autoconfiguration features may work in an isolated
   private LAN but is not meaningful over the Internet.  Note, for
   example, that both dentists' offices and cars have preconfigured
   locks and keys.

   Issues on autoconfiguration in an isolated private LAN may still be
   solved, but in a way not affecting the development of the Internet
   protocol nor, hopefully, IETF.

3.6 Automatic Renumbering

   Automatic renumbering of IP addresses of DNS glue is ignored.

   On the Internet, automatic renumbering is trivially easy, as long as
   domain names, not raw IP addresses, are used to designate hosts.
   However, automatic renumbering of DNS glue is impossible, because
   relationship between DNS servers has nothing to do with ISP topology.

3.7 Hosts and Routers

   It is a direct violation of the end to end principle to assume
   intermediate systems intelligent and end systems dumb.  Routers are
   hosts relay packets between multiple interfaces, thus, actively
   engages in generating routing tables. As has been the tradition of
   early days of the Internet, hosts with single interface are still
   expected to listen to IGP (e.g. routed -q). Note that DHCP can tell
   hosts which IGP to use. Note also that global routing table is
   assumed to be small.

3.8 Neighbor Discovery



M. Ohta               Expires on November 25, 2003              [Page 4]

INTERNET DRAFT      Simple Internet Protocol, Again             May 2003


   Neighbor discovery is not used on the Internet and is forbidden.  It
   has hopelessly bloated, partly because of a failed attempt to support
   ATM (IPv6 thought multicast over ATM were easy) and partly because of
   another failed attempt to support stateless autoconfiguration.

   As for address resolution, the original purpose of ND, except for the
   last hop, address resolution information for next hop routers become
   available from IGP exchange. In other cases, use ARP or let hosts
   speak IGP.

3.9 Jumbograms

   Jumbograms are not used on the Internet and is forbidden.  Super
   computers today are massively parallel ones that it has enough scalar
   power to handle streams of 64KB of packets.

3.10 Link & Site Local Address

   Link and site local address is not used on the Internet and is
   forbidden.

   Note that a network behind NAT is not a part of the Internet. One may
   still use NAT with IPv6, but it has nothing to do with IPv4 or IPv6
   specification.

4. Other Restriction to CIP

   To ease implementations, a router can forward packets to the next hop
   by looking at upper 64 bits of an destination address only.
   Multicast address format should be reconsidered accordingly.

   A host can accept packets to it by looking at lower 64 bits of an
   destination address only.

5. Remaining Works

   Multi6 WG is working on site multihoming of IPv6, at least
   theoretically.

   However, as there can be limited number of ASes operated at TLAs,
   support for NLA level ASes multihomed to TLA level ASes must be
   discussed somewhere.

   Mobility must be tightly integrated with multihoming, as both treats
   multiple IP addresses of a host, that current specifications on MIPv6
   must be ignored.

6. Security Considerations



M. Ohta               Expires on November 25, 2003              [Page 5]

INTERNET DRAFT      Simple Internet Protocol, Again             May 2003


   IPSEC sucks.

7. Author's Address

   Masataka Ohta
   Graduate School of Information Science and Engineering
   Tokyo Institute of Technology
   2-12-1, O-okayama, Meguro-ku, Tokyo 152-8552, JAPAN

   Phone: +81-3-5734-3299
   Fax: +81-3-5734-3299
   EMail: mohta@necom830.hpcl.titech.ac.jp







































M. Ohta               Expires on November 25, 2003              [Page 6]




From owner-ietf@ietf.org  Mon May 26 12:14:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17010
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 12:14:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KKME-00050p-Kl
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 11:57:54 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KKLa-0004y8-1o
	for ietf@asgard.ietf.org; Mon, 26 May 2003 11:57:14 -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 LAA16798
	for <ietf@ietf.org>; Mon, 26 May 2003 11:57:11 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KKK4-0007S1-00
	for ietf@ietf.org; Mon, 26 May 2003 11:55:40 -0400
Received: from h80ad26a4.async.vt.edu ([128.173.38.164] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KKK2-0007Ry-00
	for ietf@ietf.org; Mon, 26 May 2003 11:55:39 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h4QFv0a7012902;
	Mon, 26 May 2003 11:57:00 -0400
Message-Id: <200305261557.h4QFv0a7012902@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: "Eric A. Hall" <ehall@ehsco.com>
Cc: ietf@ietf.org
Subject: Re: Joint legal/technical anti-spam effort 
In-Reply-To: Your message of "Mon, 26 May 2003 00:56:19 CDT."
             <3ED1AC83.1080208@ehsco.com> 
References: <3ED1AC83.1080208@ehsco.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1511886909P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 26 May 2003 11:56:59 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1511886909P
Content-Type: text/plain; charset=us-ascii

On Mon, 26 May 2003 00:56:19 CDT, "Eric A. Hall" <ehall@ehsco.com>  said:

>     - RCPT TO response codes signifying acceptance levels, EG:
>     - 250 (default) what the law allows by default
>     - 255 (stiff) no solicitations at all
>     - 259 (extreme) no trespassing -- authorized senders only
>     - 25x allows interoperability but other codes may be more useful,

(a) this isn't usefully backwards-compatible - it only helps if you're
talking to another upgraded MTA.  As such, given the usual glacial upgrade
speed, this isn't a short-term solution.

>     - especially considering different jurisdictions will likely need
>       their own codes

See Don Eastlake's I-D:

http://www.ietf.org/internet-drafts/draft-eastlake-xxx-05.txt

You're looking at a lot of the same issues.

--==_Exmh_-1511886909P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+0jlLcC3lWbTT17ARAn6NAJ48qhiZtRJaLh9ltT1yB4QF0SBZhQCguMLQ
cCqlYGXgFPtsuHeVPBjouuI=
=WS5l
-----END PGP SIGNATURE-----

--==_Exmh_-1511886909P--



From owner-ietf@ietf.org  Mon May 26 12:22:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17332
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 12:22:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KKao-00059G-Lq
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 12:12:58 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KKXX-00056U-HZ
	for ietf@asgard.ietf.org; Mon, 26 May 2003 12:09:35 -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 MAA16964
	for <ietf@ietf.org>; Mon, 26 May 2003 12:09:32 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KKW1-0007VU-00
	for ietf@ietf.org; Mon, 26 May 2003 12:08:01 -0400
Received: from h80ad26a4.async.vt.edu ([128.173.38.164] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KKW0-0007VR-00
	for ietf@ietf.org; Mon, 26 May 2003 12:08:00 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h4QG9Ka7012963;
	Mon, 26 May 2003 12:09:20 -0400
Message-Id: <200305261609.h4QG9Ka7012963@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Anthony Atkielski <anthony@atkielski.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: spam 
In-Reply-To: Your message of "Mon, 26 May 2003 08:56:43 +0200."
             <020b01c32353$f73d18e0$0a00000a@atkielski.com> 
References: <000501c32253$f6707160$92082b45@a> <093001c322af$60b28800$0a00000a@atkielski.com> <3ED0D8B3.8070303@ehsco.com> <Pine.GSO.4.50.0305251626220.24020-100000@argos.ee.surrey.ac.uk> <3ED120AE.9000306@ehsco.com>
            <020b01c32353$f73d18e0$0a00000a@atkielski.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1499213160P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 26 May 2003 12:09:20 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1499213160P
Content-Type: text/plain; charset=us-ascii

On Mon, 26 May 2003 08:56:43 +0200, Anthony Atkielski <anthony@atkielski.com>  said:

> Even at a hundred dollars an hour, the cost of deleting spam each day with
> the delete key (and even at the current rate of hundreds of spam per day) is
> only $2-$3 ... several times cheaper than the daily cost of visiting a
> restroom.

Note that visiting the restroom gets a LOT more expensive if you have to
remodel the restroom and add more stalls because everybody is doing it all
the time.

Similarly, if your *LAST* mail server was a Sun E6500 and 4 Mirapoint boxes and
various other small things like a load balancer, it's expensive to upgrade to a
new box just so all your users can spend money hitting delete...  Also,
remember that although 20 pieces of spam a day is only a 5% increase in
in my mail volume, I clear my stuff off the server on a regular basis.
For the user who gets 5-6 pieces of mail a day and only checks once a week,
that's a *big* jump in how much disk space they consume.

So we're spending a big chunk of money to pay for a bigger CPU to receive twice as much mail as we'd
like (which would probably be even higher if we didn't have one person who
spends a *big* chunk of their day figuring what domains the spamhauses are
using THIS week so we can blackhole them), and pay for more disk space to
store all the stuff (and don't forget the second-order effects of needing
even MORE CPU/I/O to manage the bigger file store) - and all this so people
can JUST HIT DELETE ON IT ANYHOW.

What's wrong with this picture?

Sure, hitting delete isn't expensive for one person.  Scale that to our
80K mailboxes and include all the infrastructure costs, and suddenly you're
quite easily looking at $1M/year or more.

--==_Exmh_-1499213160P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+0jwwcC3lWbTT17ARAtAFAJ9SDT/mY7Thl3jPjuopLH2tsdNHNwCg3Yq5
KkBbyVciGYmtSBn79jNjWA8=
=jfUe
-----END PGP SIGNATURE-----

--==_Exmh_-1499213160P--



From owner-ietf@ietf.org  Mon May 26 12:30:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17535
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 12:30:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KKkS-0005uo-Pj
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 12:22:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KKcH-00059I-Bp
	for ietf@asgard.ietf.org; Mon, 26 May 2003 12:14:29 -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 MAA16999
	for <ietf@ietf.org>; Mon, 26 May 2003 12:14:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KKal-0007WE-00
	for ietf@ietf.org; Mon, 26 May 2003 12:12:55 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KKal-0007WB-00
	for ietf@ietf.org; Mon, 26 May 2003 12:12:55 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207698; Mon, 26 May 2003 11:13:54 -0500
Message-ID: <3ED23D60.5010900@ehsco.com>
Date: Mon, 26 May 2003 11:14:24 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Valdis.Kletnieks@vt.edu
CC: ietf@ietf.org
Subject: Re: Joint legal/technical anti-spam effort
References: <3ED1AC83.1080208@ehsco.com> <200305261557.h4QFv0a7012902@turing-police.cc.vt.edu>
In-Reply-To: <200305261557.h4QFv0a7012902@turing-police.cc.vt.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/26/2003 10:56 AM Valdis.Kletnieks@vt.edu wrote:
> On Mon, 26 May 2003 00:56:19 CDT, "Eric A. Hall" <ehall@ehsco.com>
> said:
> 
>> - RCPT TO response codes signifying acceptance levels, EG: - 250
>> (default) what the law allows by default - 255 (stiff) no
>> solicitations at all - 259 (extreme) no trespassing -- authorized
>> senders only - 25x allows interoperability but other codes may be
>> more useful,
> 
> (a) this isn't usefully backwards-compatible - it only helps if you're 
> talking to another upgraded MTA.  As such, given the usual glacial
> upgrade speed, this isn't a short-term solution.

Bulk-mailers as senders are a small enough scope that forced upgrades
within a grace-period window is feasible.

No recipients have to upgrade unless they want stronger rejection levels
over the default. Every system that generates 250 today would have the
default protection tomorrow.

There is some validity to the argument that non-spamming senders would
have to upgrade to recognize the stronger codes. Perhaps this is the best
argument for using codes other than 25x.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Mon May 26 12:35:48 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17819
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 12:35:48 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KKkT-0005xy-JJ
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 12:22:57 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KKkG-0005rx-DO
	for ietf@asgard.ietf.org; Mon, 26 May 2003 12:22:44 -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 MAA17383
	for <ietf@ietf.org>; Mon, 26 May 2003 12:22:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KKik-0007d9-00
	for ietf@ietf.org; Mon, 26 May 2003 12:21:10 -0400
Received: from pop015pub.verizon.net ([206.46.170.172] helo=pop015.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KKij-0007c3-00
	for ietf@ietf.org; Mon, 26 May 2003 12:21:10 -0400
Received: from earthlink.net ([4.65.81.213]) by pop015.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030526162211.DDRA20810.pop015.verizon.net@earthlink.net>;
          Mon, 26 May 2003 11:22:11 -0500
Message-ID: <3ED23E38.7BFDE254@earthlink.net>
Date: Mon, 26 May 2003 09:18:00 -0700
From: Peter Deutsch <pdeutsch@earthlink.net>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
CC: S Woodside <sbwoodside@yahoo.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: spam
References: <D58BF8DF-8F21-11D7-975F-000393414368@yahoo.com> <Pine.GSO.4.50.0305261357040.28832-100000@argos.ee.surrey.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at pop015.verizon.net from [4.65.81.213] at Mon, 26 May 2003 11:22:11 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Lloyd Wood wrote:
> 
> On Sun, 25 May 2003, S Woodside wrote:
> 
> > Good law could work to curtail spam. Spammers do it because it's
> > profitable. Remove the profit, fine the dickens out of the worst
> > transgressors, and the cost/benefit ratio will sink. Spamming isn't
> > like hacking, there is always a way to trace back to the person who is
> > paying for the spam because they must be able to sell their product.
> > Since you can identify the individuals responsible, you can hold them
> > accountable with the right laws in place.
> 
> and this has worked so well with the War on Drugs.

There is a difference here - the recipients want to see the flow stop,
so can be expected to participate in supression activities. This is not
to say this will be easy, but it's a matter of creating a suitable set
of conditions and in this case you can assign some part of the task
(e.g. reporting potential transgressions) to the recipients who want to
play...

				- peterd


-- 
---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software


             "I'm no stranger to sarcasm, Sir..."

                               - Red versus Blue

---------------------------------------------------------------------



From owner-ietf@ietf.org  Mon May 26 13:33:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18863
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 13:33:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KLbk-0007NK-PT
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 13:18:00 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KLZJ-0007K5-Jc
	for ietf@asgard.ietf.org; Mon, 26 May 2003 13:15:29 -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 NAA18530
	for <ietf@ietf.org>; Mon, 26 May 2003 13:15:26 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KLXn-00008g-00
	for ietf@ietf.org; Mon, 26 May 2003 13:13:55 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KLXn-00008d-00
	for ietf@ietf.org; Mon, 26 May 2003 13:13:55 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h4QHFNbM001515;
	Mon, 26 May 2003 13:15:23 -0400
Message-Id: <200305261715.h4QHFNbM001515@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: "Eric A. Hall" <ehall@ehsco.com>
Cc: ietf@ietf.org
Subject: Re: Joint legal/technical anti-spam effort 
In-Reply-To: Your message of "Mon, 26 May 2003 11:14:24 CDT."
             <3ED23D60.5010900@ehsco.com> 
References: <3ED1AC83.1080208@ehsco.com> <200305261557.h4QFv0a7012902@turing-police.cc.vt.edu>
            <3ED23D60.5010900@ehsco.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1921120801P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 26 May 2003 13:15:23 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1921120801P
Content-Type: text/plain; charset=us-ascii

On Mon, 26 May 2003 11:14:24 CDT, "Eric A. Hall" said:

> Bulk-mailers as senders are a small enough scope that forced upgrades
> within a grace-period window is feasible.

The people that are the problem have a horrible tendency to not follow
the *CURRENT* RFCs (things like ignoring MX records, syntactically borked
MAIL FROM:, the whole gamut).

What makes you think they'd upgrade to software that would diminish their
ability to spam people who didn't want to be spammed?

--==_Exmh_-1921120801P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+0kurcC3lWbTT17ARAiDGAKDc8sZ4tFtlBXuF27TX30ad4RaY2gCfdZAg
7kde4ndwcIWskxxoVERh3Dc=
=rde+
-----END PGP SIGNATURE-----

--==_Exmh_-1921120801P--



From owner-ietf@ietf.org  Mon May 26 13:40:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19040
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 13:40:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KLq9-0007Wc-SI
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 13:32:53 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KLeC-0007NM-Ub
	for ietf@asgard.ietf.org; Mon, 26 May 2003 13:20:32 -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 NAA18606
	for <ietf@ietf.org>; Mon, 26 May 2003 13:20:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KLch-0000B0-00
	for ietf@ietf.org; Mon, 26 May 2003 13:18:59 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KLcg-0000Ax-00
	for ietf@ietf.org; Mon, 26 May 2003 13:18:58 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207699; Mon, 26 May 2003 12:19:58 -0500
Message-ID: <3ED24CD3.50409@ehsco.com>
Date: Mon, 26 May 2003 12:20:19 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Valdis.Kletnieks@vt.edu
CC: ietf@ietf.org
Subject: Re: Joint legal/technical anti-spam effort
References: <3ED1AC83.1080208@ehsco.com> <200305261557.h4QFv0a7012902@turing-police.cc.vt.edu>            <3ED23D60.5010900@ehsco.com> <200305261715.h4QHFNbM001515@turing-police.cc.vt.edu>
In-Reply-To: <200305261715.h4QHFNbM001515@turing-police.cc.vt.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/26/2003 12:15 PM Valdis.Kletnieks@vt.edu wrote:
> On Mon, 26 May 2003 11:14:24 CDT, "Eric A. Hall" said:
> 
>>Bulk-mailers as senders are a small enough scope that forced upgrades
>>within a grace-period window is feasible.
> 
> The people that are the problem have a horrible tendency to not follow
> the *CURRENT* RFCs (things like ignoring MX records, syntactically borked
> MAIL FROM:, the whole gamut).
> 
> What makes you think they'd upgrade to software that would diminish their
> ability to spam people who didn't want to be spammed?

That's what the penalties are for. The people who are doing that kind of
stuff today do it because there isn't any penalty for doing so.

A grace period gives them time to get their act together, to honor the
law, to clean their lists, etc. After that, bombs away.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Mon May 26 13:50:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19316
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 13:50:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KM2y-0008NX-8r
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 13:46:08 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KLsI-0007s9-Cj
	for ietf@asgard.ietf.org; Mon, 26 May 2003 13:35:06 -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 NAA19001
	for <ietf@ietf.org>; Mon, 26 May 2003 13:35:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KLqm-0000HF-00
	for ietf@ietf.org; Mon, 26 May 2003 13:33:32 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KLqm-0000Gb-00
	for ietf@ietf.org; Mon, 26 May 2003 13:33:32 -0400
Content-class: urn:content-classes:message
Subject: RE: spam
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Mon, 26 May 2003 10:34:54 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F820@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: spam
Thread-Index: AcMjiPKJ33FI+TfPSNaac0JZ3B1xAAAImpmw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Lloyd Wood" <L.Wood@eim.surrey.ac.uk>
Cc: "IETF Discussion" <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA19316

>> S Woodside wrote:
>> Good law could work to curtail spam. Spammers do it because
>> it's profitable. Remove the profit, fine the dickens out of
>> the worst transgressors, and the cost/benefit ratio will
>> sink. Spamming isn't like hacking, there is always a way to
>> trace back to the person who is paying for the spam because
>> they must be able to sell their product. Since you can
>> identify the individuals responsible, you can hold them
>> accountable with the right laws in place.

> Lloyd Wood wrote:
> and this has worked so well with the War on Drugs.

I was about to make a similar comment. In the US teen buy drugs partly
because it's easier to obtain than booze (drug dealers don't check ID to
see if you are 21 or older).

This has worked so well with Napster too. Instead of fighting a
well-known legal entity now they are down hunting individuals and
distributed systems and it has never been easier to download mp3s.

Michel.
 



From owner-ietf@ietf.org  Mon May 26 13:55:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19557
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 13:55:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KM2y-0008Ni-FB
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 13:46:08 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KLuH-0007sN-EU
	for ietf@asgard.ietf.org; Mon, 26 May 2003 13:37:09 -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 NAA19016
	for <ietf@ietf.org>; Mon, 26 May 2003 13:37:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KLsl-0000I4-00
	for ietf@ietf.org; Mon, 26 May 2003 13:35:35 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KLsj-0000Hr-00
	for ietf@ietf.org; Mon, 26 May 2003 13:35:34 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.9/8.12.9) id h4QHb0DQ020554
	for ietf@ietf.org env-from <vjs>;
	Mon, 26 May 2003 11:37:00 -0600 (MDT)
Date: Mon, 26 May 2003 11:37:00 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200305261737.h4QHb0DQ020554@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: Joint legal/technical anti-spam effort
References:  <200305261715.h4QHFNbM001515@turing-police.cc.vt.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Valdis.Kletnieks@vt.edu

> > Bulk-mailers as senders are a small enough scope that forced upgrades
> > within a grace-period window is feasible.
>
> The people that are the problem have a horrible tendency to not follow
> the *CURRENT* RFCs (things like ignoring MX records, syntactically borked
> MAIL FROM:, the whole gamut).
>
> What makes you think they'd upgrade to software that would diminish their
> ability to spam people who didn't want to be spammed?

See also standards track RFC 2919 which is supposed to identify bulk
mail and which this mailing list does not follow.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Mon May 26 14:00:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19749
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 14:00:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KM2z-0008Q6-9S
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 13:46:09 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KLzS-0008HA-UF
	for ietf@asgard.ietf.org; Mon, 26 May 2003 13:42:30 -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 NAA19207
	for <ietf@ietf.org>; Mon, 26 May 2003 13:42:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KLxw-0000Le-00
	for ietf@ietf.org; Mon, 26 May 2003 13:40:56 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KLxw-0000Lb-00
	for ietf@ietf.org; Mon, 26 May 2003 13:40:56 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id NAA22860;
	Mon, 26 May 2003 13:39:06 -0400
Date: Mon, 26 May 2003 13:40:07 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Bill Cunningham <billc44@citynet.net>
cc: ietf@ietf.org, <watha@monitortan.com>, <phil@whirlycott.com>
Subject: Re: spam
In-Reply-To: <000501c32253$f6707160$92082b45@a>
Message-ID: <Pine.LNX.4.44.0305261205180.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 24 May 2003, Bill Cunningham wrote:

> http://story.news.yahoo.com/news?tmpl=story&u=/nm/20030524/wr_nm/tech_spam_d
> c_3
>
>     Is this what we want? The legal system taking over something that should
> be done by IETF. This new legislation isn't supposed to stop e-mail
> marketing, but stop deception. Will it work? :-s

There are 3 types of email that we generally call spam:

Type 1: Bonafide Messaging with a real Commercial or non-profit(ie
political) purpose.  This includes people selling contraband (eg drugs)
illegally, so long as they intend to deliver the illegal goods.

Type 2: Bonafide fraudulent activity. Someone is really trying to get your
money, but has no intentions of honoring their obligations to the purchase
contract.  This includes bonafide attempts at identify theft.

Type 3: Annoyance activity. This has no bonafide intention of getting
money or even personal information, even though at a casual glance it may
appear so.  Type 3 is broken into 2 subtypes:

Type 3A is a relatively harmless disgruntled person, who is not terribly
sophisticated in their abuse, or in hiding their tracks. This type can be
handled by warnings or account termination. Besides spam, this type is
also involved in small DOS attacks and other unsophisticated abuse.

Type 3B is a career criminal using viruses and rooted machines to conduct
annoyance, which is frequently just another type of DOS attack, but
targeted perhaps at an email address, or perhaps at a domain. This type of
attacker is already a career criminal, having broken into many, often
hundreds of computers, illegally. This type cannot be dealt with
effectively by ISPs, because they are reasonable adept at hiding their
tracks. Usually, the ISP only detects the infected computer, but does not
identify or catch the cracker.



Of these types of spam, Type 1 and Type 2 can be dealt with by law, and
through the actions of the FTC and other regulatory agencies. Once
something has been determined to be contraband, then the appropriate
enforcement agency is called in.  Type 3A can be handled by the ISP or
their employer. Type 3B is much more difficult to handle.

What is unclear is how much of the total spam is due to each of these
types.  A lot of the spam that I recieve, and I have kept all this for
some time now, appears to be from type 3B. It is possible that my previous
conflicts with radical anti-spammers may affect the type and proportion of
spam that I get.  My testing and logging of a large block of IP address
space over a period of years, has indicated that much abuse is supported
and promoted by certain open relay blacklists which scan for, and then
advertise open relays and open proxies to abuse.  Relays scanned by such
organizations have shown up on commercial sites selling this information.
such as helllabs.com.ua. The question of whether this activity is merely
exploited or done with active participation seems to be prejudicially
answered by the fact that the "blacklists" advertise input addresses even
though these have no utility to "normal" users of the blacklist.  This
type of abuse (Type 3B) is often done with their ISPs ignoring both their
illegal scanning, and their solicitation of abuse, false advertising,and
other issuses. It is becoming more common for such activities to try to
operately completely anonymously, or to use false out-of-country addresses
to avoid prosecution[1].  It is unclear how much this type of abuse
contributes to the total spam volume.

I note that helllabs.com.ua makes false and misleading claims that relays
and proxies are free.  The anonymity claimed by a customer's product
(www.ghostsender.com) is also false.  And of course, if the spam is of
Type 1 or Type 2, there is no anonymity at all.  Frauds (Type 2) that
obtain money are easy to track via mail fraud or wire fraud.  Only abuse
of Type 3 is hard to track, and requires law enforcement powers to obtain
the required information.

Legislation of the type we have seen is not going to any affect on Type
3B, as this type is already committing federal felonies, and the
equivalent in many countries.  But we don't need additional legislation
for this activity since it is already a federal felony with a 5 year jail
term.  The problem is catching the culprit.  This is partly an issue of
law enforcement interest in catching these "harmless" criminals.

Whether the legislation has any affect on total spam will depend on the
proportion of the various types of spam.


With that in mind, we can consider what the IETF can do: The IETF can
specify protocols. But what protocols can be specified to reduce or
eliminate spam?

Dr. Claude Shannon, one of the founders of the science of Information
Theory, proved that it is impossible to prove the non-existance of a
covert channel. In terms of spam, this means that it is impossible to
construct a protocol that cannot be abused, since one cannot prove that it
is impossible (the channel can't exist) to send abuse (a covert channel).
No protocol can ever be constructed that is spam-free.  Radical
anti-spammers often try to couch their arguments as though the spammers
are "outsiders" who have been let in. This isn't true. All abusers are the
customer of some ISP, somewhere. There are no outsiders.  The spammers are
in fact authorized users of some ISP that are authorized to send email.
They remain authorized to send email until they lose service with that
ISP.  Once this is understood, it is completely obvious even without the
formality of Shannon's theorem that protocols such as SMTP AUTH will have
no effect whatsoever.

So IETF efforts in this area are limited to finding means of identifying
the abuser, once the abuser has been detected. There is also the technical
task of detecting abuse.

Once law enforcement becomes involved to make the appropriate requests of
different ISPs, it has not been a technically difficult matter to track
down abusers. Though the technical know-how seems to elude the Law
Enforcement Authorities (e.g. Kevin Mitnick) until a technically
knowledgeable person becomes involved (Shimomura)[2]. There are many
examples of persons who have been arrested for using the internet to make
bomb threats, as well as persons who have released particularly dangerous
viruses, and persons who have cracked computers belonging to financial
institutions.  Once there is a law enforcement interest in finding the
identity of the people involved, there seems to be little technical
obstacle other than technical competence to finding the people. So I think
there is little to be done technically so far as identification goes.

The issue of detecting abuse was the focus of the MIT anti-spam
conference.  There are many paths presently being pursued: Blacklists,
header analysis, and various kinds of content analysis.  I think the
general consensus was that content analysis offers the most promising
means of detecting and blocking abuse.  I think it is too early to tell
how protocols can be helpful in this area, or if new protocols are
necessary. One scheme, used by MSN, gives the user a button to submit a
message as spam. Their system then tracks the number of complaints
involving characteristics of the message, and blocks messages accordingly,
and on per-user control. Of course, this requires no change to any
protocols, just to applications.

		--Dean


[1] SPEWS has attemtped to avoid prosecution and legal responsibility by
remaining completely anonymous. ORBZ.ORG was criminally investigated for
crashing the City of Battle Creek's computer system. The City dropped the
investigation after ORBZ announced it would end operations.  However,
simultaneously or before the City's announcement, ORBZ operator Ian
Gulliver registered DSBL.ORG with a Brazilian address. Quite obviously, he
had no intention of halting operations, but merely to disguise their
jurisdiction.

[2] Even though Kevin Mitnick was on the FBI's most wanted list, the FBI
was unable to track him down. Only after one of his victims became
involved, was Mitnick finally located and arrested.





From owner-ietf@ietf.org  Mon May 26 14:32:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20435
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 14:32:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KMTv-0001U0-EE
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 14:13:59 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KMDu-0000ot-0Z
	for ietf@asgard.ietf.org; Mon, 26 May 2003 13:57:26 -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 NAA19710
	for <ietf@ietf.org>; Mon, 26 May 2003 13:57:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KMCO-0000VL-00
	for ietf@ietf.org; Mon, 26 May 2003 13:55:52 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KMCN-0000V4-00
	for ietf@ietf.org; Mon, 26 May 2003 13:55:51 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id NAA16005;
	Mon, 26 May 2003 13:53:58 -0400
Date: Mon, 26 May 2003 13:55:00 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: ietf@ietf.org, <watha@monitortan.com>, <phil@whirlycott.com>
Subject: Re: spam (fwd) (edit error on previous)
Message-ID: <Pine.LNX.4.44.0305261351380.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Oops editing problems. Please refer to this version instead.



On Sat, 24 May 2003, Bill Cunningham wrote:

> http://story.news.yahoo.com/news?tmpl=story&u=/nm/20030524/wr_nm/tech_spam_d
> c_3
>
>     Is this what we want? The legal system taking over something that should
> be done by IETF. This new legislation isn't supposed to stop e-mail
> marketing, but stop deception. Will it work? :-s

There are 3 types of email that we generally call spam:

Type 1: Bonafide Messaging with a real Commercial or non-profit(ie
political) purpose.  This includes people selling contraband (eg drugs)
illegally, so long as they intend to deliver the illegal goods.

Type 2: Bonafide fraudulent activity. Someone is really trying to get your
money, but has no intentions of honoring their obligations to the purchase
contract.  This includes bonafide attempts at identify theft.

Type 3: Annoyance activity. This has no bonafide intention of getting
money or even personal information, even though at a casual glance it may
appear so.  Type 3 is broken into 2 subtypes:

Type 3A is a relatively harmless disgruntled person, who is not terribly
sophisticated in their abuse, or in hiding their tracks. This type can be
handled by warnings or account termination. Besides spam, this type is
also involved in small DOS attacks and other unsophisticated abuse.

Type 3B is a career criminal using viruses and rooted machines to conduct
annoyance, which is frequently just another type of DOS attack, but
targeted perhaps at an email address, or perhaps at a domain. This type of
attacker is already a career criminal, having broken into many, often
hundreds of computers, illegally. This type cannot be dealt with
effectively by ISPs, because they are reasonable adept at hiding their
tracks. Usually, the ISP only detects the infected computer, but does not
identify or catch the cracker.



Of these types of spam, Type 1 and Type 2 can be dealt with by law, and
through the actions of the FTC and other regulatory agencies. Once
something has been determined to be contraband, then the appropriate
enforcement agency is called in.  Type 3A can be handled by the ISP or
their employer. Type 3B is much more difficult to handle.

What is unclear is how much of the total spam is due to each of these
types.  A lot of the spam that I recieve, and I have kept all this for
some time now, appears to be from type 3B. It is possible that my previous
conflicts with radical anti-spammers may affect the type and proportion of
spam that I get.  My testing and logging of a large block of IP address
space over a period of years, has indicated that much abuse is supported
and promoted by certain open relay blacklists which scan for, and then
advertise open relays and open proxies to abuse.  Relays scanned by such
organizations have shown up on commercial sites selling this information.
such as helllabs.com.ua. The question of whether this activity is merely
exploited or done with active participation seems to be prejudicially
answered by the fact that the "blacklists" advertise input addresses even
though these have no utility to "normal" users of the blacklist.  This
type of abuse (Type 3B) is often done with their ISPs ignoring both their
illegal scanning, and their solicitation of abuse, false advertising,and
other issuses. It is becoming more common for such activities to try to
operately completely anonymously, or to use false out-of-country addresses
to avoid prosecution[1].  It is unclear how much this type of abuse
contributes to the total spam volume.

I note that helllabs.com.ua makes false and misleading claims that relays
and proxies are free.  The anonymity claimed by a customer's product
(www.ghostsender.com) is also false.  And of course, if the spam is of
Type 1 or Type 2, there is no anonymity at all.  Frauds (Type 2) that
obtain money are easy to track via mail fraud or wire fraud.  Only abuse
of Type 3 is hard to track, and requires law enforcement powers to obtain
the required information.

Legislation of the type we have seen is not going to any affect on Type
3B, as this type is already committing federal felonies, and the
equivalent in many countries.  But we don't need additional legislation
for this activity since it is already a federal felony with a 5 year jail
term.  The problem is catching the culprit.  This is partly an issue of
law enforcement interest in catching these "harmless" criminals.

Whether the legislation has any affect on total spam will depend on the
proportion of the various types of spam.


With that in mind, we can consider what the IETF can do: The IETF can
specify protocols. But what protocols can be specified to reduce or
eliminate spam?

Dr. Claude Shannon, one of the founders of the science of Information
Theory, proved that it is impossible to prove the non-existance of a
covert channel. In terms of spam, this means that it is impossible to
construct a protocol that cannot be abused, since one cannot prove that it
is impossible (the channel can't exist) to send abuse (a covert channel).
No protocol can ever be constructed that is spam-free.  Radical
anti-spammers often try to couch their arguments as though the spammers
are "outsiders" who have been let in. This isn't true. All abusers are the
customer of some ISP, somewhere. There are no outsiders.  The spammers are
in fact authorized users of some ISP that are authorized to send email.
They remain authorized to send email until they lose service with that
ISP.  Once this is understood, it is completely obvious even without the
formality of Shannon's theorem that protocols such as SMTP AUTH will have
no effect whatsoever.

So IETF efforts in this area are limited to finding means of identifying
the abuser, once the abuser has been detected. There is also the technical
task of detecting abuse.


The adeptness of Type 3B at hiding is not due to any technical flaw, but
due to crossing organizational boundaries. They use a proxy at one ISP to
abuse another ISP. The first ISP can identify the abuser, but often won't,
unless there is a request from Law Enforcement.  Once law enforcement
becomes involved to make the appropriate requests of different ISPs, it
has not been a technically difficult matter to track down abusers. Though
the technical know-how seems to elude the Law Enforcement Authorities
(e.g. Kevin Mitnick) until a technically knowledgeable person becomes
involved (Shimomura)[2]. There are many examples of persons who have been
arrested for using the internet to make bomb threats, as well as persons
who have released particularly dangerous viruses, and persons who have
cracked computers belonging to financial institutions.  Once there is a
law enforcement interest in finding the identity of the people involved,
there seems to be little technical obstacle other than technical
competence to finding the people. So I think there is little to be done
technically so far as identification goes.

The issue of detecting abuse was the focus of the MIT anti-spam
conference.  There are many paths presently being pursued: Blacklists,
header analysis, and various kinds of content analysis.  I think the
general consensus was that content analysis offers the most promising
means of detecting and blocking abuse.  I think it is too early to tell
how protocols can be helpful in this area, or if new protocols are
necessary. One scheme, used by MSN, gives the user a button to submit a
message as spam. Their system then tracks the number of complaints
involving characteristics of the message, and blocks messages accordingly,
and on per-user control. Of course, this requires no change to any
protocols, just to applications.

		--Dean


[1] SPEWS has attemtped to avoid prosecution and legal responsibility by
remaining completely anonymous. ORBZ.ORG was criminally investigated for
crashing the City of Battle Creek's computer system. The City dropped the
investigation after ORBZ announced it would end operations.  However,
simultaneously or before the City's announcement, ORBZ operator Ian
Gulliver registered DSBL.ORG with a Brazilian address. Quite obviously, he
had no intention of halting operations, but merely to disguise their
jurisdiction.

[2] Even though Kevin Mitnick was on the FBI's most wanted list, the FBI
was unable to track him down. Only after one of his victims became
involved, was Mitnick finally located and arrested.






From owner-ietf@ietf.org  Mon May 26 14:37:48 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20685
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 14:37:48 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KMio-0001ku-OH
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 14:29:22 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KMXg-0001a7-OA
	for ietf@asgard.ietf.org; Mon, 26 May 2003 14:17:52 -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 OAA20077
	for <ietf@ietf.org>; Mon, 26 May 2003 14:17:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KMWA-0000dm-00
	for ietf@ietf.org; Mon, 26 May 2003 14:16:18 -0400
Received: from tomts14-srv.bellnexxia.net ([209.226.175.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KMW9-0000dj-00
	for ietf@ietf.org; Mon, 26 May 2003 14:16:17 -0400
Received: from yahoo.com ([65.93.187.190]) by tomts14-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030526181739.FRCU14433.tomts14-srv.bellnexxia.net@yahoo.com>;
          Mon, 26 May 2003 14:17:39 -0400
Date: Mon, 26 May 2003 14:17:40 -0400
Subject: Re: spam
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: IETF Discussion <ietf@ietf.org>
To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <Pine.GSO.4.50.0305261357040.28832-100000@argos.ee.surrey.ac.uk>
Message-Id: <5602BC2A-8FA6-11D7-ADA9-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Monday, May 26, 2003, at 08:58  AM, Lloyd Wood wrote:

> On Sun, 25 May 2003, S Woodside wrote:
>
>> Good law could work to curtail spam. Spammers do it because it's
>> profitable. Remove the profit, fine the dickens out of the worst
>> transgressors, and the cost/benefit ratio will sink. Spamming isn't
>> like hacking, there is always a way to trace back to the person who is
>> paying for the spam because they must be able to sell their product.
>> Since you can identify the individuals responsible, you can hold them
>> accountable with the right laws in place.
>
> and this has worked so well with the War on Drugs.

The internet is not the street. Someone is selling a product. In order 
to sell a product you must be able to reach them. If you can reach 
them, you can find a way to deal with them legally.

simon




From owner-ietf@ietf.org  Mon May 26 14:43:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20800
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 14:43:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KMip-0001lB-O0
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 14:29:23 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KMaa-0001cA-CF
	for ietf@asgard.ietf.org; Mon, 26 May 2003 14:20:52 -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 OAA20176
	for <ietf@ietf.org>; Mon, 26 May 2003 14:20:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KMZ4-0000f9-00
	for ietf@ietf.org; Mon, 26 May 2003 14:19:18 -0400
Received: from 75.5.33.65.cfl.rr.com ([65.33.5.75] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KMZ3-0000f6-00
	for ietf@ietf.org; Mon, 26 May 2003 14:19:17 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19K2ZS-0005Zu-00; Sun, 25 May 2003 16:58:22 -0400
Date: Sun, 25 May 2003 16:58:17 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Dean Anderson <dean@av8.com>
cc: Bill Cunningham <billc44@citynet.net>, <ietf@ietf.org>,
        <watha@monitortan.com>, <phil@whirlycott.com>
Subject: Re: spam
In-Reply-To: <Pine.LNX.4.44.0305261205180.3699-100000@commander.av8.net>
Message-ID: <Pine.LNX.4.44.0305251656040.10631-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Dean,

>
> [1] SPEWS has attemtped to avoid prosecution and legal responsibility by
> remaining completely anonymous. ORBZ.ORG was criminally investigated for
> crashing the City of Battle Creek's computer system. The City dropped the
> investigation after ORBZ announced it would end operations.  However,
> simultaneously or before the City's announcement, ORBZ operator Ian
> Gulliver registered DSBL.ORG with a Brazilian address. Quite obviously, he
> had no intention of halting operations, but merely to disguise their
> jurisdiction.
>

sounds like ORBZ 1 Battle Creeek 0


> [2] Even though Kevin Mitnick was on the FBI's most wanted list, the FBI
> was unable to track him down. Only after one of his victims became
> involved, was Mitnick finally located and arrested.
>

Kevin gets locked away for years without even being CHARGED, and suddenly
he has victims?  He was the victim.

scott


>
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81




From owner-ietf@ietf.org  Mon May 26 14:55:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21104
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 14:55:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KMmD-0001pT-TF
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 14:32:53 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KMeb-0001dE-Qb
	for ietf@asgard.ietf.org; Mon, 26 May 2003 14:25:01 -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 OAA20234
	for <ietf@ietf.org>; Mon, 26 May 2003 14:25:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KMd5-0000gQ-00
	for ietf@ietf.org; Mon, 26 May 2003 14:23:27 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KMd5-0000gN-00
	for ietf@ietf.org; Mon, 26 May 2003 14:23:27 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2/8.11.2) id h4QIOjo25236;
	Mon, 26 May 2003 11:24:45 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200305261824.h4QIOjo25236@boreas.isi.edu>
Subject: Re: spam
In-Reply-To: <Pine.LNX.4.44.0305261205180.3699-100000@commander.av8.net> from Dean Anderson at "May 26, 3 01:40:07 pm"
To: dean@av8.com (Dean Anderson)
Date: Mon, 26 May 2003 11:24:45 -0700 (PDT)
Cc: billc44@citynet.net, ietf@ietf.org, watha@monitortan.com,
        phil@whirlycott.com
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

% There are 3 types of email that we generally call spam:

	who are "we"?

 type 4: harvesting/collecting "working" email addresses to be re-sold.


--bill
Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).



From owner-ietf@ietf.org  Mon May 26 15:10:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22205
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 15:10:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KN6Y-0003FQ-7N
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 14:53:54 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KMpR-0002B6-Um
	for ietf@asgard.ietf.org; Mon, 26 May 2003 14:36:13 -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 OAA20616
	for <ietf@ietf.org>; Mon, 26 May 2003 14:36:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KMnw-0000m9-00
	for ietf@ietf.org; Mon, 26 May 2003 14:34:40 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KMnv-0000m6-00
	for ietf@ietf.org; Mon, 26 May 2003 14:34:39 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207719; Mon, 26 May 2003 13:35:39 -0500
Message-ID: <3ED25E99.80007@ehsco.com>
Date: Mon, 26 May 2003 13:36:09 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: ietf@ietf.org
Subject: Re: spam
References: <Pine.LNX.4.44.0305261205180.3699-100000@commander.av8.net>
In-Reply-To: <Pine.LNX.4.44.0305261205180.3699-100000@commander.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/26/2003 12:40 PM Dean Anderson wrote:

<taxonomy and observations snipped>

> The issue of detecting abuse was the focus of the MIT anti-spam 
> conference.  There are many paths presently being pursued: Blacklists, 
> header analysis, and various kinds of content analysis.  I think the 
> general consensus was that content analysis offers the most promising 
> means of detecting and blocking abuse.

The problem is that this defines defeat as victory.

There is also existent proof that filtering is only "mostly" successful at
even its limited role. There are plenty of problems with false positives,
delayed positives, and so forth, which cumulative conspire to make this
approach less than functional as anything but a stop-gap measure. In that
regard, filtering is analogous to defining ~delayed defeat as victory.

What would victory actually look like? To me, it would be keeping the crap
off my network in the first place. Forcing people to engage in full-time
warfare with the ethically bankrupt is not a victory. Telling people to
give up and take it is not a victory.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Mon May 26 15:21:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23035
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 15:21:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KNNN-0002EE-59
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 15:11:17 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KNIM-0000AD-Nb
	for ietf@asgard.ietf.org; Mon, 26 May 2003 15:06:06 -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 PAA21696
	for <ietf@ietf.org>; Mon, 26 May 2003 15:06:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KNGq-00011w-00
	for ietf@ietf.org; Mon, 26 May 2003 15:04:32 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KNGq-00011t-00
	for ietf@ietf.org; Mon, 26 May 2003 15:04:32 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h4QJ63tU025427;
	Mon, 26 May 2003 15:06:03 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h4QJ63W7025426;
	Mon, 26 May 2003 15:06:03 -0400
Date: Mon, 26 May 2003 15:06:03 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200305261906.h4QJ63W7025426@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: spam
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: Paul Vixie <vixie@vix.com>

    > the IETF debated whether it should do anything about spam and chose
    > "no"

I used to think this was the right thing, but I've changed my mind.

The reason is that I think all these legal measures are a complete waste of
time. The spammers who are determined to send you stuff will simply move
overseas to jurisdictions which don't care about spam (those that aren't
already there, that is - I get a lot of spam in Asian alphabets I can't even
read). All these US laws are interesting, but ultimately a waste of time.

And if you think that there are going to be international agreements to stop
spam, you need only to look at the difficulty law enforcement agencies are
having getting international cooperation to act against outright fraud
(credit card theft, identity theft, etc) coming from some jurisdictions. The
Washington Post had a good series of stories about this recently.


The *only* thing that's going to stop spam is charging for email. Everything
else is a waste of time, because you're going to run into impossible
arguments trying to define what's spam, and what's legitimate bulk email
(q.v. the recent message about IETF-Announce email).

Needless to say, charging for email means changing the underlying protocols.
That's us. It's not going to be simple (we need an underlying micro-payments
system), and it's going to take a lot of attention to detail (q.v.
IETF-Announce again), but I think it's the only real cure.

	Noel



From owner-ietf@ietf.org  Mon May 26 15:30:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23506
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 15:30:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KNYe-0004fo-3P
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 15:22:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KNOV-0002Xq-Rl
	for ietf@asgard.ietf.org; Mon, 26 May 2003 15:12:27 -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 PAA22507
	for <ietf@ietf.org>; Mon, 26 May 2003 15:12:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KNMz-000170-00
	for ietf@ietf.org; Mon, 26 May 2003 15:10:53 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KNMz-00016l-00
	for ietf@ietf.org; Mon, 26 May 2003 15:10:53 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id PAA09817;
	Mon, 26 May 2003 15:06:41 -0400
Date: Mon, 26 May 2003 15:07:42 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Valdis.Kletnieks@vt.edu
cc: Anthony Atkielski <anthony@atkielski.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: spam 
In-Reply-To: <200305261609.h4QG9Ka7012963@turing-police.cc.vt.edu>
Message-ID: <Pine.LNX.4.44.0305261433180.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Mon, 26 May 2003 Valdis.Kletnieks@vt.edu wrote:

> On Mon, 26 May 2003 08:56:43 +0200, Anthony Atkielski <anthony@atkielski.com>  said:
>
> > Even at a hundred dollars an hour, the cost of deleting spam each day with
> > the delete key (and even at the current rate of hundreds of spam per day) is
> > only $2-$3 ... several times cheaper than the daily cost of visiting a
> > restroom.
>
> Note that visiting the restroom gets a LOT more expensive if you have to
> remodel the restroom and add more stalls because everybody is doing it all
> the time.
>
> Similarly, if your *LAST* mail server was a Sun E6500 and 4 Mirapoint boxes and
> various other small things like a load balancer, it's expensive to upgrade to a
> new box just so all your users can spend money hitting delete...  Also,
> remember that although 20 pieces of spam a day is only a 5% increase in
> in my mail volume, I clear my stuff off the server on a regular basis.
> For the user who gets 5-6 pieces of mail a day and only checks once a week,
> that's a *big* jump in how much disk space they consume.

This is a pretty bogus argument. One that really annoys the radical
anti-spammers to debunk, but that can't be avoided.  Its sort of a sacred
cow with them, but it is a trivial and weak claim.  It was made in 1998,
and trounced by the DMA then. Everything (disks, network, computers) is
cheaper now. What wasn't a convincing argument then is even less so now.

Consider a small ISP that handles 400,000 messages per day, with an
average message size of 5000 bytes. My real average message size is
smaller, but 5000 makes the math easier. Lets do the math:

400,000 * 5000 = 2,000,000,000 (2 gig per day, if you were going to save
it all).

I notice that you can get 250Gig disks now for under $400. 2 Disks make 1
500Meg volume.  Apply a raid controller with 2 more disks, and we are
talking about $2000 in disks. ($2000 is kind of inflated really, but some
ISPs like Av8 consider mail to be important).

On that 500Gig volume, we can store 500/2 days worth of email.  My
calculator says that we can _keep_ all email back for 250 days. About 8
months. And it only cost us $2000 in disk. And thats if no one deleted
anything.  Clearly, most email isn't stored that long.

People talk about Sun 6500s, and users who only read mail once per week,
but they are still able to offer mailboxes for $1 or $2/mo per user, and
aren't losing money. No one is complaining about the high cost of email
boxes.

There is no cost to spam. It is purely an annoyance factor.

As far as time spent hitting delete, I went through 409 spams today, and a
number of non-spam emails (hundreds, including IETF mail). It took me less
than 15 minutes to hand filter all my mail using only pine. And thats not
a daily total, thats after not reading email over the weekend.  Using a
spam filter would make this almost nothing, as well.

If you want to count cost of advertising on your time, then you have to
count the value of the time you spend in front of the tv watching ads,
listening to them on the radio, and the time in the movie theater watching
ads, too. The cost of accidents caused by people reading billboards. Spam
still comes out to be trivial by comparison.

As for the volume of spam affecting network utilization, this is also a
non-expense. All email, non-spam included, makes up a dwindling proportion
of network traffic, in comparision to gifs, and streaming media, and other
emerging high bandwidth applications.  Network-wise, spam takes up almost
nothing. And like disk costs, network costs, and proportion of bandwidth
consumed is dwindling.

Lets focus on real problems, not sacred cows. Promoting bogus claims
doesn't solve anything, but simply discredits those making them. This
isn't worthy of the IETF.

		--Dean




From owner-ietf@ietf.org  Mon May 26 15:46:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23923
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 15:46:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KNYe-0004fw-DL
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 15:22:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KNPN-0002pE-7A
	for ietf@asgard.ietf.org; Mon, 26 May 2003 15:13:21 -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 PAA22602
	for <ietf@ietf.org>; Mon, 26 May 2003 15:13:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KNNr-00017j-00
	for ietf@ietf.org; Mon, 26 May 2003 15:11:47 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KNNq-000174-00
	for ietf@ietf.org; Mon, 26 May 2003 15:11:46 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id PAA09821;
	Mon, 26 May 2003 15:07:56 -0400
Date: Mon, 26 May 2003 15:08:58 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Bill Manning <bmanning@ISI.EDU>
cc: billc44@citynet.net, <ietf@ietf.org>, <watha@monitortan.com>,
        <phil@whirlycott.com>
Subject: Re: spam
In-Reply-To: <200305261824.h4QIOjo25236@boreas.isi.edu>
Message-ID: <Pine.LNX.4.44.0305261508030.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Harvesting addresses isn't an email message. Its spam-related activity,
but it isn't spam.

		--Dean

On Mon, 26 May 2003, Bill Manning wrote:

> % There are 3 types of email that we generally call spam:
>
> 	who are "we"?
>
>  type 4: harvesting/collecting "working" email addresses to be re-sold.
>
>
> --bill
> Opinions expressed may not even be mine by the time you read them, and
> certainly don't reflect those of any other entity (legal or otherwise).
>




From owner-ietf@ietf.org  Mon May 26 15:47:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23958
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 15:47:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KNYe-0004gV-Ms
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 15:22:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KNU9-0003us-B3
	for ietf@asgard.ietf.org; Mon, 26 May 2003 15:18:17 -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 PAA22982
	for <ietf@ietf.org>; Mon, 26 May 2003 15:18:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KNSd-0001BM-00
	for ietf@ietf.org; Mon, 26 May 2003 15:16:43 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KNSc-0001BJ-00
	for ietf@ietf.org; Mon, 26 May 2003 15:16:42 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2/8.11.2) id h4QJI1c26858;
	Mon, 26 May 2003 12:18:01 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200305261918.h4QJI1c26858@boreas.isi.edu>
Subject: Re: spam
In-Reply-To: <Pine.LNX.4.44.0305261508030.3699-100000@commander.av8.net> from Dean Anderson at "May 26, 3 03:08:58 pm"
To: dean@av8.com (Dean Anderson)
Date: Mon, 26 May 2003 12:18:01 -0700 (PDT)
Cc: bmanning@ISI.EDU, billc44@citynet.net, ietf@ietf.org, watha@monitortan.com,
        phil@whirlycott.com
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

 sending crap to see if the email address is valid is spam.  it is
 unwanted, unsolicited, consumes resources I pay for w/o my consent.
 the perp could care less what they send, as long as my local mail 
 system indicates delivery is successful.  they then "harvest" the
 email address. if they do it twice and get an affirmative response
 that mail is/would be successfully delivered, ... double opt-in!!
 
 thats one thing -we- generally call spam.


% Harvesting addresses isn't an email message. Its spam-related activity,
% but it isn't spam.
% 
% 		--Dean
% 
% On Mon, 26 May 2003, Bill Manning wrote:
% 
% > % There are 3 types of email that we generally call spam:
% >
% > 	who are "we"?
% >
% >  type 4: harvesting/collecting "working" email addresses to be re-sold.
% >
% >
% > --bill
% > Opinions expressed may not even be mine by the time you read them, and
% > certainly don't reflect those of any other entity (legal or otherwise).
% >
% 


-- 
--bill

Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).




From owner-ietf@ietf.org  Mon May 26 15:48:49 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24205
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 15:48:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KNYe-0004gn-UG
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 15:22:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KNUu-0003vL-M9
	for ietf@asgard.ietf.org; Mon, 26 May 2003 15:19:04 -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 PAA22990
	for <ietf@ietf.org>; Mon, 26 May 2003 15:19:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KNTO-0001Bb-00
	for ietf@ietf.org; Mon, 26 May 2003 15:17:30 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KNTN-0001BY-00
	for ietf@ietf.org; Mon, 26 May 2003 15:17:29 -0400
Received: (from braden@localhost)
	by boreas.isi.edu (8.11.6p2/8.11.2) id h4QJIxs27507;
	Mon, 26 May 2003 12:18:59 -0700 (PDT)
Date: Mon, 26 May 2003 12:18:59 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Message-Id: <200305261918.h4QJIxs27507@boreas.isi.edu>
To: billc44@citynet.net, dean@av8.com
Subject: Re: spam
Cc: ietf@ietf.org, twatha@monitortan.com
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


  *> 
  *> Type 1: Bonafide Messaging with a real Commercial or non-profit(ie
  *> political) purpose.  This includes people selling contraband (eg drugs)
  *> illegally, so long as they intend to deliver the illegal goods.
  *> 
  *> 
  *> 
  *> 
  *> Of these types of spam, Type 1 and Type 2 can be dealt with by law, and
  *> through the actions of the FTC and other regulatory agencies.

So, what happens when the FTC, which is today very business-friendly,
decides to place no restriction at all on "real Commercial" spam?
Given the current politics in Washington, that seems like a likely
scenario.  Yet, this spam is the most hard-to-filter, and it may soon
become the dominant component of spam.  I for one don't want to see my
email box filled with junk as my postal mailbox is.

Bob Braden



From owner-ietf@ietf.org  Mon May 26 15:50:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24327
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 15:50:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KNYf-0004i3-Fk
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 15:22:57 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KNYE-0004Us-Ql
	for ietf@asgard.ietf.org; Mon, 26 May 2003 15:22:30 -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 PAA23109
	for <ietf@ietf.org>; Mon, 26 May 2003 15:22:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KNWi-0001Dc-00
	for ietf@ietf.org; Mon, 26 May 2003 15:20:56 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KNWi-0001CG-00
	for ietf@ietf.org; Mon, 26 May 2003 15:20:56 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id PAA27007;
	Mon, 26 May 2003 15:19:53 -0400
Date: Mon, 26 May 2003 15:20:55 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: "Eric A. Hall" <ehall@ehsco.com>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <3ED25E99.80007@ehsco.com>
Message-ID: <Pine.LNX.4.44.0305261511340.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Social problems are not that simple. They are not solved by confrontation.
Because there is no confrontation, there is no victory to be had.

But a confrontation (physical or legal) without regard to rights and
reason will only go badly for those who pursue it.  Some anti-spammers
might be happy to find a spammer in a back alley, and beat them.  But they
would find themselves up on assault charges. They would "lose".  Spammers
have rights, too.  Assuming they do not is a falacy. However, this was the
falacy that caused defeat in 1998, (as I predicted in 1997). People
assumed they could shout down anyone who disputed the costs of spam or who
suggested that they had to be reasonable with respect to spammers rights,
and so they used that as their "cause". The DMA could not be shouted down,
and were able to present their case, and debunk the anti-spammers. Who
"lost".

		--Dean

On Mon, 26 May 2003, Eric A. Hall wrote:

>
> on 5/26/2003 12:40 PM Dean Anderson wrote:
>
> <taxonomy and observations snipped>
>
> > The issue of detecting abuse was the focus of the MIT anti-spam
> > conference.  There are many paths presently being pursued: Blacklists,
> > header analysis, and various kinds of content analysis.  I think the
> > general consensus was that content analysis offers the most promising
> > means of detecting and blocking abuse.
>
> The problem is that this defines defeat as victory.
>
> There is also existent proof that filtering is only "mostly" successful at
> even its limited role. There are plenty of problems with false positives,
> delayed positives, and so forth, which cumulative conspire to make this
> approach less than functional as anything but a stop-gap measure. In that
> regard, filtering is analogous to defining ~delayed defeat as victory.
>
> What would victory actually look like? To me, it would be keeping the crap
> off my network in the first place. Forcing people to engage in full-time
> warfare with the ethically bankrupt is not a victory. Telling people to
> give up and take it is not a victory.
>
> --
> Eric A. Hall                                        http://www.ehsco.com/
> Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/
>
>




From owner-ietf@ietf.org  Mon May 26 16:03:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24718
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 16:03:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KO2n-0006vq-5u
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 15:54:05 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KNcb-0004jv-8r
	for ietf@asgard.ietf.org; Mon, 26 May 2003 15:27:01 -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 PAA23341
	for <ietf@ietf.org>; Mon, 26 May 2003 15:26:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KNb5-0001Hi-00
	for ietf@ietf.org; Mon, 26 May 2003 15:25:27 -0400
Received: from burp.tkv.asdf.org ([212.16.99.49] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KNb4-0001Hf-00
	for ietf@ietf.org; Mon, 26 May 2003 15:25:26 -0400
Received: from burp.tkv.asdf.org (msa@localhost [127.0.0.1])
	by burp.tkv.asdf.org (8.12.3/8.12.3/Debian-6.3) with ESMTP id h4QJQmhW001992;
	Mon, 26 May 2003 22:26:48 +0300
Received: (from msa@localhost)
	by burp.tkv.asdf.org (8.12.3/8.12.3/Debian-6.3) id h4QJQmQC001988;
	Mon, 26 May 2003 22:26:48 +0300
Date: Mon, 26 May 2003 22:26:48 +0300
Message-Id: <200305261926.h4QJQmQC001988@burp.tkv.asdf.org>
From: Markku Savela <msa@burp.tkv.asdf.org>
To: ehall@ehsco.com
CC: ietf@ietf.org
In-reply-to: <3ED25E99.80007@ehsco.com> (ehall@ehsco.com)
Subject: Re: spam
References: <Pine.LNX.4.44.0305261205180.3699-100000@commander.av8.net> <3ED25E99.80007@ehsco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk


> What would victory actually look like? To me, it would be keeping the crap
> off my network in the first place. Forcing people to engage in full-time
> warfare with the ethically bankrupt is not a victory.

The best techical solution that has been proposed seems to be the
"tarpit" solution: detect spam on the fly and slow down the reception
to trickle as "spamminess" grows. The great feature of this is, that
it actually would keep spam "off my network" by stopping the flow.

I would think technically, one would run a frontend tarpit pipeline on
the standard SMTP port as follows

   port 25
   --------> TARPIT ----> real SMTP on other port or host
              ^
              |
            SpamRules

TARPIT would listen incoming connections, establish another connection
to real SMTP server. It would examine the data on fly and slow the
incoming reception when the spam index grows. Mail would not be
rejected, just slowed, as "spammines index" grows.

Of course, this solution only works if you are receiving your mail
directly. If you receive your mail via mail forwarder, this won't help
-- the mail forwarder must be using it.



From owner-ietf@ietf.org  Mon May 26 16:05:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24870
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 16:05:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KO7m-0007DJ-PI
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 15:59:14 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KNzp-0006qu-Q5
	for ietf@asgard.ietf.org; Mon, 26 May 2003 15:51:01 -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 PAA24388
	for <ietf@ietf.org>; Mon, 26 May 2003 15:50:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KNyJ-0001ZK-00
	for ietf@ietf.org; Mon, 26 May 2003 15:49:27 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KNyJ-0001YN-00
	for ietf@ietf.org; Mon, 26 May 2003 15:49:27 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id E627E1396D; Mon, 26 May 2003 19:50:28 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: spam
References: <200305261906.h4QJ63W7025426@ginger.lcs.mit.edu>
From: Paul Vixie <vixie@vix.com>
Date: 26 May 2003 19:50:28 +0000
In-Reply-To: <200305261906.h4QJ63W7025426@ginger.lcs.mit.edu>
Message-ID: <g3ptm5v663.fsf@sa.vix.com>
Lines: 30
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

> > the IETF debated whether it should do anything about spam and chose "no"
> 
> I used to think this was the right thing, but I've changed my mind.
> 
> The reason is [...]
> ...
> The *only* thing that's going to stop spam is [...]

i elipsed the specifics because at this level it doesn't matter.  what the
ietf has to decide is whether there is protocol work to be done in this area.

i believe there is.  smtp's design assumptions don't apply to a mixed use
environment where the user base is larger than a few hundred researchers
who can be depended upon not to overgraze the commons.

charging for email is one oft-heard proposal.  my own preference is for a
trusted-introducer model similar in concept to pgp but more market-ready
(this has been called the "gated community" approach.)

but until iab/iesg hear a concrete wg proposal, this isn't protocol work,
and the ietf will have no official position on it one way or the other.

as has been shown several times, this isn't really approachable as a direct
proprietary/commercial effort, even though there's a lot of money to be
made as an agent in an open standards approach like my trusted-introducer
idea.

the ietf leadership seems overcommitted wrt a new effort of this magnitude.
-- 
Paul Vixie



From owner-ietf@ietf.org  Mon May 26 16:11:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25108
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 16:11:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KOBd-0007LE-GL
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 16:03:13 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KO6C-0006zV-CD
	for ietf@asgard.ietf.org; Mon, 26 May 2003 15:57:36 -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 PAA24564
	for <ietf@ietf.org>; Mon, 26 May 2003 15:57:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KO4g-0001cU-00
	for ietf@ietf.org; Mon, 26 May 2003 15:56:02 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KO4f-0001cQ-00
	for ietf@ietf.org; Mon, 26 May 2003 15:56:01 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id PAA22208;
	Mon, 26 May 2003 15:53:31 -0400
Date: Mon, 26 May 2003 15:54:22 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: shogunx <shogunx@sleekfreak.ath.cx>
cc: Bill Cunningham <billc44@citynet.net>, <ietf@ietf.org>,
        <watha@monitortan.com>, <phil@whirlycott.com>
Subject: Re: spam
In-Reply-To: <Pine.LNX.4.44.0305251656040.10631-100000@sleekfreak.ath.cx>
Message-ID: <Pine.LNX.4.44.0305261533010.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Sun, 25 May 2003, shogunx wrote:

> Dean,
>
> >
> > [1] SPEWS has attemtped to avoid prosecution and legal responsibility by
> > remaining completely anonymous. ORBZ.ORG was criminally investigated for
> > crashing the City of Battle Creek's computer system. The City dropped the
> > investigation after ORBZ announced it would end operations.  However,
> > simultaneously or before the City's announcement, ORBZ operator Ian
> > Gulliver registered DSBL.ORG with a Brazilian address. Quite obviously, he
> > had no intention of halting operations, but merely to disguise their
> > jurisdiction.
> >
>
> sounds like ORBZ 1 Battle Creeek 0

ORBZ got away with a deception, yes.  Ian Gulliver is not the first
con-artist to talk his way out of a jam with the cops and won't be the
last.

> > [2] Even though Kevin Mitnick was on the FBI's most wanted list, the FBI
> > was unable to track him down. Only after one of his victims became
> > involved, was Mitnick finally located and arrested.
> >
>
> Kevin gets locked away for years without even being CHARGED, and suddenly
> he has victims?  He was the victim.

He was not locked away for any years without being charged. While he may
also have been victimized in some respects due the difficulty and
complexity of his trial, he was by no means innocent. He brought it all on
himself.  He was a self-described con-artist, and violated numerous civil
and criminal statutes. He had no regard to civil or criminal laws, and
therefore couldn't be allowed to roam about society unsupervised. He had
many victims, as he recently admitted at a talk I attended. What he did
was wrong in a big way. He has completely repudiated his earlier
activities.

Those who see Mitnick as representative of the hacker ethic don't really
understand the hacker ethic. Hackers are not dishonest.  Hackers share,
they do not steal.  Hackers ask politely, and invent for themselves what
they are refused.  Hackers do not coerce or extort anything.

		--Dean




From owner-ietf@ietf.org  Mon May 26 16:16:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23034
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 15:21:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KNNN-0002EX-Dd
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 15:11:17 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KNIn-0000HY-21
	for ietf@asgard.ietf.org; Mon, 26 May 2003 15:06:33 -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 PAA21745
	for <ietf@ietf.org>; Mon, 26 May 2003 15:06:31 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KNHH-000128-00
	for ietf@ietf.org; Mon, 26 May 2003 15:04:59 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KNHG-000125-00
	for ietf@ietf.org; Mon, 26 May 2003 15:04:58 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h4QJ6UbM003412;
	Mon, 26 May 2003 15:06:30 -0400
Message-Id: <200305261906.h4QJ6UbM003412@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Bill Manning <bmanning@ISI.EDU>
Cc: ietf@ietf.org
Subject: Re: spam 
In-Reply-To: Your message of "Mon, 26 May 2003 11:24:45 PDT."
             <200305261824.h4QIOjo25236@boreas.isi.edu> 
References: <200305261824.h4QIOjo25236@boreas.isi.edu>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1900543639P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 26 May 2003 15:06:29 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1900543639P
Content-Type: text/plain; charset=us-ascii

On Mon, 26 May 2003 11:24:45 PDT, Bill Manning said:

>  type 4: harvesting/collecting "working" email addresses to be re-sold.

Is that just "aiding and abetting", or are you saying that things like
"Uncertainty Principle Untenable" are just fronts for list-washing groups?

--==_Exmh_-1900543639P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+0mW1cC3lWbTT17ARAqjLAJ9QlE7lcXNRkE5Yh4W5IPu1ZO4GHgCfX0WF
QrNrLDghXWtC+AQA6Qu0ndg=
=JdC3
-----END PGP SIGNATURE-----

--==_Exmh_-1900543639P--



From owner-ietf@ietf.org  Mon May 26 16:25:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25607
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 16:25:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KOL1-0000B5-EO
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 16:12:55 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KOFb-000820-Q9
	for ietf@asgard.ietf.org; Mon, 26 May 2003 16:07:19 -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 QAA24982
	for <ietf@ietf.org>; Mon, 26 May 2003 16:07:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOE5-0001kZ-00
	for ietf@ietf.org; Mon, 26 May 2003 16:05:45 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOE4-0001kI-00
	for ietf@ietf.org; Mon, 26 May 2003 16:05:45 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 1A609ABA7; Mon, 26 May 2003 13:12:45 -0700 (PDT)
To: Dean Anderson <dean@av8.com>
Cc: Valdis.Kletnieks@vt.edu, Anthony Atkielski <anthony@atkielski.com>,
        IETF Discussion <ietf@ietf.org>
Subject: Re: spam
References: <Pine.LNX.4.44.0305261433180.3699-100000@commander.av8.net>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 26 May 2003 13:12:44 -0700
In-Reply-To: <Pine.LNX.4.44.0305261433180.3699-100000@commander.av8.net>
Message-ID: <kjisrxa2mb.fsf@romeo.rtfm.com>
Lines: 16
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Dean Anderson <dean@av8.com> writes:
> There is no cost to spam. It is purely an annoyance factor.
This strikes me as a pretty limited way to measure cost.

To the extent to which people would be willing to pay to not be
spammed, then spam is costing them happiness (an economist would say
utility). That cost is no less real than if it were using up their
disk space. To be concrete about it, consider the amount of money
being spent on spam-suppression. That's a direct cost imposed by spam.

-Ekr

-- 
[Eric Rescorla                                   ekr@rtfm.com]
           Web Log: http://www.rtfm.com/movabletype




From owner-ietf@ietf.org  Mon May 26 16:42:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26110
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 16:42:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KOZX-0000tS-7R
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 16:27:55 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KOMH-0000E6-0L
	for ietf@asgard.ietf.org; Mon, 26 May 2003 16:14:13 -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 QAA25302
	for <ietf@ietf.org>; Mon, 26 May 2003 16:14:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOKl-0001p5-00
	for ietf@ietf.org; Mon, 26 May 2003 16:12:39 -0400
Received: from ip166.usw12.rb1.bel.nwlink.com ([209.20.253.166] helo=ran.psg.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOKk-0001p2-00
	for ietf@ietf.org; Mon, 26 May 2003 16:12:38 -0400
Received: from localhost ([127.0.0.1] helo=ran.psg.com)
	by ran.psg.com with esmtp (Exim 4.20)
	id 19KOME-0004PL-8t; Mon, 26 May 2003 13:14:10 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Mon, 26 May 2003 13:14:09 -0700
To: Bob Braden <braden@ISI.EDU>
Cc: ietf@ietf.org
Subject: Re: spam
References: <200305261918.h4QJIxs27507@boreas.isi.edu>
Message-Id: <E19KOME-0004PL-8t@ran.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> So, what happens when the FTC, which is today very business-friendly,
> decides to place no restriction at all on "real Commercial" spam?

thank you for saying this.  i tried to make this point on nanog and
failed.

what you will have is american television and commercial radio.

randy




From owner-ietf@ietf.org  Mon May 26 16:47:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26450
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 16:47:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KOZX-0000u7-Jw
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 16:27:55 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KOTm-0000LJ-JC
	for ietf@asgard.ietf.org; Mon, 26 May 2003 16:21:58 -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 QAA25507
	for <ietf@ietf.org>; Mon, 26 May 2003 16:21:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOSG-0001sP-00
	for ietf@ietf.org; Mon, 26 May 2003 16:20:24 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOSG-0001sM-00
	for ietf@ietf.org; Mon, 26 May 2003 16:20:24 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207736; Mon, 26 May 2003 15:21:24 -0500
Message-ID: <3ED27762.4070004@ehsco.com>
Date: Mon, 26 May 2003 15:21:54 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Markku Savela <msa@burp.tkv.asdf.org>
CC: ietf@ietf.org
Subject: Re: spam
References: <Pine.LNX.4.44.0305261205180.3699-100000@commander.av8.net> <3ED25E99.80007@ehsco.com> <200305261926.h4QJQmQC001988@burp.tkv.asdf.org>
In-Reply-To: <200305261926.h4QJQmQC001988@burp.tkv.asdf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/26/2003 2:26 PM Markku Savela wrote:

> The best techical solution that has been proposed seems to be the
> "tarpit" solution: detect spam on the fly and slow down the reception
> to trickle as "spamminess" grows. The great feature of this is, that
> it actually would keep spam "off my network" by stopping the flow.

How so? As I have heard it used in the common sense, it allows delivery to
some and slows the delivery to others, but doesn't prevent any of it. Even
in those cases of cooperative tarpits that cooperate to consume socket
resources on the spamming host, some recipients still have to take the
pain before the cooperative nets can respond.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Mon May 26 16:55:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26736
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 16:55:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KOZX-0000uI-T9
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 16:27:55 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KOUg-0000RD-IX
	for ietf@asgard.ietf.org; Mon, 26 May 2003 16:22:54 -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 QAA25521
	for <ietf@ietf.org>; Mon, 26 May 2003 16:22:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOTA-0001sq-00
	for ietf@ietf.org; Mon, 26 May 2003 16:21:20 -0400
Received: from krusty-motorsports.com ([192.94.170.8] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOTA-0001sn-00
	for ietf@ietf.org; Mon, 26 May 2003 16:21:20 -0400
Received: from [24.194.112.77] (helo=skipper.averillpark.net)
	by krusty-motorsports.com with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.14)
	id 19KOUe-0005hd-Qn
	for ietf@ietf.org; Mon, 26 May 2003 20:22:52 +0000
Received: from rwelty by skipper.averillpark.net with local (Exim 4.14)
	id 19KOU5-0007Om-U4
	for ietf@ietf.org; Mon, 26 May 2003 16:22:17 -0400
Date: Mon, 26 May 2003 16:22:17 -0400 (EDT)
From: Richard Welty <rwelty@averillpark.net>
Subject: Re[2]: spam
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Disposition: INLINE
References: <200305261918.h4QJIxs27507@boreas.isi.edu>
In-Reply-To: <200305261918.h4QJIxs27507@boreas.isi.edu>
X-Mailer: Mahogany 0.64 'Sparc', compiled for Linux 2.4.9-13 i686
Message-Id: <E19KOU5-0007Om-U4@skipper.averillpark.net>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.
Sender: owner-ietf@ietf.org
Precedence: bulk


On Mon, 26 May 2003 12:18:59 -0700 (PDT) Bob Braden <braden@ISI.EDU> wrote:
> So, what happens when the FTC, which is today very business-friendly,
> decides to place no restriction at all on "real Commercial" spam?
> Given the current politics in Washington, that seems like a likely
> scenario.

i disagree.

from what i have heard from participants in the FTC "spam summit" (and
what i viewed in some of the recordings of sessions which were available
online briefly), it seems clear that the FTC has done the math and
understands the nature of the problem fairly well.

however, they are tightly constrained by their mandate from Congress. this
is where the real problem lies.

there are at least some legislators who are willing to write legislation
that refers to standards from recognized standards bodies (e.g., the IETF).
this is where the opportunity for the IETF to help lies -- to devise new
standards and protocols which won't necessarily stop spam, but which when
combined with legislation and properly funded enforcement bodies, can stop
or at least cut it down.

the international nature of the problem is undersood by at least some
legislators as well.  Senator Schumer (NY) is already on record as believing
that there will need to be international treaties as part of the solution
to the spam problem.

one of the things that has contributed to the evident lack of progress is
the argument about technical means vs legislative/enforcement means.
neither is really sufficient, it will take a combination of the two.

richard
--
Richard Welty                                         rwelty@averillpark.net
Averill Park Networking                                         518-573-7592
              Unix, Linux, IP Network Engineering, Security





From owner-ietf@ietf.org  Mon May 26 17:10:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27258
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 17:10:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KOyq-0002Rr-Vu
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 16:54:04 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KOZl-0000wl-Px
	for ietf@asgard.ietf.org; Mon, 26 May 2003 16:28:09 -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 QAA25739
	for <ietf@ietf.org>; Mon, 26 May 2003 16:28:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOYF-0001wy-00
	for ietf@ietf.org; Mon, 26 May 2003 16:26:35 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOYF-0001wv-00
	for ietf@ietf.org; Mon, 26 May 2003 16:26:35 -0400
Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1])
	by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id VAA29463
	for <ietf@ietf.org>; Mon, 26 May 2003 21:28:06 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by pigeon.ecs.soton.ac.uk (8.9.3p2/8.9.3) with ESMTP id VAA02680
	for <ietf@ietf.org>; Mon, 26 May 2003 21:28:06 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id h4QKS6S24871
	for ietf@ietf.org; Mon, 26 May 2003 21:28:06 +0100
Date: Mon, 26 May 2003 21:28:06 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Re: spam
Message-ID: <20030526202806.GA24806@login.ecs.soton.ac.uk>
References: <Pine.LNX.4.44.0305261205180.3699-100000@commander.av8.net> <3ED25E99.80007@ehsco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3ED25E99.80007@ehsco.com>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, May 26, 2003 at 01:36:09PM -0500, Eric A. Hall wrote:
> 
> There is also existent proof that filtering is only "mostly" successful at
> even its limited role. There are plenty of problems with false positives,
> delayed positives, and so forth, which cumulative conspire to make this
> approach less than functional as anything but a stop-gap measure. In that
> regard, filtering is analogous to defining ~delayed defeat as victory.

I find filtering quite productive.  I use a free Unix gateway system developed
here called MailScanner (www.mailscanner.info) which brings together many 
different anti-spam methods and does anti-virus.   Since Sugust 2002 it's 
filtered out 8,700 spams for me, and 570 virii, with only two false positives.
Sure, it misses a few, but 8,700 deletions would have taken me a while...

Tim



From owner-ietf@ietf.org  Mon May 26 17:14:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27544
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 17:14:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KOyr-0002TH-So
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 16:54:05 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KOfi-00011v-7I
	for ietf@asgard.ietf.org; Mon, 26 May 2003 16:34:18 -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 QAA25886
	for <ietf@ietf.org>; Mon, 26 May 2003 16:34:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOeC-0001yr-00
	for ietf@ietf.org; Mon, 26 May 2003 16:32:44 -0400
Received: from anchor-post-32.mail.demon.net ([194.217.242.90])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOeB-0001yo-00
	for ietf@ietf.org; Mon, 26 May 2003 16:32:43 -0400
Received: from soaring.demon.co.uk ([80.177.120.110])
	by anchor-post-32.mail.demon.net with esmtp (Exim 3.35 #1)
	id 19KOff-000Ddc-0W
	for ietf@ietf.org; Mon, 26 May 2003 21:34:15 +0100
Message-ID: <6DSBmjGUon0+EwXs@soaring.demon.co.uk>
Date: Mon, 26 May 2003 21:33:24 +0100
To: ietf@ietf.org
From: Andrew Shore <ietf@soaring.demon.co.uk>
Reply-To: Andrew Shore <ietf@soaring.demon.co.uk>
Subject: Re: spam
References: <200305261906.h4QJ63W7025426@ginger.lcs.mit.edu>
In-Reply-To: <200305261906.h4QJ63W7025426@ginger.lcs.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain;charset=us-ascii;format=flowed
User-Agent: Turnpike/6.02-S (<aCAGT1CKFCi8lsT3mwPhfD$m6j>)
Sender: owner-ietf@ietf.org
Precedence: bulk

J. Noel Chiappa wrote:

>The *only* thing that's going to stop spam is charging for email. Everything
>else is a waste of time, because you're going to run into impossible
>arguments trying to define what's spam, and what's legitimate bulk email
>(q.v. the recent message about IETF-Announce email).

     That's an interesting argument. I suspect I've missed a lot of the 
prior discussion, since I'm not sure how charging for email would work 
(Who charges? Who pays? Could it ever work in a free market? Aren't 
there legal implications?).

     It was your "only" that caught my attention, though. Being able to 
pick and choose my email addresses, I have had a reasonable amount of 
success using different email addresses for different stores and 
subscriptions: if an address begins to collect an unreasonable amount of 
spam, I stop using it. One "technical" solution that would discourage 
spam would be to add a key (a text string, for example) to the email 
header. The user gives out their email address with different keys to 
different groups of people; if a key attracts spam, all they have to do 
is stop accepting mail with that key. It would also make organising mail 
very easy. On the negative side, the extra complexity might prove 
challenging for some...


Andrew.
-- 
Andrew Shore.



From owner-ietf@ietf.org  Mon May 26 17:18:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27692
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 17:18:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KOys-0002Td-8O
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 16:54:06 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KOiv-00013G-Nx
	for ietf@asgard.ietf.org; Mon, 26 May 2003 16:37:37 -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 QAA25967
	for <ietf@ietf.org>; Mon, 26 May 2003 16:37:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOhP-00020H-00
	for ietf@ietf.org; Mon, 26 May 2003 16:36:03 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOhO-000208-00
	for ietf@ietf.org; Mon, 26 May 2003 16:36:02 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id QAA15382;
	Mon, 26 May 2003 16:30:39 -0400
Date: Mon, 26 May 2003 16:31:40 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Bob Braden <braden@ISI.EDU>
cc: billc44@citynet.net, <ietf@ietf.org>, <twatha@monitortan.com>
Subject: Re: spam
In-Reply-To: <200305261918.h4QJIxs27507@boreas.isi.edu>
Message-ID: <Pine.LNX.4.44.0305261555040.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Not only is the FTC business friendly, but so is Congress, and the Courts
(which struck down the junk fax law). As MAPS discovered with Exactis,
real commercial solicited email can not be blocked.

Of the Type 1 spammers, there are those that send solicited mail and those
that send unsolicited. They all want to operate with least annoyance, and
least complaints. I expect this group to utilize the DMA do-not-send
lists. So I expect that they will become less of a problem as time goes
by.  Type 1 operations will make changes to comply with law, and will not
be fraudulent.  I don't think this is anywhere close to the dominant form
of spam.  But if they were, things would be pretty good.  I think it is
the little operations that don't (yet) have these facilities, and are
misled by operations like ghostsender.com, which incidentally could be
itself controlled.  So even the little ones should be less of a problem in
the future.  Of course, ISPs could help by educating users on how to use
the internet commercially, such as how to use the DMA do-not-send list,
and what sort of cons are out there (like ghostsender.com). Particularly,
users should understand the general absence of true anonymity afforded by
the internet. The internet is no really no different from the PSTN, in
that respect.  I think this mis-perception contributes to the abuses of
the internet, not just spam, but other kinds of abuses as well.

The Type 2 abusers are relatively easy to find. That isn't a tough one to
solve.  This type probably won't ever go away, but this should not be any
more significant than other kinds of con-artists and grifters.

The real difficulty will be the Type 3's. But we don't know how much is
Type 3 yet. If its not a big proportion, then this shouldn't be a big
problem. On the other hand, if it is a big proporation, then we need to
interest the law enforcement agencies to chase down more "Kevin Mitnicks"
conducting "victimless" crimes. This could be harder to motivate, and at
present, no one is working on this that I know of.

		--Dean

On Mon, 26 May 2003, Bob Braden wrote:

>
>   *>
>   *> Type 1: Bonafide Messaging with a real Commercial or non-profit(ie
>   *> political) purpose.  This includes people selling contraband (eg drugs)
>   *> illegally, so long as they intend to deliver the illegal goods.
>   *>
>   *>
>   *>
>   *>
>   *> Of these types of spam, Type 1 and Type 2 can be dealt with by law, and
>   *> through the actions of the FTC and other regulatory agencies.
>
> So, what happens when the FTC, which is today very business-friendly,
> decides to place no restriction at all on "real Commercial" spam?
> Given the current politics in Washington, that seems like a likely
> scenario.  Yet, this spam is the most hard-to-filter, and it may soon
> become the dominant component of spam.  I for one don't want to see my
> email box filled with junk as my postal mailbox is.
>
> Bob Braden
>




From owner-ietf@ietf.org  Mon May 26 17:21:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27836
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 17:21:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KOys-0002Tt-I0
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 16:54:06 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KOlt-00019l-2m
	for ietf@asgard.ietf.org; Mon, 26 May 2003 16:40:41 -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 QAA25996
	for <ietf@ietf.org>; Mon, 26 May 2003 16:40:38 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOkN-000212-00
	for ietf@ietf.org; Mon, 26 May 2003 16:39:07 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOkM-00020z-00
	for ietf@ietf.org; Mon, 26 May 2003 16:39:06 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h4QKeUbM004179;
	Mon, 26 May 2003 16:40:30 -0400
Message-Id: <200305262040.h4QKeUbM004179@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Dean Anderson <dean@av8.com>
Cc: Anthony Atkielski <anthony@atkielski.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: spam 
In-Reply-To: Your message of "Mon, 26 May 2003 15:07:42 EDT."
             <Pine.LNX.4.44.0305261433180.3699-100000@commander.av8.net> 
References: <Pine.LNX.4.44.0305261433180.3699-100000@commander.av8.net>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1886110762P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 26 May 2003 16:40:30 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1886110762P
Content-Type: text/plain; charset=us-ascii

On Mon, 26 May 2003 15:07:42 EDT, Dean Anderson said:
> I notice that you can get 250Gig disks now for under $400. 2 Disks make 1
> 500Meg volume.  Apply a raid controller with 2 more disks, and we are
> talking about $2000 in disks. ($2000 is kind of inflated really, but some
> ISPs like Av8 consider mail to be important).

I'm sorry, but our policy doesn't bet the e-mail requirements of a $400M/year
organization on a single low-bidder RAID set.

Remember that at the same time as we're putting 750K messages/day INTO the
store, it's also being pounded by some 2M+ POP checks per day.  There's
response time issues, IO/sec limits - you end up wanting more spindles.

You might want to look at the rebuild time for a RAID set using those 250G
drives - you lose one drive, you're rebuilding to a hot spare for a LONG time.
And if you lose another drive in the meantime, you're screwed.  You want
to split your mailstore across multiple raid boxes so even if the unthinkable
happens, you only lose PART of the mailstore.  Trust me - we've been doing
this for a number of years, and there's *reasons* why the current mailstore
is split across 7 shelves of Sun D1000 disk when we could stick it all on
a single set of 3 250G drives.

Did I mention that you had to be able to back this all up?  And on a prompt
regular basis?  Twice the disk space because half of it is spam means twice
the backup capacity needed and twice the time to take a backup....

And I don't care if it only costs me $5,000 to buy all the resources I need to
store the spam - I'd like to know under what moral system it's OK to
rationalize spamming "just because I think it doesn't cost as much to support
as the actual recipient does".  That's pretty much the same thing as saying
that it's OK for your dog to urinate on my lawn and kill the grass because that
just means it will cost me $40 in grass seed rather than than the $20 I was
expecting to pay....


--==_Exmh_-1886110762P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+0nu+cC3lWbTT17ARAqlEAJ9tG2aKES+rLvF9q31NsC1TIxJDQACfbiSS
9GD5MabZsLagz7cJb2wn2kA=
=qYT5
-----END PGP SIGNATURE-----

--==_Exmh_-1886110762P--



From owner-ietf@ietf.org  Mon May 26 17:22:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27964
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 17:22:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KPBi-0003BY-IT
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 17:07:22 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KOxM-0002Lu-Qn
	for ietf@asgard.ietf.org; Mon, 26 May 2003 16:52:32 -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 QAA26641
	for <ietf@ietf.org>; Mon, 26 May 2003 16:52:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOvq-0002CE-00
	for ietf@ietf.org; Mon, 26 May 2003 16:50:58 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOvq-0002Bv-00
	for ietf@ietf.org; Mon, 26 May 2003 16:50:58 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id QAA10513;
	Mon, 26 May 2003 16:47:26 -0400
Date: Mon, 26 May 2003 16:48:17 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Bill Manning <bmanning@ISI.EDU>
cc: billc44@citynet.net, <ietf@ietf.org>, <watha@monitortan.com>,
        <phil@whirlycott.com>
Subject: Re: spam
In-Reply-To: <200305261918.h4QJI1c26858@boreas.isi.edu>
Message-ID: <Pine.LNX.4.44.0305261632060.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

I haven't seen this activity related to bonafide (Type 1 or Type 2)
spam, though I've heard anti-spammers say this a lot.

By definition, this is bidirectional communication. I've only seen it
abused by fake opt-out addresses that are either directly annoyance
related (eg, send IM floods) or send more email annoyance.  For example,
I've observed that responding to 20 Nigerian 411 scams resulted in no
solicitation of personal information, one response about a forged email
address, and a increase in the rate of 411 scam emails.

It has to start with a valid address, or via a dictionary attack. I
haven't observed any real spamhouses doing this.

There is little point, if they start with a valid address.  Most real
"harvesting" is via usenet, web, or email lists, or from published
directories sold by ISPs like AOL and Hotmail. So they already have a
legitimate address.  Marketing business is not interested in how many
addresses don't bounce, but what the response rate is.  That is, how many
purchases there were on a previous campaign to the same list. There is
little point in real organizations wanting to know whether the address is
valid, except to remove invalid addresses to reduce costs. Since email
costs are trivial, there is little benefit to this activity, unless you
have to handle the bounces. Mailing lists have this concern, but spammers
don't.

I think this activity is probably done by anti-spammers in protest of
"opt-out".

		--Dean



On Mon, 26 May 2003, Bill Manning wrote:

>  sending crap to see if the email address is valid is spam.  it is
>  unwanted, unsolicited, consumes resources I pay for w/o my consent.
>  the perp could care less what they send, as long as my local mail
>  system indicates delivery is successful.  they then "harvest" the
>  email address. if they do it twice and get an affirmative response
>  that mail is/would be successfully delivered, ... double opt-in!!
>
>  thats one thing -we- generally call spam.
>
>
> % Harvesting addresses isn't an email message. Its spam-related activity,
> % but it isn't spam.
> %
> % 		--Dean
> %
> % On Mon, 26 May 2003, Bill Manning wrote:
> %
> % > % There are 3 types of email that we generally call spam:
> % >
> % > 	who are "we"?
> % >
> % >  type 4: harvesting/collecting "working" email addresses to be re-sold.
> % >
> % >
> % > --bill
> % > Opinions expressed may not even be mine by the time you read them, and
> % > certainly don't reflect those of any other entity (legal or otherwise).
> % >
> %
>
>
> --
> --bill
>
> Opinions expressed may not even be mine by the time you read them, and
> certainly don't reflect those of any other entity (legal or otherwise).
>
>




From owner-ietf@ietf.org  Mon May 26 17:29:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28137
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 17:29:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KPOR-0004sF-4M
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 17:20:31 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KOzJ-0002Uc-8T
	for ietf@asgard.ietf.org; Mon, 26 May 2003 16:54:33 -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 QAA26717
	for <ietf@ietf.org>; Mon, 26 May 2003 16:54:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOxn-0002D3-00
	for ietf@ietf.org; Mon, 26 May 2003 16:52:59 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOxm-0002Cf-00
	for ietf@ietf.org; Mon, 26 May 2003 16:52:58 -0400
Content-class: urn:content-classes:message
Subject: RE: spam
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Mon, 26 May 2003 13:54:21 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F823@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: spam
Thread-Index: AcMjwfvsp90+auz5T+GWQC+BxHlU9gAAZYOg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Markku Savela" <msa@burp.tkv.asdf.org>
Cc: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA28137

Markku,

> Markku Savela wrote:
> The best techical solution that has been proposed seems to
> be the "tarpit" solution: detect spam on the fly and slow
> down the reception to trickle as "spamminess" grows. The
> great feature of this is, that it actually would keep spam
> "off my network" by stopping the flow.
> I would think technically, one would run a frontend tarpit
> pipeline on the standard SMTP port as follows
> port 25
> --------> TARPIT ----> real SMTP on other port or host
>              ^
>              |
>          SpamRules
> TARPIT would listen incoming connections, establish another
> connection to real SMTP server. It would examine the data
> on fly and slow the incoming reception when the spam index
> grows. Mail would not be rejected, just slowed, as
> "spammines index" grows.

I agree it's part of the solution; I use something like this already
called BCWare NoSpam (http://www.bcwaresystems.com/nospam/).

However, it's all about having good SpamRules. The SpamRules I currently
use are based on IP address using multiple spamlists such as MAPS,
Spamhaus and ORDB. Even with these real-time blackholing lists based on
the source IP address it's not enough to block more than half of the
spam if lucky.

If you want SpamRules based on content (such as containing certain words
in the text) you need to receive the entire thing. Problem is
occasionally I have to retrieve a false positive so it is better at this
time to have a filter in the email client that puts spam in a spam
folder that can be searched. Unfortunately this does not help with
storage space. The two systems are complementary, I think. 


> Of course, this solution only works if you are receiving your
> mail directly. If you receive your mail via mail forwarder,
> this won't help - the mail forwarder must be using it.

Actually, you are incorrect here. I use a piece of software called
Popcon
http://www.christensen-software.com/popcon.htm
It retrieves email from multiple pop3 accounts I have and analyze
headers. Even if the SMTP server that received the spam does not filter,
if one of the mail servers down the chain is a known open relay or
spammer the spam is sent directly to the bit bucket and I never see it.
I use the same blacklists as for BCWare NoSpam.

Michel.




From owner-ietf@ietf.org  Mon May 26 17:31:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26106
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 16:42:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KOZX-0000tH-1H
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 16:27:55 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KOLd-0000Dz-B2
	for ietf@asgard.ietf.org; Mon, 26 May 2003 16:13:33 -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 QAA25296
	for <ietf@ietf.org>; Mon, 26 May 2003 16:13:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOK7-0001oz-00
	for ietf@ietf.org; Mon, 26 May 2003 16:11:59 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOK6-0001ow-00
	for ietf@ietf.org; Mon, 26 May 2003 16:11:58 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207739; Mon, 26 May 2003 15:12:59 -0500
Message-ID: <3ED27568.70609@ehsco.com>
Date: Mon, 26 May 2003 15:13:28 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Bob Braden <braden@ISI.EDU>
CC: ietf@ietf.org
Subject: Re: spam
References: <200305261918.h4QJIxs27507@boreas.isi.edu>
In-Reply-To: <200305261918.h4QJIxs27507@boreas.isi.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/26/2003 2:18 PM Bob Braden wrote:

> So, what happens when the FTC, which is today very business-friendly,
> decides to place no restriction at all on "real Commercial" spam?
> Given the current politics in Washington, that seems like a likely
> scenario.

This is why principles are strategically important. It's not enough to say
"spam is annoying" and expect action. You have to give the parties
something that is more important ideologically than their default
positions. Property-rights are a fundamental tenet of the US economic and
judicial systems, and that argument can easily trump the pro-business
default position if victory is defined in those terms. Suboridinate
effects like releasing capital and facilitating competition appeal to
other factions which are still relatively close to the center. There are
still going to be a couple of camps who will be against it, but they will
be opposed to the principle (folks who oppose any strenghthening of any
private property laws on ideological grounds, in this example). Those
factions are the minority wing of the minority party right now, though.

In other words, this is a good time to attack from the right.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Mon May 26 17:35:49 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28350
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 17:35:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KPOS-0004uT-4s
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 17:20:32 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KP2b-0002vZ-Bg
	for ietf@asgard.ietf.org; Mon, 26 May 2003 16:57: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 QAA26858
	for <ietf@ietf.org>; Mon, 26 May 2003 16:57:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KP15-0002Gj-00
	for ietf@ietf.org; Mon, 26 May 2003 16:56:23 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KP14-0002Gg-00
	for ietf@ietf.org; Mon, 26 May 2003 16:56:22 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207749; Mon, 26 May 2003 15:57:22 -0500
Message-ID: <3ED27FD0.4080209@ehsco.com>
Date: Mon, 26 May 2003 15:57:52 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
CC: Bob Braden <braden@ISI.EDU>, ietf@ietf.org
Subject: Re: spam
References: <200305261918.h4QJIxs27507@boreas.isi.edu> <E19KOME-0004PL-8t@ran.psg.com>
In-Reply-To: <E19KOME-0004PL-8t@ran.psg.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


As a point of factual record, the TCPA was passed in 1991 not 1992-2000.
The administration under Bush Sr. was just as pro-business then as it is
now, and probably moreso considering the additional previous terms under
Reagan. Being pro-business isn't exclusionary to other ideologies.

on 5/26/2003 3:14 PM Randy Bush wrote:
>>So, what happens when the FTC, which is today very business-friendly,
>>decides to place no restriction at all on "real Commercial" spam?
> 
> 
> thank you for saying this.  i tried to make this point on nanog and
> failed.
> 
> what you will have is american television and commercial radio.
> 
> randy
> 
> 

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Mon May 26 17:35:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28376
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 17:35:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KPOR-0004sQ-F7
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 17:20:31 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KOzj-0002V1-UG
	for ietf@asgard.ietf.org; Mon, 26 May 2003 16:54:59 -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 QAA26725
	for <ietf@ietf.org>; Mon, 26 May 2003 16:54:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOyD-0002DK-00
	for ietf@ietf.org; Mon, 26 May 2003 16:53:25 -0400
Received: from tomts14.bellnexxia.net ([209.226.175.35] helo=tomts14-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOyD-0002DH-00
	for ietf@ietf.org; Mon, 26 May 2003 16:53:25 -0400
Received: from yahoo.com ([65.93.189.178]) by tomts14-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030526205457.KYJE14433.tomts14-srv.bellnexxia.net@yahoo.com>;
          Mon, 26 May 2003 16:54:57 -0400
Date: Mon, 26 May 2003 16:54:54 -0400
Subject: Re: spam
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <200305261906.h4QJ63W7025426@ginger.lcs.mit.edu>
Message-Id: <4D4EB1E4-8FBC-11D7-98C2-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Monday, May 26, 2003, at 03:06  PM, J. Noel Chiappa wrote:

> The reason is that I think all these legal measures are a complete 
> waste of
> time. The spammers who are determined to send you stuff will simply 
> move
> overseas to jurisdictions which don't care about spam (those that 
> aren't
> already there, that is - I get a lot of spam in Asian alphabets I 
> can't even
> read). All these US laws are interesting, but ultimately a waste of 
> time.

If spammers are forced to operate from certain network locations it 
will, at least, be easier to filter them at the door. If the product is 
being sold from north america/europe, it doesn't matter where the 
spammer is, the seller should also be responsible legally.


--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Mon May 26 17:41:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28702
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 17:41:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KPTd-0005kZ-Gx
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 17:25:53 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KPBm-0003CP-GO
	for ietf@asgard.ietf.org; Mon, 26 May 2003 17:07:26 -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 RAA27217
	for <ietf@ietf.org>; Mon, 26 May 2003 17:07:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KPAG-0002NX-00
	for ietf@ietf.org; Mon, 26 May 2003 17:05:52 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KPAF-0002NL-00
	for ietf@ietf.org; Mon, 26 May 2003 17:05:51 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id QAA27708;
	Mon, 26 May 2003 16:57:49 -0400
Date: Mon, 26 May 2003 16:58:41 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: "Eric A. Hall" <ehall@ehsco.com>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <3ED27906.1030002@ehsco.com>
Message-ID: <Pine.LNX.4.44.0305261653061.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Mon, 26 May 2003, Eric A. Hall wrote:

>
> on 5/26/2003 2:20 PM Dean Anderson wrote:
> > Social problems are not that simple. They are not solved by
> > confrontation. Because there is no confrontation, there is no victory
> > to be had.
>
> I am advocating the establishment of a confrontation so that one can be
> had. At the moment there is none, but that's not justification to avoid
> ever having one.

You have yet to find any compelling grounds on which to limit real
commercial speech, and yet to even demonstrate any harms of real
commercial speech.

Most of the examples of harmful spam are of the Type 2 and Type 3 variety,
which is why Congress and the states have moved to address Type 2. Type 3
is already illegal.

		--Dean




From owner-ietf@ietf.org  Mon May 26 17:56:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27259
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 17:10:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KOyr-0002SJ-9f
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 16:54:05 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KOaY-0000wz-MR
	for ietf@asgard.ietf.org; Mon, 26 May 2003 16:28:58 -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 QAA25750
	for <ietf@ietf.org>; Mon, 26 May 2003 16:28:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOZ2-0001xU-00
	for ietf@ietf.org; Mon, 26 May 2003 16:27:24 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KOZ2-0001xR-00
	for ietf@ietf.org; Mon, 26 May 2003 16:27:24 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207742; Mon, 26 May 2003 15:28:24 -0500
Message-ID: <3ED27906.1030002@ehsco.com>
Date: Mon, 26 May 2003 15:28:54 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: ietf@ietf.org
Subject: Re: spam
References: <Pine.LNX.4.44.0305261511340.3699-100000@commander.av8.net>
In-Reply-To: <Pine.LNX.4.44.0305261511340.3699-100000@commander.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/26/2003 2:20 PM Dean Anderson wrote:
> Social problems are not that simple. They are not solved by
> confrontation. Because there is no confrontation, there is no victory
> to be had.

I am advocating the establishment of a confrontation so that one can be
had. At the moment there is none, but that's not justification to avoid
ever having one.

> But a confrontation (physical or legal) without regard to rights and 
> reason will only go badly for those who pursue it.

Of course they have rights. But some rights trump all others. In the US,
property rights trump commercial and free speech rights all the time.
Governments go directly against the first amendment with "post no bills"
all the time. Similarly, the first amendment doesn't give anybody the
right to put an ~abortion bumper sticker on my car without my permission.
The mere existence of some right does not grant the permanent exercise of
that right in all cases.

> Some anti-spammers might be happy to find a spammer in a back alley,
> and beat them.

Let's stick to the legal please.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Mon May 26 17:58:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29279
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 17:58:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KPfl-0007Lm-4W
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 17:38:25 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KPTU-0005kP-JE
	for ietf@asgard.ietf.org; Mon, 26 May 2003 17:25:44 -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 RAA28094
	for <ietf@ietf.org>; Mon, 26 May 2003 17:25:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KPRy-0002f2-00
	for ietf@ietf.org; Mon, 26 May 2003 17:24:10 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KPRx-0002ex-00
	for ietf@ietf.org; Mon, 26 May 2003 17:24:09 -0400
Content-class: urn:content-classes:message
Subject: RE: spam
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Mon, 26 May 2003 14:25:33 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F824@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: spam
Thread-Index: AcMjvCs71XbV0/weQKOTIhb6ZxviQAADM1Hw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA29279

Noel,


> J. Noel Chiappa wrote: 
> The *only* thing that's going to stop spam is charging for
> email. Everything else is a waste of time.

I agree. The reason why junk paper mail and catalogs stay under control
is because they cost a lot of money to send.


> because you're going to run into impossible arguments
> trying to define what's spam, and what's legitimate
> bulk email.

Yes. Sigh.


> Needless to say, charging for email means changing the
> underlying protocols. That's us. It's not going to be simple
> (we need an underlying micro-payments system),

I would like mega-payments please.


> and it's going to take a lot of attention to detail
> (q.v. IETF-Announce again), but I think it's the only
> real cure.

I think that I would like is a system that charges $20 for each email
received. No money, no email. Then if the email is spam the recipient
(me) keeps the money. You can be sure that at $20 a spam I would drop
all my filters and begin to read them.

If the email is not tagged as spam after say a week, the system charges
it back. Such a system is going to be extremely difficult to deploy
though.

Michel.




From owner-ietf@ietf.org  Mon May 26 18:07:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29931
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 18:07:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KPgu-0007Mi-AI
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 17:39:36 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KPXe-0006A8-BU
	for ietf@asgard.ietf.org; Mon, 26 May 2003 17:30:02 -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 RAA28165
	for <ietf@ietf.org>; Mon, 26 May 2003 17:29:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KPW8-0002gf-00
	for ietf@ietf.org; Mon, 26 May 2003 17:28:28 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KPW6-0002gV-00
	for ietf@ietf.org; Mon, 26 May 2003 17:28:26 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207747; Mon, 26 May 2003 16:29:26 -0500
Message-ID: <3ED28753.3070901@ehsco.com>
Date: Mon, 26 May 2003 16:29:55 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: ietf@ietf.org
Subject: Re: spam
References: <Pine.LNX.4.44.0305261653061.3699-100000@commander.av8.net>
In-Reply-To: <Pine.LNX.4.44.0305261653061.3699-100000@commander.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/26/2003 3:58 PM Dean Anderson wrote:

> You have yet to find any compelling grounds on which to limit real 
> commercial speech, and yet to even demonstrate any harms of real 
> commercial speech.

Spam on my measured-rate cellular-data PDA is real cost. Spam on my
measured-rate ISDN line (California) is real cost. Extra staffing to
counteract spam at my [isp|university|business] is real cost (setting
aside other costs that you seem willing to ignore). There are plenty of
examples to pick from.

These are abnormal expenses which go directly into maintaining the
usefulness of my property and which do not increase its value. The right
to commercial speech would not warrant these costs for any other venue,
and there is nothing sufficiently different and unique about this venue to
warrant it here.

You are certainly entitled to the opposite opinion but the existence of
previous laws for protection in other venues is evidence against you.
Perhaps you can provide an example of a law that acts as evidence in favor
of your opinion so we can see how this balances out.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Mon May 26 18:08:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00112
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 18:08:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KPub-000883-RT
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 17:53:45 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KPcT-0006Tx-69
	for ietf@asgard.ietf.org; Mon, 26 May 2003 17:35:01 -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 RAA28337
	for <ietf@ietf.org>; Mon, 26 May 2003 17:34:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KPax-0002jh-00
	for ietf@ietf.org; Mon, 26 May 2003 17:33:27 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KPaw-0002je-00
	for ietf@ietf.org; Mon, 26 May 2003 17:33:26 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4QLZ4Hs002228
	for <ietf@ietf.org>; Mon, 26 May 2003 23:35:04 +0200 (CEST)
Message-ID: <005e01c323ce$ab9f3a00$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <000501c32253$f6707160$92082b45@a> <093001c322af$60b28800$0a00000a@atkielski.com> <3ED0D8B3.8070303@ehsco.com> <Pine.GSO.4.50.0305251626220.24020-100000@argos.ee.surrey.ac.uk> <3ED120AE.9000306@ehsco.com>            <020b01c32353$f73d18e0$0a00000a@atkielski.com> <200305261609.h4QG9Ka7012963@turing-police.cc.vt.edu>
Subject: Re: spam 
Date: Mon, 26 May 2003 23:35:04 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Valdis writes:

> Sure, hitting delete isn't expensive for one
> person.  Scale that to our 80K mailboxes and
> include all the infrastructure costs, and suddenly
> you're quite easily looking at $1M/year or more.

It still costs less than having to open a separate text attachment just to
read someone's message, though.  I won't name names.




From owner-ietf@ietf.org  Mon May 26 18:13:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00744
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 18:13:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KQ60-0003Wi-RP
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 18:05:32 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KPpa-0007zg-NA
	for ietf@asgard.ietf.org; Mon, 26 May 2003 17:48:34 -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 RAA29079
	for <ietf@ietf.org>; Mon, 26 May 2003 17:48:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KPo4-0002wv-00
	for ietf@ietf.org; Mon, 26 May 2003 17:47:00 -0400
Received: from portal.hamachi.org ([140.239.227.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KPo4-0002ws-00
	for ietf@ietf.org; Mon, 26 May 2003 17:47:00 -0400
Received: from syn.hamachi.org (localhost [127.0.0.1])
	by portal.hamachi.org (Postfix) with ESMTP
	id D6B0E17939; Mon, 26 May 2003 17:48:32 -0400 (EDT)
Received: from syn.hamachi.org (sommerfeld@localhost)
	by syn.hamachi.org (8.12.7+Sun/8.8.8) with ESMTP id h4QLmlwg003904;
	Mon, 26 May 2003 17:48:47 -0400 (EDT)
Message-Id: <200305262148.h4QLmlwg003904@syn.hamachi.org>
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
To: Dean Anderson <dean@av8.com>
Cc: "Eric A. Hall" <ehall@ehsco.com>, ietf@ietf.org
Subject: Re: spam 
In-Reply-To: Your message of "Mon, 26 May 2003 16:58:41 EDT."
             <Pine.LNX.4.44.0305261653061.3699-100000@commander.av8.net> 
Reply-To: sommerfeld@orchard.arlington.ma.us
Date: Mon, 26 May 2003 17:48:47 -0400
Xender: sommerfeld@syn.hamachi.org
Sender: owner-ietf@ietf.org
Precedence: bulk

> You have yet to find any compelling grounds on which to limit real
> commercial speech, and yet to even demonstrate any harms of real
> commercial speech.

I stumbled across this writeup recently:

http://www.clifto.com/7359.html

("7359" is the estimated number of messages/day/user if the average
mailbox were to get one message a month from 1% of US businesses).

						- Bill



From owner-ietf@ietf.org  Mon May 26 18:16:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01110
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 18:16:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KQ61-0003Wt-41
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 18:05:33 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KPsn-0007zu-Do
	for ietf@asgard.ietf.org; Mon, 26 May 2003 17:51:53 -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 RAA29123
	for <ietf@ietf.org>; Mon, 26 May 2003 17:51:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KPrH-0002y4-00
	for ietf@ietf.org; Mon, 26 May 2003 17:50:19 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KPrG-0002xv-00
	for ietf@ietf.org; Mon, 26 May 2003 17:50:18 -0400
Content-class: urn:content-classes:message
Subject: RE: spam 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Mon, 26 May 2003 14:51:42 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F825@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: spam 
Thread-Index: AcMjzOedmSVbtGXpQ0Sz8+NGYWnNeAAAKjQg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Dean Anderson" <dean@av8.com>
Cc: "IETF Discussion" <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA01110

> Dean Anderson wrote:
> I notice that you can get 250Gig disks now for under $400.

What kind of crap would that be? 7200 RPM IDE drives? With a Promise
raid maybe (great product for a home PC btw). Not the kind of stuff I
put in my mission-critical servers and I don't put big drives either as
a RAID-10 array of smaller (36gig) 15KRPM is what brings speed. 


> 2 Disks make 1 500Meg volume.

By my count 500 Megs is 28 disks @$350 ea which is $10k.
Plus 4 hot-swap enclosures with RPS @$2.5k ea $10k more.
Now I need to back it up, takes 3 ultrium drives @ $6k ea is $18k more.
Backup Exec Raid option: $600
2x 64-bit RAID card: $5k

500 gigs = $45K as of today.

Michel.




From owner-ietf@ietf.org  Mon May 26 18:20:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01289
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 18:20:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KQ8v-0004s0-D6
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 18:08:33 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KQ20-0001AC-FG
	for ietf@asgard.ietf.org; Mon, 26 May 2003 18:01:24 -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 SAA29425
	for <ietf@ietf.org>; Mon, 26 May 2003 18:01:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQ0T-000334-00
	for ietf@ietf.org; Mon, 26 May 2003 17:59:49 -0400
Received: from bean.ar.com ([66.123.187.68])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQ0T-000331-00
	for ietf@ietf.org; Mon, 26 May 2003 17:59:49 -0400
Received: from flash.ar.com (wessorh@flash [66.123.187.80])
	by bean.ar.com (8.12.6/8.12.6) with ESMTP id h4QM0HdX007115;
	Mon, 26 May 2003 15:00:17 -0700 (PDT)
Date: Mon, 26 May 2003 15:00:17 -0700 (PDT)
From: Rick Wesson <wessorh@ar.com>
To: Bill Manning <bmanning@ISI.EDU>
cc: Dean Anderson <dean@av8.com>, <billc44@citynet.net>, <ietf@ietf.org>,
        <watha@monitortan.com>, <phil@whirlycott.com>
Subject: Re: spam
In-Reply-To: <200305261918.h4QJI1c26858@boreas.isi.edu>
Message-ID: <Pine.LNX.4.33.0305261458300.9427-100000@flash.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


Bill,

it depends on the context, some domain registrars check the deliverability
of an e-mail address before registering domains where a contact or
maintainer is listed on the registration.

the ability to check deliverability w/o actualling delivering mail is at
time a useful thing for those attempting to cut down on registration
fraud.

-rick


On Mon, 26 May 2003, Bill Manning wrote:

>  sending crap to see if the email address is valid is spam.  it is
>  unwanted, unsolicited, consumes resources I pay for w/o my consent.
>  the perp could care less what they send, as long as my local mail
>  system indicates delivery is successful.  they then "harvest" the
>  email address. if they do it twice and get an affirmative response
>  that mail is/would be successfully delivered, ... double opt-in!!
>
>  thats one thing -we- generally call spam.
>
>
> % Harvesting addresses isn't an email message. Its spam-related activity,
> % but it isn't spam.
> %
> % 		--Dean
> %
> % On Mon, 26 May 2003, Bill Manning wrote:
> %
> % > % There are 3 types of email that we generally call spam:
> % >
> % > 	who are "we"?
> % >
> % >  type 4: harvesting/collecting "working" email addresses to be re-sold.
> % >
> % >
> % > --bill
> % > Opinions expressed may not even be mine by the time you read them, and
> % > certainly don't reflect those of any other entity (legal or otherwise).
> % >
> %
>
>
> --
> --bill
>
> Opinions expressed may not even be mine by the time you read them, and
> certainly don't reflect those of any other entity (legal or otherwise).
>
>




From owner-ietf@ietf.org  Mon May 26 18:29:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01584
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 18:29:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KQ8v-0004sY-Ph
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 18:08:33 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KQ3z-0002uy-2f
	for ietf@asgard.ietf.org; Mon, 26 May 2003 18:03:27 -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 SAA29500
	for <ietf@ietf.org>; Mon, 26 May 2003 18:03:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQ2S-00033W-00
	for ietf@ietf.org; Mon, 26 May 2003 18:01:52 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQ2S-00033T-00
	for ietf@ietf.org; Mon, 26 May 2003 18:01:52 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4QM3THs002474
	for <ietf@ietf.org>; Tue, 27 May 2003 00:03:29 +0200 (CEST)
Message-ID: <009b01c323d2$a3c4bdb0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.44.0305261351380.3699-100000@commander.av8.net>
Subject: Re: spam (fwd) (edit error on previous)
Date: Tue, 27 May 2003 00:03:29 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dean writes:

> Of these types of spam, Type 1 and Type 2
> can be dealt with by law ...

Not on a worldwide network.  No organization or government has worldwide
jurisdiction.

> What is unclear is how much of the total spam
> is due to each of these types.  A lot of the spam
> that I recieve, and I have kept all this for
> some time now, appears to be from type 3B.

Almost everything I get seems to be Type 1, although I don't look at it very
closely.

> I note that helllabs.com.ua makes false and
> misleading claims that relays and proxies are free.

What is false about such claims?

> But what protocols can be specified to reduce or
> eliminate spam?

Almost none.  The problem is that spam is in the eye of the beholder.
Catching it with machine intelligence is practically impossible.  It's like
trying to scan messages for sarcasm.





From owner-ietf@ietf.org  Mon May 26 18:29:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01640
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 18:29:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KQ8w-0004se-4X
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 18:08:34 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KQ4B-0002yQ-Uq
	for ietf@asgard.ietf.org; Mon, 26 May 2003 18:03:39 -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 SAA29522
	for <ietf@ietf.org>; Mon, 26 May 2003 18:03:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQ2f-00033b-00
	for ietf@ietf.org; Mon, 26 May 2003 18:02:05 -0400
Received: from [208.184.79.11] (helo=clint.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQ2e-00033I-00
	for ietf@ietf.org; Mon, 26 May 2003 18:02:04 -0400
Received: from rshockeybox.shockey.us (h-69-3-5-197.MCLNVA23.covad.net [69.3.5.197])
	by clint.songbird.com (8.11.6/8.11.6) with ESMTP id h4QM5gO30330;
	Mon, 26 May 2003 15:05:42 -0700
Message-Id: <5.2.0.9.2.20030526174731.0295cbe8@shockey.us>
X-Sender: richard@shockey.us
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 26 May 2003 17:52:19 -0400
To: S Woodside <sbwoodside@yahoo.com>, Lloyd Wood <L.Wood@eim.surrey.ac.uk>
From: Richard Shockey <richard@shockey.us>
Subject: Re: spam
Cc: IETF Discussion <ietf@ietf.org>
In-Reply-To: <5602BC2A-8FA6-11D7-ADA9-000393414368@yahoo.com>
References: <Pine.GSO.4.50.0305261357040.28832-100000@argos.ee.surrey.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 02:17 PM 5/26/2003 -0400, S Woodside wrote:


>On Monday, May 26, 2003, at 08:58  AM, Lloyd Wood wrote:
>
>>On Sun, 25 May 2003, S Woodside wrote:
>>
>>>Good law could work to curtail spam. Spammers do it because it's
>>>profitable. Remove the profit, fine the dickens out of the worst
>>>transgressors, and the cost/benefit ratio will sink. Spamming isn't
>>>like hacking, there is always a way to trace back to the person who is
>>>paying for the spam because they must be able to sell their product.
>>>Since you can identify the individuals responsible, you can hold them
>>>accountable with the right laws in place.
>>
>>and this has worked so well with the War on Drugs.
>
>The internet is not the street. Someone is selling a product. In order to 
>sell a product you must be able to reach them. If you can reach them, you 
>can find a way to deal with them legally.

Excellent point .. at the FTC Workshop on SPAM this was pointed out in 
considerable detail. FTC staff randomly looked at about 2000 spam messages 
collected internally from FTC mail servers and were able to identify that 
80% of the SPAM contained phone numbers addresses or other contact data 
that could be traced to and individual or business domiciled in the United 
States.

That the mail was set off shore was not the issue... you attack the problem 
at its source ..the business that use SPAM.  Follow the money!

ON that basis they were able to conclude that with sufficient enforcement 
resources the FTC could track down these people rather easily. Conclusion a 
good law , including private right of action, written well, backed by 
sufficient resources at both the state and federal level can work.

We can never eliminate SPAM only make it a manageable problem ..just like 
we saw in the case of junk-fax. I can never understand why folks cannot 
look back at that legislation and see the parallels to SPAM and the successes.



>simon


 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
Voice +1 571.434.5651 Cell : +1 703.593.2683,  Fax: +1 815.333.1237
<mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
  <http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<




From owner-ietf@ietf.org  Mon May 26 18:33:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01882
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 18:33:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KQI0-0008Ua-Ap
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 18:17:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KQ7r-00041R-FN
	for ietf@asgard.ietf.org; Mon, 26 May 2003 18:07:27 -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 SAA29901
	for <ietf@ietf.org>; Mon, 26 May 2003 18:07:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQ6L-00034i-00
	for ietf@ietf.org; Mon, 26 May 2003 18:05:53 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQ6K-00034P-00
	for ietf@ietf.org; Mon, 26 May 2003 18:05:52 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id RAA25080;
	Mon, 26 May 2003 17:58:47 -0400
Date: Mon, 26 May 2003 17:59:49 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Richard Welty <rwelty@averillpark.net>
cc: ietf@ietf.org
Subject: Re[2]: spam
In-Reply-To: <E19KOU5-0007Om-U4@skipper.averillpark.net>
Message-ID: <Pine.LNX.4.44.0305261758060.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Actually, I've been in touch with an attorney at the FTC. It seems they
have been factually misled on some issues.

		--Dean

On Mon, 26 May 2003, Richard Welty wrote:

>
> On Mon, 26 May 2003 12:18:59 -0700 (PDT) Bob Braden <braden@ISI.EDU> wrote:
> > So, what happens when the FTC, which is today very business-friendly,
> > decides to place no restriction at all on "real Commercial" spam?
> > Given the current politics in Washington, that seems like a likely
> > scenario.
>
> i disagree.
>
> from what i have heard from participants in the FTC "spam summit" (and
> what i viewed in some of the recordings of sessions which were available
> online briefly), it seems clear that the FTC has done the math and
> understands the nature of the problem fairly well.
>
> however, they are tightly constrained by their mandate from Congress. this
> is where the real problem lies.
>
> there are at least some legislators who are willing to write legislation
> that refers to standards from recognized standards bodies (e.g., the IETF).
> this is where the opportunity for the IETF to help lies -- to devise new
> standards and protocols which won't necessarily stop spam, but which when
> combined with legislation and properly funded enforcement bodies, can stop
> or at least cut it down.
>
> the international nature of the problem is undersood by at least some
> legislators as well.  Senator Schumer (NY) is already on record as believing
> that there will need to be international treaties as part of the solution
> to the spam problem.
>
> one of the things that has contributed to the evident lack of progress is
> the argument about technical means vs legislative/enforcement means.
> neither is really sufficient, it will take a combination of the two.
>
> richard
> --
> Richard Welty                                         rwelty@averillpark.net
> Averill Park Networking                                         518-573-7592
>               Unix, Linux, IP Network Engineering, Security
>
>
>
>




From owner-ietf@ietf.org  Mon May 26 18:40:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02224
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 18:40:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KQI1-0008W5-4b
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 18:17:57 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KQ8s-0004iT-6v
	for ietf@asgard.ietf.org; Mon, 26 May 2003 18:08:30 -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 SAA00080
	for <ietf@ietf.org>; Mon, 26 May 2003 18:08:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQ7M-00036T-00
	for ietf@ietf.org; Mon, 26 May 2003 18:06:56 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQ7L-00036O-00
	for ietf@ietf.org; Mon, 26 May 2003 18:06:55 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4QM8WHs002516
	for <ietf@ietf.org>; Tue, 27 May 2003 00:08:32 +0200 (CEST)
Message-ID: <00aa01c323d3$58562ca0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <200305261906.h4QJ63W7025426@ginger.lcs.mit.edu>
Subject: Re: spam
Date: Tue, 27 May 2003 00:08:32 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

J. Noel writes:

> Needless to say, charging for email means changing
> the underlying protocols.

Once you are charging for e-mail, it's only a matter of time before you are
charging for everything.  Instead of having free access to the entire net
for $9 a month, you'll have paying access for $190 in itemized billing each
month, depending on exactly what you do and how much you do it.  And it will
all be recorded somewhere, too, in case anyone wants to look at it to see if
you're a suspcious character.

No thanks.  I'll just delete the spam when I receive it.  It's an annoyance,
not a crisis.





From owner-ietf@ietf.org  Mon May 26 18:44:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02412
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 18:44:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KQUT-0001Oc-50
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 18:30:49 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KQB2-0005wq-Nk
	for ietf@asgard.ietf.org; Mon, 26 May 2003 18:10:44 -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 SAA00416
	for <ietf@ietf.org>; Mon, 26 May 2003 18:10:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQ9W-00039f-00
	for ietf@ietf.org; Mon, 26 May 2003 18:09:10 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQ9V-00039Z-00
	for ietf@ietf.org; Mon, 26 May 2003 18:09:09 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207766; Mon, 26 May 2003 17:10:06 -0500
Message-ID: <3ED290DC.9060101@ehsco.com>
Date: Mon, 26 May 2003 17:10:36 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: ietf@ietf.org
Subject: Re: spam
References: <Pine.LNX.4.44.0305261555040.3699-100000@commander.av8.net>
In-Reply-To: <Pine.LNX.4.44.0305261555040.3699-100000@commander.av8.net>
Content-Type: text/plain; charset=ISO-8859-1
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id SAA00417
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA02412


on 5/26/2003 3:31 PM Dean Anderson wrote:
> Not only is the FTC business friendly, but so is Congress, and the
> Courts (which struck down the junk fax law).

The only instance I know of where the TCPA was "struck down", the ruling
was reversed on appeal in the 8th circuit.

http://www.techlawjournal.com/topstories/2003/20030321.asp has a sumamry

http://www.ca8.uscourts.gov/opndir/03/03/022705P.pdf has the opinion

 | We conclude that 47 U.S.C. § 227(b)(1)(C) satisfies the
 | constitutional test for regulation of commercial speech and thus
 | withstands First Amendment scrutiny. There is a substantial
 | governmental interest in protecting the public from the cost
 | shifting and interference caused by unwanted fax advertisements,
 | and the means chosen by Congress to address these harms directly
 | and materially advances the governmental interest. The statute is
 | also narrowly tailored to create a reasonable fit with its
 | objective. Accordingly, we reverse the judgment dismissing the
 | claims asserted under § 227(b)(1)(C) and remand the case to the
 | district court for further proceedings consistent with this
 | opinion.

The TCPA has survived in other circuits as well.

standard disclaimer applies, IANAL

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Mon May 26 18:45:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02547
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 18:45:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KQev-0002my-2c
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 18:41:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KQJu-0008WQ-Si
	for ietf@asgard.ietf.org; Mon, 26 May 2003 18:19:54 -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 SAA01269
	for <ietf@ietf.org>; Mon, 26 May 2003 18:19:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQIO-0003H8-00
	for ietf@ietf.org; Mon, 26 May 2003 18:18:20 -0400
Received: from krusty-motorsports.com ([192.94.170.8] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQIO-0003H5-00
	for ietf@ietf.org; Mon, 26 May 2003 18:18:20 -0400
Received: from [24.194.112.77] (helo=skipper.averillpark.net)
	by krusty-motorsports.com with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.14)
	id 19KQJt-0007EF-1U
	for ietf@ietf.org; Mon, 26 May 2003 22:19:53 +0000
Received: from rwelty by skipper.averillpark.net with local (Exim 4.14)
	id 19KQJK-0007U5-8I
	for ietf@ietf.org; Mon, 26 May 2003 18:19:18 -0400
Date: Mon, 26 May 2003 18:19:18 -0400 (EDT)
From: Richard Welty <rwelty@averillpark.net>
Subject: Re[3]: spam
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Disposition: INLINE
References: <Pine.LNX.4.44.0305261758060.3699-100000@commander.av8.net>
In-Reply-To: <Pine.LNX.4.44.0305261758060.3699-100000@commander.av8.net>
X-Mailer: Mahogany 0.64 'Sparc', compiled for Linux 2.4.9-13 i686
Message-Id: <E19KQJK-0007U5-8I@skipper.averillpark.net>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 26 May 2003 17:59:49 -0400 (EDT) Dean Anderson <dean@av8.com> wrote:

> Actually, I've been in touch with an attorney at the FTC. It seems they
> have been factually misled on some issues.

have they been factually misled, or have they simply come to conclusions
that you don't like?

this was a really useless posting, dean, asserting that the FTC has been
misled w/o providing a single bit of supporting evidence.

richard
--
Richard Welty                                         rwelty@averillpark.net
Averill Park Networking                                         518-573-7592
              Unix, Linux, IP Network Engineering, Security





From owner-ietf@ietf.org  Mon May 26 18:46:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02609
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 18:46:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KQUU-0001R9-0Z
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 18:30:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KQF3-0007SI-2I
	for ietf@asgard.ietf.org; Mon, 26 May 2003 18:14:53 -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 SAA00986
	for <ietf@ietf.org>; Mon, 26 May 2003 18:14:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQDW-0003D7-00
	for ietf@ietf.org; Mon, 26 May 2003 18:13:18 -0400
Received: from [208.184.79.11] (helo=clint.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQDW-0003Cc-00
	for ietf@ietf.org; Mon, 26 May 2003 18:13:18 -0400
Received: from rshockeybox.shockey.us (h-69-3-5-197.MCLNVA23.covad.net [69.3.5.197])
	by clint.songbird.com (8.11.6/8.11.6) with ESMTP id h4QMH0O30917;
	Mon, 26 May 2003 15:17:00 -0700
Message-Id: <5.2.0.9.2.20030526180120.029c8b78@shockey.us>
X-Sender: richard@shockey.us
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 26 May 2003 18:11:11 -0400
To: Richard Welty <rwelty@averillpark.net>, ietf@ietf.org
From: Richard Shockey <richard@shockey.us>
Subject: Re[2]: spam
In-Reply-To: <E19KOU5-0007Om-U4@skipper.averillpark.net>
References: <200305261918.h4QJIxs27507@boreas.isi.edu>
 <200305261918.h4QJIxs27507@boreas.isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 04:22 PM 5/26/2003 -0400, Richard Welty wrote:


>On Mon, 26 May 2003 12:18:59 -0700 (PDT) Bob Braden <braden@ISI.EDU> wrote:
> > So, what happens when the FTC, which is today very business-friendly,
> > decides to place no restriction at all on "real Commercial" spam?
> > Given the current politics in Washington, that seems like a likely
> > scenario.
>
>i disagree.
>
>from what i have heard from participants in the FTC "spam summit" (and
>what i viewed in some of the recordings of sessions which were available
>online briefly), it seems clear that the FTC has done the math and
>understands the nature of the problem fairly well.

Yes ... the FTC staff have been very very good at educating themselves 
about the problem because  they have had the unqualified support of the 
entire Commission particularly the Chairman and Commissioner Orson Swindle. 
They have been looking at this for over a year.

In private conversations with them they remarkably well versed in SMTP and 
could quote the RFC's from memory.


>however, they are tightly constrained by their mandate from Congress. this
>is where the real problem lies.

In Washington speak that means they don't have any money.

Charlie Schumer at the FTC meeting offered up 75M in funding (  the C-SPAN 
cameras were on ) which someone pointed out to him was half the FTC's 
current budget.


>there are at least some legislators who are willing to write legislation
>that refers to standards from recognized standards bodies (e.g., the IETF).
>this is where the opportunity for the IETF to help lies -- to devise new
>standards and protocols which won't necessarily stop spam, but which when
>combined with legislation and properly funded enforcement bodies, can stop
>or at least cut it down.

First the legislators need to know the IETF / ISOC exists...


>the international nature of the problem is undersood by at least some
>legislators as well.  Senator Schumer (NY) is already on record as believing
>that there will need to be international treaties as part of the solution
>to the spam problem.

There were two official delegations at the FTC meeting one from France 
which is looking at similar legislation and from Korea who spent most of 
their presentation apologizing for the lack of effort on the part of the 
Korean Government which they now promise to increase.


>one of the things that has contributed to the evident lack of progress is
>the argument about technical means vs legislative/enforcement means.
>neither is really sufficient, it will take a combination of the two.
>
>r







 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
Voice +1 571.434.5651 Cell : +1 703.593.2683,  Fax: +1 815.333.1237
<mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
  <http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<




From owner-ietf@ietf.org  Mon May 26 18:54:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02912
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 18:54:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KQew-0002pV-2L
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 18:41:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KQMN-0000QH-Uu
	for ietf@asgard.ietf.org; Mon, 26 May 2003 18:22:27 -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 SAA01469
	for <ietf@ietf.org>; Mon, 26 May 2003 18:22:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQKr-0003Kk-00
	for ietf@ietf.org; Mon, 26 May 2003 18:20:53 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQKr-0003KN-00
	for ietf@ietf.org; Mon, 26 May 2003 18:20:53 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id SAA31180;
	Mon, 26 May 2003 18:16:21 -0400
Date: Mon, 26 May 2003 18:17:23 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: "Eric A. Hall" <ehall@ehsco.com>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <3ED28753.3070901@ehsco.com>
Message-ID: <Pine.LNX.4.44.0305261802010.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Mon, 26 May 2003, Eric A. Hall wrote:

>
> on 5/26/2003 3:58 PM Dean Anderson wrote:
>
> > You have yet to find any compelling grounds on which to limit real
> > commercial speech, and yet to even demonstrate any harms of real
> > commercial speech.
>
> Spam on my measured-rate cellular-data PDA is real cost. Spam on my
> measured-rate ISDN line (California) is real cost. Extra staffing to
> counteract spam at my [isp|university|business] is real cost (setting
> aside other costs that you seem willing to ignore). There are plenty of
> examples to pick from.

Don't get email on measured rate services, then. Or don't publish the
email to measured rate services. Put your measured rate services on the
do-not-send list. There are many options besides banning commercial email.

> These are abnormal expenses which go directly into maintaining the
> usefulness of my property and which do not increase its value. The right
> to commercial speech would not warrant these costs for any other venue,
> and there is nothing sufficiently different and unique about this venue to
> warrant it here.

These are not abnormal expenses. You have deal with abuse no matter what
the form. You have to have an abuse person. Persons intent on performing
abuse will abuse whatever is handy.

There are no costs to warrant.  Spam cannot cost you more than $1 or $2
per month per user. It doesn't matter how many abuse administrators you
have, or how big and expensive your servers are.  Email (including spam)
is too cheap to meter. It is practically free, per person.  Sites that
have 10 million users are going to have larger expenses than sites that
have 10 users. That isn't a surprise, nor a compelling reason to ban spam.

> You are certainly entitled to the opposite opinion but the existence of
> previous laws for protection in other venues is evidence against you.
> Perhaps you can provide an example of a law that acts as evidence in favor
> of your opinion so we can see how this balances out.

Junk fax law, overturned as being unconstitutional restriction on speech.

Anyway, I think commercial speech including spam _could_ be regulated, but
there so far is no justification for doing so. I don't think there is any
chance whatsoever that spam will ever be banned completely, and if it
were, it would suffer the same fate as the Junk Fax law, which had much
more signficant costs (consumption of paper at 10 cents per page) and
significant definite harms (lost faxes due to being out of paper) than
spam ever will.

		--Dean




From owner-ietf@ietf.org  Mon May 26 19:00:28 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03168
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 19:00:28 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KQfO-0002r4-41
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 18:42:06 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KQSV-0000fh-CM
	for ietf@asgard.ietf.org; Mon, 26 May 2003 18:28:47 -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 SAA01570
	for <ietf@ietf.org>; Mon, 26 May 2003 18:28:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQQz-0003MU-00
	for ietf@ietf.org; Mon, 26 May 2003 18:27:13 -0400
Received: from thunk.org ([140.239.227.29] helo=thunker.thunk.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQQy-0003MR-00
	for ietf@ietf.org; Mon, 26 May 2003 18:27:12 -0400
Received: from [212.140.113.179] (helo=think.thunk.org)
	authenticated as tytso by thunker.thunk.org with asmtp 
	(tls_cipher TLSv1:DES-CBC3-SHA:168)  (Exim 3.35 #1 (Debian))
	id 19KQSH-0000QR-00; Mon, 26 May 2003 18:28:35 -0400
Received: from tytso authenticated as tytso by think.thunk.org with local   (Exim 3.35 #1 (Debian))
	id 19KQ2n-0001fJ-00; Mon, 26 May 2003 18:02:13 -0400
Date: Mon, 26 May 2003 18:02:13 -0400
From: "Theodore Ts'o" <tytso@mit.edu>
To: Anthony Atkielski <anthony@atkielski.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: spam
Message-ID: <20030526220212.GA6254@think>
References: <000501c32253$f6707160$92082b45@a> <093001c322af$60b28800$0a00000a@atkielski.com> <3ED0D8B3.8070303@ehsco.com> <Pine.GSO.4.50.0305251626220.24020-100000@argos.ee.surrey.ac.uk> <3ED120AE.9000306@ehsco.com> <020b01c32353$f73d18e0$0a00000a@atkielski.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <020b01c32353$f73d18e0$0a00000a@atkielski.com>
User-Agent: Mutt/1.5.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, May 26, 2003 at 08:56:43AM +0200, Anthony Atkielski wrote:
> Even at a hundred dollars an hour, the cost of deleting spam each day with
> the delete key (and even at the current rate of hundreds of spam per day) is
> only $2-$3 ... several times cheaper than the daily cost of visiting a
> restroom.

It's a lot more costly than time just to "hit delete".  It's the time
to determine whether it's spam, or something valuable, since the cost
of accidentally deleting something valuable can be very, very costly
indeed.  It's the cost to download mail.  (I'm currently travelling in
Wales, and my internet access is (a) slow, and (b) expensive.)

Tools like Spam Assassin help, but spammers are starting specifically
writing their pitches so that they aren't picked up by spam filters.
To the extent that they are successful, it takes even more valuable
time.

> This being so, the argument that deleting spam is expensive is hard to
> support.  It may be irritating, but it's not costly to delete, any more than
> it is costly to throw junk postal mail in the trash while looking through
> one's daily mail.

Funny, when someone identified the US Postal Address of a spammer, and
subscribed to vast quantities of junk postal mail, said spammer
complained about how it "wasn't fair".... seems he didn't like wading
through vast quantities of junk postal mail in order to find few bits
of postal mail that he cared about.  The really amusing thing was that
he couldn't see the irony of him complaining about getting vast
quantities of junk postal mail, and what he was inflicting on millions
of Internet users.  But then again, sociopaths have problems making
connections such as these....

						- Ted



From owner-ietf@ietf.org  Mon May 26 19:08:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03421
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 19:08:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KQfO-0002rp-HF
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 18:42:06 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KQTA-00010E-R0
	for ietf@asgard.ietf.org; Mon, 26 May 2003 18:29:28 -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 SAA01624
	for <ietf@ietf.org>; Mon, 26 May 2003 18:29:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQRe-0003NW-00
	for ietf@ietf.org; Mon, 26 May 2003 18:27:54 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQRe-0003NT-00
	for ietf@ietf.org; Mon, 26 May 2003 18:27:54 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207773; Mon, 26 May 2003 17:28:54 -0500
Message-ID: <3ED29544.4080002@ehsco.com>
Date: Mon, 26 May 2003 17:29:24 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: ietf@ietf.org
Subject: Re: spam
References: <Pine.LNX.4.44.0305261802010.3699-100000@commander.av8.net>
In-Reply-To: <Pine.LNX.4.44.0305261802010.3699-100000@commander.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/26/2003 5:17 PM Dean Anderson wrote:
> 
> On Mon, 26 May 2003, Eric A. Hall wrote:

>> Perhaps you can provide an example of a law that acts as evidence in
>> favor of your opinion so we can see how this balances out.
> 
> Junk fax law, overturned as being unconstitutional restriction on
> speech.

You keep bringing this up. Please cite. As I said in another message, the
only ruling I know of that would support this was overturned on appeal.

> Anyway, I think commercial speech including spam _could_ be regulated,
> but there so far is no justification for doing so.

There is plenty of justification for it. You are actually arguing that you
don't beleive there is sufficient justification for it, which is a matter
of opinion not proof. You should recognize that you are going to be
outvoted on this opinion.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Mon May 26 19:10:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03569
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 19:10:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KQh4-00037v-53
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 18:43:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KQZF-0002IV-SB
	for ietf@asgard.ietf.org; Mon, 26 May 2003 18:35:45 -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 SAA02153
	for <ietf@ietf.org>; Mon, 26 May 2003 18:35:43 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQXj-0003Wo-00
	for ietf@ietf.org; Mon, 26 May 2003 18:34:11 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQXj-0003Wl-00
	for ietf@ietf.org; Mon, 26 May 2003 18:34:11 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h4QMZfbM005514;
	Mon, 26 May 2003 18:35:41 -0400
Message-Id: <200305262235.h4QMZfbM005514@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Anthony Atkielski <anthony@atkielski.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: spam 
In-Reply-To: Your message of "Mon, 26 May 2003 23:35:04 +0200."
             <005e01c323ce$ab9f3a00$0a00000a@atkielski.com> 
References: <000501c32253$f6707160$92082b45@a> <093001c322af$60b28800$0a00000a@atkielski.com> <3ED0D8B3.8070303@ehsco.com> <Pine.GSO.4.50.0305251626220.24020-100000@argos.ee.surrey.ac.uk> <3ED120AE.9000306@ehsco.com> <020b01c32353$f73d18e0$0a00000a@atkielski.com> <200305261609.h4QG9Ka7012963@turing-police.cc.vt.edu>
            <005e01c323ce$ab9f3a00$0a00000a@atkielski.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1865097415P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 26 May 2003 18:35:41 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1865097415P
Content-Type: text/plain; charset=us-ascii

On Mon, 26 May 2003 23:35:04 +0200, Anthony Atkielski <anthony@atkielski.com>  said:

> It still costs less than having to open a separate text attachment just to
> read someone's message, though.  I won't name names.

Yes, one vendor has an unfortunate inability to properly follow the MIME
spec and drop unrecognized multipart/* to multipart/mixed as required.

Complain to your vendor or use a RFC-compliant MUA.

(And yes, I've verified that the problematic MUA even has problems if
you explicitly give the text/plain part a 'Content-disposition: inline').

--==_Exmh_-1865097415P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+0pa9cC3lWbTT17ARAuV4AKDcazzh8H4agfa7v4d87GV2rPy6awCfRgEQ
gquAoica9zHMA/H8/7qqfgk=
=NL6G
-----END PGP SIGNATURE-----

--==_Exmh_-1865097415P--



From owner-ietf@ietf.org  Mon May 26 19:10:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03649
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 19:10:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KQh4-0003AN-Sy
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 18:43:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KQep-0002mf-Ri
	for ietf@asgard.ietf.org; Mon, 26 May 2003 18:41:31 -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 SAA02327
	for <ietf@ietf.org>; Mon, 26 May 2003 18:41:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQdJ-0003aa-00
	for ietf@ietf.org; Mon, 26 May 2003 18:39:57 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQdI-0003aX-00
	for ietf@ietf.org; Mon, 26 May 2003 18:39:56 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4QMfWHs002789
	for <ietf@ietf.org>; Tue, 27 May 2003 00:41:32 +0200 (CEST)
Message-ID: <010d01c323d7$f492ad60$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <000501c32253$f6707160$92082b45@a> <093001c322af$60b28800$0a00000a@atkielski.com> <3ED0D8B3.8070303@ehsco.com> <Pine.GSO.4.50.0305251626220.24020-100000@argos.ee.surrey.ac.uk> <3ED120AE.9000306@ehsco.com> <020b01c32353$f73d18e0$0a00000a@atkielski.com> <20030526220212.GA6254@think>
Subject: Re: spam
Date: Tue, 27 May 2003 00:41:32 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Theodore writes:

> It's a lot more costly than time just to
> "hit delete".  It's the time to determine
> whether it's spam, or something valuable,
> since the cost of accidentally deleting something
> valuable can be very, very costly indeed.

That requires only a fraction of a second for me.

> It's the cost to download mail. 

Here again, only a fraction of a second.

> I'm currently travelling in Wales, and my
> internet access is (a) slow, and (b) expensive.

I'm at home, and my access is (a) fast and (b) cheap.

The argument of costliness just doesn't hold water.





From owner-ietf@ietf.org  Mon May 26 19:21:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01883
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 18:33:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KQI0-0008Uw-MK
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 18:17:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KQ8O-0004Xk-Kf
	for ietf@asgard.ietf.org; Mon, 26 May 2003 18:08:00 -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 SAA29982
	for <ietf@ietf.org>; Mon, 26 May 2003 18:07:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQ6s-00035D-00
	for ietf@ietf.org; Mon, 26 May 2003 18:06:26 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQ6r-00034l-00
	for ietf@ietf.org; Mon, 26 May 2003 18:06:25 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id RAA25073;
	Mon, 26 May 2003 17:56:20 -0400
Date: Mon, 26 May 2003 17:57:22 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Valdis.Kletnieks@vt.edu
cc: Anthony Atkielski <anthony@atkielski.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: spam 
In-Reply-To: <200305262040.h4QKeUbM004179@turing-police.cc.vt.edu>
Message-ID: <Pine.LNX.4.44.0305261705520.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

One justification is all the dollars that you get for hosting the email
accounts necessary to have 750K messages per day, and the fact that
whatever the costs and scalability issues (which while tricky, reduce your
costs), you are passing them on to the customer, who is still paying $1 or
$2 per month, and you are still making money at this rate.  People pay $10
per month in _taxes_alone_ for their home phone. The cost of spam is
triffling. (actaully, Valdis is at a university, probably isn't directly
billing, but could, and others do).

Another justification is that the commercial mail houses all purchased T1+
network resources, and even small spammers purchased accounts from ISPs
which purchased fiber, and contributed a small amount directly to an
information economy that made all this possible.  The sales made by these
spammers also generated tax revenue and jobs. Congress, and the FTC, and
the Courts favor business because money makes the economy move, and makes
all these things possible. It makes it possible for people to send their
kids to universities, which pay professors, and benefit the social fabric.

Anti-spammers have for years said that spammers are stealing something.
In general, this was never true. Spammers pay the same as everyone else.

One of the things that spammers said in 1998 was that spam saves trees. I
haven't heard this in a while, but I have no doubt they'll probably say it
again, and its probably true.  Lots of big companies want to use spam to
make money, and/or reduce their costs.  People own those companies. People
work for those companies. Government get lots of tax revenue from those
companies. Thats a pretty powerful justification.

Those of us who worked on the internet pre-commercialization can
understand a time when commercial activity was "immoral", and done outside
the internet. But that isn't the case anymore.  You can't simply say
"commercial activity is immoral". But that time is past, and its never
going to come back.  You can't get anywhere unless you understand what the
opponents can say about their activities, and react rationally,
reasonably, and responsibly.

The only real harm I can see, is that spam is annoying. But real, bonafide
commercial spammers are getting better at not sending me email if I ask
them not to. So it seems the annoyance is coming from somewhere else.
Somewhere that isn't commercial, and isn't commercial speech.

		--Dean




From owner-ietf@ietf.org  Mon May 26 19:36:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04301
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 19:36:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KR4M-0005bO-Kq
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 19:07:54 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KQfn-0002vU-IG
	for ietf@asgard.ietf.org; Mon, 26 May 2003 18:42:31 -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 SAA02354
	for <ietf@ietf.org>; Mon, 26 May 2003 18:42:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQeH-0003b9-00
	for ietf@ietf.org; Mon, 26 May 2003 18:40:57 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQeG-0003b1-00
	for ietf@ietf.org; Mon, 26 May 2003 18:40:56 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id SAA29676;
	Mon, 26 May 2003 18:35:28 -0400
Date: Mon, 26 May 2003 18:36:30 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Michel Py <michel@arneill-py.sacramento.ca.us>
cc: IETF Discussion <ietf@ietf.org>
Subject: RE: spam 
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F825@server2000.arneill-py.sacramento.ca.us>
Message-ID: <Pine.LNX.4.44.0305261819160.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Mon, 26 May 2003, Michel Py wrote:


> > 2 Disks make 1 500Meg volume.
>
> By my count 500 Megs is 28 disks @$350 ea which is $10k.
> Plus 4 hot-swap enclosures with RPS @$2.5k ea $10k more.
> Now I need to back it up, takes 3 ultrium drives @ $6k ea is $18k more.
> Backup Exec Raid option: $600
> 2x 64-bit RAID card: $5k
>
> 500 gigs = $45K as of today.

You can probably spend a great deal more, if you shop around.

But that is still dirt cheap, for an ISP handling 400,000 messages per
day, with the capability to store 8 months of email.  Lease on 45K is
about $500/mo. Still much, much less than $1 per month.  Let say we are
going to buy this equipment, and put in the trash after 3 years.  Now we
in the vicinity of $1600/mo. Still much, much less than $1 per month per
user.

		--Dean




From owner-ietf@ietf.org  Mon May 26 19:36:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04343
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 19:36:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KR4M-0005bj-U1
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 19:07:54 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KQgz-00032H-Qu
	for ietf@asgard.ietf.org; Mon, 26 May 2003 18:43:45 -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 SAA02373
	for <ietf@ietf.org>; Mon, 26 May 2003 18:43:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQfT-0003bY-00
	for ietf@ietf.org; Mon, 26 May 2003 18:42:11 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQfS-0003bV-00
	for ietf@ietf.org; Mon, 26 May 2003 18:42:10 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4QMhkHs002806
	for <ietf@ietf.org>; Tue, 27 May 2003 00:43:46 +0200 (CEST)
Message-ID: <012e01c323d8$447237b0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <000501c32253$f6707160$92082b45@a> <093001c322af$60b28800$0a00000a@atkielski.com> <3ED0D8B3.8070303@ehsco.com> <Pine.GSO.4.50.0305251626220.24020-100000@argos.ee.surrey.ac.uk> <3ED120AE.9000306@ehsco.com> <020b01c32353$f73d18e0$0a00000a@atkielski.com> <200305261609.h4QG9Ka7012963@turing-police.cc.vt.edu>            <005e01c323ce$ab9f3a00$0a00000a@atkielski.com> <200305262235.h4QMZfbM005514@turing-police.cc.vt.edu>
Subject: Re: spam 
Date: Tue, 27 May 2003 00:43:46 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Valdis writes:

> Yes, one vendor has an unfortunate inability
> to properly follow the MIME spec and drop
> unrecognized multipart/* to multipart/mixed
> as required.

Only one correspondent sends e-mial with this problem.

> Complain to your vendor or use a RFC-compliant MUA.

No, I have a better idea:  I'll just trash all the messages from the one
correspondent that can't join the mainstream.





From owner-ietf@ietf.org  Mon May 26 19:38:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04565
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 19:38:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KR7g-0006lK-WA
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 19:11:20 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KQpP-0004L8-4g
	for ietf@asgard.ietf.org; Mon, 26 May 2003 18:52:27 -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 SAA02893
	for <ietf@ietf.org>; Mon, 26 May 2003 18:52:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQns-0003ln-00
	for ietf@ietf.org; Mon, 26 May 2003 18:50:52 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KQnr-0003lg-00
	for ietf@ietf.org; Mon, 26 May 2003 18:50:51 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id SAA18060;
	Mon, 26 May 2003 18:49:42 -0400
Date: Mon, 26 May 2003 18:50:43 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
cc: "Eric A. Hall" <ehall@ehsco.com>, <ietf@ietf.org>
Subject: Re: spam 
In-Reply-To: <200305262148.h4QLmlwg003904@syn.hamachi.org>
Message-ID: <Pine.LNX.4.44.0305261839500.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

This site assumes that there 22 million businesses in the US.  According
to the SBA site they quote, "this number may overestimate the number of
firms, as one business may operate more than one taxable entity". With
only 300 million people, that seems a bit exaggerated. Even if 1 in 12
people operated a business, they wouldn't be able to send an email to
every person in the US on every day, certainly not on a 56K dialup, or
residential service line.  The IRS reports that there were 5.7 million
firms with employees.  The vast majority are 1 employee owner/operator
firms, with essentially residential internet service.

So, yes, as the site itself says, "this is a scare tactic". The site also
says:

    "It's time to look at some conservative situations, and come up with
some reasonable numbers".

Conservative, resonable. Indeed!

		--Dean

On Mon, 26 May 2003, Bill Sommerfeld wrote:

> > You have yet to find any compelling grounds on which to limit real
> > commercial speech, and yet to even demonstrate any harms of real
> > commercial speech.
>
> I stumbled across this writeup recently:
>
> http://www.clifto.com/7359.html
>
> ("7359" is the estimated number of messages/day/user if the average
> mailbox were to get one message a month from 1% of US businesses).
>
> 						- Bill
>
>




From owner-ietf@ietf.org  Mon May 26 19:39:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04692
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 19:39:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KRA8-0006zW-AC
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 19:13:52 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KR4G-0005T7-51
	for ietf@asgard.ietf.org; Mon, 26 May 2003 19:07:48 -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 TAA03410
	for <ietf@ietf.org>; Mon, 26 May 2003 19:07:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KR2j-0003vV-00
	for ietf@ietf.org; Mon, 26 May 2003 19:06:13 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KR2j-0003vS-00
	for ietf@ietf.org; Mon, 26 May 2003 19:06:13 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h4QN7jtU026837;
	Mon, 26 May 2003 19:07:45 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h4QN7iWh026834;
	Mon, 26 May 2003 19:07:44 -0400
Date: Mon, 26 May 2003 19:07:44 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200305262307.h4QN7iWh026834@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: spam
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: "Anthony Atkielski" <anthony@atkielski.com>

    > Once you are charging for e-mail, it's only a matter of time before you
    > are charging for everything. Instead of having free access to the
    > entire net for $9 a month, you'll have paying access for $190 in
    > itemized billing each month, depending on exactly what you do and how
    > much you do it.

This is such an incredibly lame argument I shouldn't need to refute it, but
for the benefit of those who actually believe this ludicrous claim, I will
point out that this is akin to saying:

  If toll roads exist, it's only a matter of time before you are charging for
  driving anywhere. Instead of having free access to the entire road network,
  you'll have paying access for $XXX in itemized billing each month,
  depending on exactly what you do and how much you do it.

Needless to say, toll roads exist, but billed road use doesn't.

	Noel



From owner-ietf@ietf.org  Mon May 26 19:40:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04797
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 19:40:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KRVF-0007d1-9L
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 19:35:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KR7F-0006M4-Vu
	for ietf@asgard.ietf.org; Mon, 26 May 2003 19:10:54 -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 TAA03639
	for <ietf@ietf.org>; Mon, 26 May 2003 19:10:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KR5j-0003zj-00
	for ietf@ietf.org; Mon, 26 May 2003 19:09:19 -0400
Received: from portal.hamachi.org ([140.239.227.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KR5i-0003zf-00
	for ietf@ietf.org; Mon, 26 May 2003 19:09:18 -0400
Received: from syn.hamachi.org (localhost [127.0.0.1])
	by portal.hamachi.org (Postfix) with ESMTP
	id AD7E717939; Mon, 26 May 2003 19:10:51 -0400 (EDT)
Received: from syn.hamachi.org (sommerfeld@localhost)
	by syn.hamachi.org (8.12.7+Sun/8.8.8) with ESMTP id h4QNAsVh004366;
	Mon, 26 May 2003 19:10:55 -0400 (EDT)
Message-Id: <200305262310.h4QNAsVh004366@syn.hamachi.org>
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
To: Dean Anderson <dean@av8.com>
Cc: "Eric A. Hall" <ehall@ehsco.com>, ietf@ietf.org
Subject: Re: spam 
In-Reply-To: Your message of "Mon, 26 May 2003 18:50:43 EDT."
             <Pine.LNX.4.44.0305261839500.3699-100000@commander.av8.net> 
Reply-To: sommerfeld@orchard.arlington.ma.us
Date: Mon, 26 May 2003 19:10:54 -0400
Xender: sommerfeld@syn.hamachi.org
Sender: owner-ietf@ietf.org
Precedence: bulk

> Even if 1 in 12 people operated a business, they wouldn't be able to
> send an email to every person in the US on every day, certainly not
> on a 56K dialup, or residential service line.

Why do you think the bulk sends would happen over dialup?  There are
already plenty of spam-for-hire outfits who will happily spam for you.
I get spam advertising them nearly every day.

> The IRS reports that there were 5.7 million firms with employees.
> The vast majority are 1 employee owner/operator firms, with
> essentially residential internet service.

Even if you assume sole proprietorships won't spam, that's only a
reduction by a factor of four.  That only brings you down to 1840
messages/day/mailbox, which is still 100 times more than most people
would be willing to deal with.

						- Bill



From owner-ietf@ietf.org  Mon May 26 19:46:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05014
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 19:46:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KRX5-0008M4-4h
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 19:37:35 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KR7s-0006la-Qo
	for ietf@asgard.ietf.org; Mon, 26 May 2003 19:11:32 -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 TAA03760
	for <ietf@ietf.org>; Mon, 26 May 2003 19:11:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KR6M-000425-00
	for ietf@ietf.org; Mon, 26 May 2003 19:09:58 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KR6L-000422-00
	for ietf@ietf.org; Mon, 26 May 2003 19:09:58 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h4QNBUtU026879;
	Mon, 26 May 2003 19:11:30 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h4QNBTDf026878;
	Mon, 26 May 2003 19:11:29 -0400
Date: Mon, 26 May 2003 19:11:29 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200305262311.h4QNBTDf026878@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: spam
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: Richard Shockey <richard@shockey.us>

    >> The internet is not the street. Someone is selling a product. In order
    >> to sell a product you must be able to reach them. If you can reach
    >> them, you can find a way to deal with them legally.

    > FTC staff randomly looked at about 2000 spam messages collected
    > internally from FTC mail servers and were able to identify that 80% of
    > the SPAM contained phone numbers addresses or other contact data that
    > could be traced to and individual or business domiciled in the United
    > States.

Think this through for a few seconds, eh? As soon as it becomes legally less
viable to operate via spam when you're in the US, people will simply either
i) wash all commmunications through offshore sites which can't be traced back
to the US, or ii) move their entire operations offshore.

	Noel



From owner-ietf@ietf.org  Mon May 26 19:52:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05240
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 19:52:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KRXh-00006d-Fs
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 19:38:13 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KRIS-0007Ap-8J
	for ietf@asgard.ietf.org; Mon, 26 May 2003 19:22:28 -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 TAA04075
	for <ietf@ietf.org>; Mon, 26 May 2003 19:22:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRGv-00046y-00
	for ietf@ietf.org; Mon, 26 May 2003 19:20:53 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRGv-00046v-00
	for ietf@ietf.org; Mon, 26 May 2003 19:20:53 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id TAA28956;
	Mon, 26 May 2003 19:19:58 -0400
Date: Mon, 26 May 2003 19:21:00 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Anthony Atkielski <anthony@atkielski.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: spam (fwd) (edit error on previous)
In-Reply-To: <009b01c323d2$a3c4bdb0$0a00000a@atkielski.com>
Message-ID: <Pine.LNX.4.44.0305261909330.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 27 May 2003, Anthony Atkielski wrote:

> Dean writes:
>
> > Of these types of spam, Type 1 and Type 2
> > can be dealt with by law ...
>
> Not on a worldwide network.  No organization or government has worldwide
> jurisdiction.

They don't need worldwide juridiction.  They have control over products
sold in their jurisdiction, and the transfer of money into and out of
those jurisdictions.  Many countries have extradition treaties.

> > What is unclear is how much of the total spam
> > is due to each of these types.  A lot of the spam
> > that I recieve, and I have kept all this for
> > some time now, appears to be from type 3B.
>
> Almost everything I get seems to be Type 1, although I don't look at it very
> closely.

Perhaps you should look more closely.

> > I note that helllabs.com.ua makes false and
> > misleading claims that relays and proxies are free.
>
> What is false about such claims?

That they are free. First, only the owner of the service can make
definitive statements about the price of the service. False statements
made by others are just that, false.  Newspaper stands and sidewalk vendor
carts are also unsecured, but taking their products without permission or
payment is theft. Telling others that they can take those products without
paying is solicition of a crime at worst, and false advertising and
trademark infringement at best.  Telephone systems can also have open
relay services configured, but it is well established that unuathorized
use is toll fraud.

> > But what protocols can be specified to reduce or
> > eliminate spam?
>
> Almost none.  The problem is that spam is in the eye of the beholder.
> Catching it with machine intelligence is practically impossible.  It's like
> trying to scan messages for sarcasm.

True.


		--Dean




From owner-ietf@ietf.org  Mon May 26 19:52:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05242
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 19:52:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KRX5-0008ND-Mm
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 19:37:35 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KR8l-0006m4-Hn
	for ietf@asgard.ietf.org; Mon, 26 May 2003 19:12:27 -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 TAA03822
	for <ietf@ietf.org>; Mon, 26 May 2003 19:12:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KR7F-00043T-00
	for ietf@ietf.org; Mon, 26 May 2003 19:10:53 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KR7E-00043P-00
	for ietf@ietf.org; Mon, 26 May 2003 19:10:52 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id TAA11731;
	Mon, 26 May 2003 19:07:58 -0400
Date: Mon, 26 May 2003 19:08:49 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: "Eric A. Hall" <ehall@ehsco.com>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <3ED290DC.9060101@ehsco.com>
Message-ID: <Pine.LNX.4.44.0305261855350.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by ietf.org id TAA05242

Ok, I didn't see this, which is current as of 3/21/03, two months ago.

I have asserted that it is possible to regulate commercial speech. There
are conditions that have to be met.

However, the problem with spam is that the cost is so insignificant as to
be immeasurable, so there is no cost shifting, and unlike fax, there is no
definite harm since there is no paper to consume or to run out of.  A spam
ban would have a much tougher time meeting the constitutionality
requirements.

And I note that the junk fax doesn't ban all unsolicited faxes.  Notably,
it doesn't ban political faxes.

And all this is hypothetical, since there is no chance that bonafide
commercial solicited spam will be banned anytime soon.

		--Dean

On Mon, 26 May 2003, Eric A. Hall wrote:

>
> on 5/26/2003 3:31 PM Dean Anderson wrote:
> > Not only is the FTC business friendly, but so is Congress, and the
> > Courts (which struck down the junk fax law).
>
> The only instance I know of where the TCPA was "struck down", the ruling
> was reversed on appeal in the 8th circuit.
>
> http://www.techlawjournal.com/topstories/2003/20030321.asp has a sumamry
>
> http://www.ca8.uscourts.gov/opndir/03/03/022705P.pdf has the opinion
>
>  | We conclude that 47 U.S.C. § 227(b)(1)(C) satisfies the
>  | constitutional test for regulation of commercial speech and thus
>  | withstands First Amendment scrutiny. There is a substantial
>  | governmental interest in protecting the public from the cost
>  | shifting and interference caused by unwanted fax advertisements,
>  | and the means chosen by Congress to address these harms directly
>  | and materially advances the governmental interest. The statute is
>  | also narrowly tailored to create a reasonable fit with its
>  | objective. Accordingly, we reverse the judgment dismissing the
>  | claims asserted under § 227(b)(1)(C) and remand the case to the
>  | district court for further proceedings consistent with this
>  | opinion.
>
> The TCPA has survived in other circuits as well.
>
> standard disclaimer applies, IANAL
>
> --
> Eric A. Hall                                        http://www.ehsco.com/
> Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/
>
>




From owner-ietf@ietf.org  Mon May 26 19:58:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05515
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 19:58:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KRXh-00006t-PC
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 19:38:13 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KRMY-0007Kg-Eg
	for ietf@asgard.ietf.org; Mon, 26 May 2003 19:26:42 -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 TAA04111
	for <ietf@ietf.org>; Mon, 26 May 2003 19:26:39 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRL2-00048M-00
	for ietf@ietf.org; Mon, 26 May 2003 19:25:08 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRL1-00048J-00
	for ietf@ietf.org; Mon, 26 May 2003 19:25:07 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h4QNQcbM006384;
	Mon, 26 May 2003 19:26:38 -0400
Message-Id: <200305262326.h4QNQcbM006384@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Anthony Atkielski <anthony@atkielski.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: spam 
In-Reply-To: Your message of "Tue, 27 May 2003 00:41:32 +0200."
             <010d01c323d7$f492ad60$0a00000a@atkielski.com> 
References: <000501c32253$f6707160$92082b45@a> <093001c322af$60b28800$0a00000a@atkielski.com> <3ED0D8B3.8070303@ehsco.com> <Pine.GSO.4.50.0305251626220.24020-100000@argos.ee.surrey.ac.uk> <3ED120AE.9000306@ehsco.com> <020b01c32353$f73d18e0$0a00000a@atkielski.com> <20030526220212.GA6254@think>
            <010d01c323d7$f492ad60$0a00000a@atkielski.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1855303177P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 26 May 2003 19:26:36 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1855303177P
Content-Type: text/plain; charset=us-ascii

On Tue, 27 May 2003 00:41:32 +0200, Anthony Atkielski <anthony@atkielski.com>  said:
> I'm at home, and my access is (a) fast and (b) cheap.
> 
> The argument of costliness just doesn't hold water.

Maybe for *you* it doesn't hold water, but that doesn't mean that your
experience matches everybody else's.  I'll note that you're not the one who's
trying to get roaming Internet access in Wales like Ted is, or having to find
ways to provision an OC-12 in the more remote parts of Appalachia (we bit the
bullet and started our own long-haul network provider), or having to deal with
what passes for a telco in most of Africa, as some readers almost certainly
are.  You're not having to catch and drop a *billion* spams a day like the
guys at AOL or MSN/Hotmail (my hats off to them - that's quite an engineering
feat).


--==_Exmh_-1855303177P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+0qKrcC3lWbTT17ARAj7IAKD8vdjR3dBfUQWWVEnWmGBfIBbdIgCeODnS
3CZb8fbZ6yPleOY57jq9AQk=
=73bz
-----END PGP SIGNATURE-----

--==_Exmh_-1855303177P--



From owner-ietf@ietf.org  Mon May 26 19:58:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05548
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 19:58:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KRXi-000079-45
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 19:38:14 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KRNI-0007Kt-In
	for ietf@asgard.ietf.org; Mon, 26 May 2003 19:27:28 -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 TAA04133
	for <ietf@ietf.org>; Mon, 26 May 2003 19:27:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRLm-00048i-00
	for ietf@ietf.org; Mon, 26 May 2003 19:25:54 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRLl-00048P-00
	for ietf@ietf.org; Mon, 26 May 2003 19:25:53 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id TAA05108;
	Mon, 26 May 2003 19:22:05 -0400
Date: Mon, 26 May 2003 19:23:01 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Richard Welty <rwelty@averillpark.net>
cc: ietf@ietf.org
Subject: Re[3]: spam
In-Reply-To: <E19KQJK-0007U5-8I@skipper.averillpark.net>
Message-ID: <Pine.LNX.4.44.0305261921480.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

They have been factually misled. Evidence is being provided to the FTC.
That is all I can say right now. More will be said later, though.

		--Dean

On Mon, 26 May 2003, Richard Welty wrote:

> On Mon, 26 May 2003 17:59:49 -0400 (EDT) Dean Anderson <dean@av8.com> wrote:
>
> > Actually, I've been in touch with an attorney at the FTC. It seems they
> > have been factually misled on some issues.
>
> have they been factually misled, or have they simply come to conclusions
> that you don't like?
>
> this was a really useless posting, dean, asserting that the FTC has been
> misled w/o providing a single bit of supporting evidence.
>
> richard
> --
> Richard Welty                                         rwelty@averillpark.net
> Averill Park Networking                                         518-573-7592
>               Unix, Linux, IP Network Engineering, Security
>
>
>
>




From owner-ietf@ietf.org  Mon May 26 20:05:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05962
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 20:05:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KRXj-00007b-7R
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 19:38:15 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KRPi-0007Qm-45
	for ietf@asgard.ietf.org; Mon, 26 May 2003 19:29:58 -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 TAA04183
	for <ietf@ietf.org>; Mon, 26 May 2003 19:29:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KROB-00049D-00
	for ietf@ietf.org; Mon, 26 May 2003 19:28:23 -0400
Received: from [131.227.76.5] (helo=prue.eim.surrey.ac.uk ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KROB-000493-00
	for ietf@ietf.org; Mon, 26 May 2003 19:28:23 -0400
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 19KRPO-0006Jh-00; Tue, 27 May 2003 00:29:38 +0100
Date: Tue, 27 May 2003 00:29:36 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Anthony Atkielski <anthony@atkielski.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: spam
In-Reply-To: <010d01c323d7$f492ad60$0a00000a@atkielski.com>
Message-ID: <Pine.GSO.4.50.0305270022020.8773-100000@artemis.ee.surrey.ac.uk>
References: <000501c32253$f6707160$92082b45@a> <093001c322af$60b28800$0a00000a@atkielski.com>
 <3ED0D8B3.8070303@ehsco.com> <Pine.GSO.4.50.0305251626220.24020-100000@argos.ee.surrey.ac.uk>
 <3ED120AE.9000306@ehsco.com> <020b01c32353$f73d18e0$0a00000a@atkielski.com>
 <20030526220212.GA6254@think> <010d01c323d7$f492ad60$0a00000a@atkielski.com>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-105.6 required=5.5
	tests=AWL,BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,REFERENCES,
	      REPLY_WITH_QUOTES,USER_AGENT_PINE,USER_IN_WHITELIST
	version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
X-Scanner: exiscan *19KRPO-0006Jh-00*64uxkxwNhPU* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 27 May 2003, Anthony Atkielski wrote:

> Theodore writes:
>
> > It's a lot more costly than time just to
> > "hit delete".  It's the time to determine
> > whether it's spam, or something valuable,
> > since the cost of accidentally deleting something
> > valuable can be very, very costly indeed.
>
> That requires only a fraction of a second for me.
>
> > It's the cost to download mail.
>
> Here again, only a fraction of a second.
>
> > I'm currently travelling in Wales, and my
> > internet access is (a) slow, and (b) expensive.
>
> I'm at home, and my access is (a) fast and (b) cheap.

your parents spoil you.

L.

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>



From owner-ietf@ietf.org  Mon May 26 20:10:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06178
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 20:10:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KRdA-0001La-1C
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 19:43:52 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KRX1-0008LI-9Q
	for ietf@asgard.ietf.org; Mon, 26 May 2003 19:37:31 -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 TAA04504
	for <ietf@ietf.org>; Mon, 26 May 2003 19:37:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRVU-0004FV-00
	for ietf@ietf.org; Mon, 26 May 2003 19:35:56 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRVU-0004D4-00
	for ietf@ietf.org; Mon, 26 May 2003 19:35:56 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id TAA22165;
	Mon, 26 May 2003 19:33:58 -0400
Date: Mon, 26 May 2003 19:35:00 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
cc: "Eric A. Hall" <ehall@ehsco.com>, <ietf@ietf.org>
Subject: Re: spam 
In-Reply-To: <200305262310.h4QNAsVh004366@syn.hamachi.org>
Message-ID: <Pine.LNX.4.44.0305261926420.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Mon, 26 May 2003, Bill Sommerfeld wrote:

> > Even if 1 in 12 people operated a business, they wouldn't be able to
> > send an email to every person in the US on every day, certainly not
> > on a 56K dialup, or residential service line.
>
> Why do you think the bulk sends would happen over dialup?  There are
> already plenty of spam-for-hire outfits who will happily spam for you.
> I get spam advertising them nearly every day.

Most individuals in the "22 million" only have dialup.  Most spamhouses
also don't have the capacity to send 7359 * 300 million spams per day.

> > The IRS reports that there were 5.7 million firms with employees.
> > The vast majority are 1 employee owner/operator firms, with
> > essentially residential internet service.
>
> Even if you assume sole proprietorships won't spam, that's only a
> reduction by a factor of four.  That only brings you down to 1840
> messages/day/mailbox, which is still 100 times more than most people
> would be willing to deal with.

I'm not assuming anything of the sort.

I'm asserting that most sole proprietorships don't have (nor will they
ever have) the connectivity required to send 300 million spams per day,
or 3 million spams per day.

SO this 7359.hmtl is nothing other than anti-spammer scare tactics.

Actually, I get about 250 spams per day. All hand filtered, and saved.
(and it still costs me practically nothing) At 1840 per day, I might turn
to more automated methods.

		--Dean




From owner-ietf@ietf.org  Mon May 26 20:19:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06547
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 20:19:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KS0l-0004DI-CI
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 20:08:15 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KRdU-0001Lf-Fo
	for ietf@asgard.ietf.org; Mon, 26 May 2003 19:44:12 -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 TAA04977
	for <ietf@ietf.org>; Mon, 26 May 2003 19:44:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRby-0004OT-00
	for ietf@ietf.org; Mon, 26 May 2003 19:42:38 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRbx-0004OI-00
	for ietf@ietf.org; Mon, 26 May 2003 19:42:37 -0400
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h4QNhS9x008334;
	Mon, 26 May 2003 16:43:28 -0700 (PDT)
Received: (ole@localhost) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) id QAA11144; Mon, 26 May 2003 16:43:28 -0700 (PDT)
X-Authentication-Warning: wells.cisco.com: ole set sender to ole@cisco.com using -f
Date: Mon, 26 May 2003 16:43:28 -0700 (PDT)
From: "Ole J. Jacobsen" <ole@cisco.com>
Reply-To: Ole Jacobsen <ole@cisco.com>
To: Anthony Atkielski <anthony@atkielski.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: spam
In-Reply-To: <010d01c323d7$f492ad60$0a00000a@atkielski.com>
Message-ID: <Pine.HPX.4.44.0305261639350.1870-100000@wells.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Anthony,

So, because YOU have fast access and YOU are sitting at home, "the
argument of costliness just doesn't hold water."

I guess you could make the same argument about many other things, oh say
for example: "you don't need an umbrella, just stay inside when it rains".

Nice logic. Not.

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Tel: +1 408-527-8972   GSM: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj



On Tue, 27 May 2003, Anthony Atkielski wrote:

> Theodore writes:
>
> > It's a lot more costly than time just to
> > "hit delete".  It's the time to determine
> > whether it's spam, or something valuable,
> > since the cost of accidentally deleting something
> > valuable can be very, very costly indeed.
>
> That requires only a fraction of a second for me.
>
> > It's the cost to download mail.
>
> Here again, only a fraction of a second.
>
> > I'm currently travelling in Wales, and my
> > internet access is (a) slow, and (b) expensive.
>
> I'm at home, and my access is (a) fast and (b) cheap.
>
> The argument of costliness just doesn't hold water.
>
>
>




From owner-ietf@ietf.org  Mon May 26 20:24:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06826
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 20:24:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KS6Z-0004jz-0H
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 20:14:15 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KRhQ-0001nR-T4
	for ietf@asgard.ietf.org; Mon, 26 May 2003 19:48:16 -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 TAA05154
	for <ietf@ietf.org>; Mon, 26 May 2003 19:48:13 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRfu-0004SY-00
	for ietf@ietf.org; Mon, 26 May 2003 19:46:42 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRfu-0004SV-00
	for ietf@ietf.org; Mon, 26 May 2003 19:46:42 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h4QNmCbM006813;
	Mon, 26 May 2003 19:48:12 -0400
Message-Id: <200305262348.h4QNmCbM006813@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Anthony Atkielski <anthony@atkielski.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: spam 
In-Reply-To: Your message of "Tue, 27 May 2003 00:43:46 +0200."
             <012e01c323d8$447237b0$0a00000a@atkielski.com> 
References: <000501c32253$f6707160$92082b45@a> <093001c322af$60b28800$0a00000a@atkielski.com> <3ED0D8B3.8070303@ehsco.com> <Pine.GSO.4.50.0305251626220.24020-100000@argos.ee.surrey.ac.uk> <3ED120AE.9000306@ehsco.com> <020b01c32353$f73d18e0$0a00000a@atkielski.com> <200305261609.h4QG9Ka7012963@turing-police.cc.vt.edu> <005e01c323ce$ab9f3a00$0a00000a@atkielski.com> <200305262235.h4QMZfbM005514@turing-police.cc.vt.edu>
            <012e01c323d8$447237b0$0a00000a@atkielski.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1852959625P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 26 May 2003 19:48:11 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1852959625P
Content-Type: text/plain; charset=us-ascii

On Tue, 27 May 2003 00:43:46 +0200, Anthony Atkielski <anthony@atkielski.com>  said:

> No, I have a better idea:  I'll just trash all the messages from the one
> correspondent that can't join the mainstream.

So much for "be liberal in what you accept". :)

--==_Exmh_-1852959625P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+0qe7cC3lWbTT17ARAhDPAJ49G/sjUBy1jj+uHf0ypF8yHmTX6wCePcvi
rU/WoF1K3FhWeTRdVh+m7jo=
=xCOF
-----END PGP SIGNATURE-----

--==_Exmh_-1852959625P--



From owner-ietf@ietf.org  Mon May 26 20:25:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06933
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 20:24:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KS6Z-0004kQ-Ny
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 20:14:15 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KRi4-0001pW-H6
	for ietf@asgard.ietf.org; Mon, 26 May 2003 19:48:56 -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 TAA05180
	for <ietf@ietf.org>; Mon, 26 May 2003 19:48:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRgY-0004T8-00
	for ietf@ietf.org; Mon, 26 May 2003 19:47:22 -0400
Received: from [208.184.79.11] (helo=clint.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRgX-0004Sb-00
	for ietf@ietf.org; Mon, 26 May 2003 19:47:21 -0400
Received: from bbprime (208.184.79.253.songbird.com [208.184.79.253] (may be forged))
	by clint.songbird.com (8.11.6/8.11.6) with ESMTP id h4QNp4i03262;
	Mon, 26 May 2003 16:51:04 -0700
Date: Mon, 26 May 2003 16:48:18 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <8233046778.20030526164818@brandenburg.com>
To: Richard Shockey <richard@shockey.us>
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: spam
In-Reply-To: <5.2.0.9.2.20030526174731.0295cbe8@shockey.us>
References: <Pine.GSO.4.50.0305261357040.28832-100000@argos.ee.surrey.ac.uk>
 <5.2.0.9.2.20030526174731.0295cbe8@shockey.us>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Richard,

>>The internet is not the street. Someone is selling a product. In order to
>>sell a product you must be able to reach them. If you can reach them, you
>>can find a way to deal with them legally.

RS> Excellent point .. at the FTC Workshop on SPAM this was pointed out in
RS> considerable detail. ...

RS> That the mail was set off shore was not the issue... you attack the problem
RS> at its source ..the business that use SPAM.  Follow the money!


Perhaps we heard different presentations.

The bottom line I heard was that the effort to track down spammers was
far too large to be practical.

We were regaled with a story of corporate layering, 18 pre-trial
subpoenas, and various other obfuscations (by the spammers, not the
state enforcement folk) and an eventual result of only USD 10,000 in
fines.

And then it was pointed out that government enforcers are often faced
with minor trade-offs such as going after spammers, versus going after
drug dealers and terrorists.

To me the message was very clear:  Legal recourse is not likely to be a
primary agent of change against spamming, even when the spammers are
ostensibly within an accountable jurisdiction.

And there are those based elsewhere...


d/

ps. perhaps folks haven't noticed that a) many spammers who want money
really are in other countries and they just can't be bothered to limit
their mailing to the "right" country, and b) many spammers do not want
money are are either selling religion or the like, or are simply playing
pranks.

--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Mon May 26 20:31:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07195
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 20:31:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KS6a-0004kl-13
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 20:14:16 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KRlh-0001qj-QM
	for ietf@asgard.ietf.org; Mon, 26 May 2003 19:52:41 -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 TAA05220
	for <ietf@ietf.org>; Mon, 26 May 2003 19:52:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRkB-0004Tk-00
	for ietf@ietf.org; Mon, 26 May 2003 19:51:07 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRkA-0004Th-00
	for ietf@ietf.org; Mon, 26 May 2003 19:51:06 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4QNqZHs003433
	for <ietf@ietf.org>; Tue, 27 May 2003 01:52:35 +0200 (CEST)
Message-ID: <016101c323e1$e1ae5be0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.44.0305261909330.3699-100000@commander.av8.net>
Subject: Re: spam (fwd) (edit error on previous)
Date: Tue, 27 May 2003 01:52:35 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dean writes:

> Many countries have extradition treaties.

For certain crimes.  Spamming is not likely to qualify.

> Perhaps you should look more closely.

Why?  It's spam.

> That they are free.

But they _are_ free.

> Telephone systems can also have open relay services
> configured, but it is well established that unuathorized
> use is toll fraud.

I'm not aware of any similar jurisprudence having been established for the
Internet.





From owner-ietf@ietf.org  Mon May 26 20:32:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07245
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 20:32:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KS6a-0004mD-HD
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 20:14:16 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KRmn-0002WK-95
	for ietf@asgard.ietf.org; Mon, 26 May 2003 19:53:49 -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 TAA05334
	for <ietf@ietf.org>; Mon, 26 May 2003 19:53:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRlG-0004Vn-00
	for ietf@ietf.org; Mon, 26 May 2003 19:52:14 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRlF-0004VQ-00
	for ietf@ietf.org; Mon, 26 May 2003 19:52:13 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4QNrhHs003450
	for <ietf@ietf.org>; Tue, 27 May 2003 01:53:43 +0200 (CEST)
Message-ID: <017301c323e2$0a4968b0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <000501c32253$f6707160$92082b45@a> <093001c322af$60b28800$0a00000a@atkielski.com> <3ED0D8B3.8070303@ehsco.com> <Pine.GSO.4.50.0305251626220.24020-100000@argos.ee.surrey.ac.uk> <3ED120AE.9000306@ehsco.com> <020b01c32353$f73d18e0$0a00000a@atkielski.com> <20030526220212.GA6254@think> <010d01c323d7$f492ad60$0a00000a@atkielski.com> <Pine.GSO.4.50.0305270022020.8773-100000@artemis.ee.surrey.ac.uk>
Subject: Re: spam
Date: Tue, 27 May 2003 01:53:43 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

LLoyd writes:

> your parents spoil you.

They say just the opposite.



From owner-ietf@ietf.org  Mon May 26 20:38:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07544
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 20:38:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KS6b-0004oy-As
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 20:14:17 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KRnv-0002Zm-3E
	for ietf@asgard.ietf.org; Mon, 26 May 2003 19:54:59 -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 TAA05481
	for <ietf@ietf.org>; Mon, 26 May 2003 19:54:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRmO-0004YU-00
	for ietf@ietf.org; Mon, 26 May 2003 19:53:24 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRmO-0004YR-00
	for ietf@ietf.org; Mon, 26 May 2003 19:53:24 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4QNsuHs003464
	for <ietf@ietf.org>; Tue, 27 May 2003 01:54:56 +0200 (CEST)
Message-ID: <017e01c323e2$35b65a30$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <200305262307.h4QN7iWh026834@ginger.lcs.mit.edu>
Subject: Re: spam
Date: Tue, 27 May 2003 01:54:56 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

J. Noel writes:

> This is such an incredibly lame argument I
> shouldn't need to refute it ...

Famous last words.

> Needless to say, toll roads exist, but billed road
> use doesn't.

Some truckers might disagree.



From owner-ietf@ietf.org  Mon May 26 20:46:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07919
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 20:46:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KS6c-0004r3-75
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 20:14:18 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KRrj-0003OK-51
	for ietf@asgard.ietf.org; Mon, 26 May 2003 19:58:55 -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 TAA05639
	for <ietf@ietf.org>; Mon, 26 May 2003 19:58:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRqC-0004ba-00
	for ietf@ietf.org; Mon, 26 May 2003 19:57:20 -0400
Received: from pengo.systems.pipex.net ([62.241.160.193])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRqB-0004Zj-00
	for ietf@ietf.org; Mon, 26 May 2003 19:57:19 -0400
Received: from ieee.org (userdd211.dsl.pipex.com [62.190.227.211])
	by pengo.systems.pipex.net (Postfix) with ESMTP
	id 85B6A4C000A7; Tue, 27 May 2003 00:58:15 +0100 (BST)
Message-ID: <3ED2A9DB.B72701CC@ieee.org>
Date: Tue, 27 May 2003 00:57:15 +0100
From: Dominic Pinto <dominic.pinto@ieee.org>
Reply-To: dominic.pinto@ieee.org
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: ietf@ietf.org
Subject: Re: spam
References: <200305262311.h4QNBTDf026878@ginger.lcs.mit.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

"J. Noel Chiappa" wrote:
> 
>     > From: Richard Shockey <richard@shockey.us>
> 
>     >> The internet is not the street. Someone is selling a product. In order
>     >> to sell a product you must be able to reach them. If you can reach
>     >> them, you can find a way to deal with them legally.
> 
>     > FTC staff randomly looked at about 2000 spam messages collected
>     > internally from FTC mail servers and were able to identify that 80% of
>     > the SPAM contained phone numbers addresses or other contact data that
>     > could be traced to and individual or business domiciled in the United
>     > States.
> 
> Think this through for a few seconds, eh? As soon as it becomes legally less
> viable to operate via spam when you're in the US, people will simply either
> i) wash all commmunications through offshore sites which can't be traced back
> to the US, or ii) move their entire operations offshore.
> 

That was certainly the case for premium rate services via the phone
network - especially ii). Not an exact analogy, and needed 'tolerant' or
sympathetic local telcos / governments (think Netherlands Antilles)
......



From owner-ietf@ietf.org  Mon May 26 20:46:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07921
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 20:46:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KS6d-0004tt-3h
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 20:14:19 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KRul-0003RE-U3
	for ietf@asgard.ietf.org; Mon, 26 May 2003 20:02:03 -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 UAA05864
	for <ietf@ietf.org>; Mon, 26 May 2003 20:02:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRtF-0004eX-00
	for ietf@ietf.org; Mon, 26 May 2003 20:00:29 -0400
Received: from tomts15.bellnexxia.net ([209.226.175.3] helo=tomts15-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRtE-0004eT-00
	for ietf@ietf.org; Mon, 26 May 2003 20:00:28 -0400
Received: from yahoo.com ([65.93.189.197]) by tomts15-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030527000201.FFUU24631.tomts15-srv.bellnexxia.net@yahoo.com>;
          Mon, 26 May 2003 20:02:01 -0400
Date: Mon, 26 May 2003 20:01:59 -0400
Subject: Re: spam
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "IETF Discussion" <ietf@ietf.org>
To: "Anthony Atkielski" <anthony@atkielski.com>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <010d01c323d7$f492ad60$0a00000a@atkielski.com>
Message-Id: <70275C55-8FD6-11D7-98C2-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

How about the cost of legitimate emails that get filtered and never 
read. Not everyone scans the list to check for false positives.

simon

On Monday, May 26, 2003, at 06:41  PM, Anthony Atkielski wrote:

>> I'm currently travelling in Wales, and my
>> internet access is (a) slow, and (b) expensive.
>
> I'm at home, and my access is (a) fast and (b) cheap.
>
> The argument of costliness just doesn't hold water.
>

--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Mon May 26 20:52:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08302
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 20:52:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KS6d-0004tz-EU
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 20:14:19 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KRum-0003RG-OH
	for ietf@asgard.ietf.org; Mon, 26 May 2003 20:02:04 -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 UAA05868
	for <ietf@ietf.org>; Mon, 26 May 2003 20:02:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRtG-0004ee-00
	for ietf@ietf.org; Mon, 26 May 2003 20:00:30 -0400
Received: from 75.5.33.65.cfl.rr.com ([65.33.5.75] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRtF-0004eV-00
	for ietf@ietf.org; Mon, 26 May 2003 20:00:29 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19K7tf-0005jm-00; Sun, 25 May 2003 22:39:35 -0400
Date: Sun, 25 May 2003 22:39:31 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Dean Anderson <dean@av8.com>
cc: Bill Cunningham <billc44@citynet.net>, <ietf@ietf.org>,
        <watha@monitortan.com>, <phil@whirlycott.com>
Subject: Re: spam
In-Reply-To: <Pine.LNX.4.44.0305261533010.3699-100000@commander.av8.net>
Message-ID: <Pine.LNX.4.44.0305252236200.22045-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 26 May 2003, Dean Anderson wrote:

>
>
> On Sun, 25 May 2003, shogunx wrote:
>
> > Dean,
> >
> > >
> > > [1] SPEWS has attemtped to avoid prosecution and legal responsibility by
> > > remaining completely anonymous. ORBZ.ORG was criminally investigated for
> > > crashing the City of Battle Creek's computer system. The City dropped the
> > > investigation after ORBZ announced it would end operations.  However,
> > > simultaneously or before the City's announcement, ORBZ operator Ian
> > > Gulliver registered DSBL.ORG with a Brazilian address. Quite obviously, he
> > > had no intention of halting operations, but merely to disguise their
> > > jurisdiction.
> > >
> >
> > sounds like ORBZ 1 Battle Creeek 0
>
> ORBZ got away with a deception, yes.  Ian Gulliver is not the first
> con-artist to talk his way out of a jam with the cops and won't be the
> last.

I'm not saying anyone was right or wrong in this instance.  I'm just
calling the score.


>
> > > [2] Even though Kevin Mitnick was on the FBI's most wanted list, the FBI
> > > was unable to track him down. Only after one of his victims became
> > > involved, was Mitnick finally located and arrested.
> > >
> >
> > Kevin gets locked away for years without even being CHARGED, and suddenly
> > he has victims?  He was the victim.
>
> He was not locked away for any years without being charged. While he may
> also have been victimized in some respects due the difficulty and
> complexity of his trial, he was by no means innocent. He brought it all on
> himself.  He was a self-described con-artist, and violated numerous civil
> and criminal statutes. He had no regard to civil or criminal laws, and
> therefore couldn't be allowed to roam about society unsupervised. He had
> many victims, as he recently admitted at a talk I attended. What he did
> was wrong in a big way. He has completely repudiated his earlier
> activities.
>
> Those who see Mitnick as representative of the hacker ethic don't really
> understand the hacker ethic. Hackers are not dishonest.  Hackers share,
> they do not steal.  Hackers ask politely, and invent for themselves what
> they are refused.  Hackers do not coerce or extort anything.
>

I am not challenging Mitnick's guilt or innocence.  I am challenging the
method in which the situation was dealt with.

Scott



> 		--Dean
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81




From owner-ietf@ietf.org  Mon May 26 20:52:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08325
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 20:52:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KSDy-0005Xo-3J
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 20:21:54 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KS6T-0004jk-RB
	for ietf@asgard.ietf.org; Mon, 26 May 2003 20:14:09 -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 UAA06395
	for <ietf@ietf.org>; Mon, 26 May 2003 20:14:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KS4x-0004oQ-00
	for ietf@ietf.org; Mon, 26 May 2003 20:12:35 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KS4w-0004oN-00
	for ietf@ietf.org; Mon, 26 May 2003 20:12:35 -0400
Content-class: urn:content-classes:message
Subject: RE: spam 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Mon, 26 May 2003 17:13:58 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F826@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: spam 
Thread-Index: AcMj4ruTEy+igx0fTO+o+aEgPqQXVQAAOiSw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: <Valdis.Kletnieks@vt.edu>
Cc: "IETF Discussion" <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id UAA08325

>> Anthony Atkielski wrote:
>> I'm at home, and my access is (a) fast and (b) cheap.

> Lloyd Wood wrote:
> your parents spoil you.

I think you're right Lloyd. Also Anthony must have all the time in the
world to delete spam.

>> The argument of costliness just doesn't hold water.

> Valdis Kletnieks wrote:
> Maybe for *you* it doesn't hold water, but that doesn't mean that
> your experience matches everybody else's.

Well said, also what about my GPRS charges when I sync my phone/PDA and
half of it is junk? 

Michel.




From owner-ietf@ietf.org  Mon May 26 20:55:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08598
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 20:55:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KSee-0000iC-VQ
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 20:49:28 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KS7i-0004xc-3F
	for ietf@asgard.ietf.org; Mon, 26 May 2003 20:15:26 -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 UAA06423
	for <ietf@ietf.org>; Mon, 26 May 2003 20:15:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KS6B-0004ov-00
	for ietf@ietf.org; Mon, 26 May 2003 20:13:51 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KS6A-0004os-00
	for ietf@ietf.org; Mon, 26 May 2003 20:13:51 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4R0FNHs003673
	for <ietf@ietf.org>; Tue, 27 May 2003 02:15:23 +0200 (CEST)
Message-ID: <01bf01c323e5$11292d20$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <70275C55-8FD6-11D7-98C2-000393414368@yahoo.com>
Subject: Re: spam
Date: Tue, 27 May 2003 02:15:23 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Simon asks:

> How about the cost of legitimate emails that
> get filtered and never read. 

That's why I don't filter.



From owner-ietf@ietf.org  Mon May 26 21:03:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08943
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 21:03:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KSei-0000pi-3C
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 20:49:32 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KSDi-0005Ub-Rd
	for ietf@asgard.ietf.org; Mon, 26 May 2003 20:21:38 -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 UAA06724
	for <ietf@ietf.org>; Mon, 26 May 2003 20:21:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KSCC-0004uZ-00
	for ietf@ietf.org; Mon, 26 May 2003 20:20:04 -0400
Received: from tomts15.bellnexxia.net ([209.226.175.3] helo=tomts15-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KSCB-0004uW-00
	for ietf@ietf.org; Mon, 26 May 2003 20:20:03 -0400
Received: from yahoo.com ([65.93.189.197]) by tomts15-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030527002136.FYWZ24631.tomts15-srv.bellnexxia.net@yahoo.com>;
          Mon, 26 May 2003 20:21:36 -0400
Date: Mon, 26 May 2003 20:21:33 -0400
Subject: Re: spam 
Content-Type: text/plain; delsp=yes; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: IETF Discussion <ietf@ietf.org>
To: Valdis.Kletnieks@vt.edu
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <200305262326.h4QNQcbM006384@turing-police.cc.vt.edu>
Message-Id: <2BAE4FA7-8FD9-11D7-98C2-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Monday, May 26, 2003, at 07:26  PM, Valdis.Kletnieks@vt.edu wrote:

> or having to deal with
> what passes for a telco in most of Africa, as some readers almost  
> certainly
> are.

I recently found myself bit by spam because the AFNOG mailing list  
operates on a server that uses DSBL. It's only place my mail bounces as  
spam (so far...) (I use bell sympatico in canada). This is just a  
practical need for them as the total bandwidth in and out of Africa is  
on the order of ~ 2Gbps [1]. So that spam is very expensive there.

simon

[1] mid 2002,  
http://www.telegeography.com/resources/statistics/internet/ 
intereg_internet_band.html although potentially it could improve  
dramatically, if the existing SAT-3/WASC/SAFE cable is fully tapped (it  
has 120Gbps capacity




From owner-ietf@ietf.org  Mon May 26 21:10:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09194
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 21:10:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KSen-0000u7-ID
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 20:49:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KSGw-00063l-Pk
	for ietf@asgard.ietf.org; Mon, 26 May 2003 20:24:58 -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 UAA06915
	for <ietf@ietf.org>; Mon, 26 May 2003 20:24:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KSFQ-0004x9-00
	for ietf@ietf.org; Mon, 26 May 2003 20:23:24 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KSFP-0004x6-00
	for ietf@ietf.org; Mon, 26 May 2003 20:23:23 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207804; Mon, 26 May 2003 19:24:24 -0500
Message-ID: <3ED2B056.2000203@ehsco.com>
Date: Mon, 26 May 2003 19:24:54 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: ietf@ietf.org
Subject: Re: spam
References: <Pine.LNX.4.44.0305261855350.3699-100000@commander.av8.net>
In-Reply-To: <Pine.LNX.4.44.0305261855350.3699-100000@commander.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/26/2003 6:08 PM Dean Anderson wrote:

> However, the problem with spam is that the cost is so insignificant as 
> to be immeasurable, so there is no cost shifting,

The facts demonstrated are that (1) there is real cost for bandwidth, (2)
there is a real cost for equipment, and (3) there is a real cost for
staffing, all due to spam. Whether you consider these facts to be
sufficient either cumulatively or in detail is a matter of opinion. The
existing laws support my opinion, not yours.

> and unlike fax, there is no definite harm since there is no paper to
> consume or to run out of.

There are plenty of examples of crashed and clogged servers due to
resource consumption. But that's not important, either. The TCPA addresses
other concerns including lack of availability due to excessive use, and
isn't limited to resource consumption issues.

> And I note that the junk fax doesn't ban all unsolicited faxes. 
> Notably, it doesn't ban political faxes.

My proposal left room for exceptions as well.

> And all this is hypothetical, since there is no chance that bonafide 
> commercial solicited spam will be banned anytime soon.

I haven't claimed that we need to ban solicited mail.

I think you've made your opinion pretty clear at this point. When you find
some new data that supports your opinion, let us know.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Mon May 26 21:15:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09398
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 21:15:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KSeo-0000xk-R1
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 20:49:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KSLo-0006Pz-Is
	for ietf@asgard.ietf.org; Mon, 26 May 2003 20:30:00 -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 UAA07117
	for <ietf@ietf.org>; Mon, 26 May 2003 20:29:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KSKH-00051k-00
	for ietf@ietf.org; Mon, 26 May 2003 20:28:25 -0400
Received: from u24.gpu114.samsung.co.kr ([203.254.224.24] helo=mailout1.samsung.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KSKG-00051Y-00
	for ietf@ietf.org; Mon, 26 May 2003 20:28:24 -0400
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.05 (built Nov  6 2002))
 id <0HFI005JDS07M5@mailout1.samsung.com> for ietf@ietf.org; Tue,
 27 May 2003 09:28:55 +0900 (KST)
Received: from ep_mmp1 (localhost [127.0.0.1])
 by mailout1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.05 (built Nov 6
 2002)) with ESMTP id <0HFI00KIRRWHBR@mailout1.samsung.com> for ietf@ietf.org;
 Tue, 27 May 2003 09:26:44 +0900 (KST)
Received: from daniel7209 ([168.219.203.183])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.05 (built Nov  6
 2002)) with ESMTPA id <0HFI00ISVRWF2A@mmp1.samsung.com> for ietf@ietf.org;
 Tue, 27 May 2003 09:26:39 +0900 (KST)
Date: Tue, 27 May 2003 09:25:49 +0900
From: Soohong Daniel Park <soohong.park@samsung.com>
Subject: RE: Simple Internet Protocol, Again
In-reply-to: <200305261441.XAA03510@necom830.hpcl.titech.ac.jp>
To: "'Masataka Ohta'" <mohta@necom830.hpcl.titech.ac.jp>, ietf@ietf.org
Cc: Soohong Daniel Park <soohong.park@samsung.com>
Message-id: <001101c323e6$8608cdc0$b7cbdba8@daniel7209>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

Hi Ohta.

I've looked over your draft quickly, however I don't see 
what applicability statement is possible.


	Daniel
	Mobile Platform Laboratory, SAMSUNG Electronics




-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of
Masataka Ohta
Sent: Monday, May 26, 2003 11:42 PM
To: ietf@ietf.org
Subject: Simple Internet Protocol, Again


Attached is a very rough draft to make IPv6 more deployable.

Don't I forget to forbid some of the so many useless features
of IPv6?

Comments are welcome.

						Masataka Ohta
---





INTERNET DRAFT                                                   M. Ohta
draft-ohta-sipa-00.txt                     Tokyo Institute of Technology
                                                                May 2003

                    Simple Internet Protocol, Again

Status of this Memo

   This document is an Internet-Draft and is subject to all provisions
   of Section 10 of RFC2026.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet- Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Abstract

   IPv6 has failed to be deployed partly because of its complexity.

   IPv6 mostly is a descendant of SIP (Simple Internet Protocol) but has
   fatally bloated merging with other proposals and trying to make IPv6
   has better functionality than IPv4, which makes IPv6 unnecessarily
   complex and, thus, worse than IPv4.

   SIPA (Simple Internet Protocol, Again) is a proposal attempting to
   restore simplicity to IPv6 sticking to the real world operational
   requirements for the IPv4 Internet to make IPv6 more acceptable to
   ISPs and end users.

1. Introduction

   IPv6 has failed to be deployed partly because of its complexity.

   It is a complexity of not only coding but also operation.  It should
   be noted that, even though running code may be widely available, it
   is not because IPv6 is so simple that implementors enjoyed coding



M. Ohta               Expires on November 25, 2003              [Page 1]

INTERNET DRAFT      Simple Internet Protocol, Again             May 2003


   (which was why, in good old days, running code principle was a good
   measure of protocol quality) but because governments and vendors put
   large amount of effort and money on it.  Still, among so many IPv4
   ISPs, few operate it and ratio of IPv6 end users to IPv4 ones are
   even smaller.

   Deployment is an operational issue and IPv6 has failed and will
   continue to be failing to be deployed.

   IPv6 mostly is a descendant of SIP (Simple Internet Protocol) but has
   fatally bloated merging with other proposals and trying to make IPv6
   have better functionality than IPv4, which makes IPv6 unnecessarily
   complex and, thus, worse than IPv4.

   SIPA (Simple Internet Protocol, Again) is a proposal attempting to
   restore simplicity to IPv6 sticking to the real world operational
   requirements for the IPv4 Internet, to make IPv6 more acceptable to
   ISPs and end users.

   With SIPA, IPv6 should become easy to code and operate.

   In this memo, legacy IPv6 is called CIP (Complex IP), "the Internet"
   means one in the real world, that is, the IPv4 Internet, and a router
   is a host.

2. Requirements

   The original requirement for CIP was:

      Support large number of hosts large enough to make the IPv6
      Internet for everyone.

   which resulted in bloated CIP.

   The followings are the additional requirements to SIPA based on the
   operational reality of the Internet.

      Suppress the number of global routing table entries even if
      everyone are multihomed to the IPv6 Internet.

      Make packet format compatible to CIP to make SIPA work over legacy
      routers.

      Remove all the features of CIP against the end to end principle.

      Remove all the features of CIP not present in IPv4. No
      applications on the Internet use them.




M. Ohta               Expires on November 25, 2003              [Page 2]

INTERNET DRAFT      Simple Internet Protocol, Again             May 2003


      Remove all the features of CIP not used in IPv4 Internet. No
      applications on the Internet use them.

      Remove all the features of CIP not useful in IPv4 Internet. No
      applications on the Internet need them.

3. Removed Features

   The following subsections list features of IPv6 removed to make IPv6
   simpler and more deployable.

3.1 IP Header Options

   Optional headers are not used on the Internet and is forbidden.
   Except for an optional fragmentation header, which is used on the
   Internet, a transport header follows immediately after an IP header.

   Options visible to routers is a direct violation of the end to end
   principle and just harmful.

   Note that use of a routing header by MIPv6 is architecturally wrong,
   as a home agent is, like mail relays, an end system that it should be
   an destination option.

   In addition, except for a fragmentation header, destination option is
   still forbidden. It should be implemented at protocol (see section
   3.3, for example) or transport level.

3.2 ToS & Flow Labels

   ToS & flow labels are forbidden. RSVP is far less deployed than IPv6.
   Even if it is deployed, removal of IP header options makes it easy
   for routers access port numbers or SPI (see section 3.3) that flow
   labels are not unnecessary.

   While the field for ToS & flow labels is large enough to hold
   fragmentation information (because MTU is large) not as an optional
   header, it makes SIPA not compatible to CIP.

   So, for possible future extension (such as that ECN is proven to be
   useful over the Internet), the field should contain 0 at the source
   and ignored by routers and the destination.

3.3 IPSEC

   ESP is purely optional and should be implemented as Protocol 50. SPI
   works as port numbers for resource reservation (if any).  AH is
   forbidden because its functionality overridden by ESP and its SPI is



M. Ohta               Expires on November 25, 2003              [Page 3]

INTERNET DRAFT      Simple Internet Protocol, Again             May 2003


   not located at port number part.

3.4 Path MTU Discoverly

   Path MTU discoverly is forbidden.  It often does not work over the
   Internet for various reasons.  As the MTU of the Internet is mostly
   1500 that minimum MTU of 1280 is good enough.

   Routers are encouraged to silently drop packets lager than 1280 byte
   without generating ICMP.

3.5 Stateless Autoconfiguration

   IPv6 specific stateless autoconfiguration is ignored.  Use DHCP.

   All the possible autoconfiguration can be (and is already, for most
   of the case) implemented with DHCP over the Internet.

   The remaining autoconfiguration features may work in an isolated
   private LAN but is not meaningful over the Internet.  Note, for
   example, that both dentists' offices and cars have preconfigured
   locks and keys.

   Issues on autoconfiguration in an isolated private LAN may still be
   solved, but in a way not affecting the development of the Internet
   protocol nor, hopefully, IETF.

3.6 Automatic Renumbering

   Automatic renumbering of IP addresses of DNS glue is ignored.

   On the Internet, automatic renumbering is trivially easy, as long as
   domain names, not raw IP addresses, are used to designate hosts.
   However, automatic renumbering of DNS glue is impossible, because
   relationship between DNS servers has nothing to do with ISP topology.

3.7 Hosts and Routers

   It is a direct violation of the end to end principle to assume
   intermediate systems intelligent and end systems dumb.  Routers are
   hosts relay packets between multiple interfaces, thus, actively
   engages in generating routing tables. As has been the tradition of
   early days of the Internet, hosts with single interface are still
   expected to listen to IGP (e.g. routed -q). Note that DHCP can tell
   hosts which IGP to use. Note also that global routing table is
   assumed to be small.

3.8 Neighbor Discovery



M. Ohta               Expires on November 25, 2003              [Page 4]

INTERNET DRAFT      Simple Internet Protocol, Again             May 2003


   Neighbor discovery is not used on the Internet and is forbidden.  It
   has hopelessly bloated, partly because of a failed attempt to support
   ATM (IPv6 thought multicast over ATM were easy) and partly because of
   another failed attempt to support stateless autoconfiguration.

   As for address resolution, the original purpose of ND, except for the
   last hop, address resolution information for next hop routers become
   available from IGP exchange. In other cases, use ARP or let hosts
   speak IGP.

3.9 Jumbograms

   Jumbograms are not used on the Internet and is forbidden.  Super
   computers today are massively parallel ones that it has enough scalar
   power to handle streams of 64KB of packets.

3.10 Link & Site Local Address

   Link and site local address is not used on the Internet and is
   forbidden.

   Note that a network behind NAT is not a part of the Internet. One may
   still use NAT with IPv6, but it has nothing to do with IPv4 or IPv6
   specification.

4. Other Restriction to CIP

   To ease implementations, a router can forward packets to the next hop
   by looking at upper 64 bits of an destination address only.
   Multicast address format should be reconsidered accordingly.

   A host can accept packets to it by looking at lower 64 bits of an
   destination address only.

5. Remaining Works

   Multi6 WG is working on site multihoming of IPv6, at least
   theoretically.

   However, as there can be limited number of ASes operated at TLAs,
   support for NLA level ASes multihomed to TLA level ASes must be
   discussed somewhere.

   Mobility must be tightly integrated with multihoming, as both treats
   multiple IP addresses of a host, that current specifications on MIPv6
   must be ignored.

6. Security Considerations



M. Ohta               Expires on November 25, 2003              [Page 5]

INTERNET DRAFT      Simple Internet Protocol, Again             May 2003


   IPSEC sucks.

7. Author's Address

   Masataka Ohta
   Graduate School of Information Science and Engineering
   Tokyo Institute of Technology
   2-12-1, O-okayama, Meguro-ku, Tokyo 152-8552, JAPAN

   Phone: +81-3-5734-3299
   Fax: +81-3-5734-3299
   EMail: mohta@necom830.hpcl.titech.ac.jp







































M. Ohta               Expires on November 25, 2003              [Page 6]






From owner-ietf@ietf.org  Mon May 26 21:20:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09691
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 21:20:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KSiC-0001wK-6R
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 20:53:08 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KSch-0000aQ-Fz
	for ietf@asgard.ietf.org; Mon, 26 May 2003 20:47:27 -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 UAA08008
	for <ietf@ietf.org>; Mon, 26 May 2003 20:47:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KSbB-0005Hk-00
	for ietf@ietf.org; Mon, 26 May 2003 20:45:53 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KSbA-0005Gb-00
	for ietf@ietf.org; Mon, 26 May 2003 20:45:52 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id UAA04551;
	Mon, 26 May 2003 20:43:28 -0400
Date: Mon, 26 May 2003 20:44:20 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: "Eric A. Hall" <ehall@ehsco.com>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <3ED2B056.2000203@ehsco.com>
Message-ID: <Pine.LNX.4.44.0305262032290.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 26 May 2003, Eric A. Hall wrote:

>
> on 5/26/2003 6:08 PM Dean Anderson wrote:
>
> > However, the problem with spam is that the cost is so insignificant as
> > to be immeasurable, so there is no cost shifting,
>
> The facts demonstrated are that (1) there is real cost for bandwidth, (2)
> there is a real cost for equipment, and (3) there is a real cost for
> staffing, all due to spam. Whether you consider these facts to be
> sufficient either cumulatively or in detail is a matter of opinion.

Certainly. However, in the case of Junk Faxes, there were definite costs
to each fax, and definite harms to running out of paper. This isn't the
case with spam.

> The existing laws support my opinion, not yours.

I don't think so.  The existing laws, and laws pending in Congress don't
ban spam.  I don't think there is any chance that any such proprosal will
be brought up, or passed.  If you think otherwise, please let me know why.
Bill text would be good.

> > and unlike fax, there is no definite harm since there is no paper to
> > consume or to run out of.
>
> There are plenty of examples of crashed and clogged servers due to
> resource consumption. But that's not important, either. The TCPA addresses
> other concerns including lack of availability due to excessive use, and
> isn't limited to resource consumption issues.

These examples are not due to either Type 1 or Type 2 spam.  They are due
to Type 3 activity.  In my personal experience, Type 3 activity has only
been due to the activity of anti-spammers trying to "teach me a lesson",
or as in the case with ORBZ, due to illegal scanning. Other anti-spammers
have attempted to crash mailservers from other people they didn't like.
There may be others besides anti-spammers, with other agendas, but this is
not a justification for banning Type 1 spam.  Nor will it ever be.

> > And I note that the junk fax doesn't ban all unsolicited faxes.
> > Notably, it doesn't ban political faxes.
>
> My proposal left room for exceptions as well.
>
> > And all this is hypothetical, since there is no chance that bonafide
> > commercial solicited spam will be banned anytime soon.
>
> I haven't claimed that we need to ban solicited mail.

But you are.  Perhaps I haven't seen your proposal detail.

> I think you've made your opinion pretty clear at this point. When you find
> some new data that supports your opinion, let us know.

Heh. Likewise.

		--Dean




From owner-ietf@ietf.org  Mon May 26 21:26:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07546
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 20:38:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KS6b-0004p4-IN
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 20:14:17 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KRp5-0002fa-LS
	for ietf@asgard.ietf.org; Mon, 26 May 2003 19:56:11 -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 TAA05492
	for <ietf@ietf.org>; Mon, 26 May 2003 19:56:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRnZ-0004Z9-00
	for ietf@ietf.org; Mon, 26 May 2003 19:54:37 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KRnY-0004Z6-00
	for ietf@ietf.org; Mon, 26 May 2003 19:54:36 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4QNu9Hs003480
	for <ietf@ietf.org>; Tue, 27 May 2003 01:56:09 +0200 (CEST)
Message-ID: <018501c323e2$60e9c520$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.HPX.4.44.0305261639350.1870-100000@wells.cisco.com>
Subject: Re: spam
Date: Tue, 27 May 2003 01:56:09 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Ole writes:

> So, because YOU have fast access and YOU are
> sitting at home, "the argument of costliness
> just doesn't hold water."

I'm just applying the same method as my interlocutor, who apparently
believes that if he is constrained to use dial-up while travelling, than
this makes spam costly for the whole world.





From owner-ietf@ietf.org  Mon May 26 21:34:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10158
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 21:34:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KT6B-0004bi-O8
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 21:17:55 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KSmG-0002Mc-0n
	for ietf@asgard.ietf.org; Mon, 26 May 2003 20:57:20 -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 UAA08725
	for <ietf@ietf.org>; Mon, 26 May 2003 20:57:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KSkj-0005VG-00
	for ietf@ietf.org; Mon, 26 May 2003 20:55:45 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KSkj-0005VD-00
	for ietf@ietf.org; Mon, 26 May 2003 20:55:45 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207817; Mon, 26 May 2003 19:56:41 -0500
Message-ID: <3ED2B7E6.7090006@ehsco.com>
Date: Mon, 26 May 2003 19:57:10 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: ietf@ietf.org
Subject: Re: spam
References: <Pine.LNX.4.44.0305262032290.3699-100000@commander.av8.net>
In-Reply-To: <Pine.LNX.4.44.0305262032290.3699-100000@commander.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/26/2003 7:44 PM Dean Anderson wrote:
> On Mon, 26 May 2003, Eric A. Hall wrote:

>>>And all this is hypothetical, since there is no chance that bonafide
>>>commercial solicited spam will be banned anytime soon.
>>
>>I haven't claimed that we need to ban solicited mail.
> 
> But you are.  Perhaps I haven't seen your proposal detail.

The outline in <3ED1AC83.1080208@ehsco.com> made no mention of banning it,
and specifically says "recent prior relationship is okay".

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Mon May 26 21:34:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10157
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 21:34:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KT6C-0004bo-1s
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 21:17:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KSmO-0002Me-Ak
	for ietf@asgard.ietf.org; Mon, 26 May 2003 20:57:28 -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 UAA08732
	for <ietf@ietf.org>; Mon, 26 May 2003 20:57:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KSkr-0005VQ-00
	for ietf@ietf.org; Mon, 26 May 2003 20:55:53 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KSkr-0005VA-00
	for ietf@ietf.org; Mon, 26 May 2003 20:55:53 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id UAA21736;
	Mon, 26 May 2003 20:52:05 -0400
Date: Mon, 26 May 2003 20:53:03 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Anthony Atkielski <anthony@atkielski.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: spam (fwd) (edit error on previous)
In-Reply-To: <016101c323e1$e1ae5be0$0a00000a@atkielski.com>
Message-ID: <Pine.LNX.4.44.0305262047150.3699-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Tue, 27 May 2003, Anthony Atkielski wrote:

> Dean writes:
>
> > Many countries have extradition treaties.
>
> For certain crimes.  Spamming is not likely to qualify.
>
> > Perhaps you should look more closely.
>
> Why?  It's spam.

I can see you have a goal of limiting Type 1 spam, using the harms of Type
2 and Type 3 spam. This effort is doomed to fail.

> > That they are free.
>
> But they _are_ free.

Sorry. You are wrong.  Only I get to set prices on my services. You don't
get to tell others false prices.

> > Telephone systems can also have open relay services
> > configured, but it is well established that unuathorized
> > use is toll fraud.
>
> I'm not aware of any similar jurisprudence having been established for the
> Internet.

Fraud is common law, which applies to the internet.  After $5000, it
becomes a federal felony. State laws have other requirements.

		--Dean




From owner-ietf@ietf.org  Mon May 26 21:56:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10987
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 21:56:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KTcG-0007Ab-TV
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 21:51:04 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KTYp-00071C-W0
	for ietf@asgard.ietf.org; Mon, 26 May 2003 21:47:32 -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 VAA10748
	for <ietf@ietf.org>; Mon, 26 May 2003 21:47:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KTXJ-00067A-00
	for ietf@ietf.org; Mon, 26 May 2003 21:45:57 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KTXI-000677-00
	for ietf@ietf.org; Mon, 26 May 2003 21:45:56 -0400
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200305270135.KAA02345@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id KAA02345; Tue, 27 May 2003 10:34:56 +0859
Subject: Re: Simple Internet Protocol, Again
In-Reply-To: <001101c323e6$8608cdc0$b7cbdba8@daniel7209> from Soohong Daniel
 Park at "May 27, 2003 09:25:49 am"
To: Soohong Daniel Park <soohong.park@samsung.com>
Date: Tue, 27 May 2003 10:34:56 +0859 ()
CC: ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-ietf@ietf.org
Precedence: bulk

Daniel;

> I've looked over your draft quickly, however I don't see 
> what applicability statement is possible.

It is a reality check agaist people dreaming of magical
deployment of IPv6.

It can also be a proposal to shutdown activities to further
complicate IPv6.

						Masataka Ohta



From owner-ietf@ietf.org  Mon May 26 22:01:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09400
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 21:15:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KSiB-0001tk-4B
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 20:53:07 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KSW0-0008CG-Sb
	for ietf@asgard.ietf.org; Mon, 26 May 2003 20:40:32 -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 UAA07767
	for <ietf@ietf.org>; Mon, 26 May 2003 20:40:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KSUU-0005DU-00
	for ietf@ietf.org; Mon, 26 May 2003 20:38:58 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KSUU-0005DR-00
	for ietf@ietf.org; Mon, 26 May 2003 20:38:58 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207813 for ietf@ietf.org; Mon, 26 May 2003 19:39:58 -0500
Message-ID: <3ED2B3FC.2020309@ehsco.com>
Date: Mon, 26 May 2003 19:40:28 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: spam
References: <Pine.GSO.4.50.0305261357040.28832-100000@argos.ee.surrey.ac.uk> <5.2.0.9.2.20030526174731.0295cbe8@shockey.us> <8233046778.20030526164818@brandenburg.com>
In-Reply-To: <8233046778.20030526164818@brandenburg.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/26/2003 6:48 PM Dave Crocker wrote:

> To me the message was very clear:  Legal recourse is not likely to be a
> primary agent of change against spamming, even when the spammers are 
> ostensibly within an accountable jurisdiction.

Good arguments for private right-of-action too.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Mon May 26 22:06:16 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11322
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 22:06:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KTmr-0007pd-QL
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 22:02:01 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KTiR-0007fH-FZ
	for ietf@asgard.ietf.org; Mon, 26 May 2003 21:57:27 -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 VAA11086
	for <ietf@ietf.org>; Mon, 26 May 2003 21:57:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KTgu-0006CK-00
	for ietf@ietf.org; Mon, 26 May 2003 21:55:53 -0400
Received: from pop017pub.verizon.net ([206.46.170.210] helo=pop017.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KTgu-0006BA-00
	for ietf@ietf.org; Mon, 26 May 2003 21:55:52 -0400
Received: from earthlink.net ([4.65.81.213]) by pop017.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030527015654.KRDF27254.pop017.verizon.net@earthlink.net>;
          Mon, 26 May 2003 20:56:54 -0500
Message-ID: <3ED2C508.8E2CFA44@earthlink.net>
Date: Mon, 26 May 2003 18:53:12 -0700
From: Peter Deutsch <pdeutsch@earthlink.net>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Anthony Atkielski <anthony@atkielski.com>
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: spam (fwd) (edit error on previous)
References: <Pine.LNX.4.44.0305261909330.3699-100000@commander.av8.net> <016101c323e1$e1ae5be0$0a00000a@atkielski.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at pop017.verizon.net from [4.65.81.213] at Mon, 26 May 2003 20:56:54 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

g'day,

Anthony Atkielski wrote:
...
> > Telephone systems can also have open relay services
> > configured, but it is well established that unuathorized
> > use is toll fraud.
> 
> I'm not aware of any similar jurisprudence having been established for the
> Internet.

Oh puuleez.

In Canada there is a Criminal Code offense known as something like
"unauthorized access to a computer system" (sorry for not having the
exact term, but it's been a while). A few years ago I helped prosecute a
case of illegal access onto a university machine under this provision,
and during the research phase was told by the RCMP folks I was working
with that having login prompts, warning messages, etc made it easier to
prosecute, but was not a requirement. Basically, it's a crime in Canada
to use somebody else's compute cycles without permission so what we had
to do was document access and attest that it was not authorized, they
then traced phone records to show corresponding use of modems on the
home line at the same time. The RCMP then got a search warrant, picked
up the perpetrators for questioning and searched their machine for
incriminating files. In that case, they pled out, but as Yodo would say
"guilty they were, conviction it was".

The case we prosecuted turned out to be a small group of kids breaking
into compute hosts, but from what I was told I would think you should be
able to use the same provision against spam relayers, since the key
element was the unauthorized use of compute cycles, not what they did
with the cycles. For those willing to invest some time and energy then
this could be a good starting point in that country, and perhaps a
suitable point of departure for various lawmakers looking at what could
be done in their own countries. After all, since we're gathering
analogies, it doesn't matter if I leave the keys in my car, that still
doesn't give you the right to take it for a joyride.

BTW, those who think SPAM is "too cheap to meter" need to look at the
total costs involved in providing services, including cost of staff and
all the hidden opportunity costs. My kids' school pays a part time
sysadmin who in turn makes use of a couple of technically literate
parents to help him with various chores as he's still learning his
craft. We've collectively spent many hours educating him to the issues
and he has spent hours trying to reduce the impact of SPAMers bombarding
the school mail host. I don't have a firm number, but it's a measurable
percentage of the total admin time over this past year, which translates
to other things the school didn't get because they don't have infinite
admin bandwidth. Also, since the school requires a certain amount of
volunteer time from each family (or a corresponding hourly fee) the
school has definitely suffered a loss in other stuff I might have done
for them with the finite amount of time I give them.

Put another way, gas may be cheap or expensive, but it's only one of the
costs involved in operating a motor vehicle...


			- peterd


-- 
---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software


             "I'm no stranger to sarcasm, Sir..."

                               - Red versus Blue

---------------------------------------------------------------------



From owner-ietf@ietf.org  Mon May 26 22:06:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09690
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 21:20:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KSiB-0001tz-DT
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 20:53:07 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KSXB-0008CZ-2G
	for ietf@asgard.ietf.org; Mon, 26 May 2003 20:41:45 -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 UAA07792
	for <ietf@ietf.org>; Mon, 26 May 2003 20:41:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KSVe-0005Dx-00
	for ietf@ietf.org; Mon, 26 May 2003 20:40:10 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KSVe-0005Dd-00
	for ietf@ietf.org; Mon, 26 May 2003 20:40:10 -0400
Content-class: urn:content-classes:message
Subject: RE: spam
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Mon, 26 May 2003 17:41:34 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F5067137@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: spam
Thread-Index: AcMj6GEyqReimZEfQ/yikN44llxTegAAAnIQ
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "IETF Discussion" <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA09690

So, I have not heard any replies. If hitting delete does not cost
anything, who pays for my GPRS bill when I sync my phone/PDA and it's
all junk?

Let's see. Anthony maybe?

Michel.




From owner-ietf@ietf.org  Mon May 26 22:57:49 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12167
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 22:57:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KUGi-0000kF-BN
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 22:32:52 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KUGG-0000bq-G3
	for ietf@asgard.ietf.org; Mon, 26 May 2003 22:32:24 -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 WAA11782
	for <ietf@ietf.org>; Mon, 26 May 2003 22:32:22 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KUEj-0006Oe-00
	for ietf@ietf.org; Mon, 26 May 2003 22:30:49 -0400
Received: from h80ad26c3.async.vt.edu ([128.173.38.195] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KUEi-0006Ob-00
	for ietf@ietf.org; Mon, 26 May 2003 22:30:48 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h4R2WFJ2002333;
	Mon, 26 May 2003 22:32:15 -0400
Message-Id: <200305270232.h4R2WFJ2002333@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: pdeutsch@earthlink.net
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: spam (fwd) (edit error on previous) 
In-Reply-To: Your message of "Mon, 26 May 2003 18:53:12 PDT."
             <3ED2C508.8E2CFA44@earthlink.net> 
References: <Pine.LNX.4.44.0305261909330.3699-100000@commander.av8.net> <016101c323e1$e1ae5be0$0a00000a@atkielski.com>
            <3ED2C508.8E2CFA44@earthlink.net>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-960667546P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 26 May 2003 22:32:14 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-960667546P
Content-Type: text/plain; charset=us-ascii

On Mon, 26 May 2003 18:53:12 PDT, Peter Deutsch said:

> The case we prosecuted turned out to be a small group of kids breaking
> into compute hosts, but from what I was told I would think you should be
> able to use the same provision against spam relayers, since the key
> element was the unauthorized use of compute cycles, not what they did
> with the cycles.

IANAL by any means, but I suspect that the owner of an open relay would have
a hard time demonstrating unauthorized use of cycles to relay mail *through
an open relay*.  Now if the spammer actively *bypassed* a security feature
in order to relay the mail, that would be different, as it would indicate
that they knew it was unauthorized...

--==_Exmh_-960667546P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+0s4ucC3lWbTT17ARAp4SAJsEWXVocwiUCBN7TNSaa/5vOjURDACdFT3x
uDM0r88ftmM4XUvVb6DqZTI=
=gryv
-----END PGP SIGNATURE-----

--==_Exmh_-960667546P--



From owner-ietf@ietf.org  Mon May 26 23:49:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12996
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 May 2003 23:49:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KVHb-0002qf-FZ
	for ietf-list@asgard.ietf.org; Mon, 26 May 2003 23:37:51 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KVCx-0002iT-1F
	for ietf@asgard.ietf.org; Mon, 26 May 2003 23:33:03 -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 XAA12754
	for <ietf@ietf.org>; Mon, 26 May 2003 23:33:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KVBQ-0006gd-00
	for ietf@ietf.org; Mon, 26 May 2003 23:31:28 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KVBP-0006gD-00
	for ietf@ietf.org; Mon, 26 May 2003 23:31:27 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id A5D671396A; Tue, 27 May 2003 03:32:30 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: spam
References: <00aa01c323d3$58562ca0$0a00000a@atkielski.com>
From: Paul Vixie <vixie@vix.com>
Date: 27 May 2003 03:32:30 +0000
In-Reply-To: <00aa01c323d3$58562ca0$0a00000a@atkielski.com>
Message-ID: <g3k7cduks1.fsf@sa.vix.com>
Lines: 65
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

warning, i'm answering an obvious troll from an obvious spammer.  hit D now.

anthony@atkielski.com ("Anthony Atkielski") writes:

> Once you are charging for e-mail, it's only a matter of time before you
> are charging for everything.  Instead of having free access to the entire
> net for $9 a month, you'll have paying access for $190 in itemized
> billing each month, depending on exactly what you do and how much you do
> it.  And it will all be recorded somewhere, too, in case anyone wants to
> look at it to see if you're a suspcious character.

you're describing a fairly desireable state of affairs.  many folks would
happily pay more for a commercial-free non-subsidized spam-free e-mail feed.

oops!  my t1 costs me $552 per month in pac bell service fees.  so maybe i'm
already expecting a "premium channel" since nobody is subsidizing my costs.

> I'll just delete the spam when I receive it.  It's an annoyance, not a
> crisis.

how nice for you.  here's the report of spam that's reached me and had to
be deleted in the last 15 days:

	lartomatic=# SELECT DATE(entered),COUNT(*) FROM spam
	             WHERE entered>=(NOW()-'15 days'::INTERVAL)
	             GROUP BY DATE(entered) ORDER BY DATE(entered);
	    date    | count 
	------------+-------
	 2003-05-12 |  1868
	 2003-05-13 |  2345
	 2003-05-14 |  1122
	 2003-05-15 |   902
	 2003-05-16 |   822
	 2003-05-17 |   912
	 2003-05-18 |   818
	 2003-05-19 |  1022
	 2003-05-20 |   927
	 2003-05-21 |   757
	 2003-05-22 |   811
	 2003-05-23 |   760
	 2003-05-24 |  1486
	 2003-05-25 |  1295
	 2003-05-26 |   836
	 2003-05-27 |   123
	(16 rows)

note that the 27th isn't done yet, it'll be over 1000 by 0000GMT tomorrow.
but wait, there's more.  above is the number of times i "just hit delete".
here's the count of mail i rejected due to various blackhole lists i use:

        may 20  8435
        may 21  7956
        may 22  7534
        mat 23  8111
        may 24  14868
        may 25  9171
        may 26  10262
        may 27	1236

note that this is just my home server, at work it's much much worse.

you guys can "just hit delete" all you want, but for me, nothing beats
the right to be left alone.
-- 
Paul Vixie



From owner-ietf@ietf.org  Tue May 27 00:22:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13632
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 00:22:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KVqk-00048Y-1V
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 00:14:10 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KVhI-0003ll-E8
	for ietf@asgard.ietf.org; Tue, 27 May 2003 00:04:24 -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 AAA13399
	for <ietf@ietf.org>; Tue, 27 May 2003 00:04:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KVfl-0006qj-00
	for ietf@ietf.org; Tue, 27 May 2003 00:02:49 -0400
Received: from zydeco.netbusters.com ([66.92.86.178])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KVfl-0006qg-00
	for ietf@ietf.org; Tue, 27 May 2003 00:02:49 -0400
Received: by zydeco.netbusters.com (Postfix, from userid 513)
	id 6428EB6401; Tue, 27 May 2003 04:04:22 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
	by zydeco.netbusters.com (Postfix) with ESMTP id 60F537EC1C
	for <ietf@ietf.org>; Tue, 27 May 2003 00:04:22 -0400 (EDT)
Date: Tue, 27 May 2003 00:04:22 -0400 (EDT)
From: Donald Eastlake 3rd <dee3@torque.pothole.com>
X-X-Sender: dee3@zydeco.netbusters.com
To: ietf@ietf.org
Subject: Re: Last Call: IP over MIME to Proposed Standard
In-Reply-To: <3ED15063.F33C480B@earthlink.net>
Message-ID: <Pine.LNX.4.44.0305252017150.7154-100000@zydeco.netbusters.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi,

On Sun, 25 May 2003, Peter Deutsch wrote:

> Date: Sun, 25 May 2003 16:23:15 -0700
> From: Peter Deutsch <pdeutsch@earthlink.net>
> Subject: Re: Last Call: IP over MIME to Proposed Standard
> 
> g'day,
> 
> Dave Crocker wrote:
> ...
> > Also:  We have a jillion MIME types.  Why make a big deal out of this
> > one?  What is the damage that is of concern?
> 
> Maybe you didn't pick up on it, but Keith did write:
> 
> # 2. the Introduction recommends use of NAT, which is nonstandard and
> # known to often be a harmful practice.  
> 
> Seems obvious to me - Keith smells a NAT rat trying to get its nose
> under the IETF tent flap, and is on the warpath again....  ;-)

I have only myself to blame for not being more specific in the draft.  
A likely reason you might want to use NAT technology is because things
are already screwed up, with duplicate addresses at both ends of a
tunnel, due to the pre-existing use of NATs.

> 				- peterd

Thanks,
Donald
======================================================================
 Donald E. Eastlake 3rd                       dee3@torque.pothole.com
 155 Beaver Street              +1-508-634-2066(h) +1-508-851-8280(w)
 Milford, MA 01757 USA                   Donald.Eastlake@motorola.com




From owner-ietf@ietf.org  Tue May 27 00:31:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14148
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 00:31:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KVqk-00048e-Bb
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 00:14:10 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KViT-0003lo-4r
	for ietf@asgard.ietf.org; Tue, 27 May 2003 00:05:37 -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 AAA13414
	for <ietf@ietf.org>; Tue, 27 May 2003 00:05:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KVgw-0006qw-00
	for ietf@ietf.org; Tue, 27 May 2003 00:04:02 -0400
Received: from 75.5.33.65.cfl.rr.com ([65.33.5.75] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KVgv-0006qt-00
	for ietf@ietf.org; Tue, 27 May 2003 00:04:02 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19KBh5-0005qC-00; Mon, 26 May 2003 02:42:51 -0400
Date: Mon, 26 May 2003 02:42:48 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Paul Vixie <vixie@vix.com>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <g3k7cduks1.fsf@sa.vix.com>
Message-ID: <Pine.LNX.4.44.0305260236390.22446-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Paul,

>
> you guys can "just hit delete" all you want, but for me, nothing beats
> the right to be left alone.

thats the price of genius, it appears.  the stroger your mind, the less
time you will have to use it for what you want, and greater are the number
who will try to take advantage of you for it.  can someone drop me off
on the next small unabandoned island.  i won't be needing any supplies
after that either.


> --
> Paul Vixie
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81





From owner-ietf@ietf.org  Tue May 27 00:44:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14455
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 00:44:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KWBt-0005Pw-TV
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 00:36:01 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KW6s-0004ta-Eb
	for ietf@asgard.ietf.org; Tue, 27 May 2003 00:30:50 -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 AAA14084
	for <ietf@ietf.org>; Tue, 27 May 2003 00:30:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KW5L-000719-00
	for ietf@ietf.org; Tue, 27 May 2003 00:29:15 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KW5K-00070S-00
	for ietf@ietf.org; Tue, 27 May 2003 00:29:15 -0400
Content-class: urn:content-classes:message
Subject: RE: spam
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Mon, 26 May 2003 21:30:39 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F827@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: spam
Thread-Index: AcMkAxz00k7zwHvoT32+nFTYTxcuNQAA1URw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Paul Vixie" <vixie@vix.com>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id AAA14455

> Paul Vixie wrote:
> warning, i'm answering an obvious troll from an obvious spammer.
> hit D now.

Yeah I think we should work on a system to ban obvious spammers from
IETF lists. Maybe we should also ban people that are so full of it that
they could double as a sceptic tank such as the ones that try to convey
the idea that handling spam has no cost.

Paul, I'm curious: why are you wasting your time with this? Any
withdrawals from not fighting it on a daily basis?


> oops!  my t1 costs me $552 per month in pac bell service fees.
> so maybe i'm already expecting a "premium channel" since nobody
> is subsidizing my costs.

But you do have a "premium channel". Do you realize that your connection
is 50 times faster than a dial-up so you are entitled to receive 50
times more spam than mere mortals? I think you don't realize what you
are missing: did you know for example that you could enhance your
breasts by 2 cup sizes? What a fascinating thought :-)

Michel.




From owner-ietf@ietf.org  Tue May 27 01:48:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16009
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 01:48:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KX9k-0007kg-K9
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 01:37:52 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KX5r-0007Yy-In
	for ietf@asgard.ietf.org; Tue, 27 May 2003 01:33:51 -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 BAA15545
	for <ietf@ietf.org>; Tue, 27 May 2003 01:33:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KX4K-0007Rk-00
	for ietf@ietf.org; Tue, 27 May 2003 01:32:16 -0400
Received: from out004pub.verizon.net ([206.46.170.142] helo=out004.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KX4J-0007Rb-00
	for ietf@ietf.org; Tue, 27 May 2003 01:32:16 -0400
Received: from earthlink.net ([4.65.81.213]) by out004.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030527053319.JRJQ28930.out004.verizon.net@earthlink.net>;
          Tue, 27 May 2003 00:33:19 -0500
Message-ID: <3ED2F7C1.1DADAFF0@earthlink.net>
Date: Mon, 26 May 2003 22:29:37 -0700
From: Peter Deutsch <pdeutsch@earthlink.net>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Valdis.Kletnieks@vt.edu
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: spam (fwd) (edit error on previous)
References: <Pine.LNX.4.44.0305261909330.3699-100000@commander.av8.net> <016101c323e1$e1ae5be0$0a00000a@atkielski.com>
	            <3ED2C508.8E2CFA44@earthlink.net> <200305270232.h4R2WFJ2002333@turing-police.cc.vt.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out004.verizon.net from [4.65.81.213] at Tue, 27 May 2003 00:33:18 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Valdis.Kletnieks@vt.edu wrote:
> 
> On Mon, 26 May 2003 18:53:12 PDT, Peter Deutsch said:
> 
> > The case we prosecuted turned out to be a small group of kids breaking
> > into compute hosts, but from what I was told I would think you should be
> > able to use the same provision against spam relayers, since the key
> > element was the unauthorized use of compute cycles, not what they did
> > with the cycles.
> 
> IANAL by any means, but I suspect that the owner of an open relay would have
> a hard time demonstrating unauthorized use of cycles to relay mail *through
> an open relay*.  Now if the spammer actively *bypassed* a security feature
> in order to relay the mail, that would be different, as it would indicate
> that they knew it was unauthorized...

Exaxtly, so you don't leave it open. Then, the only folks who would be
using you as a relay would be a) folks you've authorized to do so. By
definition the folks who are doing so without your authorization, would
be breaking the law and we have an existance proof that this stuff is
quite traceable and quite prosecutable. 

As a bonus, the law they would be breaking isn't one that must, in the
U.S. context, stand up to arguments about it supressing free speech and
so on. And I have no trouble with this, since you have a right to say
what you want, but I have a right not to listen, nor am I responsible
for providing you with a soapbox and megaphone...


				- peterd




-- 
---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software


                        "Bungle..."
               "That's an 'i', you idiot..."
                  "Oh, right. 'Bingle..."

                            - Red versus Blue...

---------------------------------------------------------------------



From owner-ietf@ietf.org  Tue May 27 01:56:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16343
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 01:56:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KXKw-0008NM-EU
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 01:49:26 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KXAM-0007ku-BU
	for ietf@asgard.ietf.org; Tue, 27 May 2003 01:38:30 -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 BAA15590
	for <ietf@ietf.org>; Tue, 27 May 2003 01:38:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KX8l-0007T5-00
	for ietf@ietf.org; Tue, 27 May 2003 01:36:51 -0400
Received: from cust-smtp1.radiolinja.fi ([213.161.33.208])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KX8l-0007T2-00
	for ietf@ietf.org; Tue, 27 May 2003 01:36:51 -0400
Received: from EMCL (rl045112.radiolinja.net [213.161.45.112])
	by cust-smtp1.radiolinja.fi (Postfix) with SMTP
	id 21DD840006; Tue, 27 May 2003 08:38:16 +0300 (EEST)
From: "=?UTF-8?Q?John_Loughney?=" <john.loughney@kolumbus.fi>
To: <anthony@atkielski.com>, <ietf@ietf.org>
Subject: =?UTF-8?Q?Re:_spam?=
Date: Tue, 27 May 2003 08:34:15 +0000
Message-Id: <1054024455447>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
X-Mailer: EMCL v2.14
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id BAA16343

Hi all,

Costly-ness can be factor of jurisdiction. Many places in the world do not have access to broadband. For many, receiving spam is both a monetary expense & a time expense. Also, when the ratio of spam vs. valid mail become high, the utility of email shrinks.

John 
Theodore writes:

> It's a lot more costly than time just to
> "hit delete".  It's the time to determine
> whether it's spam, or something valuable,
> since the cost of accidentally deleting something
> valuable can be very, very costly indeed.

That requires only a fraction of a second for me.

> It's the cost to download mail. 

Here again, only a fraction of a second.

> I'm currently travelling in Wales, and my
> internet access is (a) slow, and (b) expensive.

I'm at home, and my access is (a) fast and (b) cheap.

The argument of costliness just doesn't hold water.







From owner-ietf@ietf.org  Tue May 27 02:24:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28968
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 02:24:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KXck-0003u1-K6
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 02:07:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KXY1-0001yY-35
	for ietf@asgard.ietf.org; Tue, 27 May 2003 02:02: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 CAA19690
	for <ietf@ietf.org>; Tue, 27 May 2003 02:02:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KXWU-0007mV-00
	for ietf@ietf.org; Tue, 27 May 2003 02:01:22 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KXWT-0007lx-00
	for ietf@ietf.org; Tue, 27 May 2003 02:01:21 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id D85AC1396A; Tue, 27 May 2003 06:02:24 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: spam
References: <963621801C6D3E4A9CF454A1972AE8F504F827@server2000.arneill-py.sacramento.ca.us>
From: Paul Vixie <vixie@vix.com>
Date: 27 May 2003 06:02:24 +0000
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F827@server2000.arneill-py.sacramento.ca.us>
Message-ID: <g3fzn1udu7.fsf@sa.vix.com>
Lines: 26
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

michel@arneill-py.sacramento.ca.us ("Michel Py") writes:

> Paul, I'm curious: why are you wasting your time with this? Any
> withdrawals from not fighting it on a daily basis?

because several years ago when iesg commissioned a wg to study the spam
issue and decide whether ietf had a role, the carefully worded answer was
"no".  i thought this answer was short-sighted or wrong-headed or both.

c'mon guys & dolls, smtp and the model behind/beneath it are failing to
address the need for universal batch communication.  we fixed the encoding
problems (trying to fit things into a 990-by-7 box was hard without mime)
and it only took four and a half years of bitchfesting and the results have
been nothing less than spectacular (in that i don't get uuencoded tarballs
from nextstep users any more.)

on april 28 of this year, aol/microsoft/yahoo publically teamed up to fight
spam (since statistically speaking, it is universally launched by their
collective customers and aimed at their collective customers.)  see
http://www.nwfusion.com/news/2003/0428aolmsya.html for the announcement.
does anyone here think this will solve the problem for anybody, even the
customers of those three customers?

i'm wasting my time because i want this problem looked at more broadly.
-- 
Paul Vixie



From owner-ietf@ietf.org  Tue May 27 02:30:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29217
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 02:30:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KXrH-0007fz-4H
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 02:22:51 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KXlR-0006Ea-O7
	for ietf@asgard.ietf.org; Tue, 27 May 2003 02:16:49 -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 CAA28565
	for <ietf@ietf.org>; Tue, 27 May 2003 02:16:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KXju-00009H-00
	for ietf@ietf.org; Tue, 27 May 2003 02:15:14 -0400
Received: from bws10.bridgewatersystems.com ([216.113.7.10] helo=exch01.bridgewatersys.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KXju-000082-00
	for ietf@ietf.org; Tue, 27 May 2003 02:15:14 -0400
Received: by exch01.bridgewatersys.com with Internet Mail Service (5.5.2653.19)
	id <LM45320T>; Tue, 27 May 2003 02:16:18 -0400
Message-ID: <F17FB067A86B2D488382C923C532EAA746EC4C@exch01.bridgewatersys.com>
From: Avi Lior <avi@bridgewatersystems.com>
To: "'Dean Anderson'" <dean@av8.com>,
        "'Valdis.Kletnieks@vt.edu'"
	 <Valdis.Kletnieks@vt.edu>
Cc: "'Anthony Atkielski'" <anthony@atkielski.com>,
        "'IETF Discussion'"
	 <ietf@ietf.org>
Subject: RE: spam 
Date: Tue, 27 May 2003 02:16:17 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

> There is no cost to spam. It is purely an annoyance factor.

There is no cost to spam?  Ha.  Wakeup!!!!

Here are two real cases that effect me directly.  I pay for my service per
volume (per octet).  Therefore it costs me real $$$$ to receive spam.

Secondaly, the other day I received 4 spam SMS messages.  Never mind the
annoyance of having to get the warning, open the phone, navigate through the
messages, and delete them.  When I got my wireless bill, I was pleasantly
rewarded by a charge of 10 cents for each SMS message!!!!



> -----Original Message-----
> From: Dean Anderson [mailto:dean@av8.com] 
> Sent: May 26, 2003 3:08 PM
> To: Valdis.Kletnieks@vt.edu
> Cc: Anthony Atkielski; IETF Discussion
> Subject: Re: spam 
> 
> 
> 
> 
> On Mon, 26 May 2003 Valdis.Kletnieks@vt.edu wrote:
> 
> > On Mon, 26 May 2003 08:56:43 +0200, Anthony Atkielski 
> > <anthony@atkielski.com>  said:
> >
> > > Even at a hundred dollars an hour, the cost of deleting spam each 
> > > day with the delete key (and even at the current rate of 
> hundreds of 
> > > spam per day) is only $2-$3 ... several times cheaper 
> than the daily 
> > > cost of visiting a restroom.
> >
> > Note that visiting the restroom gets a LOT more expensive 
> if you have 
> > to remodel the restroom and add more stalls because 
> everybody is doing 
> > it all the time.
> >
> > Similarly, if your *LAST* mail server was a Sun E6500 and 4 
> Mirapoint 
> > boxes and various other small things like a load balancer, it's 
> > expensive to upgrade to a new box just so all your users can spend 
> > money hitting delete...  Also, remember that although 20 pieces of 
> > spam a day is only a 5% increase in in my mail volume, I clear my 
> > stuff off the server on a regular basis. For the user who gets 5-6 
> > pieces of mail a day and only checks once a week, that's a 
> *big* jump 
> > in how much disk space they consume.
> 
> This is a pretty bogus argument. One that really annoys the 
> radical anti-spammers to debunk, but that can't be avoided.  
> Its sort of a sacred cow with them, but it is a trivial and 
> weak claim.  It was made in 1998, and trounced by the DMA 
> then. Everything (disks, network, computers) is cheaper now. 
> What wasn't a convincing argument then is even less so now.
> 
> Consider a small ISP that handles 400,000 messages per day, 
> with an average message size of 5000 bytes. My real average 
> message size is smaller, but 5000 makes the math easier. Lets 
> do the math:
> 
> 400,000 * 5000 = 2,000,000,000 (2 gig per day, if you were 
> going to save it all).
> 
> I notice that you can get 250Gig disks now for under $400. 2 
> Disks make 1 500Meg volume.  Apply a raid controller with 2 
> more disks, and we are talking about $2000 in disks. ($2000 
> is kind of inflated really, but some ISPs like Av8 consider 
> mail to be important).
> 
> On that 500Gig volume, we can store 500/2 days worth of 
> email.  My calculator says that we can _keep_ all email back 
> for 250 days. About 8 months. And it only cost us $2000 in 
> disk. And thats if no one deleted anything.  Clearly, most 
> email isn't stored that long.
> 
> People talk about Sun 6500s, and users who only read mail 
> once per week, but they are still able to offer mailboxes for 
> $1 or $2/mo per user, and aren't losing money. No one is 
> complaining about the high cost of email boxes.
> 
> There is no cost to spam. It is purely an annoyance factor.
> 
> As far as time spent hitting delete, I went through 409 spams 
> today, and a number of non-spam emails (hundreds, including 
> IETF mail). It took me less than 15 minutes to hand filter 
> all my mail using only pine. And thats not a daily total, 
> thats after not reading email over the weekend.  Using a spam 
> filter would make this almost nothing, as well.
> 
> If you want to count cost of advertising on your time, then 
> you have to count the value of the time you spend in front of 
> the tv watching ads, listening to them on the radio, and the 
> time in the movie theater watching ads, too. The cost of 
> accidents caused by people reading billboards. Spam still 
> comes out to be trivial by comparison.
> 
> As for the volume of spam affecting network utilization, this 
> is also a non-expense. All email, non-spam included, makes up 
> a dwindling proportion of network traffic, in comparision to 
> gifs, and streaming media, and other emerging high bandwidth 
> applications.  Network-wise, spam takes up almost nothing. 
> And like disk costs, network costs, and proportion of 
> bandwidth consumed is dwindling.
> 
> Lets focus on real problems, not sacred cows. Promoting bogus 
> claims doesn't solve anything, but simply discredits those 
> making them. This isn't worthy of the IETF.
> 
> 		--Dean
> 
> 
Looking to offer a managed WLAN Service? Download our market report, completed by Telechoice Market Analyst group, to learn more. <a href="http://www.bridgewatersystems.com/learnmore">http://www.bridgewatersystems.com/learnmore</a>



From owner-ietf@ietf.org  Tue May 27 02:42:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29499
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 02:42:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KXrH-0007g5-E7
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 02:22:51 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KXmm-0006jj-Od
	for ietf@asgard.ietf.org; Tue, 27 May 2003 02:18:12 -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 CAA28693
	for <ietf@ietf.org>; Tue, 27 May 2003 02:18:10 -0400 (EDT)
From: Rod.Walsh@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KXlF-00009n-00
	for ietf@ietf.org; Tue, 27 May 2003 02:16:37 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KXlF-00009k-00
	for ietf@ietf.org; Tue, 27 May 2003 02:16:37 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h4R6I9L04830
	for <ietf@ietf.org>; Tue, 27 May 2003 09:18:09 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T627551cb31ac158f21083@esvir01nok.ntc.nokia.com> for <ietf@ietf.org>;
 Tue, 27 May 2003 09:18:09 +0300
Received: from esebe019.NOE.Nokia.com ([172.21.138.58]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Tue, 27 May 2003 09:18:09 +0300
Received: from trebe003.NOE.Nokia.com ([172.22.232.175]) by esebe019.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Tue, 27 May 2003 09:18:09 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: spam
Date: Tue, 27 May 2003 09:17:55 +0300
Message-ID: <2BF0AD29BC31FE46B78877321144043101B9E391@trebe003.europe.nokia.com>
Thread-Topic: spam
Thread-Index: AcMj6GEyqReimZEfQ/yikN44llxTegAAAnIQAAuTx8A=
To: <ietf@ietf.org>
X-OriginalArrivalTime: 27 May 2003 06:18:09.0172 (UTC) FILETIME=[BE47A540:01C32417]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id CAA29499

Are we witnessing the birth of a new phenomena here: metaspam

As the size of my inbox and time for my email filters to finish demonstrate - deleting spam has a very real cost AND it's a pain in the neck. But without spam how would we maintain our physical shape, impress our lovers and keep our financial houses in order while receiving (not quite morally) free cable TV? It's such a dilemma with all that high quality advertising - and such a same you can't buy most of the products outside the USA.

Kill spam please! (that's my democratic EU vote)

Rod.



From owner-ietf@ietf.org  Tue May 27 03:00:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29992
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 03:00:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KY8r-0000QY-Fk
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 02:41:01 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KXzB-0008NK-1D
	for ietf@asgard.ietf.org; Tue, 27 May 2003 02:31:01 -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 CAA29246
	for <ietf@ietf.org>; Tue, 27 May 2003 02:30:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KXxe-0000Ff-00
	for ietf@ietf.org; Tue, 27 May 2003 02:29:26 -0400
Received: from bws10.bridgewatersystems.com ([216.113.7.10] helo=exch01.bridgewatersys.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KXxd-0000FD-00
	for ietf@ietf.org; Tue, 27 May 2003 02:29:25 -0400
Received: by exch01.bridgewatersys.com with Internet Mail Service (5.5.2653.19)
	id <LM453JAD>; Tue, 27 May 2003 02:30:29 -0400
Message-ID: <F17FB067A86B2D488382C923C532EAA746EC4D@exch01.bridgewatersys.com>
From: Avi Lior <avi@bridgewatersystems.com>
To: "'EKR'" <ekr@rtfm.com>, "'Dean Anderson'" <dean@av8.com>
Cc: "'Valdis.Kletnieks@vt.edu'" <Valdis.Kletnieks@vt.edu>,
        "'Anthony Atkielski'" <anthony@atkielski.com>,
        "'IETF Discussion'"
	 <ietf@ietf.org>
Subject: RE: spam
Date: Tue, 27 May 2003 02:30:28 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

I totally agree.  There are intangible costs to spam. Consider users of
devices such as  Blackberries.  Reception of email causes the device to wake
up and generate and alert.
This generates false alerts as well as drains the batteries prematurely, and
therefore causes us to use the device in a different way (disabling alerts).
This costs us in productivity.

Most people think about email in a very traditional way, and in very
traditional cost models.  If you start thinking about receiving spam on a
wireless device, using volume based billing then, the costs become more
real. And spam becomes way more painful.



> -----Original Message-----
> From: Eric Rescorla [mailto:ekr@rtfm.com] 
> Sent: May 26, 2003 4:13 PM
> To: Dean Anderson
> Cc: Valdis.Kletnieks@vt.edu; Anthony Atkielski; IETF Discussion
> Subject: Re: spam
> 
> 
> Dean Anderson <dean@av8.com> writes:
> > There is no cost to spam. It is purely an annoyance factor.
> This strikes me as a pretty limited way to measure cost.
> 
> To the extent to which people would be willing to pay to not 
> be spammed, then spam is costing them happiness (an economist 
> would say utility). That cost is no less real than if it were 
> using up their disk space. To be concrete about it, consider 
> the amount of money being spent on spam-suppression. That's a 
> direct cost imposed by spam.
> 
> -Ekr
> 
> -- 
> [Eric Rescorla                                   ekr@rtfm.com]
>            Web Log: http://www.rtfm.com/movabletype
> 
> 
Looking to offer a managed WLAN Service? Download our market report, completed by Telechoice Market Analyst group, to learn more. <a href="http://www.bridgewatersystems.com/learnmore">http://www.bridgewatersystems.com/learnmore</a>



From owner-ietf@ietf.org  Tue May 27 03:16:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00779
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 03:16:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KYPW-0001TF-QQ
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 02:58:14 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KYA7-0000Sa-GZ
	for ietf@asgard.ietf.org; Tue, 27 May 2003 02:42:19 -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 CAA29488
	for <ietf@ietf.org>; Tue, 27 May 2003 02:42:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KY8a-0000cK-00
	for ietf@ietf.org; Tue, 27 May 2003 02:40:44 -0400
Received: from bws10.bridgewatersystems.com ([216.113.7.10] helo=exch01.bridgewatersys.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KY8a-0000cG-00
	for ietf@ietf.org; Tue, 27 May 2003 02:40:44 -0400
Received: by exch01.bridgewatersys.com with Internet Mail Service (5.5.2653.19)
	id <LM453JAQ>; Tue, 27 May 2003 02:41:48 -0400
Message-ID: <F17FB067A86B2D488382C923C532EAA746EC4F@exch01.bridgewatersys.com>
From: Avi Lior <avi@bridgewatersystems.com>
To: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: spam and Fax
Date: Tue, 27 May 2003 02:41:47 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

I have a question:

Why is it that I don't get spammed on my fax machine?

What mechansims are used to prevent unsolicited faxes?

How can these techniques be leveraged for email based spam?

Yes I know I get some unsolicited faxes but it's a rare event.
Looking to offer a managed WLAN Service? Download our market report, completed by Telechoice Market Analyst group, to learn more. <a href="http://www.bridgewatersystems.com/learnmore">http://www.bridgewatersystems.com/learnmore</a>



From owner-ietf@ietf.org  Tue May 27 03:20:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00957
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 03:20:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KYPX-0001TW-38
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 02:58:15 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KYAO-0000YZ-6Y
	for ietf@asgard.ietf.org; Tue, 27 May 2003 02:42:36 -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 CAA29519
	for <ietf@ietf.org>; Tue, 27 May 2003 02:42:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KY8r-0000cX-00
	for ietf@ietf.org; Tue, 27 May 2003 02:41:01 -0400
Received: from pengo.systems.pipex.net ([62.241.160.193])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KY8q-0000cH-00
	for ietf@ietf.org; Tue, 27 May 2003 02:41:00 -0400
Received: from ieee.org (userdd211.dsl.pipex.com [62.190.227.211])
	by pengo.systems.pipex.net (Postfix) with ESMTP
	id 279CA4C00546; Tue, 27 May 2003 07:42:00 +0100 (BST)
Message-ID: <3ED3087A.946BC242@ieee.org>
Date: Tue, 27 May 2003 07:40:58 +0100
From: Dominic Pinto <dominic.pinto@ieee.org>
Reply-To: dominic.pinto@ieee.org
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
Cc: "'Dean Anderson'" <dean@av8.com>,
        "'Valdis.Kletnieks@vt.edu'" <Valdis.Kletnieks@vt.edu>,
        "'Anthony Atkielski'" <anthony@atkielski.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: spam
References: <F17FB067A86B2D488382C923C532EAA746EC4C@exch01.bridgewatersys.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Avi Lior wrote:
> 
> > There is no cost to spam. It is purely an annoyance factor.
> 
> There is no cost to spam?  Ha.  Wakeup!!!!
> 
> Here are two real cases that effect me directly.  I pay for my service per
> volume (per octet).  Therefore it costs me real $$$$ to receive spam.
> 
> Secondaly, the other day I received 4 spam SMS messages.  Never mind the
> annoyance of having to get the warning, open the phone, navigate through the
> messages, and delete them.  When I got my wireless bill, I was pleasantly
> rewarded by a charge of 10 cents for each SMS message!!!!
> 

<lots snipped>

Reverse billing - a known and very worrying phenomenon that has been
appearing in what is normally regarded as Calling Party Pays territory
.....

-- 
Dominic Pinto
-------------

Independent Adviser
Public & International Policy - Strategy - Regulation - PR - Commercial
Covent Garden London United Kingdom
----------------------------------------------------------------------
Cellphone/GSM Mobile: +44 780 302 8268 Fax: +44 207 379-8341
----------------------------------------------------------------------
Associated with http://www.telespherelimited.com
----------------------------------------------------------------------
Friend or Former Student of University of Newcastle upon Tyne? 
Join us: See http://www.ncl.ac.uk/alumni
----------------------------------------------------------------------
Check out FITCE Congress 2003 Berlin at http://www.fitce.org
----------------------------------------------------------------------



From owner-ietf@ietf.org  Tue May 27 03:25:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01230
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 03:25:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KYkm-0003Bm-Ty
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 03:20:12 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KYWt-0002Ks-QD
	for ietf@asgard.ietf.org; Tue, 27 May 2003 03:05:51 -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 DAA00514
	for <ietf@ietf.org>; Tue, 27 May 2003 03:05:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KYUu-0000xX-00
	for ietf@ietf.org; Tue, 27 May 2003 03:03:48 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KYUt-0000xQ-00
	for ietf@ietf.org; Tue, 27 May 2003 03:03:47 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4R75IHs007743
	for <ietf@ietf.org>; Tue, 27 May 2003 09:05:18 +0200 (CEST)
Message-ID: <021f01c3241e$54a98340$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.44.0305262047150.3699-100000@commander.av8.net>
Subject: Re: spam (fwd) (edit error on previous)
Date: Tue, 27 May 2003 09:05:18 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dean writes:

> I can see you have a goal of limiting Type 1
> spam, using the harms of Type 2 and Type 3 spam.

I don't understand.

> This effort is doomed to fail.

I seem to manage to get rid of all spam, even the long string of virus
attachments sent to me a couple of hours ago from Japan with a subject line
from this list.

> Sorry. You are wrong.  Only I get to set prices
> on my services.

But nobody has to pay to use an open relay.

> Fraud is common law, which applies to the internet.

Common law requires jurisprudence to define its application.  I'm not aware
of any in this instance, so whether what you describe is fraud or not is an
open question.





From owner-ietf@ietf.org  Tue May 27 03:38:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01593
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 03:38:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KYkn-0003C2-6r
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 03:20:13 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KYbG-0002Sm-FI
	for ietf@asgard.ietf.org; Tue, 27 May 2003 03:10:22 -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 DAA00610
	for <ietf@ietf.org>; Tue, 27 May 2003 03:10:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KYZj-00010j-00
	for ietf@ietf.org; Tue, 27 May 2003 03:08:47 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KYZi-00010g-00
	for ietf@ietf.org; Tue, 27 May 2003 03:08:46 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4R7AIHs007779
	for <ietf@ietf.org>; Tue, 27 May 2003 09:10:18 +0200 (CEST)
Message-ID: <023601c3241f$07a4c1d0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.44.0305261909330.3699-100000@commander.av8.net> <016101c323e1$e1ae5be0$0a00000a@atkielski.com> <3ED2C508.8E2CFA44@earthlink.net>
Subject: Re: spam (fwd) (edit error on previous)
Date: Tue, 27 May 2003 09:10:18 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Peter writes:

> Basically, it's a crime in Canada to use somebody
> else's compute cycles without permission ...

So your e-mail to this list committed a felony, since it reached my machine
without my explicit authorization and used compute cycles thereon ... right?
If not, explain why not.

> BTW, those who think SPAM is "too cheap to meter"
> need to look at the total costs involved in providing
> services ...

And those who say that spam is "too costly to tolerate" need to look at the
total cost of downloading advertisements, animations, active content, and
pop-ups when visiting Web sites--none of which are normally authorized by
the person visiting the sites.  Why isn't that illegal?

> My kids' school pays a part time sysadmin who
> in turn makes use of a couple of technically literate
> parents to help him with various chores as he's
> still learning his craft.

Gee, that's reassuring!





From owner-ietf@ietf.org  Tue May 27 03:40:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01741
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 03:40:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KYnK-0003d8-He
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 03:22:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KYeL-0002Ut-2N
	for ietf@asgard.ietf.org; Tue, 27 May 2003 03:13:33 -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 DAA00729
	for <ietf@ietf.org>; Tue, 27 May 2003 03:13:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KYco-00012o-00
	for ietf@ietf.org; Tue, 27 May 2003 03:11:58 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KYcn-00012l-00
	for ietf@ietf.org; Tue, 27 May 2003 03:11:57 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4R7DUHs007803
	for <ietf@ietf.org>; Tue, 27 May 2003 09:13:30 +0200 (CEST)
Message-ID: <024901c3241f$7a2d96a0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <00aa01c323d3$58562ca0$0a00000a@atkielski.com> <g3k7cduks1.fsf@sa.vix.com>
Subject: Re: spam
Date: Tue, 27 May 2003 09:13:30 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Paul writes:

> warning, i'm answering an obvious troll from
> an obvious spammer.  hit D now.

In other words, you disagree with me, but for reasons I won't go into, you
cannot resist the urge to reply.

> you're describing a fairly desireable state of affairs.
> many folks would happily pay more for a commercial-free
> non-subsidized spam-free e-mail feed.

I'll believe that when I see it.

> my t1 costs me $552 per month in pac bell service
> fees.

Is it 100% busy?  If not, spam effectively costs you nothing, since I assume
you pay a flat rate for a fixed, continuously-available bandwidth.

> how nice for you.  here's the report of spam
> that's reached me and had to be deleted in the last 15 days:

If spam is so expensive, why are you logging and analyzing it?  Doesn't that
raise the cost?  I just throw it away.





From owner-ietf@ietf.org  Tue May 27 03:45:05 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02029
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 03:45:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KYnK-0003dE-PH
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 03:22:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KYgS-0002Z6-Sk
	for ietf@asgard.ietf.org; Tue, 27 May 2003 03:15:44 -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 DAA00764
	for <ietf@ietf.org>; Tue, 27 May 2003 03:15:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KYev-00013K-00
	for ietf@ietf.org; Tue, 27 May 2003 03:14:09 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KYev-00013H-00
	for ietf@ietf.org; Tue, 27 May 2003 03:14:09 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4R7FgHs007823
	for <ietf@ietf.org>; Tue, 27 May 2003 09:15:42 +0200 (CEST)
Message-ID: <025001c3241f$c8961150$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <963621801C6D3E4A9CF454A1972AE8F504F827@server2000.arneill-py.sacramento.ca.us>
Subject: Re: spam
Date: Tue, 27 May 2003 09:15:42 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Michel writes:

> Yeah I think we should work on a system to ban
> obvious spammers from IETF lists. Maybe we should
> also ban people that are so full of it that
> they could double as a sceptic tank such as the
> ones that try to convey the idea that handling
> spam has no cost.

Maybe you should work on a system that allows only people you approve of to
use the Internet.  It might be hard to get worldwide acceptance of that,
however, especially since there are probably others on the Internet who will
feel that _you_ shouldn't be allowed to use it.  How would you reconcile
those conflicts?





From owner-ietf@ietf.org  Tue May 27 03:45:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02089
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 03:45:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KYnL-0003f2-Bt
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 03:22:51 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KYiF-0002wl-Oh
	for ietf@asgard.ietf.org; Tue, 27 May 2003 03:17:35 -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 DAA00879
	for <ietf@ietf.org>; Tue, 27 May 2003 03:17:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KYgi-00016A-00
	for ietf@ietf.org; Tue, 27 May 2003 03:16:00 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KYgi-000167-00
	for ietf@ietf.org; Tue, 27 May 2003 03:16:00 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4R7HXHs007837
	for <ietf@ietf.org>; Tue, 27 May 2003 09:17:33 +0200 (CEST)
Message-ID: <025501c32420$0ac06440$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <1054024455447>
Subject: Re: spam
Date: Tue, 27 May 2003 09:17:33 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John writes:

> Many places in the world do not have access to
> broadband. For many, receiving spam is both a
> monetary expense & a time expense.

What percentage of their bandwidth is consumed by spam, and is this
bandwidth fully utilized?

> Also, when the ratio of spam vs. valid mail become
> high, the utility of email shrinks.

But when spam filters throw away legitimate e-mail, the utility of e-mail
shrinks even further.




From owner-ietf@ietf.org  Tue May 27 03:46:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29993
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 03:00:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KY8s-0000SY-MM
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 02:41:02 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KY3B-0008WB-RL
	for ietf@asgard.ietf.org; Tue, 27 May 2003 02:35:09 -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 CAA29385
	for <ietf@ietf.org>; Tue, 27 May 2003 02:35:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KY1e-0000Zq-00
	for ietf@ietf.org; Tue, 27 May 2003 02:33:34 -0400
Received: from bws10.bridgewatersystems.com ([216.113.7.10] helo=exch01.bridgewatersys.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KY1e-0000Zm-00
	for ietf@ietf.org; Tue, 27 May 2003 02:33:34 -0400
Received: by exch01.bridgewatersys.com with Internet Mail Service (5.5.2653.19)
	id <LM453JAJ>; Tue, 27 May 2003 02:34:38 -0400
Message-ID: <F17FB067A86B2D488382C923C532EAA746EC4E@exch01.bridgewatersys.com>
From: Avi Lior <avi@bridgewatersystems.com>
To: "'Andrew Shore'" <ietf@soaring.demon.co.uk>,
        "'ietf@ietf.org'"
	 <ietf@ietf.org>
Subject: RE: spam
Date: Tue, 27 May 2003 02:34:35 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

Your scheme would keep the email out of the mailbox and out of the client --
I like it.  But it still generates traffic to my network.

> -----Original Message-----
> From: Andrew Shore [mailto:ietf@soaring.demon.co.uk] 
> Sent: May 26, 2003 4:33 PM
> To: ietf@ietf.org
> Subject: Re: spam
> 
> 
> J. Noel Chiappa wrote:
> 
> >The *only* thing that's going to stop spam is charging for email. 
> >Everything else is a waste of time, because you're going to run into 
> >impossible arguments trying to define what's spam, and what's 
> >legitimate bulk email (q.v. the recent message about IETF-Announce 
> >email).
> 
>      That's an interesting argument. I suspect I've missed a 
> lot of the 
> prior discussion, since I'm not sure how charging for email 
> would work 
> (Who charges? Who pays? Could it ever work in a free market? Aren't 
> there legal implications?).
> 
>      It was your "only" that caught my attention, though. 
> Being able to 
> pick and choose my email addresses, I have had a reasonable amount of 
> success using different email addresses for different stores and 
> subscriptions: if an address begins to collect an 
> unreasonable amount of 
> spam, I stop using it. One "technical" solution that would discourage 
> spam would be to add a key (a text string, for example) to the email 
> header. The user gives out their email address with different keys to 
> different groups of people; if a key attracts spam, all they 
> have to do 
> is stop accepting mail with that key. It would also make 
> organising mail 
> very easy. On the negative side, the extra complexity might prove 
> challenging for some...
> 
> 
> Andrew.
> -- 
> Andrew Shore.
> 
Looking to offer a managed WLAN Service? Download our market report, completed by Telechoice Market Analyst group, to learn more. <a href="http://www.bridgewatersystems.com/learnmore">http://www.bridgewatersystems.com/learnmore</a>



From owner-ietf@ietf.org  Tue May 27 03:48:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02317
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 03:48:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KYny-0003gL-Qx
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 03:23:30 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KYkb-0003BX-4G
	for ietf@asgard.ietf.org; Tue, 27 May 2003 03:20:01 -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 DAA00939
	for <ietf@ietf.org>; Tue, 27 May 2003 03:19:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KYj4-000171-00
	for ietf@ietf.org; Tue, 27 May 2003 03:18:26 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KYj3-00016y-00
	for ietf@ietf.org; Tue, 27 May 2003 03:18:25 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4R7JwHs007858
	for <ietf@ietf.org>; Tue, 27 May 2003 09:19:58 +0200 (CEST)
Message-ID: <025e01c32420$6173d380$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <F17FB067A86B2D488382C923C532EAA746EC4C@exch01.bridgewatersys.com>
Subject: Re: spam 
Date: Tue, 27 May 2003 09:19:58 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Avi writes:

> Here are two real cases that effect me directly.
> I pay for my service per volume (per octet).

You pay for incoming traffic on a server?

> Secondaly, the other day I received 4 spam SMS
> messages.

Is SMS part of the Internet now?

> Never mind the annoyance of having to get the
> warning, open the phone, navigate through the
> messages, and delete them.

Done.

> When I got my wireless bill, I was pleasantly
> rewarded by a charge of 10 cents for each SMS message!!!!

Maybe you should change operators.  The more logical arrangement is to pay
for what you voluntarily originate, not for what you receive.  After all,
you pay only for letters you send, not the ones you receive.




From owner-ietf@ietf.org  Tue May 27 03:53:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02513
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 03:53:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KZ1p-0004LQ-RL
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 03:37:49 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KYmp-0003Xo-BW
	for ietf@asgard.ietf.org; Tue, 27 May 2003 03:22:19 -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 DAA01088
	for <ietf@ietf.org>; Tue, 27 May 2003 03:22:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KYlI-00019w-00
	for ietf@ietf.org; Tue, 27 May 2003 03:20:44 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KYlH-00019t-00
	for ietf@ietf.org; Tue, 27 May 2003 03:20:43 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4R7MHHs007884
	for <ietf@ietf.org>; Tue, 27 May 2003 09:22:17 +0200 (CEST)
Message-ID: <026301c32420$b3d01da0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <963621801C6D3E4A9CF454A1972AE8F504F827@server2000.arneill-py.sacramento.ca.us> <g3fzn1udu7.fsf@sa.vix.com>
Subject: Re: spam
Date: Tue, 27 May 2003 09:22:16 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Paul writes:

> does anyone here think this will solve the problem
> for anybody, even the customers of those three customers?

Their "anti-spam" efforts cause them to reject millions of legitimate
e-mails each day, so they create problems, too.

> i'm wasting my time because i want this problem
> looked at more broadly.

What process can you suggest to distinguish spam from legitimate e-mail with
100% reliability and no human intervention?  Find that, and you can become a
billionnaire.




From owner-ietf@ietf.org  Tue May 27 03:58:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02817
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 03:58:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KZDy-0006Lo-PB
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 03:50:22 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KYxZ-0004CH-Jj
	for ietf@asgard.ietf.org; Tue, 27 May 2003 03:33:25 -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 DAA01476
	for <ietf@ietf.org>; Tue, 27 May 2003 03:33:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KYw2-0001II-00
	for ietf@ietf.org; Tue, 27 May 2003 03:31:50 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KYw1-0001IF-00
	for ietf@ietf.org; Tue, 27 May 2003 03:31:49 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4R7XNHs007975
	for <ietf@ietf.org>; Tue, 27 May 2003 09:33:23 +0200 (CEST)
Message-ID: <027801c32422$40c00580$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <F17FB067A86B2D488382C923C532EAA746EC4F@exch01.bridgewatersys.com>
Subject: Re: spam and Fax
Date: Tue, 27 May 2003 09:33:22 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Avi writes:

> Why is it that I don't get spammed on my fax machine?

Several reasons:

1. Sending faxes is much slower than sending e-mails.
2. Fax numbers are much harder to obtain by the millions than are e-mail
addresses.
3. Fax senders are easier to trace.
4. Sending faxes is much more expensive than sending e-mails, in most of the
world.
5. The cost of sending faxes increases with distance; e-mail costs the same
to send anywhere in the world.
6. Sending unsolicited faxes is illegal in some jurisdictions.

Most of these mechanisms cannot be applied to the Internet for technical or
practical reasons, but let's consider the possibilities:

1. We could slow the Internet down to fax speed.  Probably not a realistic
option.

2. We could severely limit the availability of e-mail addresses.  However,
this requires a lot of voluntary discipline on the part of Internet users,
and it involves inconvenience.  I'm sure you've noticed that e-mail
addresses that never appear on USENET or on Web sites and are non-obvious
tend never to be spammed.  Although I receive a lot of spam on a lot of
addresses, there are a few that never receive anything at all.

3. We could improve tracing capability.  The one key difference between the
Internet and the telephone network in this respect is that IP numbers can
change quickly, whereas telephone numbers cannot.  If everyone were required
to have a permanent connection to the Internet, this situation would change
dramatically, and it would have significant and beneficial consequences in
many other domains, too.  Unfortunately, the infrastructure required to
provide fixed IP numbers to everyone is just not in place in most areas, and
there may not even be enough IP numbers to go around.

4. We could charge for sending e-mail.  But every ISP in the world would
have to do this, and that seems unlikely.  It also seems unlikely that any
effective inter-ISP billing could be developed, and even if it existed, it
would use far more bandwidth than the spam did to begin with.

5. Charging by distance would be even more of a nightmare than charging for
e-mail, and like charging for e-mail, it would seriously impair the
legitimate operation of the Internet.  Neither (4) nor this option are very
realistic.

6. We can make the sending of spam illegal.  But without the technical
changes above, that won't change very much.

I actually think that option (3) is by far the most promising.  As long as
it is possible for people to dial into an ISP with a relatively anonymous IP
number, they can move and hide quickly.  If they can be traced as easily as
telephone users, however, the situation changes.  The only problem is that
99.9% of the world is not in a position to implement this, and we don't have
enough IP addresses to go around, anyway.





From owner-ietf@ietf.org  Tue May 27 04:22:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03736
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 04:22:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KZcf-0007xz-HS
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 04:15:53 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KZPT-0007Zn-EP
	for ietf@asgard.ietf.org; Tue, 27 May 2003 04:02:15 -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 EAA03098
	for <ietf@ietf.org>; Tue, 27 May 2003 04:02:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KZNw-0001pK-00
	for ietf@ietf.org; Tue, 27 May 2003 04:00:40 -0400
Received: from syd-msg-core-1.cisco.com ([64.104.193.198])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KZNv-0001of-00
	for ietf@ietf.org; Tue, 27 May 2003 04:00:39 -0400
Received: from GCHISHOL-W2K2.cisco.com (localhost [127.0.0.1])
	by syd-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4R81ds0027126
	for <ietf@ietf.org>; Tue, 27 May 2003 18:01:40 +1000 (EST)
Message-Id: <5.1.1.6.2.20030527155331.04eefc70@ringer.cisco.com>
X-Sender: gchishol@ringer.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Tue, 27 May 2003 16:01:37 +0800
To: "IETF Discussion" <ietf@ietf.org>
From: Glenn Chisholm <glc@cisco.com>
Subject: Re: spam (fwd) (edit error on previous)
In-Reply-To: <023601c3241f$07a4c1d0$0a00000a@atkielski.com>
References: <Pine.LNX.4.44.0305261909330.3699-100000@commander.av8.net>
 <016101c323e1$e1ae5be0$0a00000a@atkielski.com>
 <3ED2C508.8E2CFA44@earthlink.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 09:10 AM 27/05/2003 +0200, Anthony Atkielski wrote:
>Peter writes:
>
> > Basically, it's a crime in Canada to use somebody
> > else's compute cycles without permission ...
>
>So your e-mail to this list committed a felony, since it reached my machine
>without my explicit authorization and used compute cycles thereon ... right?
>If not, explain why not.

I would imagine that your membership of the mailing list would constitute 
consent. Of course even if it did not, this would hardly be the first time 
a law has created an absurd situation.

glenn 




From owner-ietf@ietf.org  Tue May 27 04:51:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04750
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 04:51:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ka2y-0000aS-Hx
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 04:43:04 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KZyh-0000TU-KV
	for ietf@asgard.ietf.org; Tue, 27 May 2003 04:38:39 -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 EAA04380
	for <ietf@ietf.org>; Tue, 27 May 2003 04:38:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KZxA-0002BY-00
	for ietf@ietf.org; Tue, 27 May 2003 04:37:04 -0400
Received: from anchor-post-35.mail.demon.net ([194.217.242.85])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KZx9-0002BP-00
	for ietf@ietf.org; Tue, 27 May 2003 04:37:03 -0400
Received: from soaring.demon.co.uk ([80.177.120.110])
	by anchor-post-35.mail.demon.net with esmtp (Exim 3.36 #2)
	id 19KZyf-00053c-0Z
	for ietf@ietf.org; Tue, 27 May 2003 09:38:37 +0100
Message-ID: <YGxPf1C7Oy0+EwCN@soaring.demon.co.uk>
Date: Tue, 27 May 2003 09:37:15 +0100
To: "'ietf@ietf.org'" <ietf@ietf.org>
From: Andrew Shore <ietf@soaring.demon.co.uk>
Reply-To: Andrew Shore <ietf@soaring.demon.co.uk>
Subject: Re: spam
References: <F17FB067A86B2D488382C923C532EAA746EC4E@exch01.bridgewatersys.com>
In-Reply-To: <F17FB067A86B2D488382C923C532EAA746EC4E@exch01.bridgewatersys.com>
MIME-Version: 1.0
Content-Type: text/plain;charset=us-ascii;format=flowed
User-Agent: Turnpike/6.02-S (<aCAGT1CKFCi8lsT3mwPhfD$m6j>)
Sender: owner-ietf@ietf.org
Precedence: bulk

Avi Lior wrote:

>Your scheme would keep the email out of the mailbox and out of the client --
>I like it.  But it still generates traffic to my network.

     Well, it springs from an idea that works for me (as a user) without 
being particularly good for the network. As I currently implement it, 
using different email addresses, the spam I'm avoiding ends up sitting 
on my ISP's mail server waiting to bounce. I was thinking that 
widespread use of keys would eventually act as a deterrent to spam - 
knowing that email to even a valid "public" key is going to be filtered 
through an extremely selective spam filter ought to discourage people. 
On further consideration, this may be a little naive of me.


Andrew.
-- 
Andrew Shore.



From owner-ietf@ietf.org  Tue May 27 04:59:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04916
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 04:59:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ka34-0000ag-OK
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 04:43:10 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KZzQ-0000Th-In
	for ietf@asgard.ietf.org; Tue, 27 May 2003 04:39:24 -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 EAA04400
	for <ietf@ietf.org>; Tue, 27 May 2003 04:39:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KZxq-0002C1-00
	for ietf@ietf.org; Tue, 27 May 2003 04:37:46 -0400
Received: from mrburns.nildram.co.uk ([195.112.4.54])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KZxp-0002By-00
	for ietf@ietf.org; Tue, 27 May 2003 04:37:45 -0400
Received: from hourglass (unknown [81.6.214.202])
	by mrburns.nildram.co.uk (Postfix) with ESMTP
	id 1F1EE1D9623; Tue, 27 May 2003 09:39:17 +0100 (BST)
From: "Christian de Larrinaga" <cdel@firsthand.net>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, <ietf@ietf.org>
Subject: RE: spam
Date: Tue, 27 May 2003 09:39:23 +0100
Message-ID: <MABBIEBOAFJNELEGFHCKAEMCIDAA.cdel@firsthand.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <200305262307.h4QN7iWh026834@ginger.lcs.mit.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Noel Chiappa wrote...

> Needless to say, toll roads exist, but billed road use doesn't.
> 
> 	Noel
> 
> 

It does in London.


Christian de Larrinaga



From owner-ietf@ietf.org  Tue May 27 04:59:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04991
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 04:59:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ka34-0000am-Vv
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 04:43:10 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ka26-0000Tj-Bl
	for ietf@asgard.ietf.org; Tue, 27 May 2003 04:42: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 EAA04442
	for <ietf@ietf.org>; Tue, 27 May 2003 04:42:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ka0Z-0002Cn-00
	for ietf@ietf.org; Tue, 27 May 2003 04:40:35 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ka0Y-0002Ck-00
	for ietf@ietf.org; Tue, 27 May 2003 04:40:34 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4R8g4jh008598
	for <ietf@ietf.org>; Tue, 27 May 2003 10:42:04 +0200 (CEST)
Message-ID: <028701c3242b$d924b100$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.44.0305261909330.3699-100000@commander.av8.net> <016101c323e1$e1ae5be0$0a00000a@atkielski.com> <3ED2C508.8E2CFA44@earthlink.net> <5.1.1.6.2.20030527155331.04eefc70@ringer.cisco.com>
Subject: Re: spam (fwd) (edit error on previous)
Date: Tue, 27 May 2003 10:42:03 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Glenn writes:

> I would imagine that your membership of the mailing
> list would constitute consent. Of course even if it
> did not, this would hardly be the first time
> a law has created an absurd situation.

Exactly.  My point is that, without jurisprudence and precedent, there's no
telling whether a specific law (common or statutory) will be applicable to a
given situation.  And sometimes courts and judges make bizarre decisions.




From owner-ietf@ietf.org  Tue May 27 07:04:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07662
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 07:04:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kbzs-0006Sf-EB
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 06:48:00 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KbqD-0006GD-50
	for ietf@asgard.ietf.org; Tue, 27 May 2003 06:38:01 -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 GAA07076
	for <ietf@ietf.org>; Tue, 27 May 2003 06:37:57 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kbof-0002zB-00
	for ietf@ietf.org; Tue, 27 May 2003 06:36:26 -0400
Received: from h80ad2520.async.vt.edu ([128.173.37.32] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kboe-0002z8-00
	for ietf@ietf.org; Tue, 27 May 2003 06:36:24 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h4RAbqJ2006971;
	Tue, 27 May 2003 06:37:52 -0400
Message-Id: <200305271037.h4RAbqJ2006971@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Anthony Atkielski <anthony@atkielski.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: spam 
In-Reply-To: Your message of "Tue, 27 May 2003 09:17:33 +0200."
             <025501c32420$0ac06440$0a00000a@atkielski.com> 
References: <1054024455447@gkar.cc.vt.edu>
            <025501c32420$0ac06440$0a00000a@atkielski.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_522880259P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 27 May 2003 06:37:51 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_522880259P
Content-Type: text/plain; charset=us-ascii

On Tue, 27 May 2003 09:17:33 +0200, Anthony Atkielski <anthony@atkielski.com>  said:

> What percentage of their bandwidth is consumed by spam, and is this
> bandwidth fully utilized?

If you're being billed per megabyte or minute, and connected at modem speeds,
the answer doesn't really matter.   It's costing you (even if only in
people time), and installing a bigger pipe isn't an option either.

You might want to learn a bit about queuing theory also - like why you can be
dropping packets due to congestion and similar nasties when you're only
using 70% of the bandwidth.  Just because it's not clogging ALL the
bandwidth doesn't mean it's not a problem.  




--==_Exmh_522880259P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+0z//cC3lWbTT17ARAjnSAKCvFVvocM+U7YsZVJmnooxj3bMi/gCfUOTt
d+Q2Xq53eeP+iTHUvyq46BQ=
=aHLH
-----END PGP SIGNATURE-----

--==_Exmh_522880259P--



From owner-ietf@ietf.org  Tue May 27 07:26:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08374
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 07:26:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KcSl-0007rt-8R
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 07:17:51 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KcNu-0007la-Ce
	for ietf@asgard.ietf.org; Tue, 27 May 2003 07:12:50 -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 HAA08027
	for <ietf@ietf.org>; Tue, 27 May 2003 07:12:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KcLz-0003Dp-00
	for ietf@ietf.org; Tue, 27 May 2003 07:10:51 -0400
Received: from web10904.mail.yahoo.com ([216.136.131.40])
	by ietf-mx with smtp (Exim 4.12)
	id 19KcLz-0003Dm-00
	for ietf@ietf.org; Tue, 27 May 2003 07:10:51 -0400
Message-ID: <20030527111224.10777.qmail@web10904.mail.yahoo.com>
Received: from [12.237.229.250] by web10904.mail.yahoo.com via HTTP; Tue, 27 May 2003 04:12:24 PDT
Date: Tue, 27 May 2003 04:12:24 -0700 (PDT)
From: Spencer Dawkins <spencer_dawkins@yahoo.com>
Subject: Spam and Variant threads
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

You know... Ordinarily *I* have no problem just hitting the
delete key when I receive e-mail that's not what I need to be
reading, but it *does* seem odd that I'm receiving so much
e-mail on *this* thread, on the IETF list.

If I may summarize the situation as I understand it:

- the IETF has declined to work on spam as an e-mail issue, at
least thus far (IETF 40 SPAM BoF, sadly without providing any
minutes for the proceedings),

- there is an IRTF research group on the topic, but their
mailing list is not ietf@ietf.org,

- there are things that individuals can do/not do as part of the
political process in the United States, and this has already
been pointed out on ietf@ietf.org, so no strong reason to
continue to discuss it there.

So, why is this discussion continuing on ietf@ietf.org? 

You may think that the answer is "my next post will settle this
issue once and for all", but so far, this fact has not been in
evidence.

Please don't stop thinking about the problem - just stop
thinking that postings to the main IETF discussion list will do
anything to solve the problem!

Spencer



From owner-ietf@ietf.org  Tue May 27 07:51:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07663
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 07:04:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kbzt-0006TH-Nr
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 06:48:01 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KbzP-0006MY-5A
	for ietf@asgard.ietf.org; Tue, 27 May 2003 06:47:31 -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 GAA07235
	for <ietf@ietf.org>; Tue, 27 May 2003 06:47:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kbxr-00032b-00
	for ietf@ietf.org; Tue, 27 May 2003 06:45:55 -0400
Received: from [131.227.76.5] (helo=prue.eim.surrey.ac.uk ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kbxr-00032X-00
	for ietf@ietf.org; Tue, 27 May 2003 06:45:55 -0400
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 19Kbz5-0004fY-00; Tue, 27 May 2003 11:47:12 +0100
Date: Tue, 27 May 2003 11:47:10 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Christian de Larrinaga <cdel@firsthand.net>
cc: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, "" <ietf@ietf.org>
Subject: RE: spam
In-Reply-To: <MABBIEBOAFJNELEGFHCKAEMCIDAA.cdel@firsthand.net>
Message-ID: <Pine.GSO.4.50.0305271146390.10026-100000@artemis.ee.surrey.ac.uk>
References: <MABBIEBOAFJNELEGFHCKAEMCIDAA.cdel@firsthand.net>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-105.8 required=5.5
	tests=AWL,BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_PINE,
	      USER_IN_WHITELIST
	autolearn=ham version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
X-Scanner: exiscan *19Kbz5-0004fY-00*HBol7NuHPno* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 27 May 2003, Christian de Larrinaga wrote:

> Noel Chiappa wrote...
>
> > Needless to say, toll roads exist, but billed road use doesn't.
>
> It does in London.

and congestion charging apart, how do you think road building and
maintenance is paid for? tax.

L.

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>



From owner-ietf@ietf.org  Tue May 27 09:57:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11702
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 09:57:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KeZM-0002vp-5z
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 09:32:48 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KeYo-0002r1-4z
	for ietf@asgard.ietf.org; Tue, 27 May 2003 09:32:14 -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 JAA11140
	for <ietf@ietf.org>; Tue, 27 May 2003 09:32:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KeXG-0004FA-00
	for ietf@ietf.org; Tue, 27 May 2003 09:30:38 -0400
Received: from mail13.speakeasy.net ([216.254.0.213] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KeXF-0004F7-00
	for ietf@ietf.org; Tue, 27 May 2003 09:30:37 -0400
Received: (qmail 27061 invoked from network); 27 May 2003 13:31:58 -0000
Received: from unknown (HELO 192.168.254.124) ([66.92.168.196])
          (envelope-sender <dja2003@hotpop.com>)
          by mail13.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <richard@shockey.us>; 27 May 2003 13:31:58 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: Richard Shockey <richard@shockey.us>, ietf@ietf.org
Subject: IETF-related attendees at FTC spam forum
Date: Tue, 27 May 2003 09:34:14 -0400
User-Agent: KMail/1.5
References: <093001c322af$60b28800$0a00000a@atkielski.com> <5.2.0.9.2.20030525150925.050dc008@shockey.us>
In-Reply-To: <5.2.0.9.2.20030525150925.050dc008@shockey.us>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305270934.14258.dja2003@hotpop.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Sunday 25 May 2003 15:32, Richard Shockey wrote:

 RS> I personally attended the FTC hearings on SPAM and there
 RS> were only 2 other people in the audience that had any
 RS> connection to the IETF whatsoever.

Since you mention Dave Crocker, I guess I must be the mysterious third 
person.  B-)

I didn't notice any other familiar names, but methinks there were 
probably many people with "any connection to the IETF whatsoever".  
After all, you probably didn't get to check out everybody's nametag, nor 
have you probably memorized the names of all IETF-related people.

If you mean "officer, or otherwise entitled to speak on behalf, of the 
IETF or some WG", "author of any drafts or RFCs", "have attended an IETF 
meeting", or some such, well, that's a different story entirely.  
Likewise if you mean panels rather than audience.

 RS> No one from the Internet Society was there BTW.

Again, if you mean to include ordinary members, there were probably 
many... such as, again, myself.

 RS> If each of us do nothing I can guarantee you the Congress will
 RS> screw it up...

Heck, even if we do something....  ;-/

-- 
David J. Aronson, unemployed Software Engineer in Washington DC area.
Go to http://destined.to/program/ for online resume, references, etc.




From owner-ietf@ietf.org  Tue May 27 10:03:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12084
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 10:03:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ket4-0003Hv-C8
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 09:53:10 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Jd3w-000278-Vu
	for ietf@asgard.ietf.org; Sat, 24 May 2003 13:44:09 -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 NAA00832
	for <ietf@ietf.org>; Sat, 24 May 2003 13:44:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Jd2W-0001GR-00
	for ietf@ietf.org; Sat, 24 May 2003 13:42:40 -0400
Received: from vmmrnat.verisignmail.com ([216.168.230.187] helo=vmmr7.verisignmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Jd2V-0001GO-00
	for ietf@ietf.org; Sat, 24 May 2003 13:42:39 -0400
Received: from ms1.verisignmail.com (ms1.verisignmail.com [216.168.230.167] (may be forged))
	by vmmr7.verisignmail.com (Mirapoint Messaging Server MOS 3.2.2-GA)
	with ESMTP id OWC95528;
	Sat, 24 May 2003 13:44:04 -0400 (EDT)
Received: from BOB.AppliedSNMP.com (pcp830034pcs.nrockv01.md.comcast.net [68.50.129.39])
	by ms1.verisignmail.com (Mirapoint Messaging Server MOS 3.2.2-GA)
	with ESMTP id AGZ58007;
	Sat, 24 May 2003 13:44:02 -0400 (EDT)
Message-Id: <5.1.0.14.2.20030524134100.02d3ab80@mail.AppliedSNMP.com>
X-Sender: Bob.Natale@AppliedSNMP.com@mail.AppliedSNMP.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sat, 24 May 2003 13:46:51 -0400
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
From: Bob Natale <Bob.Natale@AppliedSNMP.com>
Subject: Re: Last Call: IP over MIME to Proposed Standard
Cc: ietf@ietf.org
In-Reply-To: <200305241307.h4OD7Z6o012938@ginger.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 5/24/2003:09:07 AM, J. Noel Chiappa wrote:

Hi Noel,

>Anything that more than two "real user" entities are going to want to use,
>and *might want to inter-operate*, is probably standards-track material.

Wow!  I pity the poor IESG members who would have to live with that
policy!

With all due respect, that has got to be one of the most non-scalable
concepts I've ever seen proposed...not to mention its many other counter-
productive qualities as identified already by Keith (with whom I concur
on this).

Cheers,

BobN






From owner-ietf@ietf.org  Tue May 27 10:47:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14776
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 10:47:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KfTx-0002Ii-DJ
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 10:31:17 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KfHU-00029V-Ho
	for ietf@asgard.ietf.org; Tue, 27 May 2003 10:18:24 -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 KAA13777
	for <ietf@ietf.org>; Tue, 27 May 2003 10:18:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KfFx-0004cz-00
	for ietf@ietf.org; Tue, 27 May 2003 10:16:49 -0400
Received: from [216.93.164.123] (helo=zak.ecotroph.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KfFw-0004cw-00
	for ietf@ietf.org; Tue, 27 May 2003 10:16:48 -0400
Received: from ecotroph.net (h87.s239.netsol.com [::ffff:216.168.239.87])
  (AUTH: LOGIN anewton)
  by zak.ecotroph.net with esmtp; Tue, 27 May 2003 10:18:20 -0400
Message-ID: <3ED37795.8040203@ecotroph.net>
Date: Tue, 27 May 2003 10:35:01 -0400
From: Andrew Newton <anewton@ecotroph.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: spam and the IETF
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Buried deep in this article in news.com about challenge-response systems 
as a means for fighting spam is this perception of the IETF and spam:

  All these should be obvious, but many challenge-response systems just 
don't follow them. Fortunately, the Internet Engineering Task Force's 
Anti-Spam Research Group is spending some time trying to devise a 
reasonable standard.

from: http://news.com.com/2010-1071_3-1009745.html?tag=fd_nc_1

-andy




From owner-ietf@ietf.org  Tue May 27 11:00:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15585
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 11:00:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KfoE-0003U9-NE
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 10:52:14 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KfZy-0002Tj-74
	for ietf@asgard.ietf.org; Tue, 27 May 2003 10:37:30 -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 KAA14497
	for <ietf@ietf.org>; Tue, 27 May 2003 10:37:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KfYQ-0004nT-00
	for ietf@ietf.org; Tue, 27 May 2003 10:35:54 -0400
Received: from out003pub.verizon.net ([206.46.170.103] helo=out003.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KfYP-0004n5-00
	for ietf@ietf.org; Tue, 27 May 2003 10:35:53 -0400
Received: from earthlink.net ([4.65.81.213]) by out003.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030527143655.IGVJ4805.out003.verizon.net@earthlink.net>;
          Tue, 27 May 2003 09:36:55 -0500
Message-ID: <3ED37724.56B53F25@earthlink.net>
Date: Tue, 27 May 2003 07:33:08 -0700
From: Peter Deutsch <pdeutsch@earthlink.net>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Anthony Atkielski <anthony@atkielski.com>
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: spam (fwd) (edit error on previous)
References: <Pine.LNX.4.44.0305261909330.3699-100000@commander.av8.net> <016101c323e1$e1ae5be0$0a00000a@atkielski.com> <3ED2C508.8E2CFA44@earthlink.net> <023601c3241f$07a4c1d0$0a00000a@atkielski.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out003.verizon.net from [4.65.81.213] at Tue, 27 May 2003 09:36:55 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

g'day,

Anthony Atkielski wrote:
> 
> Peter writes:
> 
> > Basically, it's a crime in Canada to use somebody
> > else's compute cycles without permission ...
> 
> So your e-mail to this list committed a felony, since it reached my machine
> without my explicit authorization and used compute cycles thereon ... right?
> If not, explain why not.

Do please pay attention, this will all be on the exam.

First, I didn't say "explicit authorization". It's generally considered
poor debating style to put words into the mouths of others so as to
appear to win a point.

Next, by subscribing to this list, you are granting implicit permission
to the list operator to connect to your machine to deliver list-related
email. If I were to take this example to the RCMP, I would fully expect
to be told that no crime was committed, because implicit authorization
was obviously granted.

Note, in signing up to a mailing list, you have *not* granted permission
to the list operator to send fragments of code intended to run your
implementation of the Distributed Halting Problem, nor are you
authorizing non-subscribers to the list to harvest your email for
unsolicited bulk commercial messaging.

The relevant concept appears to be one of property rights - you have the
right to determine what others can and cannot do with your property. You
can grant explicit or implicit rights to access your resources without
losing those rights.

Got it now?




> > BTW, those who think SPAM is "too cheap to meter"
> > need to look at the total costs involved in providing
> > services ...
> 
> And those who say that spam is "too costly to tolerate" need to look at the
> total cost of downloading advertisements, animations, active content, and
> pop-ups when visiting Web sites--none of which are normally authorized by
> the person visiting the sites.  Why isn't that illegal?

Because it's something you can control by, for example, choosing not to
visit the site. Nobody's obliged to operate a website for your
convenience, and if you don't like the service, or the way they finance
it, you don't have to come back. This is fundamentally difference from
logging onto someone else's machine and using it for your purposes with
such an implicit contract.


> > My kids' school pays a part time sysadmin who
> > in turn makes use of a couple of technically literate
> > parents to help him with various chores as he's
> > still learning his craft.
> 
> Gee, that's reassuring!

What's your point? Small groups with limited resources should have just
as much right to benefit from the Internet, and not be subject to Denial
of Service attacks from Taiwanese servers just because they can't afford
tens of thousands of dollars per year in staff and equipment to defend
themselves. It's in exactly such circumstances that the true cost of
such activities is most evident. Large companies may be able to eat the
added costs, but at the margins it forces folks to do without. Shame on
you for not being able to see that...


				- peterd





-- 
---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software


             "I'm no stranger to sarcasm, Sir..."

                               - Red versus Blue

---------------------------------------------------------------------



From owner-ietf@ietf.org  Tue May 27 11:01:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15658
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 11:01:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kfoo-0003sC-7k
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 10:52:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19K2eo-0005iT-Vg
	for ietf@asgard.ietf.org; Sun, 25 May 2003 17:03:55 -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 RAA11711
	for <ietf@ietf.org>; Sun, 25 May 2003 17:03:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K2dK-0000vH-00
	for ietf@ietf.org; Sun, 25 May 2003 17:02:22 -0400
Received: from dgesmtp02.wcom.com ([199.249.16.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 19K2dK-0000vD-00
	for ietf@ietf.org; Sun, 25 May 2003 17:02:22 -0400
Received: from pmismtp03.wcomnet.com ([166.38.62.38])
 by firewall.wcom.com (Iplanet MTA )
 with ESMTP id <0HFG00J83NSFSH@firewall.wcom.com> for ietf@ietf.org; Sun,
 25 May 2003 21:02:40 +0000 (GMT)
Received: from pmismtp03.wcomnet.com by pmismtp03.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HFG00101NSFGC@pmismtp03.wcomnet.com>; Sun,
 25 May 2003 21:02:39 +0000 (GMT)
Received: from vint.mci.com ([166.50.142.85])
 by pmismtp03.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HFG0000NNSDX0@pmismtp03.wcomnet.com>; Sun,
 25 May 2003 21:02:39 +0000 (GMT)
Date: Sun, 25 May 2003 17:02:34 -0400
From: "vinton g. cerf" <vinton.g.cerf@mci.com>
Subject: Re: spam
In-reply-to: <3ED124DE.8060409@ehsco.com>
X-Sender: vcerf@pop.mcilink.com
To: "Eric A. Hall" <ehall@ehsco.com>, Richard Shockey <richard@shockey.us>
Cc: ietf@ietf.org
Message-id: <5.2.0.9.2.20030525170219.035dbdf8@pop.mcilink.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Content-type: text/plain; charset=us-ascii
References: <5.2.0.9.2.20030525150925.050dc008@shockey.us>
 <093001c322af$60b28800$0a00000a@atkielski.com>
 <000501c32253$f6707160$92082b45@a>
 <093001c322af$60b28800$0a00000a@atkielski.com>
 <5.2.0.9.2.20030525150925.050dc008@shockey.us>
Sender: owner-ietf@ietf.org
Precedence: bulk

that's the person who tries to articulate ISOC-wide policy where this seems merited.

vint

At 03:17 PM 5/25/2003 -0500, Eric A. Hall wrote:
>I see from http://www.isoc.org/isoc/general/officers/ that they have a VP
>of Public Policy but I don't know what that means. Anybody?
>
>-- 

Vint Cerf
SVP Architecture & Technology
MCI
22001 Loudoun County Parkway, F2-4115
Ashburn, VA 20147
703 886 1690 (v806 1690)
703 886 0047 fax
vinton.g.cerf@mci.com
www.mci.com/cerfsup 






From owner-ietf@ietf.org  Tue May 27 11:17:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16341
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 11:17:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kg1X-0005ny-IK
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 11:05:59 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KfvD-0004zd-G1
	for ietf@asgard.ietf.org; Tue, 27 May 2003 10:59:27 -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 KAA15533
	for <ietf@ietf.org>; Tue, 27 May 2003 10:59:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kftf-00054d-00
	for ietf@ietf.org; Tue, 27 May 2003 10:57:51 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kftf-00053p-00
	for ietf@ietf.org; Tue, 27 May 2003 10:57:51 -0400
Content-class: urn:content-classes:message
Subject: RE: spam
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Tue, 27 May 2003 07:59:15 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F829@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: spam
Thread-Index: AcMkGMc7Pqem/5wmTViEse8R6pNR9QARuP9A
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Paul Vixie" <vixie@vix.com>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA16341

> i'm wasting my time because i want this problem looked
> at more broadly.

Are you in agreement with what Noel wrote earlier WRT involving some
money in sending email is the only deterrent that spammers that pollute
our inbox and now our mailing list would understand?

Michel.




From owner-ietf@ietf.org  Tue May 27 11:34:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17105
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 11:34:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KgHL-00079u-4S
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 11:22:19 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KgFm-00070D-F7
	for ietf@asgard.ietf.org; Tue, 27 May 2003 11:20:42 -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 LAA16540
	for <ietf@ietf.org>; Tue, 27 May 2003 11:20:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KgEE-0005MV-00
	for ietf@ietf.org; Tue, 27 May 2003 11:19:06 -0400
Received: from windlord.stanford.edu ([171.64.19.147])
	by ietf-mx with smtp (Exim 4.12)
	id 19KgEE-0005MS-00
	for ietf@ietf.org; Tue, 27 May 2003 11:19:06 -0400
Received: (qmail 26500 invoked by uid 50); 27 May 2003 15:20:33 -0000
To: "IETF Discussion" <ietf@ietf.org>
Subject: Re: spam
References: <963621801C6D3E4A9CF454A1972AE8F504F827@server2000.arneill-py.sacramento.ca.us>
	<g3fzn1udu7.fsf@sa.vix.com>
	<026301c32420$b3d01da0$0a00000a@atkielski.com>
In-Reply-To: <026301c32420$b3d01da0$0a00000a@atkielski.com> ("Anthony
 Atkielski"'s message of "Tue, 27 May 2003 09:22:16 +0200")
From: Russ Allbery <rra@stanford.edu>
Organization: The Eyrie
Date: Tue, 27 May 2003 08:20:33 -0700
Message-ID: <ylk7cc1kn2.fsf@windlord.stanford.edu>
Lines: 43
User-Agent: Gnus/5.090008 (Oort Gnus v0.08) XEmacs/21.4 (Portable Code,
 sparc-sun-solaris2.6)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Anthony Atkielski <anthony@atkielski.com> writes:

> Their "anti-spam" efforts cause them to reject millions of legitimate
> e-mails each day, so they create problems, too.

So does trying to find the legitimate mail among a pile of spam.

> What process can you suggest to distinguish spam from legitimate e-mail
> with 100% reliability and no human intervention?  Find that, and you can
> become a billionnaire.

It's reality-check time.  We're not going to get that, and the problem is
continuing to get worse.  Now what?

How many people who are active and have been active for some time on the
Internet are still putting e-mail addresses on web pages and then reading
them with no spam filtering whatsoever, just looking through the inbox and
deleting what isn't wanted?

How many of you have accidentally discarded the wrong message because it
got caught in a purge of spam from your inbox?

Personally, I can still cope with the onslaught with no filtering other
than a few simple personal rules based on observation of my incoming spam
and the types of messages I personally receive, but those rules are
utterly draconian from certain perspectives and still vulnerable to false
positives (for example, I don't speak any Asian language, so anything I
receive in that character set goes straight into the spam pile, likely
never to be looked at; if someone sent me a message that contained an
excerpt in Chinese, I would likely never see it).  I can probably make do
with Bayesian filtering for at least another two years.

Forever?  Unclear.  It would be rather nice to think that people were
working on some sort of protocol solution at the same time, though.  (But
another point made is very valid too, namely that someone needs to do
protocol work and forming a working group is something that one does after
one has some idea of what sort of protocol one is working on.  There are a
host of plausible-looking ideas for dealing with spam that have been tried
over the years that would be a waste of time to standardize because they
don't actually work.)

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>



From owner-ietf@ietf.org  Tue May 27 11:51:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17794
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 11:51:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kgc6-0008Cl-Ie
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 11:43:46 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KgYK-00087v-8F
	for ietf@asgard.ietf.org; Tue, 27 May 2003 11:39:52 -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 LAA17333
	for <ietf@ietf.org>; Tue, 27 May 2003 11:39:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KgWm-0005XO-00
	for ietf@ietf.org; Tue, 27 May 2003 11:38:16 -0400
Received: from mail12.speakeasy.net ([216.254.0.212] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KgWl-0005XL-00
	for ietf@ietf.org; Tue, 27 May 2003 11:38:15 -0400
Received: (qmail 19426 invoked from network); 27 May 2003 15:39:41 -0000
Received: from unknown (HELO 192.168.254.124) ([66.92.168.196])
          (envelope-sender <dja2003@hotpop.com>)
          by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <ehall@ehsco.com>; 27 May 2003 15:39:41 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: "Eric A. Hall" <ehall@ehsco.com>
Subject: tarpit
Date: Tue, 27 May 2003 11:41:57 -0400
User-Agent: KMail/1.5
Cc: ietf@ietf.org
References: <Pine.LNX.4.44.0305261205180.3699-100000@commander.av8.net> <200305261926.h4QJQmQC001988@burp.tkv.asdf.org> <3ED27762.4070004@ehsco.com>
In-Reply-To: <3ED27762.4070004@ehsco.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305271141.57283.dja2003@hotpop.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Monday 26 May 2003 16:21, Eric A. Hall wrote:

 EA> How so? As I have heard it used in the common sense,
 EA> [a tarpit] allows delivery to some and slows the
 EA> delivery to others, but doesn't prevent any of it.

By slowing it down, it increases the chances that the spammer may be 
caught in the act, and shut down by a responsive ISP's security 
department.  (Quit laughing.  It happens.  Once in a blue moon.  Or at 
least, the security folks TELL me they've shut the connection down....)

 EA> Even in those cases of cooperative tarpits that cooperate to
 EA> consume socket resources on the spamming host, some recipients still
 EA> have to take the pain before the cooperative nets can respond.

Well, SOMEone's gotta walk point....

-- 
David J. Aronson, unemployed Software Engineer in Washington DC area.
Go to http://destined.to/program/ for online resume, references, etc.




From owner-ietf@ietf.org  Tue May 27 12:11:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18345
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 12:11:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kgii-0008He-DH
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 11:50:36 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KgfM-0008FK-6r
	for ietf@asgard.ietf.org; Tue, 27 May 2003 11:47:08 -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 LAA17633
	for <ietf@ietf.org>; Tue, 27 May 2003 11:47:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kgdo-0005bT-00
	for ietf@ietf.org; Tue, 27 May 2003 11:45:32 -0400
Received: from mail11.speakeasy.net ([216.254.0.211] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kgdn-0005bQ-00
	for ietf@ietf.org; Tue, 27 May 2003 11:45:31 -0400
Received: (qmail 18507 invoked from network); 27 May 2003 15:47:05 -0000
Received: from unknown (HELO 192.168.254.124) ([66.92.168.196])
          (envelope-sender <dja2003@hotpop.com>)
          by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <Valdis.Kletnieks@vt.edu>; 27 May 2003 15:47:05 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: Valdis.Kletnieks@vt.edu
Subject: major ISP spam count
Date: Tue, 27 May 2003 11:49:22 -0400
User-Agent: KMail/1.5
Cc: IETF Discussion <ietf@ietf.org>
References: <000501c32253$f6707160$92082b45@a> <010d01c323d7$f492ad60$0a00000a@atkielski.com> <200305262326.h4QNQcbM006384@turing-police.cc.vt.edu>
In-Reply-To: <200305262326.h4QNQcbM006384@turing-police.cc.vt.edu>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305271149.22675.dja2003@hotpop.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Monday 26 May 2003 19:26, Valdis.Kletnieks@vt.edu wrote:

 V> You're not having to catch and drop a *billion* spams a day like
 V> the guys at AOL or MSN/Hotmail

TWO billion a day at AOL, according to their rep who spoke at the Spam 
Forum.  (IIRC her name was Margot Koschier, or something like that.)  
Probably three billion a day by now.

Yes, their press release just a month earlier said one billion.  I asked 
her about it.  She said, yes, their spam count had indeed doubled in 
about the past month....

-- 
David J. Aronson, unemployed Software Engineer in Washington DC area.
Go to http://destined.to/program/ for online resume, references, etc.




From owner-ietf@ietf.org  Tue May 27 13:01:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18347
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 12:11:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kgih-0008Gv-B7
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 11:50:35 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KgcV-0008Ct-Lx
	for ietf@asgard.ietf.org; Tue, 27 May 2003 11:44:11 -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 LAA17488
	for <ietf@ietf.org>; Tue, 27 May 2003 11:44:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kgax-0005ZR-00
	for ietf@ietf.org; Tue, 27 May 2003 11:42:35 -0400
Received: from mail11.speakeasy.net ([216.254.0.211] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kgax-0005ZO-00
	for ietf@ietf.org; Tue, 27 May 2003 11:42:35 -0400
Received: (qmail 12874 invoked from network); 27 May 2003 15:44:07 -0000
Received: from unknown (HELO 192.168.254.124) ([66.92.168.196])
          (envelope-sender <dja2003@hotpop.com>)
          by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <ietf@soaring.demon.co.uk>; 27 May 2003 15:44:07 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: Andrew Shore <ietf@soaring.demon.co.uk>
Subject: Re: spam
Date: Tue, 27 May 2003 11:46:23 -0400
User-Agent: KMail/1.5
References: <200305261906.h4QJ63W7025426@ginger.lcs.mit.edu> <6DSBmjGUon0+EwXs@soaring.demon.co.uk>
In-Reply-To: <6DSBmjGUon0+EwXs@soaring.demon.co.uk>
Cc: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305271146.23511.dja2003@hotpop.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Monday 26 May 2003 16:33, Andrew Shore wrote:

 AS> One "technical" solution that would discourage spam would be to
 AS> add a key (a text string, for example) to the email header. The
 AS> user gives out their email address with different keys to
 AS> different groups of people; if a key attracts spam, all they
 AS> have to do is stop accepting mail with that key. It would also
 AS> make organising mail very easy. On the negative side, the extra
 AS> complexity might prove challenging for some...

http://www.sneakemail.com supplies something along those lines.  You can 
use their generated addresses for purposes such as posting to Usenet, 
posting to web forums, posting to mailing lists, signing up for various 
offers whose offerors you don't quite trust with your real address, 
etc.... and if an address starts accumulating spam, not only can you 
shut it off, you get an excellent clue how you were exposed.

-- 
David J. Aronson, unemployed Software Engineer in Washington DC area.
Go to http://destined.to/program/ for online resume, references, etc.




From owner-ietf@ietf.org  Tue May 27 13:08:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19839
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 13:08:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KhjY-0003MJ-WA
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 12:55:32 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Khix-0003Kw-S1
	for ietf@asgard.ietf.org; Tue, 27 May 2003 12:54:55 -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 MAA19442
	for <ietf@ietf.org>; Tue, 27 May 2003 12:54:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KhhF-00066i-00
	for ietf@ietf.org; Tue, 27 May 2003 12:53:09 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KhhF-00066W-00
	for ietf@ietf.org; Tue, 27 May 2003 12:53:09 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id MAA26970;
	Tue, 27 May 2003 12:48:04 -0400
Date: Tue, 27 May 2003 12:47:58 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Valdis.Kletnieks@vt.edu
cc: pdeutsch@earthlink.net, IETF Discussion <ietf@ietf.org>
Subject: Re: spam (fwd) (edit error on previous) 
In-Reply-To: <200305270232.h4R2WFJ2002333@turing-police.cc.vt.edu>
Message-ID: <Pine.LNX.4.44.0305271242260.7861-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

No, it is easy.  As Chris Neill of Verio abuse found out, after he was
fired for doing this. (He posted his story to spam-l, blaming me for
getting him fired).

It is pretty much just like Peter described.  The hard part is finding a
real person to prosecute. Usually, Type 1 spammers don't abuse open
relays.

AOL has prosecuted spammers for sending _them_ mail, under the CFAA, after
the company was notified not to send them mail. (I'll try to dig up the
cite. You can find it pretty easily on lexis by searching for cases on 18
USC 1030)  Searching for cases involving AOL seems to be a good way to
stay current on computer law. ;-)

		--Dean

On Mon, 26 May 2003 Valdis.Kletnieks@vt.edu wrote:

> On Mon, 26 May 2003 18:53:12 PDT, Peter Deutsch said:
>
> > The case we prosecuted turned out to be a small group of kids breaking
> > into compute hosts, but from what I was told I would think you should be
> > able to use the same provision against spam relayers, since the key
> > element was the unauthorized use of compute cycles, not what they did
> > with the cycles.
>
> IANAL by any means, but I suspect that the owner of an open relay would have
> a hard time demonstrating unauthorized use of cycles to relay mail *through
> an open relay*.  Now if the spammer actively *bypassed* a security feature
> in order to relay the mail, that would be different, as it would indicate
> that they knew it was unauthorized...
>




From owner-ietf@ietf.org  Tue May 27 13:28:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20446
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 13:28:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KhyJ-0003mc-Ey
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 13:10:47 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Khvk-0003UO-FJ
	for ietf@asgard.ietf.org; Tue, 27 May 2003 13:08:08 -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 NAA19862
	for <ietf@ietf.org>; Tue, 27 May 2003 13:08:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KhuC-0006DZ-00
	for ietf@ietf.org; Tue, 27 May 2003 13:06:32 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KhuC-0006DE-00
	for ietf@ietf.org; Tue, 27 May 2003 13:06:32 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id MAA11881;
	Tue, 27 May 2003 12:58:39 -0400
Date: Tue, 27 May 2003 12:58:33 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Peter Deutsch <pdeutsch@earthlink.net>
cc: Valdis.Kletnieks@vt.edu, IETF Discussion <ietf@ietf.org>
Subject: Re: spam (fwd) (edit error on previous)
In-Reply-To: <3ED2F7C1.1DADAFF0@earthlink.net>
Message-ID: <Pine.LNX.4.44.0305271252280.7861-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


On Mon, 26 May 2003, Peter Deutsch wrote:

>
>
> Valdis.Kletnieks@vt.edu wrote:
> >
> > On Mon, 26 May 2003 18:53:12 PDT, Peter Deutsch said:
> >
> > > The case we prosecuted turned out to be a small group of kids breaking
> > > into compute hosts, but from what I was told I would think you should be
> > > able to use the same provision against spam relayers, since the key
> > > element was the unauthorized use of compute cycles, not what they did
> > > with the cycles.
> >
> > IANAL by any means, but I suspect that the owner of an open relay would have
> > a hard time demonstrating unauthorized use of cycles to relay mail *through
> > an open relay*.  Now if the spammer actively *bypassed* a security feature
> > in order to relay the mail, that would be different, as it would indicate
> > that they knew it was unauthorized...
>
> Exaxtly, so you don't leave it open. Then, the only folks who would be
> using you as a relay would be a) folks you've authorized to do so.

There are customers who are not on our IP address space who are authorized
to use our relays. Thats why they are open.  That's why all ISPs who
operate open relays have them.  SMTP AUTH just doesn't solve the problem,
for a number of reasons.

> By definition the folks who are doing so without your authorization,
> would be breaking the law and we have an existance proof that this stuff
> is quite traceable and quite prosecutable.

Yes. That is correct. It is prosecutable whenever Type 1 or Type 2 abusers
do this. But it is usually Type 3 abusers conducting the abuse, and Type 3
is difficult to identify without Law Enforcement powers.

> As a bonus, the law they would be breaking isn't one that must, in the
> U.S. context, stand up to arguments about it supressing free speech and
> so on. And I have no trouble with this, since you have a right to say
> what you want, but I have a right not to listen, nor am I responsible
> for providing you with a soapbox and megaphone...





From owner-ietf@ietf.org  Tue May 27 13:33:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20768
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 13:33:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KiCa-0003wB-HV
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 13:25:32 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ki0K-0003oF-NE
	for ietf@asgard.ietf.org; Tue, 27 May 2003 13:12:52 -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 NAA20067
	for <ietf@ietf.org>; Tue, 27 May 2003 13:12:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Khym-0006Ga-00
	for ietf@ietf.org; Tue, 27 May 2003 13:11:17 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Khyl-0006GX-00
	for ietf@ietf.org; Tue, 27 May 2003 13:11:16 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4RHCnjh012880
	for <ietf@ietf.org>; Tue, 27 May 2003 19:12:49 +0200 (CEST)
Message-ID: <034201c32473$334b2eb0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.44.0305261909330.3699-100000@commander.av8.net> <016101c323e1$e1ae5be0$0a00000a@atkielski.com> <3ED2C508.8E2CFA44@earthlink.net> <023601c3241f$07a4c1d0$0a00000a@atkielski.com> <3ED37724.56B53F25@earthlink.net>
Subject: Re: spam (fwd) (edit error on previous)
Date: Tue, 27 May 2003 19:12:49 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Peter writes:

> Do please pay attention, this will all be on the exam.

That's one of my problems.  I pay too much attention, and then people get
irritated when I see what they missed.

> First, I didn't say "explicit authorization".

You didn't have to.  See, the applicability of a law is decided in court,
not by Peter Deutsch.  Thus, your notion of whether or not a law applies is
little more than conjecture until it is confirmed or invalidated by a court
of law.  Even explicitly-worded statutes are still subject to interpretation
by the courts.  You cannot really say in advance how a specific case will
go, particularly when no existing jurisprudence for similar cases points the
way.

> It's generally considered poor debating style to put
> words into the mouths of others so as to appear to
> win a point.

I know of even more disreputable practices in debate.

> Next, by subscribing to this list, you are granting
> implicit permission to the list operator to connect
> to your machine to deliver list-related email.

Well, no.  Maybe I am, maybe I'm not.  A court would have to decide.  It
seems logical to me, but I'm not a judge, and judges don't always seem to be
logical.  Juries are even worse.

> If I were to take this example to the RCMP, I would
> fully expect to be told that no crime was committed,
> because implicit authorization was obviously granted.

The RCMP is an enforcement agency, not a judicial agency.  They don't decide
who is or isn't guilty of a crime (as far as I know).

> Note, in signing up to a mailing list, you have
> *not* granted permission to the list operator to send
> fragments of code intended to run your implementation
> of the Distributed Halting Problem ...

Here again, that still has not been decided, and some recent cases have
raised questions along those lines.

> Because it's something you can control by, for
> example, choosing not to visit the site.

But I don't know what the site will do until I visit it (similar to the
problem of shrink-wrapped licenses, which you cannot read without accepting
them).

> This is fundamentally difference from logging onto
> someone else's machine and using it for your purposes with
> such an implicit contract.

But that's _exactly_ what I'm doing when I send a Web query to a machine!

> What's your point?

Sysadmins are supposed to be past the learning curve already.





From owner-ietf@ietf.org  Tue May 27 13:45:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21129
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 13:45:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KiCa-0003wd-Tb
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 13:25:32 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ki3w-0003pH-Kf
	for ietf@asgard.ietf.org; Tue, 27 May 2003 13:16:36 -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 NAA20171
	for <ietf@ietf.org>; Tue, 27 May 2003 13:16:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ki2O-0006HS-00
	for ietf@ietf.org; Tue, 27 May 2003 13:15:00 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ki2N-0006HP-00
	for ietf@ietf.org; Tue, 27 May 2003 13:14:59 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h4RHHXxS016258;
	Tue, 27 May 2003 19:17:34 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Tue, 27 May 2003 19:16:37 +0200
Subject: Re: Simple Internet Protocol, Again
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Soohong Daniel Park <soohong.park@samsung.com>, ietf@ietf.org
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <200305270135.KAA02345@necom830.hpcl.titech.ac.jp>
Message-Id: <F94E7D1E-9066-11D7-81E4-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On dinsdag, mei 27, 2003, at 03:35 Europe/Amsterdam, Masataka Ohta 
wrote:

>> I've looked over your draft quickly, however I don't see
>> what applicability statement is possible.

> It is a reality check agaist people dreaming of magical
> deployment of IPv6.

> It can also be a proposal to shutdown activities to further
> complicate IPv6.

One of your objections against IPv6 as-is is that it is hard to 
implement. But by now a good number of vendors have implemented. 
Wouldn't "simplifying" existing code and increasing the 
interoperability mess (v4, v6complex and v6"simple") be a bigger hassle 
than simply using IPv6 the way it is now?




From owner-ietf@ietf.org  Tue May 27 13:45:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21202
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 13:45:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KiCb-0003x4-7m
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 13:25:33 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ki96-0003uY-Iu
	for ietf@asgard.ietf.org; Tue, 27 May 2003 13:21:56 -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 NAA20278
	for <ietf@ietf.org>; Tue, 27 May 2003 13:21:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ki7Y-0006IY-00
	for ietf@ietf.org; Tue, 27 May 2003 13:20:20 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ki7Y-0006IV-00
	for ietf@ietf.org; Tue, 27 May 2003 13:20:20 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4RHLsjh012952
	for <ietf@ietf.org>; Tue, 27 May 2003 19:21:54 +0200 (CEST)
Message-ID: <034f01c32474$77e61700$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <963621801C6D3E4A9CF454A1972AE8F504F827@server2000.arneill-py.sacramento.ca.us><g3fzn1udu7.fsf@sa.vix.com><026301c32420$b3d01da0$0a00000a@atkielski.com> <ylk7cc1kn2.fsf@windlord.stanford.edu>
Subject: Re: spam
Date: Tue, 27 May 2003 19:21:54 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Russ writes:

> So does trying to find the legitimate mail among
> a pile of spam.

The difference is that, in the first case, legitimate e-mail is lost,
whereas in the second case, legitimate e-mail is preserved.

> It's reality-check time.  We're not going to get that,
> and the problem is continuing to get worse.  Now what?

Stop replying to spam.  Somebody is _buying_ the penis enlargement kits, and
the mortgage refinancing, and the pallet-loads of Viagra, somewhere,
otherwise spam wouldn't be worth the trouble.

I have an idea that is kind of odd, and I don't know if it would work.  I
really wouldn't mind signing up for a service that sends me filtered
advertising, in domains that I find _specifically_ interesting.  I'd be
happy to read about products and services that directly address my needs and
interests, and if such a service existed, I'd be tempted to sign up.  So
what if such services did exist on a widespread basis, and everyone signed
up for them?  Would there still be a need for spam?  Wouldn't it be cheaper,
in that case, for the spammers to send targeted e-mail to people who have
already expressed an interest in their products?

Not only that, such a service could insert a unique character string in the
subject line of each e-mail, unique for each subscriber.  Then the
subscriber could filter on this string, routing interesting commercial
e-mail to a special folder.  Since it would be unique by subscriber,
non-participating merchants couldn't fake it.

I don't know if that would work or not.  But it's a thought.

> How many people who are active and have been active
> for some time on the Internet are still putting e-mail
> addresses on web pages and then reading them with no
> spam filtering whatsoever, just looking through the
> inbox and deleting what isn't wanted?

My e-mail address is on my Web site.  People need a way to contact me.  I
read all incoming e-mail, except e-mail from domains that bounce my mail
(e.g., AOL, which I bounce right back with a nasty message intended to scare
subscribers).  I check all messages and delete the spam.  Right now
freebsd.org is spamming me pretty actively, but I don't see that in my inbox
because there on my bounce list for the same reason as AOL.

> How many of you have accidentally discarded the
> wrong message because it got caught in a purge of
> spam from your inbox?

It happens once in a while.  I try to be careful.

> Personally, I can still cope with the onslaught
> with no filtering other than a few simple personal
> rules based on observation of my incoming spam
> and the types of messages I personally receive,
> but those rules are utterly draconian from certain
> perspectives and still vulnerable to false positives
> (for example, I don't speak any Asian language, so
> anything I receive in that character set goes straight
> into the spam pile ...

I do the same thing.  Any large messages get set aside, since 99% of them
are spam.  Anything in HTML is set aside, too, since almost no legitimate
e-mail is ever in HTML.  That already eliminates an awful lot.

Another filter I've been thinking of is one that sets aside anything
containing character strings that aren't in a dictionary of English words,
but I have no easy way of implementing that.





From owner-ietf@ietf.org  Tue May 27 13:47:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21422
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 13:47:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KiCb-0003xA-IL
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 13:25:33 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ki9w-0003ub-FL
	for ietf@asgard.ietf.org; Tue, 27 May 2003 13:22:48 -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 NAA20284
	for <ietf@ietf.org>; Tue, 27 May 2003 13:22:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ki8O-0006Ie-00
	for ietf@ietf.org; Tue, 27 May 2003 13:21:12 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ki8O-0006Ib-00
	for ietf@ietf.org; Tue, 27 May 2003 13:21:12 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id NAA04140;
	Tue, 27 May 2003 13:15:42 -0400
Date: Tue, 27 May 2003 13:16:30 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Paul Vixie <vixie@vix.com>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <g3fzn1udu7.fsf@sa.vix.com>
Message-ID: <Pine.LNX.4.44.0305271307040.7861-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

You seem to be missing the issue of Shannon's theorem.  The IETF is about
protocols, not about collecting and sharing statistics for bayesian
filters.

It is not the case that nothing can be done about spam. However, it is the
case that _protocols_ can do nothing about spam.  So, there is nothing for
the IETF to do, any more than the IETF can do anything to catch terrorists
such as Al Quaeda, who also abuse the communications infrastructure.

Try to recast all of your arguments to stop terrorists instead of
spammers, and you will see just how foolish they are.

"Osama bin Laden halted from communicating with Al Quaeda cells by closing
open relays".  Obviously not. So why would you think open relays have
anything whatsoever to do with spam? (because radical anti-spammers think
they must, and they conduct abuse of them, perhaps.)  Once you do that,
you will see what crusades are foolish.

		--Dean

On 27 May 2003, Paul Vixie wrote:

> michel@arneill-py.sacramento.ca.us ("Michel Py") writes:
>
> > Paul, I'm curious: why are you wasting your time with this? Any
> > withdrawals from not fighting it on a daily basis?
>
> because several years ago when iesg commissioned a wg to study the spam
> issue and decide whether ietf had a role, the carefully worded answer was
> "no".  i thought this answer was short-sighted or wrong-headed or both.
>
> c'mon guys & dolls, smtp and the model behind/beneath it are failing to
> address the need for universal batch communication.  we fixed the encoding
> problems (trying to fit things into a 990-by-7 box was hard without mime)
> and it only took four and a half years of bitchfesting and the results have
> been nothing less than spectacular (in that i don't get uuencoded tarballs
> from nextstep users any more.)
>
> on april 28 of this year, aol/microsoft/yahoo publically teamed up to fight
> spam (since statistically speaking, it is universally launched by their
> collective customers and aimed at their collective customers.)  see
> http://www.nwfusion.com/news/2003/0428aolmsya.html for the announcement.
> does anyone here think this will solve the problem for anybody, even the
> customers of those three customers?
>
> i'm wasting my time because i want this problem looked at more broadly.
> --
> Paul Vixie
>
>




From owner-ietf@ietf.org  Tue May 27 13:59:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21874
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 13:59:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KiaH-000628-VI
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 13:50:01 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KiFT-0003xi-Ur
	for ietf@asgard.ietf.org; Tue, 27 May 2003 13:28:31 -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 NAA20428
	for <ietf@ietf.org>; Tue, 27 May 2003 13:28:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KiDw-0006LH-00
	for ietf@ietf.org; Tue, 27 May 2003 13:26:56 -0400
Received: from [195.167.170.152] (helo=bowl.fysh.org ident=mail)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KiDv-0006LD-00
	for ietf@ietf.org; Tue, 27 May 2003 13:26:55 -0400
Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian))
	id 19KiFL-0006wQ-00; Tue, 27 May 2003 18:28:23 +0100
Date: Tue, 27 May 2003 18:28:23 +0100
To: Russ Allbery <rra@stanford.edu>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: spam
Message-ID: <20030527172823.GA20601@fysh.org>
References: <963621801C6D3E4A9CF454A1972AE8F504F827@server2000.arneill-py.sacramento.ca.us> <g3fzn1udu7.fsf@sa.vix.com> <026301c32420$b3d01da0$0a00000a@atkielski.com> <ylk7cc1kn2.fsf@windlord.stanford.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ylk7cc1kn2.fsf@windlord.stanford.edu>
User-Agent: Mutt/1.3.28i
From: Zefram <zefram@fysh.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

Russ Allbery wrote:
>How many people who are active and have been active for some time on the
>Internet are still putting e-mail addresses on web pages and then reading
>them with no spam filtering whatsoever, just looking through the inbox and
>deleting what isn't wanted?

I do, and I don't think I've ever had a false positive.  I get 5 to 10
spam messages per day, though this is increasing.

Professionally, I'm currently developing a Bayesian spam filter.
My intention is to eventually apply such a system to my private mail.
The results I've had so far are enough to almost entirely solve my spam
problem for the next couple of years: it currently stops 98% of spam in
tests, and gets false positives only on messages that look a lot like
spam to me.  I also know I can still improve the filter a long way,
a lot faster than the spammers can learn to dodge such filters.

With Bayesian filters being this effective, I'm not worried about spam
in the immediate future.  Proper application of filtering keeps us
inherently one step ahead of the spammers in the arms race -- they have
to do something *completely* unlike what they've done before in order
to fool us.  For this reason, I'm opposed to those anti-spam measures
that reduce the email network's tolerance for unsolicited or anonymous
messages.  I've seen rather too many proposals that would destroy the
openness of the email system in order to make spam more difficult --
and most of them would disproportionately hurt legitimate email, putting
up barriers that spammers would easily bypass.

Whether the receiving-end filtering approach is viable in the long
term is debateable.  When 99.9% of email is spam, the filtering world
will look very different.  Perhaps at that point it'll be infeasible to
continue allowing unsolicited email at all.

-zefram



From owner-ietf@ietf.org  Tue May 27 14:07:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22148
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 14:07:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KiaI-00062p-DE
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 13:50:02 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KiGT-0004Id-ST
	for ietf@asgard.ietf.org; Tue, 27 May 2003 13:29:33 -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 NAA20506
	for <ietf@ietf.org>; Tue, 27 May 2003 13:29:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KiEw-0006N3-00
	for ietf@ietf.org; Tue, 27 May 2003 13:27:58 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KiEv-0006N0-00
	for ietf@ietf.org; Tue, 27 May 2003 13:27:57 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h4RHTUk07961;
        Tue, 27 May 2003 13:29:31 -0400 (EDT)
Date: Tue, 27 May 2003 13:29:30 -0400
From: Keith Moore <moore@cs.utk.edu>
To: ietf@ietf.org
Cc: moore@cs.utk.edu
Subject: please move the spam discussion elsewhere
Message-Id: <20030527132930.3210e276.moore@cs.utk.edu>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

It's not that spam isn't an important problem, nor that it's entirely
out of scope for IETF.   But the lack of agreement on the nature of the
problem, along with the level of naivete in these discussions, suggest
that it will be a long time before these discussions can hope to bear
useful fruit.  And this isn't a particularly effective venue to work
on that problem.

If nothing else, the NSRG antispam research group has been talking about
this for several months, and there's no point in repeating the same
arguments on the IETF list that they've been having over there.

see https://www1.ietf.org/mailman/listinfo/asrg




From owner-ietf@ietf.org  Tue May 27 14:24:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22717
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 14:24:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KiuB-0007AD-Kh
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 14:10:35 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kifx-0006Co-3p
	for ietf@asgard.ietf.org; Tue, 27 May 2003 13:55:53 -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 NAA21722
	for <ietf@ietf.org>; Tue, 27 May 2003 13:55:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KieP-0006gb-00
	for ietf@ietf.org; Tue, 27 May 2003 13:54:17 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KieO-0006gT-00
	for ietf@ietf.org; Tue, 27 May 2003 13:54:16 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 00F1C1396C; Tue, 27 May 2003 17:55:20 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: spam
References: <024901c3241f$7a2d96a0$0a00000a@atkielski.com>
From: Paul Vixie <vixie@vix.com>
Date: 27 May 2003 17:55:20 +0000
In-Reply-To: <024901c3241f$7a2d96a0$0a00000a@atkielski.com>
Message-ID: <g3brxouvef.fsf@sa.vix.com>
Lines: 35
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

> > warning, i'm answering an obvious troll from an obvious spammer.  [...]
> 
> In other words, you disagree with me, but for reasons I won't go into,
> you cannot resist the urge to reply.

actually, i can speak for myself, there's no need to interpret for me.

i'm calling you a troll because you're urging people to pay no attention
to the costs, to just hit delete, and to avoid filtering since you claim
that the costs of false positives are too high.  that's three for three.
those are the three key issues that every spammer-in-troll raises whenever
they join public debates on the issue of spam.  usually it takes a week,
but you did it all in 36 hours.  congrats?

> > my t1 costs me $552 per month in pac bell service fees.
> 
> Is it 100% busy?  If not, spam effectively costs you nothing, since I
> assume you pay a flat rate for a fixed, continuously-available bandwidth.

you act as if headroom would have no value.  maybe that's true for you but
again i'll suggest that you avoid trying to interpret for me unless you're
offering to pay me $552 per month in perpetuity.

> > how nice for you.  here's the report of spam that's reached me and had
> > to be deleted in the last 15 days:
> 
> If spam is so expensive, why are you logging and analyzing it?  Doesn't
> that raise the cost?  I just throw it away.

in order to get 20:1 rejection rates at the smtp level, i have to analyze
the stuff.  since the major cost is in receiving it, the minor inconvenience
of storing and analyzing it is pretty low.  the better my analysis, the less
i receive, so it's all about risk-management in this unpoliced metaworld.
-- 
Paul Vixie



From owner-ietf@ietf.org  Tue May 27 14:28:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22934
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 14:28:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KiuC-0007AT-0D
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 14:10:36 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KihV-0006Lm-9P
	for ietf@asgard.ietf.org; Tue, 27 May 2003 13:57:29 -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 NAA21755
	for <ietf@ietf.org>; Tue, 27 May 2003 13:57:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kifw-0006hA-00
	for ietf@ietf.org; Tue, 27 May 2003 13:55:52 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kifv-0006h7-00
	for ietf@ietf.org; Tue, 27 May 2003 13:55:51 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id NAA00952;
	Tue, 27 May 2003 13:52:34 -0400
Date: Tue, 27 May 2003 13:52:47 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: ietf@ietf.org
cc: tech-contact@sphere.ad.jp, <staff@db.nic.ad.jp>, <sysadm@HPO.NET>
Subject: Re: Re: spam (fwd)
Message-ID: <Pine.LNX.4.44.0305271348000.7861-101000@commander.av8.net>
MIME-Version: 1.0
Content-Type: MULTIPART/Mixed; BOUNDARY="----=_NextPart_000_00C5_01C2FE98.C9E1D5A0"
Content-ID: <Pine.LNX.4.44.0305271348020.7861@commander.av8.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

------=_NextPart_000_00C5_01C2FE98.C9E1D5A0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.44.0305271348021.7861@commander.av8.net>

Speaking of abuse, every message I send to the ietf list is getting
responded to as follows (with virus included)

Please remove this user.

Thanks,

		--Dean



---------- Forwarded message ----------
Return-Path: <dinuka@hpo.net>
Received: from odie.av8.com (odie.av8.com [198.3.136.133] (may be forged))
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id AAA07095
	for <dean@citation.av8.net>; Tue, 27 May 2003 00:14:07 -0400
Received: from alexandria.hpo.net (alexandria.hpo.net [219.106.225.71])
	by odie.av8.com (8.9.3/8.8.5) with ESMTP id AAA28368
	for <dean@av8.com>; Tue, 27 May 2003 00:09:52 -0400 (EDT)
Received: from pl706.nas922.n-yokohama.nttpc.ne.jp ([210.139.120.194]
    helo=seawolf)
	by alexandria.hpo.net with smtp (Exim 4.12)
	id 19KVwK-0004wG-00
	for dean@av8.com; Tue, 27 May 2003 13:19:56 +0900
Message-ID: <01e301c2fe4e$0e781490$c2788bd2@seawolf>
From: "dinuka" <dinuka@hpo.net>
To: <dean@av8.com>
Subject: Re: Re: spam
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_00C5_01C2FE98.C9E1D5A0"
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Date: Tue, 27 May 2003 13:19:56 +0900
X-MailScanner: Found to be clean

'Dean Anderson' wrote:
====
> I haven't seen this activity related to bonafide (Type 1 or Type 2)
> spam, though I've heard anti-spammers say this a lot.
>
> By definition, this is bidirectional communication. I've only seen it
> abused by fake opt-out addresses that are either directly annoyance
> related (eg, send IM floods) or send more email annoyance.  For example,
> I've observed that responding to 20 Nigerian 411 scams resulted in no
> solicitation of personal information, one response about  ...'
====

 av8.com account auto-reply:

  If you can keep your head when all about you
  Are losing theirs and blaming it on you;
  If you can trust yourself when all men doubt you,
  But make allowance for their doubting too;
  If you can wait and not be tired by waiting,
  Or, being lied about,don't deal in lies,
  Or, being hated, don't give way to hating,
  And yet don't look too good, nor talk too wise;
  ... ... more  look to the attachment.


	> Get your FREE av8.com account now! <


------=_NextPart_000_00C5_01C2FE98.C9E1D5A0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

[Filename: dreamweaver MX (crack).exe, Content-Type: APPLICATION/X-MSDOWNLOAD]
The attachment file in the message has been removed by eManager.

------=_NextPart_000_00C5_01C2FE98.C9E1D5A0--



From owner-ietf@ietf.org  Tue May 27 14:29:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22982
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 14:29:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KiuC-0007Ap-Ar
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 14:10:36 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kiix-0006Lx-0s
	for ietf@asgard.ietf.org; Tue, 27 May 2003 13:58:59 -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 NAA21843
	for <ietf@ietf.org>; Tue, 27 May 2003 13:58:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KihP-0006iP-00
	for ietf@ietf.org; Tue, 27 May 2003 13:57:23 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KihO-0006i5-00
	for ietf@ietf.org; Tue, 27 May 2003 13:57:22 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207938 for ietf@ietf.org; Tue, 27 May 2003 12:58:19 -0500
Message-ID: <3ED3A759.3010806@ehsco.com>
Date: Tue, 27 May 2003 12:58:49 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: spam
References: <963621801C6D3E4A9CF454A1972AE8F504F827@server2000.arneill-py.sacramento.ca.us><g3fzn1udu7.fsf@sa.vix.com><026301c32420$b3d01da0$0a00000a@atkielski.com> <ylk7cc1kn2.fsf@windlord.stanford.edu> <034f01c32474$77e61700$0a00000a@atkielski.com>
In-Reply-To: <034f01c32474$77e61700$0a00000a@atkielski.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/27/2003 12:21 PM Anthony Atkielski wrote:

> I have an idea that is kind of odd, and I don't know if it would work.
> I really wouldn't mind signing up for a service that sends me filtered 
> advertising, in domains that I find _specifically_ interesting.  I'd be
> happy to read about products and services that directly address my
> needs and interests, and if such a service existed, I'd be tempted to
> sign up.  So what if such services did exist on a widespread basis, and
> everyone signed up for them?  Would there still be a need for spam?

People would still want to tell everybody about their products. They would
even believe that if you aren't monitoring their specific domain, it's
only because you don't fully appreciate the benefits of their products.

To quote a bulk-mailer:

http://www.nytimes.com/2003/05/25/business/yourmoney/25SPAM.html?pagewanted=3

| MICHAEL P. SHERMAN

| Q. What's wrong with the idea that people should have to "opt in" to
| get commercial e-mail?
|
| A. Do you ask for advertising? Advertising introduces someone to a new
| idea. How are you going to do that? People aren't going to say, "I
| want something new today, so I want an e-mail from you."

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Tue May 27 14:33:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23230
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 14:33:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KiuC-0007BG-Ns
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 14:10:36 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KijU-0006Qx-IO
	for ietf@asgard.ietf.org; Tue, 27 May 2003 13:59:32 -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 NAA21895
	for <ietf@ietf.org>; Tue, 27 May 2003 13:59:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kihw-0006j1-00
	for ietf@ietf.org; Tue, 27 May 2003 13:57:56 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kihw-0006iU-00
	for ietf@ietf.org; Tue, 27 May 2003 13:57:56 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 92B891396F; Tue, 27 May 2003 17:59:00 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: spam
References: <026301c32420$b3d01da0$0a00000a@atkielski.com>
From: Paul Vixie <vixie@vix.com>
Date: 27 May 2003 17:59:00 +0000
In-Reply-To: <026301c32420$b3d01da0$0a00000a@atkielski.com>
Message-ID: <g37k8cuv8b.fsf@sa.vix.com>
Lines: 25
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

> > does anyone here think this will solve the problem for anybody, even
> > the customers of those three customers?
> 
> Their "anti-spam" efforts cause them to reject millions of legitimate
> e-mails each day, so they create problems, too.

"bing!"

> > i'm wasting my time because i want this problem looked at more broadly.
> 
> What process can you suggest to distinguish spam from legitimate e-mail
> with 100% reliability and no human intervention?  Find that, and you can
> become a billionnaire.

i guess we're on different wavelengths.  you're talking e-mail even after
i ripped smtp from stem to sternum here yesterday.  i'm not going to try
to educate you about what smtp is or where it lives in the grand spectrum
of things.

but for the lurkers, i'll simply point out that there is no reason for
confidence in the identity of a sender, or the intentions of a relay/proxy,
or the value to the sender of the reception of the message.  all of these
can be proved in real time.  but not using smtp as it exists today.
-- 
Paul Vixie



From owner-ietf@ietf.org  Tue May 27 14:39:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23594
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 14:39:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KiuD-0007DV-Fu
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 14:10:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kirf-00076L-CJ
	for ietf@asgard.ietf.org; Tue, 27 May 2003 14:07:59 -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 OAA22183
	for <ietf@ietf.org>; Tue, 27 May 2003 14:07:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kiq7-0006oG-00
	for ietf@ietf.org; Tue, 27 May 2003 14:06:23 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kiq6-0006o8-00
	for ietf@ietf.org; Tue, 27 May 2003 14:06:22 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h4RI8rxS016329;
	Tue, 27 May 2003 20:08:53 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Tue, 27 May 2003 20:07:57 +0200
Subject: Re: spam
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: "Eric A. Hall" <ehall@ehsco.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <3ED25E99.80007@ehsco.com>
Message-Id: <2528F9EE-906E-11D7-81E4-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On maandag, mei 26, 2003, at 20:36 Europe/Amsterdam, Eric A. Hall wrote:

>> The issue of detecting abuse was the focus of the MIT anti-spam
>> conference.  There are many paths presently being pursued: Blacklists,
>> header analysis, and various kinds of content analysis.  I think the
>> general consensus was that content analysis offers the most promising
>> means of detecting and blocking abuse.

> The problem is that this defines defeat as victory.

> There is also existent proof that filtering is only "mostly" 
> successful at
> even its limited role. There are plenty of problems with false 
> positives,
> delayed positives, and so forth,

Exactly. Filtering and then checking for false positives is marginally 
better than nothing, but it doesn't really solve anything, especially 
as the spammers get smarter. Smart filters also use significant 
resources.

Spammers spam for a variety of reasons, with making money high on the 
list. They will continue to do it as long as:

1. they get the return they're looking for
2. it's relatively easy to do
3. they get away with it

Number one should be addressed by no longer doing business with 
spammers. I immediately cancelled my subscription to the paper when thy 
started spamming. But they're still in business so I gues most people 
didn't care as much as me.

Number two is an area where the IETF could actually do something 
useful. The way things are today, everyone can contact any mailserver 
and expect the message to be delivered. Now this is a nice way to build 
a distributed mail system, until such time that spammers pop up, 
bombard mail servers around the world with their enlargement ads, and 
when they are shut down they simply move to another IP address and 
resume their abuse. If we mandate an extension to SMTP to signal an 
unknown mail server that it should either

a. find a known server to forward the message, or
b. go through some kind of (off-line) procedure to become accredited

people who send small amounts of mail can simply be instructed to use 
their ISP's mail server while those who send lots of legitimate mail 
can be whitelisted. Spammers are presumably stopped when they flood 
their ISP's mail server or they lose their white list status.

For number three we need the law. Here in Holland we had a case where 
an ISP sued a well known Dutch spamming outfit. The original ruling 
that the spammers had to stop spamming the customers of this ISP or pay 
a fine for each spam was overturned on appeal: after all, people had to 
opportunity to unsubscribe.

> Eric A. Hall                                        
> http://www.ehsco.com/
> Internet Core Protocols          
> http://www.oreilly.com/catalog/coreprot/

I didn't know O'Reilly required us to put links to our books in our 
signatures. Here's mine: http://www.oreilly.com/catalog/bgp/




From owner-ietf@ietf.org  Tue May 27 14:42:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23761
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 14:42:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KiuE-0007Ey-44
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 14:10:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kitn-00077Q-Hz
	for ietf@asgard.ietf.org; Tue, 27 May 2003 14:10:11 -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 OAA22281
	for <ietf@ietf.org>; Tue, 27 May 2003 14:10:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KisF-0006qI-00
	for ietf@ietf.org; Tue, 27 May 2003 14:08:35 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KisF-0006qF-00
	for ietf@ietf.org; Tue, 27 May 2003 14:08:35 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h4RIA8tU002650;
	Tue, 27 May 2003 14:10:08 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h4RIA8eG002649;
	Tue, 27 May 2003 14:10:08 -0400
Date: Tue, 27 May 2003 14:10:08 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200305271810.h4RIA8eG002649@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: spam
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: Dean Anderson <dean@av8.com>

    > it is the case that _protocols_ can do nothing about spam. So, there is
    > nothing for the IETF to do

Not necessarily so.

First, if people agree that charging for email is needed, or some equally
significant change (and clearly the existing SMTP-based email system is an
open door for spam, and always will be), then that means a new protocol,
which the IETF will have to design.

Moreover, in the public policy debate that is going on now, policy makers
need to know what technical options are avaiable as they look at the spectrum
of possible solutions (legal, technical, etc). The IETF has a role to play
there, too.

	Noel



From owner-ietf@ietf.org  Tue May 27 14:42:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23845
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 14:42:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KiuE-0007F4-KW
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 14:10:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kiu6-00077S-3K
	for ietf@asgard.ietf.org; Tue, 27 May 2003 14:10:30 -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 OAA22287
	for <ietf@ietf.org>; Tue, 27 May 2003 14:10:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KisY-0006qQ-00
	for ietf@ietf.org; Tue, 27 May 2003 14:08:54 -0400
Received: from [131.227.76.5] (helo=prue.eim.surrey.ac.uk ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KisX-0006qN-00
	for ietf@ietf.org; Tue, 27 May 2003 14:08:53 -0400
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 19KitT-00074H-00; Tue, 27 May 2003 19:09:51 +0100
Date: Tue, 27 May 2003 19:09:50 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Andrew Shore <ietf@soaring.demon.co.uk>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <200305271146.23511.dja2003@hotpop.com>
Message-ID: <Pine.GSO.4.50.0305271829490.10590-100000@artemis.ee.surrey.ac.uk>
References: <200305261906.h4QJ63W7025426@ginger.lcs.mit.edu>
 <6DSBmjGUon0+EwXs@soaring.demon.co.uk> <200305271146.23511.dja2003@hotpop.com>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-105.7 required=5.5
	tests=AWL,BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,REFERENCES,
	      REPLY_WITH_QUOTES,USER_AGENT_PINE,USER_IN_WHITELIST
	version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
X-Scanner: exiscan *19KitT-00074H-00*q48oDZ1gXrY* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Monday 26 May 2003 16:33, Andrew Shore wrote:

AS> One "technical" solution that would discourage spam would be to
AS> add a key (a text string, for example) to the email header. The
AS> user gives out their email address with different keys to
AS> different groups of people; if a key attracts spam, all they
AS> have to do is stop accepting mail with that key. It would also
AS> make organising mail very easy. On the negative side, the extra
AS> complexity might prove challenging for some...

Multiple keys is too much like hard work.
Dan Kohn can probably tell you about the single text-string
key in mail headers promoted by http://www.habeas.com/ ...

What about some form of reverse verification via SMTP? After you
receive a mail, the receiver could open up a separate SMTP/TCP
connection back to the purported sender, asking 'did you send me this'
and asking for some sort of verification from logs? Might cut down on
spoofing;  possibly better than the minimum reverse lookup, since it
distinguishes spoofed from passed-through content, and gives you a
tighter audit trail of sorts.

L.

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>



From owner-ietf@ietf.org  Tue May 27 15:01:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24898
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 15:01:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KjTa-0001TN-05
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 14:47:10 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kj0P-0007H4-JE
	for ietf@asgard.ietf.org; Tue, 27 May 2003 14:17:01 -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 OAA22448
	for <ietf@ietf.org>; Tue, 27 May 2003 14:16:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kiyr-0006sy-00
	for ietf@ietf.org; Tue, 27 May 2003 14:15:25 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kiyo-0006sj-00
	for ietf@ietf.org; Tue, 27 May 2003 14:15:23 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4RIGmjh013431
	for <ietf@ietf.org>; Tue, 27 May 2003 20:16:48 +0200 (CEST)
Message-ID: <03a901c3247c$23885df0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <20030527132930.3210e276.moore@cs.utk.edu>
Subject: Re: please move the spam discussion elsewhere
Date: Tue, 27 May 2003 20:16:48 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Right now, there is probably no other greater problem with the Internet than
spam.  That sounds more than important enough to justify discussion here.
You can delete any messages that mention spam, if you want.

----- Original Message -----
From: "Keith Moore" <moore@cs.utk.edu>
To: <ietf@ietf.org>
Cc: <moore@cs.utk.edu>
Sent: Tuesday, May 27, 2003 19:29
Subject: please move the spam discussion elsewhere


> It's not that spam isn't an important problem, nor that it's entirely
> out of scope for IETF.   But the lack of agreement on the nature of the
> problem, along with the level of naivete in these discussions, suggest
> that it will be a long time before these discussions can hope to bear
> useful fruit.  And this isn't a particularly effective venue to work
> on that problem.
>
> If nothing else, the NSRG antispam research group has been talking about
> this for several months, and there's no point in repeating the same
> arguments on the IETF list that they've been having over there.
>
> see https://www1.ietf.org/mailman/listinfo/asrg
>
>
>




From owner-ietf@ietf.org  Tue May 27 15:20:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26796
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 15:20:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KjYf-0001e2-JO
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 14:52:25 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KjEB-0008OM-1Z
	for ietf@asgard.ietf.org; Tue, 27 May 2003 14:31:15 -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 OAA23186
	for <ietf@ietf.org>; Tue, 27 May 2003 14:31:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KjCd-00074p-00
	for ietf@ietf.org; Tue, 27 May 2003 14:29:39 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KjCb-00074h-00
	for ietf@ietf.org; Tue, 27 May 2003 14:29:37 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4RIV9jh013563
	for <ietf@ietf.org>; Tue, 27 May 2003 20:31:09 +0200 (CEST)
Message-ID: <03af01c3247e$2454ead0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <024901c3241f$7a2d96a0$0a00000a@atkielski.com> <g3brxouvef.fsf@sa.vix.com>
Subject: Re: spam
Date: Tue, 27 May 2003 20:31:08 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Paul writes:

> actually, i can speak for myself, there's no need
> to interpret for me.

You may not be saying what you are thinking, however.

> i'm calling you a troll because you're urging
> people to pay no attention to the costs, to just
> hit delete, and to avoid filtering since you claim
> that the costs of false positives are too high.

You're calling me a troll because you disagree with me, and you hope to make
your opinion seem more objectively valid than mine by discrediting me
personally.  It's a poor debate technique, and not very persuasive to those
who are aware of the fallacy it contains.

> those are the three key issues that every
> spammer-in-troll raises whenever they join public
> debates on the issue of spam.

I wouldn't know, as I don't recall having (knowingly) talked to spammers
directly.

> usually it takes a week, but you did it all in
> 36 hours.  congrats?

I'm afraid I don't understand.

> you act as if headroom would have no value.

It depends on the SD of the traffic and the desired uptime.  Yes, as a
matter of fact, I do know queuing theory, although it has been a few decades
since I last used it to any extent.

> maybe that's true for you but again i'll suggest
> that you avoid trying to interpret for me unless you're
> offering to pay me $552 per month in perpetuity.

Since you've interpreted for me by making assumptions about my costs for
false positives and use of the delete key, I'm surprised that you object to
any assumptions I make concerning your costs.

But I'm speaking of a general case, not your case or mine.

> in order to get 20:1 rejection rates at the smtp level,
> i have to analyze the stuff.

How do you analyze stuff you reject?  Isn't the whole idea of rejection to
avoid processing?  And doesn't analysis require processing?

> since the major cost is in receiving it, the minor
> inconvenience of storing and analyzing it is pretty low.

But if you are storing and analyzing it, you're still paying the major cost
of receiving it.

> the better my analysis, the less i receive ...

How do you avoid receiving what you don't want without any analysis or
storage?





From owner-ietf@ietf.org  Tue May 27 15:20:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26811
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 15:20:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KjTa-0001U0-Mq
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 14:47:10 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kj2W-0007Hv-Jj
	for ietf@asgard.ietf.org; Tue, 27 May 2003 14:19:12 -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 OAA22524
	for <ietf@ietf.org>; Tue, 27 May 2003 14:19:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kj0y-0006uD-00
	for ietf@ietf.org; Tue, 27 May 2003 14:17:36 -0400
Received: from carwash.centive.com ([65.220.90.249] helo=carwash.centivinc.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19Kj0y-0006u9-00
	for ietf@ietf.org; Tue, 27 May 2003 14:17:36 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003052714253211202
 for <ietf@ietf.org>; Tue, 27 May 2003 14:25:32 -0400
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 27 May 2003 14:16:13 -0400
Message-ID: <3ED3AB6D.7020301@centive.com>
Date: Tue, 27 May 2003 14:16:13 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: spam
References: <Pine.LNX.4.44.0305261802010.3699-100000@commander.av8.net> <3ED29544.4080002@ehsco.com>
In-Reply-To: <3ED29544.4080002@ehsco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 May 2003 18:16:13.0095 (UTC) FILETIME=[0E4C9370:01C3247C]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric A. Hall wrote:

>on 5/26/2003 5:17 PM Dean Anderson wrote:
>  
>
>>Junk fax law, overturned as being unconstitutional restriction on
>>speech.
>>    
>>
>You keep bringing this up. Please cite. As I said in another message, the
>only ruling I know of that would support this was overturned on appeal.
>
And the court whose ruling was overturned (I read the ruling) had made 
the same sort of error Dean is making: assuming that the only costs 
involved were those of physical resources (paper or disk space).

-- 
/==========================================================\
|John Stracke      |jstracke@centive.com                   |
|Principal Engineer|http://www.centive.com                 |
|Centive           |My opinions are my own.                |
|==========================================================|
|"Collect call from reality, will you accept the--" *click*|
\==========================================================/





From owner-ietf@ietf.org  Tue May 27 15:20:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26813
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 15:20:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KjTa-0001TT-9I
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 14:47:10 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kj0h-0007H6-6L
	for ietf@asgard.ietf.org; Tue, 27 May 2003 14:17:19 -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 OAA22461
	for <ietf@ietf.org>; Tue, 27 May 2003 14:17:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kiz9-0006tP-00
	for ietf@ietf.org; Tue, 27 May 2003 14:15:43 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kiz8-0006tM-00
	for ietf@ietf.org; Tue, 27 May 2003 14:15:42 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207945; Tue, 27 May 2003 13:16:45 -0500
Message-ID: <3ED3ABAA.1070400@ehsco.com>
Date: Tue, 27 May 2003 13:17:14 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
CC: ietf@ietf.org
Subject: Re: spam
References: <2528F9EE-906E-11D7-81E4-00039388672E@muada.com>
In-Reply-To: <2528F9EE-906E-11D7-81E4-00039388672E@muada.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/27/2003 1:07 PM Iljitsch van Beijnum wrote:

> They will continue to do it as long as:
> 
> 1. they get the return they're looking for
> 2. it's relatively easy to do
> 3. they get away with it

> Number two is an area where the IETF could actually do something 
> useful. The way things are today, everyone can contact any mailserver 
> and expect the message to be delivered. Now this is a nice way to build
> a distributed mail system, until such time that spammers pop up, 
> bombard mail servers around the world with their enlargement ads, and 
> when they are shut down they simply move to another IP address and 
> resume their abuse. If we mandate an extension to SMTP to signal an 
> unknown mail server that it should either
>
> a. find a known server to forward the message, or
> b. go through some kind of (off-line) procedure to become accredited
> 
> people who send small amounts of mail can simply be instructed to use 
> their ISP's mail server while those who send lots of legitimate mail 
> can be whitelisted. Spammers are presumably stopped when they flood 
> their ISP's mail server or they lose their white list status.

I'm all for that, but there are some serious difficulties with this. I
personally don't think it will work until the transfer protocols are
reinvented (specifically so that the exchange supports a separation of the
transfer and message headers, the current comingling of which is a
layering violation, IMHO), but rearchitecting gets a lot of push-back.
It's definitely an area that can stand some work.

> For number three we need the law.

Yep.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Tue May 27 15:27:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27191
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 15:27:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KjYf-0001e8-ST
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 14:52:25 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KjEk-0008OS-P0
	for ietf@asgard.ietf.org; Tue, 27 May 2003 14:31:50 -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 OAA23197
	for <ietf@ietf.org>; Tue, 27 May 2003 14:31:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KjDC-00074x-00
	for ietf@ietf.org; Tue, 27 May 2003 14:30:15 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KjDC-00074u-00
	for ietf@ietf.org; Tue, 27 May 2003 14:30:14 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207946; Tue, 27 May 2003 13:31:17 -0500
Message-ID: <3ED3AF12.4010609@ehsco.com>
Date: Tue, 27 May 2003 13:31:46 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Zefram <zefram@fysh.org>
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: spam
References: <963621801C6D3E4A9CF454A1972AE8F504F827@server2000.arneill-py.sacramento.ca.us> <g3fzn1udu7.fsf@sa.vix.com> <026301c32420$b3d01da0$0a00000a@atkielski.com> <ylk7cc1kn2.fsf@windlord.stanford.edu> <20030527172823.GA20601@fysh.org>
In-Reply-To: <20030527172823.GA20601@fysh.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/27/2003 12:28 PM Zefram wrote:

> Whether the receiving-end filtering approach is viable in the long
> term is debateable.  When 99.9% of email is spam, the filtering world
> will look very different.  Perhaps at that point it'll be infeasible to
> continue allowing unsolicited email at all.

Some of us are already at that point and are wanting to have the debate
right now.

Every system can be fooled (corrollary: every fool has a system). This
includes pre-emptive measures like laws, pre-transfer black/whitelists,
and post-transfer filtering techniques. What laws provide over the other
mechanisms is a discouragement hammer. The other mechanisms are purely
defensive, and as I said earlier, only have value if you redefine some
measure of defeat as victory.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Tue May 27 15:28:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27231
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 15:28:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KjYg-0001eE-3p
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 14:52:26 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KjFd-0008OY-Fx
	for ietf@asgard.ietf.org; Tue, 27 May 2003 14:32:45 -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 OAA23215
	for <ietf@ietf.org>; Tue, 27 May 2003 14:32:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KjE5-00075F-00
	for ietf@ietf.org; Tue, 27 May 2003 14:31:09 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KjE4-00075C-00
	for ietf@ietf.org; Tue, 27 May 2003 14:31:09 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4RIWhjh013579
	for <ietf@ietf.org>; Tue, 27 May 2003 20:32:43 +0200 (CEST)
Message-ID: <03bb01c3247e$5c6a85b0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <963621801C6D3E4A9CF454A1972AE8F504F827@server2000.arneill-py.sacramento.ca.us><g3fzn1udu7.fsf@sa.vix.com><026301c32420$b3d01da0$0a00000a@atkielski.com> <ylk7cc1kn2.fsf@windlord.stanford.edu> <034f01c32474$77e61700$0a00000a@atkielski.com> <3ED3A759.3010806@ehsco.com>
Subject: Re: spam
Date: Tue, 27 May 2003 20:32:42 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric writes:

> People would still want to tell everybody about
> their products.

To a certain extent, yes.  But if you get a response rate of 0.001% for
untargeted e-mail (not atypical), and 9% for targeted e-mail, you might
decide to skip the untargeted stuff pretty quickly.





From owner-ietf@ietf.org  Tue May 27 15:44:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28166
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 15:44:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KkBY-0003aX-Vo
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 15:32:36 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kjar-0001hd-Sk
	for ietf@asgard.ietf.org; Tue, 27 May 2003 14:54:41 -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 OAA24584
	for <ietf@ietf.org>; Tue, 27 May 2003 14:54:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KjZK-0007Q4-00
	for ietf@ietf.org; Tue, 27 May 2003 14:53:06 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KjZJ-0007Q1-00
	for ietf@ietf.org; Tue, 27 May 2003 14:53:05 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4RIsdjh013767
	for <ietf@ietf.org>; Tue, 27 May 2003 20:54:39 +0200 (CEST)
Message-ID: <03c201c32481$6cf1e880$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <026301c32420$b3d01da0$0a00000a@atkielski.com> <g37k8cuv8b.fsf@sa.vix.com>
Subject: Re: spam
Date: Tue, 27 May 2003 20:54:39 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Paul writes:

> you're talking e-mail even after i ripped smtp
> from stem to sternum here yesterday.  i'm not going
> to try to educate you about what smtp is or where
> it lives in the grand spectrum of things.

It would also be nice if you would additionally refrain from attacking me
personally just because I disagree with you.  It is very unbecoming.





From owner-ietf@ietf.org  Tue May 27 16:01:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28867
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 16:01:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KkCA-0003fq-F0
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 15:33:14 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KjsJ-0000O6-Qi
	for ietf@asgard.ietf.org; Tue, 27 May 2003 15:12:43 -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 PAA26151
	for <ietf@ietf.org>; Tue, 27 May 2003 15:12:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kjql-0007fA-00
	for ietf@ietf.org; Tue, 27 May 2003 15:11:07 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kjql-0007es-00
	for ietf@ietf.org; Tue, 27 May 2003 15:11:07 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id PAA23723;
	Tue, 27 May 2003 15:05:18 -0400
Date: Tue, 27 May 2003 15:06:20 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <200305271810.h4RIA8eG002649@ginger.lcs.mit.edu>
Message-ID: <Pine.LNX.4.44.0305271501570.7861-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

People can make all sorts of gratuitous changes. But that won't do
_anything_ whatsoever to stop spam.

Shannon's theorem still stands. I think perhaps you missed this:

=====
Dr. Claude Shannon, one of the founders of the science of Information
Theory, proved that it is impossible to prove the non-existance of a
covert channel. In terms of spam, this means that it is impossible to
construct a protocol that cannot be abused, since one cannot prove that it
is impossible (the channel can't exist) to send abuse (a covert channel).
No protocol can ever be constructed that is spam-free.  Radical
anti-spammers often try to couch their arguments as though the spammers
are "outsiders" who have been let in. This isn't true. All abusers are the
customer of some ISP, somewhere. There are no outsiders.  The spammers are
in fact authorized users of some ISP that are authorized to send email.
They remain authorized to send email until they lose service with that
ISP.  Once this is understood, it is completely obvious even without the
formality of Shannon's theorem that protocols such as SMTP AUTH will have
no effect whatsoever.

So IETF efforts in this area are limited to finding means of identifying
the abuser, once the abuser has been detected. There is also the technical
task of detecting abuse.
====

After you find a way to violate Shannon's theorem, come back. We'll all be
interested for a variety reasons. I'm sure the NSA and every government
and non-government security agency on the planet will be interested.

		--Dean

On Tue, 27 May 2003, J. Noel Chiappa wrote:

>     > From: Dean Anderson <dean@av8.com>
>
>     > it is the case that _protocols_ can do nothing about spam. So, there is
>     > nothing for the IETF to do
>
> Not necessarily so.
>
> First, if people agree that charging for email is needed, or some equally
> significant change (and clearly the existing SMTP-based email system is an
> open door for spam, and always will be), then that means a new protocol,
> which the IETF will have to design.
>
> Moreover, in the public policy debate that is going on now, policy makers
> need to know what technical options are avaiable as they look at the spectrum
> of possible solutions (legal, technical, etc). The IETF has a role to play
> there, too.
>
> 	Noel
>
>





From owner-ietf@ietf.org  Tue May 27 16:01:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28866
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 16:01:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KkBZ-0003az-DX
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 15:32:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KjdP-0001kT-HQ
	for ietf@asgard.ietf.org; Tue, 27 May 2003 14:57:19 -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 OAA24684
	for <ietf@ietf.org>; Tue, 27 May 2003 14:57:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kjbr-0007S2-00
	for ietf@ietf.org; Tue, 27 May 2003 14:55:43 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kjbr-0007RV-00
	for ietf@ietf.org; Tue, 27 May 2003 14:55:43 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 35FC313970; Tue, 27 May 2003 18:56:45 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: spam
References: <963621801C6D3E4A9CF454A1972AE8F504F829@server2000.arneill-py.sacramento.ca.us>
From: Paul Vixie <vixie@vix.com>
Date: 27 May 2003 18:56:45 +0000
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F829@server2000.arneill-py.sacramento.ca.us>
Message-ID: <g33cj0usk2.fsf@sa.vix.com>
Lines: 40
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

michel@arneill-py.sacramento.ca.us ("Michel Py") writes:

> > i'm wasting my time because i want this problem looked at more broadly.
> 
> Are you in agreement with what Noel wrote earlier WRT involving some
> money in sending email is the only deterrent that spammers that pollute
> our inbox and now our mailing list would understand?

no.  that's one possible avenue but i reject the word "only".  to put it
another way, the problem isn't deterring spammers or even preventing abuse,
but rather designing a new interpersonal batch communications system (ibcs?)
which allows a receiving party to accept or reject inbound traffic with some
kind of confidence in the identity of the sender, the intent of the relay or
proxy, and the value (to the sender) of the reception.

i've heard several calls to move this discussion elsewhere.  since my goal
is to get ietf to take this seriously (and if you think the asrg is serious
then you are not paying attention or you don't understand the issues) and do
another turn of the same crank that produced mime and esmtp.  the industry
has the talent, especially companies like sendmail and projects like postfix,
to design an "ibcs" that's suitable for today's diverse internet population.

to give y'all an idea of what's technically and philosophically unworkable
about the smtp model, look at the isoid "mua/mta" split and note that the
idea of an mta working on an mua's behalf but operating asynchronously (and
therefore accepting and locally queuing inbound or outbound traffic without
reference to the mua policy of the sender and especially the recipient) is
just flat out unworkable, no matter how it might've looked on a whiteboard.

my own ideas have to do with trustbrokers, certificates for both mailboxes
and transfer/relay agents, and provable confidence in subjective values.
but maybe all that's just crap, and what's actually necessary and
sufficient would have a completely different look/feel to it than anything
i've yet considered.

we (the e-mail producing/consuming community) have the technology, we have
the collective wit and wisdom, we have the proven commercial value of the
service.  what we lack, dear ietf, is simply: leadership.
-- 
Paul Vixie



From owner-ietf@ietf.org  Tue May 27 16:11:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29429
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 16:11:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KkES-0003tR-6i
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 15:35:36 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KkAw-0003Zo-V7
	for ietf@asgard.ietf.org; Tue, 27 May 2003 15:31:58 -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 PAA27551
	for <ietf@ietf.org>; Tue, 27 May 2003 15:31:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kk9O-0000Cl-00
	for ietf@ietf.org; Tue, 27 May 2003 15:30:23 -0400
Received: from mail2.microsoft.com ([131.107.3.124])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kk9O-0000B4-00
	for ietf@ietf.org; Tue, 27 May 2003 15:30:22 -0400
Received: from INET-VRS-02.redmond.corp.microsoft.com ([157.54.8.110]) by mail2.microsoft.com with Microsoft SMTPSVC(5.0.2195.6624);
	 Tue, 27 May 2003 12:31:25 -0700
Received: from 157.54.8.23 by INET-VRS-02.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 27 May 2003 12:31:25 -0700
Received: from RED-IMC-04.redmond.corp.microsoft.com ([157.54.2.168]) by inet-hub-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 27 May 2003 12:31:24 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by RED-IMC-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 27 May 2003 12:31:24 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3788.0);
	 Tue, 27 May 2003 12:31:23 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6940.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: spam
Date: Tue, 27 May 2003 12:31:22 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA036BDF66@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: spam
Thread-Index: AcMkf8t94vzodZIdTg677yWG/ao5zgABji+Q
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, <ietf@ietf.org>
X-OriginalArrivalTime: 27 May 2003 19:31:23.0911 (UTC) FILETIME=[8EF47970:01C32486]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA29429

> Moreover, in the public policy debate that is going on now, policy
makers
> need to know what technical options are avaiable as they look at the
> spectrum
> of possible solutions (legal, technical, etc). The IETF has a role to
play
> there, too.

Absolutely. We need to get something like RFC1984. As bad as spam is, a
lot of the countermeasures have a significant cost. It is probably
necessarily so, as making e-mail easy to send also makes spam easy to
send, but different measures have different side effects, and that is
worth documenting.

-- Christian Huitema 




From owner-ietf@ietf.org  Tue May 27 16:21:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29778
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 16:21:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KkYx-0004So-5g
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 15:56:47 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KkC0-0003b8-NN
	for ietf@asgard.ietf.org; Tue, 27 May 2003 15:33:04 -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 PAA27586
	for <ietf@ietf.org>; Tue, 27 May 2003 15:33:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KkAS-0000Df-00
	for ietf@ietf.org; Tue, 27 May 2003 15:31:28 -0400
Received: from ds20-1.cc.swin.edu.au ([136.186.1.150] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KkAQ-0000DV-00
	for ietf@ietf.org; Tue, 27 May 2003 15:31:27 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2/8.9.3) with ESMTP id FAA1879700;
	Wed, 28 May 2003 05:32:35 +1000 (EST)
Message-ID: <3ED3BD52.7D0BA70@swin.edu.au>
Date: Wed, 28 May 2003 05:32:34 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.8 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Anthony Atkielski <anthony@atkielski.com>
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: please move the spam discussion elsewhere
References: <20030527132930.3210e276.moore@cs.utk.edu> <03a901c3247c$23885df0$0a00000a@atkielski.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Anthony Atkielski wrote:
> 
> Right now, there is probably no other greater problem with the Internet than
> spam.

It certainly has been a problem for this list over the past few days,
that's for sure.

gja



From owner-ietf@ietf.org  Tue May 27 16:33:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00623
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 16:33:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kks4-0005l8-Ez
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 16:16:32 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KkP2-0004LX-K0
	for ietf@asgard.ietf.org; Tue, 27 May 2003 15:46:32 -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 PAA28325
	for <ietf@ietf.org>; Tue, 27 May 2003 15:46:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KkNT-0000Qc-00
	for ietf@ietf.org; Tue, 27 May 2003 15:44:55 -0400
Received: from windlord.stanford.edu ([171.64.19.147])
	by ietf-mx with smtp (Exim 4.12)
	id 19KkNS-0000QR-00
	for ietf@ietf.org; Tue, 27 May 2003 15:44:55 -0400
Received: (qmail 28741 invoked by uid 50); 27 May 2003 19:46:17 -0000
To: "IETF Discussion" <ietf@ietf.org>
Subject: Re: spam
References: <963621801C6D3E4A9CF454A1972AE8F504F827@server2000.arneill-py.sacramento.ca.us>
	<g3fzn1udu7.fsf@sa.vix.com>
	<026301c32420$b3d01da0$0a00000a@atkielski.com>
	<ylk7cc1kn2.fsf@windlord.stanford.edu>
	<034f01c32474$77e61700$0a00000a@atkielski.com>
In-Reply-To: <034f01c32474$77e61700$0a00000a@atkielski.com> ("Anthony
 Atkielski"'s message of "Tue, 27 May 2003 19:21:54 +0200")
From: Russ Allbery <rra@stanford.edu>
Organization: The Eyrie
Date: Tue, 27 May 2003 12:46:17 -0700
Message-ID: <ylptm4b2ba.fsf@windlord.stanford.edu>
Lines: 33
User-Agent: Gnus/5.090008 (Oort Gnus v0.08) XEmacs/21.4 (Portable Code,
 sparc-sun-solaris2.6)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Anthony Atkielski <anthony@atkielski.com> writes:
> Russ writes:

>> So does trying to find the legitimate mail among a pile of spam.

> The difference is that, in the first case, legitimate e-mail is lost,
> whereas in the second case, legitimate e-mail is preserved.

No, actually, there is no difference.  That's the key realization that
you've not yet reached.  Missing and deleting legitimate e-mail because a
human mistakes it for spam has the precise same end result as rejecting a
message because a computer program mistakes it for spam, except that in
the former case the sender generally does not even get a warning, whereas
they may in the latter case.

The only actual difference between the filtering methods is that one of
them takes more personal time from a human and they have different false
positive and false negative profiles.  I can think of multiple incidents
that I've personally witnessed where the computer program had a *better*
false positive and false negative profile than the human.

I think you need to think about this a little more.  No one is not
filtering spam.  Everyone filters spam; they just use different techniques
which have different impacts on the network, on their personal time, and
on the information returned to the sender.

If you, like another poster in this thread, are currently only receiving
5-10 spams a day, congratulations, you don't have to care yet.  That level
of volume is trivial to filter.  That was me three years ago; I now get
approximately 500 spam messages a day.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>



From owner-ietf@ietf.org  Tue May 27 16:41:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01198
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 16:41:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kks5-0005nL-OW
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 16:16:33 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KkZw-0004TP-5R
	for ietf@asgard.ietf.org; Tue, 27 May 2003 15:57:48 -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 PAA28699
	for <ietf@ietf.org>; Tue, 27 May 2003 15:57:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KkYO-0000Y7-00
	for ietf@ietf.org; Tue, 27 May 2003 15:56:12 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KkYM-0000Y3-00
	for ietf@ietf.org; Tue, 27 May 2003 15:56:11 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4RJvfjh014319
	for <ietf@ietf.org>; Tue, 27 May 2003 21:57:41 +0200 (CEST)
Message-ID: <03ee01c3248a$3b6c35a0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Sea2-F69N5t0GXzsddN0002e7f3@hotmail.com>
Subject: Re: please move the spam discussion elsewhere
Date: Tue, 27 May 2003 21:57:41 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bryan writes:

> Do we expect to resolve anything by continuing
> this discussion here at this time?

We don't know if we don't try.  Should we just wait for a Presidential
blue-ribbon committee, or a direct-marketing consortium report, or a study
by the Attorney General?  Would you rather that someone else decided for
you, including the potential changes that would affect your ability to use
the Internet?

I wrote a couple of suggestions in a reply to "spam and fax," but nobody
seems to have noticed.

> Again, the subject itself has great value to us all,
> but the current discussion does not, other than a
> release of written steam, if you will, which all of
> us are being subjected to, in some cases against our
> wishes.

Of all groups using the Internet, I'd expect people contributing to the IETF
to understand the absurdity of expecting the rest of the world to censor its
output rather than filter its input.  In other words, if you aren't
interested in the messages you see on the list, don't read them.  I delete
most of the traffic I see on this list most of the time, because many issues
aren't of direct interest to me, and often I have nothing to contribute.
But I don't send messages to the list telling them to stop talking about
things because it's such a tremendous burden on me to press the delete key
on my PC.

> While I realize I am capable of deleting everything
> even mentioning SPAM from the ietf list ...

Exactly.

> ... I would point out that I did so this morning already,
> when I (after not checking email for 12 hours) had 140+
> such items to delete.

Click the first item, hold down shift, click the last item, then press
Delete.  I can do this in a second or two.  In fact, I do it all the time,
on many different lists.

> This is getting nowhere fast, and I reiterate the request
> to take it offline, please.

I've never complained about anything on this list, and I've certainly
received many thousands of messages in which I had absolutely no interest.
The fact that I'm not interested in them doesn't mean that others should
stop discussing them just to allow me to rest my index finger.  I'm not the
only person on this list or on the Internet, and I don't expect or ask the
rest of the world to produce only the e-mail messages that I find acceptable
and interesting.

I find this to be a sensible and considerate policy, and the only one that
really can be practically implemented, anyway.  I submit it for your
consideration.  I won't even charge a consulting fee for the time I spent
reading your complaint and replying to it.




From owner-ietf@ietf.org  Tue May 27 16:47:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01418
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 16:47:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kl51-0006QW-IZ
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 16:29:55 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kkp4-0005eb-7P
	for ietf@asgard.ietf.org; Tue, 27 May 2003 16:13:26 -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 QAA29567
	for <ietf@ietf.org>; Tue, 27 May 2003 16:13:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KknW-0000mt-00
	for ietf@ietf.org; Tue, 27 May 2003 16:11:50 -0400
Received: from out006pub.verizon.net ([206.46.170.106] helo=out006.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KknV-0000mh-00
	for ietf@ietf.org; Tue, 27 May 2003 16:11:49 -0400
Received: from earthlink.net ([4.65.81.213]) by out006.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030527201253.NVPE25800.out006.verizon.net@earthlink.net>;
          Tue, 27 May 2003 15:12:53 -0500
Message-ID: <3ED3C5E3.23A8FEB5@earthlink.net>
Date: Tue, 27 May 2003 13:09:07 -0700
From: Peter Deutsch <pdeutsch@earthlink.net>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Anthony Atkielski <anthony@atkielski.com>
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: please move the spam discussion elsewhere
References: <20030527132930.3210e276.moore@cs.utk.edu> <03a901c3247c$23885df0$0a00000a@atkielski.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out006.verizon.net from [4.65.81.213] at Tue, 27 May 2003 15:12:53 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

g'day,

Hopefully, I can eventually control my fascination with this particular
blinking light and stop feeding this particular troll. Meanwhile, I do
feel that this particular consciousness-raising effort has value for the
members of this list, since as Paul Vixie has pointed out it may be time
to revisit the group's earlier decision to avoid tackling the problem.


So here I go again, picking up points from multiple postings:

Anthony Atkielski wrote:
> 
> Right now, there is probably no other greater problem with the Internet than
> spam.  That sounds more than important enough to justify discussion here.
> You can delete any messages that mention spam, if you want.

To our credit, everyone involved in this thread (until this mutation
appeared) seem to have properly appended the appropriate "Subject Re:
spam", making automatic SPAM filtering trivially easy..... ;-)



and:

> What's your point?
> 
> Sysadmins are supposed to be past the learning curve already.

At the risk of repeating myself, economists will tell you that it is at
margin that "marginal costs" are calculated. Those who would keep
repeating the mantra that email "costs only $1 or $2 a month" are IMHO
entirely missing the point.

Sure, these poor deluded folks should just abandon any attempt at
operating a school network or providing their community with anything
but barebones commercial services, but they chose to push the envelope a
bit, using donated equipment, part time staff and volunteers to stretch
the budget. There are a lot of folks at the periphery who are living
this story, whether in the developing world, or in non-commercial
settings. Shame of those who would consume their precious resources or
divert their attention from other, more worthy activities.

The guy helping to hold it all together in this example (and I used it
only as an illustrative example) is actually pretty good at teaching
primary school kids basic computer skills, and can certainly deliver
basic services such as a functioning file server with his extra time,
but he's ill-equipped to handle mailstorms, Denial of Service attacks or
other infrastructure problems. The system relies on folks like me for
escalation support, and it usually works fine. That's why I get so
irritated when folks like you try to minimize the costs of spam in this
thread. It really shouldn't be your call to tell them that they're
playing out of their league.

In this case, the guy called me in to investigate a sluggish,
non-responsive Window NT file server that we discovered was being
bombarded by repeated email connections from overseas, since it had
somehow got onto some spammers' list of relay hosts. Note, this was a
system he inherited, and it's not primarily a mail host, so "go sign up
for a $1 email account" really doesn't solve the underlying problem
here. After all, we all get stuck with legacy systems support at some
point, non?

In this case, we closed it up and did what we could to fix the
overflowing disk problems, etc, but the connection requests continue. So
your answer to the school would appear to be to shut it all down down,
or fire the computer teacher because he can't solve this problem on his
own? That's just silly...


and:

> > usually it takes a week, but you did it all in
> > 36 hours.  congrats?
> 
> I'm afraid I don't understand.

Here I'm going to agree with you. I do this consciously, and with the
expectation that this thread is starting on its death spiral. Can
somebody please make a reference to Adolf Hitler, so we can all declare
victory and go home?


			- peterd (queue the Monthy Python SPAM song...)



-- 
-----------------------------------------------------------------------
   Peter Deutsch                   peterd@gydig.com
   Gydig Software


      "Don't get me wrong: Emacs is a great operating system -
       it lacks a good editor, though."

					- Thomer M. Gil
----------------------------------------------------------------------



From owner-ietf@ietf.org  Tue May 27 16:53:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01768
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 16:53:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KlK9-0007gu-Hh
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 16:45:33 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KkyJ-0006Kf-DY
	for ietf@asgard.ietf.org; Tue, 27 May 2003 16:22:59 -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 QAA29944
	for <ietf@ietf.org>; Tue, 27 May 2003 16:22:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kkwl-0000td-00
	for ietf@ietf.org; Tue, 27 May 2003 16:21:23 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kkwk-0000tZ-00
	for ietf@ietf.org; Tue, 27 May 2003 16:21:22 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4RKMujh014543
	for <ietf@ietf.org>; Tue, 27 May 2003 22:22:56 +0200 (CEST)
Message-ID: <03fd01c3248d$c27ce6e0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <963621801C6D3E4A9CF454A1972AE8F504F829@server2000.arneill-py.sacramento.ca.us> <g33cj0usk2.fsf@sa.vix.com>
Subject: Re: spam
Date: Tue, 27 May 2003 22:22:56 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Paul writes:

> ... the problem isn't deterring spammers or even
> preventing abuse, but rather designing a new
> interpersonal batch communications system (ibcs?)
> which allows a receiving party to accept or reject
> inbound traffic with some kind of confidence in
> the identity of the sender, the intent of the relay or
> proxy, and the value (to the sender) of the reception.

Designing one is easy.  Getting a billion people around the world to all
implement the system, once designed, is very, very hard.

Additionally, nobody would be willing to accept a single design.  Someone
would claim patent infringement.  Different companies would want to turn it
into a money-making adventure, which would instantly make it unworkable for
most of the world.  Other companies would change the design slightly and
then try to force their own versions as the "true" standard, in order to
make commercial profits.  It would take forever to do.

Whatever the technical solution might be, I think it would have to be
something that requires only action at the receiving end, not the sending
end.  If you require action at both ends, you lock out 95% of the world's
Internet users at the push of a button.  It's like coming up with a solution
that requires everyone to upgrade to a new version of Windows with a certain
service pack.  It's not going to happen.

As always, be conservative in what you expect, and liberal in what you
accept.

> my own ideas have to do with trustbrokers ...

Trusted third parties are tempting, but that notion opens a tremendous can
of worms.  Personally, there isn't anyone I'd trust as a certification
authority even for strangers.  A PGP model is more tempting, but it would
require more sophistication on the part of users than can reasonably be
expected for 99% of the world's Internet citizens.  Indeed, any trustbroker
plan has this same problem.

Even if the certification is limited to mailers, you still have the above
problem, only with slightly reduced magnitude.

> we (the e-mail producing/consuming community) have
> the technology ...

We can rebuild it.  We can make it better.

Nah.  The Internet acquires more inertia with each passing day.  And the
more inertia it develops, the harder it is to implement any active technical
change (i.e., any change that requires actual modification of multiple
systems around the world).  Kind of like moving everyone to IPv6.

> what we lack, dear ietf, is simply: leadership.

No, we lack a genius who can come up with something that will work without
requiring a change on one billion computers around the world.  Preferably a
genius who won't file a patent on it, too.




From owner-ietf@ietf.org  Tue May 27 17:05:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02492
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 17:05:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KlK9-0007ha-Tu
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 16:45:33 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kl2j-0006NG-1D
	for ietf@asgard.ietf.org; Tue, 27 May 2003 16:27:33 -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 QAA00102
	for <ietf@ietf.org>; Tue, 27 May 2003 16:27:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kkzm-0000wC-00
	for ietf@ietf.org; Tue, 27 May 2003 16:24:30 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kkzm-0000vi-00
	for ietf@ietf.org; Tue, 27 May 2003 16:24:30 -0400
Content-class: urn:content-classes:message
Subject: RE: spam
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Tue, 27 May 2003 13:25:55 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F82C@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: spam
Thread-Index: AcMkit3hwahc41nUQOqeXplQETlhmgAAd7QQ
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Paul Vixie" <vixie@vix.com>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA02492

Paul,

> Paul Vixie wrote:
> [large snap]
> my own ideas have to do with trustbrokers, certificates for both
> mailboxes and transfer/relay agents, and provable confidence in
> subjective values. but maybe all that's just crap, and what's
> actually necessary and sufficient would have a completely
> different look/feel to it than anything i've yet considered.

I'm with you here, but keep reading.


> we (the e-mail producing/consuming community) have the
> technology, we have the collective wit and wisdom, we have the
> proven commercial value of the service.  what we lack, dear
> ietf, is simply: leadership.

Given what you wrote just above (which I agree with), what is your
assessment that a system such as what you have in mind would
successfully reach IETF consensus?

Look just the past 2 days how many trolls posted on this ML to lobby for
the spammer's cause.

The reason I agree with Noel along the lines that the only way is making
spammers pay for sending email is not because I don't think that we
don't have what it takes to invent a protocol, but because I think it
will be torpedoed before it is born.

Michel.




From owner-ietf@ietf.org  Tue May 27 17:13:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02761
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 17:13:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KlPG-0000BM-Gi
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 16:50:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KlHh-0007by-V4
	for ietf@asgard.ietf.org; Tue, 27 May 2003 16:43:01 -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 QAA01324
	for <ietf@ietf.org>; Tue, 27 May 2003 16:42:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KlG9-0001Dv-00
	for ietf@ietf.org; Tue, 27 May 2003 16:41:25 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KlG9-0001Dj-00
	for ietf@ietf.org; Tue, 27 May 2003 16:41:25 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id QAA13497;
	Tue, 27 May 2003 16:38:56 -0400
Date: Tue, 27 May 2003 16:39:59 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: John Stracke <jstracke@centive.com>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <3ED3AB6D.7020301@centive.com>
Message-ID: <Pine.LNX.4.44.0305271552070.8489-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Uh, no. You need to read the page cited by Eric Hall.
http://www.techlawjournal.com/topstories/2003/20030321.asp

I read the ruling, too.  The district court said that the government
failed to satisfy the tests for restriction of commercial speech, as
outlined in Central Hudson. The appeals court reversed.

However, this is an interesting case, since American Blast Fax was not
represented in the Appeal, and had apparently gone out of business.
Generally, when one party does't show up, a case is granted to the other
party by default. Such a victory does not make precedent, and is not
binding on any other case.

Not being a lawyer, I can't tell you what that means with respect to an
appeal. I will ask though.

The central point of review is the District courts finding that
"technological changes had eliminated the burdens imposed on recipients of
unwanted fax advertising".  The circuit court essentially reversed this
finding, and used it to reverse the decision.

In other words, cost plays a big part in the decision.  But as has been so
roundly demonstrated, the cost associated with email is practically
non-existant, and does not ever cost any user more than $1 or $2 per
month, which they pay for email services.

This is substantially different from the case with faxes. And it does seem
to be a valid arguement that if technology does eliminate the burdens
imposed, then the junk fax law could be reversed.

In the case of spam, there is no cost _shifting_ whatsoever, since by
definition, everyone pays their own way. Even spammers.  Unlike faxes, the
receipt of a spam does not increase the cost of the recipient's email.
Email is usually fixed cost, and flat rate.  Even when one pays by the
octet, the cost of a spam is in the millionths of a cent, which I think
is less than the cost to carry out the trash of one junk postal mail.

		--Dean

On Tue, 27 May 2003, John Stracke wrote:

> Eric A. Hall wrote:
>
> >on 5/26/2003 5:17 PM Dean Anderson wrote:
> >
> >
> >>Junk fax law, overturned as being unconstitutional restriction on
> >>speech.
> >>
> >>
> >You keep bringing this up. Please cite. As I said in another message, the
> >only ruling I know of that would support this was overturned on appeal.
> >
> And the court whose ruling was overturned (I read the ruling) had made
> the same sort of error Dean is making: assuming that the only costs
> involved were those of physical resources (paper or disk space).
>
> --
> /==========================================================\
> |John Stracke      |jstracke@centive.com                   |
> |Principal Engineer|http://www.centive.com                 |
> |Centive           |My opinions are my own.                |
> |==========================================================|
> |"Collect call from reality, will you accept the--" *click*|
> \==========================================================/
>
>
>
>




From owner-ietf@ietf.org  Tue May 27 17:21:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00620
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 16:33:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kks5-0005n9-FZ
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 16:16:33 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KkY2-0004S0-Pi
	for ietf@asgard.ietf.org; Tue, 27 May 2003 15:55:50 -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 PAA28625
	for <ietf@ietf.org>; Tue, 27 May 2003 15:55:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KkWU-0000WL-00
	for ietf@ietf.org; Tue, 27 May 2003 15:54:14 -0400
Received: from smtp016.mail.yahoo.com ([216.136.174.113])
	by ietf-mx with smtp (Exim 4.12)
	id 19KkWT-0000WH-00
	for ietf@ietf.org; Tue, 27 May 2003 15:54:13 -0400
Received: from 212.68.224.51.brutele.be (HELO isoc) (Tomson?Eric@212.68.224.51 with login)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 27 May 2003 19:55:39 -0000
Reply-To: <Tomson_Eric@Yahoo.fr>
From: "Tomson Eric \(Yahoo.fr\)" <Tomson_Eric@Yahoo.fr>
To: "'Christian de Larrinaga'" <cdel@firsthand.net>,
        "'J. Noel Chiappa'" <jnc@ginger.lcs.mit.edu>
Cc: <ietf@ietf.org>
Subject: RE: spam
Date: Tue, 27 May 2003 21:55:20 +0200
Organization: Internet Society
Message-ID: <007a01c32489$f0adfe40$3500a8c0@tomson.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <MABBIEBOAFJNELEGFHCKAEMCIDAA.cdel@firsthand.net>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

You must pay to drive on a highway in France, on a per-segment basis.
You must buy a voucher to use highways in Switzerland, on a per-year basis.

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of
Christian de Larrinaga
Sent: mardi 27 mai 2003 10:39
To: J. Noel Chiappa; ietf@ietf.org
Subject: RE: spam


Noel Chiappa wrote...

> Needless to say, toll roads exist, but billed road use doesn't.
> 
> 	Noel
> 
> 

It does in London.


Christian de Larrinaga





From owner-ietf@ietf.org  Tue May 27 17:34:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03370
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 17:34:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kljz-00019i-Ax
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 17:12:15 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KlR2-0000CW-Fe
	for ietf@asgard.ietf.org; Tue, 27 May 2003 16:52:40 -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 QAA01743
	for <ietf@ietf.org>; Tue, 27 May 2003 16:52:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KlPU-0001L6-00
	for ietf@ietf.org; Tue, 27 May 2003 16:51:04 -0400
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KlPT-0001Km-00
	for ietf@ietf.org; Tue, 27 May 2003 16:51:03 -0400
Received: from rflooker1 ([191.1.2.48]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com for <ietf@ietf.org>;
          Tue, 27 May 2003 16:51:58 -0400
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf@ietf.org
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: SMS, New media, old media
Date: Tue, 27 May 2003 16:51:58 -0400
Message-ID: <20030527205158609.AAA411@hq.lindsayelec.com@rflooker1>
Sender: owner-ietf@ietf.org
Precedence: bulk


Said presumably moments ago:
>we (the e-mail producing/consuming community) have the technology, we have
>the collective wit and wisdom, we have the proven commercial value of the
>service.  what we lack, dear ietf, is simply: leadership.
>Paul Vixie

Dan (Me) says. Well. I like Short Message Service on cellular phones a lot,
and use it solidly every weekend to organize my life. I noted that when i
mentioned spam is starting to show up on SMS, the first few (free tickets to
the movies, Drinking adventures, etc). Everyone I told it too who use SMS
more or less seemed pleased one of these days they might get some fun
thing... pretty well, the preverbial free lunch of some sort. I mention
this, becuase SMS is mostly decoupled from POP and SMTP mail. So is paper
unsolicited mail and telemarketing by phone, and all have more in common
with each other than techno differences. 

Technologies like http's PIC's are far too complex for non technocrats:
http://www.w3.org/PICS/

In order to not getted mugged, etc, some people elect to live in walled
cities. Others always let machines pick up voice calls before returning
them. All kinds of strategies exist and coexist to manage unsolicited bits
of reality.

I guess (its particularly interesitng to see Paul V as a recipient of this):
no one ever made a technology that let one person annoy 60 million people,
even in one lifetime before, much less in seconds in ease and comfort!

But mostly, if people didn't endlessly want something for nothing, this
problem (and Los Vegas) wouldn't exist. I think maybe SPAM volume is at a
natural equalibrium point now, and as young people get used to never
responding, the traffic will turn the corner downward? Don't know.

I know its been discussed 10E9 times before, but the IETF probably does best
with engineering that's not associated with "social engineering". Of course,
though, authentication etc mixes who'w who, with hows-it-work about 50/50.

PICS though, is a really well intentioned negative example. Not the first
time MIT has made a solution for a non problem few people can figure out;
(and... not that last, bless there ferroresenant, buckyball fuelled little
hearts).

Regs
Dan
 




From owner-ietf@ietf.org  Tue May 27 17:35:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03400
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 17:35:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Klk1-0001DB-5V
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 17:12:17 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Klb9-0000e6-Pz
	for ietf@asgard.ietf.org; Tue, 27 May 2003 17:03:07 -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 RAA02392
	for <ietf@ietf.org>; Tue, 27 May 2003 17:03:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KlZb-0001Vv-00
	for ietf@ietf.org; Tue, 27 May 2003 17:01:31 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KlZa-0001Ve-00
	for ietf@ietf.org; Tue, 27 May 2003 17:01:31 -0400
Content-class: urn:content-classes:message
Subject: RE: please move the spam discussion elsewhere
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Tue, 27 May 2003 14:02:57 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F82E@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: please move the spam discussion elsewhere
Thread-Index: AcMkkWIfci7mDWpSQ0+efz0gjDbIKQAAMtkQ
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: <pdeutsch@earthlink.net>
Cc: "IETF Discussion" <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA03400

Peter,


> Peter Deutsch wrote:
> Hopefully, I can eventually control my fascination with this
> particular blinking light and stop feeding this particular troll.

Self-consciousness of it is half done, the other half is to put him in
the troll box so you don't see the troll's traffic and therefore are not
tempted to answer it. You can do it; there will plenty other trolls if
you feel like feeding one later.


> Meanwhile, I do feel that this particular consciousness-raising
> effort has value for the members of this list, since as Paul Vixie
> has pointed out it may be time to revisit the group's earlier
> decision to avoid tackling the problem.

It is true that the size of the phenomenon has increased much since the
last BoF.

Michel.




From owner-ietf@ietf.org  Tue May 27 17:36:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01417
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 16:47:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kks7-0005sK-4N
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 16:16:35 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KkfU-0005DX-EO
	for ietf@asgard.ietf.org; Tue, 27 May 2003 16:03:32 -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 QAA29139
	for <ietf@ietf.org>; Tue, 27 May 2003 16:03:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kkdw-0000eq-00
	for ietf@ietf.org; Tue, 27 May 2003 16:01:56 -0400
Received: from f69.sea2.hotmail.com ([207.68.165.69] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KkJu-0000K5-00
	for ietf@ietf.org; Tue, 27 May 2003 15:41:14 -0400
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 27 May 2003 12:42:16 -0700
Received: from 138.162.0.44 by sea2fd.sea2.hotmail.msn.com with HTTP;
	Tue, 27 May 2003 19:42:15 GMT
X-Originating-IP: [138.162.0.44]
X-Originating-Email: [braendt@hotmail.com]
From: "Bryan Linder" <braendt@hotmail.com>
To: anthony@atkielski.com, ietf@ietf.org
Subject: Re: please move the spam discussion elsewhere
Date: Tue, 27 May 2003 15:42:15 -0400
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <Sea2-F69N5t0GXzsddN0002e7f3@hotmail.com>
X-OriginalArrivalTime: 27 May 2003 19:42:16.0359 (UTC) FILETIME=[13D82370:01C32488]
Sender: owner-ietf@ietf.org
Precedence: bulk

Anthony,

While I agree with you on the importance of the topic, I do not believe you 
in any way invalidated the message to which you replied. Is the subject 
important? YES. Is it within the scope of the IETF? YES. Has anyone 
identified the scope of the problem, or defined its exact nature? NO. Does 
anyone really agree with anyone else on this topic? NO, at least not thus 
far in the discussion. Is it currently under discussion elsewhere? YES. Do 
we expect to resolve anything by continuing this discussion here at this 
time? If you do, then I suggest you need to re-evaluate the (mostly 
degenerated, just barely above name calling) messages to date.

Again, the subject itself has great value to us all, but the current 
discussion does not, other than a release of written steam, if you will, 
which all of us are being subjected to, in some cases against our wishes. 
While I realize I am capable of deleting everything even mentioning SPAM 
from the ietf list, I would point out that I did so this morning already, 
when I (after not checking email for 12 hours) had 140+ such items to 
delete. This is getting nowhere fast, and I reiterate the request to take it 
offline, please.

Bryan A. Linder
IT Consultant, DDS (sub Lockheed Martin at the USDN SPAWAR-ITC)

>Right now, there is probably no other greater problem with the Internet 
>than
>spam.  That sounds more than important enough to justify discussion here.
>You can delete any messages that mention spam, if you want.
>
>----- Original Message -----
>From: "Keith Moore" <moore@cs.utk.edu>
>To: <ietf@ietf.org>
>Cc: <moore@cs.utk.edu>
>Sent: Tuesday, May 27, 2003 19:29
>Subject: please move the spam discussion elsewhere
>
>
> > It's not that spam isn't an important problem, nor that it's entirely
> > out of scope for IETF.   But the lack of agreement on the nature of the
> > problem, along with the level of naivete in these discussions, suggest
> > that it will be a long time before these discussions can hope to bear
> > useful fruit.  And this isn't a particularly effective venue to work
> > on that problem.
> >
> > If nothing else, the NSRG antispam research group has been talking about
> > this for several months, and there's no point in repeating the same
> > arguments on the IETF list that they've been having over there.
> >
> > see https://www1.ietf.org/mailman/listinfo/asrg
> >
> >
> >
>
>

_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail




From owner-ietf@ietf.org  Tue May 27 18:05:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04589
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 18:05:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Km91-0002cU-6B
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 17:38:07 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KlkQ-0001Df-EK
	for ietf@asgard.ietf.org; Tue, 27 May 2003 17:12:42 -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 RAA02732
	for <ietf@ietf.org>; Tue, 27 May 2003 17:12:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Klis-0001dO-00
	for ietf@ietf.org; Tue, 27 May 2003 17:11:06 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Klir-0001dK-00
	for ietf@ietf.org; Tue, 27 May 2003 17:11:05 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4RLCcjh015003
	for <ietf@ietf.org>; Tue, 27 May 2003 23:12:38 +0200 (CEST)
Message-ID: <042a01c32494$b3d13d60$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <963621801C6D3E4A9CF454A1972AE8F504F827@server2000.arneill-py.sacramento.ca.us><g3fzn1udu7.fsf@sa.vix.com><026301c32420$b3d01da0$0a00000a@atkielski.com><ylk7cc1kn2.fsf@windlord.stanford.edu><034f01c32474$77e61700$0a00000a@atkielski.com> <ylptm4b2ba.fsf@windlord.stanford.edu>
Subject: Re: spam
Date: Tue, 27 May 2003 23:12:38 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Russ writes:

> If you, like another poster in this thread, are
> currently only receiving 5-10 spams a day, congratulations,
> you don't have to care yet.

I receive about 300 a day, and that number is increasing very rapidly.





From owner-ietf@ietf.org  Tue May 27 18:11:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05259
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 18:11:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Km91-0002eS-Pt
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 17:38:07 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KlnA-0001aM-0K
	for ietf@asgard.ietf.org; Tue, 27 May 2003 17:15:32 -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 RAA02898
	for <ietf@ietf.org>; Tue, 27 May 2003 17:15:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kllb-0001h3-00
	for ietf@ietf.org; Tue, 27 May 2003 17:13:55 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kllb-0001h0-00
	for ietf@ietf.org; Tue, 27 May 2003 17:13:55 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4RLFTjh015030
	for <ietf@ietf.org>; Tue, 27 May 2003 23:15:29 +0200 (CEST)
Message-ID: <043701c32495$19c34320$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <A46BBDB345A7D5118EC90002A5072C7806BEB75E@orsmsx116.jf.intel.com>
Subject: Re: spam
Date: Tue, 27 May 2003 23:15:29 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Atul writes:

> In short, this should belong in some general purpose
> Internet Security Forum discussions.

Spam is not a security issue, just a nuisance.



From owner-ietf@ietf.org  Tue May 27 18:11:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05258
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 18:11:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KmGt-0002lI-GT
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 17:46:15 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KlyR-0001mB-PX
	for ietf@asgard.ietf.org; Tue, 27 May 2003 17:27:11 -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 RAA03199
	for <ietf@ietf.org>; Tue, 27 May 2003 17:27:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Klwt-0001lD-00
	for ietf@ietf.org; Tue, 27 May 2003 17:25:35 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Klws-0001l6-00
	for ietf@ietf.org; Tue, 27 May 2003 17:25:34 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 207984; Tue, 27 May 2003 16:26:28 -0500
Message-ID: <3ED3D821.30601@ehsco.com>
Date: Tue, 27 May 2003 16:26:57 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: John Stracke <jstracke@centive.com>, ietf@ietf.org
Subject: Re: spam
References: <Pine.LNX.4.44.0305271552070.8489-100000@commander.av8.net>
In-Reply-To: <Pine.LNX.4.44.0305271552070.8489-100000@commander.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/27/2003 3:39 PM Dean Anderson wrote:

> I read the ruling, too.  The district court said that the government 
> failed to satisfy the tests for restriction of commercial speech, as 
> outlined in Central Hudson. The appeals court reversed.

This is more waffling, and is useless. The constituionality of the law was
upheld. Everything else is irrelevant.

> However, this is an interesting case, since American Blast Fax was not 
> represented in the Appeal, and had apparently gone out of business.

More waffling. Even if this mattered, the other defendant (fax.com) was
still in business. Not that it matters, since the court specifically
upheld the validity of the law.

> In other words, cost plays a big part in the decision.  But as has been
> so roundly demonstrated, the cost associated with email is practically 
> non-existant, and does not ever cost any user more than $1 or $2 per 
> month, which they pay for email services.

The cost of a fax to a typical organization with bulk purchasing power is
probably on the order of $.02 per page, including the paper and ink used.
Using thermal paper from a retailer averages out to about $.06 per page.
It is very easy to demonstrate per-message costs in that same ballpark for
spam, especially once we get measured-rate circuits involved. That you do
not suffer from these burdens does not mean that nobody should be
protected from them.

As has been stated, the junk fax laws are not limited to cost protection,
and also address the usability arguments. It has been successfully proven
in this discussion that a sufficiently high volume of spam makes email
less useful for its owner.

You continue to exhibit an extraordinary willingness to argue your
opinions against the facts.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Tue May 27 18:13:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05623
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 18:13:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KmGt-0002lf-Ro
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 17:46:15 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Km0p-0001nN-2k
	for ietf@asgard.ietf.org; Tue, 27 May 2003 17:29:39 -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 RAA03256
	for <ietf@ietf.org>; Tue, 27 May 2003 17:29:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KlzH-0001m2-00
	for ietf@ietf.org; Tue, 27 May 2003 17:28:03 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KlzG-0001lz-00
	for ietf@ietf.org; Tue, 27 May 2003 17:28:02 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S29487> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 27 May 2003 14:29:35 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'IETF'" <ietf@ietf.org>
Subject: The utilitiy of IP is at stake here
Date: Tue, 27 May 2003 14:29:25 -0700
Message-ID: <02b001c32497$0c11a350$2a134104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <70275C55-8FD6-11D7-98C2-000393414368@yahoo.com>
Importance: Normal
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA05623

S Woodside wrote, RE: spam
> How about the cost of legitimate emails that get filtered and never 
> read. Not everyone scans the list to check for false positives.

In a major example of false positives, we already have examples of one
real cost of spam. AOL (as one example of many) has declared ranges of
IP addresses marked 'residential' as invalid for running a particular
application. In this case SMTP, but which app is next? There is a 'guilt
by association' presumption here by the operations community, which when
carried into other applications results in substantially limited value
in the core IP protocol. 

With this type of policy, the operations community is dictating which
applications can be run from specific ranges of IP addresses. This would
be comparable to the phone companies dictating that modems couldn't be
used from phone numbers that were allocated for voice use. Clearly the
operations community is fighting back with the limited tool set they
have, but they are setting a very dangerous precedent in the process. 

While the IETF can't dictate operational process, it must defend the
open and free use of its core protocol. Part of that defense means
finding architecturally viable alternatives to the evolving operational
hacks. One approach would be to undeniably associate an IP address with
a person, so existing legal recourse would be simplified. Privacy
advocates would take issue with that approach, so another would be to
encode the exact location of the source in the address, and use strict
RPF to enforce it. Location coupled with time would provide the legal
system with needed evidence, without compromising personal privacy.
There are likely other options, and issues to discuss, but we should not
just push this out as 'hard so it must be research'. The open utility of
IP is at stake here.

Tony 







From owner-ietf@ietf.org  Tue May 27 18:22:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06157
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 18:22:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KmdA-0007bM-F4
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 18:09:16 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KmA9-0002g7-PW
	for ietf@asgard.ietf.org; Tue, 27 May 2003 17:39:17 -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 RAA03705
	for <ietf@ietf.org>; Tue, 27 May 2003 17:39:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Km8b-0001rY-00
	for ietf@ietf.org; Tue, 27 May 2003 17:37:41 -0400
Received: from [64.70.31.5] (helo=www.darkuncle.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Km8a-0001rT-00
	for ietf@ietf.org; Tue, 27 May 2003 17:37:41 -0400
Received: from www.darkuncle.net (nibbles@localhost [127.0.0.1])
	by www.darkuncle.net (8.12.9/8.12.9) with ESMTP id h4RLd1Wq034793;
	Tue, 27 May 2003 14:39:01 -0700 (PDT)
	(envelope-from sfrancis@darkuncle.net)
Received: (from sfrancis@localhost)
	by www.darkuncle.net (8.12.9/8.12.9/Submit) id h4RLd1na034792;
	Tue, 27 May 2003 14:39:01 -0700 (PDT)
Date: Tue, 27 May 2003 14:39:00 -0700
From: Scott Francis <darkuncle@darkuncle.net>
To: Anthony Atkielski <anthony@atkielski.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: spam
Message-ID: <20030527213900.GG99106@darkuncle.net>
References: <000501c32253$f6707160$92082b45@a> <093001c322af$60b28800$0a00000a@atkielski.com> <3ED0D8B3.8070303@ehsco.com> <Pine.GSO.4.50.0305251626220.24020-100000@argos.ee.surrey.ac.uk> <3ED120AE.9000306@ehsco.com> <020b01c32353$f73d18e0$0a00000a@atkielski.com> <200305261609.h4QG9Ka7012963@turing-police.cc.vt.edu> <005e01c323ce$ab9f3a00$0a00000a@atkielski.com> <200305262235.h4QMZfbM005514@turing-police.cc.vt.edu> <012e01c323d8$447237b0$0a00000a@atkielski.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="Yb+qhiCg54lqZFXW"
Content-Disposition: inline
In-Reply-To: <012e01c323d8$447237b0$0a00000a@atkielski.com>
User-Agent: Mutt/1.3.25i
X-Operating-System: OpenBSD <http://www.openbsd.org>
X-PGP-Fingerprint: 7429 F75D D3F5 FA45 C6D7  D25B 59A0 7B8C 5537 F527
X-What-Happen: Somebody set up us the bomb.
Sender: owner-ietf@ietf.org
Precedence: bulk


--Yb+qhiCg54lqZFXW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, May 27, 2003 at 12:43:46AM +0200, anthony@atkielski.com said:
> Valdis writes:
>=20
> > Yes, one vendor has an unfortunate inability
> > to properly follow the MIME spec and drop
> > unrecognized multipart/* to multipart/mixed
> > as required.
>=20
> Only one correspondent sends e-mial with this problem.

Only one correspondent that you have received mail from, in this thread.
(Make that two now.)

> > Complain to your vendor or use a RFC-compliant MUA.
>=20
> No, I have a better idea:  I'll just trash all the messages from the one
> correspondent that can't join the mainstream.

So your solution is to eliminate the symptom rather than fix the problem?
Nice.
--=20
Scott Francis || darkuncle (at) darkuncle (dot) net
      illum oportet crescere me autem minui

--Yb+qhiCg54lqZFXW
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+09r0WaB7jFU39ScRAp+RAKCZWZz9RzURl1BHqjbKkbk7YDmWfwCeM2w4
fXTYFdG7gioTrX642Kk1PpI=
=m5bt
-----END PGP SIGNATURE-----

--Yb+qhiCg54lqZFXW--



From owner-ietf@ietf.org  Tue May 27 18:37:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06757
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 18:37:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KmnU-0002Mg-Le
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 18:19:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KmV6-0003Yc-ME
	for ietf@asgard.ietf.org; Tue, 27 May 2003 18:00:56 -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 SAA04204
	for <ietf@ietf.org>; Tue, 27 May 2003 18:00:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KmTY-0001yg-00
	for ietf@ietf.org; Tue, 27 May 2003 17:59:20 -0400
Received: from smtpzilla5.xs4all.nl ([194.109.127.141])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KmTX-0001yd-00
	for ietf@ietf.org; Tue, 27 May 2003 17:59:19 -0400
Received: from TheLady (a213-84-140-41.adsl.xs4all.nl [213.84.140.41])
	by smtpzilla5.xs4all.nl (8.12.9/8.12.9) with ESMTP id h4RM0lVB097307;
	Wed, 28 May 2003 00:00:48 +0200 (CEST)
From: "Fam. van den Berg" <inanbe@xs4all.nl>
To: "'Michel Py'" <michel@arneill-py.sacramento.ca.us>,
        "'Paul Vixie'" <vixie@vix.com>, <ietf@ietf.org>
Subject: RE: spam
Date: Wed, 28 May 2003 00:01:01 +0200
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAgz55/h9tW0GXHZYRsfdCb8KAAAAQAAAAipggkAUXw0KYX7iEX/niGQEAAAAA@xs4all.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 1 (Highest)
X-MSMail-Priority: High
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: High
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F82C@server2000.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Just a simple question: Can spam mail be caused by violating RFC 2821?

-----Oorspronkelijk bericht-----
Van: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] Namens Michel Py
Verzonden: dinsdag 27 mei 2003 22:26
Aan: Paul Vixie; ietf@ietf.org
Onderwerp: RE: spam


Paul,

> Paul Vixie wrote:
> [large snap]
> my own ideas have to do with trustbrokers, certificates for both 
> mailboxes and transfer/relay agents, and provable confidence in 
> subjective values. but maybe all that's just crap, and what's actually

> necessary and sufficient would have a completely different look/feel 
> to it than anything i've yet considered.

I'm with you here, but keep reading.


> we (the e-mail producing/consuming community) have the technology, we 
> have the collective wit and wisdom, we have the proven commercial 
> value of the service.  what we lack, dear ietf, is simply: leadership.

Given what you wrote just above (which I agree with), what is your
assessment that a system such as what you have in mind would
successfully reach IETF consensus?

Look just the past 2 days how many trolls posted on this ML to lobby for
the spammer's cause.

The reason I agree with Noel along the lines that the only way is making
spammers pay for sending email is not because I don't think that we
don't have what it takes to invent a protocol, but because I think it
will be torpedoed before it is born.

Michel.








From owner-ietf@ietf.org  Tue May 27 18:40:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06944
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 18:40:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KmnV-0002Oj-AQ
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 18:19:57 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kmcn-0007MO-Qt
	for ietf@asgard.ietf.org; Tue, 27 May 2003 18:08:53 -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 SAA05005
	for <ietf@ietf.org>; Tue, 27 May 2003 18:08:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KmbF-00023p-00
	for ietf@ietf.org; Tue, 27 May 2003 18:07:17 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KmbF-00023f-00
	for ietf@ietf.org; Tue, 27 May 2003 18:07:17 -0400
Content-class: urn:content-classes:message
Subject: RE: spam
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Tue, 27 May 2003 15:08:43 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F5067149@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: spam
Thread-Index: AcMkm34ikeBUYoCZQtuaA8GdeVLzNgAAOOZQ
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Fam. van den Berg" <inanbe@xs4all.nl>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA06944

> Fam. van den Berg wrote:
> Just a simple question: Can spam mail be caused by
> violating RFC 2821?

What do you mean by "violating"?

Michel.




From owner-ietf@ietf.org  Tue May 27 18:43:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07140
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 18:43:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kn1J-0003Oz-Ld
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 18:34:13 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kmm5-0002LL-7D
	for ietf@asgard.ietf.org; Tue, 27 May 2003 18:18:29 -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 SAA06091
	for <ietf@ietf.org>; Tue, 27 May 2003 18:18:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KmkW-0002Df-00
	for ietf@ietf.org; Tue, 27 May 2003 18:16:52 -0400
Received: from 75.5.33.65.cfl.rr.com ([65.33.5.75] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KmkW-0002Dc-00
	for ietf@ietf.org; Tue, 27 May 2003 18:16:52 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19KSl2-0006AK-00; Mon, 26 May 2003 20:56:05 -0400
Date: Mon, 26 May 2003 20:56:02 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Tony Hain <alh-ietf@tndh.net>
cc: "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <02b001c32497$0c11a350$2a134104@eagleswings>
Message-ID: <Pine.LNX.4.44.0305262054330.23359-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 27 May 2003, Tony Hain wrote:

> S Woodside wrote, RE: spam
> > How about the cost of legitimate emails that get filtered and never
> > read. Not everyone scans the list to check for false positives.

Below is an example for HAVING open relays, as a host on a "residential"
IP can use an open relay for outgoing, and therefore communicate with
aol/roadrunner/etc users.  a minor mod to the config of the MTA and there
you go.

scott


>
> In a major example of false positives, we already have examples of one
> real cost of spam. AOL (as one example of many) has declared ranges of
> IP addresses marked 'residential' as invalid for running a particular
> application. In this case SMTP, but which app is next? There is a 'guilt
> by association' presumption here by the operations community, which when
> carried into other applications results in substantially limited value
> in the core IP protocol.
>
> With this type of policy, the operations community is dictating which
> applications can be run from specific ranges of IP addresses. This would
> be comparable to the phone companies dictating that modems couldn't be
> used from phone numbers that were allocated for voice use. Clearly the
> operations community is fighting back with the limited tool set they
> have, but they are setting a very dangerous precedent in the process.
>
> While the IETF can't dictate operational process, it must defend the
> open and free use of its core protocol. Part of that defense means
> finding architecturally viable alternatives to the evolving operational
> hacks. One approach would be to undeniably associate an IP address with
> a person, so existing legal recourse would be simplified. Privacy
> advocates would take issue with that approach, so another would be to
> encode the exact location of the source in the address, and use strict
> RPF to enforce it. Location coupled with time would provide the legal
> system with needed evidence, without compromising personal privacy.
> There are likely other options, and issues to discuss, but we should not
> just push this out as 'hard so it must be research'. The open utility of
> IP is at stake here.
>
> Tony
>
>
>
>
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81




From owner-ietf@ietf.org  Tue May 27 18:54:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07514
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 18:54:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kn7g-00045V-U9
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 18:40:48 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kmrr-000397-Fj
	for ietf@asgard.ietf.org; Tue, 27 May 2003 18:24:27 -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 SAA06359
	for <ietf@ietf.org>; Tue, 27 May 2003 18:24:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KmqJ-0002IF-00
	for ietf@ietf.org; Tue, 27 May 2003 18:22:51 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KmqI-0002IC-00
	for ietf@ietf.org; Tue, 27 May 2003 18:22:50 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19Kmrk-000BO7-00; Tue, 27 May 2003 17:24:20 -0500
Date: Tue, 27 May 2003 18:24:20 -0400
From: John C Klensin <klensin@jck.com>
To: "alh-ietf@tndh.net" <alh-ietf@tndh.net>, "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
Message-ID: <15058072.1054059860@p3.JCK.COM>
In-Reply-To: <02b001c32497$0c11a350$2a134104@eagleswings>
References:  <02b001c32497$0c11a350$2a134104@eagleswings>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Tuesday, 27 May, 2003 14:29 -0700 Tony Hain 
<alh-ietf@tndh.net> wrote:

>...
> With this type of policy, the operations community is
> dictating which applications can be run from specific ranges
> of IP addresses. This would be comparable to the phone
> companies dictating that modems couldn't be used from phone
> numbers that were allocated for voice use.

Of course, the then-Deutschebundespost was trying to do exactly 
that well into the 1990s.

I agree with your note, and how others find it useful in putting 
the topic in perspective.

    john




From owner-ietf@ietf.org  Tue May 27 19:05:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08049
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 19:05:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kn7h-00047E-QO
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 18:40:49 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KmuL-0003DC-0L
	for ietf@asgard.ietf.org; Tue, 27 May 2003 18:27:01 -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 SAA06460
	for <ietf@ietf.org>; Tue, 27 May 2003 18:26:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kmsm-0002Kw-00
	for ietf@ietf.org; Tue, 27 May 2003 18:25:24 -0400
Received: from pop017pub.verizon.net ([206.46.170.210] helo=pop017.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kmsm-0002K7-00
	for ietf@ietf.org; Tue, 27 May 2003 18:25:24 -0400
Received: from earthlink.net ([4.65.81.213]) by pop017.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030527222628.QVMM27254.pop017.verizon.net@earthlink.net>;
          Tue, 27 May 2003 17:26:28 -0500
Message-ID: <3ED3E536.60BCD64E@earthlink.net>
Date: Tue, 27 May 2003 15:22:46 -0700
From: Peter Deutsch <pdeutsch@earthlink.net>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: ietf@ietf.org
Subject: Re: spam
References: <Pine.LNX.4.44.0305271552070.8489-100000@commander.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at pop017.verizon.net from [4.65.81.213] at Tue, 27 May 2003 17:26:28 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

g'day,

Dean Anderson wrote:
...
> In other words, cost plays a big part in the decision.  But as has been so
> roundly demonstrated, the cost associated with email is practically
> non-existant, and does not ever cost any user more than $1 or $2 per
> month, which they pay for email services.

Dammit, I'm trying to be good but you insist on repeating this canard,
despite the fact that the vast majority of folks have *not* agreed with
you, and some of us have specifically challenged (I wont be so
presumptuous as to say "refuted") your claim.

Gas in Southern California can currently be had for as little as $US1.61
a gallon. It's possible to buy a 200 Gig hard drive from Fry's in
California for about $US140. It's possible to buy advertizing supported,
limited storage public email accounts for a few dollars a month (heck,
you can even get "free" accounts at no cash outlay to you).  This does
not mean that a car that gets 30 miles per gallon costs 5.3 cents a
month to run; this does not mean you can build a commercial quality file
server for under $200; And it most certainly does not mean that email
costs anyone "only $1 or $2 per month".

If you continue to repeat this claim using such words as "roundly
demonstrated", I will conclude that you are either a poor engineer or a
troll. In either case, you will eventually provoke taunts and jears from
the audience, and we're trying very hard to raise the tone of this
place. So please, cease and desist such activity at once.

And even if you can't master engineering math, you really should
consider learning some basic economics. If nothing else, it might be
useful to you in balancing your checkbook.


> This is substantially different from the case with faxes. And it does seem
> to be a valid arguement that if technology does eliminate the burdens
> imposed, then the junk fax law could be reversed.
> 
> In the case of spam, there is no cost _shifting_ whatsoever, since by
> definition, everyone pays their own way. Even spammers.  Unlike faxes, the
> receipt of a spam does not increase the cost of the recipient's email.
> Email is usually fixed cost, and flat rate.  Even when one pays by the
> octet, the cost of a spam is in the millionths of a cent, which I think
> is less than the cost to carry out the trash of one junk postal mail.

As we say in French, "Ca c'est des horse patooties". Again, the cost of
email is not merely the cost of the physical file storage, you need to
consider the cost of your time processing it, the cost of time spent
dealing with such things as denial of service attacks, the opportunity
costs paid when folks hijack resources from their legitimate purpose and
so on. There is also a "social cost" when, for example parents must
forego having their children use email because of fears they will be
exposed to the most egregious porn and violence. Ask for, or help
develop, metrics for measuring such costs, but please do not deny their
existance.

The cost of physical delivery and storage are but a small part of the
total cost of ownership here. By ignoring all but the upfront costs, it
looks suspiciously like you're trying to lend legitimacy to odious
practices by sleight-of-hand mathematics. Shame on you...



				- peterd

-- 
---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software

                        "Bungle..."
               "That's an 'i', you idiot..."
                  "Oh, right. 'Bingle..."

                            - Red versus Blue...

---------------------------------------------------------------------



From owner-ietf@ietf.org  Tue May 27 19:05:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08047
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 19:05:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kn7h-00046K-BF
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 18:40:49 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KmsA-00039R-52
	for ietf@asgard.ietf.org; Tue, 27 May 2003 18:24:46 -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 SAA06367
	for <ietf@ietf.org>; Tue, 27 May 2003 18:24:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kmqb-0002IQ-00
	for ietf@ietf.org; Tue, 27 May 2003 18:23:09 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kmqb-0002IN-00
	for ietf@ietf.org; Tue, 27 May 2003 18:23:09 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S294A8> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 27 May 2003 15:24:43 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Michel Py'" <michel@arneill-py.sacramento.ca.us>,
        "'Paul Vixie'" <vixie@vix.com>, <ietf@ietf.org>
Subject: RE: spam
Date: Tue, 27 May 2003 15:24:38 -0700
Message-ID: <02d901c3249e$c2afce00$2a134104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F82C@server2000.arneill-py.sacramento.ca.us>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Michel Py wrote:
> The reason I agree with Noel along the lines that the only 
> way is making spammers pay for sending email is not because I 
> don't think that we don't have what it takes to invent a 
> protocol, but because I think it will be torpedoed before it is born.

Which is just another way of saying we lack leadership.

Tony




From owner-ietf@ietf.org  Tue May 27 19:08:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08296
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 19:08:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kn7i-00049A-LY
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 18:40:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KmzN-0003LF-7e
	for ietf@asgard.ietf.org; Tue, 27 May 2003 18:32:13 -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 SAA06589
	for <ietf@ietf.org>; Tue, 27 May 2003 18:32:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kmxp-0002NG-00
	for ietf@ietf.org; Tue, 27 May 2003 18:30:37 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kmxo-0002N1-00
	for ietf@ietf.org; Tue, 27 May 2003 18:30:36 -0400
Content-class: urn:content-classes:message
Subject: RE: The utilitiy of IP is at stake here
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Tue, 27 May 2003 15:32:02 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F830@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: The utilitiy of IP is at stake here
Thread-Index: AcMknUcn5P0HMyBzROWbBA1OY1d+1AAAQJvw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Tony Hain" <alh-ietf@tndh.net>, "IETF" <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id TAA08296

> Tony Hain wrote:
> AOL (as one example of many) has declared ranges of IP addresses
> marked 'residential' as invalid for running a particular application.
> In this case SMTP, but which app is next?

An especially sensitive topic here as most of us operate their own SMTP
server off the home cable or DSL.


> Clearly the operations community is fighting back with the
> limited tool set they have, but they are setting a very
> dangerous precedent in the process.

I agree, but let's not put the blame on the ops. If I had to clean 3
billion pieces of crap every day I would be tempted by using every
possible weapon I have no matter what the IETF geeks think about their
constitutional right to operate a server at home.


> The open utility of IP is at stake here.

Agree.


Michel.




From owner-ietf@ietf.org  Tue May 27 19:11:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06158
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 18:22:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KmdA-0007cL-R6
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 18:09:16 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KmDF-0002iI-01
	for ietf@asgard.ietf.org; Tue, 27 May 2003 17:42:29 -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 RAA03790
	for <ietf@ietf.org>; Tue, 27 May 2003 17:42:25 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KmBg-0001t6-00
	for ietf@ietf.org; Tue, 27 May 2003 17:40:52 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KmBg-0001t3-00
	for ietf@ietf.org; Tue, 27 May 2003 17:40:52 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h4RLgNEe006819;
	Tue, 27 May 2003 17:42:23 -0400
Message-Id: <200305272142.h4RLgNEe006819@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Re: spam 
In-Reply-To: Your message of "Tue, 27 May 2003 16:39:59 EDT."
             <Pine.LNX.4.44.0305271552070.8489-100000@commander.av8.net> 
References: <Pine.LNX.4.44.0305271552070.8489-100000@commander.av8.net>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-2031240325P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 27 May 2003 17:42:23 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-2031240325P
Content-Type: text/plain; charset=us-ascii

On Tue, 27 May 2003 16:39:59 EDT, Dean Anderson said:

> In other words, cost plays a big part in the decision.  But as has been so
> roundly demonstrated, the cost associated with email is practically
> non-existant, and does not ever cost any user more than $1 or $2 per
> month, which they pay for email services.

Umm.. it costs more than $1 or $2 per month.  One you add in all the
encumbrances like benefits and overhead, I'm somewhere close to a dollar
a *MINUTE* - and I'm far from the highest paid person here.  Assuming 20
8 hour work days in a month, I'd have to be able to "just hit delete"
on all my spam for each day in about 6 seconds or so to get in under $2/month.

Ignore all the bennies and overhead, and it's up to a whole whopping
10-15 seconds a day to deal with my entire spam load.

And you know what? I get more spam than that.  And when you total across
all the employees of this place (some who make more than I do, some that
make less), all those 2 and 3 minutes add up to a *LOT* more than just
a dollar or two a month.....

--==_Exmh_-2031240325P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+09u/cC3lWbTT17ARArllAKDyE1oQUfOJGIhivgCn0udBy6cUYgCeJdEq
BDnAHJlSa9TGXlr5homnbks=
=zSnM
-----END PGP SIGNATURE-----

--==_Exmh_-2031240325P--



From owner-ietf@ietf.org  Tue May 27 19:14:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08481
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 19:14:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kn7j-00049X-0T
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 18:40:51 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kmzc-0003LH-Ps
	for ietf@asgard.ietf.org; Tue, 27 May 2003 18:32:28 -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 SAA06598
	for <ietf@ietf.org>; Tue, 27 May 2003 18:32:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kmy4-0002NS-00
	for ietf@ietf.org; Tue, 27 May 2003 18:30:52 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kmy4-0002ND-00
	for ietf@ietf.org; Tue, 27 May 2003 18:30:52 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id SAA03585;
	Tue, 27 May 2003 18:29:26 -0400
Date: Tue, 27 May 2003 18:30:29 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Valdis.Kletnieks@vt.edu
cc: ietf@ietf.org
Subject: Re: spam 
In-Reply-To: <200305272142.h4RLgNEe006819@turing-police.cc.vt.edu>
Message-ID: <Pine.LNX.4.44.0305271756050.8489-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Then you are doing something wrong. This is not an "estimate". This is
what services actually charge.

Hotmail doesn't charge anything for mail. They probably get something
along the lines of about $1 per user per month in advertising revenue,
though.  I'm just guessing, based on web add rates. Their real revenue
could be more, it could be less.

Other services charge $1 - $2 per month for mail.

All of these services are adding in all of the benefits and overhead
necessary to perform the service.

The only real arguable harm that spam causes is annoyance.  Try to argue
costs, and you'll be trounced again. Just like in 1998.

No one has demonstrated any cost to spam, other than annoyance and
infrastructure costs which are passed on to users[1], and it seems there
is very little to add.

Despite Vixie's assertion, the "email producing/consuming" community
includes Type 1 spammers.  As others have noted, legislation is necessary
for any progress, and trying to exclude Type 1 spammers from this effort
is doomed to failure.

Vixie and other radicals also continues to ignore Shannon's theorems.  It
is impossible to carry on technical discussions with people who are
ignorant of, or simply refuse to acknowledge the relevant scientific
literature.  What remains is no longer a technical discussion at any
level, and no longer relevant to the IETF.

The assertion that anyone who argues against the anti-spammer falacies is
a spammer is also false. It is nothing other than an ad hominem.  It is a
small mind that can't respond civilly to civil argument. But as John
Gilmore writes, "anti-spammers are small-minded".

There seems to be no point in continuing the discussion. Vixie has taken
to ad hominem attacks, and someone on the IETF list is sending me
viruses[2]

		--Dean



[1] Which is why you don't see telephone companies lobbying against junk
faxes or telemarketing--kind of funny, isn't it?  You also don't see
telephone company employees sending junk faxes or making false
telemarketing calls to try to convince people that these things should be
banned, either.  Which leads me to wonder whether it will turn out that
_all_ these Type 3 spams were sent by radical anti-spammers. I don't know
yet, but I expect we will someday.


[2] I would suspect that this could be a "normal" virus infection, but the
following text in the virus message wasn't in the message I sent:

        > Get your FREE av8.com account now! <

So, it seems to be someone intentionally trying to infect me, or perhaps
defame Av8.com, but failed.


On Tue, 27 May 2003 Valdis.Kletnieks@vt.edu wrote:

> On Tue, 27 May 2003 16:39:59 EDT, Dean Anderson said:
>
> > In other words, cost plays a big part in the decision.  But as has been so
> > roundly demonstrated, the cost associated with email is practically
> > non-existant, and does not ever cost any user more than $1 or $2 per
> > month, which they pay for email services.
>
> Umm.. it costs more than $1 or $2 per month.  One you add in all the
> encumbrances like benefits and overhead, I'm somewhere close to a dollar
> a *MINUTE* - and I'm far from the highest paid person here.  Assuming 20
> 8 hour work days in a month, I'd have to be able to "just hit delete"
> on all my spam for each day in about 6 seconds or so to get in under $2/month.
>
> Ignore all the bennies and overhead, and it's up to a whole whopping
> 10-15 seconds a day to deal with my entire spam load.
>
> And you know what? I get more spam than that.  And when you total across
> all the employees of this place (some who make more than I do, some that
> make less), all those 2 and 3 minutes add up to a *LOT* more than just
> a dollar or two a month.....
>





From owner-ietf@ietf.org  Tue May 27 19:41:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07512
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 18:54:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kn7f-00040y-OG
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 18:40:47 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KmpV-0002SK-9n
	for ietf@asgard.ietf.org; Tue, 27 May 2003 18:22:01 -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 SAA06142
	for <ietf@ietf.org>; Tue, 27 May 2003 18:21:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kmnx-0002EK-00
	for ietf@ietf.org; Tue, 27 May 2003 18:20:25 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kmnw-0002EH-00
	for ietf@ietf.org; Tue, 27 May 2003 18:20:24 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4RMLwjh015652
	for <ietf@ietf.org>; Wed, 28 May 2003 00:21:58 +0200 (CEST)
Message-ID: <046f01c3249e$636d3540$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <02b001c32497$0c11a350$2a134104@eagleswings>
Subject: Re: The utilitiy of IP is at stake here
Date: Wed, 28 May 2003 00:21:58 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony writes:

> In a major example of false positives, we already
> have examples of one real cost of spam. AOL (as one
> example of many) has declared ranges of IP addresses
> marked 'residential' as invalid for running a particular
> application.

AOL bounces all of my e-mail, but they are unable to explain why they are
doing this.  A call to their center for network problems produced no
results; when the person I spoke to did not understand what I meant by MX
records, I knew that I was wasting my time.

I finally modified my sendmail config to bounce everything from AOL.  Since
I can't answer anyone in that domain, there's no point in receiving their
e-mail, and perhaps by bouncing it they'll at least know that they won't be
getting a reply.

The interesting thing is, when I examine my mail logs, almost all the mail I
get from aol.com is spam, anyway!  So by bouncing all their incoming mail, I
suppose I gain more than I lose.

> This would be comparable to the phone companies
> dictating that modems couldn't be used from phone
> numbers that were allocated for voice use.

Wasn't that once actually the case?

> While the IETF can't dictate operational process, it
> must defend the open and free use of its core protocol.

I agree.  And AOL is a major offender in many ways.  There's the real
Internet, and then there's the "AOL Internet"--not unlike the Matrix,
actually.





From owner-ietf@ietf.org  Tue May 27 19:47:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09290
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 19:47:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Knkh-00020k-1V
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 19:21:07 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KnS1-0000AK-Gp
	for ietf@asgard.ietf.org; Tue, 27 May 2003 19:01:49 -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 TAA07930
	for <ietf@ietf.org>; Tue, 27 May 2003 19:01:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KnQT-0002lv-00
	for ietf@ietf.org; Tue, 27 May 2003 19:00:13 -0400
Received: from [65.87.223.31] (helo=gambit)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KnQS-0002lI-00
	for ietf@ietf.org; Tue, 27 May 2003 19:00:13 -0400
Received: from vulcan ([65.87.223.41])
        by gambit (|-DNSH-| mail service) with SMTP id JCA74076
        for <ietf@ietf.org>; Tue, 27 May 2003 19:01:11 -0400
Message-Id: <4.2.0.58.20030527185839.012a0d88@x>
X-Sender: noc@gambit.nso.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Tue, 27 May 2003 19:01:02 -0400
To: ietf@ietf.org
From: noc <noc@nso.org>
Subject: contact
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F5067149@server2000.arneill-
 py.sacramento.ca.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk



Paul Vixie:
Could you please email me off list ?
Thanks
Bert Fortrie
noc@nso.org





From owner-ietf@ietf.org  Tue May 27 19:47:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09313
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 19:47:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Knkh-00020v-CU
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 19:21:07 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KnTF-0000AP-DA
	for ietf@asgard.ietf.org; Tue, 27 May 2003 19:03:05 -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 TAA07954
	for <ietf@ietf.org>; Tue, 27 May 2003 19:02:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KnRd-0002m7-00
	for ietf@ietf.org; Tue, 27 May 2003 19:01:25 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KnRd-0002m4-00
	for ietf@ietf.org; Tue, 27 May 2003 19:01:25 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19KnSy-000BZd-00; Tue, 27 May 2003 18:02:48 -0500
Date: Tue, 27 May 2003 19:02:47 -0400
From: John C Klensin <john-ietf@jck.com>
To: shogunx <shogunx@sleekfreak.ath.cx>, Tony Hain <alh-ietf@tndh.net>
cc: "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
Message-ID: <17365440.1054062167@p3.JCK.COM>
In-Reply-To: <Pine.LNX.4.44.0305262054330.23359-100000@sleekfreak.ath.cx>
References:  <Pine.LNX.4.44.0305262054330.23359-100000@sleekfreak.
 ath.cx>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Scott,

Good try, but no cigar.  This would be entirely reasonable if 
open relays were the only way to accomplish what you are after. 
But, if open relays were used this way, the spam flow through 
those open relays are such that "aol/roadrunner/etc" would start 
blocking the IP addresses of those relays.  Back to square one, 
with no gain.

Instead, there are at least two options available for that host 
on a "residential" network (both in heavy use today):

	(i) The host uses a relay supplied by its ISP, one that
	is not blocked by "aol/roadrunner/etc".  This is more or
	less satisfactory depending on what additional
	restrictions the ISP imposes on that relay, but the
	typical restrictions (much as I think they are
	unreasonable) have very little impact on the typical
	residential user who corresponds actively with
	"aol/roadrunner/etc users".
	
	(ii) The host uses a relay with which its owners have
	established some sort of business relationship and which
	relay is in a position to authenticate the host (via SSL
	certificates, SMTP AUTH, or some combination of a tunnel
	and authentication).

I was a big fan of open relays a decade ago, but am no longer 
convinced that they are the required solution to any problem we 
need to solve.

And, no, I don't believe that either of the measures above will 
significantly reduce the volume of spam.  After all, the volume 
of spam is much higher today than it was when open relays were 
the norm, worldwide.  One can reasonably speculate on whether 
the spam volume would be even higher if open relays were more 
readily accessible, but, as many others have pointed out in 
other ways, that really isn't the point.

      john


--On Monday, 26 May, 2003 20:56 -0400 shogunx 
<shogunx@sleekfreak.ath.cx> wrote:

> On Tue, 27 May 2003, Tony Hain wrote:
>
>> S Woodside wrote, RE: spam
>> > How about the cost of legitimate emails that get filtered
>> > and never read. Not everyone scans the list to check for
>> > false positives.
>
> Below is an example for HAVING open relays, as a host on a
> "residential" IP can use an open relay for outgoing, and
> therefore communicate with aol/roadrunner/etc users.  a minor
> mod to the config of the MTA and there you go.
>
> scott
>
>
>>
>> In a major example of false positives, we already have
>> examples of one real cost of spam. AOL (as one example of
>> many) has declared ranges of IP addresses marked
>> 'residential' as invalid for running a particular
>> application. In this case SMTP, but which app is next? There
>> is a 'guilt by association' presumption here by the
>> operations community, which when
>...






From owner-ietf@ietf.org  Tue May 27 19:47:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09340
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 19:47:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kntn-0002JT-1n
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 19:30:31 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kncs-0001MR-Jr
	for ietf@asgard.ietf.org; Tue, 27 May 2003 19:13:02 -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 TAA08452
	for <ietf@ietf.org>; Tue, 27 May 2003 19:12:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KnbK-0002vi-00
	for ietf@ietf.org; Tue, 27 May 2003 19:11:26 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KnbJ-0002vS-00
	for ietf@ietf.org; Tue, 27 May 2003 19:11:25 -0400
Content-class: urn:content-classes:message
Subject: RE: spam
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Tue, 27 May 2003 16:12:51 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F506714E@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: spam
Thread-Index: AcMkpJxPx2WdN6+/Q6uwAbG7w3RI/AAAIcKw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: <pdeutsch@earthlink.net>
Cc: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id TAA09340

> Peter Deutsch wrote:
> As we say in French, "Ca c'est des horse patooties".

I'm French. We don't say things that polite.

Peter, stop feeding the trolls; it's not good for your blood pressure.
Go home. Have a beer.

Michel.




From owner-ietf@ietf.org  Tue May 27 19:56:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09744
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 19:56:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Knto-0002MH-Q4
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 19:30:32 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KniJ-0001vH-P2
	for ietf@asgard.ietf.org; Tue, 27 May 2003 19:18:39 -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 TAA08657
	for <ietf@ietf.org>; Tue, 27 May 2003 19:18:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kngl-000309-00
	for ietf@ietf.org; Tue, 27 May 2003 19:17:03 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kngj-0002zi-00
	for ietf@ietf.org; Tue, 27 May 2003 19:17:02 -0400
Received: from localhost (dwm@localhost)
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h4RNBcm02040
	for <ietf@ietf.org>; Tue, 27 May 2003 16:11:38 -0700
Date: Tue, 27 May 2003 16:11:38 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: spam
In-Reply-To: <kjisrxa2mb.fsf@romeo.rtfm.com>
Message-ID: <Pine.LNX.4.33.0305271604330.865-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On 26 May 2003, Eric Rescorla wrote:

> Dean Anderson <dean@av8.com> writes:
> > There is no cost to spam. It is purely an annoyance factor.
> This strikes me as a pretty limited way to measure cost.
>
> To the extent to which people would be willing to pay to not be
> spammed, then spam is costing them happiness (an economist would say
> utility). That cost is no less real than if it were using up their
> disk space. To be concrete about it, consider the amount of money
> being spent on spam-suppression. That's a direct cost imposed by spam.

Another direct cost is the emotional unhappiness caused by some of the
filthy SPAM offering views of barnyard frolic, etc. Some of the stuff my
wife receives these days is pretty disgusting. Changing email addresses is
not a practical alternative because of the legitimate random email she
receives. As a society, there is also a cost when some folks avoid use of
email because of stress of having to deal with the trash.

Dave Morris




From owner-ietf@ietf.org  Tue May 27 20:03:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09971
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 20:03:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ko8K-0003Bt-Ta
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 19:45:32 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Knqt-0002F6-HU
	for ietf@asgard.ietf.org; Tue, 27 May 2003 19:27:31 -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 TAA08779
	for <ietf@ietf.org>; Tue, 27 May 2003 19:27:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KnpL-000321-00
	for ietf@ietf.org; Tue, 27 May 2003 19:25:55 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KnpK-00031x-00
	for ietf@ietf.org; Tue, 27 May 2003 19:25:54 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19Knqq-000Bey-00; Tue, 27 May 2003 18:27:28 -0500
Date: Tue, 27 May 2003 19:27:28 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Fam. van den Berg" <inanbe@xs4all.nl>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: spam
Message-ID: <18846359.1054063648@p3.JCK.COM>
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAgz55/h9tW0GXHZYRsfdCb8KAAAAQAAAAipggkAUXw0KYX7iEX/niGQEAAAAA@xs4all.nl>
References:  <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAgz55/
 h9tW0GXHZYRsfdCb8KAAAAQAAAAipggkAUXw0KYX7iEX/niGQEAAAAA@xs4all.nl>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Wednesday, 28 May, 2003 00:01 +0200 "Fam. van den Berg" 
<inanbe@xs4all.nl> wrote:

> Just a simple question: Can spam mail be caused by violating
> RFC 2821?

Michel asked what you mean by "violating".   I would add, and 
what do you mean by "caused"?

If I may guess at the question...

It is the case that most spam email that I've looked at recently 
is non-comformant to RFC2821 in one detail or another, usually 
in the order of Received fields as they try to fake those data, 
rather than in the envelope (serious protocol violations in the 
envelope typically result in non-delivery).  But there is little 
or no evidence that even optimally-positioned filters that would 
reject or drop all non-conforming messages would significantly 
reduce the volume of spam over any long period of time.  Such 
filters would also drop legitimate mail originating from at 
least some versions of what are probably the two most common 
desktop mail clients today (one might debate whether that would 
be a good thing --it would certainly help with virus/worm 
control-- but it isn't a spam issue).

The evidence is that, if it became clear that a serious effort 
was developing to deploy such filters, the spammers would start 
sending conforming messages more rapidly than the filters could 
actually be spun up.  Would this inconvenience them, or the 
authors of spam tools?  Yes, but almost certainly not very much 
or for very long.  It would, perversely, actually help the 
businesses of the spam tool builders: "get your new, updated, 
standards-conforming bulk mailer here and get past the new 
2821-conformance-testing filters".

      john




From owner-ietf@ietf.org  Tue May 27 20:03:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09976
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 20:03:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ko8L-0003Bz-8p
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 19:45:33 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KnrN-0002F9-V4
	for ietf@asgard.ietf.org; Tue, 27 May 2003 19:28:01 -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 TAA08787
	for <ietf@ietf.org>; Tue, 27 May 2003 19:27:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Knpp-00032U-00
	for ietf@ietf.org; Tue, 27 May 2003 19:26:25 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Knpp-00031y-00
	for ietf@ietf.org; Tue, 27 May 2003 19:26:25 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id TAA24823;
	Tue, 27 May 2003 19:23:16 -0400
Date: Tue, 27 May 2003 19:24:09 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: "Eric A. Hall" <ehall@ehsco.com>
cc: John Stracke <jstracke@centive.com>, <ietf@ietf.org>
Subject: Re: spam
In-Reply-To: <3ED3D821.30601@ehsco.com>
Message-ID: <Pine.LNX.4.44.0305271831130.8489-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 27 May 2003, Eric A. Hall wrote:

>
> on 5/27/2003 3:39 PM Dean Anderson wrote:
>
> > I read the ruling, too.  The district court said that the government
> > failed to satisfy the tests for restriction of commercial speech, as
> > outlined in Central Hudson. The appeals court reversed.
>
> This is more waffling, and is useless. The constituionality of the law was
> upheld. Everything else is irrelevant.

The text you quote is summary of the case. It is not waffling. It is
neutral fact.

> > However, this is an interesting case, since American Blast Fax was not
> > represented in the Appeal, and had apparently gone out of business.
>
> More waffling. Even if this mattered, the other defendant (fax.com) was
> still in business. Not that it matters, since the court specifically
> upheld the validity of the law.

No waffling. I don't know if it matters. Neither do you. It matters in
other situations, and so its a valid question. But it is an answerable
question, I'm sure.  It seems you are afraid to have the question
answered, so you attack the questioner.

Perhaps you can stick to facts. It is poor debating style to try to appear
to gain points by putting words in your opponents mouth. Someone else just
said that, and its true.

> > In other words, cost plays a big part in the decision.  But as has been
> > so roundly demonstrated, the cost associated with email is practically
> > non-existant, and does not ever cost any user more than $1 or $2 per
> > month, which they pay for email services.
>
> The cost of a fax to a typical organization with bulk purchasing power is
> probably on the order of $.02 per page, including the paper and ink used.
> Using thermal paper from a retailer averages out to about $.06 per page.
> It is very easy to demonstrate per-message costs in that same ballpark for
> spam, especially once we get measured-rate circuits involved. That you do
> not suffer from these burdens does not mean that nobody should be
> protected from them.

No, this isn't true. If you pay $1 per month for email, and get 50
messages per day, then a spam costs you $0.0006666. A 6 cent fax costs
100 times this. Of course, this is a flat rate service, and you pay
nothing extra for having received the spam. You only have the annoyance of
having to delete it. It is a valid point to say that spam cost nothing
whatsoever in this case. The user pays $1 no matter what.  If the ISP is
concerned with the cost, then one has to question whether the ISP is just
seeking a monopoly control over advertising to its users.

If you pay $30 per 15Gigabytes (a relatively high metered rate) then a
1Kbyte spam costs $0.000002. A 6 cent fax costs 30,000 times this.

If you pay $599/mo for a T1, then a 1K byte spam costs you $0.0000012. A 6
cent fax costs about 50,000 times this.

If you buy bandwidth at the OC3+ level, you get bandwidth at around
$250/per meg or less.  At that rate, a 1K byte spam costs you $0.00000077.
A 6 cent fax costs about 78,000 times this.

There is simply no way you can put spam costs in the same ballpark as
faxes, without a lot of lying that is easy to debunk.

If you try to raise the cost of email, the so-called "charge-for-email"
schemes, one runs into charges of gouging and price fixing. Such schemes
are illegal.  Gouging customers is not going to help you get a law passed.

Basically, even at $1 per month, users are getting gouged for email
services. Prices will no doubt drop even further. Much less than that, and
its not worth the credit card fees.  Probably, everyone will stop charging
for email altogether, like Hotmail.

> As has been stated, the junk fax laws are not limited to cost protection,
> and also address the usability arguments.

No, the Appeals court didn't find that at all. Apparently, you didn't
actually read the decision.  The Appeals court decision, and the law,
revolved around the costs imposed on the recipient. The Appeals court also
left open the possibility that if the technology makes the burdens less in
the future, then the law might be overturned. The court didn't find that
the argument was not-applicable, but rather that the premise of the
District Court that the technology had made the burdens insignificant was
factually wrong.  There is a difference. What you are trying to say is
that it doesn't matter what the costs are. It does indeed matter.

> It has been successfully proven in this discussion that a sufficiently
> high volume of spam makes email less useful for its owner.

No, that hasn't been proven, either. It is frequently asserted, but fact
is just the opposite. People are using email more than ever. Spam has had
no effect on the useability of email.  I get 200+ spams a day. It hasn't
affected my usuability at all.  No one is complaining about the high cost
of their email service.  There are some people that are annoyed, but it
seems that anti-spammers are responsible (in part at least) for the
annoyance.

The cases where crashed servers have been reported are frequently not due
to Type 1 spam, but are due to Type 3 attacks and DOS attacks conducted by
anti-spammers.  Certainly, this has been documented. (City of Battle Creek
V ORBZ.ORG, Av8 V Chris Neill, and others) In other cases, where Type 1
spammers have sent mail (eg AOL), the ISP has successfully used existing
laws to combat the problem.

Techno-Terrorism by anti-spammers doesn't bolster the anti-spam case. It
hurts it.

> You continue to exhibit an extraordinary willingness to argue your
> opinions against the facts.

Likewise.

> --
> Eric A. Hall                                        http://www.ehsco.com/
> Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/
>
>
>




From owner-ietf@ietf.org  Tue May 27 20:15:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10518
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 20:15:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ko8L-0003CF-GR
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 19:45:33 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Knrp-0002FL-GG
	for ietf@asgard.ietf.org; Tue, 27 May 2003 19:28:29 -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 TAA08818
	for <ietf@ietf.org>; Tue, 27 May 2003 19:28:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KnqH-00032u-00
	for ietf@ietf.org; Tue, 27 May 2003 19:26:53 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KnqG-00032q-00
	for ietf@ietf.org; Tue, 27 May 2003 19:26:52 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.9/8.12.9) id h4RNSOJs026657
	for ietf@ietf.org env-from <vjs>;
	Tue, 27 May 2003 17:28:24 -0600 (MDT)
Date: Tue, 27 May 2003 17:28:24 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200305272328.h4RNSOJs026657@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: spam
References: <3ED3E536.60BCD64E@earthlink.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Peter Deutsch <pdeutsch@earthlink.net>

> ...
> despite the fact that the vast majority of folks have *not* agreed with
> you, and some of us have specifically challenged (I wont be so
> presumptuous as to say "refuted") your claim.

That's nonsense.  There have been repeated statements to the effect
that doubling the size of a large mail system to deal with a doubling
of spam is very expensive.  That does not conflict with claims that
the cost to provide mail service for a single user is low.

> ...
> month to run; this does not mean you can build a commercial quality file
> server for under $200; And it most certainly does not mean that email
> costs anyone "only $1 or $2 per month".

If you think mail costs a lot more than $1 or $2 per month per user
to provide, what is your specific, informed, engineering estimate
without rhetorical flourishes or insults?

If mail costs a lot more than $1 or $2, say ten times as much or
$10 or $20/user/month, how can Hotmail and Yahoo provide free
mailboxes?  How can Earthlink, AOL, and others sell not ust mailboxes
but also 10 or 20 times more bandwidth for "web surfing" for $10
to $20 and claim to hope to turn a profit?


> If you continue to repeat this claim using such words as "roundly
> troll. In either case, you will eventually provoke taunts and jears from
> the audience, and we're trying very hard to raise the tone of this
> place. So please, cease and desist such activity at once.
>
> And even if you can't master engineering math, you really should
> consider learning some basic economics. If nothing else, it might be
> useful to you in balancing your checkbook.

That's good advice.


> ...
> As we say in French, "Ca c'est des horse patooties". Again, the cost of
> email is not merely the cost of the physical file storage, you need to
> consider the cost of your time processing it, the cost of time spent
> dealing with such things as denial of service attacks, the opportunity
> costs paid when folks hijack resources from their legitimate purpose and
> so on. There is also a "social cost" when, ...

Yes, the costs of spam are mostly in what it costs in human time.

However, the fact that the human costs of spam are large do not justify
your canards and other nonsense about the costs of bandwidth, CPU
cycles, disk space, and even human system administrator time to deal
with spam.

Again, if spam costs mail providers much more than $1 or $2/month/user,
then how can free providers offer mailboxes and how can you buy full
Internet service including the use of modem pools or whatever for
$10-$15/month?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Tue May 27 20:17:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10641
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 20:17:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ko8L-0003CL-Ok
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 19:45:33 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kns4-0002FR-KF
	for ietf@asgard.ietf.org; Tue, 27 May 2003 19:28:44 -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 TAA08822
	for <ietf@ietf.org>; Tue, 27 May 2003 19:28:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KnqW-000332-00
	for ietf@ietf.org; Tue, 27 May 2003 19:27:08 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KnqV-00032m-00
	for ietf@ietf.org; Tue, 27 May 2003 19:27:07 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 56475ABA6; Tue, 27 May 2003 16:34:09 -0700 (PDT)
To: Dean Anderson <dean@av8.com>
Cc: Valdis.Kletnieks@vt.edu, ietf@ietf.org
Subject: Re: spam
References: <Pine.LNX.4.44.0305271756050.8489-100000@commander.av8.net>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 27 May 2003 16:34:09 -0700
In-Reply-To: <Pine.LNX.4.44.0305271756050.8489-100000@commander.av8.net>
Message-ID: <kjllws6k26.fsf@romeo.rtfm.com>
Lines: 13
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Dean Anderson <dean@av8.com> writes:

>         > Get your FREE av8.com account now! <
> 
> So, it seems to be someone intentionally trying to infect me, or perhaps
> defame Av8.com, but failed.
I doubt it. I got similar message containing "get your free rtfm.com account now"
message.

-Ekr
-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Tue May 27 20:21:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10868
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 20:21:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KoMu-0004uI-Ff
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 20:00:36 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ko6i-00036Z-KQ
	for ietf@asgard.ietf.org; Tue, 27 May 2003 19:43:52 -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 TAA09259
	for <ietf@ietf.org>; Tue, 27 May 2003 19:43:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ko5A-0003Bj-00
	for ietf@ietf.org; Tue, 27 May 2003 19:42:16 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ko59-0003Bg-00
	for ietf@ietf.org; Tue, 27 May 2003 19:42:15 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h4RNhkk22393;
        Tue, 27 May 2003 19:43:48 -0400 (EDT)
Date: Tue, 27 May 2003 19:43:45 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: The utilitiy of IP is at stake here
Message-Id: <20030527194345.5d922e23.moore@cs.utk.edu>
In-Reply-To: <02b001c32497$0c11a350$2a134104@eagleswings>
References: <70275C55-8FD6-11D7-98C2-000393414368@yahoo.com>
	<02b001c32497$0c11a350$2a134104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> The open utility of IP is at stake here.

yup, probably so.  but why is the IETF list somehow more likely to
produce a solution than the ASRG list?

Keith



From owner-ietf@ietf.org  Tue May 27 20:22:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10997
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 20:22:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KodF-0006Vf-RK
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 20:17:29 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KoAD-0003D9-9u
	for ietf@asgard.ietf.org; Tue, 27 May 2003 19:47:29 -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 TAA09280
	for <ietf@ietf.org>; Tue, 27 May 2003 19:47:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ko8e-0003C4-00
	for ietf@ietf.org; Tue, 27 May 2003 19:45:52 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ko8e-0003C0-00
	for ietf@ietf.org; Tue, 27 May 2003 19:45:52 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id TAA26645;
	Tue, 27 May 2003 19:41:54 -0400
Date: Tue, 27 May 2003 19:42:47 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Peter Deutsch <pdeutsch@earthlink.net>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <3ED3E536.60BCD64E@earthlink.net>
Message-ID: <Pine.LNX.4.44.0305271926230.8489-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

You have to do more than say "you're wrong.".

If the corporation (like hotmail) brings in less than $1 per month from
each user, pays all of its employess, pays for all of its hardware,
software, and network connections, legal bills, and taxes from this
revenue, then quite clearly, there are no hidden costs, as you assert.

Clearly, spam can not cost more than they bring in, in revenue, else they
would go out of business.

There are sites that offer email services (unsubsidized), for $1 - $2 per
month. They also have no hidden costs, and no subsidies.

I also operate an email service, and I know that my servers, employees,
and everything else put together cost less than this for email service.

And in fact, I know of many email sites that are running $1000 linux
systems with $140 200 gig disks. I host some in colo. They are commercial
services.  At other colos (where I have facilities), I see ISPs running
Sparc 2's with single-ended scsi drives. It really doesn't take much to
make a dialup user happy. Guess thats why some dialup ISPs are offering
dialup and email for $5 per month.

And I already demonstrated that even if you buy a $45,000 sun
array, it _still_ comes out to practically nothing.

So, I suggest rather than make analogies about gas, you put together a
spreadsheet for a Hotmail-like service, and figure out how it is they can
survive, after all these years.

Crowds jeer. Governments listen.  Crowds jeer the unpopular. This has
nothing to do with whether they are right or wrong.  In fact, it is an
axiom that crowds are always wrong.  Anti-spammers are frequently nothing
but a lying, self-deceived mob of morons.  But spam is a real problem, and
it should be addressed, in spite of anti-spammers.

		--Dean


On Tue, 27 May 2003, Peter Deutsch wrote:

> g'day,
>
> Dean Anderson wrote:
> ...
> > In other words, cost plays a big part in the decision.  But as has been so
> > roundly demonstrated, the cost associated with email is practically
> > non-existant, and does not ever cost any user more than $1 or $2 per
> > month, which they pay for email services.
>
> Dammit, I'm trying to be good but you insist on repeating this canard,
> despite the fact that the vast majority of folks have *not* agreed with
> you, and some of us have specifically challenged (I wont be so
> presumptuous as to say "refuted") your claim.
>
> Gas in Southern California can currently be had for as little as $US1.61
> a gallon. It's possible to buy a 200 Gig hard drive from Fry's in
> California for about $US140. It's possible to buy advertizing supported,
> limited storage public email accounts for a few dollars a month (heck,
> you can even get "free" accounts at no cash outlay to you).  This does
> not mean that a car that gets 30 miles per gallon costs 5.3 cents a
> month to run; this does not mean you can build a commercial quality file
> server for under $200; And it most certainly does not mean that email
> costs anyone "only $1 or $2 per month".
>
> If you continue to repeat this claim using such words as "roundly
> demonstrated", I will conclude that you are either a poor engineer or a
> troll. In either case, you will eventually provoke taunts and jears from
> the audience, and we're trying very hard to raise the tone of this
> place. So please, cease and desist such activity at once.
>
> And even if you can't master engineering math, you really should
> consider learning some basic economics. If nothing else, it might be
> useful to you in balancing your checkbook.
>
>
> > This is substantially different from the case with faxes. And it does seem
> > to be a valid arguement that if technology does eliminate the burdens
> > imposed, then the junk fax law could be reversed.
> >
> > In the case of spam, there is no cost _shifting_ whatsoever, since by
> > definition, everyone pays their own way. Even spammers.  Unlike faxes, the
> > receipt of a spam does not increase the cost of the recipient's email.
> > Email is usually fixed cost, and flat rate.  Even when one pays by the
> > octet, the cost of a spam is in the millionths of a cent, which I think
> > is less than the cost to carry out the trash of one junk postal mail.
>
> As we say in French, "Ca c'est des horse patooties". Again, the cost of
> email is not merely the cost of the physical file storage, you need to
> consider the cost of your time processing it, the cost of time spent
> dealing with such things as denial of service attacks, the opportunity
> costs paid when folks hijack resources from their legitimate purpose and
> so on. There is also a "social cost" when, for example parents must
> forego having their children use email because of fears they will be
> exposed to the most egregious porn and violence. Ask for, or help
> develop, metrics for measuring such costs, but please do not deny their
> existance.
>
> The cost of physical delivery and storage are but a small part of the
> total cost of ownership here. By ignoring all but the upfront costs, it
> looks suspiciously like you're trying to lend legitimacy to odious
> practices by sleight-of-hand mathematics. Shame on you...
>
>
>
> 				- peterd
>
> --
> ---------------------------------------------------------------------
>     Peter Deutsch                       pdeutsch@gydig.com
>     Gydig Software
>
>                         "Bungle..."
>                "That's an 'i', you idiot..."
>                   "Oh, right. 'Bingle..."
>
>                             - Red versus Blue...
>
> ---------------------------------------------------------------------
>




From owner-ietf@ietf.org  Tue May 27 20:35:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11490
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 20:35:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KodG-0006X3-BZ
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 20:17:30 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KoAk-0003ef-70
	for ietf@asgard.ietf.org; Tue, 27 May 2003 19:48:02 -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 TAA09363
	for <ietf@ietf.org>; Tue, 27 May 2003 19:47:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ko9B-0003Ch-00
	for ietf@ietf.org; Tue, 27 May 2003 19:46:25 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ko9B-0003C7-00
	for ietf@ietf.org; Tue, 27 May 2003 19:46:25 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id TAA26686;
	Tue, 27 May 2003 19:43:40 -0400
Date: Tue, 27 May 2003 19:44:43 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: shogunx <shogunx@sleekfreak.ath.cx>
cc: Tony Hain <alh-ietf@tndh.net>, "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <Pine.LNX.4.44.0305262054330.23359-100000@sleekfreak.ath.cx>
Message-ID: <Pine.LNX.4.44.0305271944160.8489-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Assuming it pays for service, and isn't sending spam, I agree.

		--Dean

On Mon, 26 May 2003, shogunx wrote:

> On Tue, 27 May 2003, Tony Hain wrote:
>
> > S Woodside wrote, RE: spam
> > > How about the cost of legitimate emails that get filtered and never
> > > read. Not everyone scans the list to check for false positives.
>
> Below is an example for HAVING open relays, as a host on a "residential"
> IP can use an open relay for outgoing, and therefore communicate with
> aol/roadrunner/etc users.  a minor mod to the config of the MTA and there
> you go.
>
> scott
>
>
> >
> > In a major example of false positives, we already have examples of one
> > real cost of spam. AOL (as one example of many) has declared ranges of
> > IP addresses marked 'residential' as invalid for running a particular
> > application. In this case SMTP, but which app is next? There is a 'guilt
> > by association' presumption here by the operations community, which when
> > carried into other applications results in substantially limited value
> > in the core IP protocol.
> >
> > With this type of policy, the operations community is dictating which
> > applications can be run from specific ranges of IP addresses. This would
> > be comparable to the phone companies dictating that modems couldn't be
> > used from phone numbers that were allocated for voice use. Clearly the
> > operations community is fighting back with the limited tool set they
> > have, but they are setting a very dangerous precedent in the process.
> >
> > While the IETF can't dictate operational process, it must defend the
> > open and free use of its core protocol. Part of that defense means
> > finding architecturally viable alternatives to the evolving operational
> > hacks. One approach would be to undeniably associate an IP address with
> > a person, so existing legal recourse would be simplified. Privacy
> > advocates would take issue with that approach, so another would be to
> > encode the exact location of the source in the address, and use strict
> > RPF to enforce it. Location coupled with time would provide the legal
> > system with needed evidence, without compromising personal privacy.
> > There are likely other options, and issues to discuss, but we should not
> > just push this out as 'hard so it must be research'. The open utility of
> > IP is at stake here.
> >
> > Tony
> >
> >
> >
> >
> >
> >
>
> sleekfreak pirate broadcast
> world tour 2002-3
> live from the pirate hideout
> http://sleekfreak.ath.cx:81
>
>
>




From owner-ietf@ietf.org  Tue May 27 20:43:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11770
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 20:43:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KodL-0006j3-QS
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 20:17:35 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KoM2-0004nk-AK
	for ietf@asgard.ietf.org; Tue, 27 May 2003 19:59:42 -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 TAA09901
	for <ietf@ietf.org>; Tue, 27 May 2003 19:59:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KoKU-0003NV-00
	for ietf@ietf.org; Tue, 27 May 2003 19:58:06 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KoKT-0003NS-00
	for ietf@ietf.org; Tue, 27 May 2003 19:58:05 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S294CD> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 27 May 2003 16:59:38 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Anthony Atkielski'" <anthony@atkielski.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Tue, 27 May 2003 16:59:38 -0700
Message-ID: <000601c324ac$088080c0$56144104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <046f01c3249e$636d3540$0a00000a@atkielski.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id UAA11770

Anthony Atkielski wrote:
> AOL bounces all of my e-mail, but they are unable to explain 
> why they are doing this.  

I get:
[<02>] The reason of the delivery failure was:

550-The IP address you are using to connect to AOL is a dynamic
(residential) 550-IP address.  AOL will not accept future e-mail
transactions from your 550-IP address until your ISP removes your IP
from its list of dynamic
550-(residential) IP addresses.  For additional information, please
visit 550-http://postmaster.info.aol.com.
550 Goodbye

It is not viable for me to refuse mail from AOL since my wife's nephew
works there so most of her family uses AOL for email. 


> ...
> I agree.  And AOL is a major offender in many ways.  There's 
> the real Internet, and then there's the "AOL Internet"--not 
> unlike the Matrix, actually.

I was not AOL bashing, because they are not the only ones doing this. I
was also not claiming that ops was clueless for what they were doing
here. I was simply trying to point out the current state leaves them
little choice, and a very dangerous precedent is set as a result. As
Vixie has pointed out, the current state of affairs is the result of the
protocol design. We as the IETF need to step up and provide an alternate
design if we want the system to change. Some components of a new design
need to be a viable trust model, and irrefutable traceability. 

The IETF can't do social engineering, but can provide the framework for
others to do so. In that light, we simply need to get on with the task
at hand and create a replacement protocol.

Tony




From owner-ietf@ietf.org  Tue May 27 21:03:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12338
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 21:03:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KpAt-0000N8-GZ
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 20:52:15 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KodQ-0006mV-CE
	for ietf@asgard.ietf.org; Tue, 27 May 2003 20:17:40 -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 UAA10673
	for <ietf@ietf.org>; Tue, 27 May 2003 20:17:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kobr-0003cU-00
	for ietf@ietf.org; Tue, 27 May 2003 20:16:03 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kobr-0003bd-00
	for ietf@ietf.org; Tue, 27 May 2003 20:16:03 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id UAA04908;
	Tue, 27 May 2003 20:14:56 -0400
Date: Tue, 27 May 2003 20:15:59 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: John C Klensin <john-ietf@jck.com>
cc: shogunx <shogunx@sleekfreak.ath.cx>, Tony Hain <alh-ietf@tndh.net>,
        "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <17365440.1054062167@p3.JCK.COM>
Message-ID: <Pine.LNX.4.44.0305271959400.8489-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 27 May 2003, John C Klensin wrote:

> Scott,
>
> Good try, but no cigar.  This would be entirely reasonable if
> open relays were the only way to accomplish what you are after.

They are the only way to accomplish some things, like offering RFC 821
SMTP service to customers outside our your address space.

> But, if open relays were used this way, the spam flow through
> those open relays are such that "aol/roadrunner/etc" would start
> blocking the IP addresses of those relays.  Back to square one,
> with no gain.

Type 1 spammers don't abuse open relays. In my experience, Type 3 abusers
(anti-spammers in some cases), do this.  For example, about a year ago, I
got into an argument with two radical antispammers. Suddenly, 2400 hundred
different IP addresses started trying to abuse our relays. This continued
for about 10 days, and then abated.  Fortunately, our relay monitoring
software blocked this, but it still involved sorting through (no
exaggeration) millions of messages.  After that, (and still continuing
aperiodically), someone began trying to send viruses through a relay
address advertised by a European open relay blacklist, forging my address.

Coincidence? I don't think so.  Not given other more overt threats and
abuse by antispammers, such as Chris Neill and others.

> Instead, there are at least two options available for that host
> on a "residential" network (both in heavy use today):
>
> 	(i) The host uses a relay supplied by its ISP, one that
> 	is not blocked by "aol/roadrunner/etc".  This is more or
> 	less satisfactory depending on what additional
> 	restrictions the ISP imposes on that relay, but the
> 	typical restrictions (much as I think they are
> 	unreasonable) have very little impact on the typical
> 	residential user who corresponds actively with
> 	"aol/roadrunner/etc users".
>
> 	(ii) The host uses a relay with which its owners have
> 	established some sort of business relationship and which
> 	relay is in a position to authenticate the host (via SSL
> 	certificates, SMTP AUTH, or some combination of a tunnel
> 	and authentication).

(ii) isn't an option.

Here's a short answer:

1) This is not a standard. It is optional, even if eventually
standardized.
2) There are only about 15 mail clients that support it.
3) It doesn't scale for non-dialup ISPs
4) Time Warner called it "unsuitable for business".
5) It doesn't reduce spam. Spammers are not outsiders. It fails to
violate Shannon's theorem.
6) about a thousand other mail clients don't support it, and have no plans
to.


> I was a big fan of open relays a decade ago, but am no longer
> convinced that they are the required solution to any problem we
> need to solve.

There were no "open relays" a decade ago. There were "anonymous relays"
back then. This "anonymous relay" problem had nothing to do with SMTP, but
was a problem with reverse DNS, and lack of a numeric IP address in the
Received: header. This problem was been fixed around 1993.. It is not
possible to send anonymous email through an open relay. (you still hear
this from radical antispammers, though).

> And, no, I don't believe that either of the measures above will
> significantly reduce the volume of spam.

Then why bother at all?

		--Dean





From owner-ietf@ietf.org  Tue May 27 21:03:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12337
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 21:03:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KpAu-0000P8-6D
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 20:52:16 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KofX-0006ns-CW
	for ietf@asgard.ietf.org; Tue, 27 May 2003 20:19:51 -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 UAA10786
	for <ietf@ietf.org>; Tue, 27 May 2003 20:19:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kodz-0003eX-00
	for ietf@ietf.org; Tue, 27 May 2003 20:18:15 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kody-0003eU-00
	for ietf@ietf.org; Tue, 27 May 2003 20:18:14 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 208023; Tue, 27 May 2003 19:19:17 -0500
Message-ID: <3ED400A2.706@ehsco.com>
Date: Tue, 27 May 2003 19:19:46 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: John Stracke <jstracke@centive.com>, ietf@ietf.org
Subject: Re: spam
References: <Pine.LNX.4.44.0305271831130.8489-100000@commander.av8.net>
In-Reply-To: <Pine.LNX.4.44.0305271831130.8489-100000@commander.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/27/2003 6:24 PM Dean Anderson wrote:

<waffling snipped>

>>The cost of a fax to a typical organization with bulk purchasing power is
>>probably on the order of $.02 per page, including the paper and ink used.
>>Using thermal paper from a retailer averages out to about $.06 per page.
>>It is very easy to demonstrate per-message costs in that same ballpark for
>>spam, especially once we get measured-rate circuits involved. That you do
>>not suffer from these burdens does not mean that nobody should be
>>protected from them.
> 
> No, this isn't true. If you pay $1 per month for email

You have no idea what I pay. As far as you know, I pay $.05 per minute for
ISDN and cellular-data hookups to pull my mail down from my colo server.
Everytime I pull a piece of spam I pay the nickel, which is in the same
ballpark as fax spam costs. Your response to this point was, and I quote
here: "Don't get email on measured rate services, then." which is a limp
way of saying that spam costs people with these links too much money for
them to use email. You have admitted that spam has a cost, and are now
trying to waffle out of that position by claiming that there is no cost.

>>As has been stated, the junk fax laws are not limited to cost protection,
>>and also address the usability arguments.
>  
> No, the Appeals court didn't find that at all.

I thought you read the opinion:

| We conclude that the Government has demonstrated a substantial
| interest in restricting unsolicited fax advertisements in order to
| prevent the cost shifting and interference such unwanted advertising
| places on the recipient.  ^^^^^^^^^^^^^^^^

In this particular case, the court cited previous evidence on the issue of
usefulness, in that junk faxes prevented the machine from being used for
its intended purposes. Spam also prevents email from being used for its
intended purposes when (1) their hotmail/yahoo mailbox fills up, (2) a
false-positive in a filter or a blacklist kills a message, or (3) somebody
deletes all of their email because they can't scan it all. All of these
are examples of interference. I don't really care about how you waffle
around this fact.

In both of these examples, the verbiage present in the TCPA is equally
applicable to the problem of spam. Your continued waffling on minor,
irrelevant, non-contributory details and detours does not change that.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Tue May 27 21:08:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12661
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 21:08:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KpBI-0000Ra-8f
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 20:52:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KohW-0007Kc-Hi
	for ietf@asgard.ietf.org; Tue, 27 May 2003 20:21:54 -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 UAA10904
	for <ietf@ietf.org>; Tue, 27 May 2003 20:21:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kofy-0003gm-00
	for ietf@ietf.org; Tue, 27 May 2003 20:20:18 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kofw-0003gX-00
	for ietf@ietf.org; Tue, 27 May 2003 20:20:16 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4S0Lojh016735
	for <ietf@ietf.org>; Wed, 28 May 2003 02:21:50 +0200 (CEST)
Message-ID: <04c201c324af$22303fd0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <000601c324ac$088080c0$56144104@eagleswings>
Subject: Re: The utilitiy of IP is at stake here
Date: Wed, 28 May 2003 02:21:50 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony writes:

> I get:
> [<02>] The reason of the delivery failure was:
>
> 550-The IP address you are using to connect to AOL is a dynamic
> (residential) 550-IP address.  AOL will not accept future e-mail
> transactions from your 550-IP address until your ISP removes your IP
> from its list of dynamic
> 550-(residential) IP addresses.  For additional information, please
> visit 550-http://postmaster.info.aol.com.

Did you call AOL and ask them to remove you from their list of dynamic IP
addresses?  If so, what did they say?

I'm not on their list of dynamic addresses.  I'm not on their open-relay or
proxy lists, either.  The lady who answered the phone claimed that I need to
have a reverse lookup that matches my announced domain when I connect (at
least, as far as she seemed to understand what I was talking about).  But
when I reconfigure sendmail to send a HELO with the exact rDNS name for my
IP address, AOL still refuses the e-mail.  I think it is looking at MX
records or something, but the lady at the network center didn't know what an
MX record was, so I knew I was wasting my time with her, and she couldn't
help further or refer me to anyone else.  This prevented me from making any
progress.

Some have suggested that I smarthost through my upstream ISP's mail server.
But they bounce my e-mail, too ("relaying denied").  It seems that their
configuration believes my IP address to be a "foreign" address, even though
they assigned it to me.  They never updated their IP address database when
they added addresses.  When I e-mailed them about it, the person I talked to
didn't even understand the difference between a login name and password and
an IP address, and simply assured me over and over that my login and
password were valid.  So that was a waste of time as well.

> It is not viable for me to refuse mail from AOL
> since my wife's nephew works there so most of her
> family uses AOL for email.

How does she e-mail back to them, in that case?

They may be able to get Internet access from other ISPs for less money.

As I've said, I'm bouncing all incoming AOL mail now, and, ironically, it
has eliminated a lot of spam, so a great deal of spam comes from AOL.COM, or
appears to, at least.

> I was not AOL bashing, because they are not the
> only ones doing this.

CS.COM and NETSCAPE.NET are doing it, but they are part of AOL.  I suppose
others are doing it.

FREEBSD.ORG bounces my e-mail because they don't like what I have to say,
but their e-mail administrator, in his infinite wisdom, apparently didn't
realize that if he bounces all my e-mail, I cannot unsubscribe from their
lists.  They are spamming my server with hundreds of messages a day.  I may
have to complain to their upstream ISP, since sending unsolicited e-mail and
not allowing me to put a stop to it is spamming.

> As Vixie has pointed out, the current state of
> affairs is the result of the protocol design. We
> as the IETF need to step up and provide an alternate
> design if we want the system to change.

I agree in principle, but I can't think of any changes in the protocol
offhand that would not require changes in every machine in the world.  That
isn't practical, so the only practical change is a backward-compatible
change that excludes only spam.  The problem is that spam doesn't look any
different from legitimate e-mail to a machine.

> Some components of a new design need to be a viable
> trust model, and irrefutable traceability.

Neither of these meet the criterion of "no changes to all the machines in
the world."  In order for them to work, every machine has to change,
everywhere.  That isn't going to happen; and if it doesn't happen, the
scheme won't work, and/or tons of legitimate e-mail will be lost.





From owner-ietf@ietf.org  Tue May 27 21:10:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12776
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 21:10:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KpBJ-0000Tj-25
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 20:52:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Koj8-0007aH-EG
	for ietf@asgard.ietf.org; Tue, 27 May 2003 20:23:34 -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 UAA11047
	for <ietf@ietf.org>; Tue, 27 May 2003 20:23:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KohZ-0003jg-00
	for ietf@ietf.org; Tue, 27 May 2003 20:21:58 -0400
Received: from mailhost.iprg.nokia.com ([205.226.5.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KohY-0003in-00
	for ietf@ietf.org; Tue, 27 May 2003 20:21:57 -0400
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id RAA19271;
	Tue, 27 May 2003 17:23:00 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h4S0N0P11461;
	Tue, 27 May 2003 17:23:00 -0700
X-mProtect: <200305280023> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.9.150, claiming to be "spruce.iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdcW93q0; Tue, 27 May 2003 17:22:57 PDT
Message-Id: <4.3.2.7.2.20030527171029.00b43e78@mailhost.iprg.nokia.com>
X-Sender: hinden@mailhost.iprg.nokia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 27 May 2003 17:21:55 -0700
To: John C Klensin <john-ietf@jck.com>
From: Bob Hinden <hinden@iprg.nokia.com>
Subject: RE: spam
Cc: "ietf@ietf.org" <ietf@ietf.org>
In-Reply-To: <18846359.1054063648@p3.JCK.COM>
References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAgz55/h9tW0GXHZYRsfdCb8KAAAAQAAAAipggkAUXw0KYX7iEX/niGQEAAAAA@xs4all.nl>
 <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAgz55/ h9tW0GXHZYRsfdCb8KAAAAQAAAAipggkAUXw0KYX7iEX/niGQEAAAAA@xs4all.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

John,

>The evidence is that, if it became clear that a serious effort was 
>developing to deploy such filters, the spammers would start sending 
>conforming messages more rapidly than the filters could actually be spun 
>up.  Would this inconvenience them, or the authors of spam tools?  Yes, 
>but almost certainly not very much or for very long.  It would, 
>perversely, actually help the businesses of the spam tool builders: "get 
>your new, updated, standards-conforming bulk mailer here and get past the 
>new 2821-conformance-testing filters".

I agree and am coming to the conclusion that there won't be any technical 
solution to SPAM.  The SPAMers will adapt to all technical hurdles that are 
put in place.  The solution needs to be at the policy and/or legal level.

I also agree with Tony Hain that the current remedies may be doing more 
long term harm to the Internet than the problem.

Bob




From owner-ietf@ietf.org  Tue May 27 21:18:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13040
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 21:18:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KpBJ-0000WX-U2
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 20:52:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kood-0007jF-Ki
	for ietf@asgard.ietf.org; Tue, 27 May 2003 20:29:15 -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 UAA11246
	for <ietf@ietf.org>; Tue, 27 May 2003 20:29:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kon5-0003nv-00
	for ietf@ietf.org; Tue, 27 May 2003 20:27:39 -0400
Received: from 75.5.33.65.cfl.rr.com ([65.33.5.75] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kon4-0003ns-00
	for ietf@ietf.org; Tue, 27 May 2003 20:27:38 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19KUna-0006Ch-00; Mon, 26 May 2003 23:06:50 -0400
Date: Mon, 26 May 2003 23:06:49 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: John C Klensin <john-ietf@jck.com>
cc: Tony Hain <alh-ietf@tndh.net>, "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <17365440.1054062167@p3.JCK.COM>
Message-ID: <Pine.LNX.4.44.0305262256060.23359-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 27 May 2003, John C Klensin wrote:

> Scott,
>
> Good try, but no cigar.  This would be entirely reasonable if
> open relays were the only way to accomplish what you are after.
> But, if open relays were used this way, the spam flow through
> those open relays are such that "aol/roadrunner/etc" would start
> blocking the IP addresses of those relays.  Back to square one,
> with no gain.

>
> Instead, there are at least two options available for that host
> on a "residential" network (both in heavy use today):
>
> 	(i) The host uses a relay supplied by its ISP, one that
> 	is not blocked by "aol/roadrunner/etc".  This is more or
> 	less satisfactory depending on what additional
> 	restrictions the ISP imposes on that relay, but the
> 	typical restrictions (much as I think they are
> 	unreasonable) have very little impact on the typical
> 	residential user who corresponds actively with
> 	"aol/roadrunner/etc users".

right, except my "residential" ISP bans the use of any and all servers on
its network.  their routers are configured to drop all http requests to my
machine on the floor, by default.  so what do i do?  in true MANET style i
moved the web server to port 81.  my traffic went down significantly for
almost a month until i was able to get the word out that apache was
running on 81.  this is probably in violation of RFC, but, well, the data
must get through.


>
> 	(ii) The host uses a relay with which its owners have
> 	established some sort of business relationship and which
> 	relay is in a position to authenticate the host (via SSL
> 	certificates, SMTP AUTH, or some combination of a tunnel
> 	and authentication).
>

well i can just as easily ask one of the folks i have done consulting for
to relay for me (or just configure it that way), then tweak my local exim
config, and thats that.  but that dosen't solve the problem on a large
scale, just locally.

> I was a big fan of open relays a decade ago, but am no longer
> convinced that they are the required solution to any problem we
> need to solve.
>

i had one until about a year ago, when i was watching the packet sniffer
and saw spam being pushed through.  then i closed the relay.

> And, no, I don't believe that either of the measures above will
> significantly reduce the volume of spam.  After all, the volume
> of spam is much higher today than it was when open relays were
> the norm, worldwide.  One can reasonably speculate on whether
> the spam volume would be even higher if open relays were more
> readily accessible, but, as many others have pointed out in
> other ways, that really isn't the point.
>

personally, i get no spam.  i just don't.  i have no filters.  i somply
get none.  don't ask me why.

scott

>       john
>
>
> --On Monday, 26 May, 2003 20:56 -0400 shogunx
> <shogunx@sleekfreak.ath.cx> wrote:
>
> > On Tue, 27 May 2003, Tony Hain wrote:
> >
> >> S Woodside wrote, RE: spam
> >> > How about the cost of legitimate emails that get filtered
> >> > and never read. Not everyone scans the list to check for
> >> > false positives.
> >
> > Below is an example for HAVING open relays, as a host on a
> > "residential" IP can use an open relay for outgoing, and
> > therefore communicate with aol/roadrunner/etc users.  a minor
> > mod to the config of the MTA and there you go.
> >
> > scott
> >
> >
> >>
> >> In a major example of false positives, we already have
> >> examples of one real cost of spam. AOL (as one example of
> >> many) has declared ranges of IP addresses marked
> >> 'residential' as invalid for running a particular
> >> application. In this case SMTP, but which app is next? There
> >> is a 'guilt by association' presumption here by the
> >> operations community, which when
> >...
>
>
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81




From owner-ietf@ietf.org  Tue May 27 21:33:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13361
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 21:33:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KpGg-0000wQ-Fm
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 20:58:14 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Koys-0008ET-NZ
	for ietf@asgard.ietf.org; Tue, 27 May 2003 20:39:50 -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 UAA11719
	for <ietf@ietf.org>; Tue, 27 May 2003 20:39:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KoxK-0003v4-00
	for ietf@ietf.org; Tue, 27 May 2003 20:38:14 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KoxH-0003v1-00
	for ietf@ietf.org; Tue, 27 May 2003 20:38:11 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.9/8.12.9) id h4S0djLF009506
	for ietf@ietf.org env-from <vjs>;
	Tue, 27 May 2003 18:39:45 -0600 (MDT)
Date: Tue, 27 May 2003 18:39:45 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200305280039.h4S0djLF009506@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: spam
References: <Pine.LNX.4.44.0305271756050.8489-100000@commander.av8.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Dean Anderson <dean@av8.com>

> ...
> No one has demonstrated any cost to spam, other than annoyance and
> infrastructure costs which are passed on to users[1], and it seems there
> is very little to add.

That's a ridiculous overstatement.  Spam may be too cheap to meter
for an individual user, but if you have 30,000,000 users or only
30,000, you'll find that the total costs are substantial, particularly
when you need to double the size of your systems to deal with a doubling
of spam.

> ...
> Vixie and other radicals also continues to ignore Shannon's theorems. ...

While it's true that proving the non-existence of covert channels
is hard, you've not related that theorem to anything related to spam.
Even if covert channels or the relation among power, noise, bandwidth,
and information have something to do with spam, you've not shown
any connection to dealing with the spam problem.

A good rule of thumb is that only people who don't know much about
major theorems like Shannon's and Godel's quote them as proofs in
discussions like this.  I think you should have chosen some other
beautiful bit of archana such one of the fixed point theorems or
Fred J. Cohen's Forcing and Generic instead of something that more
than a few people around here know about such as covert channels.



> ...
> [2] I would suspect that this could be a "normal" virus infection, but the
> following text in the virus message wasn't in the message I sent:
>
>         > Get your FREE av8.com account now! <
>
> So, it seems to be someone intentionally trying to infect me, or perhaps
> defame Av8.com, but failed.

My but aren't you Very Special!  Some of the rest of us who received
that stuff got it without any recent messages to this list.  Our
copies no doubt came thanks to familiar mechanisms that don't depend
on our Specialness.


If this noise must continue, could it please move to somewhere that
it is vaguely on-topic, such as the ASRG mailing list?  I hate to say
that, because the flood of clue-challenged, chest-thumping noise in
the ASRG mailing list has tailed off in recent weeks.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Tue May 27 21:33:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13357
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 21:33:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KpGg-0000wK-9X
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 20:58:14 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Koyo-0008ER-4u
	for ietf@asgard.ietf.org; Tue, 27 May 2003 20:39:46 -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 UAA11715
	for <ietf@ietf.org>; Tue, 27 May 2003 20:39:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KoxF-0003uy-00
	for ietf@ietf.org; Tue, 27 May 2003 20:38:09 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KoxF-0003up-00
	for ietf@ietf.org; Tue, 27 May 2003 20:38:09 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S294DB> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 27 May 2003 17:39:41 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Tue, 27 May 2003 17:39:42 -0700
Message-ID: <000701c324b1$a122a740$56144104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <20030527194345.5d922e23.moore@cs.utk.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA13357

Keith Moore wrote:
> > The open utility of IP is at stake here.
> 
> yup, probably so.  but why is the IETF list somehow more 
> likely to produce a solution than the ASRG list?

For starters, this should not be a approached as research problem.
Besides that, focusing on anti-spam is targeting the symptom rather than
the underlying protocol that is being abused. We need a real engineering
effort to define an alternative to SMTP that has a reasonably deployable
trust model, and traceability. There may be other requirements, but just
those two would be a good start because the existing legal
infrastructure could start on the social engineering part of the problem
space.

Tony






From owner-ietf@ietf.org  Tue May 27 21:40:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13761
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 21:40:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KpHT-00013P-Ep
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 20:59:03 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KpA2-0000Ll-On
	for ietf@asgard.ietf.org; Tue, 27 May 2003 20:51:22 -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 UAA12144
	for <ietf@ietf.org>; Tue, 27 May 2003 20:51:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kp8U-00042N-00
	for ietf@ietf.org; Tue, 27 May 2003 20:49:46 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kp8T-00042K-00
	for ietf@ietf.org; Tue, 27 May 2003 20:49:45 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h4S0pJtU005873;
	Tue, 27 May 2003 20:51:19 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h4S0pJoc005872;
	Tue, 27 May 2003 20:51:19 -0400
Date: Tue, 27 May 2003 20:51:19 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200305280051.h4S0pJoc005872@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: spam
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: Dean Anderson <dean@av8.com>

    > Shannon's theorem still stands.
    > ...
    > In terms of spam, this means that it is impossible to construct a
    > protocol that cannot be abused
    > ...
    > No protocol can ever be constructed that is spam-free.
    > ...
    > All abusers are the customer of some ISP, somewhere. There are no
    > outsiders. The spammers are in fact authorized users of some ISP that
    > are authorized to send email. They remain authorized to send email
    > until they lose service with that ISP.

Which is precisely why I say that the solution to spam is to charge for
email. It avoids the whole question of defining what is and is not spam.

More specifically, change the email protocol so that when email arrives from
an entity which is not on the "email from these entities is free" list, the
email is rejected unless is accompanied by a payment for $X (where X is set
by a knob on the machine).

(And yes, I know there are issues with relays, etc.)

If all spam arrives with a $1 bill, I'd be happy to let spammers send me as
much spam as they want.

	Noel



From owner-ietf@ietf.org  Tue May 27 21:40:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13759
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 21:40:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KpHT-00013V-No
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 20:59:03 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KpAT-0000Lo-B7
	for ietf@asgard.ietf.org; Tue, 27 May 2003 20:51:49 -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 UAA12151
	for <ietf@ietf.org>; Tue, 27 May 2003 20:51:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kp8v-00042W-00
	for ietf@ietf.org; Tue, 27 May 2003 20:50:13 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kp8u-00042T-00
	for ietf@ietf.org; Tue, 27 May 2003 20:50:12 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 208027; Tue, 27 May 2003 19:51:15 -0500
Message-ID: <3ED40820.5020900@ehsco.com>
Date: Tue, 27 May 2003 19:51:44 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: alh-ietf@tndh.net
CC: "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
References: <000601c324ac$088080c0$56144104@eagleswings>
In-Reply-To: <000601c324ac$088080c0$56144104@eagleswings>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/27/2003 6:59 PM Tony Hain wrote:

> protocol design. We as the IETF need to step up and provide an alternate
> design if we want the system to change. Some components of a new design
> need to be a viable trust model, and irrefutable traceability. 

Yes.

> The IETF can't do social engineering, but can provide the framework for
> others to do so. In that light, we simply need to get on with the task
> at hand and create a replacement protocol.

Actually, and this was point of my early posts, the IETF or somebody who
is authorized to represent this unruly mob needs to interact with the
legislative bodies to tell them what we *CAN* do. The law has to be built
around the protocol work just as much as the protocol has to support the
machinations of the law.

As I also tried to demonstrate in the earlier messages, the coordination
can be very minor to start with, being little more than "250 means don't
send me illegal crap while 2XX means this other thing..."

Somebody has to perform this coordination. They don't have to embrace
policy or anything else.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Tue May 27 22:10:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14322
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 22:10:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kpxn-0005CE-L4
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 21:42:47 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KpQC-0001tr-NH
	for ietf@asgard.ietf.org; Tue, 27 May 2003 21:08:04 -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 VAA12650
	for <ietf@ietf.org>; Tue, 27 May 2003 21:08:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KpOe-0004Bn-00
	for ietf@ietf.org; Tue, 27 May 2003 21:06:28 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KpOd-0004Bb-00
	for ietf@ietf.org; Tue, 27 May 2003 21:06:27 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id VAA17338;
	Tue, 27 May 2003 21:03:00 -0400
Date: Tue, 27 May 2003 21:04:03 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: "Eric A. Hall" <ehall@ehsco.com>
cc: John Stracke <jstracke@centive.com>, <ietf@ietf.org>
Subject: Re: spam
In-Reply-To: <3ED400A2.706@ehsco.com>
Message-ID: <Pine.LNX.4.44.0305272043280.8489-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 27 May 2003, Eric A. Hall wrote:

>
> on 5/27/2003 6:24 PM Dean Anderson wrote:
>
> <waffling snipped>
>
> >>The cost of a fax to a typical organization with bulk purchasing power is
> >>probably on the order of $.02 per page, including the paper and ink used.
> >>Using thermal paper from a retailer averages out to about $.06 per page.
> >>It is very easy to demonstrate per-message costs in that same ballpark for
> >>spam, especially once we get measured-rate circuits involved. That you do
> >>not suffer from these burdens does not mean that nobody should be
> >>protected from them.
> >
> > No, this isn't true. If you pay $1 per month for email
>
> You have no idea what I pay. As far as you know, I pay $.05 per minute for
> ISDN and cellular-data hookups to pull my mail down from my colo server.

So what? That is no reason to ban spam.

> Everytime I pull a piece of spam I pay the nickel, which is in the same
> ballpark as fax spam costs.

To who?  Do you have receipts for this?  Anyway, I don't, and no one else
does, either. So it doesn't justify anything to Congress.

If you mean it costs you a nickle to press delete, then the cost of
hauling out the trash would be an issue for Junk Mail, and Junk Faxes, and
the cost of listening to a telemarketer would be a factor there, too. This
isn't an issue. No one said your life would be free from trash.
Furthermore, there are do-not-send lists. If anti-spammers abuse those
lists, that isn't a justification to ban spam.

> Your response to this point was, and I quote here: "Don't get email on
> measured rate services, then." which is a limp way of saying that spam
> costs people with these links too much money for them to use email. You
> have admitted that spam has a cost, and are now trying to waffle out of
> that position by claiming that there is no cost.

No, I'm saying that spam has insignificantly small cost, and that trying
to inflate the cost somehow isn't a valid reason for banning spam. YOu
could have spam gold-plated, and transported around the world by police
motorcade and armored car, and it would cost a fortune, but it still would
make the case for banning spam.

> >>As has been stated, the junk fax laws are not limited to cost protection,
> >>and also address the usability arguments.
> >
> > No, the Appeals court didn't find that at all.
>
> I thought you read the opinion:
>
> | We conclude that the Government has demonstrated a substantial
> | interest in restricting unsolicited fax advertisements in order to
> | prevent the cost shifting and interference such unwanted advertising
> | places on the recipient.  ^^^^^^^^^^^^^^^^

I read that. By interference, the court is refering to the fact that the
recipient runs out of paper, and can't receive other faxes. This doesn't
happen with spam.

And if you read the text of the decision, and not just the conclusion,
you'll see that the Court spends most of its time with the cost issue.

> In this particular case, the court cited previous evidence on the issue of
> usefulness, in that junk faxes prevented the machine from being used for
> its intended purposes.

> Spam also prevents email from being used for its intended purposes when
> (1) their hotmail/yahoo mailbox fills up, (2) a false-positive in a
> filter or a blacklist kills a message, or (3) somebody deletes all of
> their email because they can't scan it all. All of these are examples of
> interference. I don't really care about how you waffle around this fact.

Point by point:


1) Disks are so cheap that mailboxes shouldn't ever fill up. Perhaps you
should buy services from a better provider. Maybe that provider has been
growing too fast, and is using "spam caused our disks to fill up" as an
excuse for "we can't install servers fast enough to keep up with demand".
I don't sign up users faster than I can deploy servers for them. My signup
software will deny signups when resources are low. It will collect
callbacks, and send email.

2) Our spam filters don't delete spam, they just refile it. If you think
something was misfiled, you can get it back (because disks are so cheap)

3) Thats just stupid and unreasonable behavior. Stupidity and willfull
recklessness aren't either common or justifications for banning spam.


> In both of these examples, the verbiage present in the TCPA is equally
> applicable to the problem of spam. Your continued waffling on minor,
> irrelevant, non-contributory details and detours does not change that.

No, it isn't, despite your continued assertions.  You have failed to
present a case that spam costs any money, or interferes with any reaonable
person's email.





From owner-ietf@ietf.org  Tue May 27 22:18:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14617
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 22:18:34 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kpxq-0005JF-CJ
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 21:42:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kpl6-0003A6-5K
	for ietf@asgard.ietf.org; Tue, 27 May 2003 21:29:40 -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 VAA13295
	for <ietf@ietf.org>; Tue, 27 May 2003 21:29:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KpjX-0004O0-00
	for ietf@ietf.org; Tue, 27 May 2003 21:28:03 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KpjW-0004Nx-00
	for ietf@ietf.org; Tue, 27 May 2003 21:28:02 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19Kpkq-000CDd-00; Tue, 27 May 2003 20:29:24 -0500
Date: Tue, 27 May 2003 21:29:24 -0400
From: John C Klensin <john-ietf@jck.com>
To: Dean Anderson <dean@av8.com>
cc: shogunx <shogunx@sleekfreak.ath.cx>, Tony Hain <alh-ietf@tndh.net>,
        "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
Message-ID: <26161928.1054070964@p3.JCK.COM>
In-Reply-To: <Pine.LNX.4.44.0305271959400.8489-100000@commander.av8.net>
References:  <Pine.LNX.4.44.0305271959400.8489-100000@commander.av
 8.net>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dean,

Since this is a response to a note I wrote, I'm going to try to 
respond to it.  Then I'm going to go back to deleting your mail 
without reading it, because it doesn't appear to me as if you 
really intend to participate in this discussion, rather than 
reciting your set of canards over and over again.   The opinion 
of others may differ, of course but, as far as I am concerned, 
you are succeeding in losing all credibility.

--On Tuesday, 27 May, 2003 20:15 -0400 Dean Anderson 
<dean@av8.com> wrote:

>> Good try, but no cigar.  This would be entirely reasonable if
>> open relays were the only way to accomplish what you are
>> after.
>
> They are the only way to accomplish some things, like offering
> RFC 821 SMTP service to customers outside our your address
> space.

Time to start checking either your facts or your explanations. 
People offer SMTP service to others (customers or otherwise) 
"outside their address space" all the time.  Even I do it, as a 
courtesy to colleagues who have gotten stuck behind some of 
those ISP "use only our SMTP server, no outgoing SMTP 
connections get past our boundaries" arrangements (I won't 
dignify them by calling them "services") I detest.  Few of us do 
it with open relays -- we do it with the two options I 
mentioned, with selective address filtering (a poor option, IMO, 
but it is often adequate), with "send after POP" (ditto), and 
other techniques that involve at least rudimentary 
authentication and authorization.


>> But, if open relays were used this way, the spam flow through
>> those open relays are such that "aol/roadrunner/etc" would
>> start blocking the IP addresses of those relays.  Back to
>> square one, with no gain.

> Type 1 spammers don't abuse open relays.

That is a fairly strong universal assertion.  I trust that you 
have carefully interviewed and polled all of them, and that all 
of them told you the truth.  I've had evidence to the contrary 
from time to time but, unless Paul Vixie's superhuman, and, IMO, 
helpful, efforts to collect statistics and categorize the stuff, 
I just get rid of it as quickly and efficiently as possible (an 
expensive process by any measure, unless you believe my time as 
a value of zero, as you apparently do).

> In my experience,
> Type 3 abusers (anti-spammers in some cases), do this.  For
> example, about a year ago, I got into an argument with two
> radical antispammers. Suddenly, 2400 hundred different IP
> addresses started trying to abuse our relays. This continued
> for about 10 days, and then abated.  Fortunately, our relay
> monitoring software blocked this, but it still involved
> sorting through (no exaggeration) millions of messages.  After
> that, (and still continuing aperiodically), someone began
> trying to send viruses through a relay address advertised by a
> European open relay blacklist, forging my address.

> Coincidence? I don't think so.  Not given other more overt
> threats and abuse by antispammers, such as Chris Neill and
> others.

Even if you have been unreasonably abused, it doesn't make your 
point valid.   Wrt regard to the legitimacy of spam, or spammer 
behavior, the technical term for your discussion above is "red 
herring".

>> Instead, there are at least two options available for that
>> host on a "residential" network (both in heavy use today):
>>
>> 	(i) The host uses a relay supplied by its ISP, one that
>> 	is not blocked by "aol/roadrunner/etc".  This is more or
>> 	less satisfactory depending on what additional
>> 	restrictions the ISP imposes on that relay, but the
>> 	typical restrictions (much as I think they are
>> 	unreasonable) have very little impact on the typical
>> 	residential user who corresponds actively with
>> 	"aol/roadrunner/etc users".
>>
>> 	(ii) The host uses a relay with which its owners have
>> 	established some sort of business relationship and which
>> 	relay is in a position to authenticate the host (via SSL
>> 	certificates, SMTP AUTH, or some combination of a tunnel
>> 	and authentication).
>
> (ii) isn't an option.
>
> Here's a short answer:
>
> 1) This is not a standard. It is optional, even if eventually
> standardized.

Gee.  I am co-author of some odd RFC whose status seems to be 
"proposed standard".  Something like RFC 2195.  There is also 
RFC 2554, also a proposed standard, which is, I think, where 
SSL/TLS tunnels are covered (this isn't worth the energy for my 
to go back and check).  And virtually all Internet standards, at 
all maturity levels, are "optional" in the sense that no one 
requires anyone to implement them.   If they are useful and 
needed, they get implemented.  If not, they don't.  You are, 
IMO, just wasting time here -- yours and, more important, 
everyone else's.

> 2) There are only about 15 mail clients that support it.

And I'd guess the first half-dozen of those represent the _vast_ 
majority of non-AOL email senders on the Internet.  And users 
who _need_ these capabilities tend to find clients that support 
them.  So your point was?

> 3) It doesn't scale for non-dialup ISPs

And you base this on...?  Technologically, several of those 
techniques (note that I mentioned a series of techniques, so I'm 
not quite sure what "it" refers to) is easier to support with 
hardwired, semi-permanent, connections than it is with dialup.

> 4) Time Warner called it "unsuitable for business".

And Ken Olsen couldn't imagine anyone really wanting a 
"personal", desktop, computer.   Your point is?

> 5) It doesn't reduce spam. Spammers are not outsiders. It
> fails to violate Shannon's theorem.

You keep repeating your dubious reference to Shannon's 
observation about disproof of a covert channel.  Nice try, but 
it is largely irrelevant.   That theorem is the information 
theory version of the observation in traditional logic that one 
can't prove a universal negative and a relative of Goedel's work 
on the limits of set theory and mathematical logic systems.  All 
three are nicely proveable, but our day-to-day world is more 
empirical and statistical: no one I know of is asking for a 
proof that there are no covert channels out there or that all 
spam can be stopped.  Most of us would be quite happy to just 
not see any of it in a given month.  And you are wasting time -- 
yours and everyone else's.  I suppose that, since you value that 
time at zero (based on your claims about the cost of spam) that 
is ok from your perspective.  But you are, I suspect, being 
rapidly added to a lot of filters.

> 6) about a thousand other mail clients don't support it, and
> have no plans to.

So?  Either their users don't need it, or they are headed for 
failure in whatever marketplace in which they exist.  That is 
how both standards and products play themselves out.

>> I was a big fan of open relays a decade ago, but am no longer
>> convinced that they are the required solution to any problem
>> we need to solve.

> There were no "open relays" a decade ago. There were
> "anonymous relays" back then. This "anonymous relay" problem
> had nothing to do with SMTP, but was a problem with reverse
> DNS, and lack of a numeric IP address in the Received: header.

Thank you for the lecture on SMTP and its predecessors, whose 
operation and history you obviously know more about than I do.

Traditionally --although obviously not in the circles in which 
you travel-- the term "open relay" has been used to describe an 
SMTP server that would accept traffic for relaying from any 
source, without attempting to either authenticate that source or 
apply authorization rules to it.  That has a great deal to do 
with the way SMTP works in relay mode, and nothing at all to do 
with either reverse DNS or issues about what information is, or 
is not, copied into Received headers.

> This problem was been fixed around 1993.. It is not possible
> to send anonymous email through an open relay. (you still hear
> this from radical antispammers, though).

If sufficient logging information is maintained, it is not 
possible to send mail through a relay (open or not) without 
identifying the IP address of the sender (that statement was 
true before and after the changes you identify as "around 
1993").  Getting from that IP address to identification of the 
individual sender --which is what you presumably mean by "not 
anonymous"-- is more or less difficult and more or less 
expensive, depending on a number of other circumstances.   In 
some cases --and, again, if one believes that people's time has 
any value-- the practical costs of identifying an individual far 
exceed any possible value in doing so.  In some others, it may 
be nearly impossible.   For example, there is a well-known Asian 
country in which most of the dialup services appear to be 
freenets, with widely-available dialup numbers and passwords 
shared among, I believe, literally millions of people.  The mail 
relays on those systems have no way to determine which user is 
originating a piece of mail, the user's IP address is of no 
help, and a system receiving mail from one of those relays can 
only identify the relay host.  That is a pretty good 
approximation to anonymity in my book.

>> And, no, I don't believe that either of the measures above
>> will significantly reduce the volume of spam.
>
> Then why bother at all?

First, because I was trying to respond factually to a message 
thread that appeared to assert that the only way to obtain 
certain classes of service was to have open relays.  My note was 
written simply to refute that claim.

Second, because, where it is possible and doesn't cause other 
problems, having sufficient authentication that mail servers can 
be held responsible for traffic originating on them or relayed 
through them may have technical and social advantages 
independent of their relationship to spam (and your observations 
about "anonymous relays", as discussed above, just don't hold 
water).

And finally, believing that a particular technique will not be 
especially effective --in statistical or absolute terms-- 
against some behavior I don't approve of does not give me the 
obligation to make things any easier for the offender.

           john





From owner-ietf@ietf.org  Tue May 27 22:18:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14621
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 22:18:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kpxo-0005GE-Qm
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 21:42:48 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KpV0-0002b2-Fl
	for ietf@asgard.ietf.org; Tue, 27 May 2003 21:13:02 -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 VAA12933
	for <ietf@ietf.org>; Tue, 27 May 2003 21:12:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KpTS-0004HS-00
	for ietf@ietf.org; Tue, 27 May 2003 21:11:26 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KpTR-0004HJ-00
	for ietf@ietf.org; Tue, 27 May 2003 21:11:25 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 3E48E1396A; Wed, 28 May 2003 01:12:30 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: spam
References: <963621801C6D3E4A9CF454A1972AE8F504F82C@server2000.arneill-py.sacramento.ca.us>
From: Paul Vixie <vixie@vix.com>
Date: 28 May 2003 01:12:30 +0000
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F82C@server2000.arneill-py.sacramento.ca.us>
Message-ID: <g3smqzub5t.fsf@sa.vix.com>
Lines: 30
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

michel@arneill-py.sacramento.ca.us ("Michel Py") writes:

> > we (the e-mail producing/consuming community) have the technology, we
> > have the collective wit and wisdom, we have the proven commercial value
> > of the service.  what we lack, dear ietf, is simply: leadership.
> 
> Given what you wrote just above (which I agree with), what is your
> assessment that a system such as what you have in mind would successfully
> reach IETF consensus?

one developed outside ietf.  like html and http, for examples which could
never have been done amongst the self-selected rabble and trolls who manage
to consistently keep ietf's discussions focused on weeds and corners, but
which the ietf had no choice but to "embrace and extend" once they were
clearly defacto standards.  (this is what we SHOULD have done, and may yet
HAVE to do, with dnssec.)

but i digress.  MIME worked.  EDNS worked.  IPv6, warts and all, worked.
ESMTP was ugly and bloody, but it worked.  there's no reason in principle
why the MIME and ESMTP examples can't be replayed toward a secure "ibcs".

> The reason I agree with Noel along the lines that the only way is making
> spammers pay for sending email is not because I don't think that we don't
> have what it takes to invent a protocol, but because I think it will be
> torpedoed before it is born.

well, it's hard to commit acts of leadership inside a burning movie theatre.
(pass me another marshmellow, will you?)
-- 
Paul Vixie



From owner-ietf@ietf.org  Tue May 27 22:18:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14690
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 22:18:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kpxp-0005GK-1o
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 21:42:49 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KpVP-0002bB-Tp
	for ietf@asgard.ietf.org; Tue, 27 May 2003 21:13:27 -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 VAA12940
	for <ietf@ietf.org>; Tue, 27 May 2003 21:13:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KpTr-0004Hd-00
	for ietf@ietf.org; Tue, 27 May 2003 21:11:51 -0400
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KpTq-0004HP-00
	for ietf@ietf.org; Tue, 27 May 2003 21:11:51 -0400
Received: from rflooker1 ([191.1.2.48]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com for <ietf@ietf.org>;
          Tue, 27 May 2003 21:12:54 -0400
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf@ietf.org
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: The utility of IP, port blocking
Date: Tue, 27 May 2003 21:12:54 -0400
Message-ID: <20030528011254866.AAA413@hq.lindsayelec.com@rflooker1>
Sender: owner-ietf@ietf.org
Precedence: bulk

Said today:
>In a major example of false positives, we already have examples of one
>real cost of spam. AOL (as one example of many) has declared ranges of
>IP addresses marked 'residential' as invalid for running a particular
>application. In this case SMTP, but which app is next? There is a 'guilt
>by association' presumption here by the operations community, which when
>carried into other applications results in substantially limited value
>in the core IP protocol. 

About port blocking:
I think its inevitable a class action lawsuit will be tabled that any port
must be opened at the same rate/cost restriction structure (or lack of it),
as any other. The concern IP is at least a little as risk for functionality
is pretty serious stuff.

MPLS might improve this by making only the edges know the applications. But
the general principle you pay for "X" and don't get it because of the
actions of others who's behaivoirs superficially  resemble yours is unfair
in a way regarded as often actionable.

regs
Dan




From owner-ietf@ietf.org  Tue May 27 22:21:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13364
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 21:33:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KpHR-00010N-AQ
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 20:59:01 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kp0G-0008FD-Gz
	for ietf@asgard.ietf.org; Tue, 27 May 2003 20:41:16 -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 UAA11747
	for <ietf@ietf.org>; Tue, 27 May 2003 20:41:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KoyZ-0003vf-00
	for ietf@ietf.org; Tue, 27 May 2003 20:39:31 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KoyZ-0003vc-00
	for ietf@ietf.org; Tue, 27 May 2003 20:39:31 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 208024; Tue, 27 May 2003 19:40:34 -0500
Message-ID: <3ED4059F.3080708@ehsco.com>
Date: Tue, 27 May 2003 19:41:03 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Vernon Schryver <vjs@calcite.rhyolite.com>
CC: ietf@ietf.org
Subject: Re: spam
References: <3ED3E536.60BCD64E@earthlink.net> <200305272328.h4RNSOJs026657@calcite.rhyolite.com>
In-Reply-To: <200305272328.h4RNSOJs026657@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/27/2003 6:28 PM Vernon Schryver wrote:

> Again, if spam costs mail providers much more than $1 or $2/month/user,
> then how can free providers offer mailboxes and how can you buy full
> Internet service including the use of modem pools or whatever for
> $10-$15/month?

In the case of Yahoo and Hotmail, they have free and premium accounts.
They underwrite both services with advertising income. The "cost" for the
free service is the value they have assigned to the ads they display when
you read your mail. The cost for the premium service is that value plus a
little extra.

http://help.msn.com/!data/en_us/data/HMFAQv7.its51/$content$/HM_FAQ_HowMuchEmailStorageSpaceDoIGetWithHotmailUnAuth.htm

| With free MSN Hotmail accounts you receive 2 megabytes (MB) of
| storage space on Hotmail servers for messages and attachments.

| Subscribers to MSN Extra Storage and MSN Internet Services monthly
| subscribers receive 10 MB of Hotmail storage space as well as 30 MB
| of storage space in MSN Groups on which to store and share photos,
| music, and other files.

Yahoo's "free" option is a six-megabyte mailbox. The upgrade options are
at http://billing.mail.yahoo.com/bm/Upgrades and below. Note that there is
 a "Plus" option which is an extra-premium to get rid of their ads.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Tue May 27 22:24:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15163
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 22:24:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kpxr-0005Na-GW
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 21:42:51 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kpq0-0004Id-96
	for ietf@asgard.ietf.org; Tue, 27 May 2003 21:34:44 -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 VAA13626
	for <ietf@ietf.org>; Tue, 27 May 2003 21:34:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KpoR-0004U2-00
	for ietf@ietf.org; Tue, 27 May 2003 21:33:07 -0400
Received: from out001pub.verizon.net ([206.46.170.140] helo=out001.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KpoQ-0004Rd-00
	for ietf@ietf.org; Tue, 27 May 2003 21:33:06 -0400
Received: from earthlink.net ([4.65.81.213]) by out001.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030528013406.OQGR12592.out001.verizon.net@earthlink.net>;
          Tue, 27 May 2003 20:34:06 -0500
Message-ID: <3ED41131.586842D3@earthlink.net>
Date: Tue, 27 May 2003 18:30:25 -0700
From: Peter Deutsch <pdeutsch@earthlink.net>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Vernon Schryver <vjs@calcite.rhyolite.com>
CC: ietf@ietf.org
Subject: Re: spam
References: <3ED3E536.60BCD64E@earthlink.net> <200305272328.h4RNSOJs026657@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [4.65.81.213] at Tue, 27 May 2003 20:34:06 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

g'day,

Vernon Schryver wrote:
> 
> > From: Peter Deutsch <pdeutsch@earthlink.net>
> 
> > ...
> > despite the fact that the vast majority of folks have *not* agreed with
> > you, and some of us have specifically challenged (I wont be so
> > presumptuous as to say "refuted") your claim.
> 
> That's nonsense.  There have been repeated statements to the effect
> that doubling the size of a large mail system to deal with a doubling
> of spam is very expensive.  That does not conflict with claims that
> the cost to provide mail service for a single user is low.

Actually I didn't say the cost "to provide mail service for a single
user is low", since I would interpret that to mean you were talking only
about the hardware cost of the mail hosting system. In fact, the line I
was responding to was:

# the cost associated with email is practically non-existant,
# and does not ever cost any user more than $1 or $2 per month, 

I have been trying to make the point (albeit unsuccessfully, it seems)
that if you want to talk about "the cost associated with email" you need
to look at the "total cost of ownership" for processing email, and that
this is dominated by human costs, especially at the margins of the
network. 

Maybe I should have written something like: "The cost of physical
delivery and storage are but a small part of the total cost of ownership
here." Oh, wait - I did, that was the bit you left off. ;-)

Somebody did a calculation assuming a person who bills out at $60/hour.
In fact, it's not outlandish for a consultant or other professional to
bill out at $150 to $250 an hour, which means that one hour of
spam-related lost time a year costs would you as much as $20 per month.
If that's all the time you spent processing spam, it would translate to
300 seconds of lost time a month, or 10 seconds a day for those of us
who read email every day. Adjust your constants and multiply by whatever
fudge factor suits your usage pattern, the point is that the real cost
of spam is far more than the cost of the email account and human costs
would appear to dominate the equation.

*That* is why I object to statements like "If you pay $1 per month for
email, and get 50 messages per day, then a spam costs you $0.0006666."
That's no more true that that gas at $1.61 mean your car costs you 5.3 a
mile to run (yeah, I know, somebody already pointed out my typo on that
one in a previous message... :-)


...
> Yes, the costs of spam are mostly in what it costs in human time.
> 
> However, the fact that the human costs of spam are large do not justify
> your canards and other nonsense about the costs of bandwidth, CPU
> cycles, disk space, and even human system administrator time to deal
> with spam.

Actually, others may have talked about the cost of bandwidth and CPU,
but I don't think I did. I *did* cite a real example of lost time and
effort tracking down a problem in an underfunded school as an
illustrative example, but it was not a canard ("An unfounded or false,
deliberately misleading story."). The school was St.Joseph's School,
Mountain View, Ca and I was the volunteer who donated his time in lieu
of payment. IIRC correctly, the school would bill me $10/hour for
unfulfilled volunteer requirements at the end of the school year, so I
think it fair to assign an economic value of $10/hour to this volunteer
time, even though you probably couldn't hire a good sysadmin in Mountain
for $10/hour and I certainly bill my time out at more than that for
consulting work.

So forget the staff member's time for the moment, I personally donated
volunteer time to determin why the machine was sluggish and to take some
remedial cleanup steps. I did this in lieu of a $10/hour payment which I
would otherwise have had to make and having donated my time, I therefore
didn't donate my time to do something else I could have done for the
school. Sure I did other stuff on that trip, but I have no trouble
saying that this incident cost the school about $10 in opportunity cost.
They fold it into their overhead, and get that much less stuff elsewhere
as a consequence. And I personally have no trouble assigning this
expense to the "cost of SPAM" account, since that's what it was about -
a spamer beat up a small group's server, and they lost time and money as
a consequence. Now, can that other guy please stop saying there's no
cost to spam? *That* appears to me to be a canard...



> Again, if spam costs mail providers much more than $1 or $2/month/user,
> then how can free providers offer mailboxes and how can you buy full
> Internet service including the use of modem pools or whatever for
> $10-$15/month?

Again (not a good sign, I suspect the frequent occurance of this word
indicates that we're all looping here..) this is not about just the cost
of providing a mail host, it's about total cost of ownership.

I give up. Michel's right, we should stop now. I'm off to get a beer and
heartily recommend everybody else do the same....



			- peterd

-- 
---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software

                        "Bungle..."
               "That's an 'i', you idiot..."
                  "Oh, right. 'Bingle..."

                            - Red versus Blue...

---------------------------------------------------------------------



From owner-ietf@ietf.org  Tue May 27 22:42:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15804
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 22:42:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kqgi-0008Mr-Bt
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 22:29:12 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KqKb-0005yw-OK
	for ietf@asgard.ietf.org; Tue, 27 May 2003 22:06:21 -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 WAA14274
	for <ietf@ietf.org>; Tue, 27 May 2003 22:06:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KqJ3-0004fG-00
	for ietf@ietf.org; Tue, 27 May 2003 22:04:45 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KqJ2-0004f1-00
	for ietf@ietf.org; Tue, 27 May 2003 22:04:44 -0400
Received: from localhost (dwm@localhost)
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h4S1xGx02541;
	Tue, 27 May 2003 18:59:16 -0700
Date: Tue, 27 May 2003 18:59:16 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
cc: <ietf@ietf.org>
Subject: Re: spam
In-Reply-To: <200305261906.h4QJ63W7025426@ginger.lcs.mit.edu>
Message-ID: <Pine.LNX.4.33.0305271824000.865-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Mon, 26 May 2003, J. Noel Chiappa wrote:

>...
>
> The *only* thing that's going to stop spam is charging for email. Everything
> else is a waste of time, because you're going to run into impossible
> arguments trying to define what's spam, and what's legitimate bulk email
> (q.v. the recent message about IETF-Announce email).
>
> Needless to say, charging for email means changing the underlying protocols.
> That's us. It's not going to be simple (we need an underlying micro-payments
> system), and it's going to take a lot of attention to detail (q.v.
> IETF-Announce again), but I think it's the only real cure.

What I'd say is that the only way to reduce unsolicited email to a
tolerable level is to change the economics of sending spam such that the
folks paying to send spam will focus their emissions for much higher
positive response rates.

Sending physical advertising has many costs in addition to the transport
cost so it probably costs more than the US 1st class mail rate per piece
even though the advertising rate is much lower. While I get more junk mail
than I'd prefer, 90-95% has some relationship to my interests. If .01% of
the spam I receive has a relationship to my interests, I'd be surprised
(getting rich quick isn't really an interest ;-:).

There is an active proposal, perhaps already submited, in process by Rep.
Zoe Lofgren to establish a penalties and a bounty for spam. This is an
interesting variant of the enforcement paradigm, but I agree with those
who have already suggested that our government too many larger crimes to
consider.

Instead, I believe some form of pay to send stamp based approach in
parallel with the current 'free' system has the best chance of curtaining
spam while preserving the 'free' nature of the current system. This will
require new protocols as well as some social/legal infrastructure to
accomplish (an effective payment system for example). I would expect that
a portion of each sender fee would be credited to the receiver and some
portion would support the new infrastructure.

If we are able to design the protocols I imagine, the mail recipients will
drive adoption fairly quickly once implementations are available. I would
expect that an early filter criteria would be whether the mail arrived via
the new protocols. No, don't relay to my blackberry, cell phone, etc. No,
stick in a 2nd class inbox. Etc.

Since part of this solution would have to be the identification/trust kind
of mechanism Paul Vixie mentioned, easy to implement and utilzed filters
could be based on the sender being identified.

I will shut up now because I think the point of an IETF list discussion
should be to build momentum for working the problem and not design
complete solutions.

Dave Morris




From owner-ietf@ietf.org  Tue May 27 22:42:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15916
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 22:42:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KqpB-0000Du-Js
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 22:37:57 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KqTy-0006W4-Ra
	for ietf@asgard.ietf.org; Tue, 27 May 2003 22:16:02 -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 WAA14512
	for <ietf@ietf.org>; Tue, 27 May 2003 22:16:00 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KqSQ-0004jq-00
	for ietf@ietf.org; Tue, 27 May 2003 22:14:26 -0400
Received: from h80ad26af.async.vt.edu ([128.173.38.175] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KqSP-0004jn-00
	for ietf@ietf.org; Tue, 27 May 2003 22:14:25 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h4S2FsN6003379;
	Tue, 27 May 2003 22:15:54 -0400
Message-Id: <200305280215.h4S2FsN6003379@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Re: spam 
In-Reply-To: Your message of "Tue, 27 May 2003 21:04:03 EDT."
             <Pine.LNX.4.44.0305272043280.8489-100000@commander.av8.net> 
References: <Pine.LNX.4.44.0305272043280.8489-100000@commander.av8.net>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_15046098P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 27 May 2003 22:15:54 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_15046098P
Content-Type: text/plain; charset=us-ascii

On Tue, 27 May 2003 21:04:03 EDT, Dean Anderson said:

> If you mean it costs you a nickle to press delete, then the cost of
> hauling out the trash would be an issue for Junk Mail, and Junk Faxes, and

Alan Ralsky happens to have some strong opinions on what the cost of hauling
out the trash is.

--==_Exmh_15046098P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+1BvacC3lWbTT17ARAsL8AJ9qv6waIO1dS7HTUY0+SjDG8MJ0HwCeL5cF
DdKI0nJK5PCvjiFysuRL1B4=
=8QX3
-----END PGP SIGNATURE-----

--==_Exmh_15046098P--



From owner-ietf@ietf.org  Tue May 27 22:56:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA16304
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 22:56:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kqrr-0000e2-43
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 22:40:43 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kqh7-0008PM-22
	for ietf@asgard.ietf.org; Tue, 27 May 2003 22:29:37 -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 WAA15407
	for <ietf@ietf.org>; Tue, 27 May 2003 22:29:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KqfY-0004yB-00
	for ietf@ietf.org; Tue, 27 May 2003 22:28:00 -0400
Received: from 75.5.33.65.cfl.rr.com ([65.33.5.75] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KqfX-0004y8-00
	for ietf@ietf.org; Tue, 27 May 2003 22:27:59 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19KWem-0006Eh-00; Tue, 27 May 2003 01:05:52 -0400
Date: Tue, 27 May 2003 01:05:49 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Dean Anderson <dean@av8.com>
cc: "Eric A. Hall" <ehall@ehsco.com>, John Stracke <jstracke@centive.com>,
        <ietf@ietf.org>
Subject: Re: spam
In-Reply-To: <Pine.LNX.4.44.0305272043280.8489-100000@commander.av8.net>
Message-ID: <Pine.LNX.4.44.0305270104310.23359-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Dean,

>
> If you mean it costs you a nickle to press delete, then the cost of
> hauling out the trash would be an issue for Junk Mail, and Junk Faxes, and
> the cost of listening to a telemarketer would be a factor there, too.

I would be in favor of getting rid of the telemarketers.  The call centers
are sweat-shops anyway.

scott

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81




From owner-ietf@ietf.org  Tue May 27 23:06:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16629
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 23:06:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kqrr-0000ew-H9
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 22:40:43 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KqkT-0008Sd-Oy
	for ietf@asgard.ietf.org; Tue, 27 May 2003 22:33:05 -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 WAA15501
	for <ietf@ietf.org>; Tue, 27 May 2003 22:33:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kqiv-0004zy-00
	for ietf@ietf.org; Tue, 27 May 2003 22:31:29 -0400
Received: from pop017pub.verizon.net ([206.46.170.210] helo=pop017.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kqiu-0004zb-00
	for ietf@ietf.org; Tue, 27 May 2003 22:31:28 -0400
Received: from earthlink.net ([4.65.81.213]) by pop017.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030528023233.SNJD27254.pop017.verizon.net@earthlink.net>;
          Tue, 27 May 2003 21:32:33 -0500
Message-ID: <3ED41EE4.96EE6A26@earthlink.net>
Date: Tue, 27 May 2003 19:28:52 -0700
From: Peter Deutsch <pdeutsch@earthlink.net>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
CC: ietf@ietf.org
Subject: A modest proposal (was: Re: spam)
References: <200305280051.h4S0pJoc005872@ginger.lcs.mit.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at pop017.verizon.net from [4.65.81.213] at Tue, 27 May 2003 21:32:33 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

g'day,

"J. Noel Chiappa" wrote:
...
> Which is precisely why I say that the solution to spam is to charge for
> email. It avoids the whole question of defining what is and is not spam.
> 
> More specifically, change the email protocol so that when email arrives from
> an entity which is not on the "email from these entities is free" list, the
> email is rejected unless is accompanied by a payment for $X (where X is set
> by a knob on the machine).

You probably know this already, but for those who don't, Brad Templeton
proposed this scheme a while ago, based upon am micropayments model and
called it "estamps". See:

    http://www.templetons.com/brad/spam/estamps.html

He's also got a summary page on the topic of spam at:

    http://www.templetons.com/brad/spam/


He's since repudiated the idea, but it's been taken up and worked on in
the context of the hashcash system, which seeks to impose a measureable
computation cost on the sender in lieu of processing a micropayment.


Although Brad himself has repudiated the idea, I believe that the
general approach of automating the accounting and imposition of cost (as
is done in Hashcash) shows some promise, but what I actually think we
need is an automatic way to extend trust and build trust relationships.
Paul Vixie alluded to a "trusted-introducer model similar in concept to
pgp but more market-ready" a couple of postings ago, which I actually
think is the way to go.

So, okay, this discussion needs to move off the ietf general list, but
again I agree with Paul. Where is the direction about where we should be
heading with this?

				- peterd


-- 
---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software

                        "Bungle..."
               "That's an 'i', you idiot..."
                  "Oh, right. 'Bingle..."

                            - Red versus Blue...

---------------------------------------------------------------------



From owner-ietf@ietf.org  Tue May 27 23:06:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14622
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 22:18:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kpxp-0005Gf-F6
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 21:42:49 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KpZT-0002fB-MQ
	for ietf@asgard.ietf.org; Tue, 27 May 2003 21:17:39 -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 VAA13017
	for <ietf@ietf.org>; Tue, 27 May 2003 21:17:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KpXv-0004Ix-00
	for ietf@ietf.org; Tue, 27 May 2003 21:16:03 -0400
Received: from smtp-out.comcast.net ([24.153.64.113])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KpXu-0004If-00
	for ietf@ietf.org; Tue, 27 May 2003 21:16:02 -0400
Received: from max.hunnysoft.pri
 (pcp01719983pcs.nrockv01.md.comcast.net [68.50.252.119])
 by mtaout03.icomcast.net
 (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003))
 with ESMTP id <0HFK0066SOWAVY@mtaout03.icomcast.net> for ietf@ietf.org; Tue,
 27 May 2003 21:16:58 -0400 (EDT)
Received: from [192.168.2.5] (helo=hunnysoft.com)	by max.hunnysoft.pri with
 esmtp (Exim 3.36 #2)	id 19KpWA-0000Fq-00	for ietf@ietf.org; Tue,
 27 May 2003 21:14:14 -0400
Date: Tue, 27 May 2003 21:17:36 -0400
From: Doug Sauder <dws@hunnysoft.com>
Subject: What the IETF should do: Amend RFC 2822  (was: Re: spam)
To: ietf@ietf.org
Message-id: <3ED40E30.6070501@hunnysoft.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1)
 Gecko/20020826
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

Pardon me if I jump in here and change the direction of this discussion to
something more relevant.

What the IETF should do: Amend RFC 2822 to change the definition of an
email address in a way that is entirely backward compatible, yet supports
aliases.  I propose a change like the following: (pardon the ambiguity)

addr-spec       =       local-part [ "+" password ] "@" domain

local-part      =       dot-atom / quoted-string / obs-local-part

password        =       atom

domain          =       dot-atom / domain-literal / obs-domain

domain-literal  =       [CFWS] "[" *([FWS] dcontent) [FWS] "]" [CFWS]

dcontent        =       dtext / quoted-pair

dtext           =       NO-WS-CTL /     ; Non white space controls

                          %d33-90 /       ; The rest of the US-ASCII
                          %d94-126        ;  characters not including "[",
                                          ;  "]", or "\"

First of all, realize that there are already implementations deployed that
recognize email aliases -- "plus aliases" in particular.

Second, there are implementations that recognize aliases, but in
incompatible ways.  (Sendmail and Exim recognize a "+" sign.  Qmail
recognizes a '-' sign.  There are still others.)  Therefore, it is
incumbent on the IETF to update the standard for an email address so that
implementations can interoperate.  There are also new products that depend
on a plus-alias-like mechanism to create useful filters.  Without
standarization, there is the real possibility of products that don't
interoperate.

Third, this definition is entirely backward compatible, so it has
absolutely no impact on existing (correct) implementations.

Fourth, with a standard for aliases, new products can be created, and
perhaps used in creative ways to block spam.  Without a standard, new
products will be created, but they will not interoperate.  I could envision
mainstream products being modified to support plus aliases in a way that
makes it easy for unsophisticated users to use them.  But that won't happen
if there is no chance for interoperability.

Fifth, plus aliases have an impact on the S/MIME standard.  I would like to
get one personal ID certificate and use it with many aliases.  That won't
happen if aliases are not recognized by a change in the standard.  Software
that checks the identity of the sender SHOULD remove the extra "password"
part when comparing the sender address to the email address in the
certificate.  That would provide the same assurance of the sender's
authenticity, while allowing the sender to create a family of related
aliases.  The way to think about this is, the local-part and the domain
establish identity, while the "password" is used only in delivery.  If you
think S/MIME is already difficult to use, imagine needing a different
certificate for each alias you use.

How this impacts spam:

I have talked to many individuals about the use of "plus aliases."  Most
responses I get fall into two categories: (1) some have never been aware of
plus aliases, and (2) some are aware of them but think they are too
complicated for average users.  On the last point, I am not sure I agree
entirely.  Yes, they are too complicated as things are now.  But good
software designers are able to make complicated things simple.  (There are
already software products that try to make the use of aliases entirely
transparent.)

I think we could explain to unsophisticated users that the extra part in
their email address, if they choose to use it, is a "password" that keeps
junk out of their inbox.  They will understand that.  We can also explain
to them that if their email account is overrun with spam, they don't have
to change ISPs to get a new email address.  They can just change their
password.  And, I think that the popular email client applications could be
changed to make it very easy to use different aliases.  I'm not a user
interface expert, but I don't see why something as simple as
password-protecting a folder in your inbox should be complicated.  One
thing I do know, is that there are many unsophisticated users who feel
almost helpless against the onslaught of spam.  Some are driven to change
ISPs.  I think many would welcome the opportunity to password-protect a
folder in their inbox, and give out the "password" to only close relatives
and friends.

Using plus aliases is purely optional.  Users who want things simple
continue life as before -- not using plus aliases.  Users who choose to
receive a limited amount of email on their cell phone or PDA can use an
alias that they give out to only a handful of people.

The IETF is an organization that creates standards.  I believe we need a
standard for email aliases -- using a plus sign or whatever.  With almost
no impact on existing infrastructure, we can give creative anti-spam
engineers a new tool to use, and I am eager to see how such a tool might be
used.  But regardless of what one might think of the potential to control
spam through the use of aliases, creating a standard for aliases is work
the IETF should take on.

-- 
Doug Sauder
Hunny Software, Inc





From owner-ietf@ietf.org  Tue May 27 23:30:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17271
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 23:30:34 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KrLv-0002oT-3G
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 23:11:47 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kr3F-0001VF-40
	for ietf@asgard.ietf.org; Tue, 27 May 2003 22:52:29 -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 WAA16235
	for <ietf@ietf.org>; Tue, 27 May 2003 22:52:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kr1g-0005Co-00
	for ietf@ietf.org; Tue, 27 May 2003 22:50:52 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kr1f-0005Cl-00
	for ietf@ietf.org; Tue, 27 May 2003 22:50:52 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id WAA27025;
	Tue, 27 May 2003 22:47:58 -0400
Date: Tue, 27 May 2003 22:48:51 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <200305280039.h4S0djLF009506@calcite.rhyolite.com>
Message-ID: <Pine.LNX.4.44.0305272240360.8489-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 27 May 2003, Vernon Schryver wrote:

> > From: Dean Anderson <dean@av8.com>
>
> > ...
> > No one has demonstrated any cost to spam, other than annoyance and
> > infrastructure costs which are passed on to users[1], and it seems there
> > is very little to add.
>
> That's a ridiculous overstatement.  Spam may be too cheap to meter
> for an individual user, but if you have 30,000,000 users or only
> 30,000, you'll find that the total costs are substantial, particularly
> when you need to double the size of your systems to deal with a doubling
> of spam.

Whether you have 30 million or 30 thousand, the costs are passed on to the
user. At 30 million, economies of scale make the cost of spam (to the ISP)
even less.  It doesn't usually change the price to the user, so big ISPs
tend to make more money at the same price level.

Enterprises have revenue, too. And cost structures that are substantially
different (with respect to email) from similarly sized ISPs.

> > Vixie and other radicals also continues to ignore Shannon's theorems. ...
>
> While it's true that proving the non-existence of covert channels
> is hard, you've not related that theorem to anything related to spam.
> Even if covert channels or the relation among power, noise, bandwidth,
> and information have something to do with spam, you've not shown
> any connection to dealing with the spam problem.

Its not hard, its impossible.

I've pointed out the spam is a covert channel, with regard to Shannons
theorem.

> A good rule of thumb is that only people who don't know much about
> major theorems like Shannon's and Godel's quote them as proofs in
> discussions like this.  I think you should have chosen some other
> beautiful bit of archana such one of the fixed point theorems or
> Fred J. Cohen's Forcing and Generic instead of something that more
> than a few people around here know about such as covert channels.

This is a fine exposition, about what I'm not sure.. It does not seem to
demonstrate that I am wrong, or that spam isn't a covert channel, or that
Shannon's theorem (somehow) doesn't apply.

Apparently, you don't understand anything about covert channels, so
perhaps you should let the ones who do try to dispute my assertions.

		--Dean




From owner-ietf@ietf.org  Tue May 27 23:34:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17571
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 23:34:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KrZE-0003IN-3A
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 23:25:32 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KrHk-0002cT-12
	for ietf@asgard.ietf.org; Tue, 27 May 2003 23:07:28 -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 XAA16745
	for <ietf@ietf.org>; Tue, 27 May 2003 23:07:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KrGB-0005MB-00
	for ietf@ietf.org; Tue, 27 May 2003 23:05:51 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KrGA-0005Ks-00
	for ietf@ietf.org; Tue, 27 May 2003 23:05:50 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id WAA11781;
	Tue, 27 May 2003 22:57:14 -0400
Date: Tue, 27 May 2003 22:58:07 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <200305280051.h4S0pJoc005872@ginger.lcs.mit.edu>
Message-ID: <Pine.LNX.4.44.0305272253000.8489-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

You already have that in some ways: Its called a blacklist.

And Type 1 spammers can sue the blacklist for anti-trust violations.

But the other problem is that charging for email (and I take you to mean
charging everyone a some fee, like a nickle for every message, so that
bulk mailers would pay more) would raise issues of gouging and price
fixing and unfair competition, and anti-trust issues.  A large company
can't fix different prices for the same commodity service, to different
customers.

		--Dean

On Tue, 27 May 2003, J. Noel Chiappa wrote:

>     > From: Dean Anderson <dean@av8.com>
>
>     > Shannon's theorem still stands.
>     > ...
>     > In terms of spam, this means that it is impossible to construct a
>     > protocol that cannot be abused
>     > ...
>     > No protocol can ever be constructed that is spam-free.
>     > ...
>     > All abusers are the customer of some ISP, somewhere. There are no
>     > outsiders. The spammers are in fact authorized users of some ISP that
>     > are authorized to send email. They remain authorized to send email
>     > until they lose service with that ISP.
>
> Which is precisely why I say that the solution to spam is to charge for
> email. It avoids the whole question of defining what is and is not spam.
>
> More specifically, change the email protocol so that when email arrives from
> an entity which is not on the "email from these entities is free" list, the
> email is rejected unless is accompanied by a payment for $X (where X is set
> by a knob on the machine).
>
> (And yes, I know there are issues with relays, etc.)
>
> If all spam arrives with a $1 bill, I'd be happy to let spammers send me as
> much spam as they want.
>
> 	Noel
>
>




From owner-ietf@ietf.org  Tue May 27 23:43:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17806
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 23:43:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KrZE-0003Ip-Ff
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 23:25:32 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KrIO-0002ck-65
	for ietf@asgard.ietf.org; Tue, 27 May 2003 23:08:08 -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 XAA16792
	for <ietf@ietf.org>; Tue, 27 May 2003 23:08:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KrGp-0005N9-00
	for ietf@ietf.org; Tue, 27 May 2003 23:06:31 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KrGo-0005MZ-00
	for ietf@ietf.org; Tue, 27 May 2003 23:06:31 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id XAA12002;
	Tue, 27 May 2003 23:02:16 -0400
Date: Tue, 27 May 2003 23:03:19 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: "Eric A. Hall" <ehall@ehsco.com>
cc: alh-ietf@tndh.net, "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <3ED40820.5020900@ehsco.com>
Message-ID: <Pine.LNX.4.44.0305272259001.8489-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Tue, 27 May 2003, Eric A. Hall wrote:

>
> on 5/27/2003 6:59 PM Tony Hain wrote:
>
> > protocol design. We as the IETF need to step up and provide an alternate
> > design if we want the system to change. Some components of a new design
> > need to be a viable trust model, and irrefutable traceability.

we don't presently have any problems with traceability.  We have no
problems finding the person responsible for bomb threats or other issues
that warrant law enforcement requests.  We have a slight issues with open
proxies, but only because the abuser has crossed an organizational
boundery, and the organization that knows the previous hop or the
identity, won't reveal it without a subpoena.

This is a legal issue, not a technical issue.

		--Dean




From owner-ietf@ietf.org  Tue May 27 23:53:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18137
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 23:53:34 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kre3-0003TB-PF
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 23:30:31 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KrRR-0002xd-DK
	for ietf@asgard.ietf.org; Tue, 27 May 2003 23:17:29 -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 XAA17049
	for <ietf@ietf.org>; Tue, 27 May 2003 23:17:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KrPs-0005RL-00
	for ietf@ietf.org; Tue, 27 May 2003 23:15:52 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KrPs-0005RI-00
	for ietf@ietf.org; Tue, 27 May 2003 23:15:52 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id XAA29129;
	Tue, 27 May 2003 23:12:03 -0400
Date: Tue, 27 May 2003 23:13:06 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Valdis.Kletnieks@vt.edu
cc: ietf@ietf.org
Subject: Re: spam 
In-Reply-To: <200305280215.h4S2FsN6003379@turing-police.cc.vt.edu>
Message-ID: <Pine.LNX.4.44.0305272303490.8489-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Hahahha. So do I. And it isn't free, and landfills are ruining the planet.
But it hasn't stopped the post office.

The radicals just don't get what they are up against.  Every letter you
send actually subsidizes the cost of a junk mailer, who gets a discount to
send junk mail.  All you get is the ability to be put on a "do not send"
list maintained by the post office.  But you don't get to not subsidize
junk postal mail.

Talk about the cost of trash... You actually pay for junk mail through
your stamps.  All these same issues were hashed out in the 70's.

The junk fax law is a aberration to the rest of the law on the subject.
And the FTC has ruled that a prior business relationship isn't
"unsolicited" for purposes of the junk fax law.

We are lucky that spammers don't get a discount and that we don't have to
pay more so that their services aren't so expensive. As junk mailers
proved, commerce trumps personal rights. Thats the price of consumerism.

		--Dean


On Tue, 27 May 2003 Valdis.Kletnieks@vt.edu wrote:

> On Tue, 27 May 2003 21:04:03 EDT, Dean Anderson said:
>
> > If you mean it costs you a nickle to press delete, then the cost of
> > hauling out the trash would be an issue for Junk Mail, and Junk Faxes, and
>
> Alan Ralsky happens to have some strong opinions on what the cost of hauling
> out the trash is.
>




From owner-ietf@ietf.org  Wed May 28 00:14:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18633
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 00:14:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ks7D-0005sj-1T
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 00:00:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Krg9-000492-Q4
	for ietf@asgard.ietf.org; Tue, 27 May 2003 23:32:41 -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 XAA17506
	for <ietf@ietf.org>; Tue, 27 May 2003 23:32:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kreb-0005Yb-00
	for ietf@ietf.org; Tue, 27 May 2003 23:31:05 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Krea-0005Xe-00
	for ietf@ietf.org; Tue, 27 May 2003 23:31:04 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id XAA22595;
	Tue, 27 May 2003 23:29:36 -0400
Date: Tue, 27 May 2003 23:30:40 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <Pine.LNX.4.44.0305272240360.8489-100000@commander.av8.net>
Message-ID: <Pine.LNX.4.44.0305272329320.8489-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Oops, editing error.


> Enterprises have revenue, too. And cost structures that are substantially
> different (with respect to email) from similarly sized ISPs.

This should read "And cost structures that are _NOT_ substantially
different..."

		--Dean

On Tue, 27 May 2003, Dean Anderson wrote:

> On Tue, 27 May 2003, Vernon Schryver wrote:
>
> > > From: Dean Anderson <dean@av8.com>
> >
> > > ...
> > > No one has demonstrated any cost to spam, other than annoyance and
> > > infrastructure costs which are passed on to users[1], and it seems there
> > > is very little to add.
> >
> > That's a ridiculous overstatement.  Spam may be too cheap to meter
> > for an individual user, but if you have 30,000,000 users or only
> > 30,000, you'll find that the total costs are substantial, particularly
> > when you need to double the size of your systems to deal with a doubling
> > of spam.
>
> Whether you have 30 million or 30 thousand, the costs are passed on to the
> user. At 30 million, economies of scale make the cost of spam (to the ISP)
> even less.  It doesn't usually change the price to the user, so big ISPs
> tend to make more money at the same price level.
>
> Enterprises have revenue, too. And cost structures that are substantially
> different (with respect to email) from similarly sized ISPs.
>
> > > Vixie and other radicals also continues to ignore Shannon's theorems. ...
> >
> > While it's true that proving the non-existence of covert channels
> > is hard, you've not related that theorem to anything related to spam.
> > Even if covert channels or the relation among power, noise, bandwidth,
> > and information have something to do with spam, you've not shown
> > any connection to dealing with the spam problem.
>
> Its not hard, its impossible.
>
> I've pointed out the spam is a covert channel, with regard to Shannons
> theorem.
>
> > A good rule of thumb is that only people who don't know much about
> > major theorems like Shannon's and Godel's quote them as proofs in
> > discussions like this.  I think you should have chosen some other
> > beautiful bit of archana such one of the fixed point theorems or
> > Fred J. Cohen's Forcing and Generic instead of something that more
> > than a few people around here know about such as covert channels.
>
> This is a fine exposition, about what I'm not sure.. It does not seem to
> demonstrate that I am wrong, or that spam isn't a covert channel, or that
> Shannon's theorem (somehow) doesn't apply.
>
> Apparently, you don't understand anything about covert channels, so
> perhaps you should let the ones who do try to dispute my assertions.
>
> 		--Dean
>
>




From owner-ietf@ietf.org  Wed May 28 00:16:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17272
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 May 2003 23:30:34 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KrHJ-0002YQ-Nl
	for ietf-list@asgard.ietf.org; Tue, 27 May 2003 23:07:01 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kqty-00010N-AZ
	for ietf@asgard.ietf.org; Tue, 27 May 2003 22:42:54 -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 WAA15898
	for <ietf@ietf.org>; Tue, 27 May 2003 22:42:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KqsP-00056Q-00
	for ietf@ietf.org; Tue, 27 May 2003 22:41:17 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KqsO-00055E-00
	for ietf@ietf.org; Tue, 27 May 2003 22:41:16 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id WAA09881;
	Tue, 27 May 2003 22:39:06 -0400
Date: Tue, 27 May 2003 22:40:09 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: John C Klensin <john-ietf@jck.com>
cc: shogunx <shogunx@sleekfreak.ath.cx>, Tony Hain <alh-ietf@tndh.net>,
        "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <26161928.1054070964@p3.JCK.COM>
Message-ID: <Pine.LNX.4.44.0305272213410.8489-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Tue, 27 May 2003, John C Klensin wrote:

> Dean,
>
> Since this is a response to a note I wrote, I'm going to try to
> respond to it.  Then I'm going to go back to deleting your mail
> without reading it, because it doesn't appear to me as if you
> really intend to participate in this discussion, rather than
> reciting your set of canards over and over again.   The opinion
> of others may differ, of course but, as far as I am concerned,
> you are succeeding in losing all credibility.

I think the same about you. It seems this will go nowhere. I'm just trying
to be polite. You've offered absolutely nothing of substance in this
-long- message.

> --On Tuesday, 27 May, 2003 20:15 -0400 Dean Anderson
> <dean@av8.com> wrote:
>
> >> Good try, but no cigar.  This would be entirely reasonable if
> >> open relays were the only way to accomplish what you are
> >> after.
> >
> > They are the only way to accomplish some things, like offering
> > RFC 821 SMTP service to customers outside our your address
> > space.
>
> Time to start checking either your facts or your explanations.
> People offer SMTP service to others (customers or otherwise)
> "outside their address space" all the time.

Please, tell me how. I'm all ears.  Please don't mention SMTP AUTH, as I
will think you haven't read my messages, and are posting your canards.

> Even I do it, as a courtesy to colleagues who have gotten stuck behind
> some of those ISP "use only our SMTP server, no outgoing SMTP
> connections get past our boundaries" arrangements (I won't dignify them
> by calling them "services") I detest.  Few of us do it with open relays

But a few do use open relays. Seems you are defeating your own
assertions...

> -- we do it with the two options I mentioned, with selective address
> filtering (a poor option, IMO, but it is often adequate), with "send
> after POP" (ditto), and other techniques that involve at least
> rudimentary authentication and authorization.

Selective address filtering doesn't scale, and doesn't work for dynamic
addresses. Try again, please.

> >> But, if open relays were used this way, the spam flow through
> >> those open relays are such that "aol/roadrunner/etc" would
> >> start blocking the IP addresses of those relays.  Back to
> >> square one, with no gain.
>
> > Type 1 spammers don't abuse open relays.
>
> That is a fairly strong universal assertion.  I trust that you
> have carefully interviewed and polled all of them, and that all
> of them told you the truth.

When they can't be contacted, I categorize them as Type 3. When they can
be contacted, they are Type 1 or Type 2.  Mostly, it is Type 3.

> I've had evidence to the contrary from time to time but, unless Paul
> Vixie's superhuman, and, IMO, helpful, efforts to collect statistics and
> categorize the stuff, I just get rid of it as quickly and efficiently as
> possible (an expensive process by any measure, unless you believe my
> time as a value of zero, as you apparently do).

I have some little evidence that Type 1 spammers are rarely using open
relays. However, they are using IP's scanned by open relay blacklists, and
products that are falsely claiming anonymity. In other words, these are
little guys, who were duped. Anti-spammers clearly had a role in their
"duping", however.

No large spamhouses have ever done this.

> > In my experience,
> > Type 3 abusers (anti-spammers in some cases), do this.  For
> > example, about a year ago, I got into an argument with two
> > radical antispammers. Suddenly, 2400 hundred different IP
> > addresses started trying to abuse our relays. This continued
> > for about 10 days, and then abated.  Fortunately, our relay
> > monitoring software blocked this, but it still involved
> > sorting through (no exaggeration) millions of messages.  After
> > that, (and still continuing aperiodically), someone began
> > trying to send viruses through a relay address advertised by a
> > European open relay blacklist, forging my address.
>
> > Coincidence? I don't think so.  Not given other more overt
> > threats and abuse by antispammers, such as Chris Neill and
> > others.
>
> Even if you have been unreasonably abused, it doesn't make your
> point valid.   Wrt regard to the legitimacy of spam, or spammer
> behavior, the technical term for your discussion above is "red
> herring".

Really.  Not everyone thinks so. But I may have been unreasonably abused,
having spoken out, so it is a valid point that my experience may be
different from others. But it is not so easy to dismiss the cases where
antispammers have been traced to abuse.

You just wish it were a red herring.

> >> Instead, there are at least two options available for that
> >> host on a "residential" network (both in heavy use today):
> >>
> >> 	(i) The host uses a relay supplied by its ISP, one that
> >> 	is not blocked by "aol/roadrunner/etc".  This is more or
> >> 	less satisfactory depending on what additional
> >> 	restrictions the ISP imposes on that relay, but the
> >> 	typical restrictions (much as I think they are
> >> 	unreasonable) have very little impact on the typical
> >> 	residential user who corresponds actively with
> >> 	"aol/roadrunner/etc users".
> >>
> >> 	(ii) The host uses a relay with which its owners have
> >> 	established some sort of business relationship and which
> >> 	relay is in a position to authenticate the host (via SSL
> >> 	certificates, SMTP AUTH, or some combination of a tunnel
> >> 	and authentication).
> >
> > (ii) isn't an option.
> >
> > Here's a short answer:
> >
> > 1) This is not a standard. It is optional, even if eventually
> > standardized.
>
> Gee.  I am co-author of some odd RFC whose status seems to be
> "proposed standard".  Something like RFC 2195.  There is also
> RFC 2554, also a proposed standard, which is, I think, where
> SSL/TLS tunnels are covered (this isn't worth the energy for my
> to go back and check).  And virtually all Internet standards, at
> all maturity levels, are "optional" in the sense that no one
> requires anyone to implement them.   If they are useful and
> needed, they get implemented.  If not, they don't.  You are,
> IMO, just wasting time here -- yours and, more important,
> everyone else's.

Proposed standards are not standards. You are wasting time. Anyone with a
keyboard can write a proposed standard. Its harder to come up with real,
workable solutions.

> > 2) There are only about 15 mail clients that support it.
>
> And I'd guess the first half-dozen of those represent the _vast_
> majority of non-AOL email senders on the Internet.  And users
> who _need_ these capabilities tend to find clients that support
> them.  So your point was?

That is not the goal of open, standards compliant systems.  The fact is
that these clients are compliant with standards in effect.  If you don't
understand that, then you have no place in a standards organization, like
the IETF.

> > 3) It doesn't scale for non-dialup ISPs
>
> And you base this on...?  Technologically, several of those
> techniques (note that I mentioned a series of techniques, so I'm
> not quite sure what "it" refers to) is easier to support with
> hardwired, semi-permanent, connections than it is with dialup.

I base this on the fact that if you want to provide backup SMTP service
for a large company which operates its own account management services,
that the ISP would have to create and then manage thousands, perhaps tens
of thousands, perhaps millions total, accounts, when it is only providing
backup relay services for companies outside of its IP address space.

This is foolishness. The creators of SMTP AUTH _ASSUMED_ that everyone fit
into a residential ISP model, where the ISP was already managing the
dialup accounts. This assumption isn't valid.  In other words, the SMTP
AUTH authors simply don't understand SMTP.

> > 4) Time Warner called it "unsuitable for business".
>
> And Ken Olsen couldn't imagine anyone really wanting a
> "personal", desktop, computer.   Your point is?

They tried to deploy it, and found it useless. Ken Olsen was speaking of a
market that didn't yet exist.

> > 5) It doesn't reduce spam. Spammers are not outsiders. It
> > fails to violate Shannon's theorem.
>
> You keep repeating your dubious reference to Shannon's observation about
> disproof of a covert channel.  Nice try, but it is largely irrelevant.

It certainly explains the failure of SMTP AUTH, and it makes perfect sense
once you cut through the false claims made by antispammers that somehow
spammers are outsiders who are let in.

> That theorem is the information
> theory version of the observation in traditional logic that one
> can't prove a universal negative and a relative of Goedel's work
> on the limits of set theory and mathematical logic systems.

Nice try, but wrong.

> All three are nicely proveable, but our day-to-day world is more
> empirical and statistical: no one I know of is asking for a proof that
> there are no covert channels out there or that all spam can be stopped.

That's not way people were saying in 1998. And just recently, it was
suggested that if SMTP were changed that spam could be stopped. Nice try
at changing the goal, after it is clear you can't obtain the original
goal.

> Most of us would be quite happy to just not see any of it in a given
> month.  And you are wasting time -- yours and everyone else's.  I
> suppose that, since you value that time at zero (based on your claims
> about the cost of spam) that is ok from your perspective.  But you are,
> I suspect, being rapidly added to a lot of filters.
>
> > 6) about a thousand other mail clients don't support it, and
> > have no plans to.
>
> So?  Either their users don't need it, or they are headed for
> failure in whatever marketplace in which they exist.  That is
> how both standards and products play themselves out.

They comply with standards. The other 15 don't. But yes, that is how
standards (or lack thereof) play themselves out.


> >> I was a big fan of open relays a decade ago, but am no longer
> >> convinced that they are the required solution to any problem
> >> we need to solve.
>
> > There were no "open relays" a decade ago. There were
> > "anonymous relays" back then. This "anonymous relay" problem
> > had nothing to do with SMTP, but was a problem with reverse
> > DNS, and lack of a numeric IP address in the Received: header.
>
> Thank you for the lecture on SMTP and its predecessors, whose
> operation and history you obviously know more about than I do.

You are welcome.

> Traditionally --although obviously not in the circles in which
> you travel-- the term "open relay" has been used to describe an
> SMTP server that would accept traffic for relaying from any
> source, without attempting to either authenticate that source or
> apply authorization rules to it.  That has a great deal to do
> with the way SMTP works in relay mode, and nothing at all to do
> with either reverse DNS or issues about what information is, or
> is not, copied into Received headers.

That is true. The term "Anonymous Relay" is used to distinguish lack of
authentication from lack of identification.

> > This problem was been fixed around 1993.. It is not possible
> > to send anonymous email through an open relay. (you still hear
> > this from radical antispammers, though).
>
> If sufficient logging information is maintained, it is not
> possible to send mail through a relay (open or not) without
> identifying the IP address of the sender (that statement was
> true before and after the changes you identify as "around
> 1993").  Getting from that IP address to identification of the
> individual sender --which is what you presumably mean by "not
> anonymous"-- is more or less difficult and more or less
> expensive, depending on a number of other circumstances.   In
> some cases --and, again, if one believes that people's time has
> any value-- the practical costs of identifying an individual far
> exceed any possible value in doing so.  In some others, it may
> be nearly impossible.   For example, there is a well-known Asian
> country in which most of the dialup services appear to be
> freenets, with widely-available dialup numbers and passwords
> shared among, I believe, literally millions of people.  The mail
> relays on those systems have no way to determine which user is
> originating a piece of mail, the user's IP address is of no
> help, and a system receiving mail from one of those relays can
> only identify the relay host.  That is a pretty good
> approximation to anonymity in my book.

This is just nonsense.  Obviously, you have no operational experience.

>
> >> And, no, I don't believe that either of the measures above
> >> will significantly reduce the volume of spam.
> >
> > Then why bother at all?
>
> First, because I was trying to respond factually to a message
> thread that appeared to assert that the only way to obtain
> certain classes of service was to have open relays.  My note was
> written simply to refute that claim.
>
> Second, because, where it is possible and doesn't cause other
> problems, having sufficient authentication that mail servers can
> be held responsible for traffic originating on them or relayed
> through them may have technical and social advantages
> independent of their relationship to spam (and your observations
> about "anonymous relays", as discussed above, just don't hold
> water).
>
> And finally, believing that a particular technique will not be
> especially effective --in statistical or absolute terms--
> against some behavior I don't approve of does not give me the
> obligation to make things any easier for the offender.

You misunderstood. I mean, why jump through hoops that won't get anywhere
towards the goal?  Perhaps we can stand out in the rain and cry, and spam
will stop. You can do that, but I'm not going to.





From owner-ietf@ietf.org  Wed May 28 00:26:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19627
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 00:26:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ks7D-0005vr-Sn
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 00:00:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KrkM-0004Yb-PL
	for ietf@asgard.ietf.org; Tue, 27 May 2003 23:37:02 -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 XAA17701
	for <ietf@ietf.org>; Tue, 27 May 2003 23:36:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Krio-0005cU-00
	for ietf@ietf.org; Tue, 27 May 2003 23:35:26 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Krin-0005c2-00
	for ietf@ietf.org; Tue, 27 May 2003 23:35:25 -0400
Content-class: urn:content-classes:message
Subject: RE: spam
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Tue, 27 May 2003 20:36:52 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F835@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: spam
Thread-Index: AcMkv65PC6Cm91N5TbOFJr7qXEJN9wACPqBg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Paul Vixie" <vixie@vix.com>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id AAA19627

Paul,

>> Given what you wrote just above (which I agree with), what is
>> your assessment that a system such as what you have in mind
>> would successfully reach IETF consensus?

> Paul Vixie wrote:
> one developed outside ietf.

I have myself some experience in this domain, but I will get back to you
privately about it.


> well, it's hard to commit acts of leadership inside a burning
> movie theatre. (pass me another marshmellow, will you?)

Popcorn OK?

Michel.




From owner-ietf@ietf.org  Wed May 28 00:39:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19993
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 00:39:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KsUS-0006se-1D
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 00:24:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ks9b-0005zb-8X
	for ietf@asgard.ietf.org; Wed, 28 May 2003 00:03:07 -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 AAA18473
	for <ietf@ietf.org>; Wed, 28 May 2003 00:03:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ks82-0005pL-00
	for ietf@ietf.org; Wed, 28 May 2003 00:01:30 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ks81-0005oy-00
	for ietf@ietf.org; Wed, 28 May 2003 00:01:29 -0400
Content-class: urn:content-classes:message
Subject: RE: A modest proposal (was: Re: spam)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Tue, 27 May 2003 21:02:56 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F836@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: A modest proposal (was: Re: spam)
Thread-Index: AcMkxjXfe/8qVK1+SAGzjZtN/aDzIwABaHIw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: <pdeutsch@earthlink.net>
Cc: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id AAA19993

Peter,

[I like Peter even more after he's had a beer]

> Peter Deutsch wrote:
> You probably know this already, but for those who don't, Brad
> Templeton proposed this scheme a while ago, based upon am
> micropayments model and called it "estamps". See:
> http://www.templetons.com/brad/spam/estamps.html

In a nutshell it's what I proposed yesterday because I still think it's
a good idea.

> He's since repudiated the idea,

I would be interested to know his POV recently. We are getting into an
unprecedented situation; if I compare to junk fax volume (close to zero
AFAIC) and to paper junk mail volume (one useless catalog a day on
average plus 50 pages of el-cheapo printed stuff) the current situation
is that my postman would have to carry 20 pounds of junk if he was
carrying my junk email in printed form. And it's climbing.

Although junk email does not kill nearly as many trees as paper junk
does, it does not make it acceptable.

Three months ago, I thrashed my mortgage bill along with the paper junk
mail [long story, you don't want to know]. Fat fingers sorting it out.

What would subscribers of this ML do if they had to sort out their
legitimate paper mail out of 50 pounds of junk?

Michel.




From owner-ietf@ietf.org  Wed May 28 00:42:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20228
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 00:42:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ksej-000188-HX
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 00:35:17 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KsLW-0006co-99
	for ietf@asgard.ietf.org; Wed, 28 May 2003 00:15:26 -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 AAA18741
	for <ietf@ietf.org>; Wed, 28 May 2003 00:15:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KsJx-0005uH-00
	for ietf@ietf.org; Wed, 28 May 2003 00:13:49 -0400
Received: from pcp796808pcs.nrockv01.md.comcast.net ([68.48.97.27] helo=emperor.nrockv01.md.comcast.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KsJw-0005sf-00
	for ietf@ietf.org; Wed, 28 May 2003 00:13:48 -0400
Received: (from jfb@localhost)
	by emperor.nrockv01.md.comcast.net (8.11.6/8.11.6) id h4S4Eqe30398
	for ietf@ietf.org; Wed, 28 May 2003 00:14:52 -0400
Message-ID: <XFMail.20030528001451.jfbauer@comcast.net>
X-Mailer: XFMail 1.4.4 on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <04c201c324af$22303fd0$0a00000a@atkielski.com>
Date: Wed, 28 May 2003 00:14:51 -0400 (EDT)
Reply-To: Jim Bauer <jfbauer@comcast.net>
From: Jim Bauer <jfbauer@comcast.net>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
Content-Transfer-Encoding: 8bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit


On 28-May-2003 Anthony Atkielski wrote:
> Tony writes:
> 
>> I was not AOL bashing, because they are not the
>> only ones doing this.
> 
> CS.COM and NETSCAPE.NET are doing it, but they are part of AOL.  I suppose
> others are doing it.

Add Earthlink to the list.

If a phone company acted like some of these ISP, we would
have situtations like Verizon blocking all incoming calls
from phones in Ohio.





From owner-ietf@ietf.org  Wed May 28 00:47:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20409
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 00:47:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ksej-000192-VT
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 00:35:17 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KsNe-0006fE-FF
	for ietf@asgard.ietf.org; Wed, 28 May 2003 00:17:38 -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 AAA18844
	for <ietf@ietf.org>; Wed, 28 May 2003 00:17:34 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KsM5-0005vm-00
	for ietf@ietf.org; Wed, 28 May 2003 00:16:01 -0400
Received: from h80ad26af.async.vt.edu ([128.173.38.175] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KsM4-0005vj-00
	for ietf@ietf.org; Wed, 28 May 2003 00:16:00 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h4S4HUN6004619;
	Wed, 28 May 2003 00:17:30 -0400
Message-Id: <200305280417.h4S4HUN6004619@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Re: spam 
In-Reply-To: Your message of "Tue, 27 May 2003 22:48:51 EDT."
             <Pine.LNX.4.44.0305272240360.8489-100000@commander.av8.net> 
References: <Pine.LNX.4.44.0305272240360.8489-100000@commander.av8.net>
X-Spoiler-Warning: crey -r 'sbe (1..100) {cevag "V jvyy abg srrq gur gebyyf\a"}'
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_877139473P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 28 May 2003 00:17:29 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_877139473P
Content-Type: text/plain; charset=us-ascii

On Tue, 27 May 2003 22:48:51 EDT, Dean Anderson said:

> I've pointed out the spam is a covert channel, with regard to Shannons
> theorem.

If the percentage of mail that was spam was low enough that it was in
fact a "covert" channel, we could all declare victory and go home.

What Shannon proved was that you can always get *SOME* covert information
out "under the radar".  You can't stop 100% of it.

Of course, you've totally blown the most basic point about covert channels -
they are by definition between two *cooperating* parties getting information
past a security boundary.  So for instance, Shannon proves that you can do
things like use steganography or differential timing to encode 200 bytes of
covert info into a 10K message, for a 2% bandwidth channel.

What that *doesnt* do is imply that if I as a spammer send 10K of innocuous
text to you, that you will miraculously spot the 200 bytes of steganographic
spam *WITHOUT LOOKING FOR IT*. Hmm.. this message text is about 1.5K already,
plenty of room for me to have concealed a very clear but hidden message.

And remember - what Shannon was *really* saying was that *somebody* *will*
understand the previous paragraph, even if most of the IETF readership
is collectively scratching their heads.  If you don't understand THIS paragraph
you don't understand Shannon's work on covert channels.


--==_Exmh_877139473P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+1DhZcC3lWbTT17ARAsolAKCdmF8Rb/DctY6Z4Ph7Pbu79+t4VwCfSx+n
e34yEnnZpsWWX40LbEKZIkI=
=fW1G
-----END PGP SIGNATURE-----

--==_Exmh_877139473P--



From owner-ietf@ietf.org  Wed May 28 01:02:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20725
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 01:02:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KssO-0002fA-Dy
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 00:49:24 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ksft-0001Eo-Ct
	for ietf@asgard.ietf.org; Wed, 28 May 2003 00:36:29 -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 AAA19866
	for <ietf@ietf.org>; Wed, 28 May 2003 00:36:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KseK-00062G-00
	for ietf@ietf.org; Wed, 28 May 2003 00:34:52 -0400
Received: from tomts19.bellnexxia.net ([209.226.175.73] helo=tomts19-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KseK-00062D-00
	for ietf@ietf.org; Wed, 28 May 2003 00:34:52 -0400
Received: from yahoo.com ([65.93.184.195]) by tomts19-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030528043625.OBQX12935.tomts19-srv.bellnexxia.net@yahoo.com>;
          Wed, 28 May 2003 00:36:25 -0400
Date: Wed, 28 May 2003 00:36:18 -0400
Subject: Re: requiring payment (was spam)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <200305280051.h4S0pJoc005872@ginger.lcs.mit.edu>
Message-Id: <ECFCCB00-90C5-11D7-97AB-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Tuesday, May 27, 2003, at 08:51  PM, J. Noel Chiappa wrote:

> Which is precisely why I say that the solution to spam is to charge for
> email. It avoids the whole question of defining what is and is not 
> spam.
>
> More specifically, change the email protocol so that when email 
> arrives from
> an entity which is not on the "email from these entities is free" 
> list, the
> email is rejected unless is accompanied by a payment for $X (where X 
> is set
> by a knob on the machine).

This would be unfortunate for people who do not have a lot of money. 
Even if the payment were miniscule, 0.01$ or whatever, the payment 
system might require a bank account, or a credit card, etc., to 
participate in. That would effectively block out a substantial 
percentage of the earth's population, people who use community centres, 
libraries, schools, etc. for free access or internet cafes for cheap 
occasional access.

simon

--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Wed May 28 01:03:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20837
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 01:03:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kt1j-0002yF-6c
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 00:59:03 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kspn-0002FO-AB
	for ietf@asgard.ietf.org; Wed, 28 May 2003 00:46:43 -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 AAA20378
	for <ietf@ietf.org>; Wed, 28 May 2003 00:46:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KsoE-00069y-00
	for ietf@ietf.org; Wed, 28 May 2003 00:45:06 -0400
Received: from 75.5.33.65.cfl.rr.com ([65.33.5.75] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KsoE-00069v-00
	for ietf@ietf.org; Wed, 28 May 2003 00:45:06 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19KYol-0006H5-00; Tue, 27 May 2003 03:24:19 -0400
Date: Tue, 27 May 2003 03:24:19 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Dean Anderson <dean@av8.com>
cc: Valdis.Kletnieks@vt.edu, <ietf@ietf.org>
Subject: Re: spam 
In-Reply-To: <Pine.LNX.4.44.0305272303490.8489-100000@commander.av8.net>
Message-ID: <Pine.LNX.4.44.0305270321150.23359-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Dean,

On Tue, 27 May 2003, Dean Anderson wrote:
>
> The radicals just don't get what they are up against.  Every letter you
> send actually subsidizes the cost of a junk mailer, who gets a discount to
> send junk mail.  All you get is the ability to be put on a "do not send"
> list maintained by the post office.  But you don't get to not subsidize
> junk postal mail.

I'm not sure the establishment knows what they are up against?  A
generation of young people with knowledge and personal power beyond the
wildest hopes of our ancestors, unity in action, and nothing to lose.  And
i do get to not subsideize it.  I simply refuse to use their service.  It
is ecologically unfriendly, and a amjor annoyance.  Market economy at its
best.

Scott




From owner-ietf@ietf.org  Wed May 28 01:18:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21233
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 01:18:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kt3c-00035k-2Y
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 01:01:00 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KsvE-0002pr-95
	for ietf@asgard.ietf.org; Wed, 28 May 2003 00:52:20 -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 AAA20540
	for <ietf@ietf.org>; Wed, 28 May 2003 00:52:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kstf-0006D1-00
	for ietf@ietf.org; Wed, 28 May 2003 00:50:43 -0400
Received: from 75.5.33.65.cfl.rr.com ([65.33.5.75] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kste-0006Cy-00
	for ietf@ietf.org; Wed, 28 May 2003 00:50:43 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19KYts-0006HC-00; Tue, 27 May 2003 03:29:36 -0400
Date: Tue, 27 May 2003 03:29:35 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Michel Py <michel@arneill-py.sacramento.ca.us>
cc: Paul Vixie <vixie@vix.com>, <ietf@ietf.org>
Subject: RE: spam
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F835@server2000.arneill-py.sacramento.ca.us>
Message-ID: <Pine.LNX.4.44.0305270328520.23359-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

> > well, it's hard to commit acts of leadership inside a burning
> > movie theatre. (pass me another marshmellow, will you?)
>
> Popcorn OK?

This is the way the world ends,
This is the way te world ends,
This is the way the world ends,
not with a bang, but a whimper.



>
> Michel.
>
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81




From owner-ietf@ietf.org  Wed May 28 02:28:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15515
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 02:28:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ku8w-0000mX-0V
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 02:10:34 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ku2o-0007R5-FX
	for ietf@asgard.ietf.org; Wed, 28 May 2003 02:04:14 -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 CAA26693
	for <ietf@ietf.org>; Wed, 28 May 2003 02:04:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ku1F-0006fi-00
	for ietf@ietf.org; Wed, 28 May 2003 02:02:37 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ku1E-0006ff-00
	for ietf@ietf.org; Wed, 28 May 2003 02:02:36 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 208077; Wed, 28 May 2003 01:03:35 -0500
Message-ID: <3ED45154.6050308@ehsco.com>
Date: Wed, 28 May 2003 01:04:04 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: John Stracke <jstracke@centive.com>, ietf@ietf.org
Subject: Re: spam
References: <Pine.LNX.4.44.0305272043280.8489-100000@commander.av8.net>
In-Reply-To: <Pine.LNX.4.44.0305272043280.8489-100000@commander.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/27/2003 8:04 PM Dean Anderson wrote:

<more waffling snipped>

>> In both of these examples, the verbiage present in the TCPA is
>> equally applicable to the problem of spam. Your continued waffling on
>> minor, irrelevant, non-contributory details and detours does not
>> change that.
> 
> No, it isn't, despite your continued assertions.  You have failed to 
> present a case that spam costs any money, or interferes with any
> reaonable person's email.

You still don't seem to understand the nature of proof, arguing instead
that the existence of alternatives somehow disproves a matter of fact.
Again, whether or not you think that the proof is significant is a matter
of opinion, not a matter of proof.

Look, there were plenty of "alternatives" to the TCPA as well. Users could
have avoided the cost issues by keeping the fax powered off, and could
have avoided the availability issues by ensuring they had plenty of
supplies or by using a second machine. But rather than saying "lump it and
use a workaround", congress passed a law which recognized and addressed
the violative nature of the canonical problem itself. This is perfectly
demonstrated by the fact that the law affords protection *even to those
people who never had any problems with junk faxes at all*. And this law
has been upheld as constitutionally valid in circuit courts, despite your
equivocating and factually erroneous claims to the contrary.

For those same reasons -- and using the same kind of proof -- a legal ban
on email spam is a demonstrably reasonabe pursuit. There is "proof" of
cost-reversal with email spam at the same cost levels as fax spam
(measured-rate), and there is "proof" of interference with usefulness at
the same levels as fax spam (full mailboxes), even without getting into
the testimony presented to congress in various hearings, and certainly
without exposing ourselves to the common sense that the first amendment
test allows for. Your "alternatives" such as ~don't use PacBell ISDN and
~don't use Hotmail are not only facile waffling, they are also irrelevant
in the face of the proof. Unless you can disprove the proof -- showing
that *NO* communication services charges by the byte or minute, and that
*NO* free mailbox service is filled with spam -- then the proof stands.
Until then, the only part of this that can be debated is whether or not
the proof contributes to the testimony and the common sense towards the
purpose of extending the TCPA. Feel free to claim that it doesn't, nobody
will be surprised.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Wed May 28 04:12:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20577
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 04:12:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kvoc-0005wI-BT
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 03:57:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kvfz-0005mr-5L
	for ietf@asgard.ietf.org; Wed, 28 May 2003 03:48:47 -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 DAA20037
	for <ietf@ietf.org>; Wed, 28 May 2003 03:48:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KveQ-0007Px-00
	for ietf@ietf.org; Wed, 28 May 2003 03:47:10 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KveP-0007Pu-00
	for ietf@ietf.org; Wed, 28 May 2003 03:47:09 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4S7mijh020926
	for <ietf@ietf.org>; Wed, 28 May 2003 09:48:44 +0200 (CEST)
Message-ID: <050701c324ed$906da620$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.44.0305271831130.8489-100000@commander.av8.net> <3ED400A2.706@ehsco.com>
Subject: Re: spam
Date: Wed, 28 May 2003 09:48:44 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric writes:

> Your response to this point was, and I quote
> here: "Don't get email on measured rate services,
> then." which is a limp way of saying that spam
> costs people with these links too much money for
> them to use email.

The ability to receive e-mail is not a Constitutional right.  Some types of
links and connections may make it impractical.  The lower the bandwidth or
the higher the cost of a communications link, the fewer the purposes to
which it can be justifiably or practically put.





From owner-ietf@ietf.org  Wed May 28 04:12:48 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20655
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 04:12:48 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kvub-00067X-1c
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 04:03:53 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kvmm-0005tk-Gj
	for ietf@asgard.ietf.org; Wed, 28 May 2003 03:55:48 -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 DAA20119
	for <ietf@ietf.org>; Wed, 28 May 2003 03:55:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KvlD-0007Rl-00
	for ietf@ietf.org; Wed, 28 May 2003 03:54:11 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KvlC-0007Ri-00
	for ietf@ietf.org; Wed, 28 May 2003 03:54:10 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4S7tjjh020987
	for <ietf@ietf.org>; Wed, 28 May 2003 09:55:45 +0200 (CEST)
Message-ID: <054c01c324ee$8b2e4e70$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <XFMail.20030528001451.jfbauer@comcast.net>
Subject: Re: The utilitiy of IP is at stake here
Date: Wed, 28 May 2003 09:55:45 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Jim writes:

> Add Earthlink to the list.

Thus far I've had no trouble sending e-mail to Earthlink.

> If a phone company acted like some of these
> ISP, we would have situtations like Verizon
> blocking all incoming calls from phones in Ohio.

Don't give them any ideas.

In the future, it may become more and more difficult to find ISPs that
provide truly unrestrained two-way access to the Internet.




From owner-ietf@ietf.org  Wed May 28 04:18:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20930
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 04:18:28 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Kw0y-0006Qz-6h
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 04:10:28 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kvsl-0005y5-Ed
	for ietf@asgard.ietf.org; Wed, 28 May 2003 04:01:59 -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 EAA20325
	for <ietf@ietf.org>; Wed, 28 May 2003 04:01:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KvrC-0007TX-00
	for ietf@ietf.org; Wed, 28 May 2003 04:00:22 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KvrB-0007TU-00
	for ietf@ietf.org; Wed, 28 May 2003 04:00:21 -0400
Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1])
	by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id JAA09479
	for <ietf@ietf.org>; Wed, 28 May 2003 09:01:56 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by pigeon.ecs.soton.ac.uk (8.9.3p2/8.9.3) with ESMTP id JAA11484
	for <ietf@ietf.org>; Wed, 28 May 2003 09:01:56 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id h4S81uu01140
	for ietf@ietf.org; Wed, 28 May 2003 09:01:56 +0100
Date: Wed, 28 May 2003 09:01:55 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Re: spam - The IETF list is spam!
Message-ID: <20030528080155.GB990@login.ecs.soton.ac.uk>
References: <Pine.LNX.4.44.0305272043280.8489-100000@commander.av8.net> <3ED45154.6050308@ehsco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3ED45154.6050308@ehsco.com>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, May 28, 2003 at 01:04:04AM -0500, Eric A. Hall wrote:
> 
> on 5/27/2003 8:04 PM Dean Anderson wrote:
> 
> <more waffling snipped>

So now I get 4x as much spam from the IETF list as all other sources :)

Can the discussion now retire to the IRTF anti-spam list?  There seems to
be a constant troll factor keeping the topic running beyond its natural 
course...?

Tim



From owner-ietf@ietf.org  Wed May 28 04:49:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21462
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 04:49:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19KwUf-00082P-LA
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 04:41:09 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KwNY-0007tz-Qw
	for ietf@asgard.ietf.org; Wed, 28 May 2003 04:33:48 -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 EAA21220
	for <ietf@ietf.org>; Wed, 28 May 2003 04:33:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KwLz-0007ja-00
	for ietf@ietf.org; Wed, 28 May 2003 04:32:11 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KwLz-0007jX-00
	for ietf@ietf.org; Wed, 28 May 2003 04:32:11 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4S8Xkjh021334
	for <ietf@ietf.org>; Wed, 28 May 2003 10:33:46 +0200 (CEST)
Message-ID: <05af01c324f3$dafa3770$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.44.0305272043280.8489-100000@commander.av8.net> <3ED45154.6050308@ehsco.com> <20030528080155.GB990@login.ecs.soton.ac.uk>
Subject: Re: spam - The IETF list is spam!
Date: Wed, 28 May 2003 10:33:46 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tim writes:

> Can the discussion now retire to the IRTF
> anti-spam list?

Does your computer have a Delete key?



From owner-ietf@ietf.org  Wed May 28 10:17:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05174
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 10:17:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L1FC-0008Fr-4E
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 09:45:30 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Kp5q-0000CY-0U
	for ietf@asgard.ietf.org; Tue, 27 May 2003 20:47:02 -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 UAA11986
	for <ietf@ietf.org>; Tue, 27 May 2003 20:46:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kp4H-0003zI-00
	for ietf@ietf.org; Tue, 27 May 2003 20:45:25 -0400
Received: from smtp-out.comcast.net ([24.153.64.116])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kp4G-0003zA-00
	for ietf@ietf.org; Tue, 27 May 2003 20:45:25 -0400
Received: from max.hunnysoft.pri
 (pcp01719983pcs.nrockv01.md.comcast.net [68.50.252.119])
 by mtaout01.icomcast.net
 (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003))
 with ESMTP id <0HFK0024GNH0A3@mtaout01.icomcast.net> for ietf@ietf.org; Tue,
 27 May 2003 20:46:12 -0400 (EDT)
Received: from [192.168.2.5] (helo=hunnysoft.com)	by max.hunnysoft.pri with
 esmtp (Exim 3.36 #2)	id 19Kp2O-0000FD-00	for ietf@ietf.org; Tue,
 27 May 2003 20:43:28 -0400
Date: Tue, 27 May 2003 20:46:50 -0400
From: Doug Sauder <dws+001@hunnysoft.com>
Subject: What the IETF should do: Amend RFC 2822  (was: Re: spam)
To: ietf@ietf.org
Message-id: <3ED406FA.5060004@hunnysoft.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1)
 Gecko/20020826
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

Pardon me if I jump in here and change the direction of this discussion to 
something more relevant.

What the IETF should do: Amend RFC 2822 to change the definition of an
email address in a way that is entirely backward compatible, yet supports
aliases.  I propose a change like the following: (pardon the ambiguity)

addr-spec       =       local-part [ "+" password ] "@" domain

local-part      =       dot-atom / quoted-string / obs-local-part

password        =       atom

domain          =       dot-atom / domain-literal / obs-domain

domain-literal  =       [CFWS] "[" *([FWS] dcontent) [FWS] "]" [CFWS]

dcontent        =       dtext / quoted-pair

dtext           =       NO-WS-CTL /     ; Non white space controls

                         %d33-90 /       ; The rest of the US-ASCII
                         %d94-126        ;  characters not including "[",
                                         ;  "]", or "\"

First of all, realize that there are already implementations deployed that
recognize email aliases -- "plus aliases" in particular.

Second, there are implementations that recognize aliases, but in
incompatible ways.  (Sendmail and Exim recognize a "+" sign.  Qmail
recognizes a '-' sign.  There are still others.)  Therefore, it is
incumbent on the IETF to update the standard for an email address so that
implementations can interoperate.  There are also new products that depend
on a plus-alias-like mechanism to create useful filters.  Without
standarization, there is the real possibility of products that don't
interoperate.

Third, this definition is entirely backward compatible, so it has
absolutely no impact on existing (correct) implementations.

Fourth, with a standard for aliases, new products can be created, and
perhaps used in creative ways to block spam.  Without a standard, new
products will be created, but they will not interoperate.  I could envision
mainstream products being modified to support plus aliases in a way that
makes it easy for unsophisticated users to use them.  But that won't happen
if there is no chance for interoperability.

Fifth, plus aliases have an impact on the S/MIME standard.  I would like to
get one personal ID certificate and use it with many aliases.  That won't
happen if aliases are not recognized by a change in the standard.  Software
that checks the identity of the sender SHOULD remove the extra "password"
part when comparing the sender address to the email address in the
certificate.  That would provide the same assurance of the sender's
authenticity, while allowing the sender to create a family of related
aliases.  The way to think about this is, the local-part and the domain
establish identity, while the "password" is used only in delivery.  If you
think S/MIME is already difficult to use, imagine needing a different
certificate for each alias you use.

How this impacts spam:

I have talked to many individuals about the use of "plus aliases."  Most
responses I get fall into two categories: (1) some have never been aware of
plus aliases, and (2) some are aware of them but think they are too
complicated for average users.  On the last point, I am not sure I agree
entirely.  Yes, they are too complicated as things are now.  But good
software designers are able to make complicated things simple.  (There are
already software products that try to make the use of aliases entirely
transparent.)

I think we could explain to unsophisticated users that the extra part in
their email address, if they choose to use it, is a "password" that keeps
junk out of their inbox.  They will understand that.  We can also explain
to them that if their email account is overrun with spam, they don't have
to change ISPs to get a new email address.  They can just change their
password.  And, I think that the popular email client applications could be
changed to make it very easy to use different aliases.  I'm not a user
interface expert, but I don't see why something as simple as
password-protecting a folder in your inbox should be complicated.  One
thing I do know, is that there are many unsophisticated users who feel
almost helpless against the onslaught of spam.  Some are driven to change
ISPs.  I think many would welcome the opportunity to password-protect a
folder in their inbox, and give out the "password" to only close relatives
and friends.

Using plus aliases is purely optional.  Users who want things simple
continue life as before -- not using plus aliases.  Users who choose to
receive a limited amount of email on their cell phone or PDA can use an
alias that they give out to only a handful of people.

The IETF is an organization that creates standards.  I believe we need a
standard for email aliases -- using a plus sign or whatever.  With almost
no impact on existing infrastructure, we can give creative anti-spam
engineers a new tool to use, and I am eager to see how such a tool might be
used.  But regardless of what one might think of the potential to control
spam through the use of aliases, creating a standard for aliases is work
the IETF should take on.

-- 
Doug Sauder
Hunny Software, Inc






From owner-ietf@ietf.org  Wed May 28 10:17:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05171
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 10:17:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L1FB-0008Dk-Eh
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 09:45:29 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KlZZ-0000dm-TR
	for ietf@asgard.ietf.org; Tue, 27 May 2003 17:01:29 -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 RAA02345
	for <ietf@ietf.org>; Tue, 27 May 2003 17:01:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19KlY1-0001V5-00
	for ietf@ietf.org; Tue, 27 May 2003 16:59:53 -0400
Received: from fmr04.intel.com ([143.183.121.6] helo=caduceus.sc.intel.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19KlY0-0001Uc-00
	for ietf@ietf.org; Tue, 27 May 2003 16:59:53 -0400
Received: from petasus.sc.intel.com (petasus.sc.intel.com [10.3.253.4])
	by caduceus.sc.intel.com (8.11.6p2/8.11.6/d: outer.mc,v 1.66 2003/05/22 21:17:36 rfjohns1 Exp $) with ESMTP id h4RKxkL08999
	for <ietf@ietf.org>; Tue, 27 May 2003 20:59:46 GMT
Received: from fmsmsxvs042.fm.intel.com (fmsmsxvs042.fm.intel.com [132.233.42.128])
	by petasus.sc.intel.com (8.11.6p2/8.11.6/d: inner.mc,v 1.35 2003/05/22 21:18:01 rfjohns1 Exp $) with SMTP id h4RKxgI15550
	for <ietf@ietf.org>; Tue, 27 May 2003 20:59:42 GMT
Received: from fmsmsx29.FM.INTEL.COM ([132.233.42.29])
 by fmsmsxvs042.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2003052714050217060
 ; Tue, 27 May 2003 14:05:02 -0700
Received: by fmsmsx29.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <L2PM3BLY>; Tue, 27 May 2003 14:00:55 -0700
Message-ID: <A46BBDB345A7D5118EC90002A5072C7806BEB75E@orsmsx116.jf.intel.com>
From: "Sabharwal, Atul" <atul.sabharwal@intel.com>
To: "'Anthony Atkielski'" <anthony@atkielski.com>,
        IETF Discussion
	 <ietf@ietf.org>
Subject: RE: spam
Date: Tue, 27 May 2003 14:00:54 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

Now to add the mess of spam which we all are doing... NO SPAM.
PLEASE...  It has been a unsolvable problem so far... Just like
Lots of social problems we have e.g. poverty...

Regulation/Discipline rather than technology can solve this one 
as when the Punishment for spamming is bigger than the profit, 
we solve the Problem.  On technology front, all we can do is 
make spamming difficult or filter the spam content better
e.g check for spam on mail servers on transmit, forwarding, 
redirection, receive.  Client level filters would not work.  These
all fall in the area of regulating general purpose Internet content
regulation.  Spam is just misuse of this content.  There are so many
other Internet scams we have.

In short, this should belong in some general purpose Internet Security
Forum discussions.

--
Atul

P.S: These are my personal opinions.

-----Original Message-----
From: Anthony Atkielski [mailto:anthony@atkielski.com] 
Sent: Tuesday, May 27, 2003 1:23 PM
To: IETF Discussion
Subject: Re: spam

Paul writes:

> ... the problem isn't deterring spammers or even
> preventing abuse, but rather designing a new
> interpersonal batch communications system (ibcs?)
> which allows a receiving party to accept or reject
> inbound traffic with some kind of confidence in
> the identity of the sender, the intent of the relay or
> proxy, and the value (to the sender) of the reception.

Designing one is easy.  Getting a billion people around the world to all
implement the system, once designed, is very, very hard.

Additionally, nobody would be willing to accept a single design.  Someone
would claim patent infringement.  Different companies would want to turn it
into a money-making adventure, which would instantly make it unworkable for
most of the world.  Other companies would change the design slightly and
then try to force their own versions as the "true" standard, in order to
make commercial profits.  It would take forever to do.

Whatever the technical solution might be, I think it would have to be
something that requires only action at the receiving end, not the sending
end.  If you require action at both ends, you lock out 95% of the world's
Internet users at the push of a button.  It's like coming up with a solution
that requires everyone to upgrade to a new version of Windows with a certain
service pack.  It's not going to happen.

As always, be conservative in what you expect, and liberal in what you
accept.

> my own ideas have to do with trustbrokers ...

Trusted third parties are tempting, but that notion opens a tremendous can
of worms.  Personally, there isn't anyone I'd trust as a certification
authority even for strangers.  A PGP model is more tempting, but it would
require more sophistication on the part of users than can reasonably be
expected for 99% of the world's Internet citizens.  Indeed, any trustbroker
plan has this same problem.

Even if the certification is limited to mailers, you still have the above
problem, only with slightly reduced magnitude.

> we (the e-mail producing/consuming community) have
> the technology ...

We can rebuild it.  We can make it better.

Nah.  The Internet acquires more inertia with each passing day.  And the
more inertia it develops, the harder it is to implement any active technical
change (i.e., any change that requires actual modification of multiple
systems around the world).  Kind of like moving everyone to IPv6.

> what we lack, dear ietf, is simply: leadership.

No, we lack a genius who can come up with something that will work without
requiring a change on one billion computers around the world.  Preferably a
genius who won't file a patent on it, too.






From owner-ietf@ietf.org  Wed May 28 10:27:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05792
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 10:27:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L1FE-0008JF-63
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 09:45:32 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L0ej-0002Ck-Ud
	for ietf@asgard.ietf.org; Wed, 28 May 2003 09:07:49 -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 JAA01110
	for <ietf@ietf.org>; Wed, 28 May 2003 09:07:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L0dA-0002V3-00
	for ietf@ietf.org; Wed, 28 May 2003 09:06:12 -0400
Received: from carwash.centive.com ([65.220.90.249] helo=carwash.centivinc.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19L0d4-0002Sl-00
	for ietf@ietf.org; Wed, 28 May 2003 09:06:06 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003052809140424937
 for <ietf@ietf.org>; Wed, 28 May 2003 09:14:04 -0400
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 28 May 2003 09:04:44 -0400
Message-ID: <3ED4B3EC.8070206@centive.com>
Date: Wed, 28 May 2003 09:04:44 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: spam
References: <Pine.LNX.4.44.0305272303490.8489-100000@commander.av8.net>
In-Reply-To: <Pine.LNX.4.44.0305272303490.8489-100000@commander.av8.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 May 2003 13:04:44.0802 (UTC) FILETIME=[B59F1E20:01C32519]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dean Anderson wrote:

>We are lucky that spammers don't get a discount
>
Open relays give them a five-finger discount.

-- 
/===============================================================\
|John Stracke      |jstracke@centive.com                        |
|Principal Engineer|http://www.centive.com                      |
|Centive           |My opinions are my own.                     |
|===============================================================|
|"Power corrupts; Powerpoint corrupts absolutely." -- Vint Cerf |
\===============================================================/





From owner-ietf@ietf.org  Wed May 28 10:28:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05844
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 10:28:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L1FE-0008K5-QG
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 09:45:32 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L0g6-0002WS-6n
	for ietf@asgard.ietf.org; Wed, 28 May 2003 09:09:14 -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 JAA01225
	for <ietf@ietf.org>; Wed, 28 May 2003 09:09:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L0eW-0002Xl-00
	for ietf@ietf.org; Wed, 28 May 2003 09:07:36 -0400
Received: from smtp-out.comcast.net ([24.153.64.115])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L0eW-0002X0-00
	for ietf@ietf.org; Wed, 28 May 2003 09:07:36 -0400
Received: from mail.msen.com
 (pcp03303164pcs.ypwest01.mi.comcast.net [68.43.244.45])
 by mtaout02.icomcast.net
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with ESMTP id <0HFL002WZLRXQV@mtaout02.icomcast.net> for ietf@ietf.org; Wed,
 28 May 2003 09:07:11 -0400 (EDT)
Date: Wed, 28 May 2003 09:15:56 -0400
From: "Rebecca L. Page" <page@mail.msen.com>
Subject: Re: requiring payment (was spam)
To: S Woodside <sbwoodside@yahoo.com>
Cc: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, ietf@ietf.org
Reply-to: page@mail.msen.com
Message-id: <3ED4B68C.3050201@mail.msen.com>
Organization: Teris Consulting Group
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4.1)
 Gecko/20020314 Netscape6/6.2.2
References: <ECFCCB00-90C5-11D7-97AB-000393414368@yahoo.com>
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

I really find your solution to be appalling, especially when I look at 
your email address -> Yahoo! -> probably a free account.  I pay a 
premium price for a legitimate set of IPs and a space on a Server.  

The correct solution is to enforce masking techniques so we as users can 
screen our email, much like phone calls via caller ID, which also needs 
 work to prevent making a phone number.  

Charging the user is like the Internet Taxation Issue, it hurts one of 
the only semi viable markets in our deplorable economy.  Making the end 
user have restrictions and costs due to our inability to control  a 
problem internally, shows how quick we as a society are willing to hand 
over our rights to a group, such as Homeland Security of a commercial 
unit, so that we can  brush an issue under the rug!!   A good working 
solution requires understanding the issues,  architectural and 
conceptual design and development resulting from appropriate research, 
alpha/beta implementation, testing and cooperative implementation 
planning, as well as appropriate communication to users and training.

I thought IETF was founded on the idea of working through issues, not on 
being reactionary!

Rebecca L. Page
Teris Consulting Group
Saline, MI
734-944-1177
page@mail.msen.com




S Woodside wrote:

>
> On Tuesday, May 27, 2003, at 08:51  PM, J. Noel Chiappa wrote:
>
>> Which is precisely why I say that the solution to spam is to charge for
>> email. It avoids the whole question of defining what is and is not spam.
>>
>> More specifically, change the email protocol so that when email 
>> arrives from
>> an entity which is not on the "email from these entities is free" 
>> list, the
>> email is rejected unless is accompanied by a payment for $X (where X 
>> is set
>> by a knob on the machine).
>
>
> This would be unfortunate for people who do not have a lot of money. 
> Even if the payment were miniscule, 0.01$ or whatever, the payment 
> system might require a bank account, or a credit card, etc., to 
> participate in. That would effectively block out a substantial 
> percentage of the earth's population, people who use community 
> centres, libraries, schools, etc. for free access or internet cafes 
> for cheap occasional access.
>
> simon
>
> -- 
> www.simonwoodside.com -- 99% Devil, 1% Angel
>
>
>






From owner-ietf@ietf.org  Wed May 28 10:30:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06127
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 10:30:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L1FF-0008L2-EJ
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 09:45:33 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L0hf-000360-Tu
	for ietf@asgard.ietf.org; Wed, 28 May 2003 09:10:51 -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 JAA01347
	for <ietf@ietf.org>; Wed, 28 May 2003 09:10:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L0g6-0002aQ-00
	for ietf@ietf.org; Wed, 28 May 2003 09:09:14 -0400
Received: from carwash.centive.com ([65.220.90.249] helo=carwash.centivinc.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19L0g5-0002Yw-00
	for ietf@ietf.org; Wed, 28 May 2003 09:09:14 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003052809171710616
 for <ietf@ietf.org>; Wed, 28 May 2003 09:17:17 -0400
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 28 May 2003 09:07:58 -0400
Message-ID: <3ED4B4AE.5070207@centive.com>
Date: Wed, 28 May 2003 09:07:58 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: spam
References: <Pine.LNX.4.44.0305271926230.8489-100000@commander.av8.net>
In-Reply-To: <Pine.LNX.4.44.0305271926230.8489-100000@commander.av8.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 May 2003 13:07:58.0417 (UTC) FILETIME=[29066C10:01C3251A]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dean Anderson wrote:

>In fact, it is an
>axiom that crowds are always wrong.
>
I *suppose* that's a true statement--somebody somewhere (e.g., you) must 
be working with "crowds are always wrong" as an axiom.  But those of us 
who know what the word means understand that whether something is an 
axiom has nothing to do with whether it's true.

-- 
/===============================================================\
|John Stracke      |jstracke@centive.com                        |
|Principal Engineer|http://www.centive.com                      |
|Centive           |My opinions are my own.                     |
|===============================================================|
|"Power corrupts; Powerpoint corrupts absolutely." -- Vint Cerf |
\===============================================================/





From owner-ietf@ietf.org  Wed May 28 10:52:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06900
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 10:52:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L1y6-0001ML-PN
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 10:31:54 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L1aX-0004f6-IC
	for ietf@asgard.ietf.org; Wed, 28 May 2003 10:07:33 -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 KAA04161
	for <ietf@ietf.org>; Wed, 28 May 2003 10:07:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L1Yx-0003H6-00
	for ietf@ietf.org; Wed, 28 May 2003 10:05:55 -0400
Received: from [216.93.164.123] (helo=zak.ecotroph.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L1Yx-0003Gu-00
	for ietf@ietf.org; Wed, 28 May 2003 10:05:55 -0400
Received: from ecotroph.net (h87.s239.netsol.com [::ffff:216.168.239.87])
  (AUTH: LOGIN anewton)
  by zak.ecotroph.net with esmtp; Wed, 28 May 2003 10:07:05 -0400
Message-ID: <3ED4C675.8030407@ecotroph.net>
Date: Wed, 28 May 2003 10:23:49 -0400
From: Andrew Newton <anewton@ecotroph.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Anthony Atkielski <anthony@atkielski.com>
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: spam - The IETF list is spam!
References: <Pine.LNX.4.44.0305272043280.8489-100000@commander.av8.net> <3ED45154.6050308@ehsco.com> <20030528080155.GB990@login.ecs.soton.ac.uk> <05af01c324f3$dafa3770$0a00000a@atkielski.com>
In-Reply-To: <05af01c324f3$dafa3770$0a00000a@atkielski.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Anthony Atkielski wrote:
> Tim writes:
> 
> 
>>Can the discussion now retire to the IRTF
>>anti-spam list?
> 
> 
> Does your computer have a Delete key?

Look, you've solved the spam problem too!

-andy




From owner-ietf@ietf.org  Wed May 28 11:06:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05177
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 10:17:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L1FB-0008Fj-Va
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 09:45:29 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19KovK-00082B-Gx
	for ietf@asgard.ietf.org; Tue, 27 May 2003 20:36: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 UAA11514
	for <ietf@ietf.org>; Tue, 27 May 2003 20:36:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kotm-0003r5-00
	for ietf@ietf.org; Tue, 27 May 2003 20:34:34 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Kotl-0003qy-00
	for ietf@ietf.org; Tue, 27 May 2003 20:34:33 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h4S0a3tU005624;
	Tue, 27 May 2003 20:36:03 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h4S0a2fB005623;
	Tue, 27 May 2003 20:36:02 -0400
Date: Tue, 27 May 2003 20:36:02 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200305280036.h4S0a2fB005623@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: spam
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: Dean Anderson <dean@av8.com>

    > If the corporation (like hotmail) brings in less than $1 per month from
    > each user, pays all .. from this revenue, then quite clearly, there are
    > no hidden costs, as you assert.
    > Clearly, spam can not cost more than they bring in, in revenue, else
    > they would go out of business.
    > There are sites that offer email services (unsubsidized), for $1 - $2
    > per month. They also have no hidden costs, and no subsidies.

You appear to be deliberately obtuse.

The costs of spam, to the users, include not just the cost of the emailbox,
but also the costs to process the mail. This includes, principally, their time
- a component on which others (including you) are not capable of placing a
value.

If the only cost associated with spam was the cost of storing/forwarding the
email, I'll wager most people wouldn't care.


Anyway, this whole discussion is moot. I'm sure there is rough consensus in
the IETF that getting rid of spam is a good idea. (Maybe a question worthy of
a plenary hum to confirm this.)

The only question left is if there are any *technical* components to doing so
(which would be the IETF's preserve), and, if so, what they are.

	Noel





From owner-ietf@ietf.org  Wed May 28 12:32:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11101
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 12:32:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L3f6-00056P-B4
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 12:20:24 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L3cp-000546-HB
	for ietf@asgard.ietf.org; Wed, 28 May 2003 12:18:03 -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 MAA10641
	for <ietf@ietf.org>; Wed, 28 May 2003 12:18:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L3bF-0004qJ-00
	for ietf@ietf.org; Wed, 28 May 2003 12:16:25 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L3bF-0004qF-00
	for ietf@ietf.org; Wed, 28 May 2003 12:16:25 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h4SGJ1xS018516;
	Wed, 28 May 2003 18:19:01 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Wed, 28 May 2003 18:17:56 +0200
Subject: Re: spam
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <200305280036.h4S0a2fB005623@ginger.lcs.mit.edu>
Message-Id: <F114CBE4-9127-11D7-9944-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On woensdag, mei 28, 2003, at 02:36 Europe/Amsterdam, J. Noel Chiappa 
wrote:

> Anyway, this whole discussion is moot.

I couldn't agree more. The bottom line is that most people simply don't 
want to receive spam, often to the degree that they are willing to pay 
extra to get rid of it.

> I'm sure there is rough consensus in the IETF that getting rid of spam 
> is a good idea. (Maybe a question worthy of a plenary hum to confirm 
> this.)

> The only question left is if there are any *technical* components to 
> doing so
> (which would be the IETF's preserve), and, if so, what they are.

It surprises me that so many people are so eager to declare defeat 
before even trying the protocol route. (With current protocols defeat 
is pretty much inevitable.) If we adopt such an attitude in other areas 
as well, we would all refuse to have locks on our doors because they 
don't stop all burglars, and refuse to call the police when someone is 
assaulted on the street because the perpetrator may have a diplomatic 
passport.

The problem with spam isn't that legitimate business are legitimately 
advertising legitimate services. (Although even in those cases I never 
gave them my email address so even this type of spam isn't completely 
above board.) For that, filtering or unsubscribing should keep the 
problem within reasonable bounds. Without forgery it isn't all that 
simple to bypass filters and legitimate businesses lose more than they 
gain from trying to do so.

The problem is that we are subjected to all kinds of filth and scams, 
and the SMTP protocol is severely abused in the process in order to 
avoid filtering. And this is only going to get worse over time, as 
people get more adept at avoiding spam. Spammers then simply have to 
send out more messages and address even more perverse "demand" to make 
money. Going after them in the real world won't work for the same 
reason that the war against drugs doesn't work: limiting supply only 
increases profit for the remaining suppliers so it's more attractive 
than ever to enter the game. So if we can't get spam under control 
(which isn't the same as eliminating it) by doing something about 
supply or demand, we have to do it in the middle by giving users the 
means to blacklist spammers or whitelist legitimate correspondents and 
make it sufficiently hard to fake an identity to get around this.

I don't think moving to some kind of SMTPng is quite as impossible as 
people seem to think. Receiving wouldn't be a problem anyway because 
the new service would simply fall back to SMTP when delivering 
messages. Most service providers would be thrilled to switch to a near 
spam-free email service given the opportunity, so email between service 
providers wouldn't be the problem. Email between customers and their 
service providers wouldn't be a problem either: here regular SMTP can 
be used together with existing authentication mechanisms. So that 
leaves people running their own mail server: either they have to 
upgrade, or subscibe to an upgraded email service.

About the "charging for email" thing: this doesn't have to be actual 
money. Doing it with some kind of cryptographic token that is passed 
from sender to recipient should work just as well in making sure people 
can't send many orders of magnitude more email than they receive, and 
this wouldn't have many of the adverse effects of using money for this.

Mabye a BOF would be in order in Vienna?




From owner-ietf@ietf.org  Wed May 28 13:21:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12500
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 13:21:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L4Me-0005rJ-1F
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 13:05:24 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L4KS-0005p3-Pj
	for ietf@asgard.ietf.org; Wed, 28 May 2003 13:03:08 -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 NAA12042
	for <ietf@ietf.org>; Wed, 28 May 2003 13:03:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L4It-0005DL-00
	for ietf@ietf.org; Wed, 28 May 2003 13:01:31 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L4Is-0005DI-00
	for ietf@ietf.org; Wed, 28 May 2003 13:01:30 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S29644> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 28 May 2003 10:02:49 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: <ietf@ietf.org>
Subject: RE: spam
Date: Wed, 28 May 2003 10:02:41 -0700
Message-ID: <011901c3253a$f32e8930$56144104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <F114CBE4-9127-11D7-9944-00039388672E@muada.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA12500

Iljitsch van Beijnum wrote:
> ...
> About the "charging for email" thing: this doesn't have to be actual 
> money. Doing it with some kind of cryptographic token that is passed 
> from sender to recipient should work just as well in making 
> sure people 
> can't send many orders of magnitude more email than they receive, and 
> this wouldn't have many of the adverse effects of using money 
> for this.

Rather than passing a token, require the mail to be encrypted with the
public key of the recipient. This would do two things, make it expensive
to send mass random mailings, and provide an incentive for the ISPs to
actually deploy a PKI.

> 
> Mabye a BOF would be in order in Vienna?

A better idea than leaving the problem to languish as a research topic.

Tony





From owner-ietf@ietf.org  Wed May 28 13:44:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13172
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 13:44:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L4pf-0006YE-Qc
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 13:35:23 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L4l6-0006Vs-4m
	for ietf@asgard.ietf.org; Wed, 28 May 2003 13:30:40 -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 NAA12835
	for <ietf@ietf.org>; Wed, 28 May 2003 13:30:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L4jW-0005Qu-00
	for ietf@ietf.org; Wed, 28 May 2003 13:29:02 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L4jV-0005Qr-00
	for ietf@ietf.org; Wed, 28 May 2003 13:29:01 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h4SHUVk22051;
        Wed, 28 May 2003 13:30:35 -0400 (EDT)
Date: Wed, 28 May 2003 13:30:31 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: spam
Message-Id: <20030528133031.4a10f0f4.moore@cs.utk.edu>
In-Reply-To: <011901c3253a$f32e8930$56144104@eagleswings>
References: <F114CBE4-9127-11D7-9944-00039388672E@muada.com>
	<011901c3253a$f32e8930$56144104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > Mabye a BOF would be in order in Vienna?
> 
> A better idea than leaving the problem to languish as a research
> topic.

standard IETF operating procedure - start trying to engineer a solution
before the problem is understood.



From owner-ietf@ietf.org  Wed May 28 14:01:48 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13748
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 14:01:48 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L57E-000748-Sv
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 13:53:32 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L53I-0006yg-VW
	for ietf@asgard.ietf.org; Wed, 28 May 2003 13:49:29 -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 NAA13343
	for <ietf@ietf.org>; Wed, 28 May 2003 13:49:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L51j-0005YM-00
	for ietf@ietf.org; Wed, 28 May 2003 13:47:51 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L51i-0005Y5-00
	for ietf@ietf.org; Wed, 28 May 2003 13:47:50 -0400
Received: from localhost (dwm@localhost)
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h4SHgKb05197;
	Wed, 28 May 2003 10:42:20 -0700
Date: Wed, 28 May 2003 10:42:19 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: S Woodside <sbwoodside@yahoo.com>
cc: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, <ietf@ietf.org>
Subject: Re: requiring payment (was spam)
In-Reply-To: <ECFCCB00-90C5-11D7-97AB-000393414368@yahoo.com>
Message-ID: <Pine.LNX.4.33.0305281033360.865-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Simon,

The proposals haven't been to eliminate free email, only to provide an
alternative which folks can require be used to send them email if they
haven't established a free relationship with the sender.

In the USA today, it costs $.37 to send a physical mail. I don't think it
unreasonable for someone sending me mail to pay a similar fee and
conversely for me to pay such a fee for each of my posts to the IETF list,
even though I would expect the list to use a free channel to distribute
the result.

I don't believe there is any right to free mail or email service so I
don't see a reason to be overly concerned that a user of a community
computer can't send free email. In addition to the free email channel
which would have to continue to exist, providers of 'no charge' email
services such as the bottom end Yahoo service could offer some number of
free stamps per month combined with credits I suggested for receiveing
postage paid mail, folks with marginal economic situations should be able
to participate in email.

Dave Morris

On Wed, 28 May 2003, S Woodside wrote:

>
> On Tuesday, May 27, 2003, at 08:51  PM, J. Noel Chiappa wrote:
>
> > Which is precisely why I say that the solution to spam is to charge for
> > email. It avoids the whole question of defining what is and is not
> > spam.
> >
> > More specifically, change the email protocol so that when email
> > arrives from
> > an entity which is not on the "email from these entities is free"
> > list, the
> > email is rejected unless is accompanied by a payment for $X (where X
> > is set
> > by a knob on the machine).
>
> This would be unfortunate for people who do not have a lot of money.
> Even if the payment were miniscule, 0.01$ or whatever, the payment
> system might require a bank account, or a credit card, etc., to
> participate in. That would effectively block out a substantial
> percentage of the earth's population, people who use community centres,
> libraries, schools, etc. for free access or internet cafes for cheap
> occasional access.
>
> simon
>
> --
> www.simonwoodside.com -- 99% Devil, 1% Angel
>
>
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it, which is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on what to pass are made solely by Raffaele D'Albenzio.
>




From owner-ietf@ietf.org  Wed May 28 14:07:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14130
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 14:07:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L5Dr-0007A6-6m
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 14:00:23 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L5AW-00076o-Oe
	for ietf@asgard.ietf.org; Wed, 28 May 2003 13:56:56 -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 NAA13537
	for <ietf@ietf.org>; Wed, 28 May 2003 13:56:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L58w-0005b0-00
	for ietf@ietf.org; Wed, 28 May 2003 13:55:19 -0400
Received: from mail3.microsoft.com ([131.107.3.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L58w-0005ah-00
	for ietf@ietf.org; Wed, 28 May 2003 13:55:18 -0400
Received: from INET-VRS-03.redmond.corp.microsoft.com ([157.54.5.27]) by mail3.microsoft.com with Microsoft SMTPSVC(5.0.2195.6624);
	 Wed, 28 May 2003 10:56:24 -0700
Received: from 157.54.8.155 by INET-VRS-03.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 28 May 2003 10:56:24 -0700
Received: from RED-IMC-04.redmond.corp.microsoft.com ([157.54.2.168]) by inet-hub-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.6624);
	 Wed, 28 May 2003 10:56:24 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by RED-IMC-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Wed, 28 May 2003 10:56:23 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.82]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3788.0);
	 Wed, 28 May 2003 10:56:22 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6940.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: spam
Date: Wed, 28 May 2003 10:56:21 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA036BE50E@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: spam
thread-index: AcMlNuZDdgR8LxgZTnCTJsouNkGp/wACv3CQ
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>,
        "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: <ietf@ietf.org>
X-OriginalArrivalTime: 28 May 2003 17:56:22.0598 (UTC) FILETIME=[731EE660:01C32542]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA14130

> > The only question left is if there are any *technical* components to
> > doing so
> > (which would be the IETF's preserve), and, if so, what they are.
> 
> It surprises me that so many people are so eager to declare defeat
> before even trying the protocol route. (With current protocols defeat
> is pretty much inevitable.) 


There is an obvious issue with the protocol route: from a protocol point
of view, it is quite hard to distinguish unsolicited commercial e-mail,
which we would label spam, and unsolicited acceptable e-mail, which
could be more than welcome. 





From owner-ietf@ietf.org  Wed May 28 14:19:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14518
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 14:19:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L5O7-00080t-Jd
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 14:10:59 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L5GE-0007Yl-Oq
	for ietf@asgard.ietf.org; Wed, 28 May 2003 14:02:50 -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 OAA13859
	for <ietf@ietf.org>; Wed, 28 May 2003 14:02:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5Ee-0005eB-00
	for ietf@ietf.org; Wed, 28 May 2003 14:01:13 -0400
Received: from [131.227.76.5] (helo=prue.eim.surrey.ac.uk ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5Ee-0005e7-00
	for ietf@ietf.org; Wed, 28 May 2003 14:01:12 -0400
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 19L5Fz-0002wF-00; Wed, 28 May 2003 19:02:35 +0100
Date: Wed, 28 May 2003 19:02:32 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Keith Moore <moore@cs.utk.edu>
cc: alh-ietf@tndh.net, "" <ietf@ietf.org>
Subject: Re: spam
In-Reply-To: <20030528133031.4a10f0f4.moore@cs.utk.edu>
Message-ID: <Pine.GSO.4.50.0305281901450.13017-100000@artemis.ee.surrey.ac.uk>
References: <F114CBE4-9127-11D7-9944-00039388672E@muada.com>
 <011901c3253a$f32e8930$56144104@eagleswings> <20030528133031.4a10f0f4.moore@cs.utk.edu>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-105.9 required=5.5
	tests=AWL,BAYES_00,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_PINE,
	      USER_IN_WHITELIST
	autolearn=ham version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
X-Scanner: exiscan *19L5Fz-0002wF-00*reR0nwzgxcU* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 28 May 2003, Keith Moore wrote:

> > > Mabye a BOF would be in order in Vienna?
> >
> > A better idea than leaving the problem to languish as a research
> > topic.
>
> standard IETF operating procedure - start trying to engineer a solution
> before the problem is understood.

you need to engineer new problems for workgroups to work on.

L.

"We invented congestion! So we could invent congestion control!"

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>



From owner-ietf@ietf.org  Wed May 28 14:26:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14769
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 14:26:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L5O8-00083E-Bj
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 14:11:00 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L5Lj-0007wG-T8
	for ietf@asgard.ietf.org; Wed, 28 May 2003 14:08:31 -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 OAA14217
	for <ietf@ietf.org>; Wed, 28 May 2003 14:08:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5KA-0005iu-00
	for ietf@ietf.org; Wed, 28 May 2003 14:06:54 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5K9-0005hK-00
	for ietf@ietf.org; Wed, 28 May 2003 14:06:53 -0400
Received: from localhost (dwm@localhost)
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h4SI1Q305249
	for <ietf@ietf.org>; Wed, 28 May 2003 11:01:26 -0700
Date: Wed, 28 May 2003 11:01:26 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: <ietf@ietf.org>
Subject: Re: spam
In-Reply-To: <3ED45154.6050308@ehsco.com>
Message-ID: <Pine.LNX.4.33.0305281046380.865-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


I'd like propose a theory reguarding the success of the junk fax law which
would provide a reason that similar laws reguarding junk email might not
be successful:

There are significant costs associated with the origination of junk faxes
in the the sender must tie up a phone line for the duration of the
transmission and in many/most cases will be originating the fax from a
commercial measured rate phone so that even local calls will cost real
money. A wide area junk fax transmission would include long distance costs
or many remote offices.

On that basis, my theory is that the junk fax law, with the potential for
fines, etc., tipped the economics for the sender sufficiently that the
problem was resolved.

Junk email on the other hand has an extremely low cost of transmission in
the current economic model. Adding laws which establish penalties for
sending junk email will probably send the offenders outside of the reach
of the enforcement authorities. In the US, we already have major
corporations moving shell headquarters offshore to friendly taxing
authorities to avoid MAJOR tax bills and can't even fix the problem when
there are serious economic consequences to the government. Based on that
example and many others, I have no faith that enforcement based penalties
will make a significant difference because the perceived change to the
economics will be minimal.

Dave Morris




From owner-ietf@ietf.org  Wed May 28 14:41:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15564
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 14:41:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L5c2-000093-Vv
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 14:25:22 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L5PS-00084c-Fm
	for ietf@asgard.ietf.org; Wed, 28 May 2003 14:12:22 -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 OAA14387
	for <ietf@ietf.org>; Wed, 28 May 2003 14:12:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5Ns-0005lt-00
	for ietf@ietf.org; Wed, 28 May 2003 14:10:44 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5Nr-0005lY-00
	for ietf@ietf.org; Wed, 28 May 2003 14:10:43 -0400
Received: from localhost (dwm@localhost)
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h4SI56a05275;
	Wed, 28 May 2003 11:05:06 -0700
Date: Wed, 28 May 2003 11:05:05 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: Anthony Atkielski <anthony@atkielski.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <054c01c324ee$8b2e4e70$0a00000a@atkielski.com>
Message-ID: <Pine.LNX.4.33.0305281102430.865-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Wed, 28 May 2003, Anthony Atkielski wrote:

> In the future, it may become more and more difficult to find ISPs that
> provide truly unrestrained two-way access to the Internet.

Another potential outcome (other than uninformed government intervention)
if the technical community doesn't participate as appropriate in changing
the economic model. The ISPs will change the economic model to maintain
their own viability.

Dave Morris






From owner-ietf@ietf.org  Wed May 28 14:42:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15665
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 14:42:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L5c3-0000BO-Up
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 14:25:23 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L2FF-0001qi-SJ
	for ietf@asgard.ietf.org; Wed, 28 May 2003 10:49:37 -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 KAA06806
	for <ietf@ietf.org>; Wed, 28 May 2003 10:49:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L2Dg-0003mG-00
	for ietf@ietf.org; Wed, 28 May 2003 10:48:00 -0400
Received: from mxout4.cac.washington.edu ([140.142.33.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L2Df-0003mD-00
	for ietf@ietf.org; Wed, 28 May 2003 10:47:59 -0400
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
	by mxout4.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h4SEnYTc025979;
	Wed, 28 May 2003 07:49:34 -0700
Received: from DGX-104 (D-140-142-110-177.dhcp4.washington.edu [140.142.110.177])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h4SEnYQ0019375
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Wed, 28 May 2003 07:49:34 -0700
Date: Wed, 28 May 2003 07:49:35 -0700 (Pacific Standard Time)
From: Terry Gray <gray@washington.edu>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: spam
In-Reply-To: <050701c324ed$906da620$0a00000a@atkielski.com>
Message-ID: <Pine.WNT.4.55.0305280736090.1128@DGX-104>
References: <Pine.LNX.4.44.0305271831130.8489-100000@commander.av8.net>
 <3ED400A2.706@ehsco.com> <050701c324ed$906da620$0a00000a@atkielski.com>
Slogan: "I get enough exercise just pushing my luck."
Organization: University of Washington;  Computing & Communications
X-X-Sender: gray@mailer23.u.washington.edu
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


On Wed, 28 May 2003, Anthony Atkielski wrote:

> The ability to receive e-mail is not a Constitutional right.

The ability to stand outside someone's window and shout or play loud
music all night is not a constitutional right either.  True, the U.S.
government may do that to torture its captives, but most citizens
would consider such activity to be an egregious abuse of 1st amendment
free speech rights.

That's how I think of spam...

-teg

p.s. For those who believe there is no signficant cost to spam, I'd
love to have you put your money where your mouth is.  I've got plenty
of direct costs that are attributable soley to dealing with spam --and
that's not even counting the indirect costs of a "Type 1" spam storm
that brought the enterprise to its knees for two days and caused
legitimate email to be lost...

p.p.s. apologies to all for extending this futile debate; I tried
to control myself, but failed.





From owner-ietf@ietf.org  Wed May 28 15:07:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17397
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 15:07:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L5vQ-0001h1-Iw
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 14:45:24 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L5mw-0000c2-1F
	for ietf@asgard.ietf.org; Wed, 28 May 2003 14:36:38 -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 OAA15347
	for <ietf@ietf.org>; Wed, 28 May 2003 14:36:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5lM-00061D-00
	for ietf@ietf.org; Wed, 28 May 2003 14:35:00 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5lL-00061A-00
	for ietf@ietf.org; Wed, 28 May 2003 14:34:59 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S2966A> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 28 May 2003 11:36:35 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: <ietf@ietf.org>
Subject: RE: spam
Date: Wed, 28 May 2003 11:36:35 -0700
Message-ID: <013801c32548$1139a790$56144104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA036BE50E@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA17397

Christian Huitema wrote:
> There is an obvious issue with the protocol route: from a 
> protocol point of view, it is quite hard to distinguish 
> unsolicited commercial e-mail, which we would label spam, and 
> unsolicited acceptable e-mail, which could be more than welcome. 

Which is why we shouldn't even start down that path. The protocol needs
to be basic and simple, but place the bulk of the operational cost at
the origin rather than the current model of placing it at the receiver.
The system needs to let people that are willing to pay the cost at the
origin send whatever they want, but make it indisputably clear who/where
the origin is. The external mechanisms already exist to deal with the
social engineering once the originator can be pinned down.

Tony






From owner-ietf@ietf.org  Wed May 28 15:12:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18127
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 15:12:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L5vQ-0001hN-VF
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 14:45:24 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L5qJ-0000iE-Mi
	for ietf@asgard.ietf.org; Wed, 28 May 2003 14:40:07 -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 OAA15424
	for <ietf@ietf.org>; Wed, 28 May 2003 14:40:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5oj-00063C-00
	for ietf@ietf.org; Wed, 28 May 2003 14:38:29 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5oj-00062h-00
	for ietf@ietf.org; Wed, 28 May 2003 14:38:29 -0400
Received: from localhost (dwm@localhost)
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h4SIX3A05339
	for <ietf@ietf.org>; Wed, 28 May 2003 11:33:03 -0700
Date: Wed, 28 May 2003 11:33:03 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: <ietf@ietf.org>
Subject: RE: spam
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA036BE50E@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Message-ID: <Pine.LNX.4.33.0305281123010.865-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Wed, 28 May 2003, Christian Huitema wrote:

> There is an obvious issue with the protocol route: from a protocol point
> of view, it is quite hard to distinguish unsolicited commercial e-mail,
> which we would label spam, and unsolicited acceptable e-mail, which
> could be more than welcome.

I don't see where the commercial attribute has any significance.
Unsolicited BULK is what I label spam.  While I don't see the effort as
useful, detecting bulk email is probably easier than any attempt to
evaluate its purpose or (content beyond exceeding measures used to
detect the BULK nature).

Correct accurate labeling is a 2nd order solution which can be used to
reduce the people time impact via filtering, but filtering doesn't
eliminate resouce impacts such as consumption of scarce and/or costly
link bandwidth.

Protocol changes can deal with identification, authentication, trust
relationships, interoperable labeling, payment exchange, ... None of these
areas of new/improved protocols require any understanding of purpose or
content. [Perhaps even protocol support for interoperable wrapping of end
user spam nominations as documenation is collected and transfered about
the network.]


Dave Morris




From owner-ietf@ietf.org  Wed May 28 15:13:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18292
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 15:13:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L5vR-0001i4-9x
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 14:45:25 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L5sO-0001FE-JJ
	for ietf@asgard.ietf.org; Wed, 28 May 2003 14:42:16 -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 OAA15602
	for <ietf@ietf.org>; Wed, 28 May 2003 14:42:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5qo-00064j-00
	for ietf@ietf.org; Wed, 28 May 2003 14:40:38 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5qn-00064e-00
	for ietf@ietf.org; Wed, 28 May 2003 14:40:37 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4SIgCKk026487
	for <ietf@ietf.org>; Wed, 28 May 2003 20:42:12 +0200 (CEST)
Message-ID: <06a801c32548$da5d81a0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.44.0305272043280.8489-100000@commander.av8.net> <3ED45154.6050308@ehsco.com> <20030528080155.GB990@login.ecs.soton.ac.uk> <05af01c324f3$dafa3770$0a00000a@atkielski.com> <3ED4C675.8030407@ecotroph.net>
Subject: Re: spam - The IETF list is spam!
Date: Wed, 28 May 2003 20:42:12 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Andy writes:

> Look, you've solved the spam problem too!

That's exactly how I deal with it personally, but not everyone finds this an
acceptable solution, so it would be nice to help them look at other options.




From owner-ietf@ietf.org  Wed May 28 15:17:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18850
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 15:17:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L5vT-0001mE-5t
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 14:45:27 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L5vE-0001bY-1P
	for ietf@asgard.ietf.org; Wed, 28 May 2003 14:45:12 -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 OAA16180
	for <ietf@ietf.org>; Wed, 28 May 2003 14:45:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5te-0006C3-00
	for ietf@ietf.org; Wed, 28 May 2003 14:43:34 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5td-0006C0-00
	for ietf@ietf.org; Wed, 28 May 2003 14:43:33 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4SIj9Kk026528
	for <ietf@ietf.org>; Wed, 28 May 2003 20:45:09 +0200 (CEST)
Message-ID: <06af01c32549$43a84f50$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <011901c3253a$f32e8930$56144104@eagleswings>
Subject: Re: spam
Date: Wed, 28 May 2003 20:45:09 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony writes:

> Rather than passing a token, require the mail to
> be encrypted with the public key of the recipient.

Public-key encryption of an entire e-mail is extremely processor-intensive.
Even conventional encryption is very time-consuming.  You can just hash it
and sign the key.

However, this would be a problem for people in countries that outlaw
encryption.  What would they do?

> ... and provide an incentive for the ISPs to
> actually deploy a PKI.

Who would you trust to certify keys?





From owner-ietf@ietf.org  Wed May 28 15:17:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18877
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 15:17:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L5vS-0001lR-KK
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 14:45:26 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L5te-0001bC-2j
	for ietf@asgard.ietf.org; Wed, 28 May 2003 14:43:34 -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 OAA15990
	for <ietf@ietf.org>; Wed, 28 May 2003 14:43:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5s4-00069m-00
	for ietf@ietf.org; Wed, 28 May 2003 14:41:56 -0400
Received: from tomts25.bellnexxia.net ([209.226.175.188] helo=tomts25-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5s3-00069j-00
	for ietf@ietf.org; Wed, 28 May 2003 14:41:55 -0400
Received: from yahoo.com ([65.93.181.225]) by tomts25-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030528184331.MKUH18025.tomts25-srv.bellnexxia.net@yahoo.com>;
          Wed, 28 May 2003 14:43:31 -0400
Date: Wed, 28 May 2003 14:43:31 -0400
Subject: Re: spam
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: <ietf@ietf.org>
To: David Morris <dwm@xpasc.com>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <Pine.LNX.4.33.0305281046380.865-100000@egate.xpasc.com>
Message-Id: <4797E09F-913C-11D7-8C75-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Wednesday, May 28, 2003, at 02:01  PM, David Morris wrote:

> Junk email on the other hand has an extremely low cost of transmission 
> in
> the current economic model.

There is a difference between the people selling the product, and the 
people sending the spam. Usually not the same people. The SELLERS do 
have a transmission cost as they must pay the spammers to spam people 
for them. Admittedly not much, but the sellers are a much easier target 
than the spammers. Drive their costs up significantly and you dry up 
the spam market by implication (for types 1 and 2, which at least for 
me are the bulk of my 50 or so spams a day).

simon


--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Wed May 28 15:28:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19362
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 15:28:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L6QV-0006bH-PR
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 15:17:31 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L5vl-0001mI-B1
	for ietf@asgard.ietf.org; Wed, 28 May 2003 14:45:45 -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 OAA16204
	for <ietf@ietf.org>; Wed, 28 May 2003 14:45:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5uB-0006C9-00
	for ietf@ietf.org; Wed, 28 May 2003 14:44:07 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5uB-0006C6-00
	for ietf@ietf.org; Wed, 28 May 2003 14:44:07 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 208196 for ietf@ietf.org; Wed, 28 May 2003 13:45:11 -0500
Message-ID: <3ED503D3.3030408@ehsco.com>
Date: Wed, 28 May 2003 13:45:39 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: spam
References: <F114CBE4-9127-11D7-9944-00039388672E@muada.com>
In-Reply-To: <F114CBE4-9127-11D7-9944-00039388672E@muada.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/28/2003 11:17 AM Iljitsch van Beijnum wrote:

> I don't think moving to some kind of SMTPng is quite as impossible as 
> people seem to think.

Although I'm all for an SMTPng, it's important to delineate the benefits
that would be served from such an approach, and also some discussion on
how difficult this would be.

For example, a protocol would not be able to confidently deter the
transfer of unsolicited commercial email over a valid connection by
itself. However, an SMTPng by itself could specifically address the issue
of accountability.

The accountability information could in turn be used to help fight
forgeries, and this information would help to combat some kinds of spam.
It would help get a spammer's account yanked due to AUP violations since
you would be able to prove where the spam came from (assuming the ISP
enforced an AUP that prohibited spam). By the same measure, it would also
be useful for authoritatively rejecting mail from those ISPs who don't
enforce AUPs or who don't prohibit spam, and it would be usefule for
authoritatively rejecting mail from organizations who are known to be
spammers themselves (in these cases, it would effetively allow for better
blacklists). If we had a way to validate the transfer path (such as using
recursive signatures on the transfer path), then the accountability would
be further heightened by allowing us to reject any mail that had passed
through any of the known-offender networks. These would all be
improvements over what we have today, giving us better accuracy in our
rejection policies, but still allowing some spam through the network (eg,
first offenders).

Improved accountability would also substantially improve the enforcement
of anti-spam laws, should any exist. Since the improved accountability by
itself would not be sufficient to stop all spam, there would still be a
need for laws. Those laws would be significantly strengthened by the extra
accountability information. A strong law in conjunction with accurate and
credible filters would cumulatively be very effective in the fight against
spam, possibly even good enough to "win" the war.

An SMTPng could also help against forgery-related problems. This includes
common spam-related fraud, but also includes outright fraudulent
misrepresentations, worms, etc.

Co-existence with legacy SMTP is a problem. If it easy for spammers to
avoid using SMTPng, then they will stick with legacy SMTP. There are
operational ways for reducing the exposure (including heavily discounting
mail from SMTP during post-transfer filtering), but the hammer of law is
still going to be necessary to kill that problem. At the same time, if we
know that we can't directly fix this in protocol, then there is some
validity to the argument that we can just keep using the existing SMTP and
hope that laws do the rest. In that regard, the substantitive gain from
doing all of the work necessary is in the improved accountability that
SMTP *cannot* provide in its current form (even if all of the options such
as STARTTLS are used).

This is how I think an SMTPng might work:

  C: <connect>
  C: <send certificate>
  S: <validate host identity>
  S: ok
  C: <request transfer>
  S: ok
  C: <send transfer headers>
  S: <validate sender identity>
  S: <validate transfer path>
  S: <validate recipients>
  S: <...>
  S: ok
  C: <send message headers, possibly encrypted/signed>
  S: <validate headers (eg pass/reject contents)>
  S: ok
  C: <send message body>
  S: ok
  C: <close>

That gives a lot of data to validate and substantially improves the level
of accountability over anything that SMTP can offer in its current form.

There are lots of other things that could be incorporated once this was
done which would further add to the value proposition. In fact, the
long-term value to an SMTPng would be to address all of the other
mail-related issues that are also already outstanding besides just the
credibility shortcomings. This includes features such as encrypted message
headers (rather than just bodies), true i18n support, per-recipient
message routing (similar to the expiremental MB and other per-recipient
RRs), end-to-end option negotiation across the messaging network (in
addition to the hop-by-hop negotiation we have now), extensible OIDs as
response codes, reduced round-trip latencies, and more.

Things that would probably be needed to support any of this:

  - new transfer protocol syntax (replace HELO with certificate
    exchange, for example)

  - optionally a new submission service

  - URI and DNS types for the submission services

  - new message routing services separate from MX routing

  - new message format (separating transfer headers from message
    headers from message contents, which are all one unit currently)

  - MIME types for each message component, for compatibility with
    legacy mail stores

  - gateway rules for conversion betwen 821 and ng

This is a lot of work for the sole purpose of improving accountability but
it would probably be necessary in order to get beyond what SMTP can
provide today. It is much more justifiable if we are going to reinvent
mail for other purposes at the same time.

I also want to reiterate that we still need laws regardless of whether we
go to a new SMTPng or stay with SMTP. My feeling is that we (collectively)
should go ahead and start pursuing legal enforcement methods for use with
SMTP now, regardless of what we end up doing over the next five years on
the technology front. As such, I think the legal-interaction issue needs
to be addressed first.

I am also in favor of reinventing mail. It's a standing joke against the
IETF that people can readily commit flagrant forgeries in one of the most
important technologies of our time.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Wed May 28 15:44:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19915
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 15:44:34 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L6QW-0006bm-3p
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 15:17:32 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L5ya-0001nJ-7b
	for ietf@asgard.ietf.org; Wed, 28 May 2003 14:48:40 -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 OAA16266
	for <ietf@ietf.org>; Wed, 28 May 2003 14:48:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5x0-0006Ct-00
	for ietf@ietf.org; Wed, 28 May 2003 14:47:02 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L5wz-0006Cq-00
	for ietf@ietf.org; Wed, 28 May 2003 14:47:01 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4SImZKk026556
	for <ietf@ietf.org>; Wed, 28 May 2003 20:48:35 +0200 (CEST)
Message-ID: <06b601c32549$be5ad510$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.33.0305281033360.865-100000@egate.xpasc.com>
Subject: Re: requiring payment (was spam)
Date: Wed, 28 May 2003 20:48:35 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

David writes:

> In the USA today, it costs $.37 to send a physical
> mail. I don't think it unreasonable for someone
> sending me mail to pay a similar fee ...

You can pay me via PayPal.  Looking at my inbox, you owe me $1.48 already.

> ... conversely for me to pay such a fee for each
> of my posts to the IETF list ...

Who would pay the fee for the sending of each post to each list member?
Shouldn't you be paying for that, too, since it is your post?

Looks like the bill is up to $20,000 or so now.  Will that be cash, card, or
check?

> ... even though I would expect the list to use a
> free channel to distribute the result.

Why?  If you want people to pay you, why shouldn't you pay everyone else?





From owner-ietf@ietf.org  Wed May 28 15:49:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20172
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 15:49:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L6R0-00071E-Cv
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 15:18:02 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L6Aj-0003bh-9p
	for ietf@asgard.ietf.org; Wed, 28 May 2003 15:01:13 -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 PAA16722
	for <ietf@ietf.org>; Wed, 28 May 2003 15:01:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L699-0006Hm-00
	for ietf@ietf.org; Wed, 28 May 2003 14:59:35 -0400
Received: from out003pub.verizon.net ([206.46.170.103] helo=out003.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L698-0006HQ-00
	for ietf@ietf.org; Wed, 28 May 2003 14:59:34 -0400
Received: from earthlink.net ([4.65.81.213]) by out003.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030528190037.STDY4805.out003.verizon.net@earthlink.net>;
          Wed, 28 May 2003 14:00:37 -0500
Message-ID: <3ED50675.72DA7BFC@earthlink.net>
Date: Wed, 28 May 2003 11:56:53 -0700
From: Peter Deutsch <pdeutsch@earthlink.net>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Huitema <huitema@windows.microsoft.com>
CC: Iljitsch van Beijnum <iljitsch@muada.com>,
        "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, ietf@ietf.org
Subject: A peer-to-peer trust system model (was: Re: spam)
References: <DAC3FCB50E31C54987CD10797DA511BA036BE50E@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out003.verizon.net from [4.65.81.213] at Wed, 28 May 2003 14:00:37 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

g'day,

Christian Huitema wrote:
...
> There is an obvious issue with the protocol route: from a protocol point
> of view, it is quite hard to distinguish unsolicited commercial e-mail,
> which we would label spam, and unsolicited acceptable e-mail, which
> could be more than welcome.

I've sat on this posting, give both the previous volume of the thread,
and the danger of getting too far into implementation discussions on a
general list, but I've seen several postings to the effect that "it's
hard to see what we could do at the protocol level". Personally, I think
the problem would benefit from a little lateral thinking, so here's my
cut at it. Those who tire of my ramblings, and don't want a quote from
Tom Lehrer and allusions to Queen Elizabeth and Francis Drake, should
hit "n" now...


Concepts such as Hashcash or other payment-oriented systems, in which
you try to impose a cost on the sender to screen out bulk mailers, are
interesting enough, but I think they're addressing the wrong problem.
I've personally come to the conclusion that to address this problem
(that is, the decision as to whether I want to accept a message from
you), I don't actually need to know who you are, or even what you're
trying to send me, and I certainly don't need to impose artificial costs
on you (since this looks too much like punishing the innocent for the
crimes of the guilty).

The heart of the issue seems to be:

    What I really need to decide is whether I
    should trust you enough to start accepting
    unsolicited email from you (or more generally,
    to start interacting with you for purpose x).


I don't know what Paul Vixie meant by his allusion to a
trusted-introducer model but I'd love to hear more about that, since
I've been working on something that sounds a lot like that and I'd like
to compare notes and seem how much reinventing of the wheel I'm
currently doing (and to thrash the deceased equine a bit, mail I sent to
him died in his maze of twisty little email filters, all the same, so we
seem to have yet another existance proof that this problem is imposing
costs on us and hurting our ability to use the Internet for useful work.
To quote Tom Lehrer, "but I digress").


One way I can learn whether I want to interact with you is to invest
some time building up a trust relationship with you (verifying you are
who say you are, etc). Another way would be for me to ask people I
already trust who might know you to issue you a reference.

My conclusion is that we need something along the lines of a
peer-to-peer trust authentication token system which would allow the
first time caller to authenticate him/herself to new MTAs by allowing
him/her to demonstrate his/her prior participation in existing trust
relationships. The idea is to build something more oriented towards
peer-to-peer relationship building, rather than the traditional PKI
central authority model we've seen so far.

In practice, I imagine it would be most practical, if we want to
interact with the traditional store-and-forward email system, for my
friends to issue signed, non-forgable "trust tokens" (I think I called
them "letters of marque" in a recent posting, since they convert
"pirates" to "honest businessmen and women", just as Queen Elizabeth did
with Francis Drake... ;-) The redeemer would hand a set of these trust
tokens to me on first contact (you could embed them in the mail header,
or we'd negotiate which trust tokens I accept when you connect, or I'd
publish a list in "son-of-DNS" which trust groups I'm currently
trusting, etcetcetc).

When I receive such a {set of) trust token{s}, I'd check them to see if
they really do come from folks I trust and otherwise satisfy my current
policy requirements (e.g. I may need at least three valid tokens, or I
may need at least two, including one from somebody in Sweden, etc), and
if so I could start granting the bearer interaction privileges. The
unlying assumption here is that trust is a transitive relationship, and
thus I'd allow myself to build up webs of such trust relationships by
accepting references and references from references, so I wouldn't have
to rely solely on a single, centralized PKI infrastructure.

Now, in practice, I'd like to be able to adjust my policies based upon
the qualitity of your references (say, requiring x references from group
a, but only y references from group b to begin transacting). This has
the beneficial side effect of putting the policy decision making into
the hands of the grantor of privileges. All I require from the issuer of
certificates are that I can prove they come from the issuer, and that
they contain certain information (such as issuer, issue date, TTL, etc)
- the decision about what to do when they're valid rests with the
redeemer.

Obviously I'd also need to be able to issue my own letters of marque,
once I've developed sufficient trust in you (say, after I've experienced
z satisfactory interactions without incident, or maybe when I click a
button in my MUA because I like what I'm getting). Instinct tells me
this "degree of good behaviour" could be quantified and automated, but
"electing to start trusting" is not something you need to do on every
message so need not be computationally easy. As a sidebar, the policies
I use in granting my trust certificates would go far in determining to
what degree they have later redemption value for others.

And finally, I'd like these letters of marque to be revocable in
something close to real time, since sometimes you get it wrong, and
sometimes folks go bad. This doesn't necessarily mean I want to be
contacted for every redemption (in fact, sometimes this will be
impractical) but assigning such tokens a TTL and/or a refresh time and
otherwise allowing some controls over redemption policy seems to be a
good idea.

Signing a record consisting of an ID, date and some other useful data
with a private key seems to be just the ticket here, since it can be
rapidly decrypted and checked but not easily forged. There is probably a
lot more to it that this, since I probably don't care much about the
cost of signing (something I wont do every interaction, only when
agreeing to issue a new letter of marque) but I definitely want forging
to be hard, and verifying to be cheap. This is classic public key stuff,
although it looks like it would be seful if you could show *both* that
you're Alice, *and* that you're a member of a specific group (ie. you
need to transmit two secrets, one you own and one you share with your
"trust buddies". This may be nothing more than using a group key to sign
your ID within your token (making it a secret shared only by the turst
ring), but it might also be nice if you can perhaps automatically get
the group secret when you've been accepted by enough members of the
group.

I remember work from the crypto community about sharing n parts of a
secret (that is, you need at least n parts of the secret to recreate it)
that could be relevant here, although I haven't gone back and tracked it
down yet. The idea would be that as you collect references, you collect
pieces of the secret and when enough folks trust you, you have the info
needed to start generating and issuing your own certificates as part of
the club. In my notes on this, I make reference to being able to
"blackball" a potential member, since issuing him an invalid token in
effect keeps him out of the club. This area needs more thought, but it
holds the promise of automating the implementation of membership
management, which could be nice...


I'm still chewing on what's suitable stuff to put into the token, but it
lends itself to a fair number of things, when you think about it. You
might add in there info about which domains to allow, which user names,
which protocols to allow, etc. The idea is to delineate the areas and 
scope for which trust would apply.

The storage of the needed public keys probably could go into a "son of
DNS" easily enough. Extensions to SMTP to request and redeem tokens
obviously would need some thought, although I suspect you could embed
the tokens in the mail header easily enough and thus perhaps not have to
mess with the wire protocol at all, at least in initial implementations
(you'd still need some way of requesting and/or issuing new trust
tokens, but that could be taken out-of-band to another protocol).  It
might even be better to make this a part of a whole new protocol, since
as Paul points out, the current architecture appears to have some
fundamental flaws and it may be time to stop patching it up and get on
with the new architecture. This is where I'd like to  calibrate myself
against what Paul alluded to, to see where he was going with that.

Note that this idea would have some interesting side effects (or should
I call them "social effects"?) You begin life in a cold, dark, lonely
world with little trust and less functionality but over time, you build
up useful relationships which can serve you well. Your "coin of the
realm" here is your own credibility, so trying to pass forged trust
tokens rapidly pollutes your swimming pool, while valuable trust
relationships would suck in more trustworthy folks and benefit from
positive networking effects. Today's great mailing list would be
tomorrow's "trust ring", where any mail from anyone trusted by your
"list buddies" is accepted, mail from random Taiwanese MTAs is rejected
or tarpitted.

The guy who issues the certificates that start the flood of spam into
your mailbox gets deprecated as an authority with a click of a button.
The spammer (or legitimate stranger) who can't prove his bone fides gets
shunted to the slow lane over near the tarpits until he can prove
himself over time. And over time, you can elect to promote well-behaved
strangers to friends, expanding your trust ring.

My instinct tells me there's something here worth pursuing, given the
magnitude and growth rate of the current spam problem, but I doubt that
the IETF general mailing list is a place to work on this, so I'm
interested to see where the discussion  goes once the flames die
down....

As I said, I've done some digging and found nothing exactly like this,
but Paul's casual remark suggests I'm missing something basic in the
literature (admittedly I haven't done an exhaustive search yet).
Pointers to the obvious work, or pointers to the obvious holes, would be
most welcome. And of course, pointers to the best mailing list for
follow-ups are probably a *really* good idea....



                        - peterd





-- 
---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software

                        "Bungle..."
               "That's an 'i', you idiot..."
                  "Oh, right. 'Bingle..."

                            - Red versus Blue...

---------------------------------------------------------------------



From owner-ietf@ietf.org  Wed May 28 15:54:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20434
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 15:54:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L6R1-00072n-0A
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 15:18:03 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L6Gy-000375-Gm
	for ietf@asgard.ietf.org; Wed, 28 May 2003 15:07:40 -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 PAA17538
	for <ietf@ietf.org>; Wed, 28 May 2003 15:07:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L6FO-0006Nc-00
	for ietf@ietf.org; Wed, 28 May 2003 15:06:02 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L6FN-0006MW-00
	for ietf@ietf.org; Wed, 28 May 2003 15:06:01 -0400
Received: from localhost (dwm@localhost)
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h4SJ0Y105418;
	Wed, 28 May 2003 12:00:35 -0700
Date: Wed, 28 May 2003 12:00:34 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: S Woodside <sbwoodside@yahoo.com>
cc: <ietf@ietf.org>
Subject: Re: spam
In-Reply-To: <4797E09F-913C-11D7-8C75-000393414368@yahoo.com>
Message-ID: <Pine.LNX.4.33.0305281147080.865-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Wed, 28 May 2003, S Woodside wrote:

> On Wednesday, May 28, 2003, at 02:01  PM, David Morris wrote:
>
> > Junk email on the other hand has an extremely low cost of transmission
> > in
> > the current economic model.
>
> There is a difference between the people selling the product, and the
> people sending the spam. Usually not the same people. The SELLERS do
> have a transmission cost as they must pay the spammers to spam people
> for them. Admittedly not much, but the sellers are a much easier target
> than the spammers. Drive their costs up significantly and you dry up
> the spam market by implication (for types 1 and 2, which at least for
> me are the bulk of my 50 or so spams a day).

In one sense, you are agreeing with my basic premis .. the economic model
most change. Where we may disagree is whether any particular proposal will
make a significant change is costs. A cursory look at some small portion
of my spam suggests that the SELLERS have a very small physical footprint
in a very high percentage of the cases. Easy to morph into another entity.
Roughly $500 to incorporate in the US which at the minimum provides a
additional layer to the onion which must be removed to get at the real
people involved. If they move the whole operation to some carribean island
nation, it is no big deal to ship many of the products I'm offered these
days. For example, one homeopathic medical (oximoron I know) supply
company uses third party agents to take orders. The base company, which
has been in business for years, ships the product directly to the
consumer. I doubt that such a company would be found guilty of spamming if
one of these agents chose to use spam to generate business.

There are also international communications treaties, first amendment
rights, etc. which I suspect would preclude out and out blocking of
internet traffic from our infamous carribean neighbor.

Hence my conclusion that the only realistic way to alter the economics is
to collect the fee up front using a combination of protocols, social and
legal provisions designed to avoid or absolutely minimize the free
exchange of email/information between related parties.

Such fees could also support the new PKI, server, etc. infrastructure
needed to introduce other aspects of any possible technical solutions.

Dave Morris





From owner-ietf@ietf.org  Wed May 28 15:56:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20644
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 15:56:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L6R1-00074Y-M8
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 15:18:03 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L6HW-0003G2-Qi
	for ietf@asgard.ietf.org; Wed, 28 May 2003 15:08:14 -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 PAA17661
	for <ietf@ietf.org>; Wed, 28 May 2003 15:08:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L6Fw-0006P1-00
	for ietf@ietf.org; Wed, 28 May 2003 15:06:36 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L6Fw-0006Nv-00
	for ietf@ietf.org; Wed, 28 May 2003 15:06:36 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id OAA27297;
	Wed, 28 May 2003 14:59:35 -0400
Date: Wed, 28 May 2003 15:00:39 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: "Eric A. Hall" <ehall@ehsco.com>
cc: John Stracke <jstracke@centive.com>, <ietf@ietf.org>
Subject: Re: spam
In-Reply-To: <3ED45154.6050308@ehsco.com>
Message-ID: <Pine.LNX.4.44.0305281450170.7861-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Wed, 28 May 2003, Eric A. Hall wrote:

> You still don't seem to understand the nature of proof, arguing instead
> that the existence of alternatives somehow disproves a matter of fact.
> Again, whether or not you think that the proof is significant is a matter
> of opinion, not a matter of proof.

This is exactly true of your position, but not mine.  Seems you are
looking in a mirror.

* Shannon's theorem is a fact, not an opinion.

* The cost of disks and networks are facts, not opinions.

* The cost of spam is a fact deduced from the costs on disks, networks and
computers. It is a fact, not an opinion.

* Anti-spammers already tried to use "costs" in 1998, and lost, when
disks, networks, and computers were much more expensive. That is a fact,
not an opinion.

Email, and thus spam, is practically a free service.  Spam costs
practically nothing.   That is a conclusion based on fact, not opinion.

Your attempts to somehow wave about the impressive cost of the
infrastructure to serve millions of users is simply irrelevant smoke, and
forms no justification for limiting spam.  Highways cost money. Postal
Systems cost money.  Telephone systems cost money. The fact that they cost
money is no reason (nor ever was) to ban Highway billboards, Junk Mail,
Junk faxes, or telemarketing.  The costs of highways systems, postal
systems, and telephone systems played no role whatsoever in the laws that
regulate BillBoards, Junk Mail, Junk Faxes, or Telemarketing. All of which
are regulated commercial speech.

		--Dean





From owner-ietf@ietf.org  Wed May 28 16:02:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20889
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 16:02:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L6R2-00078N-NF
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 15:18:04 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L6Mw-0005WA-RO
	for ietf@asgard.ietf.org; Wed, 28 May 2003 15:13:50 -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 PAA18425
	for <ietf@ietf.org>; Wed, 28 May 2003 15:13:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L6LM-0006UL-00
	for ietf@ietf.org; Wed, 28 May 2003 15:12:12 -0400
Received: from carwash.centive.com ([65.220.90.249] helo=carwash.centivinc.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19L6L8-0006S5-00
	for ietf@ietf.org; Wed, 28 May 2003 15:11:58 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003052815200214062
 for <ietf@ietf.org>; Wed, 28 May 2003 15:20:02 -0400
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 28 May 2003 15:10:43 -0400
Message-ID: <3ED509B3.7060303@centive.com>
Date: Wed, 28 May 2003 15:10:43 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: spam
References: <013801c32548$1139a790$56144104@eagleswings>
In-Reply-To: <013801c32548$1139a790$56144104@eagleswings>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 May 2003 19:10:43.0176 (UTC) FILETIME=[D5D51680:01C3254C]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony Hain wrote:

>The protocol needs
>to be basic and simple, but place the bulk of the operational cost at
>the origin rather than the current model of placing it at the receiver.
>  
>
Hmm.  It's pretty much in the nature of human-to-human communication 
that the receiver is always going to have higher humanpower costs than 
the sender (since it's easier to say something than to understand it); 
so the only way to shift the balance is to impose extra costs on the sender.

In other words, any group chartered to work on such a protocol would be 
*required* to be inefficient.  At last, a charter goal we know we can 
meet! :-)

-- 
/==========================================================\
|John Stracke      |jstracke@centive.com                   |
|Principal Engineer|http://www.centive.com                 |
|Centive           |My opinions are my own.                |
|==========================================================|
|A man's concepts should exceed his vocabulary, or what's a|
|metaphor?                                                 |
\==========================================================/





From owner-ietf@ietf.org  Wed May 28 16:11:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21350
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 16:11:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L6se-0008Ry-3d
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 15:46:36 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L6Qy-0006z4-Ip
	for ietf@asgard.ietf.org; Wed, 28 May 2003 15:18:00 -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 PAA18900
	for <ietf@ietf.org>; Wed, 28 May 2003 15:17:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L6PO-0006Xn-00
	for ietf@ietf.org; Wed, 28 May 2003 15:16:22 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L6PO-0006XG-00
	for ietf@ietf.org; Wed, 28 May 2003 15:16:22 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id PAA24586;
	Wed, 28 May 2003 15:13:03 -0400
Date: Wed, 28 May 2003 15:14:06 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: John Stracke <jstracke@centive.com>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <3ED4B4AE.5070207@centive.com>
Message-ID: <Pine.LNX.4.44.0305281513130.7861-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Apparently, you've taken some "axioms" from radical antispammers.

		--Dean

On Wed, 28 May 2003, John Stracke wrote:

> Dean Anderson wrote:
>
> >In fact, it is an
> >axiom that crowds are always wrong.
> >
> I *suppose* that's a true statement--somebody somewhere (e.g., you) must
> be working with "crowds are always wrong" as an axiom.  But those of us
> who know what the word means understand that whether something is an
> axiom has nothing to do with whether it's true.
>
> --
> /===============================================================\
> |John Stracke      |jstracke@centive.com                        |
> |Principal Engineer|http://www.centive.com                      |
> |Centive           |My opinions are my own.                     |
> |===============================================================|
> |"Power corrupts; Powerpoint corrupts absolutely." -- Vint Cerf |
> \===============================================================/
>
>
>
>




From owner-ietf@ietf.org  Wed May 28 16:12:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21548
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 16:12:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L6se-0008S4-Dy
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 15:46:36 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L6Qz-0006zb-81
	for ietf@asgard.ietf.org; Wed, 28 May 2003 15:18:01 -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 PAA18904
	for <ietf@ietf.org>; Wed, 28 May 2003 15:17:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L6PP-0006Xs-00
	for ietf@ietf.org; Wed, 28 May 2003 15:16:23 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L6PO-0006XG-01
	for ietf@ietf.org; Wed, 28 May 2003 15:16:22 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id PAA24573;
	Wed, 28 May 2003 15:11:02 -0400
Date: Wed, 28 May 2003 15:12:06 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: John Stracke <jstracke@centive.com>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <3ED4B3EC.8070206@centive.com>
Message-ID: <Pine.LNX.4.44.0305281507320.7861-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Type 1 spammers don't take that "discount". When they do, we make them
pay.

Type 1 spammers also seem to (in vast majority) understand that open
relays do not offer any anonymity.  This is the _false_ assertion of
radical anti-spammers, who seem to me to be the abusers.  Chris Neill
(antispammer open relay abuser eventually fired from Verio--he was
ironically, an abuse admin) was shocked to learn he was't anonymous, like
he thought.

The claims made by antispammers about open relays are false. Type 1
spammers seem to get that, judging by their behavior.  But radical
antispammers don't.

		--Dean

On Wed, 28 May 2003, John Stracke wrote:

> Dean Anderson wrote:
>
> >We are lucky that spammers don't get a discount
> >
> Open relays give them a five-finger discount.
>
> --
> /===============================================================\
> |John Stracke      |jstracke@centive.com                        |
> |Principal Engineer|http://www.centive.com                      |
> |Centive           |My opinions are my own.                     |
> |===============================================================|
> |"Power corrupts; Powerpoint corrupts absolutely." -- Vint Cerf |
> \===============================================================/
>
>
>
>




From owner-ietf@ietf.org  Wed May 28 16:19:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21845
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 16:19:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L738-0001Lc-CN
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 15:57:26 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L6ot-0007zz-Ua
	for ietf@asgard.ietf.org; Wed, 28 May 2003 15:42:43 -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 PAA19876
	for <ietf@ietf.org>; Wed, 28 May 2003 15:42:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L6nJ-0006oG-00
	for ietf@ietf.org; Wed, 28 May 2003 15:41:05 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L6nJ-0006ny-00
	for ietf@ietf.org; Wed, 28 May 2003 15:41:05 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id PAA03056;
	Wed, 28 May 2003 15:38:15 -0400
Date: Wed, 28 May 2003 15:39:09 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Iljitsch van Beijnum <iljitsch@muada.com>
cc: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, <ietf@ietf.org>
Subject: Re: spam
In-Reply-To: <F114CBE4-9127-11D7-9944-00039388672E@muada.com>
Message-ID: <Pine.LNX.4.44.0305281536460.7861-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


On Wed, 28 May 2003, Iljitsch van Beijnum wrote:

> It surprises me that so many people are so eager to declare defeat
> before even trying the protocol route.

We tried protocols 5 years ago. They haven't worked.  I've explained why
specifically, and why in theory they can't work.  Now the protocol
designers say that controlling spam wasn't the goal. It was the goal when
they started. Perhaps they should have stayed focused.





From owner-ietf@ietf.org  Wed May 28 16:54:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23023
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 16:54:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L7d5-0003sP-4v
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 16:34:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L7D4-0002RE-RB
	for ietf@asgard.ietf.org; Wed, 28 May 2003 16:07:42 -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 QAA21168
	for <ietf@ietf.org>; Wed, 28 May 2003 16:07:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L7BU-00079i-00
	for ietf@ietf.org; Wed, 28 May 2003 16:06:04 -0400
Received: from bean.ar.com ([66.123.187.68])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L7BT-00079L-00
	for ietf@ietf.org; Wed, 28 May 2003 16:06:04 -0400
Received: from flash.ar.com (wessorh@flash [66.123.187.80])
	by bean.ar.com (8.12.6/8.12.6) with ESMTP id h4SK6ddX016246;
	Wed, 28 May 2003 13:06:39 -0700 (PDT)
Date: Wed, 28 May 2003 13:06:39 -0700 (PDT)
From: Rick Wesson <wessorh@ar.com>
To: Dean Anderson <dean@av8.com>
cc: <ietf@ietf.org>
Subject: Re: spam
In-Reply-To: <Pine.LNX.4.44.0305281450170.7861-100000@commander.av8.net>
Message-ID: <Pine.LNX.4.33.0305281301010.27483-100000@flash.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


dean a small note before i add you to my procmailrc

>
> On Wed, 28 May 2003, Eric A. Hall wrote:
>
> > You still don't seem to understand the nature of proof, arguing instead
> > that the existence of alternatives somehow disproves a matter of fact.
> > Again, whether or not you think that the proof is significant is a matter
> > of opinion, not a matter of proof.
>
> This is exactly true of your position, but not mine.  Seems you are
> looking in a mirror.
>
> * Shannon's theorem is a fact, not an opinion.
>
> * The cost of disks and networks are facts, not opinions.
>
> * The cost of spam is a fact deduced from the costs on disks, networks and
> computers. It is a fact, not an opinion.
>
> * Anti-spammers already tried to use "costs" in 1998, and lost, when
> disks, networks, and computers were much more expensive. That is a fact,
> not an opinion.
>
> Email, and thus spam, is practically a free service.  Spam costs
> practically nothing.   That is a conclusion based on fact, not opinion.
>

your conclusion is incorrect, we have to pay sysadmins to keep spam out of
our mail boxes and in some cases prefessional services to keep spam out of
mailboxes that are real important.

just as my paper shredder and the electricity to run it cost me to process
junk mail and garbage service to throw away the trash. buring it is not an
option in my fair city.

if you wish to continue draw conslusions through falty analysis you may
land in my filters...


-rick








From owner-ietf@ietf.org  Wed May 28 16:54:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23024
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 16:54:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L7d4-0003rd-B8
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 16:34:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L7Ae-0002OA-EH
	for ietf@asgard.ietf.org; Wed, 28 May 2003 16:05:12 -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 QAA21064
	for <ietf@ietf.org>; Wed, 28 May 2003 16:05:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L794-00077y-00
	for ietf@ietf.org; Wed, 28 May 2003 16:03:34 -0400
Received: from vrx.net ([216.13.126.22] helo=ns1.vrx.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L793-00077g-00
	for ietf@ietf.org; Wed, 28 May 2003 16:03:33 -0400
Received: from [192.168.1.14] (lsanca1-ar47-4-33-128-181.lsanca1.dsl-verizon.net [4.33.128.181])
	by ns1.vrx.net (Postfix) with ESMTP
	id CE1B2D3BD; Wed, 28 May 2003 16:04:58 -0400 (EDT)
Mime-Version: 1.0
X-Sender: steflist@vrx.net
Message-Id: <v04220805bafac4f8ad58@[192.168.1.14]>
In-Reply-To: <Pine.LNX.4.33.0305281033360.865-100000@egate.xpasc.com>
References: <Pine.LNX.4.33.0305281033360.865-100000@egate.xpasc.com>
Date: Wed, 28 May 2003 13:04:51 -0700
To: David Morris <dwm@xpasc.com>
From: Einar Stefferud <Steflist@thor.nma.com>
Subject: Re: requiring payment (was spam)
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

Hello Dave Morris ---

It would be helpful if you would explain how this payment system of 
yours might actually work in real life.

Perhaps like TELEX worked before it died, with settlements between 
the first posing ISP to the last receiving ISP, with "settlement" 
payments spread across all ISPs in between.

Of course this leads to bilateral agreements among al the thousands of 
ISPs, and collective agreements among the mass of global ISPs.

Now, consider the cost of such arrangements, to cover the frictional 
costs of just being in business, plus the required profit margins that
accrue to any such massive payment shuffling.

Everyone here advocating payments do not seem to understand the overhead costs of collecting and distributing the money. 

Be careful of what you wish for! -- You just might get it!

Cheers...\Stef

>Simon,
>
>The proposals haven't been to eliminate free email, only to provide an
>alternative which folks can require be used to send them email if they
>haven't established a free relationship with the sender.
>
>In the USA today, it costs $.37 to send a physical mail. I don't think it
>unreasonable for someone sending me mail to pay a similar fee and
>conversely for me to pay such a fee for each of my posts to the IETF list,
>even though I would expect the list to use a free channel to distribute
>the result.
>
>I don't believe there is any right to free mail or email service so I
>don't see a reason to be overly concerned that a user of a community
>computer can't send free email. In addition to the free email channel
>which would have to continue to exist, providers of 'no charge' email
>services such as the bottom end Yahoo service could offer some number of
>free stamps per month combined with credits I suggested for receiveing
>postage paid mail, folks with marginal economic situations should be able
>to participate in email.
>
>Dave Morris
>
>On Wed, 28 May 2003, S Woodside wrote:
>
> >
> > On Tuesday, May 27, 2003, at 08:51  PM, J. Noel Chiappa wrote:
> >
> > > Which is precisely why I say that the solution to spam is to charge for
> > > email. It avoids the whole question of defining what is and is not
> > > spam.
> > >
> > > More specifically, change the email protocol so that when email
> > > arrives from
> > > an entity which is not on the "email from these entities is free"
> > > list, the
> > > email is rejected unless is accompanied by a payment for $X (where X
> > > is set
> > > by a knob on the machine).
> >
> > This would be unfortunate for people who do not have a lot of money.
> > Even if the payment were miniscule, 0.01$ or whatever, the payment
> > system might require a bank account, or a credit card, etc., to
> > participate in. That would effectively block out a substantial
> > percentage of the earth's population, people who use community centres,
> > libraries, schools, etc. for free access or internet cafes for cheap
> > occasional access.
> >
> > simon
> >
> > --
> > www.simonwoodside.com -- 99% Devil, 1% Angel
> >
> >
> > _______________________________________________
> > This message was passed through ietf_censored@carmen.ipv6.cselt.it, which is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on what to pass are made solely by Raffaele D'Albenzio.
> >




From owner-ietf@ietf.org  Wed May 28 16:55:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23108
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 16:55:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L7d5-0003sq-H0
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 16:34:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L7FT-0002RO-85
	for ietf@asgard.ietf.org; Wed, 28 May 2003 16:10:11 -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 QAA21274
	for <ietf@ietf.org>; Wed, 28 May 2003 16:10:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L7Dt-0007Br-00
	for ietf@ietf.org; Wed, 28 May 2003 16:08:33 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L7Ds-0007Bl-00
	for ietf@ietf.org; Wed, 28 May 2003 16:08:32 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S2968E> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 28 May 2003 13:10:08 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: spam
Date: Wed, 28 May 2003 13:10:11 -0700
Message-ID: <014d01c32555$250d1c90$56144104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <06af01c32549$43a84f50$0a00000a@atkielski.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA23108

Anthony Atkielski wrote:
> Public-key encryption of an entire e-mail is extremely 
> processor-intensive. 

Which is precisely the goal. It is not so extreme as to make routine
mail unusable, but extreme enough to make random bulk mail not worth the
cost.

> Even conventional encryption is very 
> time-consuming.  You can just hash it and sign the key.

That simply provides message integrity, the point is to make the cost
for the bulk sender higher than for the individual receiver. 

> 
> However, this would be a problem for people in countries that 
> outlaw encryption.  What would they do?

Break the law, because it is likely they are anyway for anything that
those laws are designed to prevent. ;)

Realistically, those situations would be addressed by including a plain
text copy as well. The agency concerned about enforcing encryption laws
could run the plain text part through the same encryption process and
verify that the output matches. Alternatively, the origin could be
required to encrypt using the enforcement agency key, then have the
enforcement point decrypt & re-encrypt with the receiver's key. Either
way there is enough pain felt at the enforcement point to ensure any
random bulk spam is dealt with locally and quickly.

> 
> > ... and provide an incentive for the ISPs to
> > actually deploy a PKI.
> 
> Who would you trust to certify keys?

For the purpose of email through the ISP servers, the ISP would be able
to handle key certification. Those keys may or may not be useful or
meaningful outside the context of services arranged by that ISP. 

Tony





From owner-ietf@ietf.org  Wed May 28 17:09:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24165
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 17:09:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L7d7-0003xl-74
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 16:34:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L7Ju-0003C2-RO
	for ietf@asgard.ietf.org; Wed, 28 May 2003 16:14:46 -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 QAA21715
	for <ietf@ietf.org>; Wed, 28 May 2003 16:14:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L7IK-0007Jw-00
	for ietf@ietf.org; Wed, 28 May 2003 16:13:08 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L7II-0007Jt-00
	for ietf@ietf.org; Wed, 28 May 2003 16:13:06 -0400
Received: from [63.202.92.152] (adsl-63-202-92-152.dsl.snfc21.pacbell.net [63.202.92.152])
	(authenticated bits=0)
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h4SKEdAG065252
	for <ietf@ietf.org>; Wed, 28 May 2003 13:14:40 -0700 (PDT)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p0521064dbafac8bd8afd@[63.202.92.152]>
In-Reply-To: <013801c32548$1139a790$56144104@eagleswings>
References: <013801c32548$1139a790$56144104@eagleswings>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Wed, 28 May 2003 13:14:38 -0700
To: ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: RE: spam
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 11:36 AM -0700 5/28/03, Tony Hain wrote:
>The external mechanisms already exist to deal with the
>social engineering once the originator can be pinned down.

This is good to hear. I thought that the international trusted 
micropayments that would be needed for such a sender-pays system was 
a problem that was yet to be solved.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Wed May 28 17:13:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24367
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 17:13:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L7sS-0004Kr-G0
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 16:50:28 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L7ca-0003pk-FI
	for ietf@asgard.ietf.org; Wed, 28 May 2003 16:34:04 -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 QAA22471
	for <ietf@ietf.org>; Wed, 28 May 2003 16:34:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L7b0-0007Vs-00
	for ietf@ietf.org; Wed, 28 May 2003 16:32:26 -0400
Received: from vrx.net ([216.13.126.22] helo=ns1.vrx.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L7aw-0007Vk-00
	for ietf@ietf.org; Wed, 28 May 2003 16:32:23 -0400
Received: from [192.168.1.14] (lsanca1-ar47-4-33-128-181.lsanca1.dsl-verizon.net [4.33.128.181])
	by ns1.vrx.net (Postfix) with ESMTP
	id C42EBD4CF; Wed, 28 May 2003 16:33:29 -0400 (EDT)
Mime-Version: 1.0
X-Sender: steflist@vrx.net
Message-Id: <v04220806bafac9e6d5e9@[192.168.1.14]>
In-Reply-To: <3ED50675.72DA7BFC@earthlink.net>
References: 
 <DAC3FCB50E31C54987CD10797DA511BA036BE50E@WIN-MSG-10.wingroup.windeploy.nt
 dev.microsoft.com> <3ED50675.72DA7BFC@earthlink.net>
Date: Wed, 28 May 2003 13:33:22 -0700
To: pdeutsch@earthlink.net
From: Einar Stefferud <Steflist@thor.nma.com>
Subject: Re: A peer-to-peer trust system model (was: Re: spam)
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

Hello  Peter --

I hate to be the one to tell you that the following is provably false:

"The unlying (sic) assumption here is that trust is a transitive relationship," 

Which leaves a bit of a gapping hole in your entire logical build...

"A trusts B" and "B trusts C"  does not imply anything about "A trusting C".

Even though you might decide to act on this assumption, believing it is true.

If trust is as transitive as you suggest, then it must also be true that if:
A trust B, and B trust C, and C trust D, and ... ; then A must also trust Z.

When you prover the latter true, then you have a chance at correctness: 
But even that is only true for a chain of 25 relationships.

If this assumption is true, then you must be a very gullible person, 
which I somehow seriously doubt;-)...

Cheers...\Stef

At 11:56 -0700 5/28/03, Peter Deutsch wrote:
>g'day,
>
>Christian Huitema wrote:
>...
> > There is an obvious issue with the protocol route: from a protocol point
> > of view, it is quite hard to distinguish unsolicited commercial e-mail,
> > which we would label spam, and unsolicited acceptable e-mail, which
> > could be more than welcome.
>
>I've sat on this posting, give both the previous volume of the thread,
>and the danger of getting too far into implementation discussions on a
>general list, but I've seen several postings to the effect that "it's
>hard to see what we could do at the protocol level". Personally, I think
>the problem would benefit from a little lateral thinking, so here's my
>cut at it. Those who tire of my ramblings, and don't want a quote from
>Tom Lehrer and allusions to Queen Elizabeth and Francis Drake, should
>hit "n" now...
>
>
>Concepts such as Hashcash or other payment-oriented systems, in which
>you try to impose a cost on the sender to screen out bulk mailers, are
>interesting enough, but I think they're addressing the wrong problem.
>I've personally come to the conclusion that to address this problem
>(that is, the decision as to whether I want to accept a message from
>you), I don't actually need to know who you are, or even what you're
>trying to send me, and I certainly don't need to impose artificial costs
>on you (since this looks too much like punishing the innocent for the
>crimes of the guilty).
>
>The heart of the issue seems to be:
>
>    What I really need to decide is whether I
>    should trust you enough to start accepting
>    unsolicited email from you (or more generally,
>    to start interacting with you for purpose x).
>
>
>I don't know what Paul Vixie meant by his allusion to a
>trusted-introducer model but I'd love to hear more about that, since
>I've been working on something that sounds a lot like that and I'd like
>to compare notes and seem how much reinventing of the wheel I'm
>currently doing (and to thrash the deceased equine a bit, mail I sent to
>him died in his maze of twisty little email filters, all the same, so we
>seem to have yet another existance proof that this problem is imposing
>costs on us and hurting our ability to use the Internet for useful work.
>To quote Tom Lehrer, "but I digress").
>
>
>One way I can learn whether I want to interact with you is to invest
>some time building up a trust relationship with you (verifying you are
>who say you are, etc). Another way would be for me to ask people I
>already trust who might know you to issue you a reference.
>
>My conclusion is that we need something along the lines of a
>peer-to-peer trust authentication token system which would allow the
>first time caller to authenticate him/herself to new MTAs by allowing
>him/her to demonstrate his/her prior participation in existing trust
>relationships. The idea is to build something more oriented towards
>peer-to-peer relationship building, rather than the traditional PKI
>central authority model we've seen so far.
>
>In practice, I imagine it would be most practical, if we want to
>interact with the traditional store-and-forward email system, for my
>friends to issue signed, non-forgable "trust tokens" (I think I called
>them "letters of marque" in a recent posting, since they convert
>"pirates" to "honest businessmen and women", just as Queen Elizabeth did
>with Francis Drake... ;-) The redeemer would hand a set of these trust
>tokens to me on first contact (you could embed them in the mail header,
>or we'd negotiate which trust tokens I accept when you connect, or I'd
>publish a list in "son-of-DNS" which trust groups I'm currently
>trusting, etcetcetc).
>
>When I receive such a {set of) trust token{s}, I'd check them to see if
>they really do come from folks I trust and otherwise satisfy my current
>policy requirements (e.g. I may need at least three valid tokens, or I
>may need at least two, including one from somebody in Sweden, etc), and
>if so I could start granting the bearer interaction privileges. *** The
>unlying assumption here is that trust is a transitive relationship, *** 
>and thus I'd allow myself to build up webs of such trust relationships
>by accepting references and references from references, so I wouldn't
>have to rely solely on a single, centralized PKI infrastructure.
>
>Now, in practice, I'd like to be able to adjust my policies based upon
>the qualitity of your references (say, requiring x references from group
>a, but only y references from group b to begin transacting). This has
>the beneficial side effect of putting the policy decision making into
>the hands of the grantor of privileges. All I require from the issuer of
>certificates are that I can prove they come from the issuer, and that
>they contain certain information (such as issuer, issue date, TTL, etc)
>- the decision about what to do when they're valid rests with the
>redeemer.
>
>Obviously I'd also need to be able to issue my own letters of marque,
>once I've developed sufficient trust in you (say, after I've experienced
>z satisfactory interactions without incident, or maybe when I click a
>button in my MUA because I like what I'm getting). Instinct tells me
>this "degree of good behaviour" could be quantified and automated, but
>"electing to start trusting" is not something you need to do on every
>message so need not be computationally easy. As a sidebar, the policies
>I use in granting my trust certificates would go far in determining to
>what degree they have later redemption value for others.
>
>And finally, I'd like these letters of marque to be revocable in
>something close to real time, since sometimes you get it wrong, and
>sometimes folks go bad. This doesn't necessarily mean I want to be
>contacted for every redemption (in fact, sometimes this will be
>impractical) but assigning such tokens a TTL and/or a refresh time and
>otherwise allowing some controls over redemption policy seems to be a
>good idea.
>
>Signing a record consisting of an ID, date and some other useful data
>with a private key seems to be just the ticket here, since it can be
>rapidly decrypted and checked but not easily forged. There is probably a
>lot more to it that this, since I probably don't care much about the
>cost of signing (something I wont do every interaction, only when
>agreeing to issue a new letter of marque) but I definitely want forging
>to be hard, and verifying to be cheap. This is classic public key stuff,
>although it looks like it would be seful if you could show *both* that
>you're Alice, *and* that you're a member of a specific group (ie. you
>need to transmit two secrets, one you own and one you share with your
>"trust buddies". This may be nothing more than using a group key to sign
>your ID within your token (making it a secret shared only by the turst
>ring), but it might also be nice if you can perhaps automatically get
>the group secret when you've been accepted by enough members of the
>group.
>
>I remember work from the crypto community about sharing n parts of a
>secret (that is, you need at least n parts of the secret to recreate it)
>that could be relevant here, although I haven't gone back and tracked it
>down yet. The idea would be that as you collect references, you collect
>pieces of the secret and when enough folks trust you, you have the info
>needed to start generating and issuing your own certificates as part of
>the club. In my notes on this, I make reference to being able to
>"blackball" a potential member, since issuing him an invalid token in
>effect keeps him out of the club. This area needs more thought, but it
>holds the promise of automating the implementation of membership
>management, which could be nice...
>
>
>I'm still chewing on what's suitable stuff to put into the token, but it
>lends itself to a fair number of things, when you think about it. You
>might add in there info about which domains to allow, which user names,
>which protocols to allow, etc. The idea is to delineate the areas and 
>scope for which trust would apply.
>
>The storage of the needed public keys probably could go into a "son of
>DNS" easily enough. Extensions to SMTP to request and redeem tokens
>obviously would need some thought, although I suspect you could embed
>the tokens in the mail header easily enough and thus perhaps not have to
>mess with the wire protocol at all, at least in initial implementations
>(you'd still need some way of requesting and/or issuing new trust
>tokens, but that could be taken out-of-band to another protocol).  It
>might even be better to make this a part of a whole new protocol, since
>as Paul points out, the current architecture appears to have some
>fundamental flaws and it may be time to stop patching it up and get on
>with the new architecture. This is where I'd like to  calibrate myself
>against what Paul alluded to, to see where he was going with that.
>
>Note that this idea would have some interesting side effects (or should
>I call them "social effects"?) You begin life in a cold, dark, lonely
>world with little trust and less functionality but over time, you build
>up useful relationships which can serve you well. Your "coin of the
>realm" here is your own credibility, so trying to pass forged trust
>tokens rapidly pollutes your swimming pool, while valuable trust
>relationships would suck in more trustworthy folks and benefit from
>positive networking effects. Today's great mailing list would be
>tomorrow's "trust ring", where any mail from anyone trusted by your
>"list buddies" is accepted, mail from random Taiwanese MTAs is rejected
>or tarpitted.
>
>The guy who issues the certificates that start the flood of spam into
>your mailbox gets deprecated as an authority with a click of a button.
>The spammer (or legitimate stranger) who can't prove his bone fides gets
>shunted to the slow lane over near the tarpits until he can prove
>himself over time. And over time, you can elect to promote well-behaved
>strangers to friends, expanding your trust ring.
>
>My instinct tells me there's something here worth pursuing, given the
>magnitude and growth rate of the current spam problem, but I doubt that
>the IETF general mailing list is a place to work on this, so I'm
>interested to see where the discussion  goes once the flames die
>down....
>
>As I said, I've done some digging and found nothing exactly like this,
>but Paul's casual remark suggests I'm missing something basic in the
>literature (admittedly I haven't done an exhaustive search yet).
>Pointers to the obvious work, or pointers to the obvious holes, would be
>most welcome. And of course, pointers to the best mailing list for
>follow-ups are probably a *really* good idea....
>
>
>
>                        - peterd
>
>
>
>
>
>-- 
>---------------------------------------------------------------------
>    Peter Deutsch                       pdeutsch@gydig.com
>    Gydig Software
>
>                        "Bungle..."
>               "That's an 'i', you idiot..."
>                  "Oh, right. 'Bingle..."
>
>                            - Red versus Blue...
>
>---------------------------------------------------------------------




From owner-ietf@ietf.org  Wed May 28 17:23:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24687
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 17:23:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L8C4-00060p-Iv
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 17:10:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L7kq-00047f-LB
	for ietf@asgard.ietf.org; Wed, 28 May 2003 16:42:36 -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 QAA22688
	for <ietf@ietf.org>; Wed, 28 May 2003 16:42:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L7jG-0007Zl-00
	for ietf@ietf.org; Wed, 28 May 2003 16:40:58 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L7jG-0007Zh-00
	for ietf@ietf.org; Wed, 28 May 2003 16:40:58 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id QAA01084;
	Wed, 28 May 2003 16:39:06 -0400
Date: Wed, 28 May 2003 16:40:10 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Rick Wesson <wessorh@ar.com>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <Pine.LNX.4.33.0305281301010.27483-100000@flash.ar.com>
Message-ID: <Pine.LNX.4.44.0305281617220.7861-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

We are not going to agree.

Those who sincerely want to reduce spam are going to have to choose their
leadership: Those who brought them to technical and political failure, or
those who understand the issues that can be successfully promoted, as I
did as President of the League for Programming Freedom in the 90s.

If it is as I say, and the costs you assert are irrelevant, then you will
lose. If I am wrong, you really should have won in 1998.  No doubt the
1998 leaders think that.  No one has disputed that the costs of spam were
in fact higher in 1998 than they are now. Obviously, you had a stronger
case on the cost issue then, than now.  So, are you going to trust them
again?

Your procmailrc won't have any more effect on that issue now than it did
in 1998, after I was shouted down in 1997.  Same story, different day.
If people are so foolish as to follow Vixie and his crew again, same
result.  We will see.

Shannon's Theorem isn't a popularity contest. It is either applies to
spam, or it doesn't. True or false.  If true, it means your protocol
efforts are a waste of time.  It isn't going to go away, despite your
procmailrc.

If it is false, then I have to wonder why SMTP AUTH didn't have any effect
on spam.  Perhaps, like I alluded, the authors lost focus. I suppose that
could be the case.  Time will reveal the truth of that as well.

But no one has offered any explanation of why Shannon's Theorem doesn't
apply. They have just arm waved that it could be related to Godel's work
on Set Theory. I suppose just about any computer or information science
theorem must be "a relative of Godel's work on Set Theory". This doesn't
prove it is either wrong, or doesn't apply to the development of a
spam-free protocol. (The very name spam-free protocol sounds ridiculous).

Unless someone has something new to say, I don't see anything else to say.
People will have to decide for themselves, and take the appropriate
personal action: Start work on a "spam-free protocol", or contact me
off-list to work on productive anti-spam lobbying and start working with
the IETF to prevent standarization of gratuitous protocol changes.

		--Dean

On Wed, 28 May 2003, Rick Wesson wrote:

>
> dean a small note before i add you to my procmailrc
>
> >
> > On Wed, 28 May 2003, Eric A. Hall wrote:
> >
> > > You still don't seem to understand the nature of proof, arguing instead
> > > that the existence of alternatives somehow disproves a matter of fact.
> > > Again, whether or not you think that the proof is significant is a matter
> > > of opinion, not a matter of proof.
> >
> > This is exactly true of your position, but not mine.  Seems you are
> > looking in a mirror.
> >
> > * Shannon's theorem is a fact, not an opinion.
> >
> > * The cost of disks and networks are facts, not opinions.
> >
> > * The cost of spam is a fact deduced from the costs on disks, networks and
> > computers. It is a fact, not an opinion.
> >
> > * Anti-spammers already tried to use "costs" in 1998, and lost, when
> > disks, networks, and computers were much more expensive. That is a fact,
> > not an opinion.
> >
> > Email, and thus spam, is practically a free service.  Spam costs
> > practically nothing.   That is a conclusion based on fact, not opinion.
> >
>
> your conclusion is incorrect, we have to pay sysadmins to keep spam out of
> our mail boxes and in some cases prefessional services to keep spam out of
> mailboxes that are real important.
>
> just as my paper shredder and the electricity to run it cost me to process
> junk mail and garbage service to throw away the trash. buring it is not an
> option in my fair city.
>
> if you wish to continue draw conslusions through falty analysis you may
> land in my filters...
>
>
> -rick
>
>
>
>
>
>




From owner-ietf@ietf.org  Wed May 28 17:24:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24738
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 17:24:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L8C4-000616-SN
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 17:10:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L7oO-0004AI-Vg
	for ietf@asgard.ietf.org; Wed, 28 May 2003 16:46:17 -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 QAA22756
	for <ietf@ietf.org>; Wed, 28 May 2003 16:46:14 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L7mo-0007bP-00
	for ietf@ietf.org; Wed, 28 May 2003 16:44:38 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L7mo-0007bM-00
	for ietf@ietf.org; Wed, 28 May 2003 16:44:38 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h4SKkC0N011140;
	Wed, 28 May 2003 16:46:12 -0400
Message-Id: <200305282046.h4SKkC0N011140@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Re: spam 
In-Reply-To: Your message of "Wed, 28 May 2003 15:12:06 EDT."
             <Pine.LNX.4.44.0305281507320.7861-100000@commander.av8.net> 
References: <Pine.LNX.4.44.0305281507320.7861-100000@commander.av8.net>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1930498787P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 28 May 2003 16:46:12 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_1930498787P
Content-Type: text/plain; charset=us-ascii

On Wed, 28 May 2003 15:12:06 EDT, Dean Anderson said:
> Type 1 spammers don't take that "discount". When they do, we make them
> pay.

On Wed, 28 May 2003 15:00:39 -0400, Dean Anderson said:
> Email, and thus spam, is practically a free service.  Spam costs
> practically nothing.   That is a conclusion based on fact, not opinion.

What a strange and interesting world you live in, Dean.  You simply *MUST*
write a guidebook so you can promote tourism there.

Alternatively, if spam is free, what exactly *do* the spammers pay, and
to whom?

--==_Exmh_1930498787P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+1SATcC3lWbTT17ARAiUuAKDTXPXK8hoOzBaGgeHzMtimRrlYqwCgsoH8
/bvBOps+bGnC2DhT/JyOb9c=
=UoN7
-----END PGP SIGNATURE-----

--==_Exmh_1930498787P--



From owner-ietf@ietf.org  Wed May 28 18:04:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25904
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 18:04:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L8fA-0001b6-Jj
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 17:40:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L8a1-0001QH-8e
	for ietf@asgard.ietf.org; Wed, 28 May 2003 17:35:29 -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 RAA25287
	for <ietf@ietf.org>; Wed, 28 May 2003 17:35:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L8YR-0000TQ-00
	for ietf@ietf.org; Wed, 28 May 2003 17:33:51 -0400
Received: from [208.184.79.11] (helo=clint.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L8YQ-0000TK-00
	for ietf@ietf.org; Wed, 28 May 2003 17:33:50 -0400
Received: from bbprime (208.184.79.253.songbird.com [208.184.79.253] (may be forged))
	by clint.songbird.com (8.11.6/8.11.6) with ESMTP id h4SLbgi26182;
	Wed, 28 May 2003 14:37:42 -0700
Date: Wed, 28 May 2003 14:34:53 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <8221498523.20030528143453@brandenburg.com>
To: "Tony Hain" <alh-ietf@tndh.net>
CC: "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <02b001c32497$0c11a350$2a134104@eagleswings>
References: <02b001c32497$0c11a350$2a134104@eagleswings>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony,

TH> With this type of policy, the operations community is dictating which
TH> applications can be run from specific ranges of IP addresses.

Does an ISP have a *right* to specify what applications may be run by
their customers?

Well, certainly an ISP has a right to make specifications concerning
consumption of the ISP's resources, and restrictions of applications
might be seen as falling under this.

That said, yes, this is about as dumb as an ISP's rules can get.
Certainly as cynical and possibly as manipulative.

The question is what the IETF can or should do about bad ISP customer
policies, when those policies do not cause operations problems for the
rest of the Internet?



d/

ps.  When AOL, MSN and Yahoo announced that they were going to lead an
initiative for spam control, it *did* occur to me that the policies that
might be tolerable for their mass-market customers would be entirely
inappropriate and damaging to the rest of the Internet's user base.

--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Wed May 28 18:20:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27618
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 18:20:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L8yF-00028Z-Pr
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 18:00:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L8gn-0001dB-8S
	for ietf@asgard.ietf.org; Wed, 28 May 2003 17:42:29 -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 RAA25417
	for <ietf@ietf.org>; Wed, 28 May 2003 17:42:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L8fD-0000Uj-00
	for ietf@ietf.org; Wed, 28 May 2003 17:40:51 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L8fC-0000Uf-00
	for ietf@ietf.org; Wed, 28 May 2003 17:40:50 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id RAA31669;
	Wed, 28 May 2003 17:39:43 -0400
Date: Wed, 28 May 2003 17:40:47 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Valdis.Kletnieks@vt.edu
cc: ietf@ietf.org
Subject: Re: spam 
In-Reply-To: <200305282046.h4SKkC0N011140@turing-police.cc.vt.edu>
Message-ID: <Pine.LNX.4.44.0305281705040.7861-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Now you are just being obtuse.  But if travel brochures will help you come
to the real world, you should just log off and go outside for a bit.

Spammers pay for their connection, just like telemarketers, and for that
matter, just like Junk Mailers and anyone else.

But the costs of Junk Mail and telemarketing on either infrastructure or
the recipient were not issues, even though those "costs" are obviously
higher than the corresponding spam costs. It takes more time to take out
the trash, and to answer and hang up the phone, than it does to delete a
spam.  It costs the telephone companies much more to complete a
telemarketing call than it costs ISPs to transport a spam. And it costs
the post office way more to deliver junk mail.

You want to focus exclusively on the Junk Fax law, and take it out of
context, and just completely make up issues (infrastructure costs on
telecoms) that weren't in its passage.

As I've pointed out, the Junk Fax law was unique due to the fact that
unlike either spam, junk postal mail, or telemarketing, faxes consume the
*recipients* paper, and consume the *recipients* ink, and causes the
*recipient* to run out of paper.  This is a unique characteristic to junk
fax, which doesn't apply to spam, or telemarketing, or junk mail.  Junk
faxes don't just borrow the paper, or borrow the use of the answering
machine.  They *consume* the paper and the ink.  And having consuming
these limited resources, they aren't available for other purposes.  Thus,
there is a government interest in the utilization of those resources.

Whatever your hopes otherwise, they are not realistic.

My point (the goal of this whole discussion) is that you simply can't just
hope to wave your arms, quote some impressive numbers about infrastructure
costs, and win by shouting down your opponents. It doesn't work that way
in the world outside mailing lists.  Your opponents are going to analyze
your numbers, point out the irrelevancies and inconsistencies, and
untangle anything that is confusing while you are forced to sit quietly.

And if you somehow lie to the FTC, and get the FTC to exclude your
opponents, as happened recently, they will eventually find out, and that
misinformation will be corrected.  And the antispammers are discredited
(as a consequence of actions by radicals).  Moderates are always expected
to reign in (and rat out) the radicals, whether they anti-spammers,
palestinians, or jewish settlers.  You can be absolutely sure that this
won't happen in Congress, where the DMA maintains a presence.

		--Dean

On Wed, 28 May 2003 Valdis.Kletnieks@vt.edu wrote:

> On Wed, 28 May 2003 15:12:06 EDT, Dean Anderson said:
> > Type 1 spammers don't take that "discount". When they do, we make them
> > pay.
>
> On Wed, 28 May 2003 15:00:39 -0400, Dean Anderson said:
> > Email, and thus spam, is practically a free service.  Spam costs
> > practically nothing.   That is a conclusion based on fact, not opinion.
>
> What a strange and interesting world you live in, Dean.  You simply *MUST*
> write a guidebook so you can promote tourism there.
>
> Alternatively, if spam is free, what exactly *do* the spammers pay, and
> to whom?
>




From owner-ietf@ietf.org  Wed May 28 18:59:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28649
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 18:59:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L9Ho-0001qC-QC
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 18:20:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L9Do-00015c-Et
	for ietf@asgard.ietf.org; Wed, 28 May 2003 18:16:36 -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 SAA27502
	for <ietf@ietf.org>; Wed, 28 May 2003 18:16:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L9CE-0000kP-00
	for ietf@ietf.org; Wed, 28 May 2003 18:14:58 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L9CD-0000kM-00
	for ietf@ietf.org; Wed, 28 May 2003 18:14:57 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S296C9> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 28 May 2003 15:16:32 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Dave Crocker'" <dcrocker@brandenburg.com>
Cc: "'IETF'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Wed, 28 May 2003 15:16:32 -0700
Message-ID: <017601c32566$cb6fcea0$56144104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <8221498523.20030528143453@brandenburg.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA28649

Dave Crocker wrote:
> Tony,
> 
> TH> With this type of policy, the operations community is dictating 
> TH> which applications can be run from specific ranges of IP 
> addresses.
> 
> Does an ISP have a *right* to specify what applications may 
> be run by their customers?

Not if it simultaneously wants protection from liability for any content
that the customer might be sending. The ISP is either an immune carrier
of content, or in the content management business, not both. The
transport protocol id and everything past it are only really meaningful
to the endpoints, so that qualifies as content. More below.

> 
> Well, certainly an ISP has a right to make specifications 
> concerning consumption of the ISP's resources, and 
> restrictions of applications might be seen as falling under this.

The lines that were crossed here are guilt-by-association, and the
declaration by one ISP that an entire class of another ISPs customers do
not have the right to run a particular app. 

In context, it is clearly the right of a mail server operator to refuse
mail. My concern is more about the precedent where a large ISP decides
that address ranges have particular application semantics. 

> 
> That said, yes, this is about as dumb as an ISP's rules can 
> get. Certainly as cynical and possibly as manipulative.
> 
> The question is what the IETF can or should do about bad ISP 
> customer policies, when those policies do not cause 
> operations problems for the rest of the Internet?
> 

The IETF needs to recognize that the ISPs don't really have a good
alternative, and work on providing one. If they have an alternative and
continue down the path, you are right there is not much the IETF can do.
At the same time, market forces will fix that when customers move to the
ISP that implements the alternative.

> 
> 
> d/
> 
> ps.  When AOL, MSN and Yahoo announced that they were going 
> to lead an initiative for spam control, it *did* occur to me 
> that the policies that might be tolerable for their 
> mass-market customers would be entirely inappropriate and 
> damaging to the rest of the Internet's user base.

MSN & Yahoo have not (yet?) implemented the address range controls. At
least I am not getting any bounces, while my wife is active on a couple
of Yahoo groups and I can still send mail to my MSN account. 

Tony






From owner-ietf@ietf.org  Wed May 28 19:28:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29483
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 19:28:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L9pN-0002aY-Rg
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 18:55:25 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L9VJ-00021S-Jv
	for ietf@asgard.ietf.org; Wed, 28 May 2003 18:34:41 -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 SAA28101
	for <ietf@ietf.org>; Wed, 28 May 2003 18:34:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L9Tj-0000sM-00
	for ietf@ietf.org; Wed, 28 May 2003 18:33:03 -0400
Received: from tomts15.bellnexxia.net ([209.226.175.3] helo=tomts15-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L9Ti-0000sJ-00
	for ietf@ietf.org; Wed, 28 May 2003 18:33:02 -0400
Received: from yahoo.com ([65.93.181.225]) by tomts15-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030528223433.MBYN5719.tomts15-srv.bellnexxia.net@yahoo.com>;
          Wed, 28 May 2003 18:34:33 -0400
Date: Wed, 28 May 2003 18:34:32 -0400
Subject: Re: requiring payment (was spam)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: <ietf@ietf.org>
To: David Morris <dwm@xpasc.com>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <Pine.LNX.4.33.0305281033360.865-100000@egate.xpasc.com>
Message-Id: <8D73F39C-915C-11D7-8571-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Wednesday, May 28, 2003, at 01:42  PM, David Morris wrote:

> In the USA today, it costs $.37 to send a physical mail. I don't think 
> it
> unreasonable for someone sending me mail to pay a similar fee and
> conversely for me to pay such a fee for each of my posts to the IETF 
> list,
> even though I would expect the list to use a free channel to distribute
> the result.

Really? I email with people who would not be able to afford $.37 to 
send me an email. (They live developing nations.)

> I don't believe there is any right to free mail or email service so I
> don't see a reason to be overly concerned that a user of a community
> computer can't send free email.

But consider that the internet today is based on widely available free 
email. There would be major changes to the whole email dynamic if that 
changed. Besides people who have different economics at work, Another 
that comes to mind is people who use email interfaces to websites, 
maybe because they're firewalled at work, or they can only use a 
store-and-forward system if they on a sufficiently remote / slow link 
(in a very remote area, this could include researchers as well as 
people who simply live in a very rural place).

simon




From owner-ietf@ietf.org  Wed May 28 19:30:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29648
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 19:30:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19L9pO-0002dA-KI
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 18:55:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19L9pA-0002Wj-K2
	for ietf@asgard.ietf.org; Wed, 28 May 2003 18:55:12 -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 SAA28558
	for <ietf@ietf.org>; Wed, 28 May 2003 18:55:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19L9na-0000xb-00
	for ietf@ietf.org; Wed, 28 May 2003 18:53:34 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19L9nZ-0000xW-00
	for ietf@ietf.org; Wed, 28 May 2003 18:53:33 -0400
Received: from localhost (dwm@localhost)
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h4SMlvB05999;
	Wed, 28 May 2003 15:47:58 -0700
Date: Wed, 28 May 2003 15:47:57 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: Einar Stefferud <Steflist@thor.nma.com>
cc: <ietf@ietf.org>
Subject: Re: requiring payment (was spam)
In-Reply-To: <v04220805bafac4f8ad58@[192.168.1.14]>
Message-ID: <Pine.LNX.4.33.0305281505260.865-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Wed, 28 May 2003, Einar Stefferud wrote:

> Hello Dave Morris ---
>
> It would be helpful if you would explain how this payment system of
> yours might actually work in real life.

One model exists in the postal service operated 'by' each country. Stamps
exist, procedures exist for sharing revenue or whatever when, say, a US
Stamp is used to get mail delivered in Germany. Using the new protocols,
my MUA would drop the mail in the local post box ... the SMTPnew server I
use to send mail. That server would need to authenticate me and verify
that I have money or credit available. That server would be resonsible to
a local epostal clearing house for payment and would initiate delivery
transfer of the post paid email. Could be that an electronic stamp token
is included, generated with the servers private PKI key. It is possibly
reasonable in the current network to insist that all mail delivery be
point to point, but if not, intervening MXlike servers just move the
bundle along.  The final destination SMTPnew server verifies that the
proper postage is attached, mostly a PKI decryption exercise. The stamp
tokens are recorded in a database. Periodically, stamps would be
bundled and sent to the epostoffice, perhaps along with cash, to
get the local epostage meter recharged. Depending on the epostal cost
structure, perhaps each received stamp would be worth 1/2 of a to send
stamp. Based on local SMTPnew operator policy, end users might get 1/4 of
a stamp credit for each received email.

> Perhaps like TELEX worked before it died, with settlements between
> the first posing ISP to the last receiving ISP, with "settlement"
> payments spread across all ISPs in between.

As implied above, one or a few organizations per nation would provide
clearing services.


>
> Of course this leads to bilateral agreements among al the thousands of
> ISPs, and collective agreements among the mass of global ISPs.

No, only between the ISPs (where ISP means SMTPnew operator) and the
chosen epostal service. And then tiered between epostal services. Millions
of businesses today use postage meters, humble folks just by stamps.

> Now, consider the cost of such arrangements, to cover the frictional
> costs of just being in business, plus the required profit margins that
> accrue to any such massive payment shuffling.

Of course, there is a cost. And if you will, friction. A new PKI based
trust system will also have added 'frictional' costs to create and
support. My general approach provides a funding mechanism to pay those
costs on a per use basis.

>
> Everyone here advocating payments do not seem to understand the
> overhead costs of collecting and distributing the money.

I think I understand the costs quite well. One of the protocol design
challenges will to be minimize costs. Probably by appropriate tiering of
responsiblity and granularity of transactions recharging meters.


> Be careful of what you wish for! -- You just might get it!

Hooray!





From owner-ietf@ietf.org  Wed May 28 19:38:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29942
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 19:38:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LAQE-0004El-Jv
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 19:33:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LA5c-00039x-3i
	for ietf@asgard.ietf.org; Wed, 28 May 2003 19:12:12 -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 TAA29118
	for <ietf@ietf.org>; Wed, 28 May 2003 19:12:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LA41-00016c-00
	for ietf@ietf.org; Wed, 28 May 2003 19:10:33 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LA41-00016Z-00
	for ietf@ietf.org; Wed, 28 May 2003 19:10:33 -0400
Received: from localhost (dwm@localhost)
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h4SN57H06050
	for <ietf@ietf.org>; Wed, 28 May 2003 16:05:07 -0700
Date: Wed, 28 May 2003 16:05:07 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: <ietf@ietf.org>
Subject: Re: requiring payment (was spam)
In-Reply-To: <8D73F39C-915C-11D7-8571-000393414368@yahoo.com>
Message-ID: <Pine.LNX.4.33.0305281548440.865-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Simon,

I have repeatedly asserted that the current free SMTP service or
equivalent would be preserved. You could choose with any degree of
filtering you choose to accept postage free mail. You could choose to
only accept free mail or all free mail.

I frankly don't see random free mail as an important part of the internet
dynamic. People who who send email from work for personal perposes are
often violating published AUP, even if it is not enforced. They are often
using work time to do personal work. One of the 'hidden' costs of the
internet revolution which is likely to receive more focus over time. I
don't see any reason why protocol design should accomadate theft or
other violations of employer policies.

On Wed, 28 May 2003, S Woodside wrote:

>
> On Wednesday, May 28, 2003, at 01:42  PM, David Morris wrote:
>
> > In the USA today, it costs $.37 to send a physical mail. I don't think
> > it
> > unreasonable for someone sending me mail to pay a similar fee and
> > conversely for me to pay such a fee for each of my posts to the IETF
> > list,
> > even though I would expect the list to use a free channel to distribute
> > the result.
>
> Really? I email with people who would not be able to afford $.37 to
> send me an email. (They live developing nations.)
>
> > I don't believe there is any right to free mail or email service so I
> > don't see a reason to be overly concerned that a user of a community
> > computer can't send free email.
>
> But consider that the internet today is based on widely available free
> email. There would be major changes to the whole email dynamic if that
> changed. Besides people who have different economics at work, Another

You mean, no more spam? You mean the employers will have a better return
on their investment in payroll? You mean more thought before sticking ones
foot in the electronic mouth?

The point of this proposal is to change the dynamic of email by
associating a small but significant cost with sending mail to folks with
whom one has no established relationship.

> that comes to mind is people who use email interfaces to websites,
> maybe because they're firewalled at work, or they can only use a
> store-and-forward system if they on a sufficiently remote / slow link
> (in a very remote area, this could include researchers as well as
> people who simply live in a very rural place).

They have bigger problems than a charge for email, but if the web site
email server chooses, it can accept free email ... qed ... no problem.

Dave Morris




From owner-ietf@ietf.org  Wed May 28 20:02:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00457
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 20:02:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LAcN-0004pp-Jc
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 19:46:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LARp-0004GS-K4
	for ietf@asgard.ietf.org; Wed, 28 May 2003 19:35:09 -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 TAA29906
	for <ietf@ietf.org>; Wed, 28 May 2003 19:35:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LAQF-0001JC-00
	for ietf@ietf.org; Wed, 28 May 2003 19:33:31 -0400
Received: from sj-core-3.cisco.com ([171.68.223.137])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LAQE-0001J4-00
	for ietf@ietf.org; Wed, 28 May 2003 19:33:30 -0400
Received: from edison.cisco.com (edison.cisco.com [171.70.144.164])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h4SNYMAV014177;
	Wed, 28 May 2003 16:34:22 -0700 (PDT)
Received: from cisco.com (dhcp-171-71-119-122.cisco.com [171.71.119.122]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id QAA22471; Wed, 28 May 2003 16:34:22 -0700 (PDT)
Message-ID: <3ED5477D.5020004@cisco.com>
Date: Wed, 28 May 2003 16:34:21 -0700
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: alh-ietf@tndh.net
CC: "'Dave Crocker'" <dcrocker@brandenburg.com>, "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
References: <017601c32566$cb6fcea0$56144104@eagleswings>
In-Reply-To: <017601c32566$cb6fcea0$56144104@eagleswings>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony Hain wrote:
> The IETF needs to recognize that the ISPs don't really have a good
> alternative, and work on providing one. If they have an alternative and
> continue down the path, you are right there is not much the IETF can do.
> At the same time, market forces will fix that when customers move to the
> ISP that implements the alternative.

This is very well said.  That first sentence could arguably be the credo 
of the IETF, only perhaps not limiting to ISPs.

Eliot






From owner-ietf@ietf.org  Wed May 28 21:18:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01902
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 21:18:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LBcd-0006Q2-KI
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 20:50:23 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LBJ3-000663-2K
	for ietf@asgard.ietf.org; Wed, 28 May 2003 20:30:09 -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 UAA01074
	for <ietf@ietf.org>; Wed, 28 May 2003 20:30:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LBHS-0001cD-00
	for ietf@ietf.org; Wed, 28 May 2003 20:28:30 -0400
Received: from h-135-207-24-32.research.att.com ([135.207.24.32] helo=mailman.research.att.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LBHS-0001bu-00
	for ietf@ietf.org; Wed, 28 May 2003 20:28:30 -0400
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mailman.research.att.com (8.12.8/8.12.8) with ESMTP id h4T0Ow3j014673;
	Wed, 28 May 2003 20:24:58 -0400
Received: from berkshire.research.att.com (raptor.research.att.com [135.207.23.32])
	by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id h4T0TLV11697;
	Wed, 28 May 2003 20:29:21 -0400 (EDT)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id DB80B7B4D; Wed, 28 May 2003 20:29:20 -0400 (EDT)
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
To: Eliot Lear <lear@cisco.com>
Cc: alh-ietf@tndh.net, "'Dave Crocker'" <dcrocker@brandenburg.com>,
        "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 28 May 2003 20:29:20 -0400
From: "Steven M. Bellovin" <smb@research.att.com>
Message-Id: <20030529002920.DB80B7B4D@berkshire.research.att.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

In message <3ED5477D.5020004@cisco.com>, Eliot Lear writes:
>Tony Hain wrote:
>> The IETF needs to recognize that the ISPs don't really have a good
>> alternative, and work on providing one. If they have an alternative and
>> continue down the path, you are right there is not much the IETF can do.
>> At the same time, market forces will fix that when customers move to the
>> ISP that implements the alternative.
>
>This is very well said.  That first sentence could arguably be the credo 
>of the IETF, only perhaps not limiting to ISPs.

Yes.  Normally, I'd worry a lot about backwards compatibility.  In this 
case, I think the problems for ISPs -- and users -- are so severe that 
people will switch *rapidly* to a new protocol if it solved most of the 
spam problem.

My new concern is making sure that we get a *good* solution -- one that 
preserves privacy and the end-to-end principle, as well as blocking 
spam.

		--Steve Bellovin, http://www.research.att.com/~smb (me)
		http://www.wilyhacker.com (2nd edition of "Firewalls" book)





From owner-ietf@ietf.org  Wed May 28 21:53:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02556
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 21:53:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LCYY-0007Kg-BV
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 21:50:14 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LCGE-0007AQ-KJ
	for ietf@asgard.ietf.org; Wed, 28 May 2003 21:31:18 -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 VAA02259
	for <ietf@ietf.org>; Wed, 28 May 2003 21:31:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LCEe-0001te-00
	for ietf@ietf.org; Wed, 28 May 2003 21:29:40 -0400
Received: from [208.184.79.11] (helo=clint.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LCEd-0001tT-00
	for ietf@ietf.org; Wed, 28 May 2003 21:29:39 -0400
Received: from rshockeybox.shockey.us (h-69-3-5-197.MCLNVA23.covad.net [69.3.5.197])
	by clint.songbird.com (8.11.6/8.11.6) with ESMTP id h4T1XUi07197;
	Wed, 28 May 2003 18:33:30 -0700
Message-Id: <5.2.0.9.2.20030528212209.02965c60@shockey.us>
X-Sender: richard@shockey.us
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 28 May 2003 21:30:35 -0400
To: Dave Crocker <dcrocker@brandenburg.com>, "Tony Hain" <alh-ietf@tndh.net>
From: Richard Shockey <richard@shockey.us>
Subject: Re: The utilitiy of IP is at stake here
Cc: "'IETF'" <ietf@ietf.org>
In-Reply-To: <8221498523.20030528143453@brandenburg.com>
References: <02b001c32497$0c11a350$2a134104@eagleswings>
 <02b001c32497$0c11a350$2a134104@eagleswings>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

A
>That said, yes, this is about as dumb as an ISP's rules can get.
>Certainly as cynical and possibly as manipulative.
>
>The question is what the IETF can or should do about bad ISP customer
>policies, when those policies do not cause operations problems for the
>rest of the Internet?


In the short term let me plead once again ...

One question is what can or should individual members of the IETF do about 
bad US Congressional policies. In the absence of personal initiates by 
folks like us to Senators and Congressmen..let me assure you they will 
screw things up.

Its not that hard to write a letter, sign it with a return address and put 
a postage stamp on it or make a phone call to a local representatives office..

The US Congress is not very good a dealing with email ..trust me.

they like snail mail...



 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
Voice +1 571.434.5651 Cell : +1 703.593.2683,  Fax: +1 815.333.1237
<mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
  <http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<




From owner-ietf@ietf.org  Wed May 28 21:53:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02581
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 21:53:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LCAW-000786-Rr
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 21:25:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LC6E-00071v-SM
	for ietf@asgard.ietf.org; Wed, 28 May 2003 21:20:58 -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 VAA02087
	for <ietf@ietf.org>; Wed, 28 May 2003 21:20:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LC4e-0001qN-00
	for ietf@ietf.org; Wed, 28 May 2003 21:19:20 -0400
Received: from [208.184.79.11] (helo=clint.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LC4d-0001q3-00
	for ietf@ietf.org; Wed, 28 May 2003 21:19:19 -0400
Received: from bbprime (208.184.79.253.songbird.com [208.184.79.253] (may be forged))
	by clint.songbird.com (8.11.6/8.11.6) with ESMTP id h4T1Mei06356;
	Wed, 28 May 2003 18:22:40 -0700
Date: Wed, 28 May 2003 18:19:48 -0700
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: dcrocker@brandenburg.com
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <7534992907.20030528181948@brandenburg.com>
To: "Tony Hain" <alh-ietf@tndh.net>
CC: "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <017601c32566$cb6fcea0$56144104@eagleswings>
References: <017601c32566$cb6fcea0$56144104@eagleswings>
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-15
X-MIME-Autoconverted: from 8bit to quoted-printable by clint.songbird.com id h4T1Mei06356
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA02581

Tony and Steve, et al,

TH> In context, it is clearly the right of a mail server operator to refuse
TH> mail. My concern is more about the precedent where a large ISP decides
TH> that address ranges have particular application semantics. 
...
TH> The IETF needs to recognize that the ISPs don't really have a good
TH> alternative, and work on providing one.

and

SMB> Yes.  Normally, I'd worry a lot about backwards compatibility.  In this
SMB> case, I think the problems for ISPs -- and users -- are so severe that
SMB> people will switch *rapidly* to a new protocol if it solved most of the
SMB> spam problem.


Most of this thread is really about legal and customer service issues.
I do not see how it is an IETF topic, no matter how much each of us
might (and do) feel strongly about it.


However I'll join the ranks of those heartily supporting your
conclusion about the absence of good alternatives...

However there is a catch:

      With respect to spam, and many other content-related activities,
      what does it mean to provide a good alternative?

      To answer this means we need to understand the problem very well
      and understand the technical underpinnings of the problem very
      well.

It is easy to note features that are lacking from email, but dangerous
to assume that adding those features will result in their being adopted
or that their adoption will magically fix the problem at hand.

Worse is that, by and large, spam is a topic for which reasoned
discussion -- and especially careful analysis -- is so far proving
impossible in an open forum. Between the formal fuzziness of the topic,
the strong emotion it engenders, and the compulsive self-interest of
many constituencies, the reality is fragmented, heated exchanges, rather
than anything really productive.

Here are some realities that I think we must juggle:

1.  We do not understand the full range of email (ie, electronic
mediated human exchanges) very well at all;

2.  An installed base of 100 million users should be expected to adopt
changes very, very slowly

3. Each change will have large, unintended consequences, most of which
will be undesirable. (This statement is an absolute cliché in serious
discussions about organizational and social change.)

Note that the definition of spam largely depends upon the person making
the definition; unless and until we can develop of reasonably simple
definition that has a) broad acceptance, and b) a largely technical
basis, then it is pure folly for the IETF to think it can do anything
major in this arena.  It might be useful for us to standardize some relatively
straight tools, like a client/filter-server exchange protocol, but we
are not going to achieve really strategic improvements.

I should also note that the last two years have seen at least two
efforts to consider a replacement email service -- or at least an
alternative one -- but that neither seems to have achieved a critical
mass of interest.

And before anyone claims that spam will be the flag around which
Email(ng) troops will rally, I'll ask what changes anyone thinks are
required. As soon as anyone tries to answer that, everyone else should
watch the style of responses they get...

(if you want to save time, just look at the discussion of spam on the
ietf over the last few days. has it been analytic? has it been systemic?
has it been productive? -- except for the thread that Tony just started,
of course.)

d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Wed May 28 22:20:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03223
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 22:20:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LCvP-0008Jo-6P
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 22:13:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LCoU-0008GQ-QX
	for ietf@asgard.ietf.org; Wed, 28 May 2003 22:06:42 -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 WAA03021
	for <ietf@ietf.org>; Wed, 28 May 2003 22:06:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LCmu-00024m-00
	for ietf@ietf.org; Wed, 28 May 2003 22:05:04 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LCmt-00024g-00
	for ietf@ietf.org; Wed, 28 May 2003 22:05:03 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19LCoE-000IrE-00; Wed, 28 May 2003 21:06:26 -0500
Date: Wed, 28 May 2003 22:06:26 -0400
From: John C Klensin <john-ietf@jck.com>
To: Einar Stefferud <Steflist@thor.nma.com>, David Morris <dwm@xpasc.com>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: requiring payment (was spam)
Message-ID: <114782448.1054159586@p3.JCK.COM>
In-Reply-To: <v04220805bafac4f8ad58@[192.168.1.14]>
References: <Pine.LNX.4.33.0305281033360.865-100000@egate.xpasc.co
 m> <v04220805bafac4f8ad58@[192.168.1.14]>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Since Stef has chimed in here, let me point out one other aspect 
of payment systems, one that is more or less the corollary to 
his observation about bilateral agreements.  It is an 
interesting and useful property of the Internet email 
environment that we have SMTP servers all over the place, some 
of them operated at rather large scale and others operated at 
fairly small scale.   In general, anyone can send mail to anyone 
else.

But, as soon as one institutes either charging schemes or 
collections of bilateral agreements, there are huge incentives 
to created "hub systems" or "carriers" -- entities whose 
business it is to make agreements with lots of local 
providers/servers (whom they will come to call "customers") and 
bilateral agreements with each other.  Without that, everyone 
who wants to run a mail server has to either establish bilateral 
agreements with everyone else, or a regulatory regime becomes 
necessary to make the sequential settlement arrangements work. 
Economies of scale, if only in agreement-making, imply few 
enough, and large enough, carriers for governments to start 
taking interest on a "competition" or "anti-trust" or "consumer 
protection" basis.   Sorry to be pessimistic about this, but I 
think it quickly takes us where we don't want to go.

Quoting Stef, "be careful what you wish for..."

      john



--On Wednesday, 28 May, 2003 13:04 -0700 Einar Stefferud 
<Steflist@thor.nma.com> wrote:

> Hello Dave Morris ---
>
> It would be helpful if you would explain how this payment
> system of  yours might actually work in real life.
>
> Perhaps like TELEX worked before it died, with settlements
> between  the first posing ISP to the last receiving ISP, with
> "settlement"  payments spread across all ISPs in between.
>
> Of course this leads to bilateral agreements among al the
> thousands of  ISPs, and collective agreements among the mass
> of global ISPs.
>
> Now, consider the cost of such arrangements, to cover the
> frictional  costs of just being in business, plus the required
> profit margins that accrue to any such massive payment
> shuffling.
>
> Everyone here advocating payments do not seem to understand
> the overhead costs of collecting and distributing the money.
>
> Be careful of what you wish for! -- You just might get it!
>
> Cheers...\Stef







From owner-ietf@ietf.org  Wed May 28 22:53:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04014
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 22:53:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LDEa-0000am-VZ
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 22:33:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LDAc-0000VR-T9
	for ietf@asgard.ietf.org; Wed, 28 May 2003 22:29:34 -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 WAA03423
	for <ietf@ietf.org>; Wed, 28 May 2003 22:29:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LD92-0002At-00
	for ietf@ietf.org; Wed, 28 May 2003 22:27:56 -0400
Received: from vrx.net ([216.13.126.22] helo=ns1.vrx.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LD91-0002Aq-00
	for ietf@ietf.org; Wed, 28 May 2003 22:27:55 -0400
Received: from [192.168.1.14] (lsanca1-ar47-4-33-128-181.lsanca1.dsl-verizon.net [4.33.128.181])
	by ns1.vrx.net (Postfix) with ESMTP
	id 8382CD26D; Wed, 28 May 2003 22:29:29 -0400 (EDT)
Mime-Version: 1.0
X-Sender: steflist@vrx.net
Message-Id: <v04220808bafb208b4797@[192.168.1.14]>
In-Reply-To: <114782448.1054159586@p3.JCK.COM>
References: <Pine.LNX.4.33.0305281033360.865-100000@egate.xpasc.co m>
 <v04220805bafac4f8ad58@[192.168.1.14]> <114782448.1054159586@p3.JCK.COM>
Date: Wed, 28 May 2003 19:29:21 -0700
To: John C Klensin <john-ietf@jck.com>
From: Einar Stefferud <Steflist@thor.nma.com>
Subject: Re: requiring payment (was spam)
Cc: David Morris <dwm@xpasc.com>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

Thanks John for your support!

I think we should all be careful not to return to the good old days of Telex
bilateral agreements!

Cheers...\Stef

At 22:06 -0400 5/28/03, John C Klensin wrote:
>Since Stef has chimed in here, let me point out one other aspect of payment systems, one that is more or less the corollary to his observation about bilateral agreements.  It is an interesting and useful property of the Internet email environment that we have SMTP servers all over the place, some of them operated at rather large scale and others operated at fairly small scale.   In general, anyone can send mail to anyone else.
>
>But, as soon as one institutes either charging schemes or collections of bilateral agreements, there are huge incentives to created "hub systems" or "carriers" -- entities whose business it is to make agreements with lots of local providers/servers (whom they will come to call "customers") and bilateral agreements with each other.  Without that, everyone who wants to run a mail server has to either establish bilateral agreements with everyone else, or a regulatory regime becomes necessary to make the sequential settlement arrangements work. Economies of scale, if only in agreement-making, imply few enough, and large enough, carriers for governments to start taking interest on a "competition" or "anti-trust" or "consumer protection" basis.   Sorry to be pessimistic about this, but I think it quickly takes us where we don't want to go.
>
>Quoting Stef, "be careful what you wish for..."
>
>     john
>
>
>
>--On Wednesday, 28 May, 2003 13:04 -0700 Einar Stefferud <Steflist@thor.nma.com> wrote:
>
>>Hello Dave Morris ---
>>
>>It would be helpful if you would explain how this payment
>>system of  yours might actually work in real life.
>>
>>Perhaps like TELEX worked before it died, with settlements
>>between  the first posing ISP to the last receiving ISP, with
>>"settlement"  payments spread across all ISPs in between.
>>
>>Of course this leads to bilateral agreements among al the
>>thousands of  ISPs, and collective agreements among the mass
>>of global ISPs.
>>
>>Now, consider the cost of such arrangements, to cover the
>>frictional  costs of just being in business, plus the required
>>profit margins that accrue to any such massive payment
>>shuffling.
>>
>>Everyone here advocating payments do not seem to understand
>>the overhead costs of collecting and distributing the money.
>>
>>Be careful of what you wish for! -- You just might get it!
>>
>>Cheers...\Stef




From owner-ietf@ietf.org  Wed May 28 23:06:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04342
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 23:06:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LDW1-0000iv-Jc
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 22:51:41 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LDF4-0000av-OK
	for ietf@asgard.ietf.org; Wed, 28 May 2003 22:34: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 WAA03523
	for <ietf@ietf.org>; Wed, 28 May 2003 22:34:08 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LDDU-0002Bu-00
	for ietf@ietf.org; Wed, 28 May 2003 22:32:32 -0400
Received: from h80ad2690.async.vt.edu ([128.173.38.144] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LDDS-0002Br-00
	for ietf@ietf.org; Wed, 28 May 2003 22:32:31 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h4T2Y1aA002701;
	Wed, 28 May 2003 22:34:01 -0400
Message-Id: <200305290234.h4T2Y1aA002701@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Einar Stefferud <Steflist@thor.nma.com>
Cc: pdeutsch@earthlink.net, ietf@ietf.org
Subject: Re: A peer-to-peer trust system model (was: Re: spam) 
In-Reply-To: Your message of "Wed, 28 May 2003 13:33:22 PDT."
             <v04220806bafac9e6d5e9@[192.168.1.14]> 
References: <3ED50675.72DA7BFC@earthlink.net>
            <v04220806bafac9e6d5e9@[192.168.1.14]>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_467937232P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 28 May 2003 22:34:01 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_467937232P
Content-Type: text/plain; charset=us-ascii

On Wed, 28 May 2003 13:33:22 PDT, Einar Stefferud said:

> "A trusts B" and "B trusts C"  does not imply anything about "A trusting C".
> 
> Even though you might decide to act on this assumption, believing it is true.

Mathematically provably true is a term used mostly by mathematicians - which
often means that what they come up with (being mathematicians(*) and thus often
disjoint from reality) is something that may be not usable.  There are a LOT
of transitive trust relationships that may not be *strictly* true, but are
close enough to trust billions of dollars with...

Every time I use a credit card, the entire scheme only works because the
vendor trusts the people at Visa to trust the bank to trust me to actually
pay the bill.  Now mathematically speaking, this scheme is a large crock
of concentrated fertilizer - but you add a few laws making it illegal to
use it to defraud, the various middlemen take 3-4%, write off 1% for bad
debt losses, and you have a system that 99% works and is widely accepted
because that last 1% is just too much effort for too little gain.

> If this assumption is true, then you must be a very gullible person, 
> which I somehow seriously doubt;-)...

The next time you walk into a delicatessen and hand the cashier a piece
of paper printed by some government, and walk out of there holding a
salami and several smaller-denomination pieces of paper and pieces of
metal, think about what size web of trust makes *that* transaction work.

/Valdis

(*) My degree is in math.  I'm allowed to say that. ;)

--==_Exmh_467937232P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+1XGYcC3lWbTT17ARAuU8AJwJkFowHAzH6jg+kLdJaNb07XMlxgCgljuh
RfAgDFcGKpsT1ZQ4CEC4QuI=
=LqCg
-----END PGP SIGNATURE-----

--==_Exmh_467937232P--



From owner-ietf@ietf.org  Wed May 28 23:36:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05031
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 May 2003 23:36:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LE60-0001tx-So
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 23:28:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LE0z-0001oa-1t
	for ietf@asgard.ietf.org; Wed, 28 May 2003 23:23:41 -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 XAA04774
	for <ietf@ietf.org>; Wed, 28 May 2003 23:23:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LDzO-0002Ws-00
	for ietf@ietf.org; Wed, 28 May 2003 23:22:02 -0400
Received: from out001pub.verizon.net ([206.46.170.140] helo=out001.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LDzN-0002Wm-00
	for ietf@ietf.org; Wed, 28 May 2003 23:22:01 -0400
Received: from earthlink.net ([4.65.81.213]) by out001.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030529032307.XWAA12592.out001.verizon.net@earthlink.net>;
          Wed, 28 May 2003 22:23:07 -0500
Message-ID: <3ED57C34.F4906D3@earthlink.net>
Date: Wed, 28 May 2003 20:19:16 -0700
From: Peter Deutsch <pdeutsch@earthlink.net>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Einar Stefferud <Steflist@thor.nma.com>
CC: ietf@ietf.org
Subject: Re: A peer-to-peer trust system model (was: Re: spam)
References: <DAC3FCB50E31C54987CD10797DA511BA036BE50E@WIN-MSG-10.wingroup.windeploy.nt
	 dev.microsoft.com> <3ED50675.72DA7BFC@earthlink.net> <v04220806bafac9e6d5e9@[192.168.1.14]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [4.65.81.213] at Wed, 28 May 2003 22:23:06 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

g'day,

Einar Stefferud wrote:
> 
> Hello  Peter --
> 
> I hate to be the one to tell you that the following is provably false:
> 
> "The unlying (sic) assumption here is that trust is a transitive relationship,"
> 
> Which leaves a bit of a gapping hole in your entire logical build...

Not at all, since the assumption of transitive trust is used merely to
"prime the pump". Once you start to develop evidence that disagrees with
your assumptions, you are expected to change your trust rules
accordingly. That's actually the heart of the system.

For example, I might start off by trusting mail from a particular
mailing list, and all its participants (say, anyone from my family
mailing list). I would then accept trust tokens from anyone who submits
a valid token from anyone on that mail list. Of course, if anyone used
such a tokento feed me spam, I'd hit the "Junk This" button on my MUA,
which would in turn tell my MTA to remove both the sender and that trust
token from my "trusted" list.

Put simply, I'd use a rule that says something like "fool me once, shame
on you, fool me twice, shame on me".

Note that this wouldn't prevent any of the folks on that mailing list
from reaching me, it would only prevent my MTA from trusting the
offender's token in the future. You could even tune that by putting
additional policy info in the trust token (you could put in a "degree of
trust" number, indicating how well you know the bearer, for example).


Now, suppose I wanted to send mail to Paul Vixie. I might just try to
send him mail, but from recent experience, I would expect that to go
something like this: "Hi, Paul!", "Mail System Error - Returned Mail".

Hmmm...

So, my MTA checks Paul's list of trusted buddies in the new, improved
DNS++, but doesn't recognize anyone in the list as somebody who's issued
me a trust token recently. So, off it goes to the Token Oracle, and ask
her for a trust path between myself and Paul Vixie (trust me, this can
be done. I have a proof of this, but the margins of my screen are too
small to contain it. It's enough for the purposes of this exposition to
note that this is something that can be precomputed so it can be
obtained somewhat efficiently).

So, back comes the Oracle, with the path:

  Peter Deutsch -> Einar Stefferud -> Randy Bush -> Paul Vixie


In other words, there is a trust chain from Einer Stefferud (who trust
me), to Randy Bush (who trusts Einar), to Paul Vixie (who trusts Randy).

Well, that's okay then, since I have a trust token from Einar Stefferud,
because I earned a trust token from you last week and you'd kindly
supplied me with one. Okay, so my MTA again contacts Paul's MTA and
offers it the trust token I have from you, as well as the trust chain.
Now, Paul can elect to accept mail from me, since the path checks out
and the token's good, and we'd be in business. Parenthetically, his MTA
would add the trust token from Einar Stefferud to his keychain for the
next time somebody comes a'calling.

Of course, if Paul reads my mail and decides that I really am as much of
a bozo as he'd feared, he's free to hit *his* "Junk This" button. This
would revoke my credit, and your trust token to me in his eyes, so he's
free to go back and finish reading the IETF mailing list without any
further direct interruption me. If I really want to reach him again, I
could try to find other paths from the tokens I've got left, until
either I've used up all my friends and acquaintences in a vain attempt
to get Paul's attention, or perhaps until I finally (through constant
allusions to Tom Lehrer) convince Paul Vixie that I'm not so bad after
all ("heck," he says, "this guy's a dope, but I do like 'Poisoning
Pigeons in the Park'...")


So, trust can be assumed to be transitive to prime the pump. Where you
find that this assumption is not valid, you can use the evidence that
it's not to tune and adjust your list of trusted sources. It's this
tuning over time that would make them more effective and lead to the
predicted success of the technique. 


As a final observation, the transitive nature of the trust is not the
key part of the system. To me, it's the ability to put policy decisions
in the hands of the recipient based upon past experience with trusted
sources, without having those trusted sources participate in the
interaction in real time. This seems to offer simplicity and scaling,
and means we can build this beast and get it out without requiring such
things as a single globally populated PKI, or universal takeup on the
scheme (the degenerative case is to accept everything, as folks do today
- the benefits accrue to the participants proportional to their
participation, but it begins paying off the first time you reject an
unknown sender without a trust token).


So, in summary, trust may not be transitive, but it makes a useful axiom
to kick things off. To paraphrase somebody's point a few hundred
postings ago, something can be an axiom without being true... ;-)


				- peterd



-- 
---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software

                        "Bungle..."
               "That's an 'i', you idiot..."
                  "Oh, right. 'Bingle..."

                            - Red versus Blue...

---------------------------------------------------------------------



From owner-ietf@ietf.org  Thu May 29 00:03:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05723
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 00:03:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LEYi-0002Yh-FV
	for ietf-list@asgard.ietf.org; Wed, 28 May 2003 23:58:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LEPx-0002Qz-0G
	for ietf@asgard.ietf.org; Wed, 28 May 2003 23:49:29 -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 XAA05431
	for <ietf@ietf.org>; Wed, 28 May 2003 23:49:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LEOM-0002hP-00
	for ietf@ietf.org; Wed, 28 May 2003 23:47:50 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LEOL-0002hM-00
	for ietf@ietf.org; Wed, 28 May 2003 23:47:49 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 208261; Wed, 28 May 2003 22:48:55 -0500
Message-ID: <3ED58344.9050704@ehsco.com>
Date: Wed, 28 May 2003 22:49:24 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Richard Shockey <richard@shockey.us>
CC: "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
References: <02b001c32497$0c11a350$2a134104@eagleswings> <02b001c32497$0c11a350$2a134104@eagleswings> <5.2.0.9.2.20030528212209.02965c60@shockey.us>
In-Reply-To: <5.2.0.9.2.20030528212209.02965c60@shockey.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/28/2003 8:30 PM Richard Shockey wrote:

> Its not that hard to write a letter, sign it with a return address and
> put a postage stamp on it or make a phone call to a local
> representatives office..
> 
> The US Congress is not very good a dealing with email ..trust me.
> 
> they like snail mail...

As a follow-up to anyone considering it, one office has said that the
anthrax scare has made snail-mail processing even more snail-like on the
hill. Sending postal mail to the home-state office is supposedly much
faster. If it has an in-state return address then it is that much more
likely to get read.

Also, at least some of the senators supposedly get several thousand emails
each week. Interestingly, about half the senators and reps no longer
publish email addresses, and many of them bounce email with a message
saying to resubmit via a web form. Whether this is due to the volume of
political spamming or UCE spamming is left to the reader to ponder.

All of that aside, the one response I've received which doesn't appear to
be completely automated (or at least somebody had to manually choose the
correct automated response) was to email.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Thu May 29 00:26:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06269
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 00:26:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LEs4-00034V-6u
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 00:18:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LEct-0002c9-3n
	for ietf@asgard.ietf.org; Thu, 29 May 2003 00:02:51 -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 AAA05702
	for <ietf@ietf.org>; Thu, 29 May 2003 00:02:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LEbI-0002kx-00
	for ietf@ietf.org; Thu, 29 May 2003 00:01:12 -0400
Received: from out006pub.verizon.net ([206.46.170.106] helo=out006.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LEbH-0002kS-00
	for ietf@ietf.org; Thu, 29 May 2003 00:01:11 -0400
Received: from earthlink.net ([4.65.81.213]) by out006.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030529040218.YUAB25800.out006.verizon.net@earthlink.net>;
          Wed, 28 May 2003 23:02:18 -0500
Message-ID: <3ED5856A.BF4BD4F9@earthlink.net>
Date: Wed, 28 May 2003 20:58:34 -0700
From: Peter Deutsch <pdeutsch@earthlink.net>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Einar Stefferud <Steflist@thor.nma.com>, ietf@ietf.org
Subject: Re: A peer-to-peer trust system model (was: Re: spam)
References: <DAC3FCB50E31C54987CD10797DA511BA036BE50E@WIN-MSG-10.wingroup.windeploy.nt
		 dev.microsoft.com> <3ED50675.72DA7BFC@earthlink.net> <v04220806bafac9e6d5e9@[192.168.1.14]> <3ED57C34.F4906D3@earthlink.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out006.verizon.net from [4.65.81.213] at Wed, 28 May 2003 23:02:18 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

g'day,

Oops, bad form to follow-up to your own posts, but I just want to make
sure I'm on record as being the first to notice that this is really just
another instantiation of the Six Degrees of Kevin Bacon. In honour of
this observation, my current working name for this system is "Bacon"
(for the hopefully obvious reason).


I wrote:

> So, back comes the Oracle, with the path:
> 
>   Peter Deutsch -> Einar Stefferud -> Randy Bush -> Paul Vixie

Sorry Randy, I'm going to drop you from the example. I think it's
funnier if it reads:


   Peter Deutsch -> Einar Stefferud -> Kevin Bacon -> Paul Vixie



And if you don't get this, go read:

   http://www-distance.syr.edu/bacon.html



			- peterd


-- 
---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software

                        "Bungle..."
               "That's an 'i', you idiot..."
                  "Oh, right. 'Bingle..."

                            - Red versus Blue...

---------------------------------------------------------------------



From owner-ietf@ietf.org  Thu May 29 00:43:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06623
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 00:43:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LEyi-0003DE-RI
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 00:25:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LEuI-00038x-EI
	for ietf@asgard.ietf.org; Thu, 29 May 2003 00:20:50 -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 AAA06069
	for <ietf@ietf.org>; Thu, 29 May 2003 00:20:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LEsh-0002r1-00
	for ietf@ietf.org; Thu, 29 May 2003 00:19:11 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LEsg-0002qw-00
	for ietf@ietf.org; Thu, 29 May 2003 00:19:11 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4T4KlKk031839
	for <ietf@ietf.org>; Thu, 29 May 2003 06:20:47 +0200 (CEST)
Message-ID: <077f01c32599$ae33cc00$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <014d01c32555$250d1c90$56144104@eagleswings>
Subject: Re: spam
Date: Thu, 29 May 2003 06:20:47 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony writes:

> Which is precisely the goal. It is not so extreme
> as to make routine mail unusable, but extreme enough
> to make random bulk mail not worth the cost.

Point taken, although I think conventional encryption would probably a
better choice for this purpose.

I think, though, that a more effective method would be to find something
that one can require on each message and that is not trivially easy for a
computer to do automatically.

For example, the various admininstrations passing through the White House
have long had a policy of establishing a "secret number" or similar text
that must be placed on any incoming letter that is to be forwarded directly
to the President or his family with minimal screening.  The President and
family then give this number to a select few people.  Any correspondence
without the number goes through all the usual screening.

This works because the number is an out-of-band datum that the average
sender is not likely to have.  It is communicated from human being to human
being, and isn't to be found anywhere in public.  So it cannot be
automatically added by a machine, nor can unauthorized people add it.

A simple e-mail implementation of this would be to place a random string in
the subject line of a message intended for a specific recipient that serves
the same purpose as this "secret number."  The string would be different for
each recipient, and the only way to obtain it would be through some
out-of-band process (such as contacting the recipient by phone, or
something).  Since there would be no record of this anywhere that spammers
could harvest, it would be impossible for spammers to include these numbers
on outgoing mail.  Very simple, and very effective.  It would, however, be
nice to have e-mail clients that automated this, by allow for a secret
number field in address books that would make it possible to insert them
automatically on outgoing mail (most clients already provide a way to filter
for such numbers on incoming mail).

Digital signatures and similar authentication would work but are overkill.
All you need is some bit of information that spammers cannot harvest, and
the above random string fits that purpose.  Spammers might pick up your
address on a newsgroup or Web site, but they'd have no way of discovering
your secret number.

> That simply provides message integrity ...

Hash it and sign it with the public key of the recipient.  That would work,
because spammers would not have the public key, whereas legitimate senders
would.

However, I think the secret-number concept described above would be much
similar and would be just as effective.




From owner-ietf@ietf.org  Thu May 29 00:48:05 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06812
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 00:48:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LFDD-0003iM-Lk
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 00:40:23 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LEzv-0003Hs-Vz
	for ietf@asgard.ietf.org; Thu, 29 May 2003 00:26:40 -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 AAA06288
	for <ietf@ietf.org>; Thu, 29 May 2003 00:26:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LEyL-0002s3-00
	for ietf@ietf.org; Thu, 29 May 2003 00:25:01 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LEyK-0002ry-00
	for ietf@ietf.org; Thu, 29 May 2003 00:25:00 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4T4QbKk031885
	for <ietf@ietf.org>; Thu, 29 May 2003 06:26:37 +0200 (CEST)
Message-ID: <079b01c3259a$7e5951c0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <02b001c32497$0c11a350$2a134104@eagleswings> <8221498523.20030528143453@brandenburg.com>
Subject: Re: The utilitiy of IP is at stake here
Date: Thu, 29 May 2003 06:26:36 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dave writes:

> The question is what the IETF can or should do
> about bad ISP customer policies, when those policies
> do not cause operations problems for the rest
> of the Internet?

Nothing.  While I'm strongly opposed to such restrictive policies at ISPs, I
don't see how they have anything to do with Internet engineering.  The ITU
does not tell telephone companies that they cannot charge extra for
Touch-Tone service.




From owner-ietf@ietf.org  Thu May 29 00:52:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06951
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 00:52:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LFDE-0003kU-Ac
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 00:40:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LF3G-0003Yq-ED
	for ietf@asgard.ietf.org; Thu, 29 May 2003 00:30:06 -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 AAA06431
	for <ietf@ietf.org>; Thu, 29 May 2003 00:30:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LF1f-0002uw-00
	for ietf@ietf.org; Thu, 29 May 2003 00:28:27 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LF1e-0002ut-00
	for ietf@ietf.org; Thu, 29 May 2003 00:28:26 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4T4U2Kk031916
	for <ietf@ietf.org>; Thu, 29 May 2003 06:30:02 +0200 (CEST)
Message-ID: <07a201c3259a$f8fbd1f0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <017601c32566$cb6fcea0$56144104@eagleswings>
Subject: Re: The utilitiy of IP is at stake here
Date: Thu, 29 May 2003 06:30:02 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony writes:

> Not if it simultaneously wants protection from
> liability for any content that the customer might
> be sending.

Now that I can fully agree with, although it's not an engineering issue.

ISPs that simultaneously want common-carrier protection from liability AND
the ability to finely dictate what types of traffic they will accept need to
choose one or the other.  Either you screen and restrict the traffic on your
network, but you take full responsibility for whatever is passing over it,
or you just provide raw bandwidth and you are shielded from any claims of
impropriety in the use thereof.  You can't have it both ways, as companies
like Prodigy have discovered.





From owner-ietf@ietf.org  Thu May 29 00:57:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07082
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 00:57:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LFDE-0003l0-L3
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 00:40:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LF9g-0003ec-Tc
	for ietf@asgard.ietf.org; Thu, 29 May 2003 00:36:44 -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 AAA06549
	for <ietf@ietf.org>; Thu, 29 May 2003 00:36:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LF86-0002vr-00
	for ietf@ietf.org; Thu, 29 May 2003 00:35:06 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LF85-0002vo-00
	for ietf@ietf.org; Thu, 29 May 2003 00:35:05 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4T4agKk031969
	for <ietf@ietf.org>; Thu, 29 May 2003 06:36:42 +0200 (CEST)
Message-ID: <07a901c3259b$e74bf7e0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.33.0305281505260.865-100000@egate.xpasc.com>
Subject: Re: requiring payment (was spam)
Date: Thu, 29 May 2003 06:36:42 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

David writes:

> One model exists in the postal service operated
> 'by' each country.

Have you really thought through how much this would cost in the Internet
world?  It would be a staggering burden, just as it already is for postal
mail.

A large part of what you pay in postage for a letter simply covers the cost
of collecting and verifying the postage for a letter.  And a large part of
the delay in getting the letter to its destination comes from the need to
collect and verify postage.

> As implied above, one or a few organizations
> per nation would provide clearing services.

Monopolies, you mean?  I can imagine the effect on prices.  Then again, I
don't have to imagine, since it has already been done in other domains.
That's another reason why sending a letter costs 37 cents--and that's a
price-controlled monopoly.

> Of course, there is a cost.

The cost is far beyond what you appear to be imagining.

> I think I understand the costs quite well.

I think not.  I hope your ideas are not too widespread.

> Probably by appropriate tiering of responsiblity
> and granularity of transactions recharging meters.

Transactions recharging meters.  With a billion computers talking to a
billion other computers a trillion times a day?

What you are suggesting is a bit like billing for telephone service based on
the content of a conversation, or billing for cable TV based on the stars in
the cast of the show you are watching.




From owner-ietf@ietf.org  Thu May 29 01:23:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07489
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 01:23:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LFpb-0005e2-IP
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 01:20:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LFjd-0005aX-M4
	for ietf@asgard.ietf.org; Thu, 29 May 2003 01:13:53 -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 BAA07442
	for <ietf@ietf.org>; Thu, 29 May 2003 01:13:52 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LFi3-0003Da-00
	for ietf@ietf.org; Thu, 29 May 2003 01:12:15 -0400
Received: from h80ad2690.async.vt.edu ([128.173.38.144] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LFi1-0003DX-00
	for ietf@ietf.org; Thu, 29 May 2003 01:12:14 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h4T5DjaA004635;
	Thu, 29 May 2003 01:13:45 -0400
Message-Id: <200305290513.h4T5DjaA004635@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Anthony Atkielski <anthony@atkielski.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: spam 
In-Reply-To: Your message of "Thu, 29 May 2003 06:20:47 +0200."
             <077f01c32599$ae33cc00$0a00000a@atkielski.com> 
References: <014d01c32555$250d1c90$56144104@eagleswings>
            <077f01c32599$ae33cc00$0a00000a@atkielski.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1440260128P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 29 May 2003 01:13:45 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_1440260128P
Content-Type: text/plain; charset=us-ascii

On Thu, 29 May 2003 06:20:47 +0200, Anthony Atkielski <anthony@atkielski.com>  said:

> A simple e-mail implementation of this would be to place a random string in
> the subject line of a message intended for a specific recipient that serves
> the same purpose as this "secret number." 

This works for the somewhat restricted case of e-mail between people who
already have some out-of-band way of communicating.

You're welcome to extend your proposal to handle bootstrapping
communications between people who haven't before - if the whole intent
of the "secret number" is so I can ignore email without it so I don't
get spam, people can't send me e-mail to ask me for a secret number
so they can e-mail me...

And if I *still* have to check my mail that doesn't have the number on it,
in case I've missed a request like that, what has this proposal bought me?

> Hash it and sign it with the public key of the recipient.  That would work,
> because spammers would not have the public key, whereas legitimate senders
> would.

Only if it's an *UNPUBLISHED* public key - at which point it just degenerates
into your "secret number" protocol, with the same bootstrapping issues.

--==_Exmh_1440260128P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+1ZcIcC3lWbTT17ARApxLAKC608szZFI1OgKIT3pkcp39VeWf6gCePmA1
FwzPT5d5DSWSqMSnKhV4vyg=
=MF0Y
-----END PGP SIGNATURE-----

--==_Exmh_1440260128P--



From owner-ietf@ietf.org  Thu May 29 02:46:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20474
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 02:46:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LGqo-0004iw-Sf
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 02:25:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LGqb-0004fg-Mt
	for ietf@asgard.ietf.org; Thu, 29 May 2003 02:25:09 -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 CAA20220
	for <ietf@ietf.org>; Thu, 29 May 2003 02:25:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LGp0-0003SI-00
	for ietf@ietf.org; Thu, 29 May 2003 02:23:30 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LGp0-0003SE-00
	for ietf@ietf.org; Thu, 29 May 2003 02:23:30 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 555E913968; Thu, 29 May 2003 06:24:36 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: requiring payment (was spam)
References: <114782448.1054159586@p3.JCK.COM>
From: Paul Vixie <vixie@vix.com>
Date: 29 May 2003 06:24:36 +0000
In-Reply-To: <114782448.1054159586@p3.JCK.COM>
Message-ID: <g3fzmytgm3.fsf@sa.vix.com>
Lines: 60
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

john-ietf@jck.com (John C Klensin) writes:

> ..., as soon as one institutes either charging schemes or collections of
> bilateral agreements, there are huge incentives to created "hub systems"
> or "carriers" -- entities whose business it is to make agreements with
> lots of local providers/servers (whom they will come to call "customers")
> and bilateral agreements with each other.  Without that, everyone who
> wants to run a mail server has to either establish bilateral agreements
> with everyone else, or a regulatory regime becomes necessary to make the
> sequential settlement arrangements work.  Economies of scale, if only in
> agreement-making, imply few enough, and large enough, carriers for
> governments to start taking interest on a "competition" or "anti-trust"
> or "consumer protection" basis.  Sorry to be pessimistic about this, but
> I think it quickly takes us where we don't want to go.
> 
> Quoting Stef, "be careful what you wish for..."

i'm not worried about this.  in fact, i'm *counting* on the existence of a
new class of businesses which i call "trust providers" or "trust brokers"
whose only claim to revenue is when they act as a trusted trust aggregator
so that i don't have to attend key signing parties in order to be able to
confidently accept mail based on reasonable certainty of the relay's intent,
the identity of the sender, and the value (to the sender) of the receipt.

will it be abused?  you betcha.  two ways off the top of my head.  first,
as jck says above, there's a lot of antitrust concern if for example verisign
decided to "trust-peer" with yahoo and noone else, and yahoo did likewise,
in hopes that the two of them could "pull a uunet" in terms of making everyone
else in the world their customer before a more diverse market can become
established.  fortunately we have the sherman act in the usa and similar
things elsewhere, so, unless microsoft itself decided to play, we're safe.

second, will be a class of trustbrokers who will try very hard to blur the
distinctions as to exactly what they are "promising about", so as to feed
you "gray spam" and reap both the transactional rewards associated with the
work AND kickbacks and bribes from the senders of the gray spam.  these folks
will have to be put out of business the old fashioned way, by poison reverse.
that is, a large number of consumers and other trustbrokers will have to
declare "gray promises" to have negative value, thus rendering them worthless.

all this goes to show is that there is no silver bullet, no one size fits all,
no magic pill or potion.  as long as we fit breitbart's "can be reached by
an ip packet from" notation, then we'll have the lower end of the humanity
scale nibbling at our resources, trying to take something and give nothing,
and so on.  however, even though unsolicited fax is dead, consider the
telemarketing field.  when my phone rings, there's a better than even chance
that it isn't a telemarketer.  it's not 100% but it's better than even.  if
we could get that for an ibcs that replaced smtp, i'd be singing in the aisles.

by the way mr. deutsch, there is no reference work available.  i've waved my
arms about this stuff and described it to no less than 1.5 dozen people in
the last six years, at varying levels of bakedness, but i don't want to have
to do the work myself and i met have no success in getting anybody else to
take it on.  therefore there's no formal design, not even a list of criteria,
and nothing's been wrote up, and there's no wheel for you to duplicate, so you
have a clear field and i encourage you to take advantage of the fact that the
rest of the world thinks this is just crackpot stupidity on the march.  please
put me on your friends and family list if you squeeze an IPO out of it, though.
-- 
Paul Vixie



From owner-ietf@ietf.org  Thu May 29 02:47:48 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20570
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 02:47:48 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LH8N-0004wM-JZ
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 02:43:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LH4v-0004rJ-JI
	for ietf@asgard.ietf.org; Thu, 29 May 2003 02:39: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 CAA20395
	for <ietf@ietf.org>; Thu, 29 May 2003 02:39:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LH3K-0003m8-00
	for ietf@ietf.org; Thu, 29 May 2003 02:38:18 -0400
Received: from smtp-out.comcast.net ([24.153.64.115])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LH3K-0003lv-00
	for ietf@ietf.org; Thu, 29 May 2003 02:38:18 -0400
Received: from max.hunnysoft.pri
 (pcp01719983pcs.nrockv01.md.comcast.net [68.50.252.119])
 by mtaout02.icomcast.net
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with ESMTP id <0HFM00HSPYHPSQ@mtaout02.icomcast.net> for ietf@ietf.org; Thu,
 29 May 2003 02:39:25 -0400 (EDT)
Received: from [192.168.2.5] (helo=hunnysoft.com)	by max.hunnysoft.pri with
 esmtp (Exim 3.36 #2)	id 19LH1k-0002Nr-00; Thu, 29 May 2003 02:36:40 -0400
Date: Thu, 29 May 2003 02:39:42 -0400
From: Doug Sauder <dws@hunnysoft.com>
Subject: Re: spam
To: Anthony Atkielski <anthony@atkielski.com>, ietf@ietf.org
Message-id: <3ED5AB2E.7040002@hunnysoft.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1)
 Gecko/20020826
References: <014d01c32555$250d1c90$56144104@eagleswings>
 <077f01c32599$ae33cc00$0a00000a@atkielski.com>
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT


Do we have to solve *the* spam problem?  How about a much simpler, solvable 
problem that perhaps a large majority of email users struggle with?

The hard problem is how to allow people to be generally accessible by email, 
but not so accessible that they get tons of spam.  In other words, how they 
can participate in a public forum -- say a newsgroup or mailing list -- 
allowing other individuals to contact them with non-spam, while keeping the 
spam out.

The easy problem is how to allow two consenting parties to communicate via 
email without interference from spam.  Not everyone feels it's necessary 
that they participate in a public forum.  Many would be happy if just the 
easy problem were solved.

The easy problem has not been solved satisfactorily.  Some options:

1. Get multiple email accounts.  Some are throw-away accounts.  Some are 
closely guarded, but eventually end up compromised.

2. Change email addresses from time to time.  For many users, that, to them, 
means changing ISPs.

3. Just learn to live with spam.

4. Try a filter and live with false positives.

Those are the options available to average email users.  For more capable 
users, there is another option:

5. Some clever ad hoc solution.  Like putting a special string in the 
subject line.

As this easy problem is a truly solvable problem, and one that many people 
care about, why not solve it in a standard way?

See my further comments below...

Anthony Atkielski wrote:
[snip]
> I think, though, that a more effective method would be to find something
> that one can require on each message and that is not trivially easy for a
> computer to do automatically.
> 
> For example, the various admininstrations passing through the White House
> have long had a policy of establishing a "secret number" or similar text
> that must be placed on any incoming letter that is to be forwarded directly
> to the President or his family with minimal screening.  The President and
> family then give this number to a select few people.  Any correspondence
> without the number goes through all the usual screening.
> 
> This works because the number is an out-of-band datum that the average
> sender is not likely to have.  It is communicated from human being to human
> being, and isn't to be found anywhere in public.  So it cannot be
> automatically added by a machine, nor can unauthorized people add it.
> 
> A simple e-mail implementation of this would be to place a random string in
> the subject line of a message intended for a specific recipient that serves
> the same purpose as this "secret number."  The string would be different for
> each recipient, and the only way to obtain it would be through some
> out-of-band process (such as contacting the recipient by phone, or
> something).  Since there would be no record of this anywhere that spammers
> could harvest, it would be impossible for spammers to include these numbers
> on outgoing mail.  Very simple, and very effective.  It would, however, be
> nice to have e-mail clients that automated this, by allow for a secret
> number field in address books that would make it possible to insert them
> automatically on outgoing mail (most clients already provide a way to filter
> for such numbers on incoming mail).

As Anthony's suggestion implies, the solution is simple.  It works like 
this: You can get into my email imbox because I authorized you to get in. 
You prove that you are authorized by presenting the "secret" that I provided 
to you.

While some would prefer to re-engineer the entire Internet mail system, I 
just see that average users would be happy if email from their relatives, 
friends, co-workers, and acquaintances went into one folder, while 
everything else went into another folder, automatically.  Why is that so 
hard to do?  Why isn't it done?

Personally, I think that plus aliases (also called subaddresses) are the 
best way to solve the easy problem.  But I would be thrilled to see the 
problem solved for the sake of Joe Average User by whatever technique: plus 
aliases, secret number in the subject line, new mail header field, or any 
other good idea.  Once that problem is solved sufficiently, we can go back 
to our research problems.

BTW, some commercial enterprises are on to this idea in a big way.  Just as 
one example, there is ZoEmail (www.zoemail.com).

> 
> Digital signatures and similar authentication would work but are overkill.
> All you need is some bit of information that spammers cannot harvest, and
> the above random string fits that purpose.  Spammers might pick up your
> address on a newsgroup or Web site, but they'd have no way of discovering
> your secret number.
> 
> 
>>That simply provides message integrity ...
> 
> 
> Hash it and sign it with the public key of the recipient.  That would work,
> because spammers would not have the public key, whereas legitimate senders
> would.
> 
> However, I think the secret-number concept described above would be much
> similar and would be just as effective.
> 
> 
> 
> 


-- 
Doug Sauder
Hunny Software, Inc




From owner-ietf@ietf.org  Thu May 29 03:45:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21857
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 03:45:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LHri-0006J9-Dm
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 03:30:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LHoj-0006Ff-A8
	for ietf@asgard.ietf.org; Thu, 29 May 2003 03:27:17 -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 DAA21537
	for <ietf@ietf.org>; Thu, 29 May 2003 03:27:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LHn8-00045A-00
	for ietf@ietf.org; Thu, 29 May 2003 03:25:38 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LHn7-000456-00
	for ietf@ietf.org; Thu, 29 May 2003 03:25:37 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4T7RDKk033334
	for <ietf@ietf.org>; Thu, 29 May 2003 09:27:13 +0200 (CEST)
Message-ID: <082601c325b3$b949efb0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <014d01c32555$250d1c90$56144104@eagleswings>            <077f01c32599$ae33cc00$0a00000a@atkielski.com> <200305290513.h4T5DjaA004635@turing-police.cc.vt.edu>
Subject: Re: spam 
Date: Thu, 29 May 2003 09:27:12 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Valdis writes:

> You're welcome to extend your proposal to handle
> bootstrapping communications between people who
> haven't before ...

There isn't any way to automate this without opening the door to spammers.

> ... if the whole intent of the "secret number"
> is so I can ignore email without it so I don't
> get spam, people can't send me e-mail to ask me
> for a secret number so they can e-mail me...

Correct.  They'll have to ask you in some out-of-band way.  There isn't any
other option.  Any means you provide of obtaining your secret number without
your explicit, out-of-band approval will be used by spammers just as readily
as by anyone else.  There is no unambiguous, automated way to distinguish
between spammers and any other sender of unsolicited e-mail.

> And if I *still* have to check my mail that
> doesn't have the number on it, in case I've missed
> a request like that, what has this proposal bought me?

Not very much, but for people with a small circle of legitimate
correspondents as compared to the volume of e-mail they receive, it might
help.

In the world of postal mail, the same problem of spam exists, and there is
no solution to it.  Political figures, celebrities, and organizations
receive incredible volumes of unsolicited, junk mail; the one and only way
to separate the truly useless mail from legitimate mail is to hire human
beings to sort through it.  There isn't any other way.  And prosecuting
those who send mail improperly doesn't work, either; it stops one entity
from sending mail, but all the rest continue, so the incoming volume does
not decrease.

If you send a letter to the President of the United States, he may not read
it himself, but the letter will definitely be read by a human being.  All
incoming mail is read.  The same is true for all incoming e-mail.  And the
President is not the only one having this done.  Many celebrities have staff
or subcontractors that do nothing but read every piece of incoming mail.
There isn't any other option.  And prosecuting someone who sends mail
illegally, or sends threats, or something like that, does nothing to slow
the flow of mail overall.

It may be that spam is an insoluble problem.  No automated filter can
protect against it.  No after-the-fact prosecution or lawsuits can slow the
flow significantly.  No billing scheme can slow the flow of spam without
equally affecting the flow of legitimate e-mail, because there isn't really
any fundamental difference between the two, except in the eye of the
recipient.




From owner-ietf@ietf.org  Thu May 29 04:05:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22241
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 04:05:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LI1Z-0006Qc-OQ
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 03:40:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LHtT-0006JW-1r
	for ietf@asgard.ietf.org; Thu, 29 May 2003 03:32:11 -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 DAA21636
	for <ietf@ietf.org>; Thu, 29 May 2003 03:32:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LHrs-00047A-00
	for ietf@ietf.org; Thu, 29 May 2003 03:30:32 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LHrr-000477-00
	for ietf@ietf.org; Thu, 29 May 2003 03:30:31 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4T7W7Kk033369
	for <ietf@ietf.org>; Thu, 29 May 2003 09:32:07 +0200 (CEST)
Message-ID: <082b01c325b4$689d0dd0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <014d01c32555$250d1c90$56144104@eagleswings> <077f01c32599$ae33cc00$0a00000a@atkielski.com> <3ED5AB2E.7040002@hunnysoft.com>
Subject: Re: spam
Date: Thu, 29 May 2003 09:32:07 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Doug writes:

> Do we have to solve *the* spam problem?

I'm beginning to think that it cannot be solved--not technically, and not
legally.  One man's spam is another man's legitimate e-mail.  It's like
censorship.

> The hard problem is how to allow people to be
> generally accessible by email, but not so accessible
> that they get tons of spam.  In other words, how they
> can participate in a public forum -- say a newsgroup
> or mailing list -- allowing other individuals to contact
> them with non-spam, while keeping the spam out.

Agreed.  Most spammers seem to pull addresses from newsgroups, discussion
forums, and Web sites.  Addresses of mine that appear on none of these never
receive any spam.

> While some would prefer to re-engineer the entire
> Internet mail system, I just see that average users
> would be happy if email from their relatives,
> friends, co-workers, and acquaintances went into
> one folder, while everything else went into another
> folder, automatically.

I agree.

> Why is that so hard to do?

It's not.

> Why isn't it done?

Probably because the same people who might easily be able to use such a
system are not receiving spam, anyway, because their e-mail addresses are
invisible to spammers (they don't post to USENET, they have no Web sites,
they've never given their e-mail address to a Web site, and their e-mail
address is largely immune to a dictionary or exhaustive attack).





From owner-ietf@ietf.org  Thu May 29 04:32:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22861
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 04:32:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LIe5-000861-Up
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 04:20:21 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LIYm-0007z4-RL
	for ietf@asgard.ietf.org; Thu, 29 May 2003 04:14:52 -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 EAA22682
	for <ietf@ietf.org>; Thu, 29 May 2003 04:14:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LIXB-0004QL-00
	for ietf@ietf.org; Thu, 29 May 2003 04:13:13 -0400
Received: from vrx.net ([216.13.126.22] helo=ns1.vrx.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LIXB-0004QI-00
	for ietf@ietf.org; Thu, 29 May 2003 04:13:13 -0400
Received: from [192.168.1.14] (lsanca1-ar47-4-33-128-181.lsanca1.dsl-verizon.net [4.33.128.181])
	by ns1.vrx.net (Postfix) with ESMTP
	id 5B101D3E3; Thu, 29 May 2003 04:14:45 -0400 (EDT)
Mime-Version: 1.0
X-Sender: steflist@vrx.net
Message-Id: <v04220801bafb5019ca42@[192.168.1.14]>
In-Reply-To: <3ED5856A.BF4BD4F9@earthlink.net>
References: 
 <DAC3FCB50E31C54987CD10797DA511BA036BE50E@WIN-MSG-10.wingroup.windeploy.nt
 	 dev.microsoft.com> <3ED50675.72DA7BFC@earthlink.net>
 <v04220806bafac9e6d5e9@[192.168.1.14]> <3ED57C34.F4906D3@earthlink.net>
 <3ED5856A.BF4BD4F9@earthlink.net>
Date: Thu, 29 May 2003 01:14:43 -0700
To: pdeutsch@earthlink.net
From: Einar Stefferud <Steflist@thor.nma.com>
Subject: Re: A peer-to-peer trust system model (was: Re: spam)
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi Peter -- 

Your two additional explanatory messages here were needed to explain 
how you deal with trust transitivity when trust is not simply transitive, 
but might serve to allow you to explore for a path that, when tested by 
trial and error, might find a working transitive case in reality, based 
on more information than the simple assumption of transitivity without 
testing it to obtain more information via additional information 
transmission channels.

So, now you are confirming what I understand about defining trust.

Information, per Shannon, is some specific bits which the recipient did 
not expect to receive.  On this definitional foundation he built a huge 
edifice of mathematics for computing a lot of stuff about the capacities 
of wires and other transmission media, and the design of telephone and 
other communications channels, including how many redundant bits are 
needed to detect and correct errors.

And Trust, per my friend Ed Gerck, is that information, obtained via 
some different channel (or channels), which is required to 
understand and to trust said received information bits that (per Shannon) 
were not specifically expected to be received.

So, what you have done to counter the fact that trust is simply not 
transitive, is to add more channels to the process of communication, 
to obtain the required trust information via other channels, which you 
also state "might not prove to induce the desired trust". 

In the specific case you have chosen, I expect that your target will not 
accept your "tokens" as I have been considered to be the most dangerous 
person on the Internet, per various people.  This means that I might not 
be considered to be trustworthy.

This condition of untrustworthy perceptions is OK with me, but in the 
context of this discussion, you may very well have not gotten your message 
to be accepted by Paul Vixie.

Maybe next time you will succeed, but so far, the odds are against you 
next time too;-)...

So, for all intentions and purposes, trust is not simply transitive.

In part this is because it assumes a single channel, while additional 
channels are required because trust information cannot be meaningfully 
sent via the same channel as carried the information to be trusted.

This is why people typically laugh when a salesman says "Trust Me!"
Because they intuitively know that self assertion of trustworthiness 
has no value.

Cheers...\Stef

PS:  In this case, it is good that you did follow-up on your own message.
     ...\S




At 20:58 -0700 5/28/03, Peter Deutsch wrote:
>g'day,
>
>Oops, bad form to follow-up to your own posts, but I just want to make
>sure I'm on record as being the first to notice that this is really just
>another instantiation of the Six Degrees of Kevin Bacon. In honour of
>this observation, my current working name for this system is "Bacon"
>(for the hopefully obvious reason).
>
>
>I wrote:
>
> > So, back comes the Oracle, with the path:
> > 
> >   Peter Deutsch -> Einar Stefferud -> Randy Bush -> Paul Vixie
>
>Sorry Randy, I'm going to drop you from the example. I think it's
>funnier if it reads:
>
>
>   Peter Deutsch -> Einar Stefferud -> Kevin Bacon -> Paul Vixie
>
>
>
>And if you don't get this, go read:
>
>   http://www-distance.syr.edu/bacon.html
>
>
>
>			- peterd
>
>
>-- 
>---------------------------------------------------------------------
>    Peter Deutsch                       pdeutsch@gydig.com
>    Gydig Software
>
>                        "Bungle..."
>               "That's an 'i', you idiot..."
>                  "Oh, right. 'Bingle..."
>
>                            - Red versus Blue...
>
>---------------------------------------------------------------------




From owner-ietf@ietf.org  Thu May 29 04:48:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23224
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 04:48:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LJ1F-0000Ev-Na
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 04:44:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LItx-00009o-5b
	for ietf@asgard.ietf.org; Thu, 29 May 2003 04:36:45 -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 EAA23022
	for <ietf@ietf.org>; Thu, 29 May 2003 04:36:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LIsM-0004WO-00
	for ietf@ietf.org; Thu, 29 May 2003 04:35:06 -0400
Received: from vrx.net ([216.13.126.22] helo=ns1.vrx.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LIsL-0004WL-00
	for ietf@ietf.org; Thu, 29 May 2003 04:35:05 -0400
Received: from [192.168.1.14] (lsanca1-ar47-4-33-128-181.lsanca1.dsl-verizon.net [4.33.128.181])
	by ns1.vrx.net (Postfix) with ESMTP
	id 238B6D4A6; Thu, 29 May 2003 04:36:39 -0400 (EDT)
Mime-Version: 1.0
X-Sender: steflist@vrx.net
Message-Id: <v04220802bafb769cd6b7@[192.168.1.14]>
In-Reply-To: <g3fzmytgm3.fsf@sa.vix.com>
References: <114782448.1054159586@p3.JCK.COM> <g3fzmytgm3.fsf@sa.vix.com>
Date: Thu, 29 May 2003 01:36:36 -0700
To: ietf@ietf.org
From: Einar Stefferud <Steflist@thor.nma.com>
Subject: Re: requiring payment (was spam)
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

I suggest that those who wish to more fully understand all this trust stuff might find it useful to look at http://mcg.org.br/.

Cheers...\Stef


At 6:24 +0000 5/29/03, Paul Vixie wrote:
>john-ietf@jck.com (John C Klensin) writes:
>
> > ..., as soon as one institutes either charging schemes or collections of
> > bilateral agreements, there are huge incentives to created "hub systems"
> > or "carriers" -- entities whose business it is to make agreements with
> > lots of local providers/servers (whom they will come to call "customers")
> > and bilateral agreements with each other.  Without that, everyone who
> > wants to run a mail server has to either establish bilateral agreements
> > with everyone else, or a regulatory regime becomes necessary to make the
> > sequential settlement arrangements work.  Economies of scale, if only in
> > agreement-making, imply few enough, and large enough, carriers for
> > governments to start taking interest on a "competition" or "anti-trust"
> > or "consumer protection" basis.  Sorry to be pessimistic about this, but
> > I think it quickly takes us where we don't want to go.
> > 
> > Quoting Stef, "be careful what you wish for..."
>
>i'm not worried about this.  in fact, i'm *counting* on the existence of a
>new class of businesses which i call "trust providers" or "trust brokers"
>whose only claim to revenue is when they act as a trusted trust aggregator
>so that i don't have to attend key signing parties in order to be able to
>confidently accept mail based on reasonable certainty of the relay's intent,
>the identity of the sender, and the value (to the sender) of the receipt.
>
>will it be abused?  you betcha.  two ways off the top of my head.  first,
>as jck says above, there's a lot of antitrust concern if for example verisign
>decided to "trust-peer" with yahoo and noone else, and yahoo did likewise,
>in hopes that the two of them could "pull a uunet" in terms of making everyone
>else in the world their customer before a more diverse market can become
>established.  fortunately we have the sherman act in the usa and similar
>things elsewhere, so, unless microsoft itself decided to play, we're safe.
>
>second, will be a class of trustbrokers who will try very hard to blur the
>distinctions as to exactly what they are "promising about", so as to feed
>you "gray spam" and reap both the transactional rewards associated with the
>work AND kickbacks and bribes from the senders of the gray spam.  these folks
>will have to be put out of business the old fashioned way, by poison reverse.
>that is, a large number of consumers and other trustbrokers will have to
>declare "gray promises" to have negative value, thus rendering them worthless.
>
>all this goes to show is that there is no silver bullet, no one size fits all,
>no magic pill or potion.  as long as we fit breitbart's "can be reached by
>an ip packet from" notation, then we'll have the lower end of the humanity
>scale nibbling at our resources, trying to take something and give nothing,
>and so on.  however, even though unsolicited fax is dead, consider the
>telemarketing field.  when my phone rings, there's a better than even chance
>that it isn't a telemarketer.  it's not 100% but it's better than even.  if
>we could get that for an ibcs that replaced smtp, i'd be singing in the aisles.
>
>by the way mr. deutsch, there is no reference work available.  i've waved my
>arms about this stuff and described it to no less than 1.5 dozen people in
>the last six years, at varying levels of bakedness, but i don't want to have
>to do the work myself and i met have no success in getting anybody else to
>take it on.  therefore there's no formal design, not even a list of criteria,
>and nothing's been wrote up, and there's no wheel for you to duplicate, so you
>have a clear field and i encourage you to take advantage of the fact that the
>rest of the world thinks this is just crackpot stupidity on the march.  please
>put me on your friends and family list if you squeeze an IPO out of it, though.
>-- 
>Paul Vixie




From owner-ietf@ietf.org  Thu May 29 04:51:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22240
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 04:05:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LIId-0006vv-2d
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 03:58:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LHxy-0006Lg-0U
	for ietf@asgard.ietf.org; Thu, 29 May 2003 03:36:50 -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 DAA21718
	for <ietf@ietf.org>; Thu, 29 May 2003 03:36:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LHwM-00048u-00
	for ietf@ietf.org; Thu, 29 May 2003 03:35:10 -0400
Received: from cust-smtp1.radiolinja.fi ([213.161.33.208])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LHwM-00048r-00
	for ietf@ietf.org; Thu, 29 May 2003 03:35:10 -0400
Received: from EMCL (rl045112.radiolinja.net [213.161.45.112])
	by cust-smtp1.radiolinja.fi (Postfix) with SMTP
	id 7BBE94000B; Thu, 29 May 2003 10:36:35 +0300 (EEST)
From: "=?UTF-8?Q?John_Loughney?=" <john.loughney@kolumbus.fi>
To: <dean@av8.com>, <jstracke@centive.com>
Cc: <ietf@ietf.org>
Subject: =?UTF-8?Q?Re:_spam?=
Date: Thu, 29 May 2003 10:32:35 +0000
Message-Id: <1054204355389>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
X-Mailer: EMCL v2.14
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id EAA22240

Hi,

What is a 'radical anti-spammer'?

----------

This is the _false_ assertion of
radical anti-spammers, who seem to me to be the abusers.  Chris Neill
(antispammer open relay abuser eventually fired from Verio--he was
ironically, an abuse admin) was shocked to learn he was't anonymous, like
he thought.

The claims made by antispammers about open relays are false. Type 1
spammers seem to get that, judging by their behavior.  But radical
antispammers don't.

		--Dean

On Wed, 28 May 2003, John Stracke wrote:

> Dean Anderson wrote:
>
> >We are lucky that spammers don't get a discount
> >
> Open relays give them a five-finger discount.
>
> --
> /===============================================================\
> |John Stracke      |jstracke@centive.com                        |
> |Principal Engineer|http://www.centive.com                      |
> |Centive           |My opinions are my own.                     |
> |===============================================================|
> |"Power corrupts; Powerpoint corrupts absolutely." -- Vint Cerf |
> \===============================================================/
>
>
>
>


    



From owner-ietf@ietf.org  Thu May 29 08:53:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01542
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 08:53:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LMf2-00031c-Cj
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 08:37:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LMCY-00010O-13
	for ietf@asgard.ietf.org; Thu, 29 May 2003 08:08: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 IAA29743
	for <ietf@ietf.org>; Thu, 29 May 2003 08:08:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LMAw-0006Jg-00
	for ietf@ietf.org; Thu, 29 May 2003 08:06:30 -0400
Received: from krusty-motorsports.com ([192.94.170.8] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LMAw-0006Jd-00
	for ietf@ietf.org; Thu, 29 May 2003 08:06:30 -0400
Received: from [24.194.112.77] (helo=skipper.averillpark.net)
	by krusty-motorsports.com with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.14)
	id 19LMCV-00074w-Vo
	for ietf@ietf.org; Thu, 29 May 2003 12:08:08 +0000
Received: from rwelty by skipper.averillpark.net with local (Exim 4.14)
	id 19LMBD-0002Ov-T3
	for ietf@ietf.org; Thu, 29 May 2003 08:06:47 -0400
Date: Thu, 29 May 2003 08:06:45 -0400 (EDT)
From: Richard Welty <rwelty@averillpark.net>
Subject: Re[2]: spam
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Disposition: INLINE
References: <1054204355389>
In-Reply-To: <1054204355389>
X-Mailer: Mahogany 0.64 'Sparc', compiled for Linux 2.4.9-13 i686
Message-Id: <E19LMBD-0002Ov-T3@skipper.averillpark.net>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 29 May 2003 10:32:35 +0000 John Loughney <john.loughney@kolumbus.fi> wrote:
> What is a 'radical anti-spammer'?

it's a rhetorical device used when one wants to paint with an overly broad
brush.

cheers,
  richard
--
Richard Welty                                         rwelty@averillpark.net
Averill Park Networking                                         518-573-7592
              Unix, Linux, IP Network Engineering, Security





From owner-ietf@ietf.org  Thu May 29 09:09:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02069
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 09:09:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LMgz-00036Z-Gc
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 08:39:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LMGZ-0001wU-8c
	for ietf@asgard.ietf.org; Thu, 29 May 2003 08:12:19 -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 IAA00006
	for <ietf@ietf.org>; Thu, 29 May 2003 08:12:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LMEy-0006O1-00
	for ietf@ietf.org; Thu, 29 May 2003 08:10:40 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LMEw-0006Nu-00
	for ietf@ietf.org; Thu, 29 May 2003 08:10:39 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h4TCDIxS020477;
	Thu, 29 May 2003 14:13:19 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Thu, 29 May 2003 14:12:15 +0200
Subject: Re: fighting spam, the protocol route
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: "Christian Huitema" <huitema@windows.microsoft.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA036BE50E@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Message-Id: <C90A2341-91CE-11D7-9B54-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On woensdag, mei 28, 2003, at 19:56 Europe/Amsterdam, Christian Huitema 
wrote:

>> It surprises me that so many people are so eager to declare defeat
>> before even trying the protocol route. (With current protocols defeat
>> is pretty much inevitable.)

> There is an obvious issue with the protocol route: from a protocol 
> point
> of view, it is quite hard to distinguish unsolicited commercial e-mail,
> which we would label spam, and unsolicited acceptable e-mail, which
> could be more than welcome.

Detecting spam is hard, as spamminess is in the eye/mailbox of the 
beholder. However, I see no reason why we can't detect unsollicited 
bulk email for reasonable definitions of "sollicited" and "bulk".

To see whether a messsage would be welcome (sollicited) we can simply 
see if we know the source. This can be done end-to-end 
cryptographically or by trusting that a known MTA has checked the 
previous MTA and so on until we reach the MTA that verified the source. 
In order to detect bulk email we simply count the number of messages 
received from each MTA we're in contact with.

Then it's simply a question of rate limiting the number of messages 
accepted from unknown MTAs and/or redirecting unknown MTAs to a trusted 
MTA or an MTA that's in the position to do better anti-spam filtering.

So if I'm an AOL user with my own dial-up MTA and I want to send you a 
message, the Microsoft MTA doesn't know me so it either takes a chance 
and accepts messages at a low rate, it tells me "why don't you deliver 
this message to your ISP's MTA and have them forward it", "deliver this 
message to mx13.spamwashers.com" or "we can't accept your message, 
submit your remarks using our web form" or "submit a public key signed 
by at least two organizations listed on trustedmailers.microsoft.com".

So will this be enough? It won't get rid of all unsollicited email, 
commercial or otherwise. But the improved accountability should make 
life much harder for every type of spammer.




From owner-ietf@ietf.org  Thu May 29 09:26:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02764
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 09:26:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LNB7-0005Vi-9a
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 09:10:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LMrp-0004UP-6o
	for ietf@asgard.ietf.org; Thu, 29 May 2003 08:50:49 -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 IAA01473
	for <ietf@ietf.org>; Thu, 29 May 2003 08:50:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LMqD-0006nf-00
	for ietf@ietf.org; Thu, 29 May 2003 08:49:09 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LMqD-0006nc-00
	for ietf@ietf.org; Thu, 29 May 2003 08:49:09 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h4TCoktU015848;
	Thu, 29 May 2003 08:50:46 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h4TCojKT015845;
	Thu, 29 May 2003 08:50:46 -0400
Date: Thu, 29 May 2003 08:50:46 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200305291250.h4TCojKT015845@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: spam
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: "Anthony Atkielski" <anthony@atkielski.com>

    > In the world of postal mail, the same problem of spam exists, and there
    > is no solution to it. .. the one and only way to separate the truly
    > useless mail from legitimate mail is to hire human beings to sort
    > through it. There isn't any other way.

Unfortunately, this option isn't available to us. We can't *all* hire N other
humans to sort our email.

    > It may be that spam is an insoluble problem.

It *better* be solvable, otherwise when email becomes 99% spam, everyone will
stop reading email.

    > No billing scheme can slow the flow of spam without equally affecting
    > the flow of legitimate e-mail, because there isn't really any
    > fundamental difference between the two, except in the eye of the
    > recipient.

I'm willing to spend $.25 to communicate with someone I've never sent email
to before. I doubt very much the spammers who boast of sending millions of
messages a day are willing to spend $.25 each message for the privilege.

	Noel



From owner-ietf@ietf.org  Thu May 29 11:14:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06853
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 11:14:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LOxb-0000IO-Ci
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 11:04:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LOem-00005d-BF
	for ietf@asgard.ietf.org; Thu, 29 May 2003 10:45:28 -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 KAA06111
	for <ietf@ietf.org>; Thu, 29 May 2003 10:45:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LOdA-0007Yl-00
	for ietf@ietf.org; Thu, 29 May 2003 10:43:48 -0400
Received: from mail.cdt.org ([206.112.85.61])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LOdA-0007Yh-00
	for ietf@ietf.org; Thu, 29 May 2003 10:43:48 -0400
Received: from [10.0.1.20] (66.safeclick.net [63.119.245.66])
	by mail.cdt.org (Postfix) with ESMTP id 0EA0149011B
	for <ietf@ietf.org>; Thu, 29 May 2003 10:29:03 -0400 (EDT)
Mime-Version: 1.0
X-Sender: john@mail.cdt.org
Message-Id: <a05200f00bafbc9fdb2f1@[10.0.1.20]>
In-Reply-To: <07a201c3259a$f8fbd1f0$0a00000a@atkielski.com>
References: <017601c32566$cb6fcea0$56144104@eagleswings>
 <07a201c3259a$f8fbd1f0$0a00000a@atkielski.com>
Date: Thu, 29 May 2003 10:44:51 -0400
To: "IETF Discussion" <ietf@ietf.org>
From: John Morris <jmorris@cdt.org>
Subject: Re: The utilitiy of IP is at stake here
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 6:30 AM +0200 5/29/03, Anthony Atkielski wrote:
>Tony writes:
>
>>  Not if it simultaneously wants protection from
>>  liability for any content that the customer might
>>  be sending.
>
>Now that I can fully agree with, although it's not an engineering issue.
>
>ISPs that simultaneously want common-carrier protection from liability AND
>the ability to finely dictate what types of traffic they will accept need to
>choose one or the other.  Either you screen and restrict the traffic on your
>network, but you take full responsibility for whatever is passing over it,
>or you just provide raw bandwidth and you are shielded from any claims of
>impropriety in the use thereof.  You can't have it both ways, as companies
>like Prodigy have discovered.

FWIW, and not to drag us too far into a legal discussion, but the 
above is not correct for the United States.   In the US, ISPs are 
not, and never have been viewed, as common carriers.  And, as one can 
see in the on-going arguments made about the possibility that cable 
ISPs might interfere with content, ISPs in general have strongly 
resisted being treated as common carriers.  They do not want to take 
on the obligations that common carrier status would bring.

Having said that, ISPs in the US do have common carrier-like 
protection from liability for content of their customers and others 
-- but this protection from liability is by statute, not as a result 
of any common carrier status.  Section 230(c)(1) of chapter 47 of the 
U.S. Code states:

   (1) Treatment of publisher or speaker
       No provider or user of an interactive computer service [read, 
an ISP] shall be
       treated as the publisher or speaker of any information provided
       by another information content provider.

This protection from liability is in no way dependent on what 
restrictions an ISP places on its traffic.  Thus, for purposes of 
this thread, if an ISP wants to "finely dictate what types of traffic 
they will accept" they can do so without loss of liability protection.

John



From owner-ietf@ietf.org  Thu May 29 11:18:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07006
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 11:18:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LOxb-0000J3-Uh
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 11:04:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LOkK-000079-Aq
	for ietf@asgard.ietf.org; Thu, 29 May 2003 10:51:12 -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 KAA06249
	for <ietf@ietf.org>; Thu, 29 May 2003 10:51:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LOii-0007b9-00
	for ietf@ietf.org; Thu, 29 May 2003 10:49:32 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LOii-0007b6-00
	for ietf@ietf.org; Thu, 29 May 2003 10:49:32 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h4TEq9xS020690;
	Thu, 29 May 2003 16:52:10 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Thu, 29 May 2003 16:51:06 +0200
Subject: Re: spam
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Dean Anderson <dean@av8.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <Pine.LNX.4.44.0305281536460.7861-100000@commander.av8.net>
Message-Id: <FA2605DA-91E4-11D7-9B54-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On woensdag, mei 28, 2003, at 21:39 Europe/Amsterdam, Dean Anderson 
wrote:

>> It surprises me that so many people are so eager to declare defeat
>> before even trying the protocol route.

> We tried protocols 5 years ago. They haven't worked.  I've explained 
> why
> specifically, and why in theory they can't work.

I'm not interested in a discussion about semantics so we can define the 
problem as solvable or unsolvable.

I found the following to be an interesting read: 
http://www.cdt.org/spam/

It shows that even five years ago or so most ligitimate businesses 
advertising legitimate services through spam employed header forgery. 
If we can't stop spammers from spamming we should at least be able to 
stop them from doing so in ways that add insult to injury by derailing 
the entire email service.

So let's have that BOF.




From owner-ietf@ietf.org  Thu May 29 12:04:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08414
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 12:04:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LPk0-0002N3-Ob
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 11:54:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LPZc-00029M-Pq
	for ietf@asgard.ietf.org; Thu, 29 May 2003 11:44:12 -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 LAA07817
	for <ietf@ietf.org>; Thu, 29 May 2003 11:44:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LPY1-0000AF-00
	for ietf@ietf.org; Thu, 29 May 2003 11:42:33 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LPY0-0000A9-00
	for ietf@ietf.org; Thu, 29 May 2003 11:42:32 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.9/8.12.9) id h4TFi8FR006326
	for ietf@ietf.org env-from <vjs>;
	Thu, 29 May 2003 09:44:08 -0600 (MDT)
Date: Thu, 29 May 2003 09:44:08 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200305291544.h4TFi8FR006326@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: spam
References: <FA2605DA-91E4-11D7-9B54-00039388672E@muada.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Iljitsch van Beijnum <iljitsch@muada.com>

> ...
> I found the following to be an interesting read: 
> http://www.cdt.org/spam/
>
> It shows that even five years ago or so most ligitimate businesses 
> advertising legitimate services through spam employed header forgery. 
> ...

It is an article of faith for many people that most spam involves
header forgery, but no one seems to have better support than intuition
for that faith.  Where in the report at http://www.cdt.org/spam/ does
it say that "most ligitimate businesses advertising legitimate services
through spam employed header forgery?"  I found "forged addresses and
domain names as the source of innumerable problems" and similar
statements, but they differ signficiantly from the familiar claims
that most spam involves header forgery.  Moreover, since that report
there have been the Flowers.com case and many state laws against header
forgery that I think have discouraged a lot of header forgery.

A lot of spam does involve header forgery, but a lot clearly does not.
The problem with concluding that "most" spam uses header forgery is
that it encourages looking for solutions to header forgery instead of
stopping unsolicited bulk mail.

That leads to a major problem in dealing with spam.  Most people
who say they want to stop spam in fact have other goals that they
value more.  Those other goals include:
  - stopping header forgery,
  - making all mail "authenticated," for various notions of that word,
  - stopping commercial email, and never mind that an order confirmation
     is commercial,
  - stopping unsolicited commercial email (Never mind that many of us
     depend on unsolicited non-bulk commercial email for our daily bread),
  - selling anti-spam services or software,
  - counting coup on spammers by "LARTing" them, signing them up for
     junk postal mail, etc,
  - becoming famous for having stopped spam, or at least getting into
     the RFC index.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Thu May 29 13:06:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10343
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 13:06:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LQgQ-0003ya-Ta
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 12:55:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LQg6-0003u3-HH
	for ietf@asgard.ietf.org; Thu, 29 May 2003 12:54:58 -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 MAA09928
	for <ietf@ietf.org>; Thu, 29 May 2003 12:54:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LQeU-0000fL-00
	for ietf@ietf.org; Thu, 29 May 2003 12:53:18 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LQeT-0000fI-00
	for ietf@ietf.org; Thu, 29 May 2003 12:53:18 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h4TGtnxS020882;
	Thu, 29 May 2003 18:55:50 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Thu, 29 May 2003 18:54:45 +0200
Subject: Re: spam
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <200305291544.h4TFi8FR006326@calcite.rhyolite.com>
Message-Id: <404EFA10-91F6-11D7-9B54-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On donderdag, mei 29, 2003, at 17:44 Europe/Amsterdam, Vernon Schryver 
wrote:

>> I found the following to be an interesting read:
>> http://www.cdt.org/spam/

>> It shows that even five years ago or so most ligitimate businesses
>> advertising legitimate services through spam employed header forgery.
>> ...

> It is an article of faith for many people that most spam involves
> header forgery, but no one seems to have better support than intuition
> for that faith.  Where in the report at http://www.cdt.org/spam/ does
> it say that "most ligitimate businesses advertising legitimate services
> through spam employed header forgery?"

Ok, I can't find it right now, and the thing is too big to completely 
reread.

> A lot of spam does involve header forgery, but a lot clearly does not.
> The problem with concluding that "most" spam uses header forgery is
> that it encourages looking for solutions to header forgery instead of
> stopping unsolicited bulk mail.

Stopping header forgery would be useful in and of itself, but 
regardless of that it will also help against unsollicitated bulk email. 
I downloaded the list with known spam address blocks from spews.org. It 
lists around 1600 spammers and 14000 addresses or address blocks. 
Obviously spammers are trying hard to cover their tracks. Filtering out 
1600 spammers is easier than filtering out many more thousands of 
individual addresses. I'm assuming we can come up with some identifier 
that's harder to change than an IP address.

A quick look at a week's worth of email for an account I've used to 
post to Usenet for nearly 10 years (370, 98% spam or mailinglists I 
can't unsubscribe) tells me around 75% of the spam I received either 
has obvious header problems or employs some kind of anti-anti-spam 
measure. Also around 75% is of a pharmaceutical, sexual or financial 
nature (often at least two of those at the same time). There is no 
obvious correlation.

> That leads to a major problem in dealing with spam.  Most people
> who say they want to stop spam in fact have other goals that they
> value more.

Yes, it seems like many of them are more interested in perpetuating the 
status quo.




From owner-ietf@ietf.org  Thu May 29 13:23:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10951
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 13:23:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LR14-0004dj-Ik
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 13:16:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LQtN-0004TB-4W
	for ietf@asgard.ietf.org; Thu, 29 May 2003 13:08:41 -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 NAA10544
	for <ietf@ietf.org>; Thu, 29 May 2003 13:08:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LQrl-0000mI-00
	for ietf@ietf.org; Thu, 29 May 2003 13:07:01 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LQrj-0000mF-00
	for ietf@ietf.org; Thu, 29 May 2003 13:07:00 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.9/8.12.9) id h4TH8aWE021951
	for ietf@ietf.org env-from <vjs>;
	Thu, 29 May 2003 11:08:36 -0600 (MDT)
Date: Thu, 29 May 2003 11:08:36 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200305291708.h4TH8aWE021951@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: spam
References: <404EFA10-91F6-11D7-9B54-00039388672E@muada.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Iljitsch van Beijnum <iljitsch@muada.com>

> ...
> Stopping header forgery would be useful in and of itself, 

Many people who say that have strange notions of "header forgery."
They consider using your home mail address as a sender or return email
address when sending mail while away from home to be "forgery" but
they don't have any problems using their home postal addresses on
postcards while on vacation.

>                                                           but 
> regardless of that it will also help against unsollicitated bulk email. 

That is not logical, unless you assume that spammers have no
alternative to using header forgery.

> I downloaded the list with known spam address blocks from spews.org. It 
> lists around 1600 spammers and 14000 addresses or address blocks. 
> Obviously spammers are trying hard to cover their tracks. Filtering out 
> 1600 spammers is easier than filtering out many more thousands of 
> individual addresses. I'm assuming we can come up with some identifier 
> that's harder to change than an IP address.

That is a tall assumption.  Unless you involve national governments,
I've never yeard of an identifier that is harder to change than an IP
address, except when you get your IP addresses from ISPs that look away
from the spam of their customers and the customers of their resellers.
Such ISPs would be as happy to sell new identifiers of whatever sort
you like to spammers as they have been happy to rent IP addresses.


> A quick look at a week's worth of email for an account I've used to 
> post to Usenet for nearly 10 years (370, 98% spam or mailinglists I 
> can't unsubscribe) tells me around 75% of the spam I received either 
> has obvious header problems or employs some kind of anti-anti-spam 
> measure. Also around 75% is of a pharmaceutical, sexual or financial 
> nature (often at least two of those at the same time). There is no 
> obvious correlation.

I notice that you wrote "header problems" instead of "forgery."

> > That leads to a major problem in dealing with spam.  Most people
> > who say they want to stop spam in fact have other goals that they
> > value more.
>
> Yes, it seems like many of them are more interested in perpetuating the 
> status quo.

I do not agree with that.  Some people do have usually unconcious
interests in the status quo, but most people are doing illogical
things like attacking header forgery as if spammers could not create
zillions of valid user names at free or cheap providers or domain
names and avoid header forgery.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Thu May 29 13:39:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11407
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 13:39:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LRIA-0005G2-ED
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 13:34:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LR3Z-0004i0-3m
	for ietf@asgard.ietf.org; Thu, 29 May 2003 13:19:13 -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 NAA10784
	for <ietf@ietf.org>; Thu, 29 May 2003 13:19:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LR1x-0000oj-00
	for ietf@ietf.org; Thu, 29 May 2003 13:17:33 -0400
Received: from tx1.wvinternetservices.com ([66.118.64.16])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LR1w-0000og-00
	for ietf@ietf.org; Thu, 29 May 2003 13:17:32 -0400
Received: from a (dhcp-69-43-8-045.park.dialup.citynet.net [69.43.8.45])
	by tx1.wvinternetservices.com (8.12.9/8.12.6=Outbound) with SMTP id h4THfTnl032236
	for <ietf@ietf.org>; Thu, 29 May 2003 13:41:30 -0400
Message-ID: <001901c32606$649d5e40$2d082b45@a>
From: "Bill Cunningham" <billc44@citynet.net>
To: <ietf@ietf.org>
Subject: spam
Date: Thu, 29 May 2003 13:18:58 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Personally I think the best idea I've seen yet is the idea of a prefix, such
as ADV in the subject line. The real problem I agree is with sorting through
unsolicited mail for what you really want. It maybe possible to put
something like ADV in a protocol header. Or maybe that is too extreme.

    Bill





From owner-ietf@ietf.org  Thu May 29 14:17:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12701
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 14:17:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LRO7-0005ng-BW
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 13:40:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LRLH-0005NG-GT
	for ietf@asgard.ietf.org; Thu, 29 May 2003 13:37:31 -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 NAA11391
	for <ietf@ietf.org>; Thu, 29 May 2003 13:37:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LRJf-0000xP-00
	for ietf@ietf.org; Thu, 29 May 2003 13:35:51 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LRJf-0000xE-00
	for ietf@ietf.org; Thu, 29 May 2003 13:35:51 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id NAA08993;
	Thu, 29 May 2003 13:33:01 -0400
Date: Thu, 29 May 2003 13:34:05 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Iljitsch van Beijnum <iljitsch@muada.com>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <FA2605DA-91E4-11D7-9B54-00039388672E@muada.com>
Message-ID: <Pine.LNX.4.44.0305291332220.16521-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Thu, 29 May 2003, Iljitsch van Beijnum wrote:

> It shows that even five years ago or so most ligitimate businesses
> advertising legitimate services through spam employed header forgery.
> If we can't stop spammers from spamming we should at least be able to
> stop them from doing so in ways that add insult to injury by derailing
> the entire email service.
>
> So let's have that BOF.

Agreed. But I think the current legislation will make header forgery
illegal, and already is in some states.

I expect that Type 1 spammers will comply. Some already are.

		--Dean




From owner-ietf@ietf.org  Thu May 29 14:26:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13116
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 14:26:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LRvq-0006mT-Gf
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 14:15:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LRq2-0006PQ-3A
	for ietf@asgard.ietf.org; Thu, 29 May 2003 14:09:18 -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 OAA12356
	for <ietf@ietf.org>; Thu, 29 May 2003 14:09:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LRoP-0001B5-00
	for ietf@ietf.org; Thu, 29 May 2003 14:07:37 -0400
Received: from bay7-dav20.bay7.hotmail.com ([64.4.10.124] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LRoO-0001Aq-00
	for ietf@ietf.org; Thu, 29 May 2003 14:07:37 -0400
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Thu, 29 May 2003 11:08:44 -0700
Received: from 156.153.255.196 by bay7-dav20.bay7.hotmail.com with DAV;
	Thu, 29 May 2003 18:08:44 +0000
X-Originating-IP: [156.153.255.196]
X-Originating-Email: [fritz_saad@hotmail.com]
From: "Fritz F. Saad" <Fritz_Saad@hotmail.com>
To: "Bill Cunningham" <billc44@citynet.net>, <ietf@ietf.org>
References: <001901c32606$649d5e40$2d082b45@a>
Subject: Re: spam
Date: Thu, 29 May 2003 12:08:27 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <BAY7-DAV20UDA1XiHY500025ebe@hotmail.com>
X-OriginalArrivalTime: 29 May 2003 18:08:44.0814 (UTC) FILETIME=[57EDD2E0:01C3260D]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I can only echo Bill's comment on that regards, and I don't find that too
extreme.

Cheers,
Fritz.
----- Original Message ----- 
From: "Bill Cunningham" <billc44@citynet.net>
To: <ietf@ietf.org>
Sent: Thursday, May 29, 2003 11:18 AM
Subject: spam


> Personally I think the best idea I've seen yet is the idea of a prefix,
such
> as ADV in the subject line. The real problem I agree is with sorting
through
> unsolicited mail for what you really want. It maybe possible to put
> something like ADV in a protocol header. Or maybe that is too extreme.
>
>     Bill
>
>
>
>



From owner-ietf@ietf.org  Thu May 29 14:51:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13986
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 14:51:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LSMr-0000Ug-SI
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 14:43:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LS6Z-0007yd-V0
	for ietf@asgard.ietf.org; Thu, 29 May 2003 14:26:23 -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 OAA13107
	for <ietf@ietf.org>; Thu, 29 May 2003 14:26:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LS4y-0001LP-00
	for ietf@ietf.org; Thu, 29 May 2003 14:24:44 -0400
Received: from brmea-mail-2.sun.com ([192.18.98.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LS4x-0001LM-00
	for ietf@ietf.org; Thu, 29 May 2003 14:24:43 -0400
Received: from esunmail ([129.147.58.198])
	by brmea-mail-2.sun.com (8.12.9/8.12.9) with ESMTP id h4TIQLYU013903
	for <ietf@ietf.org>; Thu, 29 May 2003 12:26:21 -0600 (MDT)
Received: from xpa-fe2 (esunmail [129.147.58.120]) by edgemail1.Central.Sun.COM
 (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003))
 with ESMTP id <0HFN00ERWV7WA3@edgemail1.Central.Sun.COM> for ietf@ietf.org;
 Thu, 29 May 2003 12:26:21 -0600 (MDT)
Received: from sun.com ([129.146.18.20])
 by mail.sun.net (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003))
 with ESMTPSA id <0HFN00051V7VJZ@mail.sun.net> for ietf@ietf.org; Thu,
 29 May 2003 12:26:20 -0600 (MDT)
Date: Thu, 29 May 2003 11:26:19 -0700
From: Alain Durand <Alain.Durand@Sun.COM>
Subject: Re: The utilitiy of IP is at stake here
To: dcrocker@brandenburg.com
Cc: Tony Hain <alh-ietf@tndh.net>, "'IETF'" <ietf@ietf.org>
Message-id: <3ED650CB.3000205@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-15; format=flowed
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920
 Netscape/7.0
References: <017601c32566$cb6fcea0$56144104@eagleswings>
 <7534992907.20030528181948@brandenburg.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA13986

I tend to agree with Dave Crocker, getting 100+ millions users
to upgrade to SMTPng is not going to be any easier
than getting them to move to IPv6... It will also suffer from
the second design syndrome. I will not fool myself and believe
it can happen overnight....
... although, due to the volume of spam, there is little choice but 
doing it.

For this effort to be effective, I think it will have to be done
in a way that is at odds with the traditional IETF thinking:

1) Compatibility with SMTP is not desirable
    ==> if not, spam will be forward compatible!

2) Some form of privacy is not desirable
    ==> You cannot define Spam but you know this is spam when you see one.
            As you cannot put any reliable filters in place,  your only
            solution is the legal route. For this to work, you want to 
be able
            to trace exactly who was sending the mail.

3) To much scalability is not desirable
     ==> There is (almost) no direct cost per mail, but a lot of 
indirect costs.
            This may actually very well be the root cause of the problem.
            There is relatively little spam in regular snail mail or 
telephone,
            not only because of legislative regulations, but also
            because it cost money per message. This regulate the flow.
            One cannot sent millions of mail/phone calls for just $20...
            Another way of saying this is that SMTP is a victim of the 
IETF credo,
            the protocol scales too well.


     - Alain.







Dave Crocker wrote:

>Tony and Steve, et al,
>
>TH> In context, it is clearly the right of a mail server operator to refuse
>TH> mail. My concern is more about the precedent where a large ISP decides
>TH> that address ranges have particular application semantics. 
>...
>TH> The IETF needs to recognize that the ISPs don't really have a good
>TH> alternative, and work on providing one.
>
>and
>
>SMB> Yes.  Normally, I'd worry a lot about backwards compatibility.  In this
>SMB> case, I think the problems for ISPs -- and users -- are so severe that
>SMB> people will switch *rapidly* to a new protocol if it solved most of the
>SMB> spam problem.
>
>
>Most of this thread is really about legal and customer service issues.
>I do not see how it is an IETF topic, no matter how much each of us
>might (and do) feel strongly about it.
>
>
>However I'll join the ranks of those heartily supporting your
>conclusion about the absence of good alternatives...
>
>However there is a catch:
>
>      With respect to spam, and many other content-related activities,
>      what does it mean to provide a good alternative?
>
>      To answer this means we need to understand the problem very well
>      and understand the technical underpinnings of the problem very
>      well.
>
>It is easy to note features that are lacking from email, but dangerous
>to assume that adding those features will result in their being adopted
>or that their adoption will magically fix the problem at hand.
>
>Worse is that, by and large, spam is a topic for which reasoned
>discussion -- and especially careful analysis -- is so far proving
>impossible in an open forum. Between the formal fuzziness of the topic,
>the strong emotion it engenders, and the compulsive self-interest of
>many constituencies, the reality is fragmented, heated exchanges, rather
>than anything really productive.
>
>Here are some realities that I think we must juggle:
>
>1.  We do not understand the full range of email (ie, electronic
>mediated human exchanges) very well at all;
>
>2.  An installed base of 100 million users should be expected to adopt
>changes very, very slowly
>
>3. Each change will have large, unintended consequences, most of which
>will be undesirable. (This statement is an absolute cliché in serious
>discussions about organizational and social change.)
>
>Note that the definition of spam largely depends upon the person making
>the definition; unless and until we can develop of reasonably simple
>definition that has a) broad acceptance, and b) a largely technical
>basis, then it is pure folly for the IETF to think it can do anything
>major in this arena.  It might be useful for us to standardize some relatively
>straight tools, like a client/filter-server exchange protocol, but we
>are not going to achieve really strategic improvements.
>
>I should also note that the last two years have seen at least two
>efforts to consider a replacement email service -- or at least an
>alternative one -- but that neither seems to have achieved a critical
>mass of interest.
>
>And before anyone claims that spam will be the flag around which
>Email(ng) troops will rally, I'll ask what changes anyone thinks are
>required. As soon as anyone tries to answer that, everyone else should
>watch the style of responses they get...
>
>(if you want to save time, just look at the discussion of spam on the
>ietf over the last few days. has it been analytic? has it been systemic?
>has it been productive? -- except for the thread that Tony just started,
>of course.)
>
>d/
>--
> Dave Crocker <mailto:dcrocker@brandenburg.com>
> Brandenburg InternetWorking <http://www.brandenburg.com>
> Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>
>
>
>  
>





From owner-ietf@ietf.org  Thu May 29 15:04:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14540
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 15:04:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LSN5-0000Xv-OF
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 14:43:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LSBX-00005y-8u
	for ietf@asgard.ietf.org; Thu, 29 May 2003 14:31:31 -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 OAA13341
	for <IETF@ietf.org>; Thu, 29 May 2003 14:31:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LS9v-0001Oq-00
	for IETF@ietf.org; Thu, 29 May 2003 14:29:51 -0400
Received: from [208.184.79.11] (helo=clint.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LS9u-0001Oe-00
	for IETF@ietf.org; Thu, 29 May 2003 14:29:50 -0400
Received: from bbprime (208.184.79.253.songbird.com [208.184.79.253] (may be forged))
	by clint.songbird.com (8.11.6/8.11.6) with ESMTP id h4TIXkx21454
	for <IETF@ietf.org>; Thu, 29 May 2003 11:33:46 -0700
Date: Thu, 29 May 2003 11:30:56 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <13596858415.20030529113056@brandenburg.com>
To: IETF@ietf.org
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <a05200f00bafbc9fdb2f1@[10\.0\.1\.20]>
References: <017601c32566$cb6fcea0$56144104@eagleswings>
 <07a201c3259a$f8fbd1f0$0a00000a@atkielski.com>
 <a05200f00bafbc9fdb2f1@[10.0.1.20]>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks,

JM> FWIW, and not to drag us too far into a legal discussion, but the 
JM> above is not correct for the United States.   In the US, ISPs are 
JM> not, and never have been viewed, as common carriers.  And, as one can


I can see that my point was entirely missed:

Yes, this is an important topic.

But no, it does not belong in the IETF.  We have no *** IETF *** work to
do.


d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Thu May 29 15:06:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12700
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 14:17:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LRO7-0005na-1Q
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 13:40:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LRKH-0005N9-AY
	for ietf@asgard.ietf.org; Thu, 29 May 2003 13:36:29 -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 NAA11380
	for <ietf@ietf.org>; Thu, 29 May 2003 13:36:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LRIf-0000xB-00
	for ietf@ietf.org; Thu, 29 May 2003 13:34:49 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LRIe-0000wq-00
	for ietf@ietf.org; Thu, 29 May 2003 13:34:48 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id NAA00423;
	Thu, 29 May 2003 13:27:56 -0400
Date: Thu, 29 May 2003 13:28:51 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: =?UTF-8?Q?John_Loughney?= <john.loughney@kolumbus.fi>
cc: jstracke@centive.com, <ietf@ietf.org>
Subject: Re: =?UTF-8?Q?Re:_spam?=
In-Reply-To: <1054204355389>
Message-ID: <Pine.LNX.4.44.0305291308330.16521-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by ietf.org id OAA12700

Radical anti-spammers, like other kinds of radicals, make unreasonable
demands, employ illegal methods such as extortion and terrorism (or
techno-terrorism, in this case), feel there is no other point of view
other than their own, and that other points of views can be supressed.
They feel that because the law won't give them what they want, that they
can employ whatever methods they feel like to achieve their goals.

Frequently, they do more harm to their goals as a result. For example,
Palestinian radicals blow themselves up. Radical Jewish settlers create
illegal settlements, and terrorize the local population.

When the leadership of a group doesn't repudiate and root out the
radicals, significant harm is done to their goals.

For example, the Israeli government repudiates and cracks down on illegal
settlements. While the Palestinian government doesn't repudiate the
Palestinian radicals. The result is a loss of credibility for the
Palestinians.  By contract, the actions of the radical settlers inflaming
the Palestinians is clearly harmful to Israel, but has little effect on
the credibility of the Israeli government.

Some might think it is inappropriate to compare violent terrorism to
techno-terrorism.  The difference is primarilly that techno-terrorism
doesn't result in loss of life. Just crashed computers.  But the mentality
is essentially the same.   Radical Anti-spammers are willing to give their
jobs and livelihood for their beliefs.

And like the Palestinians, the lies, abuse, and misdeeds of the radical
anti-spammers discredit the entire group, because the leadership refuses
to root them out. The leadership is itself radical.

		--Dean

On Thu, 29 May 2003, [UTF-8] John Loughney wrote:

> Hi,
>
> What is a 'radical anti-spammer'?
>
> ----------
>
> This is the _false_ assertion of
> radical anti-spammers, who seem to me to be the abusers.  Chris Neill
> (antispammer open relay abuser eventually fired from Verio--he was
> ironically, an abuse admin) was shocked to learn he was't anonymous, like
> he thought.
>
> The claims made by antispammers about open relays are false. Type 1
> spammers seem to get that, judging by their behavior.  But radical
> antispammers don't.
>
> 		--Dean
>
> On Wed, 28 May 2003, John Stracke wrote:
>
> > Dean Anderson wrote:
> >
> > >We are lucky that spammers don't get a discount
> > >
> > Open relays give them a five-finger discount.
> >
> > --
> > /===============================================================\
> > |John Stracke      |jstracke@centive.com                        |
> > |Principal Engineer|http://www.centive.com                      |
> > |Centive           |My opinions are my own.                     |
> > |===============================================================|
> > |"Power corrupts; Powerpoint corrupts absolutely." -- Vint Cerf |
> > \===============================================================/
> >
> >
> >
> >
>
>
>     
>




From owner-ietf@ietf.org  Thu May 29 15:57:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17311
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 15:57:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LSn6-0007tb-SK
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 15:10:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LSlL-00078X-NN
	for ietf@asgard.ietf.org; Thu, 29 May 2003 15:08:31 -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 PAA15146
	for <ietf@ietf.org>; Thu, 29 May 2003 15:08:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LSjj-0001fb-00
	for ietf@ietf.org; Thu, 29 May 2003 15:06:51 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LSjj-0001fY-00
	for ietf@ietf.org; Thu, 29 May 2003 15:06:51 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 208367; Thu, 29 May 2003 14:07:58 -0500
Message-ID: <3ED65AAB.4090903@ehsco.com>
Date: Thu, 29 May 2003 14:08:27 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Bill Cunningham <billc44@citynet.net>
CC: ietf@ietf.org
Subject: Re: spam
References: <001901c32606$649d5e40$2d082b45@a>
In-Reply-To: <001901c32606$649d5e40$2d082b45@a>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/29/2003 12:18 PM Bill Cunningham wrote:
> Personally I think the best idea I've seen yet is the idea of a prefix,
>  such as ADV in the subject line.

Using the current transfer and message-format models, that requires
post-transfer processing. At a minimum, you would be legitimizing
artificially increased bandwdith and processing demands (assuming that
everybody complied with the law).

> It maybe possible to put something like ADV in a protocol header. Or
> maybe that is too extreme.

A special header would be feasible if the transfer headers and message
headers were separate, since you could reject the message before the
transfer. The same results would also be possible with ESMTP using
something like an ;ADV extension to the MAIL FROM command. Both of those
require wholesale upgrades to have any impact, so in the meantime you'd
still have to rely on post-transfer processing.

There is another significant problem with using an ADV tag with all
commercial mail, which is that it doesn't adequately distinguish between
spam and legitimate commercial mail. Would upgrade notification messages
for stuff like software need to be marked? Would domain renewal notices
from your registrar need to be marked? Would you need to explicitly opt-in
to get those messages without them being marked?

Seems to me we should be defining laws that put the onus on the spammers
rather than on the recipients and legitimate business communications.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Thu May 29 16:14:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17807
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 16:14:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LTai-0002Uk-6w
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 16:01:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LTAS-0001WN-Gx
	for ietf@asgard.ietf.org; Thu, 29 May 2003 15:34:28 -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 PAA16651
	for <ietf@ietf.org>; Thu, 29 May 2003 15:34:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LT8n-0001pq-00
	for ietf@ietf.org; Thu, 29 May 2003 15:32:45 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LT8m-0001pm-00
	for ietf@ietf.org; Thu, 29 May 2003 15:32:44 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S29850> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 29 May 2003 12:34:16 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Thu, 29 May 2003 12:34:13 -0700
Message-ID: <00e401c32619$49512b40$56144104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <a05200f00bafbc9fdb2f1@[10.0.1.20]>
Importance: Normal
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA17807

John Morris wrote:
> FWIW, and not to drag us too far into a legal discussion, but the 
> above is not correct for the United States.   In the US, ISPs are 
> not, and never have been viewed, as common carriers. 

I agree on the legal point, but note that as we move further down the
path of VOIP that is likely to change. My point was more about the
inconsistency of wanting absolute control, but zero responsibility. For
starters, they don't have absolute control, and even if they try to
establish it, the endpoints will simply push them down a layer and
tunnel over whatever is allowed. More importantly they want to maintain
their zero responsibility position, and that will take precedence over
control as soon as they are taken to court because they didn't prevent
an action which they had the means to control through ever deeper packet
inspection. 

The fundamental legal issue we need to deal with is the ability to
absolutely identify the originator of the mail. Is that precluded by any
existing privacy laws? If not, identity would provide the means to
pursue financial recourse for wasted time and resources. If so, we have
a non-technical issue that may prevent any solution.

Tony




From owner-ietf@ietf.org  Thu May 29 16:14:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17806
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 16:14:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LTam-0002WQ-G2
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 16:01:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LTQc-0001y7-HB
	for ietf@asgard.ietf.org; Thu, 29 May 2003 15:51: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 PAA17134
	for <ietf@ietf.org>; Thu, 29 May 2003 15:51:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LTP0-0001w9-00
	for ietf@ietf.org; Thu, 29 May 2003 15:49:30 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LTOz-0001w1-00
	for ietf@ietf.org; Thu, 29 May 2003 15:49:30 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S2985B> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 29 May 2003 12:51:07 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'IETF'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Thu, 29 May 2003 12:51:04 -0700
Message-ID: <00e901c3261b$a3dbcf50$56144104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <3ED650CB.3000205@sun.com>
Importance: Normal
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA17806

Alain Durand wrote:
> I tend to agree with Dave Crocker, getting 100+ millions 
> users to upgrade to SMTPng is not going to be any easier than 
> getting them to move to IPv6... It will also suffer from the 
> second design syndrome. I will not fool myself and believe it 
> can happen overnight.... 

In this case, I disagree. Yes SMTP will have to exist for some time to
come, but it wouldn't take much to convince people that moving to a new
mail system would either reduce spam, or had adequate mechanisms for
financial recourse. If the courts routinely granted judgments to
individuals of 100 $/euro for every received unsolicited message, people
would jump at the chance to run the new mail tool, and spam as we know
it would loose its economic viability. Making that work means absolute
traceability of the message origin.

 
> For this effort to be effective, I think it will have to be 
> done in a way that is at odds with the traditional IETF thinking:
> 
> 1) Compatibility with SMTP is not desirable
> 2) Some form of privacy is not desirable
> 3) To much scalability is not desirable

I agree, with the condition that scalability should be a factor
everywhere except the originator. 

Tony




From owner-ietf@ietf.org  Thu May 29 16:46:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18717
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 16:46:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LU7J-0004Of-L6
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 16:35:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LTpr-0003tF-VI
	for ietf@asgard.ietf.org; Thu, 29 May 2003 16:17:15 -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 QAA18065
	for <ietf@ietf.org>; Thu, 29 May 2003 16:17:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LToG-00029R-00
	for ietf@ietf.org; Thu, 29 May 2003 16:15:36 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LToF-00029O-00
	for ietf@ietf.org; Thu, 29 May 2003 16:15:35 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4TKHDKk039527
	for <ietf@ietf.org>; Thu, 29 May 2003 22:17:13 +0200 (CEST)
Message-ID: <088701c3261f$4a7b6bb0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <200305291250.h4TCojKT015845@ginger.lcs.mit.edu>
Subject: Re: spam
Date: Thu, 29 May 2003 22:17:12 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Noel writes:

> It *better* be solvable, otherwise when email
> becomes 99% spam, everyone will stop reading email.

I wouldn't worry about that.  When everyone stops reading e-mail, spam will
disappear again.  Remember, spammers only send out spam because people reply
to it.  If nobody replies, they'll stop.

Actually nearly 99% of my e-mail _already is_ spam, but I still read the
non-spam messages.

As for the problem being solvable, I'm not at all confident about that.

It's interesting to note that almost all spam references a handful of
products or services.  Clearly, there are quite a few people out there who
want larger penises, or are in tremendous debt, or are being crushed by
large mortgages, or are in search of pictures of teenage girls, otherwise
these advertisements would not dominate spam.  And somebody is still trying
to cut deals with mysterious executives of Nigerian Oil Development Central
Bank, judging by the number of letters I receive on that.

Maybe the real problem is that there are too many dolts on the Net who
actually reply to this spam.  Eliminate them, and the spam will go away.
Maybe an IQ test for each new Internet subscriber; anyone with a
single-digit score isn't allowed to sign up without adult supervision.

> I'm willing to spend $.25 to communicate with someone
> I've never sent email to before.

I'm not.  The e-mail only costs $0.000000007 to send, so why should I give
anyone $0.25 for it?

> I doubt very much the spammers who boast of sending
> millions of messages a day are willing to spend $.25
> each message for the privilege.

I don't blame them, nor do I think they should be required to pay that.  I
won't even spend that on one message.  If I want to throw money out the
window, there are already lots of other scams that will deprive me of my
wealth just as quickly.




From owner-ietf@ietf.org  Thu May 29 16:53:48 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18986
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 16:53:48 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LU7J-0004P0-UU
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 16:35:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LTs7-000419-Cc
	for ietf@asgard.ietf.org; Thu, 29 May 2003 16:19:35 -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 QAA18096
	for <ietf@ietf.org>; Thu, 29 May 2003 16:19:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LTqV-0002A8-00
	for ietf@ietf.org; Thu, 29 May 2003 16:17:55 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LTqU-0002A5-00
	for ietf@ietf.org; Thu, 29 May 2003 16:17:54 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4TKJWKk039544
	for <ietf@ietf.org>; Thu, 29 May 2003 22:19:32 +0200 (CEST)
Message-ID: <088c01c3261f$9dcc00e0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <017601c32566$cb6fcea0$56144104@eagleswings> <07a201c3259a$f8fbd1f0$0a00000a@atkielski.com> <a05200f00bafbc9fdb2f1@[10.0.1.20]>
Subject: Re: The utilitiy of IP is at stake here
Date: Thu, 29 May 2003 22:19:32 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John writes:

> In the US, ISPs are not, and never have been
> viewed, as common carriers.

I recall a case involving CompuServe in which it was treated at least
partially as a common carrier, not responsible for the content of its
network.

>    (1) Treatment of publisher or speaker
>        No provider or user of an interactive
>        computer service [read, an ISP] shall be
>        treated as the publisher or speaker of
>        any information provided
>        by another information content provider.

How is this reconciled with the DMCA?





From owner-ietf@ietf.org  Thu May 29 17:03:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19680
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 17:03:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LU7L-0004Qu-PV
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 16:35:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LU2J-0004CJ-4z
	for ietf@asgard.ietf.org; Thu, 29 May 2003 16:30:07 -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 QAA18316
	for <ietf@ietf.org>; Thu, 29 May 2003 16:30:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LU0h-0002De-00
	for ietf@ietf.org; Thu, 29 May 2003 16:28:27 -0400
Received: from [208.184.79.11] (helo=clint.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LU0g-0002DO-00
	for ietf@ietf.org; Thu, 29 May 2003 16:28:26 -0400
Received: from bbprime (208.184.79.253.songbird.com [208.184.79.253] (may be forged))
	by clint.songbird.com (8.11.6/8.11.6) with ESMTP id h4TKWLx28396;
	Thu, 29 May 2003 13:32:21 -0700
Date: Thu, 29 May 2003 13:29:30 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <127103972754.20030529132930@brandenburg.com>
To: "Tony Hain" <alh-ietf@tndh.net>
CC: "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <00e901c3261b$a3dbcf50$56144104@eagleswings>
References: <00e901c3261b$a3dbcf50$56144104@eagleswings>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony,

TH> come, but it wouldn't take much to convince people that moving to a new
TH> mail system would either reduce spam,

Please indicate some historical basis for moving an installed base of
users on this kind of scale and for this kind of reason.


TH>  If the courts routinely granted judgments to
TH> individuals of 100 $/euro for every received unsolicited message, people

a transition plan for 100 million users that relies on an "if"
concerning entirely new behaviors for a large number of independent
judicial systems around the world is a rather fragile dependency, to say
the least.

(and, yes, I realize that that was just an example.  so, please, go
ahead and provide a scenario that is not equally fragile.  i can't.)


TH> would jump at the chance to run the new mail tool, and spam as we know
TH> it would loose its economic viability. Making that work means absolute
TH> traceability of the message origin.
>> For this effort to be effective, I think it will have to be
>> done in a way that is at odds with the traditional IETF thinking:
>> 
>> 1) Compatibility with SMTP is not desirable

why?


>> 2) Some form of privacy is not desirable
>> 3) To much scalability is not desirable

scalability is not desirable?  wow.

please explain.



d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Thu May 29 17:04:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19711
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 17:04:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LU7M-0004R5-3V
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 16:35:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LU3B-0004DD-Mp
	for ietf@asgard.ietf.org; Thu, 29 May 2003 16:31:01 -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 QAA18390
	for <ietf@ietf.org>; Thu, 29 May 2003 16:30:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LU1Z-0002E5-00
	for ietf@ietf.org; Thu, 29 May 2003 16:29:21 -0400
Received: from [64.70.31.5] (helo=www.darkuncle.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LU1Z-0002E0-00
	for ietf@ietf.org; Thu, 29 May 2003 16:29:21 -0400
Received: from www.darkuncle.net (elvis@localhost [127.0.0.1])
	by www.darkuncle.net (8.12.9/8.12.9) with ESMTP id h4TKUaWq048352;
	Thu, 29 May 2003 13:30:36 -0700 (PDT)
	(envelope-from sfrancis@darkuncle.net)
Received: (from sfrancis@localhost)
	by www.darkuncle.net (8.12.9/8.12.9/Submit) id h4TKUZEV048351;
	Thu, 29 May 2003 13:30:35 -0700 (PDT)
Date: Thu, 29 May 2003 13:30:35 -0700
From: Scott Francis <darkuncle@darkuncle.net>
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Re: spam
Message-ID: <20030529203035.GN99106@darkuncle.net>
References: <3ED27906.1030002@ehsco.com> <Pine.LNX.4.44.0305261653061.3699-100000@commander.av8.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="SCOJXUq1iwCn05li"
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0305261653061.3699-100000@commander.av8.net>
User-Agent: Mutt/1.3.25i
X-Operating-System: OpenBSD <http://www.openbsd.org>
X-PGP-Fingerprint: 7429 F75D D3F5 FA45 C6D7  D25B 59A0 7B8C 5537 F527
X-What-Happen: Somebody set up us the bomb.
Sender: owner-ietf@ietf.org
Precedence: bulk


--SCOJXUq1iwCn05li
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, May 26, 2003 at 04:58:41PM -0400, dean@av8.com said:
[snip]
> Most of the examples of harmful spam are of the Type 2 and Type 3 variety,
> which is why Congress and the states have moved to address Type 2. Type 3
> is already illegal.

there's a non-harmful kind of spam? Do tell ...
--=20
Scott Francis || darkuncle (at) darkuncle (dot) net
      illum oportet crescere me autem minui

--SCOJXUq1iwCn05li
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+1m3rWaB7jFU39ScRAls6AJ4lR+GIHIFA30QTNf9kCx9obfZB8ACdFFqf
zmGxPyS5b4IHDrwQD5S0qhI=
=i2Kw
-----END PGP SIGNATURE-----

--SCOJXUq1iwCn05li--



From owner-ietf@ietf.org  Thu May 29 17:18:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20343
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 17:18:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LUZp-0006Wp-6t
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 17:04:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LUFp-0004Yw-2l
	for ietf@asgard.ietf.org; Thu, 29 May 2003 16:44:05 -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 QAA18664
	for <ietf@ietf.org>; Thu, 29 May 2003 16:44:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LUED-0002Gp-00
	for ietf@ietf.org; Thu, 29 May 2003 16:42:25 -0400
Received: from out005pub.verizon.net ([206.46.170.143] helo=out005.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LUEC-0002Gf-00
	for ietf@ietf.org; Thu, 29 May 2003 16:42:24 -0400
Received: from earthlink.net ([4.65.81.213]) by out005.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030529204332.MIVL20032.out005.verizon.net@earthlink.net>;
          Thu, 29 May 2003 15:43:32 -0500
Message-ID: <3ED67014.9E8161B7@earthlink.net>
Date: Thu, 29 May 2003 13:39:48 -0700
From: Peter Deutsch <pdeutsch@earthlink.net>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: alh-ietf@tndh.net
CC: "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
References: <00e901c3261b$a3dbcf50$56144104@eagleswings>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out005.verizon.net from [4.65.81.213] at Thu, 29 May 2003 15:43:32 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

g'day,

Tony Hain wrote:
> 
> Alain Durand wrote:
> > I tend to agree with Dave Crocker, getting 100+ millions
> > users to upgrade to SMTPng is not going to be any easier than
> > getting them to move to IPv6... It will also suffer from the
> > second design syndrome. I will not fool myself and believe it
> > can happen overnight....
> 
> In this case, I disagree. Yes SMTP will have to exist for some time to
> come, but it wouldn't take much to convince people that moving to a new
> mail system would either reduce spam, or had adequate mechanisms for
> financial recourse. If the courts routinely granted judgments to
> individuals of 100 $/euro for every received unsolicited message, people
> would jump at the chance to run the new mail tool, and spam as we know
> it would loose its economic viability. Making that work means absolute
> traceability of the message origin.
> 
> > For this effort to be effective, I think it will have to be
> > done in a way that is at odds with the traditional IETF thinking:
> >
> > 1) Compatibility with SMTP is not desirable
> > 2) Some form of privacy is not desirable
> > 3) To much scalability is not desirable
> 

Sorry, guys, I don't see this one taking wing. I'd agree that many of us
would jump at the chance to receive the occasional $100 gratuity, but
far fewer would want to sign up for the corollary, a system in which you
willingly and consciously abandon all hopes for privacy and anonymity. I
think the issue of preserving privacy will be a major one for us all in
the coming years, so starting the design of a new system with the axiom
that privacy is not desirable seems, well, I find it hard to describe
without being either flip or rude.

I personally want a next generation system that would *increase* my
privacy, not attempt to make a virtue out of *removing* the few shreds
of annonymity I have left. I would specifically refuse to use such a
system. And yes, I also want it to make unsolicited, bulk email harder
to send to me, but not at the cost of my privacy.

As I've already pointed out, I think we need to have another look at the
problem definition before we get too far down the design path. For
example, virtually every posting on this topic over the past few days
seems to be labouring under the assumption that the spammer wants to
trigger a commercial exchange of some sort with the recipient (with the
corollaries that the commercial entities can be traced, they will allow
you to impose costs upon them as a cost of doing business, etc). From
looking at a lot of the crap I'm getting, I'd say that a certain
percentage of it has no reasonable expectation that I'll react to it at
all (e.g. the Portugese language spam, the spam containing viruses, the
spam containing random strings of junk which I assume might help it get
past spam filters, but which guarantee that I wont take the sender
seriously as a someone I'd be willing to share my credit card with,
etc). 

Here's a radical thought, what if some percentage of this problem is
simply economic terrorism and random script kiddies doing the equivalent
of scribbling on the walls and tagging the billboards? No amount of
legislated Subject lines, protocol design and/or education will solve
that problem. In case you missed it, graffitti is already illegal, but
it hasn't been eliminated by legislation.

Maybe somebody should get some foundation to fund study to trace a pile
of this stuff to its roots and do some statistically valid analysis on
its origins, goals, etc. Otherwise, we seem to be in grave danger of
designing a system (spam control) without ever talking to its users (the
spam generators). Sounds like a recipe for disaster to me...

				- peterd



-- 
---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software

                        "Bungle..."
               "That's an 'i', you idiot..."
                  "Oh, right. 'Bingle..."

                            - Red versus Blue...

---------------------------------------------------------------------



From owner-ietf@ietf.org  Thu May 29 17:29:49 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20737
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 17:29:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LUZq-0006ZV-20
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 17:04:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LUKk-0004y1-Bu
	for ietf@asgard.ietf.org; Thu, 29 May 2003 16:49: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 QAA18910
	for <ietf@ietf.org>; Thu, 29 May 2003 16:49:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LUJ8-0002Kd-00
	for ietf@ietf.org; Thu, 29 May 2003 16:47:30 -0400
Received: from [64.70.31.5] (helo=www.darkuncle.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LUJ7-0002Ka-00
	for ietf@ietf.org; Thu, 29 May 2003 16:47:29 -0400
Received: from www.darkuncle.net (bonkbonk@localhost [127.0.0.1])
	by www.darkuncle.net (8.12.9/8.12.9) with ESMTP id h4TKmqWq048465;
	Thu, 29 May 2003 13:48:52 -0700 (PDT)
	(envelope-from sfrancis@darkuncle.net)
Received: (from sfrancis@localhost)
	by www.darkuncle.net (8.12.9/8.12.9/Submit) id h4TKmqLf048464;
	Thu, 29 May 2003 13:48:52 -0700 (PDT)
Date: Thu, 29 May 2003 13:48:52 -0700
From: Scott Francis <darkuncle@darkuncle.net>
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Re: spam
Message-ID: <20030529204852.GO99106@darkuncle.net>
References: <3ED28753.3070901@ehsco.com> <Pine.LNX.4.44.0305261802010.3699-100000@commander.av8.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="/jkxxxtAhYIHVDuh"
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0305261802010.3699-100000@commander.av8.net>
User-Agent: Mutt/1.3.25i
X-Operating-System: OpenBSD <http://www.openbsd.org>
X-PGP-Fingerprint: 7429 F75D D3F5 FA45 C6D7  D25B 59A0 7B8C 5537 F527
X-What-Happen: Somebody set up us the bomb.
Sender: owner-ietf@ietf.org
Precedence: bulk


--/jkxxxtAhYIHVDuh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, May 26, 2003 at 06:17:23PM -0400, dean@av8.com said:
[snip]
> > Spam on my measured-rate cellular-data PDA is real cost. Spam on my
> > measured-rate ISDN line (California) is real cost. Extra staffing to
> > counteract spam at my [isp|university|business] is real cost (setting
> > aside other costs that you seem willing to ignore). There are plenty of
> > examples to pick from.
>=20
> Don't get email on measured rate services, then. Or don't publish the
> email to measured rate services. Put your measured rate services on the
> do-not-send list. There are many options besides banning commercial email.

Want to lay odds on how many of the hardcore spammers (spamsites hosted on
Chinanet, etc.) will respect a do-not-send list? They already ignore various
state legislations against spam (I'm a California resident, for instance, a=
nd
get any number of spams to various accounts daily that ignore existing
legislation on this topic); why would they pay any attention to a do-not-se=
nd
list?

(I'm also fairly sure such a list will not allow wildcards, and for those of
us running a domain where one address receives *@domain.org, listing every
unique address we've created over the years would be tiresome, to say the
least. I'm sure if this is not the case, someone will correct me.)

> > These are abnormal expenses which go directly into maintaining the
> > usefulness of my property and which do not increase its value. The right
> > to commercial speech would not warrant these costs for any other venue,
> > and there is nothing sufficiently different and unique about this venue=
 to
> > warrant it here.
>=20
> These are not abnormal expenses. You have deal with abuse no matter what

so, because I have an abuse person to deal with legitimate abuse problems
(both ingress and egress), I should consider it part of the cost of doing
business to put up with whatever the spammers want to do to me?

I wonder if AOL considers the cost of dealing with 2 billion spams _daily_ =
an
"abnormal expense". Especially when comparing their costs for dealing with
spam from 2 years ago. Or 6 months ago.

> the form. You have to have an abuse person. Persons intent on performing
> abuse will abuse whatever is handy.

Only too true, but it doesn't mean we have to 1) make it easy for them, or =
2)
ignore it when they do.

> There are no costs to warrant.  Spam cannot cost you more than $1 or $2
> per month per user. It doesn't matter how many abuse administrators you
> have, or how big and expensive your servers are.  Email (including spam)
> is too cheap to meter. It is practically free, per person.  Sites that
> have 10 million users are going to have larger expenses than sites that
> have 10 users. That isn't a surprise, nor a compelling reason to ban spam.

Tell that to AOL. Or Hotmail. Or any other large provider for whom the vast
majority of their network traffic is unsolicited commecial email. Your
assertions simply do not hold water. I bet they consider the costs of deali=
ng
with that illegitimate traffic a fairly compelling reason to ban spam.

> Anyway, I think commercial speech including spam _could_ be regulated, but
> there so far is no justification for doing so. I don't think there is any

If you can make that statement after considering the cost (personnel,
bandwidth, and intangibles like degradation of the quality of Internet
experience the average consumer has) of spam traffic now, compared with the
cost just 18 months ago, I guess there is no chance you will ever see the
flaws in your reasoning.

> chance whatsoever that spam will ever be banned completely, and if it
> were, it would suffer the same fate as the Junk Fax law, which had much
> more signficant costs (consumption of paper at 10 cents per page) and

10 cents per page, but there was also no single organization handling 2
billion incoming junk faxes a day. Apples and oranges, Dean.
--=20
Scott Francis || darkuncle (at) darkuncle (dot) net
      illum oportet crescere me autem minui

--/jkxxxtAhYIHVDuh
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+1nI0WaB7jFU39ScRAkWyAJ0XpVh6cPt2K7AGiW1T9DEE293cHgCfdWUt
LmlNVhoJTmGr7YXz6AGRd9Q=
=YHLo
-----END PGP SIGNATURE-----

--/jkxxxtAhYIHVDuh--



From owner-ietf@ietf.org  Thu May 29 17:30:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20785
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 17:30:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LUjK-0006tC-3J
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 17:14:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LUS3-0005oF-PF
	for ietf@asgard.ietf.org; Thu, 29 May 2003 16:56:43 -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 QAA19279
	for <ietf@ietf.org>; Thu, 29 May 2003 16:56:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LUQR-0002R7-00
	for ietf@ietf.org; Thu, 29 May 2003 16:55:03 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LUQR-0002QX-00
	for ietf@ietf.org; Thu, 29 May 2003 16:55:03 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h4TKu29N020500;
	Thu, 29 May 2003 13:56:03 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AEP02303;
	Thu, 29 May 2003 13:56:02 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id NAA23501; Thu, 29 May 2003 13:56:01 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16086.29665.751319.81278@thomasm-u1.cisco.com>
Date: Thu, 29 May 2003 13:56:01 -0700 (PDT)
To: "Anthony Atkielski" <anthony@atkielski.com>
Cc: "IETF Discussion" <ietf@ietf.org>
Subject: Re: spam
In-Reply-To: <088701c3261f$4a7b6bb0$0a00000a@atkielski.com>
References: <200305291250.h4TCojKT015845@ginger.lcs.mit.edu>
	<088701c3261f$4a7b6bb0$0a00000a@atkielski.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Anthony Atkielski writes:
 > Noel writes:
 > 
 > > It *better* be solvable, otherwise when email
 > > becomes 99% spam, everyone will stop reading email.
 > 
 > I wouldn't worry about that.  When everyone stops reading e-mail, spam will
 > disappear again.  Remember, spammers only send out spam because people reply
 > to it.  If nobody replies, they'll stop.

You mean I might yet achieve salvation without my
procmail rosary beads? Will it be preceded by the
RFC 822 apocalypse?

		Mike



From owner-ietf@ietf.org  Thu May 29 17:33:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21102
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 17:33:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LUjK-0006u5-G0
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 17:14:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LUWX-0005rm-Dl
	for ietf@asgard.ietf.org; Thu, 29 May 2003 17:01:21 -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 RAA19631
	for <ietf@ietf.org>; Thu, 29 May 2003 17:01:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LUUv-0002WH-00
	for ietf@ietf.org; Thu, 29 May 2003 16:59:41 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LUUu-0002WC-00
	for ietf@ietf.org; Thu, 29 May 2003 16:59:40 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4TL1JKk039902
	for <ietf@ietf.org>; Thu, 29 May 2003 23:01:19 +0200 (CEST)
Message-ID: <08ef01c32625$73992e50$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <200305291250.h4TCojKT015845@ginger.lcs.mit.edu><088701c3261f$4a7b6bb0$0a00000a@atkielski.com> <16086.29665.751319.81278@thomasm-u1.cisco.com>
Subject: Re: spam
Date: Thu, 29 May 2003 23:01:18 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I simply mean that when the returns are low enough, spammers will stop.  If
spam produces so much noise that people stop using e-mail, that will stop
the spammers.

However, I think that for the vast majority of Internet users, spam is only
a minor nuisance, and they will probably continue to use e-mail with or
without spam.

----- Original Message -----
From: "Michael Thomas" <mat@cisco.com>
To: "Anthony Atkielski" <anthony@atkielski.com>
Cc: "IETF Discussion" <ietf@ietf.org>
Sent: Thursday, May 29, 2003 22:56
Subject: Re: spam


> Anthony Atkielski writes:
>  > Noel writes:
>  >
>  > > It *better* be solvable, otherwise when email
>  > > becomes 99% spam, everyone will stop reading email.
>  >
>  > I wouldn't worry about that.  When everyone stops reading e-mail, spam
will
>  > disappear again.  Remember, spammers only send out spam because people
reply
>  > to it.  If nobody replies, they'll stop.
>
> You mean I might yet achieve salvation without my
> procmail rosary beads? Will it be preceded by the
> RFC 822 apocalypse?
>
> Mike
>




From owner-ietf@ietf.org  Thu May 29 17:42:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21556
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 17:42:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LUjK-0006ub-Ue
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 17:14:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LUZ0-0005um-0l
	for ietf@asgard.ietf.org; Thu, 29 May 2003 17:03:54 -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 RAA19667
	for <ietf@ietf.org>; Thu, 29 May 2003 17:03:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LUXO-0002Wj-00
	for ietf@ietf.org; Thu, 29 May 2003 17:02:14 -0400
Received: from mail15.speakeasy.net ([216.254.0.215] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LUXN-0002Wg-00
	for ietf@ietf.org; Thu, 29 May 2003 17:02:13 -0400
Received: (qmail 2624 invoked from network); 29 May 2003 21:03:50 -0000
Received: from unknown (HELO 192.168.254.124) ([66.92.168.196])
          (envelope-sender <dja2003@hotpop.com>)
          by mail15.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <Valdis.Kletnieks@vt.edu>; 29 May 2003 21:03:50 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: Valdis.Kletnieks@vt.edu, Anthony Atkielski <anthony@atkielski.com>
Subject: Re: spam
Date: Thu, 29 May 2003 17:06:10 -0400
User-Agent: KMail/1.5
Cc: IETF Discussion <ietf@ietf.org>
References: <014d01c32555$250d1c90$56144104@eagleswings> <077f01c32599$ae33cc00$0a00000a@atkielski.com> <200305290513.h4T5DjaA004635@turing-police.cc.vt.edu>
In-Reply-To: <200305290513.h4T5DjaA004635@turing-police.cc.vt.edu>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305291706.10574.dja2003@hotpop.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Thursday 29 May 2003 01:13, Valdis.Kletnieks@vt.edu wrote:

 Va> On Thu, 29 May 2003 06:20:47 +0200, Anthony Atkielski
 Va> <anthony@atkielski.com>  said:
 ...
 Va> > Hash it and sign it with the public key of the recipient.
 Va> > That would work, because spammers would not have the
 Va> > public key, whereas legitimate senders would.
 Va>
 Va> Only if it's an *UNPUBLISHED* public key - at which point
 Va> it just degenerates into your "secret number" protocol,
 Va> with the same bootstrapping issues.

Correct, but still methinks Anthony is onto something.

Yes, a spammer could get hold of your public key.  However, this 
"tailoring" means that he's going to have to send the spam to each 
recipient individually, instead of using a huge Bcc list.  This won't 
get rid of spam entirely, but it could put somewhat of a damper on the 
flow.

The big question is, how many recipients are there (To + Cc + Bcc), for 
the average piece of outbound spam?  That is roughly the ratio by which 
such a scheme will make it costlier to spam.  (I'm purposesly ignoring 
the extra cost of the hashing and encryption.  These will probably make 
a small contribution, by comparison.)  Anybody got a large corpus of 
spam, COMPLETE WITH BCC LISTS, to analyze?

Then comes the followup question of whether that ratio is enough to be 
worth the trouble of further investigation along this path.  Keep in 
mind, they could always simply apply the usual Microsoft solution: throw 
more and faster hardware at it.  Note also that a lot of spam is already 
sent to single recipients per piece.  In those cases, the extra costs of 
hashing and encryption MIGHT make a SMALL dent, but I doubt it would be 
enough to be worth the hassle.

-- 
David J. Aronson, Unemployed Software Engineer near Washington DC
See http://destined.to/program/ for online resume, and other info




From owner-ietf@ietf.org  Thu May 29 17:46:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18985
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 16:53:48 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LU7K-0004PM-7M
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 16:35:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LTuq-00044N-GJ
	for ietf@asgard.ietf.org; Thu, 29 May 2003 16:22:24 -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 QAA18154
	for <ietf@ietf.org>; Thu, 29 May 2003 16:22:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LTtE-0002BL-00
	for ietf@ietf.org; Thu, 29 May 2003 16:20:44 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LTtD-0002BI-00
	for ietf@ietf.org; Thu, 29 May 2003 16:20:43 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4TKMMKk039571
	for <ietf@ietf.org>; Thu, 29 May 2003 22:22:22 +0200 (CEST)
Message-ID: <089f01c32620$029edb00$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.44.0305291332220.16521-100000@commander.av8.net>
Subject: Re: spam
Date: Thu, 29 May 2003 22:22:21 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dean writes:

> I expect that Type 1 spammers will comply. Some already are.

Of course they will.  The whole idea of Type 1 spammers is to provide a way
for you to contact them, anyway, so they have little incentive to hide.




From owner-ietf@ietf.org  Thu May 29 17:48:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21843
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 17:48:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LUwR-0007kr-2G
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 17:28:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LUcv-0006iC-57
	for ietf@asgard.ietf.org; Thu, 29 May 2003 17:07: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 RAA20002
	for <ietf@ietf.org>; Thu, 29 May 2003 17:07:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LUbJ-0002ci-00
	for ietf@ietf.org; Thu, 29 May 2003 17:06:17 -0400
Received: from anchor-post-39.mail.demon.net ([194.217.242.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LUbI-0002cf-00
	for ietf@ietf.org; Thu, 29 May 2003 17:06:16 -0400
Received: from soaring.demon.co.uk ([80.177.120.110])
	by anchor-post-39.mail.demon.net with esmtp (Exim 3.36 #2)
	id 19LUcs-0007Rq-0U; Thu, 29 May 2003 22:07:55 +0100
Message-ID: <ZzjfytD1Zn1+Ew5H@soaring.demon.co.uk>
Date: Thu, 29 May 2003 22:07:01 +0100
To: ietf@ietf.org
Cc: Doug Sauder <dws@hunnysoft.com>
From: Andrew Shore <ietf@soaring.demon.co.uk>
Reply-To: Andrew Shore <ietf@soaring.demon.co.uk>
Subject: Re: spam
References: <FA2605DA-91E4-11D7-9B54-00039388672E@muada.com>
 <200305291544.h4TFi8FR006326@calcite.rhyolite.com>
In-Reply-To: <200305291544.h4TFi8FR006326@calcite.rhyolite.com>
MIME-Version: 1.0
Content-Type: text/plain;charset=us-ascii;format=flowed
User-Agent: Turnpike/6.02-S (<aCAGT1CKFCi8lsT3mwPhfD$m6j>)
Sender: owner-ietf@ietf.org
Precedence: bulk

Vernon Schryver wrote:

>  - becoming famous for having stopped spam, or at least getting into
>     the RFC index.

     And on that subject, would Doug be willing to write up his 
"subaddresses" proposal as a draft? Or would that be counterproductive 
to its eventual acceptance? At least three of us have proposed variants 
on this theme, and while it will not put an end to spam overnight, it 
will be a useful beginning. I realise there may be patent issues... ^^


Andrew.
-- 
Andrew Shore.



From owner-ietf@ietf.org  Thu May 29 18:07:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22847
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 18:07:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LVD3-00014c-U0
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 17:45:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LUv4-0007iK-AN
	for ietf@asgard.ietf.org; Thu, 29 May 2003 17:26:42 -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 RAA20646
	for <ietf@ietf.org>; Thu, 29 May 2003 17:26:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LUtS-0002mC-00
	for ietf@ietf.org; Thu, 29 May 2003 17:25:02 -0400
Received: from mail.cdt.org ([206.112.85.61])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LUtR-0002m0-00
	for ietf@ietf.org; Thu, 29 May 2003 17:25:01 -0400
Received: from [10.0.1.20] (66.safeclick.net [63.119.245.66])
	by mail.cdt.org (Postfix) with ESMTP id 3756049002C
	for <ietf@ietf.org>; Thu, 29 May 2003 17:10:15 -0400 (EDT)
Mime-Version: 1.0
X-Sender: john@mail.cdt.org
Message-Id: <a05200f05bafc2932beeb@[10.0.1.20]>
In-Reply-To: <088c01c3261f$9dcc00e0$0a00000a@atkielski.com>
References: <017601c32566$cb6fcea0$56144104@eagleswings>
 <07a201c3259a$f8fbd1f0$0a00000a@atkielski.com>
 <a05200f00bafbc9fdb2f1@[10.0.1.20]>
 <088c01c3261f$9dcc00e0$0a00000a@atkielski.com>
Date: Thu, 29 May 2003 17:26:07 -0400
To: "IETF Discussion" <ietf@ietf.org>
From: John Morris <jmorris@cdt.org>
Subject: Re: The utilitiy of IP is at stake here
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 10:19 PM +0200 5/29/03, Anthony Atkielski wrote:
>John writes:
>
>>  In the US, ISPs are not, and never have been
>>  viewed, as common carriers.
>
>I recall a case involving CompuServe in which it was treated at least
>partially as a common carrier, not responsible for the content of its
>network.

The Compuserve case went the general way you suggest, and the Prodigy 
case went the other way.  Both cases predate the passage of 47 U.S.C. 
Section 230, which was a part of the Communicaitons Decency Act, 
which in turn was a part of the Telecommuncations Act of 1996. 
Section 230 was enacted specifically to reverse the holding of the 
Stratton Oakmont v. Prodigy  decision, which did impose liability on 
Prodigy.

>  >    (1) Treatment of publisher or speaker
>>         No provider or user of an interactive
>>         computer service [read, an ISP] shall be
>>         treated as the publisher or speaker of
>>         any information provided
>>         by another information content provider.
>
>How is this reconciled with the DMCA?

The DMCA does not in general make ISPs liable for copyright 
infringement by their customers, but instead puts certain takedown 
obligations on ISPs.   So there is no conflict.

John



From owner-ietf@ietf.org  Thu May 29 18:07:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22845
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 18:07:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LVD3-00013p-E8
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 17:45:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LUs9-0007ch-3u
	for ietf@asgard.ietf.org; Thu, 29 May 2003 17:23:41 -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 RAA20543
	for <ietf@ietf.org>; Thu, 29 May 2003 17:23:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LUqX-0002lP-00
	for ietf@ietf.org; Thu, 29 May 2003 17:22:01 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LUqW-0002lF-00
	for ietf@ietf.org; Thu, 29 May 2003 17:22:00 -0400
Received: from edison.cisco.com (edison.cisco.com [171.70.144.164])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h4TLMxFW017417;
	Thu, 29 May 2003 14:22:59 -0700 (PDT)
Received: from cisco.com (sjc-vpn4-452.cisco.com [10.21.81.196]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id OAA15251; Thu, 29 May 2003 14:22:58 -0700 (PDT)
Message-ID: <3ED67A32.4020007@cisco.com>
Date: Thu, 29 May 2003 14:22:58 -0700
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dave Crocker <dcrocker@brandenburg.com>
CC: Tony Hain <alh-ietf@tndh.net>, "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
References: <00e901c3261b$a3dbcf50$56144104@eagleswings> <127103972754.20030529132930@brandenburg.com>
In-Reply-To: <127103972754.20030529132930@brandenburg.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dave,

> Please indicate some historical basis for moving an installed base of
> users on this kind of scale and for this kind of reason.

History is replete with examples.  From the Internet Worm to Code Red, 
consumers do install software when they perceive either a threat or a 
benefit.  Getting rid of spam is a HUGE benefit.  Heck.  What I've found 
so amusing is that people seem to upgrade their Microsoft systems just 
'cause, with no perceived benefit, but merely protecting from Bit Rot.

Eliot





From owner-ietf@ietf.org  Thu May 29 18:19:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24113
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 18:19:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LVTm-0003wW-Bk
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 18:02:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LVAt-0000la-S8
	for ietf@asgard.ietf.org; Thu, 29 May 2003 17:43:03 -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 RAA21582
	for <ietf@ietf.org>; Thu, 29 May 2003 17:43:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LV9H-0002zU-00
	for ietf@ietf.org; Thu, 29 May 2003 17:41:23 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LV9G-0002zQ-00
	for ietf@ietf.org; Thu, 29 May 2003 17:41:23 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h4TLi0xS021326;
	Thu, 29 May 2003 23:44:00 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Thu, 29 May 2003 23:42:58 +0200
Subject: Re: The utilitiy of IP is at stake here
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "'IETF Discussion'" <ietf@ietf.org>
To: <alh-ietf@tndh.net>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <00e401c32619$49512b40$56144104@eagleswings>
Message-Id: <83CE7BB8-921E-11D7-9B54-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On donderdag, mei 29, 2003, at 21:34 Europe/Amsterdam, Tony Hain wrote:

> The fundamental legal issue we need to deal with is the ability to
> absolutely identify the originator of the mail. Is that precluded by 
> any
> existing privacy laws? If not, identity would provide the means to
> pursue financial recourse for wasted time and resources. If so, we have
> a non-technical issue that may prevent any solution.

Too bad the bad ideas get much more air time than the good ones. 
Yesterday some really good points were brought up, today we're mostly 
rehashing the bad stuff.

About the law: current laws are unable to keep spam in check. Is this a 
problem with the law? I don't think so. A good percentage of all spam 
(but certainly not all of it) breaks existing laws. It seems unlikely 
that additional laws will make people who already operate outside the 
law change their behavior.

Another preposterous idea: charging money for sending email. Economics 
dictates that this will increase the overall cost of emailing by many 
orders of magnitude and there is no reasonable upgrade path from the 
current situation to the new one.

Both points are moot anyway as they fall outside the scope of the 
IETF's activities. The real question is whether the current protocols 
exhibit flaws that make the spam problem worse than it would be without 
those flaws; and whether improved protocols can be implemented and 
deployed at reasonable levels of effectiveness and efficiency.

It seems the answer to this was "no" five or six years ago. In the mean 
time, many things have changed. We now have more advanced techniques 
and more processing power at our disposal. Also, spamming in general 
has become much worse and many more children are online now, who are 
subjected to spam that isn't always "child friendly" to say the least. 
Maybe the answer is still "no" but the time is right to at least 
revisit the question.




From owner-ietf@ietf.org  Thu May 29 18:38:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24743
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 18:38:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LVgy-0000Ne-UE
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 18:16:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LVDW-00014v-E3
	for ietf@asgard.ietf.org; Thu, 29 May 2003 17:45:46 -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 RAA21770
	for <ietf@ietf.org>; Thu, 29 May 2003 17:45:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LVBu-00033E-00
	for ietf@ietf.org; Thu, 29 May 2003 17:44:06 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LVBt-00033B-00
	for ietf@ietf.org; Thu, 29 May 2003 17:44:05 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 208408; Thu, 29 May 2003 16:45:08 -0500
Message-ID: <3ED67F80.3040108@ehsco.com>
Date: Thu, 29 May 2003 16:45:36 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: pdeutsch@earthlink.net
CC: alh-ietf@tndh.net, "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
References: <00e901c3261b$a3dbcf50$56144104@eagleswings> <3ED67014.9E8161B7@earthlink.net>
In-Reply-To: <3ED67014.9E8161B7@earthlink.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/29/2003 3:39 PM Peter Deutsch wrote:

> I personally want a next generation system that would *increase* my
> privacy, not attempt to make a virtue out of *removing* the few shreds
> of annonymity I have left. I would specifically refuse to use such a
> system. And yes, I also want it to make unsolicited, bulk email harder
> to send to me, but not at the cost of my privacy.

Everybody wants to see caller-ID but nobody wants to send it.

Actually, the use of an identification system doesn't necessarily have to
go directly against privacy or anonymity. It leaves the door open for some
kinds of abuses in that area, but those aren't a whole lot worse.

A ~certificate would validate the identity you are using for that piece of
email. That identity doesn't have to be your name or anything else that
identifies you personally. Hell, use 20 certificates, call yourself Batman
in one group and Wonder Woman in the other, nobody will care. As long as
they all verify -- and as long as I can track you down with a court order
that exposes what I need to know when I have a demonstrable reason to know
it -- nobody should care about the identitiers you choose to use.

The real risk here is that the delegator will know who you really are and
might tell somebody. I don't see much difference between that and the risk
we already have from upstreams being able to sniff and delegate, though.

Besides, if everybody feels that strongly about it, a mail system like the
one I laid out doesn't *require* user identification, only host and domain
identification. If folks want the user part to be optional, that's fine
with me.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Thu May 29 18:43:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25150
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 18:43:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LVh4-0000Rw-Ue
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 18:16:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LVMw-0001qV-N6
	for ietf@asgard.ietf.org; Thu, 29 May 2003 17:55:30 -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 RAA22098
	for <ietf@ietf.org>; Thu, 29 May 2003 17:55:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LVLK-00038e-00
	for ietf@ietf.org; Thu, 29 May 2003 17:53:50 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LVLJ-00038b-00
	for ietf@ietf.org; Thu, 29 May 2003 17:53:50 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S298AC> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 29 May 2003 14:55:27 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'IETF'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Thu, 29 May 2003 14:55:20 -0700
Message-ID: <00f401c3262c$ff9b9a30$56144104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <127103972754.20030529132930@brandenburg.com>
Importance: Normal
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA25150

Dave Crocker wrote:
> Please indicate some historical basis for moving an installed 
> base of users on this kind of scale and for this kind of reason.

WWW browser deployment shows that given appropriate motivation, users
will aggressively take advantage of a new app. Yes I consider this to be
a new app, even though it is replacing an existing capability. Rather
than force people to move or upgrade, give them a new tool and explain
the value. They will move as soon as they believe it is less painful
than staying where they are. Given the growing level of complaint, and
the fact that it will be at least 2 years before anything is ready to
deploy, just about anything will be an easy sell.

> 
> 
> TH>  If the courts routinely granted judgments to
> TH> individuals of 100 $/euro for every received unsolicited message, 
> TH> people
> 
> a transition plan for 100 million users that relies on an 
> "if" concerning entirely new behaviors for a large number of 
> independent judicial systems around the world is a rather 
> fragile dependency, to say the least.
> 
> (and, yes, I realize that that was just an example.  so, 
> please, go ahead and provide a scenario that is not equally 
> fragile.  i can't.)
> 

I would argue this is not entirely new behavior, just that one widely
publicized instance needs to establish precedent that receiving
unsolicited email constitutes an abuse of personal resources and
establish the value of that abuse. Since I think we are talking
small-claims here ($100/day per spam source), it would be most efficient
for the courts to have a procedure where the claimant provided the
abusing email with tracability to the origin, then an automatic judgment
could be issued (yes that is new, but the newness is about efficiency,
not basic process). 

Defining an alternative mechanism is the IETF's job. As long as we
explicitly refuse to allow interoperability, we don't need to worry
about a transition. The mail service providers have the means to inform
their customers about the opportunity to use a new app. The larger
providers (AOL, MSN, Yahoo, ...) can drive media attention and might
even help with any legal efforts to make the case that the new app will
have anti-spam characteristics. In any case, transition is not a problem
when we simply let the spam laden legacy die off as people start
refusing to use the old apps.

> 
> TH> would jump at the chance to run the new mail tool, and spam as we 
> TH> know it would loose its economic viability. Making that 
> work means 
> TH> absolute traceability of the message origin.
> >> For this effort to be effective, I think it will have to 
> be done in a 
> >> way that is at odds with the traditional IETF thinking:
> >> 
> >> 1) Compatibility with SMTP is not desirable
> 
> why?

See above about this being a new app. Requiring integration and
compatibility will only create unnecessary complexity, and won't show
any quantitative value to the end user. Also, as Alain pointed out in
the mail I was responding to, interoperability simply creates a forward
path for the SMTP based spam. Just make them parallel systems and move
on.

> 
> 
> >> 2) Some form of privacy is not desirable
> >> 3) To much scalability is not desirable
> 
> scalability is not desirable?  wow.
> 
> please explain.

You cut off my comment that scalability is desirable everywhere except
at the originator. The point is to raise the cost at the origin to bias
the economics against random spamming. Something like requiring
recipient based public key cryptography substantially raises the
originator cost for mass mailings. 

Mail list servers would be a problem if we only use public key, so
another part of the new system could be establishing a symmetric key as
part of subscribing to a mail list. Clearly we have a number of
technologies available, we just need to define the characteristics of
the desired system and start applying technologies to build a new app. 

Tony





From owner-ietf@ietf.org  Thu May 29 18:43:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25153
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 18:43:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LVh4-0000Qy-F5
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 18:16:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LVJb-0001me-2I
	for ietf@asgard.ietf.org; Thu, 29 May 2003 17:52:03 -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 RAA21987
	for <ietf@ietf.org>; Thu, 29 May 2003 17:52:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LVHz-00037D-00
	for ietf@ietf.org; Thu, 29 May 2003 17:50:23 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LVHy-00037A-00
	for ietf@ietf.org; Thu, 29 May 2003 17:50:22 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h4TLqqxS021360;
	Thu, 29 May 2003 23:52:53 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Thu, 29 May 2003 23:51:51 +0200
Subject: Re: spam
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: IETF Discussion <ietf@ietf.org>
To: Dave Aronson <dja2003@hotpop.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <200305291706.10574.dja2003@hotpop.com>
Message-Id: <C17A52AE-921F-11D7-9B54-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On donderdag, mei 29, 2003, at 23:06 Europe/Amsterdam, Dave Aronson 
wrote:

[Having to do crypto for each outgoing spam]

> Keep in
> mind, they could always simply apply the usual Microsoft solution: 
> throw
> more and faster hardware at it.  Note also that a lot of spam is 
> already
> sent to single recipients per piece.  In those cases, the extra costs 
> of
> hashing and encryption MIGHT make a SMALL dent, but I doubt it would be
> enough to be worth the hassle.

I think the people selling crypto accelerators will be very happy about 
this...

However, creating new publick/private key pairs is an incredibly 
expensive operation, and one that a legitimate email wouldn't have to 
do very often, but a spammer would if we just keep blacklisting their 
keys.




From owner-ietf@ietf.org  Thu May 29 18:48:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25525
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 18:48:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LVhr-0000p0-Ai
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 18:17:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LVaN-0006pE-K7
	for ietf@asgard.ietf.org; Thu, 29 May 2003 18:09:23 -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 SAA23246
	for <ietf@ietf.org>; Thu, 29 May 2003 18:09:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LVYl-0003Ip-00
	for ietf@ietf.org; Thu, 29 May 2003 18:07:43 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LVYk-0003Ik-00
	for ietf@ietf.org; Thu, 29 May 2003 18:07:42 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S298B4> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 29 May 2003 15:09:20 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Thu, 29 May 2003 15:09:21 -0700
Message-ID: <00f901c3262e$f4f2cd90$56144104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <83CE7BB8-921E-11D7-9B54-00039388672E@muada.com>
Importance: Normal
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA25525

Iljitsch van Beijnum wrote:
> On donderdag, mei 29, 2003, at 21:34 Europe/Amsterdam, Tony 
> Hain wrote:
> 
> > The fundamental legal issue we need to deal with is the ability to 
> > absolutely identify the originator of the mail. Is that 
> precluded by 
> > any existing privacy laws? If not, identity would provide 
> the means to
> > pursue financial recourse for wasted time and resources. If 
> so, we have
> > a non-technical issue that may prevent any solution.
> 
> Too bad the bad ideas get much more air time than the good ones. 
> Yesterday some really good points were brought up, today we're mostly 
> rehashing the bad stuff.
> 
> About the law: current laws are unable to keep spam in check. 

I was not asking about spam law. I was trying to be specific about any
privacy laws that would prevent identification of the originator of a
message. As long as there is a legal way to undeniably trace the message
origin, there is a chance we can build a technical approach to bulk
message handling system that will end random spam. 

> ...
> The real question is whether the current protocols 
> exhibit flaws that make the spam problem worse than it would 
> be without 
> those flaws; and whether improved protocols can be implemented and 
> deployed at reasonable levels of effectiveness and efficiency.

I would argue yes, in that it is impossible to nail down the originator
with the current system. 

> 
> It seems the answer to this was "no" five or six years ago. 
> In the mean 
> time, many things have changed. We now have more advanced techniques 
> and more processing power at our disposal. Also, spamming in general 
> has become much worse and many more children are online now, who are 
> subjected to spam that isn't always "child friendly" to say 
> the least. 
> Maybe the answer is still "no" but the time is right to at least 
> revisit the question.
>

I agree.

Tony

 




From owner-ietf@ietf.org  Thu May 29 19:02:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26066
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 19:02:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LWDN-0003Lr-SW
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 18:49:41 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LVmM-0001BQ-9s
	for ietf@asgard.ietf.org; Thu, 29 May 2003 18:21:46 -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 SAA24245
	for <ietf@ietf.org>; Thu, 29 May 2003 18:21:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LVkk-0003PL-00
	for ietf@ietf.org; Thu, 29 May 2003 18:20:06 -0400
Received: from iserver.sj.symbol.com ([63.145.233.51])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LVkj-0003PI-00
	for ietf@ietf.org; Thu, 29 May 2003 18:20:05 -0400
Received: from gwianameserver.sj.symbol.com (symsjdmz.sj.symbol.com [63.145.233.50])
	by iserver.sj.symbol.com (8.12.8/8.12.8) with ESMTP id h4TMICFZ000396
	for <ietf@ietf.org>; Thu, 29 May 2003 15:18:12 -0700 (PDT)
Received: from SJ-DOM-MTA by gwianameserver.sj.symbol.com
	with Novell_GroupWise; Thu, 29 May 2003 14:36:54 -0700
Message-Id: <sed61b06.038@gwianameserver.sj.symbol.com>
X-Mailer: Novell GroupWise Internet Agent 6.0.2
Date: Thu, 29 May 2003 14:36:51 -0700
From: "Clint Chaplin" <cchaplin@sj.symbol.com>
To: <anthony@atkielski.com>, <ietf@ietf.org>
Subject: Re: spam
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I've been lurking all this time, and was about to give up completely on
this thread, but then I got sucked into the reality distortion field,
drank the kool-aid, and, well....

One problem with attaching the "secret" string to an email address is
how that is done at the sender's side.  I can see email clients
automating the process, which is fine, until a virus comes along and
starts popping off random emails.

Plus, how would CC: and vast To: lists hide the secret string?

Clint (JOATMON) Chaplin

>>> "Anthony Atkielski" <anthony@atkielski.com> 5/28/03 21:20:47 >>>
Tony writes:

> Which is precisely the goal. It is not so extreme
> as to make routine mail unusable, but extreme enough
> to make random bulk mail not worth the cost.

Point taken, although I think conventional encryption would probably a
better choice for this purpose.

I think, though, that a more effective method would be to find
something
that one can require on each message and that is not trivially easy for
a
computer to do automatically.

For example, the various admininstrations passing through the White
House
have long had a policy of establishing a "secret number" or similar
text
that must be placed on any incoming letter that is to be forwarded
directly
to the President or his family with minimal screening.  The President
and
family then give this number to a select few people.  Any
correspondence
without the number goes through all the usual screening.

This works because the number is an out-of-band datum that the average
sender is not likely to have.  It is communicated from human being to
human
being, and isn't to be found anywhere in public.  So it cannot be
automatically added by a machine, nor can unauthorized people add it.

A simple e-mail implementation of this would be to place a random
string in
the subject line of a message intended for a specific recipient that
serves
the same purpose as this "secret number."  The string would be
different for
each recipient, and the only way to obtain it would be through some
out-of-band process (such as contacting the recipient by phone, or
something).  Since there would be no record of this anywhere that
spammers
could harvest, it would be impossible for spammers to include these
numbers
on outgoing mail.  Very simple, and very effective.  It would, however,
be
nice to have e-mail clients that automated this, by allow for a secret
number field in address books that would make it possible to insert
them
automatically on outgoing mail (most clients already provide a way to
filter
for such numbers on incoming mail).

Digital signatures and similar authentication would work but are
overkill.
All you need is some bit of information that spammers cannot harvest,
and
the above random string fits that purpose.  Spammers might pick up
your
address on a newsgroup or Web site, but they'd have no way of
discovering
your secret number.

> That simply provides message integrity ...

Hash it and sign it with the public key of the recipient.  That would
work,
because spammers would not have the public key, whereas legitimate
senders
would.

However, I think the secret-number concept described above would be
much
similar and would be just as effective.



________________________________________________________________________
This email has been scanned for computer viruses.



From owner-ietf@ietf.org  Thu May 29 19:04:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26238
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 19:04:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LWDO-0003N2-9E
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 18:49:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LVvK-0001LI-J5
	for ietf@asgard.ietf.org; Thu, 29 May 2003 18:31:02 -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 SAA24482
	for <ietf@ietf.org>; Thu, 29 May 2003 18:30:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LVti-0003SX-00
	for ietf@ietf.org; Thu, 29 May 2003 18:29:22 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LVth-0003ST-00
	for ietf@ietf.org; Thu, 29 May 2003 18:29:21 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.9/8.12.9) id h4TMUwZi026406
	for ietf@ietf.org env-from <vjs>;
	Thu, 29 May 2003 16:30:59 -0600 (MDT)
Date: Thu, 29 May 2003 16:30:59 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200305292230.h4TMUwZi026406@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: The utilitiy of IP is at stake here
References:  <3ED67A32.4020007@cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Eliot Lear <lear@cisco.com>

> > Please indicate some historical basis for moving an installed base of
> > users on this kind of scale and for this kind of reason.
>
> History is replete with examples.  From the Internet Worm 

What?  The Morris Worm resulted in a significant marketshare decline
for sendmail?  That's strange, since my recollections are that sendmail
became more instead of less popular, in part because SMTP swamped
other protocols.

>                                                           to Code Red, 
> consumers do install software when they perceive either a threat or a 
> benefit.

Do you really intend to say what those words mean in context, that
Microsoft products were replaced wholesale by other software.


>           Getting rid of spam is a HUGE benefit.  Heck.  What I've found 
> so amusing is that people seem to upgrade their Microsoft systems just 
> 'cause, with no perceived benefit, but merely protecting from Bit Rot.

Installing patches or updates that do not significantly change the
form, fit or function of a system is entirely different from pitching
SMTP and switching to something else with major differences not only
in form, fit, and function but fundamental assumptions.

Spam is an implicit problem in any mail protocol that lets you receive
mail from strangers.  If a message is from a stranger, how do you know
the stranger isn't sending copies to 30,000,000 of your intimate
friends?  Any protocol that keeps a stranger and so possible spamemr
from sending you a message will be a radical change far larger than
the change from IPv4 to IPv6, not to mention turning off the debug
switch in sendmail or pasting yet another a security bandaid on IIS.
For example, Cisco will stop receiving spam as well as inquiries from
prospective customers, at least not as freely and with semi-anomity
as today.  This mailing list will stop receiving new subscriptions by
the old mechanism of sending a "subscribe" mail message.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Thu May 29 19:05:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26377
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 19:05:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LWDO-0003NK-LQ
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 18:49:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LVvp-0001LN-DF
	for ietf@asgard.ietf.org; Thu, 29 May 2003 18:31:33 -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 SAA24515
	for <ietf@ietf.org>; Thu, 29 May 2003 18:31:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LVuD-0003Sn-00
	for ietf@ietf.org; Thu, 29 May 2003 18:29:53 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LVuC-0003SU-00
	for ietf@ietf.org; Thu, 29 May 2003 18:29:52 -0400
Received: from mira-sjc5-a.cisco.com (IDENT:mirapoint@mira-sjc5-a.cisco.com [171.71.163.34])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h4TMUv9x026479
	for <ietf@ietf.org>; Thu, 29 May 2003 15:30:58 -0700 (PDT)
Received: from cisco.com (sjc-vpn1-48.cisco.com [10.21.96.48])
	by mira-sjc5-a.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with SMTP id AGO97249;
	Thu, 29 May 2003 15:23:04 -0700 (PDT)
Received: by cisco.com (sSMTP sendmail emulation); Thu, 29 May 2003 18:30:41 -0400
Date: Thu, 29 May 2003 18:30:41 -0400
From: Scott W Brim <swb@employees.org>
To: "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
Message-ID: <20030529223041.GO2012@sbrim-w2k>
Mail-Followup-To: Scott W Brim <swb@employees.org>, 'IETF' <ietf@ietf.org>
References: <00e901c3261b$a3dbcf50$56144104@eagleswings> <127103972754.20030529132930@brandenburg.com> <3ED67A32.4020007@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3ED67A32.4020007@cisco.com>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

> Please indicate some historical basis for moving an installed base of
> users on this kind of scale and for this kind of reason.

Times have changed.  End users aren't the problem anymore.  We have
easy, if not automatic, updating for every major user environment.  The
critical point is the SMTP servers.  I believe the great majority of
them understand the spam pain, so they would be motivated to change.
You throttle SMTP relative to the enhanced protocol to motivate the
remaining good guys to convert, and as time goes on and only the bad
guys are left, you throttle it even more.

.swb



From owner-ietf@ietf.org  Thu May 29 19:13:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26697
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 19:13:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LWDP-0003Nf-19
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 18:49:43 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LVwb-0001Lk-IZ
	for ietf@asgard.ietf.org; Thu, 29 May 2003 18:32:21 -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 SAA24537
	for <ietf@ietf.org>; Thu, 29 May 2003 18:32:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LVuz-0003Su-00
	for ietf@ietf.org; Thu, 29 May 2003 18:30:41 -0400
Received: from carwash.centive.com ([65.220.90.249] helo=carwash.centivinc.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19LVuy-0003Sq-00
	for ietf@ietf.org; Thu, 29 May 2003 18:30:40 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003052918384600264
 for <ietf@ietf.org>; Thu, 29 May 2003 18:38:46 -0400
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 29 May 2003 18:29:26 -0400
Message-ID: <3ED689C6.30100@centive.com>
Date: Thu, 29 May 2003 18:29:26 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
References: <00e901c3261b$a3dbcf50$56144104@eagleswings>
In-Reply-To: <00e901c3261b$a3dbcf50$56144104@eagleswings>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 May 2003 22:29:26.0527 (UTC) FILETIME=[C31DD0F0:01C32631]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony Hain wrote:

>it wouldn't take much to convince people that moving to a new
>mail system would either reduce spam, or had adequate mechanisms for
>financial recourse.
>
I think you mean that, if people believed the new system would reduce 
spam, it wouldn't take much to convince them.  It *would* take a lot to 
convince them that it would reduce spam; people with a normal, healthy 
cynicism gland (and without the expertise to analyze the new protocols) 
would assume that it was just a marketing ploy.

-- 
/=============================================================\
|John Stracke      |jstracke@centive.com                      |
|Principal Engineer|http://www.centive.com                    |
|Centive           |My opinions are my own.                   |
|=============================================================|
|*BOOM* "Thank you, Beaker. Now we know that is definitely too|
|much gunpowder." -- Dr. Bunsen Honeydew                      |
\=============================================================/





From owner-ietf@ietf.org  Thu May 29 19:26:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24744
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 18:38:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LVh3-0000P2-PD
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 18:16:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LVFF-0001M5-Rk
	for ietf@asgard.ietf.org; Thu, 29 May 2003 17:47:33 -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 RAA21823
	for <ietf@ietf.org>; Thu, 29 May 2003 17:47:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LVDd-00033o-00
	for ietf@ietf.org; Thu, 29 May 2003 17:45:53 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LVDd-00033d-00
	for ietf@ietf.org; Thu, 29 May 2003 17:45:53 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id RAA32295;
	Thu, 29 May 2003 17:43:54 -0400
Date: Thu, 29 May 2003 17:45:00 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Scott Francis <darkuncle@darkuncle.net>
cc: ietf@ietf.org
Subject: Re: spam
In-Reply-To: <20030529204852.GO99106@darkuncle.net>
Message-ID: <Pine.LNX.4.44.0305291742250.8489-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Last time I refuted you, I got hit by 2400 sites trying to abuse our
relays for 10 days.  Sorry. Not this time.

You're too late for this discussion anyway.  Your points were already made
by others. There is no point to rehashing them with you.

		--Dean

On Thu, 29 May 2003, Scott Francis wrote:

> On Mon, May 26, 2003 at 06:17:23PM -0400, dean@av8.com said:
> [snip]
> > > Spam on my measured-rate cellular-data PDA is real cost. Spam on my
> > > measured-rate ISDN line (California) is real cost. Extra staffing to
> > > counteract spam at my [isp|university|business] is real cost (setting
> > > aside other costs that you seem willing to ignore). There are plenty of
> > > examples to pick from.
> >
> > Don't get email on measured rate services, then. Or don't publish the
> > email to measured rate services. Put your measured rate services on the
> > do-not-send list. There are many options besides banning commercial email.
>
> Want to lay odds on how many of the hardcore spammers (spamsites hosted on
> Chinanet, etc.) will respect a do-not-send list? They already ignore various
> state legislations against spam (I'm a California resident, for instance, and
> get any number of spams to various accounts daily that ignore existing
> legislation on this topic); why would they pay any attention to a do-not-send
> list?
>
> (I'm also fairly sure such a list will not allow wildcards, and for those of
> us running a domain where one address receives *@domain.org, listing every
> unique address we've created over the years would be tiresome, to say the
> least. I'm sure if this is not the case, someone will correct me.)
>
> > > These are abnormal expenses which go directly into maintaining the
> > > usefulness of my property and which do not increase its value. The right
> > > to commercial speech would not warrant these costs for any other venue,
> > > and there is nothing sufficiently different and unique about this venue to
> > > warrant it here.
> >
> > These are not abnormal expenses. You have deal with abuse no matter what
>
> so, because I have an abuse person to deal with legitimate abuse problems
> (both ingress and egress), I should consider it part of the cost of doing
> business to put up with whatever the spammers want to do to me?
>
> I wonder if AOL considers the cost of dealing with 2 billion spams _daily_ an
> "abnormal expense". Especially when comparing their costs for dealing with
> spam from 2 years ago. Or 6 months ago.
>
> > the form. You have to have an abuse person. Persons intent on performing
> > abuse will abuse whatever is handy.
>
> Only too true, but it doesn't mean we have to 1) make it easy for them, or 2)
> ignore it when they do.
>
> > There are no costs to warrant.  Spam cannot cost you more than $1 or $2
> > per month per user. It doesn't matter how many abuse administrators you
> > have, or how big and expensive your servers are.  Email (including spam)
> > is too cheap to meter. It is practically free, per person.  Sites that
> > have 10 million users are going to have larger expenses than sites that
> > have 10 users. That isn't a surprise, nor a compelling reason to ban spam.
>
> Tell that to AOL. Or Hotmail. Or any other large provider for whom the vast
> majority of their network traffic is unsolicited commecial email. Your
> assertions simply do not hold water. I bet they consider the costs of dealing
> with that illegitimate traffic a fairly compelling reason to ban spam.
>
> > Anyway, I think commercial speech including spam _could_ be regulated, but
> > there so far is no justification for doing so. I don't think there is any
>
> If you can make that statement after considering the cost (personnel,
> bandwidth, and intangibles like degradation of the quality of Internet
> experience the average consumer has) of spam traffic now, compared with the
> cost just 18 months ago, I guess there is no chance you will ever see the
> flaws in your reasoning.
>
> > chance whatsoever that spam will ever be banned completely, and if it
> > were, it would suffer the same fate as the Junk Fax law, which had much
> > more signficant costs (consumption of paper at 10 cents per page) and
>
> 10 cents per page, but there was also no single organization handling 2
> billion incoming junk faxes a day. Apples and oranges, Dean.
> --
> Scott Francis || darkuncle (at) darkuncle (dot) net
>       illum oportet crescere me autem minui
>




From owner-ietf@ietf.org  Thu May 29 19:28:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27124
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 19:28:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LWLq-0003hP-Si
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 18:58:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LWCA-0002xy-KU
	for ietf@asgard.ietf.org; Thu, 29 May 2003 18:48:26 -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 SAA25515
	for <ietf@ietf.org>; Thu, 29 May 2003 18:48:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LWAY-0003ig-00
	for ietf@ietf.org; Thu, 29 May 2003 18:46:46 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LWAX-0003id-00
	for ietf@ietf.org; Thu, 29 May 2003 18:46:45 -0400
Received: from [63.202.92.152] (adsl-63-202-92-152.dsl.snfc21.pacbell.net [63.202.92.152])
	(authenticated bits=0)
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h4TMmLAG062517
	for <ietf@ietf.org>; Thu, 29 May 2003 15:48:21 -0700 (PDT)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05210672bafc3d9bca93@[63.202.92.152]>
In-Reply-To: <3ED67A32.4020007@cisco.com>
References: <00e901c3261b$a3dbcf50$56144104@eagleswings>
 <127103972754.20030529132930@brandenburg.com> <3ED67A32.4020007@cisco.com>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Thu, 29 May 2003 15:47:40 -0700
To: ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: The utilitiy of IP is at stake here
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 2:22 PM -0700 5/29/03, Eliot Lear wrote:
>>Please indicate some historical basis for moving an installed base of
>>users on this kind of scale and for this kind of reason.
>
>History is replete with examples.  From the Internet Worm to Code 
>Red, consumers do install software when they perceive either a 
>threat or a benefit.

Tony's proposal is not for new software: it is for software that 
*replaces* what they have now. Further, it is not a one-to-one 
replacement. It requires new administrative actions by the sysadmin 
and by the user to validate who they want to get mail from.

>   Getting rid of spam is a HUGE benefit.

And all the proposals so far have some amount of cost. The trick is 
to come up with a solution whose benefit to at least half of the 100 
million mail users overwhelms the cost. That is, the bother of using 
the new system has to be less than the bother of getting spam.

>   Heck.  What I've found so amusing is that people seem to upgrade 
>their Microsoft systems just 'cause, with no perceived benefit, but 
>merely protecting from Bit Rot.

This is because (despite history) people believe that the replacement 
will be no harder to user than the previous version.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Thu May 29 19:35:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27401
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 19:35:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LWkX-0005Ut-Qz
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 19:23:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LWG9-0003Ti-NQ
	for ietf@asgard.ietf.org; Thu, 29 May 2003 18:52:33 -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 SAA25726
	for <ietf@ietf.org>; Thu, 29 May 2003 18:52:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LWEX-0003mM-00
	for ietf@ietf.org; Thu, 29 May 2003 18:50:53 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LWEW-0003mD-00
	for ietf@ietf.org; Thu, 29 May 2003 18:50:52 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id SAA19519;
	Thu, 29 May 2003 18:46:30 -0400
Date: Thu, 29 May 2003 18:47:35 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Iljitsch van Beijnum <iljitsch@muada.com>
cc: alh-ietf@tndh.net, "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <83CE7BB8-921E-11D7-9B54-00039388672E@muada.com>
Message-ID: <Pine.LNX.4.44.0305291834540.17321-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Thu, 29 May 2003, Iljitsch van Beijnum wrote:

> About the law: current laws are unable to keep spam in check. Is this a
> problem with the law? I don't think so. A good percentage of all spam
> (but certainly not all of it) breaks existing laws. It seems unlikely
> that additional laws will make people who already operate outside the
> law change their behavior.

Type 3 spammers are doing most of this.  These abusers are usually also in
violation of criminal federal statutes (viruses and cracking), but the
feds won't pursue them, since it seems to be a victimless, low value
crime.  This doesn't require more legislation so much as it requires Law
Enforcement to focus on the problem.

> It seems the answer to this was "no" five or six years ago. In the mean
> time, many things have changed. We now have more advanced techniques
> and more processing power at our disposal. Also, spamming in general
> has become much worse and many more children are online now, who are
> subjected to spam that isn't always "child friendly" to say the least.
> Maybe the answer is still "no" but the time is right to at least
> revisit the question.

Yes. But quite obviously, the "spammers" appearing to sell stuff like
child porn are not really selling anything. This is Type 3 abuse (no doubt
by radical anti-spammers) meant to offend people.

Spam volume is up quite a bit over the last year.  But there aren't more
spammers. There are more Type 3 abusers running larger stables of virus
infected machines, and using those stables to send junk that looks like
spam.  This isn't Type 1 or usually Type 2 spam.

The timing of the rise seems to correspond to MAPS loss in Exactis, and
the realization by certain radicals that they have to use illegal means.

		--Dean




From owner-ietf@ietf.org  Thu May 29 19:39:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27618
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 19:39:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LWsg-0006AW-Ju
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 19:32:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LWTS-0004w6-M3
	for ietf@asgard.ietf.org; Thu, 29 May 2003 19:06:18 -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 TAA26419
	for <ietf@ietf.org>; Thu, 29 May 2003 19:06:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LWRq-0003xk-00
	for ietf@ietf.org; Thu, 29 May 2003 19:04:38 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LWRp-0003wh-00
	for ietf@ietf.org; Thu, 29 May 2003 19:04:37 -0400
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49])
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h4TMx5S09763;
	Thu, 29 May 2003 15:59:05 -0700
Date: Thu, 29 May 2003 15:59:05 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: Tony Hain <alh-ietf@tndh.net>
cc: "'IETF'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
In-Reply-To: <00f401c3262c$ff9b9a30$56144104@eagleswings>
Message-ID: <Pine.LNX.4.33.0305291546570.6420-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Thu, 29 May 2003, Tony Hain wrote:

> Dave Crocker wrote:
> > Please indicate some historical basis for moving an installed
> > base of users on this kind of scale and for this kind of reason.
>
> their customers about the opportunity to use a new app. The larger
> providers (AOL, MSN, Yahoo, ...) can drive media attention and might

The providers you have listed all have what I'd call closed applications.
Yahoo is (largely) browser based working from a MUA coded in their server.
AOL is client-server, again the MUA is in their server and, I believe but
have never observed, MSN is similar to AOL. Other examples as well.

Once a new/updated mail protocol is available, then each of the above must
implement updates to their servers.  Then deploy the changes. The new
revised system will just happen to the average user of those services.

The slower process will be the millions of smaller mail infrastructures,

As long as the new protocols provide a migration plan and support, upgrade
over a year or two is a reasonable expectation. A key requirement on the
providers of the server and client software is to NOT include dependancies
on related system software versions which would force the prospective
upgradee to encounter the upgrade domino chain which ends up in
substantial costs for unrelated software or hardware.

Dave Morris




From owner-ietf@ietf.org  Thu May 29 19:47:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27830
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 19:47:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LWsi-0006GT-D1
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 19:32:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LWkT-0005UF-1R
	for ietf@asgard.ietf.org; Thu, 29 May 2003 19:23:53 -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 TAA27014
	for <ietf@ietf.org>; Thu, 29 May 2003 19:23:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LWiq-00049W-00
	for ietf@ietf.org; Thu, 29 May 2003 19:22:12 -0400
Received: from mail3.microsoft.com ([131.107.3.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LWiq-00049G-00
	for ietf@ietf.org; Thu, 29 May 2003 19:22:12 -0400
Received: from mail5.microsoft.com ([157.54.6.156]) by mail3.microsoft.com with Microsoft SMTPSVC(5.0.2195.6624);
	 Thu, 29 May 2003 16:23:19 -0700
Received: from inet-vrs-06.redmond.corp.microsoft.com ([157.54.6.181]) by mail5.microsoft.com with Microsoft SMTPSVC(5.0.2195.6624);
	 Thu, 29 May 2003 16:23:19 -0700
Received: from 157.54.5.25 by inet-vrs-06.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 29 May 2003 16:23:19 -0700
Received: from red-imc-01.redmond.corp.microsoft.com ([157.54.9.102]) by inet-hub-03.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 29 May 2003 16:23:19 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 29 May 2003 16:23:17 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3788.0);
	 Thu, 29 May 2003 16:23:16 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6940.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Subject: RE: spam
Date: Thu, 29 May 2003 16:23:15 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA037D6B39@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: spam
Thread-Index: AcMmM++r1OXO5gTvTGmhhs+1BYnCiwABM0rQ
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>,
        "Dave Aronson" <dja2003@hotpop.com>
Cc: "IETF Discussion" <ietf@ietf.org>
X-OriginalArrivalTime: 29 May 2003 23:23:16.0768 (UTC) FILETIME=[487D7A00:01C32639]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id TAA27830

> However, creating new publick/private key pairs is an incredibly
> expensive operation, and one that a legitimate email wouldn't have to
> do very often, but a spammer would if we just keep blacklisting their
> keys.

Uh? Creating a Diffie-Hellman public/private key pair is actually quite
simple. Even an RSA pair is not all that hard, considering that a set of
N prime numbers can generate N.(N-1)/2 key pairs. The logical
consequence of authenticated e-mail is bound to be authenticated spam...

-- Christian Huitema




From owner-ietf@ietf.org  Thu May 29 19:47:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27831
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 19:47:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LWsh-0006DP-FF
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 19:32:23 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LWZW-000543-MP
	for ietf@asgard.ietf.org; Thu, 29 May 2003 19:12:34 -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 TAA26676
	for <ietf@ietf.org>; Thu, 29 May 2003 19:12:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LWXu-00042V-00
	for ietf@ietf.org; Thu, 29 May 2003 19:10:54 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LWXt-000429-00
	for ietf@ietf.org; Thu, 29 May 2003 19:10:53 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id TAA13615;
	Thu, 29 May 2003 19:09:55 -0400
Date: Thu, 29 May 2003 19:11:00 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Iljitsch van Beijnum <iljitsch@muada.com>
cc: Dave Aronson <dja2003@hotpop.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: spam
In-Reply-To: <C17A52AE-921F-11D7-9B54-00039388672E@muada.com>
Message-ID: <Pine.LNX.4.44.0305291908590.17321-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 29 May 2003, Iljitsch van Beijnum wrote:

> However, creating new publick/private key pairs is an incredibly
> expensive operation, and one that a legitimate email wouldn't have to
> do very often, but a spammer would if we just keep blacklisting their
> keys.

Of course, this results in another Type 3 attack, where you get messages
with lots of bogus keys, and you have to verify the keys.

		--Dean




From owner-ietf@ietf.org  Thu May 29 19:53:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28222
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 19:53:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LWsi-0006GZ-MK
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 19:32:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LWkU-0005UH-BT
	for ietf@asgard.ietf.org; Thu, 29 May 2003 19:23:54 -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 TAA27018
	for <ietf@ietf.org>; Thu, 29 May 2003 19:23:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LWis-00049b-00
	for ietf@ietf.org; Thu, 29 May 2003 19:22:14 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LWir-00049T-00
	for ietf@ietf.org; Thu, 29 May 2003 19:22:13 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S298E9> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 29 May 2003 16:23:48 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'John Stracke'" <jstracke@centive.com>, "'IETF'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Thu, 29 May 2003 16:23:34 -0700
Message-ID: <010b01c32639$5338d250$56144104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <3ED689C6.30100@centive.com>
Importance: Normal
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id TAA28222

John Stracke wrote:
> I think you mean that, if people believed the new system would reduce 
> spam, it wouldn't take much to convince them.  

Yes.

> It *would* take a lot to 
> convince them that it would reduce spam; people with a 
> normal, healthy 
> cynicism gland (and without the expertise to analyze the new 
> protocols) 
> would assume that it was just a marketing ploy.

But a coordinated marketing ploy by the major service providers would
not be taken with the same level of cynicism as the normal hype.

Tony






From owner-ietf@ietf.org  Thu May 29 20:09:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28578
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 20:09:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LXGj-0008O1-8H
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 19:57:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LWsp-0006H4-Kb
	for ietf@asgard.ietf.org; Thu, 29 May 2003 19:32:31 -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 TAA27329
	for <ietf@ietf.org>; Thu, 29 May 2003 19:32:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LWrD-0004Dx-00
	for ietf@ietf.org; Thu, 29 May 2003 19:30:51 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LWrC-0004Dq-00
	for ietf@ietf.org; Thu, 29 May 2003 19:30:50 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id TAA15984;
	Thu, 29 May 2003 19:26:26 -0400
Date: Thu, 29 May 2003 19:27:31 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Tony Hain <alh-ietf@tndh.net>
cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
In-Reply-To: <00f901c3262e$f4f2cd90$56144104@eagleswings>
Message-ID: <Pine.LNX.4.44.0305291911180.17321-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

The ECPA permits ISPs and telecos to reveal the identification of the
participants in a communication.  Though, the Privacy Protection Act may
impose some additional requirements. Usuaully, ISPs have no interest in
providing this information without a warrant or subpoena. Privacy is part
of the service customers purchase.

In the current system, it is not hard to nail down the originator, given
there is Law Enforcement interest in finding our the identity. An IP
address works just as good as a phone number. Even an open proxy has logs,
or can be logged.

In some cases, it has been hard to find out the identity via a civil
action, as in the RIAA V Verizon. That case is not yet decided. AOL had a
somewhat similar case, where it resisted a subpoena for identification.
That case has some quirks, though. The plaintiffs also didn't want to be
identified, and I think it was considered to be frivolous or malicious
suit. I don't remember all the details.

However, sans Law Enforcement requests, or civil subpoenas, it is
difficult. It is unlikely that would change, though.  And privacy groups
would want to keep it that way, at least so that a court would decide
whether the identity is wanted for frivolous or malicious reasons. I
support the EFF in this view.

Anyway, with Type 1 and Type 2 spam, this is unnecessary, since they tell
you how to contact them in the message. It is only hard with Type 3 abuse,
which is generally involved in crimes that Law Enforcement could pursue,
but won't, for lack of interest.

		--Dean

On Thu, 29 May 2003, Tony Hain wrote:

> Iljitsch van Beijnum wrote:
> > On donderdag, mei 29, 2003, at 21:34 Europe/Amsterdam, Tony
> > Hain wrote:
> >
> > > The fundamental legal issue we need to deal with is the ability to
> > > absolutely identify the originator of the mail. Is that
> > precluded by
> > > any existing privacy laws? If not, identity would provide
> > the means to
> > > pursue financial recourse for wasted time and resources. If
> > so, we have
> > > a non-technical issue that may prevent any solution.
> >
> > Too bad the bad ideas get much more air time than the good ones.
> > Yesterday some really good points were brought up, today we're mostly
> > rehashing the bad stuff.
> >
> > About the law: current laws are unable to keep spam in check.
>
> I was not asking about spam law. I was trying to be specific about any
> privacy laws that would prevent identification of the originator of a
> message. As long as there is a legal way to undeniably trace the message
> origin, there is a chance we can build a technical approach to bulk
> message handling system that will end random spam.
>
> > ...
> > The real question is whether the current protocols
> > exhibit flaws that make the spam problem worse than it would
> > be without
> > those flaws; and whether improved protocols can be implemented and
> > deployed at reasonable levels of effectiveness and efficiency.
>
> I would argue yes, in that it is impossible to nail down the originator
> with the current system.
>
> >
> > It seems the answer to this was "no" five or six years ago.
> > In the mean
> > time, many things have changed. We now have more advanced techniques
> > and more processing power at our disposal. Also, spamming in general
> > has become much worse and many more children are online now, who are
> > subjected to spam that isn't always "child friendly" to say
> > the least.
> > Maybe the answer is still "no" but the time is right to at least
> > revisit the question.
> >
>
> I agree.
>
> Tony
>
>
>
>
>




From owner-ietf@ietf.org  Thu May 29 20:21:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28995
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 20:21:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LXGk-0008S6-QG
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 19:57:14 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LWyV-0006lB-Rh
	for ietf@asgard.ietf.org; Thu, 29 May 2003 19:38:23 -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 TAA27598
	for <ietf@ietf.org>; Thu, 29 May 2003 19:38:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LWwt-0004It-00
	for ietf@ietf.org; Thu, 29 May 2003 19:36:43 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LWwt-0004Iq-00
	for ietf@ietf.org; Thu, 29 May 2003 19:36:43 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 208439 for ietf@ietf.org; Thu, 29 May 2003 18:37:51 -0500
Message-ID: <3ED699EB.8090005@ehsco.com>
Date: Thu, 29 May 2003 18:38:19 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
References: <00e901c3261b$a3dbcf50$56144104@eagleswings> <127103972754.20030529132930@brandenburg.com>
In-Reply-To: <127103972754.20030529132930@brandenburg.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/29/2003 3:29 PM Dave Crocker wrote:

> Please indicate some historical basis for moving an installed base of
> users on this kind of scale and for this kind of reason.

Notwithstanding the overly-specific nature of the request, I can think of
two off the top of my head, which are FTP/Gopher->HTTP and POP->IMAP.

The features define the benefits, and the benefits are the motivators (I
already gave a list of the features I'd like, and which I think would be
motivational). Large-scale mail carriers would probably switch quickly if
the accountability feature proved useful, even in the absence of laws. The
same is probably true for corporates and financial services firms who rely
heavily on accountability. That's just one benefit.

There are external motivators as well, such as flagdays for the government
and all of its contractors.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Thu May 29 20:23:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29245
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 20:23:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LXHx-0008Vm-6J
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 19:58:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LX7K-0007HG-3n
	for ietf@asgard.ietf.org; Thu, 29 May 2003 19:47:30 -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 TAA27816
	for <ietf@ietf.org>; Thu, 29 May 2003 19:47:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LX5h-0004Mg-00
	for ietf@ietf.org; Thu, 29 May 2003 19:45:49 -0400
Received: from thunk.org ([140.239.227.29] helo=thunker.thunk.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LX5h-0004Md-00
	for ietf@ietf.org; Thu, 29 May 2003 19:45:49 -0400
Received: from [216.155.167.65] (helo=think.thunk.org)
	authenticated as tytso by thunker.thunk.org with asmtp 
	(tls_cipher TLSv1:DES-CBC3-SHA:168)  (Exim 3.35 #1 (Debian))
	id 19LX6p-0005EY-00; Thu, 29 May 2003 19:47:10 -0400
Received: from tytso authenticated as tytso by think.thunk.org with local   (Exim 3.35 #1 (Debian))
	id 19LQ8Q-0002Ew-00; Thu, 29 May 2003 12:20:10 -0400
Date: Thu, 29 May 2003 12:20:10 -0400
From: "Theodore Ts'o" <tytso@mit.edu>
To: Peter Deutsch <pdeutsch@earthlink.net>
Cc: Christian Huitema <huitema@windows.microsoft.com>,
        Iljitsch van Beijnum <iljitsch@muada.com>,
        "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, ietf@ietf.org
Subject: Re: A peer-to-peer trust system model (was: Re: spam)
Message-ID: <20030529162010.GB815@think>
References: <DAC3FCB50E31C54987CD10797DA511BA036BE50E@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com> <3ED50675.72DA7BFC@earthlink.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3ED50675.72DA7BFC@earthlink.net>
User-Agent: Mutt/1.5.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, May 28, 2003 at 11:56:53AM -0700, Peter Deutsch wrote:
> Concepts such as Hashcash or other payment-oriented systems, in which
> you try to impose a cost on the sender to screen out bulk mailers, are
> interesting enough, but I think they're addressing the wrong problem.
> I've personally come to the conclusion that to address this problem
> (that is, the decision as to whether I want to accept a message from
> you), I don't actually need to know who you are, or even what you're
> trying to send me, and I certainly don't need to impose artificial costs
> on you (since this looks too much like punishing the innocent for the
> crimes of the guilty).

I'm curious why you think Hashcash doesn't work.  Personally, I think
a scheme where (a) you provide a crypto signature which proves who you
are that you are someone that I trust to send me something useful,
*OR* (b) you have to send me some token which proves that you have
spent 120 seconds worth of CPU time calculating it, would work
perfectly.  That way, someone can still send me unsolicited mail
asking for help with e2fsck, or some other aspect of the Linux kernel,
but a spammer simply won't be able to afford the necessary CPU time to
send vast numbers of SPAM.  And regular correspondents with me
wouldn't could simply send a PKI authenticated token to avoid needing
to do the necessary CPU-burning calculations.  (And this is an
optimization anyway; someone who is sending me a human generated
message can generally easily afford the 2 minutes worth of CPU time
before their mailers can deliver the message to my mail host.)

						- Ted



From owner-ietf@ietf.org  Thu May 29 20:28:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29508
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 20:28:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LXOW-0000Ix-FE
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 20:05:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LXAN-000801-3f
	for ietf@asgard.ietf.org; Thu, 29 May 2003 19:50:39 -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 TAA28159
	for <ietf@ietf.org>; Thu, 29 May 2003 19:50:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LX8k-0004SA-00
	for ietf@ietf.org; Thu, 29 May 2003 19:48:58 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LX8k-0004S7-00
	for ietf@ietf.org; Thu, 29 May 2003 19:48:58 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 208445; Thu, 29 May 2003 18:50:06 -0500
Message-ID: <3ED69CCA.6010404@ehsco.com>
Date: Thu, 29 May 2003 18:50:34 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: David Morris <dwm@xpasc.com>
CC: "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
References: <Pine.LNX.4.33.0305291546570.6420-100000@egate.xpasc.com>
In-Reply-To: <Pine.LNX.4.33.0305291546570.6420-100000@egate.xpasc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/29/2003 5:59 PM David Morris wrote:

> The slower process will be the millions of smaller mail infrastructures,

Yes, small business are the biggest hurdle in the deployment cycle.

Fortunately, I think that most of them probably use their ISP's mail
services, so its not quite like we have to convince every office in every
stripmall to upgrade.

> As long as the new protocols provide a migration plan and support,
> upgrade over a year or two is a reasonable expectation.

Yes. And its also reasonable that after ~80% switch, sites can start to
disable the legacy compatibility mode. Note that many of them will still
need it for things like printservers and other devices, but for general
Internet communications it should be a little easier since most of the
changeover can happen just by getting most of the ISPs to switch.

The really hard question isn't the upgrade, its how to limit pollution
from legacy MTAs during the upgrade. If spam is still running high during
the transition, then people will wonder why they bothered.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Thu May 29 20:32:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29928
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 20:32:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LXdp-00011A-F0
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 20:21:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LXHd-0008VF-Q2
	for ietf@asgard.ietf.org; Thu, 29 May 2003 19:58:09 -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 TAA28379
	for <ietf@ietf.org>; Thu, 29 May 2003 19:58:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LXG1-0004WO-00
	for ietf@ietf.org; Thu, 29 May 2003 19:56:29 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LXG0-0004WL-00
	for ietf@ietf.org; Thu, 29 May 2003 19:56:29 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S29900> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 29 May 2003 16:58:07 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Paul Hoffman / IMC'" <phoffman@imc.org>, <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Thu, 29 May 2003 16:58:06 -0700
Message-ID: <010d01c3263e$2626ca10$56144104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <p05210672bafc3d9bca93@[63.202.92.152]>
Importance: Normal
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id UAA29928

Paul Hoffman wrote:
> Tony's proposal is not for new software: it is for software that 
> *replaces* what they have now. Further, it is not a one-to-one 
> replacement. It requires new administrative actions by the sysadmin 
> and by the user to validate who they want to get mail from.

The sysadmin effort would be setting up an automated way to hand out
keys, and the user would have a one-time (or very infrequently) effort
to establish a key pair. All the processing would then be automatic. If
the message couldn't be decrypted, or the signature verification
returned the wrong result, the message would simply be dropped. This
keeps everyone except the originator and receiver out of the content
inspection business, yet provides the receiver with an undeniable link
back to the originator for anything that gets delivered. When the
receiver decides that the content wastes resources, they get to decide
the appropriate action to take against the identified origin. 

This approach does not prevent spam, because the spammer could set up
their own public key service. It does keep the IETF out of defining spam
and how to identify & filter it, the service provider out of the
business of content inspection, and has a fairly straight forward set of
technical bounds to build products against. It increases the cost to the
spammer by seriously reducing the number of messages per minute they can
send, and it creates a traceable record to the spammer (well at least to
the key service). Existing legal infrastructure should be sufficient
from there, but I can imagine that politicians would want to claim they
were doing something about the problem and might dream up new laws, or
mandates to deploy such a technology (I am not arguing they should, just
predicting their actions). 

Tony







From owner-ietf@ietf.org  Thu May 29 20:50:05 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00532
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 20:50:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LXi7-00028F-Tj
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 20:25:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LXIM-00009B-Q7
	for ietf@asgard.ietf.org; Thu, 29 May 2003 19:58:54 -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 TAA28407
	for <ietf@ietf.org>; Thu, 29 May 2003 19:58:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LXGk-0004Wp-00
	for ietf@ietf.org; Thu, 29 May 2003 19:57:14 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LXGj-0004WS-00
	for ietf@ietf.org; Thu, 29 May 2003 19:57:14 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h4TNwJ9x003247;
	Thu, 29 May 2003 16:58:19 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AEP23027;
	Thu, 29 May 2003 16:58:18 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id QAA24075; Thu, 29 May 2003 16:58:17 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16086.40601.424667.80175@thomasm-u1.cisco.com>
Date: Thu, 29 May 2003 16:58:17 -0700 (PDT)
To: "Christian Huitema" <huitema@windows.microsoft.com>
Cc: "Iljitsch van Beijnum" <iljitsch@muada.com>,
        "Dave Aronson" <dja2003@hotpop.com>, "IETF Discussion" <ietf@ietf.org>
Subject: RE: spam
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA037D6B39@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
References: <DAC3FCB50E31C54987CD10797DA511BA037D6B39@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Christian Huitema writes:
 > > However, creating new publick/private key pairs is an incredibly
 > > expensive operation, and one that a legitimate email wouldn't have to
 > > do very often, but a spammer would if we just keep blacklisting their
 > > keys.
 > 
 > Uh? Creating a Diffie-Hellman public/private key pair is actually quite
 > simple. Even an RSA pair is not all that hard, considering that a set of
 > N prime numbers can generate N.(N-1)/2 key pairs. The logical
 > consequence of authenticated e-mail is bound to be authenticated spam...

You don't see that as a step in the right direction?

	  Mike



From owner-ietf@ietf.org  Thu May 29 20:54:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00757
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 20:54:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LXkz-0002ON-P4
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 20:28:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LXSl-0000eC-2n
	for ietf@asgard.ietf.org; Thu, 29 May 2003 20:09:39 -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 UAA28622
	for <ietf@ietf.org>; Thu, 29 May 2003 20:09:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LXR8-0004aI-00
	for ietf@ietf.org; Thu, 29 May 2003 20:07:58 -0400
Received: from smtp014.mail.yahoo.com ([216.136.173.58])
	by ietf-mx with smtp (Exim 4.12)
	id 19LXR7-0004Zy-00
	for ietf@ietf.org; Thu, 29 May 2003 20:07:57 -0400
Received: from 212.68.224.51.brutele.be (HELO isoc) (Tomson?Eric@212.68.224.51 with login)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 30 May 2003 00:09:31 -0000
Reply-To: <Tomson_Eric@Yahoo.fr>
From: "Tomson Eric \(Yahoo.fr\)" <Tomson_Eric@Yahoo.fr>
To: "'Eric A. Hall'" <ehall@ehsco.com>,
        "'John Stracke'" <jstracke@centive.com>
Cc: <ietf@ietf.org>
Subject: RE: spam
Date: Fri, 30 May 2003 02:09:25 +0200
Organization: Internet Society
Message-ID: <00e601c3263f$bc4799b0$3500a8c0@tomson.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <Pine.LNX.4.44.0305272043280.8489-100000@commander.av8.net>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id UAA00757

Guys,

Dean Anderson obviously supports and defends SPAM.
No further conversation with him could lead to anything constructive.
Stop feeding the Troll, now.

E.T.

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of Dean
Anderson
Sent: mercredi 28 mai 2003 3:04
To: Eric A. Hall
Cc: John Stracke; ietf@ietf.org
Subject: Re: spam

(...)

So what? That is no reason to ban spam.

(...)

This isn't an issue. No one said your life would be free from trash.
Furthermore, there are do-not-send lists. If anti-spammers abuse those
lists, that isn't a justification to ban spam.

(...)

No, I'm saying that spam has insignificantly small cost, and that trying to
inflate the cost somehow isn't a valid reason for banning spam.

(...)

3) Thats just stupid and unreasonable behavior. Stupidity and willfull
recklessness aren't either common or justifications for banning spam.

(...)

No, it isn't, despite your continued assertions.  You have failed to present
a case that spam costs any money, or interferes with any reaonable person's
email.





From owner-ietf@ietf.org  Thu May 29 21:00:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01093
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 21:00:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LXmi-0002dB-Nz
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 20:30:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LXbz-0000zF-En
	for ietf@asgard.ietf.org; Thu, 29 May 2003 20:19:11 -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 UAA28920
	for <ietf@ietf.org>; Thu, 29 May 2003 20:19:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LXaN-0004fn-00
	for ietf@ietf.org; Thu, 29 May 2003 20:17:31 -0400
Received: from mail4.microsoft.com ([131.107.3.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LXaM-0004fi-00
	for ietf@ietf.org; Thu, 29 May 2003 20:17:30 -0400
Received: from mail5.microsoft.com ([157.54.6.156]) by mail4.microsoft.com with Microsoft SMTPSVC(5.0.2195.6624);
	 Thu, 29 May 2003 17:18:39 -0700
Received: from inet-vrs-05.redmond.corp.microsoft.com ([157.54.6.157]) by mail5.microsoft.com with Microsoft SMTPSVC(5.0.2195.6624);
	 Thu, 29 May 2003 17:18:38 -0700
Received: from 157.54.8.109 by inet-vrs-05.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 29 May 2003 17:18:38 -0700
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-hub-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 29 May 2003 17:18:38 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 29 May 2003 17:18:37 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3788.0);
	 Thu, 29 May 2003 17:18:36 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6940.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Subject: RE: spam
Date: Thu, 29 May 2003 17:18:35 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA037D6BB0@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: spam
Thread-Index: AcMmPkoO2wc/QiE9SwW9JdmGsEUNvgAALksQ
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Michael Thomas" <mat@cisco.com>
Cc: "Iljitsch van Beijnum" <iljitsch@muada.com>,
        "Dave Aronson" <dja2003@hotpop.com>, "IETF Discussion" <ietf@ietf.org>
X-OriginalArrivalTime: 30 May 2003 00:18:36.0929 (UTC) FILETIME=[0375D710:01C32641]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA01093

>  > > However, creating new publick/private key pairs is an incredibly
>  > > expensive operation, and one that a legitimate email wouldn't
have to
>  > > do very often, but a spammer would if we just keep blacklisting
their
>  > > keys.
>  >
>  > Uh? Creating a Diffie-Hellman public/private key pair is actually
quite
>  > simple. Even an RSA pair is not all that hard, considering that a
set
> of
>  > N prime numbers can generate N.(N-1)/2 key pairs. The logical
>  > consequence of authenticated e-mail is bound to be authenticated
> spam...
> 
> You don't see that as a step in the right direction?

It depends whether you use something like PGP or something like PKI. If
PGP or PGP-like, then the spammers can very easily create throw away
identities, and we have not gained much. In fact, spammers seldom fake
the email addresses of one of your friends, so a PGP solution would not
be a dramatic improvement over simply maintaining a "white list" of
friendly email addresses. 

If PKI or PKI-like, then the spammers would need to obtain an actual
certificate for each of their throwaway identities. But so would
everyone else, which implicitly limits the cost of obtaining a
certificate to whatever the public can bear, and the amount of identity
checks to whatever the public is willing to accept, which today is an
e-mail reachability test. So, the spammers will be slowed down, but not
much.

-- Christian Huitema




From owner-ietf@ietf.org  Thu May 29 21:01:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01237
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 21:01:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LY1E-0003M2-Ut
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 20:45:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LXi4-000274-Qj
	for ietf@asgard.ietf.org; Thu, 29 May 2003 20:25:28 -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 UAA29436
	for <ietf@ietf.org>; Thu, 29 May 2003 20:25:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LXgS-0004qG-00
	for ietf@ietf.org; Thu, 29 May 2003 20:23:48 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LXgR-0004qD-00
	for ietf@ietf.org; Thu, 29 May 2003 20:23:47 -0400
Received: from [63.202.92.152] (adsl-63-202-92-152.dsl.snfc21.pacbell.net [63.202.92.152])
	(authenticated bits=0)
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h4U0PNAG065801;
	Thu, 29 May 2003 17:25:23 -0700 (PDT)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05210673bafc53af7796@[63.202.92.152]>
In-Reply-To: <010d01c3263e$2626ca10$56144104@eagleswings>
References: <010d01c3263e$2626ca10$56144104@eagleswings>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Thu, 29 May 2003 17:23:43 -0700
To: <alh-ietf@tndh.net>, <ietf@ietf.org>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: RE: The utilitiy of IP is at stake here
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 4:58 PM -0700 5/29/03, Tony Hain wrote:
>The sysadmin effort would be setting up an automated way to hand out
>keys, and the user would have a one-time (or very infrequently) effort
>to establish a key pair.

And you are saying that is trivial? How would a typical user know 
which third parties to trust? How would the typical user know what to 
do when they started getting spam through this filter? How would the 
typical user know what to do when someone wants to send him/her mail 
but can't because the sender isn't in the right trust group?

If you have already worked this out and I missed it, my apologies. A 
pointer to that document would be very helpful.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Thu May 29 21:06:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28997
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 20:21:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LXGj-0008O7-I4
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 19:57:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LWsu-0006H6-Cv
	for ietf@asgard.ietf.org; Thu, 29 May 2003 19:32:36 -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 TAA27333
	for <ietf@ietf.org>; Thu, 29 May 2003 19:32:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LWrI-0004E3-00
	for ietf@ietf.org; Thu, 29 May 2003 19:30:56 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LWrH-0004E0-00
	for ietf@ietf.org; Thu, 29 May 2003 19:30:55 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S298F0> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 29 May 2003 16:32:33 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'IETF'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Thu, 29 May 2003 16:32:18 -0700
Message-ID: <010c01c3263a$8b53f600$56144104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <Pine.LNX.4.33.0305291546570.6420-100000@egate.xpasc.com>
Importance: Normal
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id UAA28997

David Morris wrote:
> > their customers about the opportunity to use a new app. The larger 
> > providers (AOL, MSN, Yahoo, ...) can drive media attention and might
> 
> The providers you have listed all have what I'd call closed 
> applications. Yahoo is (largely) browser based working from a 
> MUA coded in their server. AOL is client-server, again the 
> MUA is in their server and, I believe but have never 
> observed, MSN is similar to AOL. Other examples as well.

In one incarnation, MSN mail is simple SMTP/POP3, in another it is web
based. That is less the point than the fact they collectively cover a
very substantial number of clients. Cover those, and provide the
enterprise mail administrator with an equivalent tool, and the rest of
the world will follow, including the spammers. It will take external
action to push back and stop the spam.

> 
> Once a new/updated mail protocol is available, then each of 
> the above must implement updates to their servers.  Then 
> deploy the changes. The new revised system will just happen 
> to the average user of those services.
> 
> The slower process will be the millions of smaller mail 
> infrastructures,

They feel the pain of spam as much (or more on a percentage basis) as
anyone else. Why wouldn't they be motiveted to deploy a spam reduction
tool?

> 
> As long as the new protocols provide a migration plan and 
> support, upgrade over a year or two is a reasonable 
> expectation. A key requirement on the providers of the server 
> and client software is to NOT include dependancies on related 
> system software versions which would force the prospective 
> upgradee to encounter the upgrade domino chain which ends up 
> in substantial costs for unrelated software or hardware.

I agree completely with the point about dependencies, but there should
be absolutely no interoperability between the old and new. The migration
plan should simply be to let the existing infrastructure and set of apps
die for lack of use.

Tony






From owner-ietf@ietf.org  Thu May 29 21:11:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01642
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 21:11:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LYE6-0004Gd-75
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 20:58:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LXnv-0002hl-Lb
	for ietf@asgard.ietf.org; Thu, 29 May 2003 20:31:31 -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 UAA29840
	for <ietf@ietf.org>; Thu, 29 May 2003 20:31:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LXmI-0004w9-00
	for ietf@ietf.org; Thu, 29 May 2003 20:29:50 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LXmG-0004w1-00
	for ietf@ietf.org; Thu, 29 May 2003 20:29:48 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 208467; Thu, 29 May 2003 19:30:52 -0500
Message-ID: <3ED6A658.8000505@ehsco.com>
Date: Thu, 29 May 2003 19:31:20 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: Tony Hain <alh-ietf@tndh.net>, "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
References: <Pine.LNX.4.44.0305291911180.17321-100000@commander.av8.net>
In-Reply-To: <Pine.LNX.4.44.0305291911180.17321-100000@commander.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/29/2003 6:27 PM Dean Anderson wrote:

> Anyway, with Type 1 and Type 2 spam, this is unnecessary, since they
> tell you how to contact them in the message.

There is still a reason to have verifiable identities for commercial spam,
which is protection against joe-jobs. You want to have proof that the
beneficiary is really the spammer and not just a victim, or that the
spammer is really the spammer regardless of who he is spamming for. While
there are ways of doing this after the fact as you said, having a
verifiable sender identity makes it a lot simpler.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Thu May 29 21:13:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01901
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 21:13:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LYE7-0004HF-0u
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 20:58:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LXoW-0002i5-Ci
	for ietf@asgard.ietf.org; Thu, 29 May 2003 20:32:08 -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 UAA29903
	for <ietf@ietf.org>; Thu, 29 May 2003 20:32:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LXmu-0004xM-00
	for ietf@ietf.org; Thu, 29 May 2003 20:30:28 -0400
Received: from sbcsmtp6.sbc.com ([144.160.20.36])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LXmt-0004w2-00
	for ietf@ietf.org; Thu, 29 May 2003 20:30:27 -0400
Received: from sbc.com (localhost [127.0.0.1])
	by sbcsmtp6.sbc.com (8.12.5/8.12.5) with ESMTP id h4U0V2A5008818
	for <ietf@ietf.org>; Thu, 29 May 2003 20:31:04 -0400 (EDT)
Received: from misout7msghub01.ITServices.sbc.com (misout7msghub01.itservices.sbc.com [144.155.106.21])
	by sbcsmtp6.sbc.com (8.12.5/8.12.5) with ESMTP id h4U0V0F5008798
	for <ietf@ietf.org>; Thu, 29 May 2003 20:31:00 -0400 (EDT)
Received: by misout7msghub01.ITServices.sbc.com with Internet Mail Service (5.5.2654.52)
	id <L7KW39N0>; Thu, 29 May 2003 20:31:26 -0400
Message-ID: <81396B513EEFB64E94E96676D5187B79D14EBC@ilnort1msgusr01.itservices.sbc.com>
From: "TABAKIS, ELEAS (AIT)" <et7563@sbc.com>
To: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here/spam
Date: Thu, 29 May 2003 20:31:20 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Would a solution to manage spam by as "simple" as to have a central email
address registry database were consumers can opt out from receiving any spam
email? Very similar proposition to the current direct marketing
"do-not-call" lists. Such an approach coupled with enforcement may be an
option. Basically this approach put the onerous on the spamer to comply and
check if an email address belongs to a list. 

Regards,

Eleas 
"Talk Straight, Follow Through"
"Trust, Character, Commitment, Passion"

 -----Original Message-----
From: 	Dean Anderson [mailto:dean@av8.com] 
Sent:	Thursday, May 29, 2003 6:28 PM
To:	Tony Hain
Cc:	'IETF Discussion'
Subject:	RE: The utilitiy of IP is at stake here

The ECPA permits ISPs and telecos to reveal the identification of the
participants in a communication.  Though, the Privacy Protection Act may
impose some additional requirements. Usuaully, ISPs have no interest in
providing this information without a warrant or subpoena. Privacy is part
of the service customers purchase.

In the current system, it is not hard to nail down the originator, given
there is Law Enforcement interest in finding our the identity. An IP
address works just as good as a phone number. Even an open proxy has logs,
or can be logged.

In some cases, it has been hard to find out the identity via a civil
action, as in the RIAA V Verizon. That case is not yet decided. AOL had a
somewhat similar case, where it resisted a subpoena for identification.
That case has some quirks, though. The plaintiffs also didn't want to be
identified, and I think it was considered to be frivolous or malicious
suit. I don't remember all the details.

However, sans Law Enforcement requests, or civil subpoenas, it is
difficult. It is unlikely that would change, though.  And privacy groups
would want to keep it that way, at least so that a court would decide
whether the identity is wanted for frivolous or malicious reasons. I
support the EFF in this view.

Anyway, with Type 1 and Type 2 spam, this is unnecessary, since they tell
you how to contact them in the message. It is only hard with Type 3 abuse,
which is generally involved in crimes that Law Enforcement could pursue,
but won't, for lack of interest.

		--Dean

On Thu, 29 May 2003, Tony Hain wrote:

> Iljitsch van Beijnum wrote:
> > On donderdag, mei 29, 2003, at 21:34 Europe/Amsterdam, Tony
> > Hain wrote:
> >
> > > The fundamental legal issue we need to deal with is the ability to
> > > absolutely identify the originator of the mail. Is that
> > precluded by
> > > any existing privacy laws? If not, identity would provide
> > the means to
> > > pursue financial recourse for wasted time and resources. If
> > so, we have
> > > a non-technical issue that may prevent any solution.
> >
> > Too bad the bad ideas get much more air time than the good ones.
> > Yesterday some really good points were brought up, today we're mostly
> > rehashing the bad stuff.
> >
> > About the law: current laws are unable to keep spam in check.
>
> I was not asking about spam law. I was trying to be specific about any
> privacy laws that would prevent identification of the originator of a
> message. As long as there is a legal way to undeniably trace the message
> origin, there is a chance we can build a technical approach to bulk
> message handling system that will end random spam.
>
> > ...
> > The real question is whether the current protocols
> > exhibit flaws that make the spam problem worse than it would
> > be without
> > those flaws; and whether improved protocols can be implemented and
> > deployed at reasonable levels of effectiveness and efficiency.
>
> I would argue yes, in that it is impossible to nail down the originator
> with the current system.
>
> >
> > It seems the answer to this was "no" five or six years ago.
> > In the mean
> > time, many things have changed. We now have more advanced techniques
> > and more processing power at our disposal. Also, spamming in general
> > has become much worse and many more children are online now, who are
> > subjected to spam that isn't always "child friendly" to say
> > the least.
> > Maybe the answer is still "no" but the time is right to at least
> > revisit the question.
> >
>
> I agree.
>
> Tony
>
>
>
>
>




From owner-ietf@ietf.org  Thu May 29 21:20:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02215
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 21:20:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LYE7-0004HL-C0
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 20:58:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LXp4-0002i7-F3
	for ietf@asgard.ietf.org; Thu, 29 May 2003 20:32:42 -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 UAA29909
	for <ietf@ietf.org>; Thu, 29 May 2003 20:32:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LXnS-0004xe-00
	for ietf@ietf.org; Thu, 29 May 2003 20:31:02 -0400
Received: from sj-core-4.cisco.com ([171.68.223.138])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LXnR-0004xP-00
	for ietf@ietf.org; Thu, 29 May 2003 20:31:01 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id h4U0W6Nb027926;
	Thu, 29 May 2003 17:32:07 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AEP26300;
	Thu, 29 May 2003 17:32:06 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id RAA24179; Thu, 29 May 2003 17:32:06 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16086.42630.127611.283035@thomasm-u1.cisco.com>
Date: Thu, 29 May 2003 17:32:06 -0700 (PDT)
To: "Christian Huitema" <huitema@windows.microsoft.com>
Cc: "Michael Thomas" <mat@cisco.com>,
        "Iljitsch van Beijnum" <iljitsch@muada.com>,
        "Dave Aronson" <dja2003@hotpop.com>, "IETF Discussion" <ietf@ietf.org>
Subject: RE: spam
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA037D6BB0@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
References: <DAC3FCB50E31C54987CD10797DA511BA037D6BB0@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Christian Huitema writes:
 > If PKI or PKI-like, then the spammers would need to obtain an actual
 > certificate for each of their throwaway identities. But so would
 > everyone else, which implicitly limits the cost of obtaining a
 > certificate to whatever the public can bear, and the amount of identity
 > checks to whatever the public is willing to accept, which today is an
 > e-mail reachability test. So, the spammers will be slowed down, but not
 > much.

What if it cost some nominal amount, but with that
payment came another form of authentication (eg
credit card number) which you could then use to
_meter_ the rate of issuing new certs, and/or
cross referencing issued certs associated with
spammers with the credit card number used to
obtain the cert? Assumedly spammers would
eventually run out of credit cards well before
they ran out of money.

As a note, the identity bound to the key can be
completely opaque and insignificant (and thus
certs could be issued trivially and cheaply).

	  Mike



From owner-ietf@ietf.org  Thu May 29 21:22:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02412
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 21:22:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LYE8-0004KQ-Jq
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 20:58:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LXwX-0003Av-Vg
	for ietf@asgard.ietf.org; Thu, 29 May 2003 20:40:25 -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 UAA00278
	for <ietf@ietf.org>; Thu, 29 May 2003 20:40:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LXuv-00053L-00
	for ietf@ietf.org; Thu, 29 May 2003 20:38:45 -0400
Received: from smtp013.mail.yahoo.com ([216.136.173.57])
	by ietf-mx with smtp (Exim 4.12)
	id 19LXuu-00053I-00
	for ietf@ietf.org; Thu, 29 May 2003 20:38:45 -0400
Received: from 212.68.224.51.brutele.be (HELO isoc) (Tomson?Eric@212.68.224.51 with login)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 30 May 2003 00:40:23 -0000
Reply-To: <Tomson_Eric@Yahoo.fr>
From: "Tomson Eric \(Yahoo.fr\)" <Tomson_Eric@Yahoo.fr>
To: "'Anthony Atkielski'" <anthony@atkielski.com>
Cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: spam - The IETF list is spam!
Date: Fri, 30 May 2003 02:40:12 +0200
Organization: Internet Society
Message-ID: <00f401c32644$0bcb99b0$3500a8c0@tomson.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <05af01c324f3$dafa3770$0a00000a@atkielski.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

So?

"Don't stop selling guns, force people to buy bullet-proof jackets"?

"Don't forbid selling cigarettes, build larger hospitals"?

Pardon me if I do not agree with you...

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of Anthony
Atkielski
Sent: mercredi 28 mai 2003 10:34
To: IETF Discussion
Subject: Re: spam - The IETF list is spam!


Tim writes:

> Can the discussion now retire to the IRTF
> anti-spam list?

Does your computer have a Delete key?





From owner-ietf@ietf.org  Thu May 29 21:33:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02921
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 21:33:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LYcF-0007v3-4h
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 21:23:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LYT1-0006PW-ND
	for ietf@asgard.ietf.org; Thu, 29 May 2003 21:13:59 -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 VAA01959
	for <ietf@ietf.org>; Thu, 29 May 2003 21:13:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LYRP-0005Vb-00
	for ietf@ietf.org; Thu, 29 May 2003 21:12:19 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LYRO-0005UU-00
	for ietf@ietf.org; Thu, 29 May 2003 21:12:18 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h4U1DN9x000576;
	Thu, 29 May 2003 18:13:23 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AEP30209;
	Thu, 29 May 2003 18:13:23 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id SAA24302; Thu, 29 May 2003 18:13:22 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16086.45106.802222.833243@thomasm-u1.cisco.com>
Date: Thu, 29 May 2003 18:13:22 -0700 (PDT)
To: Paul Hoffman / IMC <phoffman@imc.org>
Cc: <alh-ietf@tndh.net>, <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
In-Reply-To: <p05210673bafc53af7796@[63.202.92.152]>
References: <010d01c3263e$2626ca10$56144104@eagleswings>
	<p05210673bafc53af7796@[63.202.92.152]>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Paul Hoffman / IMC writes:
 > At 4:58 PM -0700 5/29/03, Tony Hain wrote:
 > >The sysadmin effort would be setting up an automated way to hand out
 > >keys, and the user would have a one-time (or very infrequently) effort
 > >to establish a key pair.
 > 
 > And you are saying that is trivial? How would a typical user know 
 > which third parties to trust? How would the typical user know what to 
 > do when they started getting spam through this filter? How would the 
 > typical user know what to do when someone wants to send him/her mail 
 > but can't because the sender isn't in the right trust group?
 > 
 > If you have already worked this out and I missed it, my apologies. A 
 > pointer to that document would be very helpful.

In reality, is this any more onerous than trying
to decide which spam or virus filters I should
trust? I "trust" spamassassin pretty explicitly
not to be a bad guy. If they distributed me a
public key I should trust too, would that really
change anything? Also: why need this be especially
different than the trust roots pre-loaded in
Mozilla, say? This problem space seems to much
more web-like than, oh say, peer to peer
authentication for computerized financial
transactions...

		Mike



From owner-ietf@ietf.org  Thu May 29 21:57:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01644
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 21:11:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LYE6-0004H4-KK
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 20:58:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LXo3-0002hu-Ij
	for ietf@asgard.ietf.org; Thu, 29 May 2003 20:31:39 -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 UAA29857
	for <ietf@ietf.org>; Thu, 29 May 2003 20:31:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LXmQ-0004wi-00
	for ietf@ietf.org; Thu, 29 May 2003 20:29:58 -0400
Received: from smtp018.mail.yahoo.com ([216.136.174.115])
	by ietf-mx with smtp (Exim 4.12)
	id 19LXmN-0004wc-00
	for ietf@ietf.org; Thu, 29 May 2003 20:29:55 -0400
Received: from 212.68.224.51.brutele.be (HELO isoc) (Tomson?Eric@212.68.224.51 with login)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 30 May 2003 00:31:33 -0000
Reply-To: <Tomson_Eric@Yahoo.fr>
From: "Tomson Eric \(Yahoo.fr\)" <Tomson_Eric@Yahoo.fr>
To: "'John C Klensin'" <john-ietf@jck.com>
Cc: "'IETF'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Fri, 30 May 2003 02:31:22 +0200
Organization: Internet Society
Message-ID: <00ed01c32642$d03ad740$3500a8c0@tomson.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <Pine.LNX.4.44.0305272213410.8489-100000@commander.av8.net>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John,

Since I don't think Dean "Troll" Anderson will do it, I would like to
apologize, in the name of every honest and decent contributor to this list,
for the insults made against someone that was so deeply involved in the
development of SMTP and MIME, and whose contribution, reputation, and
experience earned him the Internet Architecture Board's chair.

I feel so sorry to see how dishonest and undecent one can be with those who
contributed to design and build the Internet and all related technologies
and protocols.

E.T.

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of Dean
Anderson
Sent: mercredi 28 mai 2003 4:40
To: John C Klensin
Cc: shogunx; Tony Hain; 'IETF'
Subject: Re: The utilitiy of IP is at stake here

On Tue, 27 May 2003, John C Klensin wrote:

(...)

> The opinion
> of others may differ, of course but, as far as I am concerned, you are 
> succeeding in losing all credibility.

I think the same about you. It seems this will go nowhere. I'm just trying
to be polite. You've offered absolutely nothing of substance in this
-long- message.

(...)

This is just nonsense.  Obviously, you have no operational experience.

(...)





From owner-ietf@ietf.org  Thu May 29 22:12:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02411
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 21:22:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LYE8-0004KK-9P
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 20:58:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LXvx-00038X-Cc
	for ietf@asgard.ietf.org; Thu, 29 May 2003 20:39:49 -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 UAA00269
	for <ietf@ietf.org>; Thu, 29 May 2003 20:39:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LXuL-000535-00
	for ietf@ietf.org; Thu, 29 May 2003 20:38:09 -0400
Received: from carwash.centive.com ([65.220.90.249] helo=carwash.centivinc.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19LXuK-000531-00
	for ietf@ietf.org; Thu, 29 May 2003 20:38:08 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003052920461500144
 for <ietf@ietf.org>; Thu, 29 May 2003 20:46:15 -0400
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 29 May 2003 20:36:55 -0400
Message-ID: <3ED6A7A7.8050207@centive.com>
Date: Thu, 29 May 2003 20:36:55 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: A peer-to-peer trust system model
References: <DAC3FCB50E31C54987CD10797DA511BA036BE50E@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com> <3ED50675.72DA7BFC@earthlink.net> <20030529162010.GB815@think>
In-Reply-To: <20030529162010.GB815@think>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 30 May 2003 00:36:55.0678 (UTC) FILETIME=[925DA1E0:01C32643]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Theodore Ts'o wrote:

>someone who is sending me a human generated
>message can generally easily afford the 2 minutes worth of CPU time
>before their mailers can deliver the message to my mail host.)
>  
>
But what CPU? The machines with which I routinely send mail range from a 
200MHz handheld to a 2GHz*2 desktop.  I would be unhappy with a protocol 
that required me to run my handheld's CPU at full speed for 2 minutes 
(the battery life isn't so hot); but that level of hashcash would 
require only 6 seconds from my desktop, which is probably too little to 
be a deterrent.  And, if it were targetted at making my *desktop* take 2 
minutes, then the handheld would take about 40, which is totally 
unacceptable.

The whole hashcash idea has two major flaws.  The most obvious is 
Moore's Law (you'll have to keep doubling the bar every 18 months, which 
means email will get more and more expensive for people who don't 
upgrade their CPUs).  The other is that all it proves is that *somebody* 
spent those CPU cycles.  Spammers already steal resources to send their 
messages; what's to stop them from sending out stealth worms that use 
the victim's machine to do hashcash calculations?

-- 
/===========================================================\
|John Stracke      |jstracke@centive.com                    |
|Principal Engineer|http://www.centive.com                  |
|Centive           |My opinions are my own.                 |
|===========================================================|
|There are footprints on the moon. No feet, just footprints.|
\===========================================================/





From owner-ietf@ietf.org  Thu May 29 22:22:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02923
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 21:33:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LYcB-0007po-Ia
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 21:23:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LYIW-00054w-De
	for ietf@asgard.ietf.org; Thu, 29 May 2003 21:03:08 -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 VAA01469
	for <ietf@ietf.org>; Thu, 29 May 2003 21:03:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LYGu-0005Mh-00
	for ietf@ietf.org; Thu, 29 May 2003 21:01:28 -0400
Received: from 205-158-62-62.outblaze.com ([205.158.62.62] helo=mta1-2.us4.outblaze.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19LYGs-0005MP-00
	for ietf@ietf.org; Thu, 29 May 2003 21:01:27 -0400
Received: (qmail 24966 invoked by uid 0); 30 May 2003 01:02:30 -0000
MBOX-Line: From owner-ietf@ietf.org Thu May 29 21:31:20 2003
X-OB-Received: from unknown (205.158.62.35)
  by 205-158-62-62.outblaze.com; 29 May 2003 21:31:18 -0000
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by spf8.us4.outblaze.com (Postfix) with ESMTP id 28CDD7C2DE
	for <sqeet@mail.com>; Thu, 29 May 2003 21:31:14 +0000 (GMT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LUZq-0006ZV-20
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 17:04:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LUKk-0004y1-Bu
	for ietf@asgard.ietf.org; Thu, 29 May 2003 16:49: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 QAA18910
	for <ietf@ietf.org>; Thu, 29 May 2003 16:49:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LUJ8-0002Kd-00
	for ietf@ietf.org; Thu, 29 May 2003 16:47:30 -0400
Received: from [64.70.31.5] (helo=www.darkuncle.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LUJ7-0002Ka-00
	for ietf@ietf.org; Thu, 29 May 2003 16:47:29 -0400
Received: from www.darkuncle.net (bonkbonk@localhost [127.0.0.1])
	by www.darkuncle.net (8.12.9/8.12.9) with ESMTP id h4TKmqWq048465;
	Thu, 29 May 2003 13:48:52 -0700 (PDT)
	(envelope-from sfrancis@darkuncle.net)
Received: (from sfrancis@localhost)
	by www.darkuncle.net (8.12.9/8.12.9/Submit) id h4TKmqLf048464;
	Thu, 29 May 2003 13:48:52 -0700 (PDT)
Date: Thu, 29 May 2003 13:48:52 -0700
From: Scott Francis <darkuncle@darkuncle.net>
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Re: spam
Message-ID: <20030529204852.GO99106@darkuncle.net>
References: <3ED28753.3070901@ehsco.com> <Pine.LNX.4.44.0305261802010.3699-100000@commander.av8.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="/jkxxxtAhYIHVDuh"
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0305261802010.3699-100000@commander.av8.net>
User-Agent: Mutt/1.3.25i
X-Operating-System: OpenBSD <http://www.openbsd.org>
X-PGP-Fingerprint: 7429 F75D D3F5 FA45 C6D7  D25B 59A0 7B8C 5537 F527
X-What-Happen: Somebody set up us the bomb.
Sender: owner-ietf@ietf.org
Precedence: bulk


--/jkxxxtAhYIHVDuh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, May 26, 2003 at 06:17:23PM -0400, dean@av8.com said:
[snip]
> > Spam on my measured-rate cellular-data PDA is real cost. Spam on my
> > measured-rate ISDN line (California) is real cost. Extra staffing to
> > counteract spam at my [isp|university|business] is real cost (setting
> > aside other costs that you seem willing to ignore). There are plenty of
> > examples to pick from.
>=20
> Don't get email on measured rate services, then. Or don't publish the
> email to measured rate services. Put your measured rate services on the
> do-not-send list. There are many options besides banning commercial email.

Want to lay odds on how many of the hardcore spammers (spamsites hosted on
Chinanet, etc.) will respect a do-not-send list? They already ignore various
state legislations against spam (I'm a California resident, for instance, a=
nd
get any number of spams to various accounts daily that ignore existing
legislation on this topic); why would they pay any attention to a do-not-se=
nd
list?

(I'm also fairly sure such a list will not allow wildcards, and for those of
us running a domain where one address receives *@domain.org, listing every
unique address we've created over the years would be tiresome, to say the
least. I'm sure if this is not the case, someone will correct me.)

> > These are abnormal expenses which go directly into maintaining the
> > usefulness of my property and which do not increase its value. The right
> > to commercial speech would not warrant these costs for any other venue,
> > and there is nothing sufficiently different and unique about this venue=
 to
> > warrant it here.
>=20
> These are not abnormal expenses. You have deal with abuse no matter what

so, because I have an abuse person to deal with legitimate abuse problems
(both ingress and egress), I should consider it part of the cost of doing
business to put up with whatever the spammers want to do to me?

I wonder if AOL considers the cost of dealing with 2 billion spams _daily_ =
an
"abnormal expense". Especially when comparing their costs for dealing with
spam from 2 years ago. Or 6 months ago.

> the form. You have to have an abuse person. Persons intent on performing
> abuse will abuse whatever is handy.

Only too true, but it doesn't mean we have to 1) make it easy for them, or =
2)
ignore it when they do.

> There are no costs to warrant.  Spam cannot cost you more than $1 or $2
> per month per user. It doesn't matter how many abuse administrators you
> have, or how big and expensive your servers are.  Email (including spam)
> is too cheap to meter. It is practically free, per person.  Sites that
> have 10 million users are going to have larger expenses than sites that
> have 10 users. That isn't a surprise, nor a compelling reason to ban spam.

Tell that to AOL. Or Hotmail. Or any other large provider for whom the vast
majority of their network traffic is unsolicited commecial email. Your
assertions simply do not hold water. I bet they consider the costs of deali=
ng
with that illegitimate traffic a fairly compelling reason to ban spam.

> Anyway, I think commercial speech including spam _could_ be regulated, but
> there so far is no justification for doing so. I don't think there is any

If you can make that statement after considering the cost (personnel,
bandwidth, and intangibles like degradation of the quality of Internet
experience the average consumer has) of spam traffic now, compared with the
cost just 18 months ago, I guess there is no chance you will ever see the
flaws in your reasoning.

> chance whatsoever that spam will ever be banned completely, and if it
> were, it would suffer the same fate as the Junk Fax law, which had much
> more signficant costs (consumption of paper at 10 cents per page) and

10 cents per page, but there was also no single organization handling 2
billion incoming junk faxes a day. Apples and oranges, Dean.
--=20
Scott Francis || darkuncle (at) darkuncle (dot) net
      illum oportet crescere me autem minui

--/jkxxxtAhYIHVDuh
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+1nI0WaB7jFU39ScRAkWyAJ0XpVh6cPt2K7AGiW1T9DEE293cHgCfdWUt
LmlNVhoJTmGr7YXz6AGRd9Q=
=YHLo
-----END PGP SIGNATURE-----

--/jkxxxtAhYIHVDuh--




From owner-ietf@ietf.org  Thu May 29 22:29:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05011
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 22:29:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LZ2O-0001CK-1R
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 21:50:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LYrz-0000q5-MQ
	for ietf@asgard.ietf.org; Thu, 29 May 2003 21:39:47 -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 VAA03713
	for <ietf@ietf.org>; Thu, 29 May 2003 21:39:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LYqN-00061D-00
	for ietf@ietf.org; Thu, 29 May 2003 21:38:07 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LYqM-000615-00
	for ietf@ietf.org; Thu, 29 May 2003 21:38:06 -0400
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49])
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h4U1WbS10273
	for <ietf@ietf.org>; Thu, 29 May 2003 18:32:37 -0700
Date: Thu, 29 May 2003 18:32:37 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <3ED6A658.8000505@ehsco.com>
Message-ID: <Pine.LNX.4.33.0305291827450.6420-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Thu, 29 May 2003, Eric A. Hall wrote:

>
> on 5/29/2003 6:27 PM Dean Anderson wrote:
>
> > Anyway, with Type 1 and Type 2 spam, this is unnecessary, since they
> > tell you how to contact them in the message.
>
> There is still a reason to have verifiable identities for commercial spam,
> which is protection against joe-jobs. You want to have proof that the
> beneficiary is really the spammer and not just a victim, or that the
> spammer is really the spammer regardless of who he is spamming for. While
> there are ways of doing this after the fact as you said, having a
> verifiable sender identity makes it a lot simpler.

Yes, and for those folks who have asserted that I don't understand the
infrastructure cost for my stamp based proposal, may I suggest they are
ignoring the very high cost of obtaining a warrant for each piece of the
electronic trail SPAM follows.

Having built in source identification will at least allow for aggregation
of data requests in warrants for access to one ISP for many documented
infractions. It also won't be necessary to force folks to retain logs for
some period of time or force open relays to have logs or deal with the
issues where the open relay is offshore.

Dave Morris




From owner-ietf@ietf.org  Thu May 29 22:45:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05930
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 22:45:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LZXy-0001gr-Ns
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 22:23:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LZEJ-0001Mb-JW
	for ietf@asgard.ietf.org; Thu, 29 May 2003 22:02:51 -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 WAA04307
	for <ietf@ietf.org>; Thu, 29 May 2003 22:02:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LZCh-0006D0-00
	for ietf@ietf.org; Thu, 29 May 2003 22:01:11 -0400
Received: from bay7-dav26.bay7.hotmail.com ([64.4.10.83] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LZCg-0006Cx-00
	for ietf@ietf.org; Thu, 29 May 2003 22:01:10 -0400
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Thu, 29 May 2003 19:02:19 -0700
Received: from 63.228.86.45 by bay7-dav26.bay7.hotmail.com with DAV;
	Fri, 30 May 2003 02:02:18 +0000
X-Originating-IP: [63.228.86.45]
X-Originating-Email: [fritz_saad@hotmail.com]
From: "Fritz F. Saad" <Fritz_Saad@hotmail.com>
To: <ietf@ietf.org>
Subject: Home agent discovery
Date: Thu, 29 May 2003 20:02:15 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <BAY7-DAV26kXy1AP5pQ000270de@hotmail.com>
X-OriginalArrivalTime: 30 May 2003 02:02:19.0162 (UTC) FILETIME=[80333FA0:01C3264F]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Greetings,



  I'm looking for ways to manage (via SNMP if possible) home agents. My goal
is to be able to :  -1- Dynamically discover home agents -2- Query the home
agent for registered nodes with specific home agents.  Any pointers, RFCs,
ideas are appreciated.



All the best,
Fritz.









From owner-ietf@ietf.org  Thu May 29 22:46:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06049
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 22:46:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LZXz-0001hR-82
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 22:23:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LZIz-0001Q6-PP
	for ietf@asgard.ietf.org; Thu, 29 May 2003 22:07:41 -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 WAA04422
	for <ietf@ietf.org>; Thu, 29 May 2003 22:07:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LZHN-0006Ed-00
	for ietf@ietf.org; Thu, 29 May 2003 22:06:01 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LZHM-0006EI-00
	for ietf@ietf.org; Thu, 29 May 2003 22:06:00 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id WAA01283;
	Thu, 29 May 2003 22:01:49 -0400
Date: Thu, 29 May 2003 22:02:54 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: "Tomson Eric (Yahoo.fr)" <Tomson_Eric@Yahoo.fr>
cc: "'John C Klensin'" <john-ietf@jck.com>, "'IETF'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
In-Reply-To: <00ed01c32642$d03ad740$3500a8c0@tomson.be>
Message-ID: <Pine.LNX.4.44.0305292158580.17819-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Well, Einstein made blunders too. He could admit them.

Some people seem to think that having invented or significantly
contributed to something means that the inventor is immune to criticism.
That is called a personality cult. Personality cults usually have few
useful contributions, because they distract the personality.  Maybe that
is what happened to John with SMTP AUTH. I don't know.

		--Dean

On Fri, 30 May 2003, Tomson Eric (Yahoo.fr) wrote:

> John,
>
> Since I don't think Dean "Troll" Anderson will do it, I would like to
> apologize, in the name of every honest and decent contributor to this list,
> for the insults made against someone that was so deeply involved in the
> development of SMTP and MIME, and whose contribution, reputation, and
> experience earned him the Internet Architecture Board's chair.
>
> I feel so sorry to see how dishonest and undecent one can be with those who
> contributed to design and build the Internet and all related technologies
> and protocols.
>
> E.T.
>
> -----Original Message-----
> From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of Dean
> Anderson
> Sent: mercredi 28 mai 2003 4:40
> To: John C Klensin
> Cc: shogunx; Tony Hain; 'IETF'
> Subject: Re: The utilitiy of IP is at stake here
>
> On Tue, 27 May 2003, John C Klensin wrote:
>
> (...)
>
> > The opinion
> > of others may differ, of course but, as far as I am concerned, you are
> > succeeding in losing all credibility.
>
> I think the same about you. It seems this will go nowhere. I'm just trying
> to be polite. You've offered absolutely nothing of substance in this
> -long- message.
>
> (...)
>
> This is just nonsense.  Obviously, you have no operational experience.
>
> (...)
>
>
>
>




From owner-ietf@ietf.org  Thu May 29 23:09:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06396
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 23:09:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LaAo-0004Ft-Id
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 23:03:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19La0T-0003zc-JD
	for ietf@asgard.ietf.org; Thu, 29 May 2003 22:52:37 -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 WAA06221
	for <ietf@ietf.org>; Thu, 29 May 2003 22:52:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LZyr-0006lw-00
	for ietf@ietf.org; Thu, 29 May 2003 22:50:57 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LZyq-0006lm-00
	for ietf@ietf.org; Thu, 29 May 2003 22:50:56 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id WAA14451;
	Thu, 29 May 2003 22:48:49 -0400
Date: Thu, 29 May 2003 22:49:54 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: David Morris <dwm@xpasc.com>
cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <Pine.LNX.4.33.0305291827450.6420-100000@egate.xpasc.com>
Message-ID: <Pine.LNX.4.44.0305292243220.17819-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 29 May 2003, David Morris wrote:

> Having built in source identification will at least allow for aggregation
> of data requests in warrants for access to one ISP for many documented
> infractions.

We already have that in the form of the client numeric IP address in the
message headers inserted by open and closed relays.

Only open proxies complicate the issue, and require access to logs.

> It also won't be necessary to force folks to retain logs for some period
> of time or force open relays to have logs or deal with the issues where
> the open relay is offshore.

Open relays don't need logs. They put the IP address of the sender in the
message. This can't be altered by the sender.

This is a common misconception, promoted by anti-open-relay zealots, even
though they now this to be false. Relays that don't put in the numeric IP
addres of the sender are called "anonymous relays" to distinguish lack of
authentication from lack of identification.

The noise you've heard about open relays being anonyous (and thus
promoting spam) is false, and willfully misleading.

		--Dean




From owner-ietf@ietf.org  Thu May 29 23:16:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05010
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 May 2003 22:29:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LZXx-0001g8-Sh
	for ietf-list@asgard.ietf.org; Thu, 29 May 2003 22:23:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LZ9B-0001Fd-6n
	for ietf@asgard.ietf.org; Thu, 29 May 2003 21:57:33 -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 VAA04148
	for <ietf@ietf.org>; Thu, 29 May 2003 21:57:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LZ7Y-0006AY-00
	for ietf@ietf.org; Thu, 29 May 2003 21:55:52 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LZ7Y-0006AL-00
	for ietf@ietf.org; Thu, 29 May 2003 21:55:52 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id VAA24863;
	Thu, 29 May 2003 21:54:46 -0400
Date: Thu, 29 May 2003 21:55:51 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: "Eric A. Hall" <ehall@ehsco.com>
cc: Tony Hain <alh-ietf@tndh.net>, "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <3ED6A658.8000505@ehsco.com>
Message-ID: <Pine.LNX.4.44.0305292132490.17819-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


I think this makes sense, but one issue I see is deciding non-repudiation
after something like a virus infection steals your private key.  And a pgp
signed message can be resent. So if the joe-job uses a real Type 1 spam
there is ambiguity:  The type 1 spammer can't tell if the private key was
stolen, or if the message was just resent. Should he revoke his
certificate and buy a new one, or not?  No one else knows either.

They could perhaps keep a copy of all messages sent, and assume any signed
message in this list previously sent does not mean the key is stolen.

So far, most of the Joe Jobs on real type 1 spammers have made the message
obviously forged with incorrect information, apparently because the Joe
Jobber doesn't really want to inadvertantly help the Type 1 spammer. (eg,
forged McAfee spams, etc). This and the fact that the particular Type 1
spammer doesn't use open proxies in Russia to send spam, gives it away as
a joe job. But they could just as easily start sending out real McAfee
spams, say to recipients on a do-not-send list.

SO, you are still back to header analysis. And to some extent, reputation
and trust.  Things that depend on making a connection between the IP
address and the purported sender of the message.

		--Dean

On Thu, 29 May 2003, Eric A. Hall wrote:

>
> on 5/29/2003 6:27 PM Dean Anderson wrote:
>
> > Anyway, with Type 1 and Type 2 spam, this is unnecessary, since they
> > tell you how to contact them in the message.
>
> There is still a reason to have verifiable identities for commercial spam,
> which is protection against joe-jobs. You want to have proof that the
> beneficiary is really the spammer and not just a victim, or that the
> spammer is really the spammer regardless of who he is spamming for. While
> there are ways of doing this after the fact as you said, having a
> verifiable sender identity makes it a lot simpler.
>
> --
> Eric A. Hall                                        http://www.ehsco.com/
> Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/
>
>




From owner-ietf@ietf.org  Fri May 30 02:51:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21504
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 02:51:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ldbm-0005uq-AZ
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 02:43:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LdVZ-0005qn-MZ
	for ietf@asgard.ietf.org; Fri, 30 May 2003 02:36: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 CAA21274
	for <ietf@ietf.org>; Fri, 30 May 2003 02:36:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LdTw-0000BA-00
	for ietf@ietf.org; Fri, 30 May 2003 02:35:16 -0400
Received: from [208.184.79.11] (helo=clint.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LdTw-0000B6-00
	for ietf@ietf.org; Fri, 30 May 2003 02:35:16 -0400
Received: from bbprime (208.184.79.253.songbird.com [208.184.79.253] (may be forged))
	by clint.songbird.com (8.11.6/8.11.6) with ESMTP id h4U6dBx26807;
	Thu, 29 May 2003 23:39:11 -0700
Date: Thu, 29 May 2003 23:36:17 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <115140380105.20030529233617@brandenburg.com>
To: "Eric A. Hall" <ehall@ehsco.com>
CC: "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <3ED699EB.8090005@ehsco.com>
References: <00e901c3261b$a3dbcf50$56144104@eagleswings>
 <127103972754.20030529132930@brandenburg.com> <3ED699EB.8090005@ehsco.com>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks,


>> Please indicate some historical basis for moving an installed base of
>> users on this kind of scale and for this kind of reason.

EAH> Notwithstanding the overly-specific nature of the request, I can think of
EAH> two off the top of my head, which are FTP/Gopher->HTTP and POP->IMAP.

HTTP can reasonably be considered a replacement for Anonymous FTP,
during an academic discussion.  The massive difference in the service
experience makes this a less-than-practical comparison, when discussion
an email transition.  So does the massive difference in scaling issues
for the 1989 timeframe, versus now.

The POP->IMAP example is excellent, since it really demonstrates my
point. IMAP is rather popular in some local area network environments.
However it's long history has failed utterly to seriously displace POP
on a global scale.


EAH> Large-scale mail carriers would probably switch quickly if
EAH> the accountability feature proved useful,

and now we are back to hypothesizing about the behaviors of
mega-corporations with massive installed bases and a rather poor history
of adopting changes from the IETF community.

Seriously folks, if discussion about changes is going to be productive,
it needs to pay much more realistic attention to history and pragmatics
of ISP operations and average-user preferences.


d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Fri May 30 03:06:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21944
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 03:06:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LdnF-0006Sd-5K
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 02:55:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ldk4-0006M4-Mp
	for ietf@asgard.ietf.org; Fri, 30 May 2003 02:51:56 -0400
Received: from goose.ehsco.com (98.in-addr.ehsco.com [207.65.203.98] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21543
	for <ietf@ietf.org>; Fri, 30 May 2003 02:51:55 -0400 (EDT)
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 208518; Fri, 30 May 2003 01:51:20 -0500
Message-ID: <3ED6FF85.5060406@ehsco.com>
Date: Fri, 30 May 2003 01:51:49 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Dave Crocker <dcrocker@brandenburg.com>
CC: "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
References: <00e901c3261b$a3dbcf50$56144104@eagleswings> <127103972754.20030529132930@brandenburg.com> <3ED699EB.8090005@ehsco.com> <115140380105.20030529233617@brandenburg.com>
In-Reply-To: <115140380105.20030529233617@brandenburg.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/30/2003 1:36 AM Dave Crocker wrote:

> HTTP can reasonably be considered a replacement for Anonymous FTP,
> during an academic discussion.  The massive difference in the service
> experience makes this a less-than-practical comparison, when discussion
> an email transition.  So does the massive difference in scaling issues
> for the 1989 timeframe, versus now.
>
> The POP->IMAP example is excellent, since it really demonstrates my
> point. IMAP is rather popular in some local area network environments.
> However it's long history has failed utterly to seriously displace POP
> on a global scale.

I would not disagree with your assessments other than to say that the
comparisons aren't exactly applicable.

Specifically, you don't have to upgrade every client in the world for the
transition to work. As a matter of deployment, you only have to upgrade
the MTAs. The submission service can still be SMTP or whatever you want;
as long as the server which first puts the message into the ng stream is
ng-compliant *AND* that server is capable of providing the identity
information, then the first-hop(s) don't really have to be ng-compliant
for the scheme to work.

Asking for examples of upgrades involving hundreds of millions of clients
isn't really an applicable exercise. The examples I gave are useful to the
extent that they demonstrate a willingness to move critical technology in
varying scales.

> Seriously folks, if discussion about changes is going to be productive,
> it needs to pay much more realistic attention to history and pragmatics
> of ISP operations and average-user preferences.

Let's not overdo it either.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Fri May 30 03:12:48 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22158
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 03:12:48 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Le10-0006wI-LK
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 03:09:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ldny-0006UO-Tv
	for ietf@asgard.ietf.org; Fri, 30 May 2003 02:55:58 -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 CAA21738
	for <ietf@ietf.org>; Fri, 30 May 2003 02:55:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LdmM-0000IB-00
	for ietf@ietf.org; Fri, 30 May 2003 02:54:18 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LdmL-0000I8-00
	for ietf@ietf.org; Fri, 30 May 2003 02:54:17 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4U6tuKk045329
	for <ietf@ietf.org>; Fri, 30 May 2003 08:55:56 +0200 (CEST)
Message-ID: <09a301c32678$84dc31a0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <00e901c3261b$a3dbcf50$56144104@eagleswings> <127103972754.20030529132930@brandenburg.com> <3ED67A32.4020007@cisco.com>
Subject: Re: The utilitiy of IP is at stake here
Date: Fri, 30 May 2003 08:55:56 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eliot writes:

> From the Internet Worm to Code Red, consumers do
> install software when they perceive either a
> threat or a benefit.

What percentage of users, even today, have installed fixes for either of
these problems?

> What I've found so amusing is that people seem
> to upgrade their Microsoft systems just 'cause,
> with no perceived benefit, but merely protecting
> from Bit Rot.

I've never noticed that, except in cases of automated updates, such as those
of Windows XP.




From owner-ietf@ietf.org  Fri May 30 03:23:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22590
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 03:23:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Le10-0006wY-UE
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 03:09:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LdsP-0006WL-93
	for ietf@asgard.ietf.org; Fri, 30 May 2003 03:00:33 -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 DAA21802
	for <ietf@ietf.org>; Fri, 30 May 2003 03:00:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ldqm-0000Ja-00
	for ietf@ietf.org; Fri, 30 May 2003 02:58:52 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ldql-0000JX-00
	for ietf@ietf.org; Fri, 30 May 2003 02:58:51 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4U70VKk045370
	for <ietf@ietf.org>; Fri, 30 May 2003 09:00:31 +0200 (CEST)
Message-ID: <09aa01c32679$289e09d0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <sed61b06.037@gwianameserver.sj.symbol.com>
Subject: Re: spam
Date: Fri, 30 May 2003 09:00:30 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Clint writes:

> One problem with attaching the "secret" string
> to an email address is how that is done at the
> sender's side.  I can see email clients automating
> the process, which is fine, until a virus comes
> along and starts popping off random emails.

Viruses are a separate problem from spam.

> Plus, how would CC: and vast To: lists hide
> the secret string?

They wouldn't, but that wouldn't be necessary, either.

The whole idea is to provide some sort of authentication for messages that
is easy to obtain for human beings, but hard to obtain in an automated way
for spammers.  Spammers obtain e-mail addresses from Web sites, USENET,
discussion forums, and the like.  Secret strings would not be posted to any
of these, so no automated harvesting of the strings would be possible.  Just
leaving the string in an e-mail addresses to a number of recipients would
not be a problem, because spammers would not be intercepting such e-mails
(or any e-mails, for that matter).  As long as the string is not posted in a
place where spammers can harvest it, they won't get it.  And hiring human
beings to locate strings for individual addresses rapidly becomes too
expensive to contemplate.

As I've said, the White House uses it, and I don't think they get too many
letters from unauthorized parties with the secret string/number, even though
conceivably anyone in the delivery chain along the way could see the number.
The mere fact that it is not publicly posted is security enough.




From owner-ietf@ietf.org  Fri May 30 03:27:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22764
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 03:27:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Le1q-00070T-DZ
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 03:10:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ldyi-0006s1-B2
	for ietf@asgard.ietf.org; Fri, 30 May 2003 03:07:04 -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 DAA21983
	for <ietf@ietf.org>; Fri, 30 May 2003 03:07:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ldx5-0000Ly-00
	for ietf@ietf.org; Fri, 30 May 2003 03:05:23 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ldx4-0000Ln-00
	for ietf@ietf.org; Fri, 30 May 2003 03:05:22 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4U771Kk045433
	for <ietf@ietf.org>; Fri, 30 May 2003 09:07:01 +0200 (CEST)
Message-ID: <09e301c3267a$111f85d0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <00f401c32644$0bcb99b0$3500a8c0@tomson.be>
Subject: Re: spam - The IETF list is spam!
Date: Fri, 30 May 2003 09:07:00 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Your analogies are flawed.  Spam is easy to delete, but bullets are
exceedingly hard to dodge (outside the Matrix), and cigarettes are smoked
voluntarily by the people in whom they produce cancer.

----- Original Message -----
From: "Tomson Eric (Yahoo.fr)" <Tomson_Eric@Yahoo.fr>
To: "'Anthony Atkielski'" <anthony@atkielski.com>
Cc: "'IETF Discussion'" <ietf@ietf.org>
Sent: Friday, May 30, 2003 02:40
Subject: RE: spam - The IETF list is spam!


> So?
>
> "Don't stop selling guns, force people to buy bullet-proof jackets"?
>
> "Don't forbid selling cigarettes, build larger hospitals"?
>
> Pardon me if I do not agree with you...




From owner-ietf@ietf.org  Fri May 30 03:33:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22981
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 03:33:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LeGG-0007s7-Pi
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 03:25:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Le13-0006wf-7i
	for ietf@asgard.ietf.org; Fri, 30 May 2003 03:09:29 -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 DAA22106
	for <ietf@ietf.org>; Fri, 30 May 2003 03:09:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LdzQ-0000OR-00
	for ietf@ietf.org; Fri, 30 May 2003 03:07:48 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LdzP-0000OO-00
	for ietf@ietf.org; Fri, 30 May 2003 03:07:47 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4U79QKk045450
	for <ietf@ietf.org>; Fri, 30 May 2003 09:09:26 +0200 (CEST)
Message-ID: <09ea01c3267a$67ed0cc0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <00e601c3263f$bc4799b0$3500a8c0@tomson.be>
Subject: Re: spam
Date: Fri, 30 May 2003 09:09:26 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Guys,

Girls aren't included?

> Dean Anderson obviously supports and defends SPAM.
> No further conversation with him could lead to anything
> constructive. Stop feeding the Troll, now.

I tend to find calls to censorship and lynchings suspicious.  If you don't
like someone's posts, you don't have to read or reply to them, but
attempting to turn others against someone with whom you disagree is
ethically questionable.




From owner-ietf@ietf.org  Fri May 30 03:42:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23285
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 03:42:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LeKa-0008FQ-En
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 03:29:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Le5E-0007Ml-PM
	for ietf@asgard.ietf.org; Fri, 30 May 2003 03:13:48 -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 DAA22251
	for <ietf@ietf.org>; Fri, 30 May 2003 03:13:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Le3b-0000RP-00
	for ietf@ietf.org; Fri, 30 May 2003 03:12:07 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Le3b-0000RL-00
	for ietf@ietf.org; Fri, 30 May 2003 03:12:07 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4U7DkKk045494
	for <ietf@ietf.org>; Fri, 30 May 2003 09:13:46 +0200 (CEST)
Message-ID: <09f601c3267b$02b82000$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <00ed01c32642$d03ad740$3500a8c0@tomson.be>
Subject: Re: The utilitiy of IP is at stake here
Date: Fri, 30 May 2003 09:13:46 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> John,

If you are speaking only to John, why do you send your message to an entire
list?

> Since I don't think Dean "Troll" Anderson will do
> it, I would like to apologize, in the name of every
> honest and decent contributor to this list, for the
> insults made against someone that was so deeply
> involved in the development of SMTP and MIME, and
> whose contribution, reputation, and experience earned
> him the Internet Architecture Board's chair.

Your attempt to discredit someone else on the list is transparently obvious.
Why not just state your disagreement with him and leave it at that, instead
of embarking on a smear campaign?

> I feel so sorry to see how dishonest and undecent
> one can be with those who contributed to design and
> build the Internet and all related technologies
> and protocols.

See above.  A rather poor attempt to disguise defamation as nobility.

Perhaps you should simply speak for yourself, instead of presuming to speak
for others, particularly when the latter is really only a platform for
actions of questionable merit?




From owner-ietf@ietf.org  Fri May 30 03:46:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23471
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 03:46:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LeKa-0008Fv-PM
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 03:29:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Le6H-0007N4-Vk
	for ietf@asgard.ietf.org; Fri, 30 May 2003 03:14:53 -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 DAA22297
	for <ietf@ietf.org>; Fri, 30 May 2003 03:14:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Le4f-0000SR-00
	for ietf@ietf.org; Fri, 30 May 2003 03:13:13 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Le4e-0000SO-00
	for ietf@ietf.org; Fri, 30 May 2003 03:13:12 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4U7EpKk045504
	for <ietf@ietf.org>; Fri, 30 May 2003 09:14:51 +0200 (CEST)
Message-ID: <09fb01c3267b$29821650$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <81396B513EEFB64E94E96676D5187B79D14EBC@ilnort1msgusr01.itservices.sbc.com>
Subject: Re: The utilitiy of IP is at stake here/spam
Date: Fri, 30 May 2003 09:14:51 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The problem is that it does nothing to address rogue spammers who refuse to
respect the opt-out list.

----- Original Message -----
From: "TABAKIS, ELEAS (AIT)" <et7563@sbc.com>
To: "'IETF Discussion'" <ietf@ietf.org>
Sent: Friday, May 30, 2003 02:31
Subject: RE: The utilitiy of IP is at stake here/spam


> Would a solution to manage spam by as "simple" as to have a central email
> address registry database were consumers can opt out from receiving any
spam
> email? Very similar proposition to the current direct marketing
> "do-not-call" lists. Such an approach coupled with enforcement may be an
> option. Basically this approach put the onerous on the spamer to comply
and
> check if an email address belongs to a list.
>
> Regards,
>
> Eleas
> "Talk Straight, Follow Through"
> "Trust, Character, Commitment, Passion"




From owner-ietf@ietf.org  Fri May 30 03:47:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23596
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 03:47:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LeKb-0008GB-2O
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 03:29:41 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Le8n-0007QI-1E
	for ietf@asgard.ietf.org; Fri, 30 May 2003 03:17:29 -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 DAA22367
	for <ietf@ietf.org>; Fri, 30 May 2003 03:17:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Le7A-0000Tg-00
	for ietf@ietf.org; Fri, 30 May 2003 03:15:48 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Le79-0000Td-00
	for ietf@ietf.org; Fri, 30 May 2003 03:15:47 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4U7HQKk045524
	for <ietf@ietf.org>; Fri, 30 May 2003 09:17:26 +0200 (CEST)
Message-ID: <0a0001c3267b$860fa130$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <DAC3FCB50E31C54987CD10797DA511BA037D6BB0@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com> <16086.42630.127611.283035@thomasm-u1.cisco.com>
Subject: Re: spam
Date: Fri, 30 May 2003 09:17:26 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I can't say that I'd favor any solution that requires everyone to pay money
or obtain the approval of some third party before sending e-mail.  Any
system that imposes a universal financial burden on all Internet users
and/or effectively allows a third party to censor communication between two
other parties is extremely questionable in my view.

A technical solution must be free, voluntary for people who are not
spammers, and must not subject anyone to the control of third parties.

----- Original Message -----
From: "Michael Thomas" <mat@cisco.com>
To: "Christian Huitema" <huitema@windows.microsoft.com>
Cc: "Michael Thomas" <mat@cisco.com>; "Iljitsch van Beijnum"
<iljitsch@muada.com>; "Dave Aronson" <dja2003@hotpop.com>; "IETF Discussion"
<ietf@ietf.org>
Sent: Friday, May 30, 2003 02:32
Subject: RE: spam


> Christian Huitema writes:
>  > If PKI or PKI-like, then the spammers would need to obtain an actual
>  > certificate for each of their throwaway identities. But so would
>  > everyone else, which implicitly limits the cost of obtaining a
>  > certificate to whatever the public can bear, and the amount of identity
>  > checks to whatever the public is willing to accept, which today is an
>  > e-mail reachability test. So, the spammers will be slowed down, but not
>  > much.
>
> What if it cost some nominal amount, but with that
> payment came another form of authentication (eg
> credit card number) which you could then use to
> _meter_ the rate of issuing new certs, and/or
> cross referencing issued certs associated with
> spammers with the credit card number used to
> obtain the cert? Assumedly spammers would
> eventually run out of credit cards well before
> they ran out of money.
>
> As a note, the identity bound to the key can be
> completely opaque and insignificant (and thus
> certs could be issued trivially and cheaply).
>
>   Mike
>
>




From owner-ietf@ietf.org  Fri May 30 04:13:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24538
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 04:13:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LeeV-0001ZG-SV
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 03:50:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LeLU-0008MH-Pm
	for ietf@asgard.ietf.org; Fri, 30 May 2003 03:30:36 -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 DAA22940
	for <ietf@ietf.org>; Fri, 30 May 2003 03:30:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LeJr-0000dy-00
	for ietf@ietf.org; Fri, 30 May 2003 03:28:55 -0400
Received: from [208.184.79.253] (helo=jay.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LeJr-0000du-00
	for ietf@ietf.org; Fri, 30 May 2003 03:28:55 -0400
Received: from Rincewind.ninebynine.org (jay.songbird.com [208.184.79.253])
	(authenticated)
	by jay.songbird.com (8.11.6/8.11.3) with ESMTP id h4U7UQf09877;
	Fri, 30 May 2003 00:30:26 -0700
Message-Id: <5.1.0.14.2.20030529175647.02e04bc0@127.0.0.1>
X-Sender: gk-bulk@127.0.0.1 (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 29 May 2003 18:16:09 +0100
To: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
From: Graham Klyne <GK@ninebynine.org>
Subject: Re: spam
In-Reply-To: <200305291544.h4TFi8FR006326@calcite.rhyolite.com>
References: <FA2605DA-91E4-11D7-9B54-00039388672E@muada.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 09:44 29/05/03 -0600, Vernon Schryver wrote:
>It is an article of faith for many people that most spam involves
>header forgery, but no one seems to have better support than intuition
>for that faith.

This comment prompted me to do a little experimentation.  I keep all my 
spam (except that large ones that I don't bother to download), mostly unread.

It's not scientific, or very statistically significant, but I examined the 
last 20 spam mails I received, and note that:

(a)  3 appear to have been received at my ISP with forged or inconsistent 
SMTP envelope information.

(b)  7 have significant inconsistencies between email headers and 
received-from trace to make me believe that they are probably forged headers.

(c)  5 have email header information that may or may not be forged -- I 
couldn't see enough evidence to make an assessment either way

(d)  5 have email headers that I believe to be genuine.  Of these, 3 come 
from what I presume to be throw-away accounts at AOL or hotmail.

My assessments were made initially by comparing the from address with the 
received trace, and making a judgement (not always scientifically) about 
the relationship between the addresses offered.  In some cases, I also 
looked to the message content and check to see if the source address is 
DNS-resolvable and/or reachable.  Of the "definitely-forged" headers, three 
used domain names that are operated by my own ISP, and I'm pretty sure are 
not customers of same.

The 20 messages I examined appeared to be broadly typical of the style of 
spam I generally receive.

This little experiment suggests to me that header forgery is a significant 
factor in spam -- I estimate about 50% of the sample I examined.

And one other data point:  in looking at my spam, I discovered two messages 
that were not strictly spam, because I had signed up for communications in 
the past, but which had been swept into my spam-box in the general 
clear-out.  I don't currently use automatic filtering, but simply move 
unrecognized messages  onopened into the spam box.  The point of this is 
that legitimate email marketing is suffering by failing to be sufficiently 
distinct from the unsolicited spam.

I don't claim all this proves anything, but I think I have cause to believe 
forgery of email headers is involved in a significant portion of the spam I 
receive.

#g


-------------------
Graham Klyne
<GK@NineByNine.org>
PGP: 0FAA 69FF C083 000B A2E9  A131 01B9 1C7A DBCA CB5E




From owner-ietf@ietf.org  Fri May 30 07:14:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28195
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 07:14:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LhcK-00057A-PY
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 07:00:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LhYS-00053U-PR
	for ietf@asgard.ietf.org; Fri, 30 May 2003 06:56:12 -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 GAA27503
	for <ietf@ietf.org>; Fri, 30 May 2003 06:56:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LhWp-0001zN-00
	for ietf@ietf.org; Fri, 30 May 2003 06:54:31 -0400
Received: from anchor-post-35.mail.demon.net ([194.217.242.85])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LhWp-0001zK-00
	for ietf@ietf.org; Fri, 30 May 2003 06:54:31 -0400
Received: from soaring.demon.co.uk ([80.177.120.110])
	by anchor-post-35.mail.demon.net with esmtp (Exim 3.36 #2)
	id 19LhYQ-0001Xg-0Z
	for ietf@ietf.org; Fri, 30 May 2003 11:56:10 +0100
Message-ID: <lHoQPzDbiz1+Ewdx@soaring.demon.co.uk>
Date: Fri, 30 May 2003 11:55:23 +0100
To: ietf@ietf.org
From: Andrew Shore <ietf@soaring.demon.co.uk>
Reply-To: Andrew Shore <ietf@soaring.demon.co.uk>
Subject: Re: Spam
MIME-Version: 1.0
Content-Type: text/plain;charset=us-ascii;format=flowed
User-Agent: Turnpike/6.02-S (<aCAGT1CKFCi8lsT3mwPhfD$m6j>)
Sender: owner-ietf@ietf.org
Precedence: bulk


     The following is part of a message posted to my ISP's announce NG. I 
found it interesting, specifically the claim that there are 180 entities 
creating nearly all the spam... it would explain the recurrence of 
certain seemingly unlikely patterns across the board, but is still hard 
to credit even with that in mind.

-----

Subject:     Unsolicited Commercial / Bulk Email Spam
Newsgroups:  demon.announce
From:        Malcolm S. Muir <Malcolm@demon.net>
Reply-To:    helpdesk@demon.net
Date:        Fri, 30 May 2003 10:41:48 +0100
Message-ID:  <zMof+XAcdy1+EwvH@demon.net>

The following is a summary of advice we have available on our web
site for customers having trouble with unsolicited email.

The full text can be found at:

    http://www.demon.net/helpdesk/spam

[snip]
Where does UCE come from?

    Some 'spam' is sent by companies that are new to the Internet
    and do not understand how unwelcome this material is. However
    recent reports suggest that 90% of all the material currently
    being sent originates from as few as 180 individuals or 'spam
    gangs'. These groups make a business out of promoting unsavoury
    (and sometimes illegal) material. They hide the true origin of
    the material by relaying their email via insecure mail systems
    and machines. Although in the past they have targeted incorrectly
    configured machines at ISPs and large companies, they now
    regularly exploit end-user ('customer') machines.
[snip]

Malcolm Muir
Demon Internet

-----


Andrew.
-- 
Andrew Shore.



From owner-ietf@ietf.org  Fri May 30 09:33:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06288
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 09:33:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LiyN-0005sw-Tw
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 08:27:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Lhrl-0008Pp-5p
	for ietf@asgard.ietf.org; Fri, 30 May 2003 07:16:09 -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 HAA28636
	for <ietf@ietf.org>; Fri, 30 May 2003 07:16:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lhq8-00027d-00
	for ietf@ietf.org; Fri, 30 May 2003 07:14:28 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lhq7-00027a-00
	for ietf@ietf.org; Fri, 30 May 2003 07:14:27 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h4UBH9xS022735;
	Fri, 30 May 2003 13:17:09 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Fri, 30 May 2003 13:16:06 +0200
Subject: Re: spam
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "IETF Discussion" <ietf@ietf.org>
To: "Christian Huitema" <huitema@windows.microsoft.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA037D6BB0@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Message-Id: <1B7C2780-9290-11D7-9B54-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On vrijdag, mei 30, 2003, at 02:18 Europe/Amsterdam, Christian Huitema 
wrote:

>>>> However, creating new publick/private key pairs is an incredibly
>>>> expensive operation,

>>> Uh? Creating a Diffie-Hellman public/private key pair is actually 
>>> quite
>>> simple. Even an RSA pair is not all that hard, considering that a 
>>> set of
>>> N prime numbers can generate N.(N-1)/2 key pairs.

Ok, so the actual generating of new keys may not help us much.

>>> The logical
>>> consequence of authenticated e-mail is bound to be authenticated 
>>> spam...

>> You don't see that as a step in the right direction?

> It depends whether you use something like PGP or something like PKI. If
> PGP or PGP-like, then the spammers can very easily create throw away
> identities, and we have not gained much.

Only the ability to recognize a known sender.

> In fact, spammers seldom fake
> the email addresses of one of your friends, so a PGP solution would not
> be a dramatic improvement over simply maintaining a "white list" of
> friendly email addresses.

Right.

> If PKI or PKI-like, then the spammers would need to obtain an actual
> certificate for each of their throwaway identities. But so would
> everyone else, which implicitly limits the cost of obtaining a
> certificate to whatever the public can bear, and the amount of identity
> checks to whatever the public is willing to accept, which today is an
> e-mail reachability test. So, the spammers will be slowed down, but not
> much.

Disagree. If people want to run their own MTA or a substantial mailing 
list, it's not unreasonable to require much more than a simple email 
reachability check. Usually this includes buying a domain name anyway. 
Having to buy a certificate or having some relations sign a newly 
generated key isn't a huge imposition.

People who don't want/need an MTA of their own and only send hand-typed 
email can use a service provider who can limit the number of messasges 
from such customers to 100 per hour or so. That means that even if a 
spammer spams for an entire weekend until his account is yanked, that's 
less than 10k messages which isn't enough to make spamming worth their 
while.




From owner-ietf@ietf.org  Fri May 30 09:37:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06626
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 09:37:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LiyS-000656-CG
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 08:27:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LiK4-0003Ia-1F
	for ietf@asgard.ietf.org; Fri, 30 May 2003 07:45:24 -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 HAA00069
	for <ietf@ietf.org>; Fri, 30 May 2003 07:45:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LiIQ-0002Vw-00
	for ietf@ietf.org; Fri, 30 May 2003 07:43:42 -0400
Received: from cust-smtp1.radiolinja.fi ([213.161.33.208])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LiIQ-0002Vt-00
	for ietf@ietf.org; Fri, 30 May 2003 07:43:42 -0400
Received: from EMCL (rl045112.radiolinja.net [213.161.45.112])
	by cust-smtp1.radiolinja.fi (Postfix) with SMTP
	id 6A8554000A; Fri, 30 May 2003 14:45:17 +0300 (EEST)
From: "=?UTF-8?Q?John_Loughney?=" <john.loughney@kolumbus.fi>
To: <vjs@calcite.rhyolite.com>, <ietf@ietf.org>
Subject: =?UTF-8?Q?Re:_The_utilitiy_of_IP_is_at_stake_here?=
Date: Fri, 30 May 2003 14:41:16 +0000
Message-Id: <1054305676191>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
X-Mailer: EMCL v2.14
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA06626

Elliot,

>           Getting rid of spam is a HUGE benefit.  Heck.  What I've found 
> so amusing is that people seem to upgrade their Microsoft systems just 
> 'cause, with no perceived benefit, but merely protecting from Bit Rot.


Many folks update their MS software (Linux, too) in the hope they will get more stability / more security / more seatures - not becaue of bit rot. Updating mail clients does not seem to be a huge deal - manypeople update their OS / browser when prompted. Majority of my friends & family use a web browser to access private mail. Companies would have interest in upgrading, if it helped also with viruses & security.

John                                         



From owner-ietf@ietf.org  Fri May 30 09:54:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07431
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 09:54:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lk4g-0006QD-Ux
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 09:37:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LjK8-0000HN-WF
	for ietf@asgard.ietf.org; Fri, 30 May 2003 08:49:33 -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 IAA04240
	for <ietf@ietf.org>; Fri, 30 May 2003 08:49:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LjIV-0003lS-00
	for ietf@ietf.org; Fri, 30 May 2003 08:47:51 -0400
Received: from mail13.speakeasy.net ([216.254.0.213] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LjIU-0003lP-00
	for ietf@ietf.org; Fri, 30 May 2003 08:47:50 -0400
Received: (qmail 14814 invoked from network); 30 May 2003 12:49:29 -0000
Received: from unknown (HELO 192.168.254.124) ([66.92.168.196])
          (envelope-sender <dja2003@hotpop.com>)
          by mail13.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <iljitsch@muada.com>; 30 May 2003 12:49:29 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: crypto-spam
Date: Fri, 30 May 2003 08:51:51 -0400
User-Agent: KMail/1.5
Cc: IETF Discussion <ietf@ietf.org>
References: <C17A52AE-921F-11D7-9B54-00039388672E@muada.com>
In-Reply-To: <C17A52AE-921F-11D7-9B54-00039388672E@muada.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305300851.51089.dja2003@hotpop.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Thursday 29 May 2003 17:51, Iljitsch van Beijnum wrote:

 I> However, creating new publick/private key pairs is an
 I> incredibly expensive operation, and one that a legitimate
 I> email wouldn't have to do very often, but a spammer would
 I> if we just keep blacklisting their keys.

I was only responding to the part about encrypting the message's hash 
with the recipient's public key.  Nobody needs to generate any keys, 
except those who want to be behind this sort of gatekeeping function.  
Requiring that all email be signed with a private key is another story, 
which has been (ahem) hashed over many times.

BTW, I also thought of a way you can make the computational costs much 
harder for spammers.  This unfortunately also affects legitimate bulk 
mailers, but they can be whitelisted.  However, it keeps the costs 
roughly the same for most ordinary (one-to-one) senders.  The trick is 
to require that the hash include the recipient address, not just the 
message body.  That way, not only must the hash be re-encrypted per 
recipient, but re*calculated*.  Even worse, you can insist that the 
address be *first*, so they can't just save the results of hashing the 
message and start from there for each victim.  Sorry if this has been 
brought up already; I've only been lurking a few days and haven't delved 
THAT deeply into the archives....  B-)

-- 
David J. Aronson, Unemployed Software Engineer near Washington DC
See http://destined.to/program/ for online resume, and other info




From owner-ietf@ietf.org  Fri May 30 10:05:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08247
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 10:05:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lk55-0006Tg-Vf
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 09:38:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LjS5-0001Au-Hj
	for ietf@asgard.ietf.org; Fri, 30 May 2003 08:57:45 -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 IAA04493
	for <ietf@ietf.org>; Fri, 30 May 2003 08:57:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LjQS-0003qK-00
	for ietf@ietf.org; Fri, 30 May 2003 08:56:04 -0400
Received: from mail13.speakeasy.net ([216.254.0.213] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LjQR-0003qG-00
	for ietf@ietf.org; Fri, 30 May 2003 08:56:03 -0400
Received: (qmail 31681 invoked from network); 30 May 2003 12:57:41 -0000
Received: from unknown (HELO 192.168.254.124) ([66.92.168.196])
          (envelope-sender <dja2003@hotpop.com>)
          by mail13.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <ietf@ietf.org>; 30 May 2003 12:57:41 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: crypto-spam
Date: Fri, 30 May 2003 09:00:02 -0400
User-Agent: KMail/1.5
References: <C17A52AE-921F-11D7-9B54-00039388672E@muada.com> <200305300851.51089.dja2003@hotpop.com>
In-Reply-To: <200305300851.51089.dja2003@hotpop.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305300900.02801.dja2003@hotpop.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Yeah, I know, self-followup is bad form, but I just wrote:

 DA> Sorry if this has been brought up already; I've only been lurking a
 DA> few days and haven't delved THAT deeply into the archives....  B-)

Oops, wrong list.  Thought I was on ASRG, not IETF.  Too much blood in my 
caffeine stream....

-- 
David J. Aronson, Unemployed Software Engineer near Washington DC
See http://destined.to/program/ for online resume, and other info




From owner-ietf@ietf.org  Fri May 30 10:10:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08846
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 10:10:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lk59-0006UX-IZ
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 09:38:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LafW-00053Z-0j
	for ietf@asgard.ietf.org; Thu, 29 May 2003 23:35:02 -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 XAA06944
	for <ietf@ietf.org>; Thu, 29 May 2003 23:34:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ladt-0006wh-00
	for ietf@ietf.org; Thu, 29 May 2003 23:33:21 -0400
Received: from aharp.is-net.depaul.edu ([140.192.91.90])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lads-0006we-00
	for ietf@ietf.org; Thu, 29 May 2003 23:33:20 -0400
Received: (from jtk@localhost)
	by aharp.is-net.depaul.edu (8.9.3/8.9.3) id WAA21333
	for ietf@ietf.org; Thu, 29 May 2003 22:34:27 -0500
Date: Thu, 29 May 2003 22:34:27 -0500
From: John Kristoff <jtk@depaul.edu>
To: ietf@ietf.org
Subject: Re: A peer-to-peer trust system model
Message-ID: <20030530033427.GA20903@aharp.is-net.depaul.edu>
References: <DAC3FCB50E31C54987CD10797DA511BA036BE50E@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com> <3ED50675.72DA7BFC@earthlink.net> <20030529162010.GB815@think> <3ED6A7A7.8050207@centive.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3ED6A7A7.8050207@centive.com>
User-Agent: Mutt/1.3.25i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, May 29, 2003 at 08:36:55PM -0400, John Stracke wrote:
> >someone who is sending me a human generated
> >message can generally easily afford the 2 minutes worth of CPU time
> >before their mailers can deliver the message to my mail host.)
> > 
> >
> But what CPU? The machines with which I routinely send mail range from a 
> 200MHz handheld to a 2GHz*2 desktop.  I would be unhappy with a protocol 
> that required me to run my handheld's CPU at full speed for 2 minutes 
> (the battery life isn't so hot); but that level of hashcash would 

Rather than actually force the remote CPU be run for 2 minutes, the
receiving SMTP host can force the TCP window to 0 for 2 minutes.  This
could be coupled with a RBL list, but instead of a blackhole, it would
be more like a realtime pushback list (RPL), which has some nice
properties of punishing known abusers, but not causing complete
collateral damage to innocent parties.

John





From owner-ietf@ietf.org  Fri May 30 10:17:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09607
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 10:17:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LkIG-0006vT-WA
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 09:51:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LjgO-0001a5-1E
	for ietf@asgard.ietf.org; Fri, 30 May 2003 09:12:32 -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 JAA05222
	for <ietf@ietf.org>; Fri, 30 May 2003 09:12:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ljek-000402-00
	for ietf@ietf.org; Fri, 30 May 2003 09:10:50 -0400
Received: from mail11.speakeasy.net ([216.254.0.211] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ljek-0003zz-00
	for ietf@ietf.org; Fri, 30 May 2003 09:10:50 -0400
Received: (qmail 17989 invoked from network); 30 May 2003 13:12:29 -0000
Received: from unknown (HELO 192.168.254.124) ([66.92.168.196])
          (envelope-sender <dja2003@hotpop.com>)
          by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <alh-ietf@tndh.net>; 30 May 2003 13:12:29 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: <alh-ietf@tndh.net>
Subject: crypto-spam
Date: Fri, 30 May 2003 09:14:51 -0400
User-Agent: KMail/1.5
References: <00f401c3262c$ff9b9a30$56144104@eagleswings>
In-Reply-To: <00f401c3262c$ff9b9a30$56144104@eagleswings>
Cc: "'IETF'" <ietf@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305300914.51095.dja2003@hotpop.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

"Tony Hain" <alh-ietf@tndh.net> wrote:

 TH> Mail list servers would be a problem if we only use public
 TH> key, so another part of the new system could be establishing
 TH> a symmetric key as part of subscribing to a mail list.

Or alternately, some kind of whitelisting, so that encryption is not 
necessary at all.

-- 
David J. Aronson, Unemployed Software Engineer near Washington DC
See http://destined.to/program/ for online resume, and other info




From owner-ietf@ietf.org  Fri May 30 10:18:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09731
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 10:18:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LkdH-0005Zb-DA
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 10:13:23 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LkOB-0007aR-Hf
	for ietf@asgard.ietf.org; Fri, 30 May 2003 09:57:47 -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 JAA07717
	for <ietf@ietf.org>; Fri, 30 May 2003 09:57:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LkMY-0004j6-00
	for ietf@ietf.org; Fri, 30 May 2003 09:56:06 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LkMX-0004iy-00
	for ietf@ietf.org; Fri, 30 May 2003 09:56:05 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.9/8.12.9) id h4UDvicS010563
	for ietf@ietf.org env-from <vjs>;
	Fri, 30 May 2003 07:57:44 -0600 (MDT)
Date: Fri, 30 May 2003 07:57:44 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200305301357.h4UDvicS010563@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: spam
References: <5.1.0.14.2.20030529175647.02e04bc0@127.0.0.1>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Graham Klyne <GK@ninebynine.org>

> ...
> >It is an article of faith for many people that most spam involves
> >header forgery, but no one seems to have better support than intuition
> >for that faith.
>
> This comment prompted me to do a little experimentation.  I keep all my 
> spam (except that large ones that I don't bother to download), mostly unread.
>
> It's not scientific, or very statistically significant, but I examined the 
> last 20 spam mails I received, and note that:
> ...

> This little experiment suggests to me that header forgery is a significant 
> factor in spam -- I estimate about 50% of the sample I examined.

> ...
> I don't claim all this proves anything, but I think I have cause to believe 
> forgery of email headers is involved in a significant portion of the spam I 
> receive.

The main thing your experiment proves is the compelling nature of the
article of faith.  You actually found 15% were forged, 35% might have
been, and concluded that probably 50% were.  Please understand that
I do not mean to suggest less than 50% of your sample was forged or
that forgery is not significant.  My point is that in fact you have
only what sounds like weak ("pertty sure") evidence for only the 15%.

When designing things, the first and most important requirement is
keeping track of what you know, what you suspect, and what you don't
know.  Someone I worked for 25 years ago was fond of saying "what you
don't know can hurt, but what you know that aint so can kill you."
Many spam solutions are based on the religious belief that most spam
is and must remain "forged."  Even if the first half of that religion
is true, the second half is plainly false.  Forgery is not required,
and spam solutions that stop forgery will only cause spammers that
now forge to use other tactics like registering hundreds of domain
names such as addadomainforyoutomail.com, addthisonetoo.com,
atepaintchips.com, chairwithfingersattached.com, and downinone.net.
(My notes list more than 270 other fairly recent domains of that porn
spammer.)

Why are do many spam "solutions" address only forgery?  I think there
are two main reasons.  Stopping forgery seems far easier than stopping
spam.  More important is that admitting forgery is not part of a
significant fraction of spam (your other 50%) and not a required part
of spam in general requires admitting that the spam problem exists
only because many of our own ISPs do not care enough about spam to
punish our fellow spamming customers.  Many ISPs are like UUNET/MCI,
which always dealt with spam with more wishful thinking and even bald
faced lies than its finances.  (People here may have missed the years
of obviously false statements from the UUnet abuse department spokesmen
in news.admin.net-abuse.email.  I hope bland claims of the impossibility
of examining RADIUS logs to find a reseller to hold responsible or
the technical impossibility of packet sniffers on fiber would have
been laughed out of the IETF.)

The spam problem is in a state like the dot-com stock bubble before
that collapse.  Neither problem could or can be addressed anywhere
that hype and wishful thinking is preferred to facing facts.

The IETF will design SMTPng and the world will replace SMTP with SMTPng
in fewer than 10 or 20 years, and the proof of that is HTTP needed 5
years to reach critical mass without any significant competition and
in a trivially tiny network compared to the Internet of today?
http://www.w3.org/History.html


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Fri May 30 11:05:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11914
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 11:05:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LlE8-0000ZL-IJ
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 10:51:28 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Lkoh-0007ld-US
	for ietf@asgard.ietf.org; Fri, 30 May 2003 10:25:11 -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 KAA10199
	for <ietf@ietf.org>; Fri, 30 May 2003 10:25:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lkn4-00055K-00
	for ietf@ietf.org; Fri, 30 May 2003 10:23:30 -0400
Received: from mail14.speakeasy.net ([216.254.0.214] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lkn3-00055H-00
	for ietf@ietf.org; Fri, 30 May 2003 10:23:29 -0400
Received: (qmail 25392 invoked from network); 30 May 2003 14:25:09 -0000
Received: from unknown (HELO 192.168.254.124) ([66.92.168.196])
          (envelope-sender <dja2003@hotpop.com>)
          by mail14.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <anthony@atkielski.com>; 30 May 2003 14:25:09 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: "Anthony Atkielski" <anthony@atkielski.com>
Subject: Re: spam
Date: Fri, 30 May 2003 10:27:30 -0400
User-Agent: KMail/1.5
References: <sed61b06.037@gwianameserver.sj.symbol.com> <09aa01c32679$289e09d0$0a00000a@atkielski.com>
In-Reply-To: <09aa01c32679$289e09d0$0a00000a@atkielski.com>
Cc: "IETF Discussion" <ietf@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305301027.30905.dja2003@hotpop.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

"Anthony Atkielski" <anthony@atkielski.com> wrote:

 AA> Spammers obtain e-mail addresses from Web sites, USENET,
 AA> discussion forums, and the like.  Secret strings would
 AA> not be posted to any of these, so no automated harvesting
 AA> of the strings would be possible.  Just leaving the
 AA> string in an e-mail addresses to a number of recipients
 AA> would not be a problem, because spammers would not be
 AA> intercepting such e-mails (or any e-mails, for that
 AA> matter).  As long as the string is not posted in a place
 AA> where spammers can harvest it, they won't get it.

But spammers DO sometimes subscribe to mailing lists, for the purpose of 
harvesting addresses.

-- 
David J. Aronson, Unemployed Software Engineer near Washington DC
See http://destined.to/program/ for online resume, and other info




From owner-ietf@ietf.org  Fri May 30 11:07:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12107
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 11:07:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LlE8-0000Zm-Sr
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 10:51:28 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Lkrn-0007o2-KV
	for ietf@asgard.ietf.org; Fri, 30 May 2003 10:28:23 -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 KAA10281
	for <ietf@ietf.org>; Fri, 30 May 2003 10:28:21 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LkqA-00056e-00
	for ietf@ietf.org; Fri, 30 May 2003 10:26:42 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lkq9-00056b-00
	for ietf@ietf.org; Fri, 30 May 2003 10:26:41 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h4UESKe6005244;
	Fri, 30 May 2003 10:28:20 -0400
Message-Id: <200305301428.h4UESKe6005244@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Dave Aronson <dja2003@hotpop.com>
Cc: "'IETF'" <ietf@ietf.org>
Subject: Re: crypto-spam 
In-Reply-To: Your message of "Fri, 30 May 2003 09:14:51 EDT."
             <200305300914.51095.dja2003@hotpop.com> 
References: <00f401c3262c$ff9b9a30$56144104@eagleswings>
            <200305300914.51095.dja2003@hotpop.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_986230179P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 30 May 2003 10:28:19 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_986230179P
Content-Type: text/plain; charset=us-ascii

On Fri, 30 May 2003 09:14:51 EDT, Dave Aronson said:
> "Tony Hain" <alh-ietf@tndh.net> wrote:
> 
>  TH> Mail list servers would be a problem if we only use public
>  TH> key, so another part of the new system could be establishing
>  TH> a symmetric key as part of subscribing to a mail list.
> 
> Or alternately, some kind of whitelisting, so that encryption is not 
> necessary at all.

The problem is that to be effective, the whitelisting has to happen at
your mail server, not your MUA.  And although there's at least a *chance*
of your MUA twigging onto the fact that you sent a 'subscribe' request,
it's not clear that your provider's MTA can check and auto-whitelist your
subscriptions (especially since the 'subscribe' in general does *NOT*
give a hint of what MAIL FROM: to whitelist (especially if the list
is using VERPs or similar)....

And of course, "fill out this form on a webpage" subscriptions are a near-total
loss for automagic whitelisting - which means that the provider's phone WILL
ring.. ;)

It's not clear that you can expect users to hand-whitelist correctly either,
especially if the list doesn't give you an RFC2919-style hint of what to
whitelist (and see my comment about VERPs)....

--==_Exmh_986230179P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+12qDcC3lWbTT17ARAmK3AKDtKupFEbnsq+gZeyWwjGMnmEZ1RQCeKG9x
7qWBvo0FUcAZqRq+nj/RJ0Q=
=Idf8
-----END PGP SIGNATURE-----

--==_Exmh_986230179P--



From owner-ietf@ietf.org  Fri May 30 11:11:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12386
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 11:11:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LlEC-0000fm-GZ
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 10:51:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ll8P-0000Pt-Qs
	for ietf@asgard.ietf.org; Fri, 30 May 2003 10:45:33 -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 KAA11072
	for <ietf@ietf.org>; Fri, 30 May 2003 10:45:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ll6m-0005Hy-00
	for ietf@ietf.org; Fri, 30 May 2003 10:43:52 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ll6l-0005Hv-00
	for ietf@ietf.org; Fri, 30 May 2003 10:43:51 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.9/8.12.9) id h4UEjVi8018264
	for ietf@ietf.org env-from <vjs>;
	Fri, 30 May 2003 08:45:31 -0600 (MDT)
Date: Fri, 30 May 2003 08:45:31 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200305301445.h4UEjVi8018264@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: spam
References: <1B7C2780-9290-11D7-9B54-00039388672E@muada.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> spammer spams for an entire weekend until his account is yanked,

I've picked that fragment out of context only as an example of the
larger religion that holds "most spam is forged" as an article of
faith.  If you watch much spam without religious blinders, you know
that the religion that enough ISPs care about spam is delusional.

Consider the many entries in the SPEWS, SBL, and MAPS RBL blacklists.
If accounts were yanked within a business day, then the major DNS
blacklists would be useless instead of good for stopping 40-80% of
spam with low (at least for the SBL and RBL) false positives.  If
accounts were terminated with dispatch, then by the time entries were
added to the blacklists, the spammer would already be gone.

Then there is the fact that often nothing more than pro forma account
yanking is done.  For example, if you read carefully the recent accounts
of Earthlink's efforts against the Buffalo Spammer, you might wonder
how Earthlink spent millions of dollars and months of technician and
inside lawyer time chasing and not finding the spammer, but the outside
lawyer pinned him in days.  I've heard privately of cases of large,
telco-related ISPs that could not stop a spammer known by name and
address from using stolen hundreds of credit card numbers and that
supposedly had to be told by outsiders (who were neither lawyers nor
telco experts) about 1-800 ANI, the courts, and so forth.  I trust
these oddly unsuccessful or uninformed ISP employees are doing their
best, but something smells.

That pro forma account yanking is analogous to the pro forma financial
accounting of the dot-bombs.  Until there is a real accounting, things
continue.  Until organizations like UUNet care enough about spam to
not just whine about the impossibility of determining which customer
of a reseller is a spammer and seriously consider terminating the
reseller, spam cannot be reduced by technical mechanisms.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Fri May 30 12:25:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14947
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 12:25:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LmVL-0004H6-TJ
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 12:13:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LmOf-00040O-Uj
	for ietf@asgard.ietf.org; Fri, 30 May 2003 12:06:25 -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 MAA14444
	for <ietf@ietf.org>; Fri, 30 May 2003 12:06:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LmN2-00062F-00
	for ietf@ietf.org; Fri, 30 May 2003 12:04:44 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LmN1-00062C-00
	for ietf@ietf.org; Fri, 30 May 2003 12:04:43 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h4UG75xS023359;
	Fri, 30 May 2003 18:07:05 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Fri, 30 May 2003 18:06:04 +0200
Subject: Re: spam
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <200305301445.h4UEjVi8018264@calcite.rhyolite.com>
Message-Id: <9D6291E4-92B8-11D7-9B54-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On vrijdag, mei 30, 2003, at 16:45 Europe/Amsterdam, Vernon Schryver 
wrote:

>> spammer spams for an entire weekend until his account is yanked,

> I've picked that fragment out of context only as an example of the
> larger religion that holds "most spam is forged" as an article of
> faith.

Most of it is. But that's not an incredibly interesting point: I think 
we can all agree that there is a lot of spam that is forged and there 
is a lot of spam that isn't forged. There is too much of either type.

It sometimes seems like people are saying "it's no use going after spam 
that's forged as there's always the non-forged type" but then also 
"it's no use to go after non-forged spam because spammers simply forge 
headers to get by filters". May I suggest taking logic 101 again for 
those of you who think this makes sense?

> If you watch much spam without religious blinders, you know
> that the religion that enough ISPs care about spam is delusional.

If an ISP doesn't yank the mail identity from people that spam and/or 
lets spam through from known spammers, that would be a good reason to 
require additional validation for identities used by customers of this 
ISP.




From owner-ietf@ietf.org  Fri May 30 12:42:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15844
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 12:42:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LmqU-0005HL-QN
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 12:35:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LmjR-00051P-4P
	for ietf@asgard.ietf.org; Fri, 30 May 2003 12:27:53 -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 MAA15115
	for <ietf@ietf.org>; Fri, 30 May 2003 12:27:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lmhn-0006BM-00
	for ietf@ietf.org; Fri, 30 May 2003 12:26:11 -0400
Received: from smtp011.mail.yahoo.com ([216.136.173.31])
	by ietf-mx with smtp (Exim 4.12)
	id 19Lmhm-0006BJ-00
	for ietf@ietf.org; Fri, 30 May 2003 12:26:10 -0400
Received: from 212.68.224.51.brutele.be (HELO isoc) (Tomson?Eric@212.68.224.51 with login)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 30 May 2003 16:27:50 -0000
Reply-To: <Tomson_Eric@Yahoo.fr>
From: "Tomson Eric \(Yahoo.fr\)" <Tomson_Eric@Yahoo.fr>
To: "'Anthony Atkielski'" <anthony@atkielski.com>
Cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Fri, 30 May 2003 18:27:38 +0200
Organization: Internet Society
Message-ID: <012e01c326c8$676edfa0$3500a8c0@tomson.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <09f601c3267b$02b82000$0a00000a@atkielski.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA15844

Anthony,

First, I sent my mail to the list to make public apologies for the public
insult made to John on this list.

Second, the objective of this mail was not to discredit Dean (despite his
insults), but to apologize vis-à-vis John (because of the insults made to
him).
Read my mail a bit closer, and you will discover that the main idea was not
defamation but apologies.

Finally, I said that I spoke "in the name of every honest and decent
contributor to this list".
So tell me how I should consider the fact that you don't feel concerned...

E.T.

P.S.: this having been said as a "droit de réponse", you are free to
continue this conversation privately, off the list...

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of Anthony
Atkielski
Sent: vendredi 30 mai 2003 9:14
To: IETF Discussion
Subject: Re: The utilitiy of IP is at stake here


> John,

If you are speaking only to John, why do you send your message to an entire
list?

> Since I don't think Dean "Troll" Anderson will do
> it, I would like to apologize, in the name of every
> honest and decent contributor to this list, for the
> insults made against someone that was so deeply
> involved in the development of SMTP and MIME, and
> whose contribution, reputation, and experience earned
> him the Internet Architecture Board's chair.

Your attempt to discredit someone else on the list is transparently obvious.
Why not just state your disagreement with him and leave it at that, instead
of embarking on a smear campaign?

> I feel so sorry to see how dishonest and undecent
> one can be with those who contributed to design and
> build the Internet and all related technologies
> and protocols.

See above.  A rather poor attempt to disguise defamation as nobility.

Perhaps you should simply speak for yourself, instead of presuming to speak
for others, particularly when the latter is really only a platform for
actions of questionable merit?






From owner-ietf@ietf.org  Fri May 30 12:47:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16303
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 12:47:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LmqV-0005Hz-Am
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 12:35:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LmnY-000596-9g
	for ietf@asgard.ietf.org; Fri, 30 May 2003 12:32:08 -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 MAA15264
	for <ietf@ietf.org>; Fri, 30 May 2003 12:32:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lmlu-0006DJ-00
	for ietf@ietf.org; Fri, 30 May 2003 12:30:26 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lmlu-0006DG-00
	for ietf@ietf.org; Fri, 30 May 2003 12:30:26 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 208635 for ietf@ietf.org; Fri, 30 May 2003 11:31:35 -0500
Message-ID: <3ED78783.1090909@ehsco.com>
Date: Fri, 30 May 2003 11:32:03 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: spam
References: <5.1.0.14.2.20030529175647.02e04bc0@127.0.0.1> <200305301357.h4UDvicS010563@calcite.rhyolite.com>
In-Reply-To: <200305301357.h4UDvicS010563@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/30/2003 8:57 AM Vernon Schryver wrote:

> Why are do many spam "solutions" address only forgery?  I think there 
> are two main reasons.  Stopping forgery seems far easier than stopping 
> spam.  More important is that admitting forgery is not part of a 
> significant fraction of spam (your other 50%) and not a required part 
> of spam in general requires admitting that the spam problem exists only
> because many of our own ISPs do not care enough about spam to punish
> our fellow spamming customers.  Many ISPs are like UUNET/MCI, which
> always dealt with spam with more wishful thinking and even bald faced
> lies than its finances.  (People here may have missed the years of
> obviously false statements from the UUnet abuse department spokesmen in
> news.admin.net-abuse.email.  I hope bland claims of the impossibility 
> of examining RADIUS logs to find a reseller to hold responsible or the
> technical impossibility of packet sniffers on fiber would have been
> laughed out of the IETF.)

Accountability features would (hopefully) prove useful for preventing base
forgeries, but I don't think anybody has said that would be its only
benefit. Although some spammers might stop spamming if they lose their
artificial anonymity, the real strength comes from the improved ability to
enforce rules against a known identity (the meaning of the word).

The first step in that means weakening the ability to use forgery
techniques as a shield, but that's just a start. It should also help
against some of the prevarication you describe above, since there would be
less room for waffling if recipients were able to "prove" by verifiable
transfer-path analysis that a particular node had absolutely sent some
piece of spam. This ~provability would also be useful in whatever legal
enforcement options might be available (even if it's just one of the
state-specific laws, or a private lawsuit on the part of AOL/whoever).
Another benefit would come from the ability to have better pre-transfer
filters wherever the identity information made itself available.

These are all examples of how accountability can be used as a tool to help
fight spam. Forgeries are just a part of that particular fight.

Secondarily, there is another class of user where forgeries are
problematic in their own right, which is outright impersonation and/or
fraud, and in that context the anti-forgery capabilities would stand as a
unique benefit. However, the enforcement options which were made available
to those users as a result of the accountability features would be no less
compelling to those users if forgery were attempted and caught.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Fri May 30 13:28:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17819
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 13:28:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LnDj-0000Mr-K2
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 12:59:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LmyJ-0006w9-6p
	for ietf@asgard.ietf.org; Fri, 30 May 2003 12:43:15 -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 MAA15895
	for <ietf@ietf.org>; Fri, 30 May 2003 12:43:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lmwf-0006LT-00
	for ietf@ietf.org; Fri, 30 May 2003 12:41:33 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lmwc-0006LB-00
	for ietf@ietf.org; Fri, 30 May 2003 12:41:31 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.9/8.12.9) id h4UGh2KG015237
	for ietf@ietf.org env-from <vjs>;
	Fri, 30 May 2003 10:43:02 -0600 (MDT)
Date: Fri, 30 May 2003 10:43:02 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200305301643.h4UGh2KG015237@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: spam
References: <9D6291E4-92B8-11D7-9B54-00039388672E@muada.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Iljitsch van Beijnum <iljitsch@muada.com>

> ...
> Most of it is. But that's not an incredibly interesting point: I think 
> we can all agree that there is a lot of spam that is forged and there 
> is a lot of spam that isn't forged. There is too much of either type.
>
> It sometimes seems like people are saying "it's no use going after spam 
> that's forged as there's always the non-forged type" but then also 
> "it's no use to go after non-forged spam because spammers simply forge 
> headers to get by filters". May I suggest taking logic 101 again for 
> those of you who think this makes sense?

That is a red herring.  That forgery is not a required part of spam
does not imply that stopping forged spam is useless.  However, many
people are uninterested in mechanisms that reduce their own spam loads
by less than 80%.  Few care about mechanisms that would stop only 50%,
not to mention 15%.


> > If you watch much spam without religious blinders, you know
> > that the religion that enough ISPs care about spam is delusional.
>
> If an ISP doesn't yank the mail identity from people that spam and/or 
> lets spam through from known spammers, that would be a good reason to 
> require additional validation for identities used by customers of this 
> ISP.

That is an intersting point, but only if you think that ISPs that
don't care enough about spam today to yank accounts (even of
resellers) will bother to provide any of the things that might be
called "additional validation of identities."  Otherwise, you may
as well permanently blacklist those ISPs by their IP addresses with
supplemental whitelists of your correspondents that patronize them,
and declare victory in the spam war.

Most of the anti-forgery proposals depend on ISPs doing lots expensive
work with the intended result in many cases of preventing spammers from
using the services of the ISPs that would do that work and today are
not terminating those same accounts....talk about a need for Logic 101!


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Fri May 30 13:30:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18026
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 13:30:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LnEj-0000VN-9l
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 13:00:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ln1s-0007eI-07
	for ietf@asgard.ietf.org; Fri, 30 May 2003 12:46:56 -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 MAA16198
	for <ietf@ietf.org>; Fri, 30 May 2003 12:46:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ln0E-0006Qa-00
	for ietf@ietf.org; Fri, 30 May 2003 12:45:14 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ln0D-0006QX-00
	for ietf@ietf.org; Fri, 30 May 2003 12:45:13 -0400
Received: from [63.202.92.152] (adsl-63-202-92-152.dsl.snfc21.pacbell.net [63.202.92.152])
	(authenticated bits=0)
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h4UGkpAG038973
	for <ietf@ietf.org>; Fri, 30 May 2003 09:46:52 -0700 (PDT)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05210603bafd388cbb49@[63.202.92.152]>
In-Reply-To: <115140380105.20030529233617@brandenburg.com>
References: <00e901c3261b$a3dbcf50$56144104@eagleswings>
 <127103972754.20030529132930@brandenburg.com>
 <3ED699EB.8090005@ehsco.com> <115140380105.20030529233617@brandenburg.com>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Fri, 30 May 2003 09:45:53 -0700
To: ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: The utilitiy of IP is at stake here
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 11:36 PM -0700 5/29/03, Dave Crocker wrote:
>The POP->IMAP example is excellent, since it really demonstrates my
>point. IMAP is rather popular in some local area network environments.
>However it's long history has failed utterly to seriously displace POP
>on a global scale.

Exactly right. The benefits of IMAP are obvious to everyone who has 
looked at it in any depth, and yet it is very thinly deployed. The 
main reason: the perceived additional administrative overhead.

>EAH> Large-scale mail carriers would probably switch quickly if
>EAH> the accountability feature proved useful,
>
>and now we are back to hypothesizing about the behaviors of
>mega-corporations with massive installed bases and a rather poor history
>of adopting changes from the IETF community.

So far on this thread, we have heard from none of the "large-scale 
mail carriers", although we have heard that the spam problem is 
costing them millions of dollars a year. That should be a clue to the 
IETF list. If there is a problem that is affecting a company to the 
tune of millions of dollars a year, and that company thinks that the 
problem could be solved, they would spend that much money to solve 
it. Please note that they aren't.

I have spoken to some of these heavily-affected companies (instead of 
just hypothesizing about them). Their answers were all the same: they 
don't believe the problem is solvable for the amount of money that 
they are losing. They would love to solve the spam problem: not only 
would doing so save them money, it would get them new income. Some 
estimate this potential income to be hundreds of millions of dollars 
a year, much more than they are losing on spam. But they believe that 
the overhead of the needed trust system, and the cost of losing mail 
that didn't go through the trust system, is simply too high.

You might disagree with them, and based on that disagreement you 
might write a protocol. But don't do so saying "the big carriers will 
want this" without much more concrete evidence as to their desires.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Fri May 30 13:43:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18499
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 13:43:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lnhj-0003NH-4b
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 13:30:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LnF0-0000ZB-9R
	for ietf@asgard.ietf.org; Fri, 30 May 2003 13:00:30 -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 NAA16886
	for <ietf@ietf.org>; Fri, 30 May 2003 13:00:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LnDM-0006au-00
	for ietf@ietf.org; Fri, 30 May 2003 12:58:48 -0400
Received: from aragorn.bbn.com ([128.33.0.62])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LnDH-0006aY-00
	for ietf@ietf.org; Fri, 30 May 2003 12:58:43 -0400
Received: from [128.89.88.34] (comsec.bbn.com [128.89.88.34])
	by aragorn.bbn.com (8.12.7/8.12.7) with ESMTP id h4UGxWD9026251;
	Fri, 30 May 2003 12:59:32 -0400 (EDT)
Mime-Version: 1.0
X-Sender: kent@po2.bbn.com
Message-Id: <p05100306bafd3c440103@[128.89.88.34]>
In-Reply-To: <v04220802bafb769cd6b7@[192.168.1.14]>
References: <114782448.1054159586@p3.JCK.COM> <g3fzmytgm3.fsf@sa.vix.com>
 <v04220802bafb769cd6b7@[192.168.1.14]>
Date: Fri, 30 May 2003 12:52:01 -0400
To: Einar Stefferud <Steflist@thor.nma.com>
From: Stephen Kent <kent@bbn.com>
Subject: Re: requiring payment (was spam)
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
Sender: owner-ietf@ietf.org
Precedence: bulk

At 1:36 AM -0700 5/29/03, Einar Stefferud wrote:
>I suggest that those who wish to more fully understand all this 
>trust stuff might find it useful to look at http://mcg.org.br/.
>
>Cheers...\Stef
>
>

I would recommend this web site only to folks who want to see a very 
narrow view of what trust and certification are about, a view not 
consistent with most standards in the PKI arena, and one not shared 
by most legal experts, ...

Steve



From owner-ietf@ietf.org  Fri May 30 13:47:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18698
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 13:47:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lnhj-0003Oc-Kq
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 13:30:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LnJk-0001IU-H2
	for ietf@asgard.ietf.org; Fri, 30 May 2003 13:05:24 -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 NAA17079
	for <ietf@ietf.org>; Fri, 30 May 2003 13:05:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LnI6-0006eH-00
	for ietf@ietf.org; Fri, 30 May 2003 13:03:42 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LnI1-0006dM-00
	for ietf@ietf.org; Fri, 30 May 2003 13:03:41 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.9/8.12.9) id h4UH52EF020008
	for ietf@ietf.org env-from <vjs>;
	Fri, 30 May 2003 11:05:02 -0600 (MDT)
Date: Fri, 30 May 2003 11:05:02 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200305301705.h4UH52EF020008@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: spam
References: <3ED78783.1090909@ehsco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: "Eric A. Hall" <ehall@ehsco.com>

> ...
> Accountability features would (hopefully) prove useful for preventing base
> forgeries, but I don't think anybody has said that would be its only
> benefit. Although some spammers might stop spamming if they lose their
> artificial anonymity, the real strength comes from the improved ability to
> enforce rules against a known identity (the meaning of the word).

None of the even slightly plausible anti-forgery proposals have even
the slightest believable effects toward enforcing the use of known
identities.  No anti-forgery proposal has included anything that would
inconvenience a spammer that wants 10,000 "known identities."  No
price on certificates or any other mechanism can be low enough to be
tolerable by users but high enough to determine that the next new
account an ISP sees is not a known spammer with a new name, adresses,
and valid credit card number.

> The first step in that means weakening the ability to use forgery
> techniques as a shield, but that's just a start. It should also help
> against some of the prevarication you describe above, since there would be
> less room for waffling if recipients were able to "prove" by verifiable
> transfer-path analysis that a particular node had absolutely sent some
> piece of spam.  ...

That should sound like the mistake it is in a more or less technical
setting like this.  There has never been any lack of a "verifiable
transfer-path analysis that a particular node had absolutely sent some
piece of spam" unless you believe that spammers use initial sequence
number prediction to forge IP addresses.  You always know the IP
address of the SMTP client, even if it is a relay or proxy.  ISPs
could and should hold operators of open relays and proxies accountable
for sending the spam their systems send.


> Secondarily, there is another class of user where forgeries are
> problematic in their own right, which is outright impersonation and/or
> fraud, and in that context the anti-forgery capabilities would stand as a
> unique benefit. However, the enforcement options which were made available
> to those users as a result of the accountability features would be no less
> compelling to those users if forgery were attempted and caught.

Please point out a single such case where header forgery was not obvious
and that needed or could have used any extra machinery.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Fri May 30 13:48:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18779
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 13:48:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lnhk-0003Q9-Dt
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 13:30:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LnMz-0001x8-Gn
	for ietf@asgard.ietf.org; Fri, 30 May 2003 13:08:45 -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 NAA17283
	for <ietf@ietf.org>; Fri, 30 May 2003 13:08:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LnLL-0006iJ-00
	for ietf@ietf.org; Fri, 30 May 2003 13:07:03 -0400
Received: from mailgate1b.savvis.net ([216.91.182.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LnLJ-0006h3-00
	for ietf@ietf.org; Fri, 30 May 2003 13:07:02 -0400
Received: from sl6exch3.savvis.ad.savvis.net (sl6exch3.it.savvis.net [10.12.134.21])
	by mailgate1b.savvis.net (8.12.9/8.12.1) with ESMTP id h4UH7fvR024833
	for <ietf@ietf.org>; Fri, 30 May 2003 12:07:42 -0500
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Subject: RE: The utilitiy of ietf@ietf.org is at stake here
Date: Fri, 30 May 2003 12:07:42 -0500
Message-ID: <51909D9AC2941E4F9D35B264D12CD7C2590D1F@sl6exch3.savvis.ad.savvis.net>
Thread-Topic: The utilitiy of IP is at stake here
Thread-Index: AcMmS50ck17hwB5tSQ2d84zujhX+5AAe4YFg
From: "Schliesser, Benson" <benson.schliesser@Savvis.net>
To: <ietf@ietf.org>
X-ECS-MailScanner: No virus is found
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA18779

This is an important topic. However, it's crossed a certain traffic threshold, to where I would vote to see it moved to a more appropriate forum than the IETF general discussion list...



From owner-ietf@ietf.org  Fri May 30 14:08:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19313
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 14:08:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lo1r-0005QU-Po
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 13:50:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Lniv-0003pO-2O
	for ietf@asgard.ietf.org; Fri, 30 May 2003 13:31:25 -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 NAA18071
	for <ietf@ietf.org>; Fri, 30 May 2003 13:31:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LnhH-0006ta-00
	for ietf@ietf.org; Fri, 30 May 2003 13:29:43 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LnhG-0006tW-00
	for ietf@ietf.org; Fri, 30 May 2003 13:29:42 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S29A89> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Fri, 30 May 2003 10:31:21 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'IETF'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Fri, 30 May 2003 10:31:18 -0700
Message-ID: <000a01c326d1$47cddd00$56144104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <115140380105.20030529233617@brandenburg.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA19313

Dave Crocker wrote:
> The POP->IMAP example is excellent, since it really
> demonstrates my point. IMAP is rather popular in some local 
> area network environments. However it's long history has 
> failed utterly to seriously displace POP on a global scale.

Could that be because from the end user perspective IMAP doesn't provide
any clear value over POP? Isn't IMAP all about shifting control of the
mail store from the end user into the hands of the mail administrator? I
would claim this lack of clear value to the end user is not a valid
basis for arguing that people won't move, but it is one for arguing that
people need to know what they are getting in return for the effort.

> 
> 
> EAH> Large-scale mail carriers would probably switch quickly if the
> EAH> accountability feature proved useful,
> 
> and now we are back to hypothesizing about the behaviors of
> mega-corporations with massive installed bases and a rather 
> poor history of adopting changes from the IETF community.
> 
> Seriously folks, if discussion about changes is going to be
> productive, it needs to pay much more realistic attention to 
> history and pragmatics of ISP operations and average-user preferences.

We agree, the IETF has a very poor history of doing this. As much as
people hate requirements documents, their purpose is to get the
engineering team all focused on solving the same problem. Unfortunately
the few times there are requirements docs the IETF has a history of
discounting the needs of the end user or network operator, while it
places a premium on minimizing developer effort. In general the end user
doesn't care how elegant a protocol is (they never even know it exists),
they just care that the app works as advertised and accomplishes the
task they need done. When elegance reduces cost, they will gravitate
that way, but when it increases cost they will avoid it. Network
operators care more about the labor involved (in engineering time to
keep up with scale, and operator understanding) as that usually
dominates their costs. Elegant protocols mean nothing unless they lead
to improved service, reduced labor, or preferably both. 

The IETF is in a difficult spot, because the customer of the IETF is the
vendor developer (in the generic sense of vendor as producer of things
used by someone else). Yet it is the customer of those vendors that
ultimately decide the value of the work and its deployability. If the
vendors do a good job of translating the protocol work into products
that meed a need, and market them well, the result will be deployed.
When not, we get cases like IMAP where there may be value, but the end
user doesn't know what it is.

In any case, the end user would know the value in a different mail tool
that made it possible to recover the cost of their time in dealing with
spam. By Joe-sixpack math, at 10 spam items per day and $100 potential
compensation, even after taxes that is $1/4M per year (tell me the
masses wouldn't switch with that kind of motivation). The lame spammer
that only gets out 10k messages per day would be facing $1M /day in
judgments. Politicians will sit up and take notice when cumulative
judgments across borders quickly reach the $1B range. We don't need
complex micro-payments to provide financial feedback. What we need is a
way for existing legal mechanisms to clearly nail down the originator.
Personally I think we could help law enforcement by providing the
lat/long of the source server on something like a 6.4m resolution, but I
am slightly biased about that approach.

Tony




From owner-ietf@ietf.org  Fri May 30 14:09:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19379
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 14:09:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lo1t-0005VX-23
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 13:51:01 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LnwO-0004ai-8g
	for ietf@asgard.ietf.org; Fri, 30 May 2003 13:45:20 -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 NAA18629
	for <ietf@ietf.org>; Fri, 30 May 2003 13:45:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lnuk-00072H-00
	for ietf@ietf.org; Fri, 30 May 2003 13:43:38 -0400
Received: from out002pub.verizon.net ([206.46.170.141] helo=out002.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lnuj-00071z-00
	for ietf@ietf.org; Fri, 30 May 2003 13:43:38 -0400
Received: from earthlink.net ([4.65.81.213]) by out002.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030530174447.ITBP13328.out002.verizon.net@earthlink.net>;
          Fri, 30 May 2003 12:44:47 -0500
Message-ID: <3ED79782.195F1A20@earthlink.net>
Date: Fri, 30 May 2003 10:40:18 -0700
From: Peter Deutsch <pdeutsch@earthlink.net>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Paul Hoffman / IMC <phoffman@imc.org>
CC: ietf@ietf.org
Subject: Re: The utilitiy of IP is at stake here
References: <00e901c3261b$a3dbcf50$56144104@eagleswings>
	 <127103972754.20030529132930@brandenburg.com>
	 <3ED699EB.8090005@ehsco.com> <115140380105.20030529233617@brandenburg.com> <p05210603bafd388cbb49@[63.202.92.152]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out002.verizon.net from [4.65.81.213] at Fri, 30 May 2003 12:44:47 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Paul Hoffman / IMC wrote:
...
> So far on this thread, we have heard from none of the "large-scale
> mail carriers", although we have heard that the spam problem is
> costing them millions of dollars a year. That should be a clue to the
> IETF list. If there is a problem that is affecting a company to the
> tune of millions of dollars a year, and that company thinks that the
> problem could be solved, they would spend that much money to solve
> it. Please note that they aren't.

Well, perhaps it's more accurate to say "if they thought it could be
solved by working with all those nice and entusiastic folks on the IETF
general discussion list"... ;-)



> I have spoken to some of these heavily-affected companies (instead of
> just hypothesizing about them). Their answers were all the same: they
> don't believe the problem is solvable for the amount of money that
> they are losing. They would love to solve the spam problem: not only
> would doing so save them money, it would get them new income. Some
> estimate this potential income to be hundreds of millions of dollars
> a year, much more than they are losing on spam. But they believe that
> the overhead of the needed trust system, and the cost of losing mail
> that didn't go through the trust system, is simply too high.
> 
> You might disagree with them, and based on that disagreement you
> might write a protocol. But don't do so saying "the big carriers will
> want this" without much more concrete evidence as to their desires.

Paul, are you aware of any concrete numbers here? I've looked through
the IMC site, but the only references to cost seem to be in a report
from the late 90's, with no hard data. If not, this might be something
the IMC could consider pulling together? I'd agree that there's way too
much hand-waving going on here on this point...


				- peterd

-- 
---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software

    "Angels fly because they take themselves so lightly"

                                   - G.K. Chesterton  
---------------------------------------------------------------------



From owner-ietf@ietf.org  Fri May 30 14:19:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19926
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 14:19:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LoKQ-0006lZ-1E
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 14:10:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Lo2l-0005Zv-Q9
	for ietf@asgard.ietf.org; Fri, 30 May 2003 13:51:55 -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 NAA19021
	for <ietf@ietf.org>; Fri, 30 May 2003 13:51:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lo18-00079a-00
	for ietf@ietf.org; Fri, 30 May 2003 13:50:14 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lo17-00079X-00
	for ietf@ietf.org; Fri, 30 May 2003 13:50:13 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 208658 for ietf@ietf.org; Fri, 30 May 2003 12:51:23 -0500
Message-ID: <3ED79A37.9020400@ehsco.com>
Date: Fri, 30 May 2003 12:51:51 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: spam
References: <9D6291E4-92B8-11D7-9B54-00039388672E@muada.com> <200305301643.h4UGh2KG015237@calcite.rhyolite.com>
In-Reply-To: <200305301643.h4UGh2KG015237@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/30/2003 11:43 AM Vernon Schryver wrote:

> That is an intersting point, but only if you think that ISPs that
> don't care enough about spam today to yank accounts (even of
> resellers) will bother to provide any of the things that might be
> called "additional validation of identities."  Otherwise, you may
> as well permanently blacklist those ISPs by their IP addresses with
> supplemental whitelists of your correspondents that patronize them,
> and declare victory in the spam war.

I do that already. Trace information would let me do it sooner, and with
greater precision. Also, I can be more selective in my blocks, rather than
having to block entire countries (not all of whom are in Greater Asia)
because some ISPs have multiple netblocks or move around frequently. In
this regard, being able to identify an idiot ISP gives me finer-grained
control over that idiot's access to my network.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Fri May 30 14:30:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20362
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 14:30:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LoKR-0006oy-9v
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 14:10:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LoJu-0006XN-0h
	for ietf@asgard.ietf.org; Fri, 30 May 2003 14:09:38 -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 OAA19455
	for <ietf@ietf.org>; Fri, 30 May 2003 14:09:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LoIG-0007Gt-00
	for ietf@ietf.org; Fri, 30 May 2003 14:07:56 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LoIF-0007Gg-00
	for ietf@ietf.org; Fri, 30 May 2003 14:07:55 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S29A9A> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Fri, 30 May 2003 11:09:33 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Fri, 30 May 2003 11:09:30 -0700
Message-ID: <001a01c326d6$9dfe6e60$56144104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <p05210603bafd388cbb49@[63.202.92.152]>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA20362

Paul Hoffman wrote:
> So far on this thread, we have heard from none of the "large-scale 
> mail carriers", although we have heard that the spam problem is 
> costing them millions of dollars a year. That should be a clue to the 
> IETF list. If there is a problem that is affecting a company to the 
> tune of millions of dollars a year, and that company thinks that the 
> problem could be solved, they would spend that much money to solve 
> it. Please note that they aren't.

And that would be because they can't do it in isolation. They need a
system wide standard everyone is building to, to make your argument
below about cost of untrusted mail moot.

> 
> I have spoken to some of these heavily-affected companies (instead of 
> just hypothesizing about them). Their answers were all the same: they 
> don't believe the problem is solvable for the amount of money that 
> they are losing. They would love to solve the spam problem: not only 
> would doing so save them money, it would get them new income. Some 
> estimate this potential income to be hundreds of millions of dollars 
> a year, much more than they are losing on spam. But they believe that 
> the overhead of the needed trust system, and the cost of losing mail 
> that didn't go through the trust system, is simply too high.

We agree the trust infrastructure has to provide as much or more value
than it costs. The reason they are concerned about the cost of loosing
untrusted mail stems from the deployment in isolation scenario. Provide
a standard that has appropriate value for cost, define it to run in
parallel so nothing is lost, and deployment will happen.

Taken another way, how would the IETF react if the large carriers
decided to go off and solve this problem amongst themselves with an
undocumented protocol? I predict there would be an outcry that the big
players were ignoring standards and bullying the market place. If the
IETF continues to consider it a research project, their hand will be
forced to take some action and the result might not be in the IETF's
favor. 

That was somewhat the point of the thread subject, in that they are
already feeling the pressure and taking action which reduces the utility
of ranges of IP addresses. 

> 
> You might disagree with them, and based on that disagreement you 
> might write a protocol. But don't do so saying "the big carriers will 
> want this" without much more concrete evidence as to their desires.

The real cost is not in the big carrier equipment or engineering, it is
in the millions of person hours per day lost to configuring filters,
waiting for the delivery of what gets past the filters, and hitting
delete ~100 times. Yes there is cost in the middle, but it is minor in
comparison, and will likely be comparable or slightly higher to run the
proposed trusted mail system. The question is, will the value of that
approach outweigh the cost? Obviously I suspect it will. YMMV ...

Tony 







From owner-ietf@ietf.org  Fri May 30 14:32:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20569
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 14:32:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Loc4-0007XZ-Tm
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 14:28:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LoMk-0006qc-0y
	for ietf@asgard.ietf.org; Fri, 30 May 2003 14:12:34 -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 OAA19667
	for <ietf@ietf.org>; Fri, 30 May 2003 14:12:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LoL6-0007Ku-00
	for ietf@ietf.org; Fri, 30 May 2003 14:10:52 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LoL5-0007KZ-00
	for ietf@ietf.org; Fri, 30 May 2003 14:10:51 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id OAA00924;
	Fri, 30 May 2003 14:08:05 -0400
Date: Fri, 30 May 2003 14:09:11 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: "Tomson Eric (Yahoo.fr)" <Tomson_Eric@Yahoo.fr>
cc: "'Anthony Atkielski'" <anthony@atkielski.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
In-Reply-To: <012e01c326c8$676edfa0$3500a8c0@tomson.be>
Message-ID: <Pine.LNX.4.44.0305301340250.17819-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by ietf.org id OAA20569

Well, John has not been insulted.

You seem to take issue with section:

=================
> > This problem was been fixed around 1993.. It is not possible
> > to send anonymous email through an open relay. (you still hear
> > this from radical antispammers, though).
>
> If sufficient logging information is maintained, it is not
> possible to send mail through a relay (open or not) without
> identifying the IP address of the sender (that statement was
> true before and after the changes you identify as "around
> 1993").  Getting from that IP address to identification of the
> individual sender --which is what you presumably mean by "not
> anonymous"-- is more or less difficult and more or less
> expensive, depending on a number of other circumstances.   In
> some cases --and, again, if one believes that people's time has
> any value-- the practical costs of identifying an individual far
> exceed any possible value in doing so.  In some others, it may
> be nearly impossible.   For example, there is a well-known Asian
> country in which most of the dialup services appear to be
> freenets, with widely-available dialup numbers and passwords
> shared among, I believe, literally millions of people.  The mail
> relays on those systems have no way to determine which user is
> originating a piece of mail, the user's IP address is of no
> help, and a system receiving mail from one of those relays can
> only identify the relay host.  That is a pretty good
> approximation to anonymity in my book.

This is just nonsense.  Obviously, you have no operational experience.
=================

It is nonsense because "sufficient logging information" has no bearing on
whether is possible to send email through an (open or not) relay without
identifying the IP address of the sender. This IP address is in the
'Recieved:' header, and cannot be altered or removed by the sender.

It is nonsense because the prior anonymity of a user because of shared
passwords by an asian dialup has no bearing on whether open relays are
anonymous. The property of a users anonymity isn't changed by SMTP, as is
wrongly asserted. It is irrelevant whether an ISP in asia doesn't have
accounting records for their users and shares passwords.

So, my statement is correct.  It is nonsense.

And John has obviously never been involved in a Law Enforcement request.
But I have.  Private emails to him seem to confirm this, or at least he
didn't indicate anything to the contrary.  While he may have been working
on SMTP protocols for 30 years, he obviously hasn't been involved in
trackig abuse of various sorts, and has no idea of whether this is
expensive or difficult.

Here is a Law Enforcement request I can relate:  Shortly after Genuity
took their national VOIP service into production, some kid used a
customer's free PC-to-phone service to phone in a bomb threat to a school.
Law Enforcement called the phone company, which traced the PSTN call back
to a CLEC. A call to the CLEC identified Genuity. Genuity operations staff
called me, because they were still somewhat untrained with the integrated
Radius/accounting system for which I was a significant contributing
engineer. They knew how to keep it running, but did not know the queries
to find certain kinds of information.

I explained how to get what they needed to know. They quickly identifed an
IP address belonging to a Genuity (retail VOIP) customer. That customer
used a gateway to relay the call from their customer to Genuity. I believe
that they then got a call from Law Enforcement, and they then identified a
residential ISP, which then identified the original user. Who was quickly
arrested.

This all happened fairly quickly. It is not expensive, as John wrongly
seems to think. And the process has nothing whatsoever to do with SMTP.
In the case of an open relay abuse, the IP of the abuser is quickly and
easily found*. More more easily than in the case above.

*Unless of course, they have an ISP that doesn't keep track of
users--which isn't a fault of open relay.  As was pointed out to John,
SMTP AUTH doesn't alter this situtation in the least.


On Fri, 30 May 2003, Tomson Eric (Yahoo.fr) wrote:

> Anthony,
>
> First, I sent my mail to the list to make public apologies for the public
> insult made to John on this list.
>
> Second, the objective of this mail was not to discredit Dean (despite his
> insults), but to apologize vis-à-vis John (because of the insults made to
> him).
> Read my mail a bit closer, and you will discover that the main idea was not
> defamation but apologies.
>
> Finally, I said that I spoke "in the name of every honest and decent
> contributor to this list".
> So tell me how I should consider the fact that you don't feel concerned...
>
> E.T.
>
> P.S.: this having been said as a "droit de réponse", you are free to
> continue this conversation privately, off the list...
>
> -----Original Message-----
> From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of Anthony
> Atkielski
> Sent: vendredi 30 mai 2003 9:14
> To: IETF Discussion
> Subject: Re: The utilitiy of IP is at stake here
>
>
> > John,
>
> If you are speaking only to John, why do you send your message to an entire
> list?
>
> > Since I don't think Dean "Troll" Anderson will do
> > it, I would like to apologize, in the name of every
> > honest and decent contributor to this list, for the
> > insults made against someone that was so deeply
> > involved in the development of SMTP and MIME, and
> > whose contribution, reputation, and experience earned
> > him the Internet Architecture Board's chair.
>
> Your attempt to discredit someone else on the list is transparently obvious.
> Why not just state your disagreement with him and leave it at that, instead
> of embarking on a smear campaign?
>
> > I feel so sorry to see how dishonest and undecent
> > one can be with those who contributed to design and
> > build the Internet and all related technologies
> > and protocols.
>
> See above.  A rather poor attempt to disguise defamation as nobility.
>
> Perhaps you should simply speak for yourself, instead of presuming to speak
> for others, particularly when the latter is really only a platform for
> actions of questionable merit?
>
>
>
>
>






From owner-ietf@ietf.org  Fri May 30 14:43:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20929
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 14:43:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Loc5-0007YG-A8
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 14:28:25 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LoRd-0006xz-LL
	for ietf@asgard.ietf.org; Fri, 30 May 2003 14:17:37 -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 OAA19891
	for <ietf@ietf.org>; Fri, 30 May 2003 14:17:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LoPz-0007P0-00
	for ietf@ietf.org; Fri, 30 May 2003 14:15:56 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LoPz-0007Ox-00
	for ietf@ietf.org; Fri, 30 May 2003 14:15:55 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 208669 for ietf@ietf.org; Fri, 30 May 2003 13:17:04 -0500
Message-ID: <3ED7A03C.1040603@ehsco.com>
Date: Fri, 30 May 2003 13:17:32 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: The utilitiy of IP is at stake here
References: <00e901c3261b$a3dbcf50$56144104@eagleswings> <127103972754.20030529132930@brandenburg.com> <3ED699EB.8090005@ehsco.com> <115140380105.20030529233617@brandenburg.com> <p05210603bafd388cbb49@[63.202.92.152]>
In-Reply-To: <p05210603bafd388cbb49@[63.202.92.152]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/30/2003 11:45 AM Paul Hoffman / IMC wrote:

> So far on this thread, we have heard from none of the "large-scale 
> mail carriers", although we have heard that the spam problem is 
> costing them millions of dollars a year. That should be a clue to the 
> IETF list. If there is a problem that is affecting a company to the 
> tune of millions of dollars a year, and that company thinks that the 
> problem could be solved, they would spend that much money to solve 
> it. Please note that they aren't.

http://www.nytimes.com/2003/05/25/business/yourmoney/25SPAM.html?pagewanted=3
leads with the question "Microsoft has spent more than a half-billion
dollars trying to build software to filter out spam. Why isn't that good
enough?" Note that the responder doesn't challenge the amount.

> I have spoken to some of these heavily-affected companies (instead of 
> just hypothesizing about them). Their answers were all the same: they 
> don't believe the problem is solvable for the amount of money that 
> they are losing. They would love to solve the spam problem: not only 
> would doing so save them money, it would get them new income. Some 
> estimate this potential income to be hundreds of millions of dollars 
> a year, much more than they are losing on spam. But they believe that 
> the overhead of the needed trust system, and the cost of losing mail 
> that didn't go through the trust system, is simply too high.

http://www.infoworld.com/article/03/05/30/HNmsspam_1.html demonstrates
that at least some of the large mailers still beleive there is a problem
worth addressing, and that they are continuing to spend towards solving
the problem.

There's no need to hypothesize about much of this. There is a problem,
obviously. Some of the specific approaches have proven to be untenable
(many of the approaches which were discussed here have been tried and
apparently rejected as part of the Black Penny Project for example). I
think it's equally obvious that companies are spending massive amounts of
money to try and solve this problem (assuming we agree that $500 million
from one company qualifies as "massive"), and that they are continuing to
pursue those solutions which are probably the most viable for their
peculiar situations.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Fri May 30 14:57:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21492
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 14:57:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Losy-0000fn-OA
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 14:45:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Lofu-00084W-CD
	for ietf@asgard.ietf.org; Fri, 30 May 2003 14:32:22 -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 OAA20552
	for <ietf@ietf.org>; Fri, 30 May 2003 14:32:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LoeG-0007ap-00
	for ietf@ietf.org; Fri, 30 May 2003 14:30:40 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LoeF-0007am-00
	for ietf@ietf.org; Fri, 30 May 2003 14:30:40 -0400
Received: from [63.202.92.152] (adsl-63-202-92-152.dsl.snfc21.pacbell.net [63.202.92.152])
	(authenticated bits=0)
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h4UIWGAI044938
	for <ietf@ietf.org>; Fri, 30 May 2003 11:32:18 -0700 (PDT)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05210607bafd52b3d9b3@[63.202.92.152]>
In-Reply-To: <3ED79782.195F1A20@earthlink.net>
References: <00e901c3261b$a3dbcf50$56144104@eagleswings>	
 <127103972754.20030529132930@brandenburg.com>	
 <3ED699EB.8090005@ehsco.com>
 <115140380105.20030529233617@brandenburg.com>
 <p05210603bafd388cbb49@[63.202.92.152]> <3ED79782.195F1A20@earthlink.net>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Fri, 30 May 2003 11:32:15 -0700
To: ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: The utilitiy of IP is at stake here
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 10:40 AM -0700 5/30/03, Peter Deutsch wrote:
>Paul Hoffman / IMC wrote:
>...
>>  So far on this thread, we have heard from none of the "large-scale
>>  mail carriers", although we have heard that the spam problem is
>>  costing them millions of dollars a year. That should be a clue to the
>>  IETF list. If there is a problem that is affecting a company to the
>>  tune of millions of dollars a year, and that company thinks that the
>>  problem could be solved, they would spend that much money to solve
>>  it. Please note that they aren't.
>
>Well, perhaps it's more accurate to say "if they thought it could be
>solved by working with all those nice and entusiastic folks on the IETF
>general discussion list"... ;-)

We disagree here. For the millions of dollars that they are losing, 
they would come up with the solution with the IETF or not. They 
haven't.

>  > I have spoken to some of these heavily-affected companies (instead of
>>  just hypothesizing about them). Their answers were all the same: they
>>  don't believe the problem is solvable for the amount of money that
>>  they are losing. They would love to solve the spam problem: not only
>>  would doing so save them money, it would get them new income. Some
>>  estimate this potential income to be hundreds of millions of dollars
>>  a year, much more than they are losing on spam. But they believe that
>>  the overhead of the needed trust system, and the cost of losing mail
>>  that didn't go through the trust system, is simply too high.
>>
>>  You might disagree with them, and based on that disagreement you
>>  might write a protocol. But don't do so saying "the big carriers will
>>  want this" without much more concrete evidence as to their desires.
>
>Paul, are you aware of any concrete numbers here?

Yes.

>  I've looked through
>the IMC site, but the only references to cost seem to be in a report
>from the late 90's, with no hard data. If not, this might be something
>the IMC could consider pulling together? I'd agree that there's way too
>much hand-waving going on here on this point...

All my discussions were not for attribution. Large mail carriers 
don't want their competitors to know how many users they actually 
have (as compared to the highly inflated numbers that various 
analysts say they have), and they certainly don't want their 
competitors knowing how much they are spending on dealing with spam. 
"Our company spends more per user on fighting spam than 
OtherBigCarrier!"

In aggregate, then numbers were in the tens of millions of dollars 
US, and that was more than two years ago. I would be shocked if the 
numbers were much lower now, given the greatly increasing amount of 
spam and the level-or-increasing number of customers.

Again, the summary is that these folks are hurting badly enough to 
throw highly-qualified full-time staff on the problem, and they don't 
believe any of the solutions that have been presented so far will 
save them enough money. If they thought differently, they would have 
deployed them by now so that they could save those millions of 
dollars.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Fri May 30 14:58:28 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21540
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 14:58:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Losz-0000iM-Jx
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 14:45:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Lonm-0000AP-DE
	for ietf@asgard.ietf.org; Fri, 30 May 2003 14:40:30 -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 OAA20876
	for <ietf@ietf.org>; Fri, 30 May 2003 14:40:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lom8-0007gM-00
	for ietf@ietf.org; Fri, 30 May 2003 14:38:48 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lom8-0007gI-00
	for ietf@ietf.org; Fri, 30 May 2003 14:38:48 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id D8E411396C; Fri, 30 May 2003 18:39:57 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Spam
References: <lHoQPzDbiz1+Ewdx@soaring.demon.co.uk>
From: Paul Vixie <vixie@vix.com>
Date: 30 May 2003 18:39:57 +0000
In-Reply-To: <lHoQPzDbiz1+Ewdx@soaring.demon.co.uk>
Message-ID: <g37k88th1e.fsf@sa.vix.com>
Lines: 40
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

ietf@soaring.demon.co.uk (Andrew Shore) writes:

> ... I found it interesting, specifically the claim that there are 180
> entities creating nearly all the spam... it would explain the recurrence
> of certain seemingly unlikely patterns across the board, but is still
> hard to credit even with that in mind.

it's absolutely true.  see the background at www.spamhaus.org for details.

however, it's also irrelevant.  bad spam has currently driven-low gray spam,
but if not for those ~200 spam gangs giving unsolicited e-mail a bad reputation
there would be 50X more unsolicited bulk e-mail coming to each of us, from
companies who don't want to be evil but who don't think our privacy is worth
as much as their revenues.  the spectre of "gray spam" from so-called legit
companies is more frightening to me even then the Windows Open Proxy Platform.

if we could put those ~200 spam gangs in jail then they would be replaced in
a month.  if we could make spamganging so illegal that they were eventually
not replaced, then their traffic would be replaced by bulk e-mail from every
customer of every CRM (customer relationship management) company in the world.

not that it's practical to even do away with the spam gangs we have now, but
what would replace them is actually worse, so let's reconsider that goal set.

as i've said here several times in the last 10 days, the problem isn't
stopping spam but enabling batched interpersonal digital communications
where the recipients are happy to have some delivery costs shifted to them
because they have some confidence in the identity of the sender, the intent
of the relay, and the value (to the sender) of the reception.

don't think negative thoughts like "how can we save smtp from the spammers"
but rather positive ones like "what batched interpersonal digital
communications system can we create that fits the full spectrum of humanity"?
smtp was for the research community, where trust was implied by reachability.
in the full spectrum of humanity, that implication is, and has always been,
provably false.

smtp cannot be saved.  let's move on.
-- 
Paul Vixie



From owner-ietf@ietf.org  Fri May 30 15:03:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21981
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 15:03:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Losz-0000is-Vq
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 14:45:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Loqh-0000NU-DJ
	for ietf@asgard.ietf.org; Fri, 30 May 2003 14:43:31 -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 OAA20961
	for <ietf@ietf.org>; Fri, 30 May 2003 14:43:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lop3-0007hn-00
	for ietf@ietf.org; Fri, 30 May 2003 14:41:49 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lop2-0007hJ-00
	for ietf@ietf.org; Fri, 30 May 2003 14:41:48 -0400
Received: from edison.cisco.com (edison.cisco.com [171.70.144.164])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h4UIgu9N017038;
	Fri, 30 May 2003 11:42:57 -0700 (PDT)
Received: from cisco.com (sjc-vpn3-790.cisco.com [10.21.67.22]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id LAA04179; Fri, 30 May 2003 11:42:56 -0700 (PDT)
Message-ID: <3ED7A62F.7080401@cisco.com>
Date: Fri, 30 May 2003 11:42:55 -0700
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Hoffman / IMC <phoffman@imc.org>
CC: ietf@ietf.org
Subject: Re: The utilitiy of IP is at stake here
References: <00e901c3261b$a3dbcf50$56144104@eagleswings> <127103972754.20030529132930@brandenburg.com> <3ED699EB.8090005@ehsco.com> <115140380105.20030529233617@brandenburg.com> <p05210603bafd388cbb49@[63.202.92.152]>
In-Reply-To: <p05210603bafd388cbb49@[63.202.92.152]>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Paul Hoffman / IMC wrote:

> At 11:36 PM -0700 5/29/03, Dave Crocker wrote:
> 
>> The POP->IMAP example is excellent, since it really demonstrates my
>> point. IMAP is rather popular in some local area network environments.
>> However it's long history has failed utterly to seriously displace POP
>> on a global scale.
> 
> 
> Exactly right. The benefits of IMAP are obvious to everyone who has 
> looked at it in any depth, and yet it is very thinly deployed. The main 
> reason: the perceived additional administrative overhead.

I think what this shows is that client and server implementations still 
do a lousy job with IMAP.  In particular, the few IMAP implementations 
I'm familiar with don't do a very good job of online/offline separation. 
  In one case, you have to modify the properties of each folder, and it 
doesn't indicate whether or not a message is downloaded.

Also, since most consumers don't use procmail, there's probably not much 
of a direct benefit to them -- yet.

Eliot





From owner-ietf@ietf.org  Fri May 30 15:07:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22549
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 15:07:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lot1-0000jR-Bn
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 14:45:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Loqv-0000Vs-8Q
	for ietf@asgard.ietf.org; Fri, 30 May 2003 14:43:45 -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 OAA20978
	for <ietf@ietf.org>; Fri, 30 May 2003 14:43:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LopH-0007iL-00
	for ietf@ietf.org; Fri, 30 May 2003 14:42:03 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LopG-0007hM-00
	for ietf@ietf.org; Fri, 30 May 2003 14:42:03 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 5740B1396D; Fri, 30 May 2003 18:43:13 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: A peer-to-peer trust system model
References: <3ED6A7A7.8050207@centive.com>
	<20030530033427.GA20903@aharp.is-net.depaul.edu>
From: Paul Vixie <vixie@vix.com>
Date: 30 May 2003 18:43:13 +0000
In-Reply-To: <20030530033427.GA20903@aharp.is-net.depaul.edu>
Message-ID: <g33ciwtgvy.fsf@sa.vix.com>
Lines: 11
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

> ..., but instead of a blackhole, it would be more like a realtime
> pushback list (RPL), which has some nice properties of punishing known
> abusers, but not causing complete collateral damage to innocent parties.

the definitions of your words "known", "abusers", and "innocent" are highly
subjective and are known to vary considerably from one recipient to the next.

y'all have got to stop trying to save smtp, and just agree to move on.  smtp
was an ivory tower thing and it isn't working well down in the fields.
-- 
Paul Vixie



From owner-ietf@ietf.org  Fri May 30 15:18:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23774
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 15:18:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LpGk-0000Gr-V2
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 15:10:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Loux-0000l5-0b
	for ietf@asgard.ietf.org; Fri, 30 May 2003 14:47:55 -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 OAA21183
	for <ietf@ietf.org>; Fri, 30 May 2003 14:47:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LotJ-0007lt-00
	for ietf@ietf.org; Fri, 30 May 2003 14:46:13 -0400
Received: from dsl092-066-067.bos1.dsl.speakeasy.net ([66.92.66.67] helo=thrintun.hactrn.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LotI-0007li-00
	for ietf@ietf.org; Fri, 30 May 2003 14:46:12 -0400
Received: from thrintun.hactrn.net (localhost [::1])
	by thrintun.hactrn.net (Postfix) with ESMTP id 2F34518F0
	for <ietf@ietf.org>; Fri, 30 May 2003 14:47:22 -0400 (EDT)
Date: Fri, 30 May 2003 14:47:22 -0400
From: Rob Austein <sra+ietf@hactrn.net>
To: ietf@ietf.org
Subject: Last 7 days on the IETF list
User-Agent: Wanderlust/2.10.0 (Venus) Emacs/20.7 Mule/4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20030530184722.2F34518F0@thrintun.hactrn.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

Traffic statistics (as seen from my cave, your milage may vary) for
the last seven days on the ietf@ietf.org mailing list.

Conclusions, if any, are left as an exercise for the reader.


  Messages   |     Bytes       | Who
-------+-----+-------+---------+------------------------
 11.4% |  53 | 13.9% |  233614 | dean@av8.com
 12.2% |  57 | 10.1% |  170963 | anthony@atkielski.com
  7.5% |  35 |  7.2% |  121074 | ehall@ehsco.com
  3.0% |  14 |  4.8% |   80253 | pdeutsch@earthlink.net
  3.9% |  18 |  3.6% |   60755 | valdis.kletnieks@vt.edu
  3.4% |  16 |  3.5% |   58293 | alh-ietf@tndh.net
  3.6% |  17 |  2.6% |   43278 | michel@arneill-py.sacramento.ca.us
  2.8% |  13 |  2.2% |   37288 | moore@cs.utk.edu
  2.4% |  11 |  2.3% |   37930 | dwm@xpasc.com
  2.1% |  10 |  2.2% |   37479 | vjs@calcite.rhyolite.com
  2.1% |  10 |  2.2% |   36561 | iljitsch@muada.com
  2.1% |  10 |  1.9% |   31676 | l.wood@eim.surrey.ac.uk
  1.9% |   9 |  1.8% |   31053 | shogunx@sleekfreak.ath.cx
  1.9% |   9 |  1.8% |   31016 | vixie@vix.com
  1.9% |   9 |  1.7% |   27856 | dhc2@dcrocker.net
  1.9% |   9 |  1.6% |   27349 | dja2003@hotpop.com
  1.9% |   9 |  1.5% |   24511 | sbwoodside@yahoo.com
  1.1% |   5 |  2.1% |   34761 | steflist@thor.nma.com
  1.7% |   8 |  1.3% |   21321 | jnc@ginger.lcs.mit.edu
  1.3% |   6 |  1.7% |   28495 | richard@shockey.us
  1.3% |   6 |  1.2% |   19636 | tomson_eric@yahoo.fr
  1.3% |   6 |  1.1% |   19259 | jstracke@centive.com
  0.9% |   4 |  1.5% |   24586 | john-ietf@jck.com
  1.1% |   5 |  1.0% |   16989 | mat@cisco.com
  0.9% |   4 |  0.9% |   15992 | avi@bridgewatersystems.com
  0.9% |   4 |  0.9% |   14418 | huitema@windows.microsoft.com
  0.9% |   4 |  0.8% |   13896 | phoffman@imc.org
  0.9% |   4 |  0.7% |   12281 | dee3@torque.pothole.com
  0.9% |   4 |  0.7% |   11323 | ietf@soaring.demon.co.uk
  0.9% |   4 |  0.7% |   11275 | tjc@ecs.soton.ac.uk
  0.6% |   3 |  0.8% |   13511 | darkuncle@darkuncle.net
  0.6% |   3 |  0.7% |   12302 | harald@alvestrand.no
  0.4% |   2 |  0.9% |   14402 | dws@hunnysoft.com
  0.4% |   2 |  0.8% |   14209 | mohta@necom830.hpcl.titech.ac.jp
  0.6% |   3 |  0.6% |   10191 | wessorh@ar.com
  0.6% |   3 |  0.6% |   10181 | rwelty@averillpark.net
  0.6% |   3 |  0.5% |    9109 | lear@cisco.com
  0.6% |   3 |  0.5% |    8328 | john.loughney@kolumbus.fi
  0.6% |   3 |  0.5% |    7803 | sommerfeld@orchard.arlington.ma.us
  0.6% |   3 |  0.5% |    7584 | billc44@citynet.net
  0.6% |   3 |  0.4% |    6866 | randy@psg.com
  0.2% |   1 |  0.8% |   13680 | soohong.park@samsung.com
  0.4% |   2 |  0.5% |    8935 | stephen@sprunk.org
  0.4% |   2 |  0.5% |    7722 | tytso@mit.edu
  0.4% |   2 |  0.5% |    7620 | rra@stanford.edu
  0.4% |   2 |  0.4% |    6916 | jmorris@cdt.org
  0.4% |   2 |  0.4% |    6630 | dank@hq.lindsayelec.com
  0.4% |   2 |  0.4% |    6470 | dominic.pinto@ieee.org
  0.4% |   2 |  0.4% |    6156 | zefram@fysh.org
  0.2% |   1 |  0.6% |    9711 | awduche@awduche.com
  0.4% |   2 |  0.3% |    5077 | bmanning@isi.edu
  0.4% |   2 |  0.3% |    4924 | fritz_saad@hotmail.com
  0.4% |   2 |  0.3% |    4618 | ekr@rtfm.com
  0.4% |   2 |  0.3% |    4576 | cdel@firsthand.net
  0.4% |   2 |  0.3% |    4438 | anewton@ecotroph.net
  0.4% |   2 |  0.3% |    4335 | garmitage@swin.edu.au
  0.2% |   1 |  0.5% |    7750 | alain.durand@sun.com
  0.2% |   1 |  0.4% |    7195 | dws+001@hunnysoft.com
  0.2% |   1 |  0.4% |    6953 | bob@wyman.us
  0.2% |   1 |  0.4% |    6315 | ggm@apnic.net
  0.2% |   1 |  0.4% |    6293 | et7563@sbc.com
  0.2% |   1 |  0.4% |    6003 | atul.sabharwal@intel.com
  0.2% |   1 |  0.3% |    5766 | hardie@qualcomm.com
  0.2% |   1 |  0.3% |    5699 | dhc@dcrocker.net
  0.2% |   1 |  0.3% |    5206 | cchaplin@sj.symbol.com
  0.2% |   1 |  0.3% |    4923 | peterf@exchange.microsoft.com
  0.2% |   1 |  0.3% |    4425 | page@mail.msen.com
  0.2% |   1 |  0.3% |    4388 | braendt@hotmail.com
  0.2% |   1 |  0.3% |    4306 | gk@ninebynine.org
  0.2% |   1 |  0.2% |    4096 | jorge.contreras@haledorr.com
  0.2% |   1 |  0.2% |    3465 | inanbe@xs4all.nl
  0.2% |   1 |  0.2% |    3310 | hinden@iprg.nokia.com
  0.2% |   1 |  0.2% |    3214 | smb@research.att.com
  0.2% |   1 |  0.2% |    3194 | gray@washington.edu
  0.2% |   1 |  0.2% |    3085 | ole@cisco.com
  0.2% |   1 |  0.2% |    3077 | rod.walsh@nokia.com
  0.2% |   1 |  0.2% |    2958 | msa@burp.tkv.asdf.org
  0.2% |   1 |  0.2% |    2946 | vinton.g.cerf@mci.com
  0.2% |   1 |  0.2% |    2782 | swb@employees.org
  0.2% |   1 |  0.2% |    2761 | jtk@depaul.edu
  0.2% |   1 |  0.2% |    2661 | bob.natale@appliedsnmp.com
  0.2% |   1 |  0.2% |    2621 | spencer_dawkins@yahoo.com
  0.2% |   1 |  0.1% |    2510 | glc@cisco.com
  0.2% |   1 |  0.1% |    2416 | klensin@jck.com
  0.2% |   1 |  0.1% |    2323 | braden@isi.edu
  0.2% |   1 |  0.1% |    2303 | kent@bbn.com
  0.2% |   1 |  0.1% |    2265 | andy.malis@vivacenetworks.com
  0.2% |   1 |  0.1% |    2259 | jfbauer@comcast.net
  0.2% |   1 |  0.1% |    2175 | benson.schliesser@savvis.net
  0.2% |   1 |  0.1% |    1789 | noc@nso.org
-------+-----+-------+---------+------------------------
100.0% | 466 |100.0% | 1684907 | Total



From owner-ietf@ietf.org  Fri May 30 15:23:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24020
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 15:23:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LpGn-0000PS-0f
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 15:10:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LpBE-0006Jm-7R
	for ietf@asgard.ietf.org; Fri, 30 May 2003 15:04:44 -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 PAA22227
	for <ietf@ietf.org>; Fri, 30 May 2003 15:04:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lp9a-0000Cw-00
	for ietf@ietf.org; Fri, 30 May 2003 15:03:02 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lp9Z-0000Ct-00
	for ietf@ietf.org; Fri, 30 May 2003 15:03:01 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19LpB3-00047J-00; Fri, 30 May 2003 14:04:33 -0500
Date: Fri, 30 May 2003 15:04:33 -0400
From: John C Klensin <john-ietf@jck.com>
To: Dean Anderson <dean@av8.com>
cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Message-ID: <262266829.1054307073@p3.JCK.COM>
In-Reply-To: <Pine.LNX.4.44.0305301340250.17819-100000@commander.av8.net>
References:  <Pine.LNX.4.44.0305301340250.17819-100000@commander.a
 v8.net>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Friday, 30 May, 2003 14:09 -0400 Dean Anderson 
<dean@av8.com> wrote:

>...
> And John has obviously never been involved in a Law
> Enforcement request. But I have.  Private emails to him seem
> to confirm this, or at least he didn't indicate anything to
> the contrary.  While he may have been working on SMTP
> protocols for 30 years, he obviously hasn't been involved in
> trackig abuse of various sorts, and has no idea of whether
> this is expensive or difficult.

Dean, private emails to me didn't raise the issue of Law 
Enforcement requests, so, no I "didn't indicate anything to the 
contrary (I note that I didn't "indicate to the contrary" about 
eating babies three times a week either).  But, yes, I've been 
involved in them, as well as in very small group discussions 
with FBI personnel about what is and is not feasible to request 
and monitor.  More important, some of those private exchanges 
explained to you, in some detail (even by my normally 
long-winded standards), about my involvement in abuse handling 
and tracing at front-line, management, and training levels, as 
well as my involvement in very large scale email provisioning 
and operation.  I also, fairly patiently, explained to you that 
I had been involved in a number of standardization efforts 
--both policy-level and in the trenches-- quite different from 
SMTP, and about my involvement in those and other areas on the 
development, deployment, operational, and procurement sides as 
well as standards development.

I'm not insulted, because I've been around the IETF and other 
areas long enough to have developed a pretty thick skin about 
this sort of stuff.   But I wish you would stop repeating this 
(to use your term) nonsense about what I do and don't know and 
have and haven't done.  It is, at best, a waste of everyone 
else's time.

Indeed, I think it has gone on about long enough.  Harald, of 
whomever is responsible for the IETF list, Dean has repeatedly 
attempted to defame my character and experience, despite (and 
after) having been supplied ample detail to refute his claims, 
assumptions, and accusations (I will supply copies of the 
relevant correspondence to you on request).  That is against the 
rules for the IETF list as I understand them.  Would you please 
initiate the appropriate action to formally warn him and, if the 
practice persists, suspend posting rights?

    john





From owner-ietf@ietf.org  Fri May 30 15:28:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24230
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 15:28:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LpGo-0000TU-Nj
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 15:10:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LpGB-0008KV-2X
	for ietf@asgard.ietf.org; Fri, 30 May 2003 15:09:51 -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 PAA22912
	for <ietf@ietf.org>; Fri, 30 May 2003 15:09:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LpEW-0000HS-00
	for ietf@ietf.org; Fri, 30 May 2003 15:08:08 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LpEM-0000GG-00
	for ietf@ietf.org; Fri, 30 May 2003 15:07:58 -0400
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49])
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h4UJ1eS13023
	for <ietf@ietf.org>; Fri, 30 May 2003 12:01:40 -0700
Date: Fri, 30 May 2003 12:01:40 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
In-Reply-To: <Pine.LNX.4.44.0305301340250.17819-100000@commander.av8.net>
Message-ID: <Pine.LNX.4.33.0305301146440.6420-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
X-MIME-Autoconverted: from 8bit to quoted-printable by egate.xpasc.com id h4UJ1eS13023
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA24230


What is demonstrated is that given the incentive, there was sufficient
information in this case to track down the offender in a relatively short
time span.

There is a signficant difference between spam and this example. Making a
bomb threat is a felony AND an activity which gets immediate attention
from law enforcement. The existance of a bomb threat will also encourge
the immediate cooperation of the intermediate entitities. There are
relatively few such threats to pursue. The perpetrator was also sounded
pretty inexperienced in terms of the facilities they used to obscure their
identity.

It is highly unlikely that unsolicited bulk email will ever receive this
degree of attention or the coordinated attack to track down a verifiable
origin.

My security gurus tell me that spoofing IP addresses well enough to open
a TCP/IP is not difficult.  If that is correct, then reliance on
knowledge of origin IP address won't stand up over the long haul.

There is a small operation in the ether that periodically offers to
introduce me to eastern women wishing to meet western men. There is no
obvious commercial operation, the pictures provided are not generally
offensive. At some point I got curious trying to figure out the value
proposition. What I've observed is that the domain name changes frequently
and the IP address it translates to changes almost as often. My guess is
that the folks running this 'service' are pirating internet connectivity
and get shutdown when discovered. Sometimes a few days. Sometimes a couple
of weeks. If my presumption of service pirating is correct, this serves as
an existance proof that IP addresses can't be relied on to identify the
source of future spam.

Dave Morris

On Fri, 30 May 2003, Dean Anderson wrote:

> Well, John has not been insulted.
>
> You seem to take issue with section:
>
> =================
> > > This problem was been fixed around 1993.. It is not possible
> > > to send anonymous email through an open relay. (you still hear
> > > this from radical antispammers, though).
> >
> > If sufficient logging information is maintained, it is not
> > possible to send mail through a relay (open or not) without
> > identifying the IP address of the sender (that statement was
> > true before and after the changes you identify as "around
> > 1993").  Getting from that IP address to identification of the
> > individual sender --which is what you presumably mean by "not
> > anonymous"-- is more or less difficult and more or less
> > expensive, depending on a number of other circumstances.   In
> > some cases --and, again, if one believes that people's time has
> > any value-- the practical costs of identifying an individual far
> > exceed any possible value in doing so.  In some others, it may
> > be nearly impossible.   For example, there is a well-known Asian
> > country in which most of the dialup services appear to be
> > freenets, with widely-available dialup numbers and passwords
> > shared among, I believe, literally millions of people.  The mail
> > relays on those systems have no way to determine which user is
> > originating a piece of mail, the user's IP address is of no
> > help, and a system receiving mail from one of those relays can
> > only identify the relay host.  That is a pretty good
> > approximation to anonymity in my book.
>
> This is just nonsense.  Obviously, you have no operational experience.
> =================
>
> It is nonsense because "sufficient logging information" has no bearing on
> whether is possible to send email through an (open or not) relay without
> identifying the IP address of the sender. This IP address is in the
> 'Recieved:' header, and cannot be altered or removed by the sender.
>
> It is nonsense because the prior anonymity of a user because of shared
> passwords by an asian dialup has no bearing on whether open relays are
> anonymous. The property of a users anonymity isn't changed by SMTP, as is
> wrongly asserted. It is irrelevant whether an ISP in asia doesn't have
> accounting records for their users and shares passwords.
>
> So, my statement is correct.  It is nonsense.
>
> And John has obviously never been involved in a Law Enforcement request.
> But I have.  Private emails to him seem to confirm this, or at least he
> didn't indicate anything to the contrary.  While he may have been working
> on SMTP protocols for 30 years, he obviously hasn't been involved in
> trackig abuse of various sorts, and has no idea of whether this is
> expensive or difficult.
>
> Here is a Law Enforcement request I can relate:  Shortly after Genuity
> took their national VOIP service into production, some kid used a
> customer's free PC-to-phone service to phone in a bomb threat to a school.
> Law Enforcement called the phone company, which traced the PSTN call back
> to a CLEC. A call to the CLEC identified Genuity. Genuity operations staff
> called me, because they were still somewhat untrained with the integrated
> Radius/accounting system for which I was a significant contributing
> engineer. They knew how to keep it running, but did not know the queries
> to find certain kinds of information.
>
> I explained how to get what they needed to know. They quickly identifed an
> IP address belonging to a Genuity (retail VOIP) customer. That customer
> used a gateway to relay the call from their customer to Genuity. I believe
> that they then got a call from Law Enforcement, and they then identified a
> residential ISP, which then identified the original user. Who was quickly
> arrested.
>
> This all happened fairly quickly. It is not expensive, as John wrongly
> seems to think. And the process has nothing whatsoever to do with SMTP.
> In the case of an open relay abuse, the IP of the abuser is quickly and
> easily found*. More more easily than in the case above.
>
> *Unless of course, they have an ISP that doesn't keep track of
> users--which isn't a fault of open relay.  As was pointed out to John,
> SMTP AUTH doesn't alter this situtation in the least.
>
>
> On Fri, 30 May 2003, Tomson Eric (Yahoo.fr) wrote:
>
> > Anthony,
> >
> > First, I sent my mail to the list to make public apologies for the public
> > insult made to John on this list.
> >
> > Second, the objective of this mail was not to discredit Dean (despite his
> > insults), but to apologize vis-à-vis John (because of the insults made to
> > him).
> > Read my mail a bit closer, and you will discover that the main idea was not
> > defamation but apologies.
> >
> > Finally, I said that I spoke "in the name of every honest and decent
> > contributor to this list".
> > So tell me how I should consider the fact that you don't feel concerned...
> >
> > E.T.
> >
> > P.S.: this having been said as a "droit de réponse", you are free to
> > continue this conversation privately, off the list...
> >
> > -----Original Message-----
> > From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of Anthony
> > Atkielski
> > Sent: vendredi 30 mai 2003 9:14
> > To: IETF Discussion
> > Subject: Re: The utilitiy of IP is at stake here
> >
> >
> > > John,
> >
> > If you are speaking only to John, why do you send your message to an entire
> > list?
> >
> > > Since I don't think Dean "Troll" Anderson will do
> > > it, I would like to apologize, in the name of every
> > > honest and decent contributor to this list, for the
> > > insults made against someone that was so deeply
> > > involved in the development of SMTP and MIME, and
> > > whose contribution, reputation, and experience earned
> > > him the Internet Architecture Board's chair.
> >
> > Your attempt to discredit someone else on the list is transparently obvious.
> > Why not just state your disagreement with him and leave it at that, instead
> > of embarking on a smear campaign?
> >
> > > I feel so sorry to see how dishonest and undecent
> > > one can be with those who contributed to design and
> > > build the Internet and all related technologies
> > > and protocols.
> >
> > See above.  A rather poor attempt to disguise defamation as nobility.
> >
> > Perhaps you should simply speak for yourself, instead of presuming to speak
> > for others, particularly when the latter is really only a platform for
> > actions of questionable merit?
> >
> >
> >
> >
> >
>
>
>
>
>
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it, which is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on what to pass are made solely by Raffaele D'Albenzio.
>




From owner-ietf@ietf.org  Fri May 30 15:55:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25146
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 15:55:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lpez-0004Ao-QL
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 15:35:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LpQP-0002rk-Fq
	for ietf@asgard.ietf.org; Fri, 30 May 2003 15:20:25 -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 PAA23944
	for <ietf@ietf.org>; Fri, 30 May 2003 15:20:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LpOl-0000PD-00
	for ietf@ietf.org; Fri, 30 May 2003 15:18:43 -0400
Received: from carwash.centive.com ([65.220.90.249] helo=carwash.centivinc.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19LpOl-0000OU-00
	for ietf@ietf.org; Fri, 30 May 2003 15:18:43 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003053015265000034
 for <ietf@ietf.org>; Fri, 30 May 2003 15:26:50 -0400
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 30 May 2003 15:17:30 -0400
Message-ID: <3ED7AE4A.3080703@centive.com>
Date: Fri, 30 May 2003 15:17:30 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Spam
References: <lHoQPzDbiz1+Ewdx@soaring.demon.co.uk> <g37k88th1e.fsf@sa.vix.com>
In-Reply-To: <g37k88th1e.fsf@sa.vix.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 30 May 2003 19:17:30.0580 (UTC) FILETIME=[1D7D8140:01C326E0]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Paul Vixie wrote:

>if we could make spamganging so illegal that they were eventually
>not replaced, then their traffic would be replaced by bulk e-mail from every
>customer of every CRM (customer relationship management) company in the world.
>
I'm not sure why this follows.  Wiping out the fraudulent spammers would 
take a War On Spam, with massive levels of propaganda to stir up public 
opinion enough to justify the money it would cost.  In that kind of 
environment, even in the aftermath, no white hat would dare spam; their 
customers would immediately turn against them.

-- 
/============================================\
|John Stracke      |jstracke@centive.com     |
|Principal Engineer|http://www.centive.com   |
|Centive           |My opinions are my own.  |
|============================================|
|Never do card tricks for your poker buddies.|
\============================================/





From owner-ietf@ietf.org  Fri May 30 16:03:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25579
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 16:03:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lpy4-0004mq-Qu
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 15:55:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Lpm3-0004Mg-RG
	for ietf@asgard.ietf.org; Fri, 30 May 2003 15:42:47 -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 PAA24722
	for <ietf@ietf.org>; Fri, 30 May 2003 15:42:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LpkP-0000cV-00
	for ietf@ietf.org; Fri, 30 May 2003 15:41:05 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LpkP-0000cS-00
	for ietf@ietf.org; Fri, 30 May 2003 15:41:05 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 208711 for ietf@ietf.org; Fri, 30 May 2003 14:42:14 -0500
Message-ID: <3ED7B42F.3090705@ehsco.com>
Date: Fri, 30 May 2003 14:42:39 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: spam
References: <3ED78783.1090909@ehsco.com> <200305301705.h4UH52EF020008@calcite.rhyolite.com>
In-Reply-To: <200305301705.h4UH52EF020008@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/30/2003 12:05 PM Vernon Schryver wrote:

> None of the even slightly plausible anti-forgery proposals have even 
> the slightest believable effects toward enforcing the use of known 
> identities.

They don't have to be "known" identies to provide accountability measures,
they only have to be verifiable. The proposals that even I think are too
complex are the ones that require the use of "known" identities
(exchanging tickets, bilateral postage agreements, etc).

Simply limiting the information to a "verifiable" scope can provide
sufficient levels of accountability. For exmaple, allowing self-signed
certificates but restricting their acceptance to the same mail domain
would provide some baseline measure of verification (DNS lookups), and
would provide some level of accountability (through the DNS domain
delegation information), and would provide additional strenght to the
available enforcement options. None of that requires "known" identities
(btw, I'm not ready to propose that usage model, just laying it out as an
example of how "known" identities aren't necessary to achieve a goal of
accountability through verified paths).

> No anti-forgery proposal has included anything that would 
> inconvenience a spammer that wants 10,000 "known identities." No price
> on certificates or any other mechanism can be low enough to be 
> tolerable by users but high enough to determine that the next new 
> account an ISP sees is not a known spammer with a new name, adresses, 
> and valid credit card number.

First of all, I think this is really an argument for legal options. I've
already stated that I don't think the spam problem in particular can be
"fixed" in the absence of legal enforcement options.

Secondarily, if we wanted to be productive (forward-moving) on this
particular subject, we should be discussing the mechanisms that would be
needed and/or useful towards making the necessary retrieval, comparison
and enforcement functions useful, and which would in turn make any of the
available enforcement options useful. I don't find the current absence of
credible services (WHOIS is currently useless) to be a compelling argument
against their eventual presence (WHOISng may be more useful), nor as
compelling arguments against their subsequent integration with other
services (integration between a WHOISng and an SMTPng for locating all of
the domains associated with a known offender, as one possibility). We
already know we're going to need some kind of identification mechanism, so
what else would we need as part of that?

>> The first step in that means weakening the ability to use forgery 
>> techniques as a shield, but that's just a start. It should also help 
>> against some of the prevarication you describe above, since there
>> would be less room for waffling if recipients were able to "prove" by
>> verifiable transfer-path analysis that a particular node had
>> absolutely sent some piece of spam.  ...
> 
> That should sound like the mistake it is in a more or less technical 
> setting like this.  There has never been any lack of a "verifiable 
> transfer-path analysis that a particular node had absolutely sent some 
> piece of spam" unless you believe that spammers use initial sequence 
> number prediction to forge IP addresses.  You always know the IP 
> address of the SMTP client, even if it is a relay or proxy.  ISPs could
> and should hold operators of open relays and proxies accountable for
> sending the spam their systems send.

Conceding that "ISPs could and should hold operators...accountable"
doesn't dismiss the claims, and neither does the rest of your text.

Preventing the use of proxies through verifiable end-system identifiers is
one of "the first steps" I referred to. The problem would mostly move into
the relay and direct-sender space, but those uses could be dealt with much
more aggressively given the "proof" that would be available afterwards;
the range of enforcement options are all strengthened by better proof. The
original claims stand, despite your concession and fist-waving.

>> Secondarily, there is another class of user where forgeries are 
>> problematic in their own right, which is outright impersonation
>> and/or fraud, and in that context the anti-forgery capabilities would
>> stand as a unique benefit. However, the enforcement options which
>> were made available to those users as a result of the accountability
>> features would be no less compelling to those users if forgery were
>> attempted and caught.
> 
> Please point out a single such case where header forgery was not
> obvious and that needed or could have used any extra machinery.

In 1993, Adelyn Lee won a $100,000 wrongful-termination settlement against
Oracle, partially using forged email between her superiors as evidence.
Four years later the forgery was exposed, but the evidence that did her in
was testimony, log files, and cell-phone records, not the email message.
It seems obvious to me that a mail system which offered the kinds of
accountability features we're talking about and which cost less than the
settlement costs, corporate personnel and legal fees would have been well
worth the expense to them.

http://www.wired.com/news/technology/0,1282,9641,00.html describes three
different instances of fraudulent misrepresentation of Yahoo, any of which
would have been ameliorated with half-decent identity information which
clearly indicated the user was a customer and not an employee of Yahoo.
I've no idea what the dollar cost to Yahoo was, but the legal time alone
couldn't have been cheap, not to mention the economic impact from loss of
credibility.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Fri May 30 16:20:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26218
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 16:20:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lq9x-0005qc-QX
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 16:07:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Lq4o-0005Ib-W2
	for ietf@asgard.ietf.org; Fri, 30 May 2003 16:02:11 -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 QAA25508
	for <ietf@ietf.org>; Fri, 30 May 2003 16:02:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lq3B-0000qg-00
	for ietf@ietf.org; Fri, 30 May 2003 16:00:29 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lq3A-0000qd-00
	for ietf@ietf.org; Fri, 30 May 2003 16:00:28 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 208715 for ietf@ietf.org; Fri, 30 May 2003 15:01:38 -0500
Message-ID: <3ED7B8BE.1010307@ehsco.com>
Date: Fri, 30 May 2003 15:02:06 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: Spam
References: <lHoQPzDbiz1+Ewdx@soaring.demon.co.uk> <g37k88th1e.fsf@sa.vix.com> <3ED7AE4A.3080703@centive.com>
In-Reply-To: <3ED7AE4A.3080703@centive.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/30/2003 2:17 PM John Stracke wrote:
> Paul Vixie wrote:
> 
>>if we could make spamganging so illegal that they were eventually
>>not replaced, then their traffic would be replaced by bulk e-mail from every
>>customer of every CRM (customer relationship management) company in the world.
> 
> I'm not sure why this follows.  Wiping out the fraudulent spammers would 
> take a War On Spam, with massive levels of propaganda to stir up public 
> opinion enough to justify the money it would cost.  In that kind of 
> environment, even in the aftermath, no white hat would dare spam; their 
> customers would immediately turn against them.

The way to avoid that kind of blow-back against legitimate use is through
documented innocence (saving the explicit opt-in confirmation).

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Fri May 30 16:28:28 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26607
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 16:28:28 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LqMJ-0006Oo-49
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 16:20:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LqA9-0005sG-Nu
	for ietf@asgard.ietf.org; Fri, 30 May 2003 16:07:41 -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 QAA25767
	for <ietf@ietf.org>; Fri, 30 May 2003 16:07:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lq8V-0000v0-00
	for ietf@ietf.org; Fri, 30 May 2003 16:05:59 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lq8U-0000uh-00
	for ietf@ietf.org; Fri, 30 May 2003 16:05:58 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id QAA04193;
	Fri, 30 May 2003 16:00:33 -0400
Date: Fri, 30 May 2003 16:01:24 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: John C Klensin <john-ietf@jck.com>
cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
In-Reply-To: <262266829.1054307073@p3.JCK.COM>
Message-ID: <Pine.LNX.4.44.0305301553050.17819-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


I haven't repeatedly (or at all) defamed anyone.

You haven't answered the question.  The answer you gave was irrelevant to
the question, and doesn't support your wrong assertion that open relays
allow one to send anonymous email without the IP address of the sender.

I think that I am the one being defamed, since you repeated question my
credibility while avoiding the question.

And I also would like to initiate a formal complaint.

You should answer the question, and quit complaining that you are being
put in the spot to answer it.

		--Dean




On Fri, 30 May 2003, John C Klensin wrote:

> --On Friday, 30 May, 2003 14:09 -0400 Dean Anderson
> <dean@av8.com> wrote:
>
> >...
> > And John has obviously never been involved in a Law
> > Enforcement request. But I have.  Private emails to him seem
> > to confirm this, or at least he didn't indicate anything to
> > the contrary.  While he may have been working on SMTP
> > protocols for 30 years, he obviously hasn't been involved in
> > trackig abuse of various sorts, and has no idea of whether
> > this is expensive or difficult.
>
> Dean, private emails to me didn't raise the issue of Law
> Enforcement requests, so, no I "didn't indicate anything to the
> contrary (I note that I didn't "indicate to the contrary" about
> eating babies three times a week either).  But, yes, I've been
> involved in them, as well as in very small group discussions
> with FBI personnel about what is and is not feasible to request
> and monitor.  More important, some of those private exchanges
> explained to you, in some detail (even by my normally
> long-winded standards), about my involvement in abuse handling
> and tracing at front-line, management, and training levels, as
> well as my involvement in very large scale email provisioning
> and operation.  I also, fairly patiently, explained to you that
> I had been involved in a number of standardization efforts
> --both policy-level and in the trenches-- quite different from
> SMTP, and about my involvement in those and other areas on the
> development, deployment, operational, and procurement sides as
> well as standards development.
>
> I'm not insulted, because I've been around the IETF and other
> areas long enough to have developed a pretty thick skin about
> this sort of stuff.   But I wish you would stop repeating this
> (to use your term) nonsense about what I do and don't know and
> have and haven't done.  It is, at best, a waste of everyone
> else's time.
>
> Indeed, I think it has gone on about long enough.  Harald, of
> whomever is responsible for the IETF list, Dean has repeatedly
> attempted to defame my character and experience, despite (and
> after) having been supplied ample detail to refute his claims,
> assumptions, and accusations (I will supply copies of the
> relevant correspondence to you on request).  That is against the
> rules for the IETF list as I understand them.  Would you please
> initiate the appropriate action to formally warn him and, if the
> practice persists, suspend posting rights?
>
>     john
>
>
>




From owner-ietf@ietf.org  Fri May 30 17:09:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28401
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 17:09:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lqw1-0000rX-15
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 16:57:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Lqd0-0007f9-ID
	for ietf@asgard.ietf.org; Fri, 30 May 2003 16:37:30 -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 QAA27034
	for <ietf@ietf.org>; Fri, 30 May 2003 16:37:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LqbM-0001Eq-00
	for ietf@ietf.org; Fri, 30 May 2003 16:35:48 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LqbL-0001En-00
	for ietf@ietf.org; Fri, 30 May 2003 16:35:48 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19Lqcy-0004Si-00; Fri, 30 May 2003 15:37:28 -0500
Date: Fri, 30 May 2003 16:37:28 -0400
From: John C Klensin <john-ietf@jck.com>
To: Dean Anderson <dean@av8.com>
cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: Answering questions and defamation (was: RE: The
 utilitiy of IP is at stake here)
Message-ID: <267841966.1054312648@p3.JCK.COM>
In-Reply-To: <Pine.LNX.4.44.0305301553050.17819-100000@commander.av8.net>
References:  <Pine.LNX.4.44.0305301553050.17819-100000@commander.a
 v8.net>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Friday, 30 May, 2003 16:01 -0400 Dean Anderson 
<dean@av8.com> wrote:

> I haven't repeatedly (or at all) defamed anyone.

You have repeatedly made public statements about what I don't 
know, what experience I lack, etc.   I have questioned the facts 
you report, but have not made any public claims that you lack 
sufficient background to know what you are talking about.  I 
honestly don't know much about your background and experience, 
and have not claimed otherwise.   You have made repeated claims 
about mine that are not based on any knowledge of my actual 
experience and which several readers of this list know enough to 
refute, at least in particular areas.
>...
> And I also would like to initiate a formal complaint.

Oh, goodie.   In the interesting of getting resolution, and to 
preserve everyone's sanity in the interim, I'm going to make no 
further postings on these threads until Harald, or someone else, 
indicate how he (or they) intend to sort this out.

> You haven't answered the question.  The answer you gave was
> irrelevant to the question, and doesn't support your wrong
> assertion that open relays allow one to send anonymous email
> without the IP address of the sender.

What I told you, at some length if I recall, in a private note, 
is that

* Only the IP address recorded in a Received field by the SMTP 
server that last accepts the message for delivery to you can 
generally be considered reliable and trustworthy.   Reliance on 
any other IP address in the Received chain requires a chain of 
trust between SMTP servers.   Independent of its utility, 
several of the discussions on this list in the last few days 
have ultimately been about establishing such chains of trust, 
but nothing in either SMTP or generally-accepted Internet 
operational procedures require or provide it today.  Even for 
the delivery MTA, the trust and/or contractual relationship 
between the recipient and the operator may not guarantee the 
integrity of the Received fields it inserts, although they are 
usually accurate.

* Received fields --other than, again, the one that you own 
server inserts-- are routinely faked in some varieties of spam. 
Consequently, the source MTA can often not be identified with 
any reliability if more than one relay (open or otherwise) is 
involved.

* While it is not easy when a multiple-transaction TCP-based 
protocol like SMTP is involved, IP addresses can be faked.

* Obtaining the IP address of a client does not permit 
identifying a specific user, unless the owner/provider of that 
IP address retains sufficient information to identify the user 
and makes that information available upon request.  There is no 
present operational or legal requirement on SMTP server 
operators, or on ISPs, to log that information at all, nor to 
retain the information for any particular length of time if they 
do log it.  So, even if the source IP address is known and 
authentic, the originating user may not be identifiable.   That 
is a fairly good approximation to "anonymous" in my book, but 
perhaps you are using a different definition.

> I think that I am the one being defamed, since you repeated
> question my credibility while avoiding the question.
>
> You should answer the question, and quit complaining that you
> are being put in the spot to answer it.

See above, assuming that was the question -- I have had trouble 
identifying it in the noise.

As indicated above, I'm now out of this discussion until our 
respective complaints can be evaluated.  I encourage you to do 
likewise.

      john







From owner-ietf@ietf.org  Fri May 30 17:10:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28489
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 17:10:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lqw1-0000rd-BW
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 16:57:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LqdB-0007fD-1b
	for ietf@asgard.ietf.org; Fri, 30 May 2003 16:37:41 -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 QAA27040
	for <ietf@ietf.org>; Fri, 30 May 2003 16:37:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LqbX-0001F0-00
	for ietf@ietf.org; Fri, 30 May 2003 16:35:59 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LqbW-0001El-00
	for ietf@ietf.org; Fri, 30 May 2003 16:35:58 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id QAA20773;
	Fri, 30 May 2003 16:30:28 -0400
Date: Fri, 30 May 2003 16:31:19 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: John C Klensin <john-ietf@jck.com>
cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
In-Reply-To: <262266829.1054307073@p3.JCK.COM>
Message-ID: <Pine.LNX.4.44.0305301628240.17819-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Fri, 30 May 2003, John C Klensin wrote:

> --On Friday, 30 May, 2003 14:09 -0400 Dean Anderson
> <dean@av8.com> wrote:
>
> >...
> > And John has obviously never been involved in a Law
> > Enforcement request. But I have.  Private emails to him seem
> > to confirm this, or at least he didn't indicate anything to
> > the contrary.  While he may have been working on SMTP
> > protocols for 30 years, he obviously hasn't been involved in
> > trackig abuse of various sorts, and has no idea of whether
> > this is expensive or difficult.
>
> Dean, private emails to me didn't raise the issue of Law
> Enforcement requests, so, no I "didn't indicate anything to the
> contrary (I note that I didn't "indicate to the contrary" about
> eating babies three times a week either).

You make is sound as though I didn't ask. I obviously didn't ask you if
you eat babies. But I did ask if you've ever tracked down an abuser:

This is from a private message to you:
===========================
> And I've been involved with SMTP, and its predecessors, for over
> thirty years now -- standards, protocol design, gateway design
> and implementation, and operations and deployment in
> organizations and enterprises ranging from the very small to the
> very large.

But have you ever tracked down an abuser?

Have you ever sold standards based services to customers that want
standards based services?  Do you really understand why customers want
standards?

Thats operational experience.
============================





From owner-ietf@ietf.org  Fri May 30 17:27:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29095
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 17:27:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LrBp-00023C-OM
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 17:13:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LkgY-0006gl-63
	for ietf@asgard.ietf.org; Fri, 30 May 2003 10:16:46 -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 KAA09562
	for <IETF@IETF.ORG>; Fri, 30 May 2003 10:16:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lkeu-0004w2-00
	for IETF@IETF.ORG; Fri, 30 May 2003 10:15:04 -0400
Received: from d.psc.edu ([128.182.73.107])
	by ietf-mx with smtp (Exim 4.12)
	id 19Lket-0004vy-00
	for IETF@IETF.ORG; Fri, 30 May 2003 10:15:03 -0400
Received: by c.psc.edu; Fri, 30 May 2003 10:16:41 -0400
Date: Fri, 30 May 2003 10:16:41 -0400
From: "Raghurama 'REDDY'" <rreddy@psc.edu>
Reply-To: rreddy@psc.edu
To: john.loughney@kolumbus.fi
CC: IETF@ietf.org
Message-Id: <03053010164149.23416156.7915185@psc.edu>
Subject: RE: =?UTF-8?Q?Re:_The_utilitiy_of_IP_is_at_stake_here?=
Sender: owner-ietf@ietf.org
Precedence: bulk

>> From:	SMTP%"john.loughney@kolumbus.fi"  "=?UTF-8?Q?John_Loughney?=" 30-MAY-2003 09:37:08.49
>> To:	vjs@calcite.rhyolite.com, ietf@ietf.org
>> CC:	
>> Subj:	=?UTF-8?Q?Re:_The_utilitiy_of_IP_is_at_stake_here?=
>> 
>> ...
>> ...
>> 
>> Many folks update their MS software (Linux, too) in the hope th=
>> ey will get more stability / more security / more seatures - no=
>> t becaue of bit rot. Updating mail clients does not seem to be =
>> a huge deal - manypeople update their OS / browser when prompte=
>> d. Majority of my friends & family use a web browser to access =
>> private mail. Companies would have interest in upgrading, if it=
>>  helped also with viruses & security.
>> 

True.  The recent MSN TV ads (with their butterfly man) touting their
spam guard suggest that they do value user's ability to control spam.

Best Regards,

--rr





From owner-ietf@ietf.org  Fri May 30 17:37:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29379
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 17:37:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LrBp-00023K-T3
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 17:13:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Lo9w-0005kE-35
	for ietf@asgard.ietf.org; Fri, 30 May 2003 13:59:20 -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 NAA19139
	for <ietf@ietf.org>; Fri, 30 May 2003 13:59:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lo8I-0007C6-00
	for ietf@ietf.org; Fri, 30 May 2003 13:57:38 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lo8H-0007C3-00
	for ietf@ietf.org; Fri, 30 May 2003 13:57:37 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4UHxHKk050684
	for <ietf@ietf.org>; Fri, 30 May 2003 19:59:17 +0200 (CEST)
Message-ID: <0a8001c326d5$30342880$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <sed61b06.037@gwianameserver.sj.symbol.com> <09aa01c32679$289e09d0$0a00000a@atkielski.com> <200305301027.30905.dja2003@hotpop.com>
Subject: Re: spam
Date: Fri, 30 May 2003 19:59:17 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dave writes:

> But spammers DO sometimes subscribe to mailing lists,
> for the purpose of harvesting addresses.

So?  That wouldn't give them the secret strings.  The only secret string a
mailing list subscription would provide would be the secret string to send
to the list (if any).






From owner-ietf@ietf.org  Fri May 30 17:57:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29894
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 17:57:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LrZt-0003Si-EU
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 17:38:21 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LrNb-0002U2-GK
	for ietf@asgard.ietf.org; Fri, 30 May 2003 17:25:39 -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 RAA29037
	for <ietf@ietf.org>; Fri, 30 May 2003 17:25:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LrLx-0001oB-00
	for ietf@ietf.org; Fri, 30 May 2003 17:23:57 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LrLw-0001o6-00
	for ietf@ietf.org; Fri, 30 May 2003 17:23:56 -0400
Received: from [63.202.92.152] (adsl-66-125-125-65.dsl.pltn13.pacbell.net [66.125.125.65])
	(authenticated bits=0)
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h4ULPVAG053481;
	Fri, 30 May 2003 14:25:34 -0700 (PDT)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p0521060fbafd7b28680b@[63.202.92.152]>
In-Reply-To: <001a01c326d6$9dfe6e60$56144104@eagleswings>
References: <001a01c326d6$9dfe6e60$56144104@eagleswings>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Fri, 30 May 2003 14:23:51 -0700
To: <alh-ietf@tndh.net>, <ietf@ietf.org>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: RE: The utilitiy of IP is at stake here
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 11:09 AM -0700 5/30/03, Tony Hain wrote:
>Paul Hoffman wrote:
>>  So far on this thread, we have heard from none of the "large-scale
>>  mail carriers", although we have heard that the spam problem is
>>  costing them millions of dollars a year. That should be a clue to the
>>  IETF list. If there is a problem that is affecting a company to the
>>  tune of millions of dollars a year, and that company thinks that the
>>  problem could be solved, they would spend that much money to solve
>>  it. Please note that they aren't.
>
>And that would be because they can't do it in isolation. They need a
>system wide standard everyone is building to, to make your argument
>below about cost of untrusted mail moot.

And you believe that these companies are so stupid that when they 
have a problem that is costing them tens of millions of dollars a 
year, they wouldn't think of coming together for a solution? Maybe I 
have a higher opinion of them than you do because they were members 
of my consortium.

All of these companies have people following (and often 
participating) in the IETF. To assume otherwise without first asking 
them is pretty silly.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Fri May 30 18:13:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01167
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 18:13:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LrtE-0004Oy-LA
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 17:58:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LroH-0003sg-JO
	for ietf@asgard.ietf.org; Fri, 30 May 2003 17:53:13 -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 RAA29760
	for <ietf@ietf.org>; Fri, 30 May 2003 17:53:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lrmd-0001zu-00
	for ietf@ietf.org; Fri, 30 May 2003 17:51:31 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lrmc-0001zr-00
	for ietf@ietf.org; Fri, 30 May 2003 17:51:30 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.9/8.12.9) id h4ULrATA019693
	for ietf@ietf.org env-from <vjs>;
	Fri, 30 May 2003 15:53:10 -0600 (MDT)
Date: Fri, 30 May 2003 15:53:10 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200305302153.h4ULrATA019693@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: The utilitiy of IP is at stake here
References: <3ED7A03C.1040603@ehsco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: "Eric A. Hall" <ehall@ehsco.com>

> ...
> think it's equally obvious that companies are spending massive amounts of
> money to try and solve this problem (assuming we agree that $500 million
> from one company qualifies as "massive"), and that they are continuing to
> pursue those solutions which are probably the most viable for their
> peculiar situations.
> ...

That's true only if you accept stuff in the mass media uncritically.
The mass media frequently get almost every thing else wrong by many
orders of magnitude, so why pick this tidbit to believe?
For Heaven's sake!  Do a sanity check and think about how you would
spend $0.5B on filtering spam.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Fri May 30 19:10:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02523
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 19:10:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LsWq-0003L8-4a
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 18:39:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ls5T-0000yi-E7
	for ietf@asgard.ietf.org; Fri, 30 May 2003 18:10:59 -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 SAA00945
	for <ietf@ietf.org>; Fri, 30 May 2003 18:10:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ls3p-00026e-00
	for ietf@ietf.org; Fri, 30 May 2003 18:09:17 -0400
Received: from ns1.vrx.net ([216.13.126.22])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ls3o-00026b-00
	for ietf@ietf.org; Fri, 30 May 2003 18:09:16 -0400
Received: from [192.168.1.14] (lsanca1-ar47-4-33-128-181.lsanca1.dsl-verizon.net [4.33.128.181])
	by ns1.vrx.net (Postfix) with ESMTP id 9A756D282
	for <ietf@ietf.org>; Fri, 30 May 2003 18:10:48 -0400 (EDT)
Mime-Version: 1.0
X-Sender: steflist@vrx.net
Message-Id: <v04220812bafd86c6908a@[192.168.1.14]>
In-Reply-To: <p05100306bafd3c440103@[128.89.88.34]>
References: <114782448.1054159586@p3.JCK.COM> <g3fzmytgm3.fsf@sa.vix.com>
 <v04220802bafb769cd6b7@[192.168.1.14]>
 <p05100306bafd3c440103@[128.89.88.34]>
Date: Fri, 30 May 2003 15:10:42 -0700
To: ietf@ietf.org
From: Einar Stefferud <Steflist@thor.nma.com>
Subject: Re: requiring payment (was spam)
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

Pity the poor Zealot; who, when he loses sight of his objective,
simply redoubles his efforts.

For sure, do not let any new ideas leak into the IETF!

Cheers...\Stef


At 12:52 -0400 5/30/03, Stephen Kent wrote:
>At 1:36 AM -0700 5/29/03, Einar Stefferud wrote:
>>I suggest that those who wish to more fully understand all this trust stuff might find it useful to look at http://mcg.org.br/.
>>
>>Cheers...\Stef
>>
>>
>
>I would recommend this web site only to folks who want to see a very narrow view of what trust and certification are about, a view not consistent with most standards in the PKI arena, and one not shared by most legal experts, ...
>
>Steve




From owner-ietf@ietf.org  Fri May 30 19:12:16 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02645
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 19:12:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LssJ-000419-Rk
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 19:01:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LsLc-00038m-3y
	for ietf@asgard.ietf.org; Fri, 30 May 2003 18:27:40 -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 SAA01746
	for <ietf@ietf.org>; Fri, 30 May 2003 18:27:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LsJx-0002Co-00
	for ietf@ietf.org; Fri, 30 May 2003 18:25:57 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LsJx-0002CY-00
	for ietf@ietf.org; Fri, 30 May 2003 18:25:57 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id SAA17177;
	Fri, 30 May 2003 18:23:24 -0400
Date: Fri, 30 May 2003 18:24:30 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: John C Klensin <john-ietf@jck.com>
cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: Answering questions and defamation (was: RE: The utilitiy of IP
 is at stake here)
In-Reply-To: <267841966.1054312648@p3.JCK.COM>
Message-ID: <Pine.LNX.4.44.0305301734560.21528-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


On Fri, 30 May 2003, John C Klensin wrote:

> --On Friday, 30 May, 2003 16:01 -0400 Dean Anderson
> <dean@av8.com> wrote:
>
> > I haven't repeatedly (or at all) defamed anyone.
>
> You have repeatedly made public statements about what I don't
> know, what experience I lack, etc.

You have made incorrect claims about the difficulty of tracing an IP
address.  This suggests a lack of operational experience in tracing IP
addresses. But I concede I don't know your full resume and I could be
wrong about your operational experience tracing abusers.  Writing RFC's,
inventing protocols, and chairing standards bodies, and managing large
groups of people, and high level talks with the FBI does not seem to be
relevent experience.  So far, you haven't sent anything (despite a very
impressive resume) that seems to be relevant experience in tracking
abusers.

But whatever direct experience you do have doing such things, you are
_still_ *wrong* about the *difficulty and expense* of doing them. If you
do have experience tracking criminal abusers, where you found it was
expensive, I would say that perhaps you were doing something wrong, and
making it more difficult than it needs to be.

In any case, arguing about what your experience is deflects attention from
the question of whether it is expensive to track down an IP address, and
is irrelevant to the question of whether an open relay allows a user to
send anonymous email.

> I have questioned the facts you report, but have not made any public
> claims that you lack sufficient background to know what you are talking
> about.

You've questioned them, but only to say they are wrong and the go into
irrelevant detail about Asian ISPs and such.

> > And I also would like to initiate a formal complaint.
>
> Oh, goodie.   In the interesting of getting resolution, and to
> preserve everyone's sanity in the interim, I'm going to make no
> further postings on these threads until Harald, or someone else,
> indicate how he (or they) intend to sort this out.

OK by me. I will do the same.

> > You haven't answered the question.  The answer you gave was
> > irrelevant to the question, and doesn't support your wrong
> > assertion that open relays allow one to send anonymous email
> > without the IP address of the sender.
>
> What I told you, at some length if I recall, in a private note,
> is that

You didn't say (except for the very last) the things below in any private
message to me. I will be happy to post them on the web, so that people can
see what you wrote off list. What you wrote is rather condencending, while
I have be respectful, if direct.

Some of your claims below are true statements, but are irrelevant to the
question of whether an open relay alters the property of a users'
anonymity.

> * Only the IP address recorded in a Received field by the SMTP
> server that last accepts the message for delivery to you can
> generally be considered reliable and trustworthy.

This is not so. All Recieved headers inserted *after* the spammer has
released the message are trustworthy, since the spammer can only insert
false headers, but cannot modify anything after they send the message.

> * Received fields --other than, again, the one that you own
> server inserts-- are routinely faked in some varieties of spam.

No. again, modification isn't possible *after* the spammer sends the
message.  See above.

> * While it is not easy when a multiple-transaction TCP-based
> protocol like SMTP is involved, IP addresses can be faked.

Faking TCP connections is difficult, and not relevant to the question of
whether Open relay allows anonymous email.  If IP addresses are faked,
they are faked regardless of whether open relays are used. Nothing is
altered by open relays.

> * Obtaining the IP address of a client does not permit
> identifying a specific user, unless the owner/provider of that

This may be true in some (few) situations, such as the Asian ISP you
mentioned.  But, this is *still irrelevant* to the question of open relay
allows anonymous email. As I pointed out, previously. You are just
repeating canards, rather than addressing the issue of relevance.





From owner-ietf@ietf.org  Fri May 30 19:15:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02867
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 19:15:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LssK-00041e-6V
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 19:01:28 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LsN9-00039I-DY
	for ietf@asgard.ietf.org; Fri, 30 May 2003 18:29:15 -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 SAA01763
	for <ietf@ietf.org>; Fri, 30 May 2003 18:29:12 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LsLV-0002DH-00
	for ietf@ietf.org; Fri, 30 May 2003 18:27:33 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LsLU-0002DE-00
	for ietf@ietf.org; Fri, 30 May 2003 18:27:32 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h4UMT26n004706;
	Fri, 30 May 2003 18:29:02 -0400
Message-Id: <200305302229.h4UMT26n004706@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: ietf@ietf.org
Subject: Re: The utilitiy of IP is at stake here 
In-Reply-To: Your message of "Fri, 30 May 2003 15:53:10 MDT."
             <200305302153.h4ULrATA019693@calcite.rhyolite.com> 
References: <3ED7A03C.1040603@ehsco.com>
            <200305302153.h4ULrATA019693@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1437183404P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 30 May 2003 18:29:02 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_1437183404P
Content-Type: text/plain; charset=us-ascii

On Fri, 30 May 2003 15:53:10 MDT, Vernon Schryver <vjs@calcite.rhyolite.com>  said:

> That's true only if you accept stuff in the mass media uncritically.
> The mass media frequently get almost every thing else wrong by many
> orders of magnitude, so why pick this tidbit to believe?
> For Heaven's sake!  Do a sanity check and think about how you would
> spend $0.5B on filtering spam.

I'd believe $500M on a forklift upgrade of the entire Hotmail/MSN infrastructure
if it had to deal with both the added volume of mail and the added resource
expense of filtering spam.  If they're seeing 2G spams/day, they're doing
about 2,000 times our volume - and our mail hub setup is about $500K (and
those of you who say that's too expensive, tough ;).  So they're about 1,000
times as much money for 2,000 as much volume - so in the right ballbark.

--==_Exmh_1437183404P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+19sucC3lWbTT17ARAjL4AJ4icV6UPDrgHxy6+xEV3A6QiR0aPQCePFa8
YUQ2BTq+fJ/FIvoNquwf7mI=
=TXR6
-----END PGP SIGNATURE-----

--==_Exmh_1437183404P--



From owner-ietf@ietf.org  Fri May 30 19:38:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03380
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 19:38:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lt5a-0005On-Iq
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 19:15:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Lt3T-0005DB-PO
	for ietf@asgard.ietf.org; Fri, 30 May 2003 19:12:59 -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 TAA02694
	for <ietf@ietf.org>; Fri, 30 May 2003 19:12:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lt1p-0002Rz-00
	for ietf@ietf.org; Fri, 30 May 2003 19:11:17 -0400
Received: from [208.184.79.11] (helo=clint.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lt1o-0002R2-00
	for ietf@ietf.org; Fri, 30 May 2003 19:11:16 -0400
Received: from bbprime (208.184.79.253.songbird.com [208.184.79.253] (may be forged))
	by clint.songbird.com (8.11.6/8.11.6) with ESMTP id h4UNFFx12751;
	Fri, 30 May 2003 16:15:15 -0700
Date: Fri, 30 May 2003 16:12:24 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <13622120747.20030530161224@brandenburg.com>
To: Paul Hoffman / IMC <phoffman@imc.org>
CC: ietf@ietf.org
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <p05210607bafd52b3d9b3@[63\.202\.92\.152]>
References: <00e901c3261b$a3dbcf50$56144104@eagleswings>
 <127103972754.20030529132930@brandenburg.com>  <3ED699EB.8090005@ehsco.com>
 <115140380105.20030529233617@brandenburg.com>
 <p05210603bafd388cbb49@[63.202.92.152]> <3ED79782.195F1A20@earthlink.net>
 <p05210607bafd52b3d9b3@[63.202.92.152]>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Paul,

PHI> All my discussions were not for attribution. Large mail carriers
PHI> don't want their competitors to know how many users they actually 
PHI> have (as compared to the highly inflated numbers that various 
PHI> analysts say they have), and they certainly don't want their 
PHI> competitors knowing how much they are spending on dealing with spam.


Perhaps you could synthesize the numbers in a way that the carriers will
agree to?   That it, sanitize out the competitive information, to
produce something relevant only to spam control in the aggregate.

For example, if you offer a numeric range for cost per use, this says
nothing about how large anyone's installed base in, and they only need
to agree to you that their number is within the range.



d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Fri May 30 19:48:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03688
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 19:48:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LtTl-0006hF-D9
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 19:40:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LtCx-0005rB-F4
	for ietf@asgard.ietf.org; Fri, 30 May 2003 19:22:47 -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 TAA03056
	for <ietf@ietf.org>; Fri, 30 May 2003 19:22:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LtBJ-0002Xz-00
	for ietf@ietf.org; Fri, 30 May 2003 19:21:05 -0400
Received: from [208.184.79.11] (helo=clint.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LtBI-0002Xv-00
	for ietf@ietf.org; Fri, 30 May 2003 19:21:04 -0400
Received: from bbprime (208.184.79.253.songbird.com [208.184.79.253] (may be forged))
	by clint.songbird.com (8.11.6/8.11.6) with ESMTP id h4UNP2x13247;
	Fri, 30 May 2003 16:25:03 -0700
Date: Fri, 30 May 2003 16:22:11 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <2122707842.20030530162211@brandenburg.com>
To: "Tony Hain" <alh-ietf@tndh.net>
CC: "'IETF'" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <000a01c326d1$47cddd00$56144104@eagleswings>
References: <000a01c326d1$47cddd00$56144104@eagleswings>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony,


>> The POP->IMAP example is excellent, since it really
>> demonstrates my point. IMAP is rather popular in some local 
TH> Could that be because from the end user perspective IMAP doesn't provide

somehow I can't imagine that it would be useful to the main line of this
thread to explore reasons for particular outcomes.

I asked for examples. Some were offered. I believe none demonstrate what
I asked for. All the rest is secondary to an already-congested thread
(though entirely worthy of an extended bar bof.)


>> Seriously folks, if discussion about changes is going to be
>> productive, it needs to pay much more realistic attention to 
>> history and pragmatics of ISP operations and average-user preferences.
...
TH> the few times there are requirements docs the IETF has a history of
TH> discounting the needs of the end user or network operator, while it
TH> places a premium on minimizing developer effort.

One of the things that cropped up during the Problem WG "editing team"
discussions was a view that Operators used to be an integral part of the
IETF -- ie, "insiders" -- but have moved to be customers of our work and
not much involved in the creation of it.  As the IETF tries to find way
to check with its customers about needs, benefits, etc., we need to make
sure to count operators in that market research.


TH> The IETF is in a difficult spot, because the customer of the IETF is the
TH> vendor developer

certainly folks who create software are our immediate customers, but the
folks they produce software for are our ultimate customers.

d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Fri May 30 20:17:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04448
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 20:17:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LtlM-0007U1-GM
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 19:58:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LtZp-0006rb-C0
	for ietf@asgard.ietf.org; Fri, 30 May 2003 19:46:25 -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 TAA03620
	for <ietf@ietf.org>; Fri, 30 May 2003 19:46:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LtYB-0002iL-00
	for ietf@ietf.org; Fri, 30 May 2003 19:44:43 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LtYA-0002iD-00
	for ietf@ietf.org; Fri, 30 May 2003 19:44:42 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4UNkMKk053581
	for <ietf@ietf.org>; Sat, 31 May 2003 01:46:22 +0200 (CEST)
Message-ID: <0b2901c32705$ad1dffd0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <51909D9AC2941E4F9D35B264D12CD7C2590D1F@sl6exch3.savvis.ad.savvis.net>
Subject: Re: The utilitiy of ietf@ietf.org is at stake here
Date: Sat, 31 May 2003 01:46:22 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Delete keys are very handy as a traffic-control device.

----- Original Message -----
From: "Schliesser, Benson" <benson.schliesser@Savvis.net>
To: <ietf@ietf.org>
Sent: Friday, May 30, 2003 19:07
Subject: RE: The utilitiy of ietf@ietf.org is at stake here


> This is an important topic. However, it's crossed a certain traffic
threshold, to where I would vote to see it moved to a more appropriate forum
than the IETF general discussion list...
>
>
>




From owner-ietf@ietf.org  Fri May 30 20:17:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04457
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 20:17:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LtlM-0007Tq-88
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 19:58:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LtZ5-0006rU-Dq
	for ietf@asgard.ietf.org; Fri, 30 May 2003 19:45:39 -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 TAA03604
	for <ietf@ietf.org>; Fri, 30 May 2003 19:45:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LtXR-0002hm-00
	for ietf@ietf.org; Fri, 30 May 2003 19:43:57 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LtXQ-0002hi-00
	for ietf@ietf.org; Fri, 30 May 2003 19:43:56 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4UNjbKk053576
	for <ietf@ietf.org>; Sat, 31 May 2003 01:45:37 +0200 (CEST)
Message-ID: <0b1c01c32705$91cb5ed0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <00e901c3261b$a3dbcf50$56144104@eagleswings> <127103972754.20030529132930@brandenburg.com> <3ED699EB.8090005@ehsco.com> <115140380105.20030529233617@brandenburg.com> <p05210603bafd388cbb49@[63.202.92.152]>
Subject: Re: The utilitiy of IP is at stake here
Date: Sat, 31 May 2003 01:45:36 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Paul writes:

> The benefits of IMAP are obvious to everyone who has
> looked at it in any depth, and yet it is very thinly
> deployed. The main reason: the perceived additional
> administrative overhead.

A more significant reason, perhaps:  IMAP is a solution looking for a
problem, in most cases.  POP3 provides a way to move mail from a server to a
user agent, and that is all that is really required for 99% of all users.

Organizations that use IMAP are often in a position to simply adopt a
proprietary system with even more advanced functionality, such as Notes or
Exchange.  The average Internet user, however, has little incentive or need
to try IMAP.

> But they believe that the overhead of the needed
> trust system, and the cost of losing mail that didn't
> go through the trust system, is simply too high.

I agree.  Doing much more than they are doing now would get very expensive,
very quickly.




From owner-ietf@ietf.org  Fri May 30 20:18:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04582
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 20:18:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LtlN-0007Wg-MK
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 19:58:21 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ltew-0007L0-Er
	for ietf@asgard.ietf.org; Fri, 30 May 2003 19:51:42 -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 TAA03834
	for <ietf@ietf.org>; Fri, 30 May 2003 19:51:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LtdI-0002mF-00
	for ietf@ietf.org; Fri, 30 May 2003 19:50:00 -0400
Received: from out001pub.verizon.net ([206.46.170.140] helo=out001.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LtdH-0002mB-00
	for ietf@ietf.org; Fri, 30 May 2003 19:49:59 -0400
Received: from earthlink.net ([4.65.81.213]) by out001.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030530235110.NHZJ12592.out001.verizon.net@earthlink.net>;
          Fri, 30 May 2003 18:51:10 -0500
Message-ID: <3ED7ED58.12E798F5@earthlink.net>
Date: Fri, 30 May 2003 16:46:32 -0700
From: Peter Deutsch <pdeutsch@earthlink.net>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Paul Hoffman / IMC <phoffman@imc.org>
CC: ietf@ietf.org
Subject: Re: The utilitiy of IP is at stake here
References: <00e901c3261b$a3dbcf50$56144104@eagleswings>	
	 <127103972754.20030529132930@brandenburg.com>	
	 <3ED699EB.8090005@ehsco.com>
	 <115140380105.20030529233617@brandenburg.com>
	 <p05210603bafd388cbb49@[63.202.92.152]> <3ED79782.195F1A20@earthlink.net> <p05210607bafd52b3d9b3@[63.202.92.152]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [4.65.81.213] at Fri, 30 May 2003 18:51:09 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

g'day,

Paul Hoffman / IMC wrote:
> 
> At 10:40 AM -0700 5/30/03, Peter Deutsch wrote:
> >Paul Hoffman / IMC wrote:
> >...
> >Well, perhaps it's more accurate to say "if they thought it could be
> >solved by working with all those nice and entusiastic folks on the IETF
> >general discussion list"... ;-)
> 
> We disagree here. For the millions of dollars that they are losing,
> they would come up with the solution with the IETF or not. They
> haven't.
... 
> Again, the summary is that these folks are hurting badly enough to
> throw highly-qualified full-time staff on the problem, and they don't
> believe any of the solutions that have been presented so far will
> save them enough money. If they thought differently, they would have
> deployed them by now so that they could save those millions of
> dollars.

Then we're actually in agreement. What I was trying to point out was
these folks are spending money on the problem, but aren't trying to
engineer the solution on the IETF general mailing list (the
implicationbeing that we probably shouldn't be trying to do this
either). And yes, I know I'm one of those who's been guilty of this,
although my motivation was more to change the direction of thought, not
to bake a solution here.

Thanks for what info you provided, although I echo DaveC's request for
whatever additional info you could manage. I think this sort of thing
provides a welcome dose of reality in the debate. Any solution which
requires solutions beyond the costs aren't likely to thrive, whether
that's the cost to an individual or to a major ISP. Having such real
data helps constrain the engineering usefully, to say the least, given
the amount of anecdotal "but I haven't seen that" going on.


					- peterd



-- 
---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software

   "The invisible and the non-existent look very much alike." 

                                -- Delo McKown  
---------------------------------------------------------------------



From owner-ietf@ietf.org  Fri May 30 20:23:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05002
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 20:23:34 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ltyl-0008Pq-CF
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 20:12:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LtiY-0007MV-Je
	for ietf@asgard.ietf.org; Fri, 30 May 2003 19:55:26 -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 TAA03864
	for <ietf@ietf.org>; Fri, 30 May 2003 19:55:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ltgu-0002nE-00
	for ietf@ietf.org; Fri, 30 May 2003 19:53:44 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ltgt-0002nB-00
	for ietf@ietf.org; Fri, 30 May 2003 19:53:43 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4UNtNKk053661
	for <ietf@ietf.org>; Sat, 31 May 2003 01:55:23 +0200 (CEST)
Message-ID: <0b3901c32706$ef39b750$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <001a01c326d6$9dfe6e60$56144104@eagleswings>
Subject: Re: The utilitiy of IP is at stake here
Date: Sat, 31 May 2003 01:55:23 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony writes:

> And that would be because they can't do it in
> isolation.

AOL, to cite one example, does a lot of things in isolation.  They don't
seem to care if the rest of the Internet goes along, nor do they wait for
any system-wide standards to be put in place before they act unilaterally.
So I don't think that is a problem.

> Taken another way, how would the IETF react if the
> large carriers decided to go off and solve this problem
> amongst themselves with an undocumented protocol?

They already have, with open-relay lists and "residential" blacklists and so
on.  They don't care what the IETF thinks about it, and I don't see much
reaction in turn on the part of the IETF, either.

> I predict there would be an outcry that the big
> players were ignoring standards and bullying the
> market place.

And what would that change?  Would AOL start letting small businesses send
e-mail to its customers again?

> The real cost is not in the big carrier equipment or
> engineering, it is in the millions of person hours
> per day lost to configuring filters, waiting for the
> delivery of what gets past the filters, and hitting
> delete ~100 times.

That isn't millions of hours per day.  I get hundreds of spam messages a
day, and it only takes me a minute or two each day to delete them; often not
even that.  The filters are set up just once.

I think there is a great tendency to confuse annoyance with real, tangible
losses (of time or money).

I find television commercials to be a tremendous annoyance, but they don't
cause me any losses.  And it's interesting that nobody seems to object to
them, even though television programs are interrupted literally every few
minutes by them (which, when you think about it, is exceedingly bizarre).





From owner-ietf@ietf.org  Fri May 30 20:28:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05225
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 20:28:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lu6S-0001Y2-JH
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 20:20:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LtmT-0007Wp-TR
	for ietf@asgard.ietf.org; Fri, 30 May 2003 19:59:29 -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 TAA03923
	for <ietf@ietf.org>; Fri, 30 May 2003 19:59:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ltkp-0002nq-00
	for ietf@ietf.org; Fri, 30 May 2003 19:57:47 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ltko-0002nn-00
	for ietf@ietf.org; Fri, 30 May 2003 19:57:46 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4UNxRKk053685
	for <ietf@ietf.org>; Sat, 31 May 2003 01:59:27 +0200 (CEST)
Message-ID: <0b4a01c32707$80b5fa90$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <20030530184722.2F34518F0@thrintun.hactrn.net>
Subject: Re: Last 7 days on the IETF list
Date: Sat, 31 May 2003 01:59:27 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Now post the same numbers for the past year, and perhaps some even more
interesting conclusions can be drawn.

----- Original Message -----
From: "Rob Austein" <sra+ietf@hactrn.net>
To: <ietf@ietf.org>
Sent: Friday, May 30, 2003 20:47
Subject: Last 7 days on the IETF list


> Traffic statistics (as seen from my cave, your milage may vary) for
> the last seven days on the ietf@ietf.org mailing list.
>
> Conclusions, if any, are left as an exercise for the reader.
>
>
>   Messages   |     Bytes       | Who
> -------+-----+-------+---------+------------------------
>  11.4% |  53 | 13.9% |  233614 | dean@av8.com
>  12.2% |  57 | 10.1% |  170963 | anthony@atkielski.com
>   7.5% |  35 |  7.2% |  121074 | ehall@ehsco.com
>   3.0% |  14 |  4.8% |   80253 | pdeutsch@earthlink.net
>   3.9% |  18 |  3.6% |   60755 | valdis.kletnieks@vt.edu
>   3.4% |  16 |  3.5% |   58293 | alh-ietf@tndh.net
>   3.6% |  17 |  2.6% |   43278 | michel@arneill-py.sacramento.ca.us
>   2.8% |  13 |  2.2% |   37288 | moore@cs.utk.edu
>   2.4% |  11 |  2.3% |   37930 | dwm@xpasc.com
>   2.1% |  10 |  2.2% |   37479 | vjs@calcite.rhyolite.com
>   2.1% |  10 |  2.2% |   36561 | iljitsch@muada.com
>   2.1% |  10 |  1.9% |   31676 | l.wood@eim.surrey.ac.uk
>   1.9% |   9 |  1.8% |   31053 | shogunx@sleekfreak.ath.cx
>   1.9% |   9 |  1.8% |   31016 | vixie@vix.com
>   1.9% |   9 |  1.7% |   27856 | dhc2@dcrocker.net
>   1.9% |   9 |  1.6% |   27349 | dja2003@hotpop.com
>   1.9% |   9 |  1.5% |   24511 | sbwoodside@yahoo.com
>   1.1% |   5 |  2.1% |   34761 | steflist@thor.nma.com
>   1.7% |   8 |  1.3% |   21321 | jnc@ginger.lcs.mit.edu
>   1.3% |   6 |  1.7% |   28495 | richard@shockey.us
>   1.3% |   6 |  1.2% |   19636 | tomson_eric@yahoo.fr
>   1.3% |   6 |  1.1% |   19259 | jstracke@centive.com
>   0.9% |   4 |  1.5% |   24586 | john-ietf@jck.com
>   1.1% |   5 |  1.0% |   16989 | mat@cisco.com
>   0.9% |   4 |  0.9% |   15992 | avi@bridgewatersystems.com
>   0.9% |   4 |  0.9% |   14418 | huitema@windows.microsoft.com
>   0.9% |   4 |  0.8% |   13896 | phoffman@imc.org
>   0.9% |   4 |  0.7% |   12281 | dee3@torque.pothole.com
>   0.9% |   4 |  0.7% |   11323 | ietf@soaring.demon.co.uk
>   0.9% |   4 |  0.7% |   11275 | tjc@ecs.soton.ac.uk
>   0.6% |   3 |  0.8% |   13511 | darkuncle@darkuncle.net
>   0.6% |   3 |  0.7% |   12302 | harald@alvestrand.no
>   0.4% |   2 |  0.9% |   14402 | dws@hunnysoft.com
>   0.4% |   2 |  0.8% |   14209 | mohta@necom830.hpcl.titech.ac.jp
>   0.6% |   3 |  0.6% |   10191 | wessorh@ar.com
>   0.6% |   3 |  0.6% |   10181 | rwelty@averillpark.net
>   0.6% |   3 |  0.5% |    9109 | lear@cisco.com
>   0.6% |   3 |  0.5% |    8328 | john.loughney@kolumbus.fi
>   0.6% |   3 |  0.5% |    7803 | sommerfeld@orchard.arlington.ma.us
>   0.6% |   3 |  0.5% |    7584 | billc44@citynet.net
>   0.6% |   3 |  0.4% |    6866 | randy@psg.com
>   0.2% |   1 |  0.8% |   13680 | soohong.park@samsung.com
>   0.4% |   2 |  0.5% |    8935 | stephen@sprunk.org
>   0.4% |   2 |  0.5% |    7722 | tytso@mit.edu
>   0.4% |   2 |  0.5% |    7620 | rra@stanford.edu
>   0.4% |   2 |  0.4% |    6916 | jmorris@cdt.org
>   0.4% |   2 |  0.4% |    6630 | dank@hq.lindsayelec.com
>   0.4% |   2 |  0.4% |    6470 | dominic.pinto@ieee.org
>   0.4% |   2 |  0.4% |    6156 | zefram@fysh.org
>   0.2% |   1 |  0.6% |    9711 | awduche@awduche.com
>   0.4% |   2 |  0.3% |    5077 | bmanning@isi.edu
>   0.4% |   2 |  0.3% |    4924 | fritz_saad@hotmail.com
>   0.4% |   2 |  0.3% |    4618 | ekr@rtfm.com
>   0.4% |   2 |  0.3% |    4576 | cdel@firsthand.net
>   0.4% |   2 |  0.3% |    4438 | anewton@ecotroph.net
>   0.4% |   2 |  0.3% |    4335 | garmitage@swin.edu.au
>   0.2% |   1 |  0.5% |    7750 | alain.durand@sun.com
>   0.2% |   1 |  0.4% |    7195 | dws+001@hunnysoft.com
>   0.2% |   1 |  0.4% |    6953 | bob@wyman.us
>   0.2% |   1 |  0.4% |    6315 | ggm@apnic.net
>   0.2% |   1 |  0.4% |    6293 | et7563@sbc.com
>   0.2% |   1 |  0.4% |    6003 | atul.sabharwal@intel.com
>   0.2% |   1 |  0.3% |    5766 | hardie@qualcomm.com
>   0.2% |   1 |  0.3% |    5699 | dhc@dcrocker.net
>   0.2% |   1 |  0.3% |    5206 | cchaplin@sj.symbol.com
>   0.2% |   1 |  0.3% |    4923 | peterf@exchange.microsoft.com
>   0.2% |   1 |  0.3% |    4425 | page@mail.msen.com
>   0.2% |   1 |  0.3% |    4388 | braendt@hotmail.com
>   0.2% |   1 |  0.3% |    4306 | gk@ninebynine.org
>   0.2% |   1 |  0.2% |    4096 | jorge.contreras@haledorr.com
>   0.2% |   1 |  0.2% |    3465 | inanbe@xs4all.nl
>   0.2% |   1 |  0.2% |    3310 | hinden@iprg.nokia.com
>   0.2% |   1 |  0.2% |    3214 | smb@research.att.com
>   0.2% |   1 |  0.2% |    3194 | gray@washington.edu
>   0.2% |   1 |  0.2% |    3085 | ole@cisco.com
>   0.2% |   1 |  0.2% |    3077 | rod.walsh@nokia.com
>   0.2% |   1 |  0.2% |    2958 | msa@burp.tkv.asdf.org
>   0.2% |   1 |  0.2% |    2946 | vinton.g.cerf@mci.com
>   0.2% |   1 |  0.2% |    2782 | swb@employees.org
>   0.2% |   1 |  0.2% |    2761 | jtk@depaul.edu
>   0.2% |   1 |  0.2% |    2661 | bob.natale@appliedsnmp.com
>   0.2% |   1 |  0.2% |    2621 | spencer_dawkins@yahoo.com
>   0.2% |   1 |  0.1% |    2510 | glc@cisco.com
>   0.2% |   1 |  0.1% |    2416 | klensin@jck.com
>   0.2% |   1 |  0.1% |    2323 | braden@isi.edu
>   0.2% |   1 |  0.1% |    2303 | kent@bbn.com
>   0.2% |   1 |  0.1% |    2265 | andy.malis@vivacenetworks.com
>   0.2% |   1 |  0.1% |    2259 | jfbauer@comcast.net
>   0.2% |   1 |  0.1% |    2175 | benson.schliesser@savvis.net
>   0.2% |   1 |  0.1% |    1789 | noc@nso.org
> -------+-----+-------+---------+------------------------
> 100.0% | 466 |100.0% | 1684907 | Total
>
>




From owner-ietf@ietf.org  Fri May 30 20:39:05 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05571
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 20:39:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lu6T-0001ZQ-7j
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 20:20:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Lts4-0008H7-GP
	for ietf@asgard.ietf.org; Fri, 30 May 2003 20:05:16 -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 UAA04147
	for <ietf@ietf.org>; Fri, 30 May 2003 20:05:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LtqQ-0002sH-00
	for ietf@ietf.org; Fri, 30 May 2003 20:03:34 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LtqP-0002sE-00
	for ietf@ietf.org; Fri, 30 May 2003 20:03:33 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4V05EKk053740
	for <ietf@ietf.org>; Sat, 31 May 2003 02:05:14 +0200 (CEST)
Message-ID: <0b5e01c32708$4f5f67a0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.44.0305301553050.17819-100000@commander.av8.net>
Subject: Re: The utilitiy of IP is at stake here
Date: Sat, 31 May 2003 02:05:13 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I haven't repeatedly (or at all) defamed anyone.

While I don't recall reading the original posts, you've backquoted text you
wrote yourself in which you cast aspersions upon others, which is
defamation.  Speculating that someone lacks experience or that what he has
written is "nonsense" falls into this category.

> And I also would like to initiate a formal complaint.

Formal complaints of defamation generally must be based on clear evidence of
damages.  Unless you've lost a job or someone has slashed your tires or
something because of posts on this list, a "formal complaint" really doesn't
serve any purpose.

I suggest that everyone here be a lot less sensitive, and try a lot harder
to stick to the discussion, minus the personal attacks.  It's easy enough to
say "I don't agree with you" without adding "because I think you're stupid."




From owner-ietf@ietf.org  Fri May 30 20:59:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06034
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 20:59:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lub6-0004R4-WB
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 20:51:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LuUQ-00046n-FL
	for ietf@asgard.ietf.org; Fri, 30 May 2003 20:44:54 -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 UAA05846
	for <ietf@ietf.org>; Fri, 30 May 2003 20:44:52 -0400 (EDT)
From: william@elan.net
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LuSm-0003NF-00
	for ietf@ietf.org; Fri, 30 May 2003 20:43:12 -0400
Received: from sokol.elan.net ([216.151.192.200])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LuSl-0003NC-00
	for ietf@ietf.org; Fri, 30 May 2003 20:43:11 -0400
Received: from sokol.elan.net (localhost.localdomain [127.0.0.1])
	by sokol.elan.net (8.12.5/8.12.5) with ESMTP id h4V0hlli007053;
	Fri, 30 May 2003 17:43:47 -0700
Received: from localhost (william@localhost)
	by sokol.elan.net (8.12.5/8.12.5/Submit) with ESMTP id h4V0hkRx007049;
	Fri, 30 May 2003 17:43:47 -0700
X-Authentication-Warning: sokol.elan.net: william owned process doing -bs
Date: Fri, 30 May 2003 17:43:46 -0700 (PDT)
To: Rob Austein <sra+ietf@hactrn.net>
cc: ietf@ietf.org
Subject: Re: Last 7 days on the IETF list
In-Reply-To: <20030530184722.2F34518F0@thrintun.hactrn.net>
Message-ID: <Pine.LNX.4.44.0305301736050.20347-100000@sokol.elan.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

I don't think posting message size is quite appropriate as part of your
statistics and even more particularly as a criteria to order the list. 
Unless I'm mistaken you're calculating bytes for entire message but often 
> 75% comes from another message being replied to and so you can't really 
judge amount of input the actual poster added to the message. If you want 
message bytes statistics, you could try to see what parts of that were 
not from previous message and only calculate size based on that.

On Fri, 30 May 2003, Rob Austein wrote:

> Traffic statistics (as seen from my cave, your milage may vary) for
> the last seven days on the ietf@ietf.org mailing list.
> 
> Conclusions, if any, are left as an exercise for the reader.
> 
> 
>   Messages   |     Bytes       | Who
> -------+-----+-------+---------+------------------------
>  11.4% |  53 | 13.9% |  233614 | dean@av8.com
>  12.2% |  57 | 10.1% |  170963 | anthony@atkielski.com
>   7.5% |  35 |  7.2% |  121074 | ehall@ehsco.com
>   3.0% |  14 |  4.8% |   80253 | pdeutsch@earthlink.net
>   3.9% |  18 |  3.6% |   60755 | valdis.kletnieks@vt.edu
>   3.4% |  16 |  3.5% |   58293 | alh-ietf@tndh.net
>   3.6% |  17 |  2.6% |   43278 | michel@arneill-py.sacramento.ca.us
>   2.8% |  13 |  2.2% |   37288 | moore@cs.utk.edu
>   2.4% |  11 |  2.3% |   37930 | dwm@xpasc.com
>   2.1% |  10 |  2.2% |   37479 | vjs@calcite.rhyolite.com
>   2.1% |  10 |  2.2% |   36561 | iljitsch@muada.com
>   2.1% |  10 |  1.9% |   31676 | l.wood@eim.surrey.ac.uk
>   1.9% |   9 |  1.8% |   31053 | shogunx@sleekfreak.ath.cx
>   1.9% |   9 |  1.8% |   31016 | vixie@vix.com
>   1.9% |   9 |  1.7% |   27856 | dhc2@dcrocker.net
>   1.9% |   9 |  1.6% |   27349 | dja2003@hotpop.com
>   1.9% |   9 |  1.5% |   24511 | sbwoodside@yahoo.com
>   1.1% |   5 |  2.1% |   34761 | steflist@thor.nma.com
>   1.7% |   8 |  1.3% |   21321 | jnc@ginger.lcs.mit.edu
>   1.3% |   6 |  1.7% |   28495 | richard@shockey.us
>   1.3% |   6 |  1.2% |   19636 | tomson_eric@yahoo.fr
>   1.3% |   6 |  1.1% |   19259 | jstracke@centive.com
>   0.9% |   4 |  1.5% |   24586 | john-ietf@jck.com
>   1.1% |   5 |  1.0% |   16989 | mat@cisco.com
>   0.9% |   4 |  0.9% |   15992 | avi@bridgewatersystems.com
>   0.9% |   4 |  0.9% |   14418 | huitema@windows.microsoft.com
>   0.9% |   4 |  0.8% |   13896 | phoffman@imc.org
>   0.9% |   4 |  0.7% |   12281 | dee3@torque.pothole.com
>   0.9% |   4 |  0.7% |   11323 | ietf@soaring.demon.co.uk
>   0.9% |   4 |  0.7% |   11275 | tjc@ecs.soton.ac.uk
>   0.6% |   3 |  0.8% |   13511 | darkuncle@darkuncle.net
>   0.6% |   3 |  0.7% |   12302 | harald@alvestrand.no
>   0.4% |   2 |  0.9% |   14402 | dws@hunnysoft.com
>   0.4% |   2 |  0.8% |   14209 | mohta@necom830.hpcl.titech.ac.jp
>   0.6% |   3 |  0.6% |   10191 | wessorh@ar.com
>   0.6% |   3 |  0.6% |   10181 | rwelty@averillpark.net
>   0.6% |   3 |  0.5% |    9109 | lear@cisco.com
>   0.6% |   3 |  0.5% |    8328 | john.loughney@kolumbus.fi
>   0.6% |   3 |  0.5% |    7803 | sommerfeld@orchard.arlington.ma.us
>   0.6% |   3 |  0.5% |    7584 | billc44@citynet.net
>   0.6% |   3 |  0.4% |    6866 | randy@psg.com
>   0.2% |   1 |  0.8% |   13680 | soohong.park@samsung.com
>   0.4% |   2 |  0.5% |    8935 | stephen@sprunk.org
>   0.4% |   2 |  0.5% |    7722 | tytso@mit.edu
>   0.4% |   2 |  0.5% |    7620 | rra@stanford.edu
>   0.4% |   2 |  0.4% |    6916 | jmorris@cdt.org
>   0.4% |   2 |  0.4% |    6630 | dank@hq.lindsayelec.com
>   0.4% |   2 |  0.4% |    6470 | dominic.pinto@ieee.org
>   0.4% |   2 |  0.4% |    6156 | zefram@fysh.org
>   0.2% |   1 |  0.6% |    9711 | awduche@awduche.com
>   0.4% |   2 |  0.3% |    5077 | bmanning@isi.edu
>   0.4% |   2 |  0.3% |    4924 | fritz_saad@hotmail.com
>   0.4% |   2 |  0.3% |    4618 | ekr@rtfm.com
>   0.4% |   2 |  0.3% |    4576 | cdel@firsthand.net
>   0.4% |   2 |  0.3% |    4438 | anewton@ecotroph.net
>   0.4% |   2 |  0.3% |    4335 | garmitage@swin.edu.au
>   0.2% |   1 |  0.5% |    7750 | alain.durand@sun.com
>   0.2% |   1 |  0.4% |    7195 | dws+001@hunnysoft.com
>   0.2% |   1 |  0.4% |    6953 | bob@wyman.us
>   0.2% |   1 |  0.4% |    6315 | ggm@apnic.net
>   0.2% |   1 |  0.4% |    6293 | et7563@sbc.com
>   0.2% |   1 |  0.4% |    6003 | atul.sabharwal@intel.com
>   0.2% |   1 |  0.3% |    5766 | hardie@qualcomm.com
>   0.2% |   1 |  0.3% |    5699 | dhc@dcrocker.net
>   0.2% |   1 |  0.3% |    5206 | cchaplin@sj.symbol.com
>   0.2% |   1 |  0.3% |    4923 | peterf@exchange.microsoft.com
>   0.2% |   1 |  0.3% |    4425 | page@mail.msen.com
>   0.2% |   1 |  0.3% |    4388 | braendt@hotmail.com
>   0.2% |   1 |  0.3% |    4306 | gk@ninebynine.org
>   0.2% |   1 |  0.2% |    4096 | jorge.contreras@haledorr.com
>   0.2% |   1 |  0.2% |    3465 | inanbe@xs4all.nl
>   0.2% |   1 |  0.2% |    3310 | hinden@iprg.nokia.com
>   0.2% |   1 |  0.2% |    3214 | smb@research.att.com
>   0.2% |   1 |  0.2% |    3194 | gray@washington.edu
>   0.2% |   1 |  0.2% |    3085 | ole@cisco.com
>   0.2% |   1 |  0.2% |    3077 | rod.walsh@nokia.com
>   0.2% |   1 |  0.2% |    2958 | msa@burp.tkv.asdf.org
>   0.2% |   1 |  0.2% |    2946 | vinton.g.cerf@mci.com
>   0.2% |   1 |  0.2% |    2782 | swb@employees.org
>   0.2% |   1 |  0.2% |    2761 | jtk@depaul.edu
>   0.2% |   1 |  0.2% |    2661 | bob.natale@appliedsnmp.com
>   0.2% |   1 |  0.2% |    2621 | spencer_dawkins@yahoo.com
>   0.2% |   1 |  0.1% |    2510 | glc@cisco.com
>   0.2% |   1 |  0.1% |    2416 | klensin@jck.com
>   0.2% |   1 |  0.1% |    2323 | braden@isi.edu
>   0.2% |   1 |  0.1% |    2303 | kent@bbn.com
>   0.2% |   1 |  0.1% |    2265 | andy.malis@vivacenetworks.com
>   0.2% |   1 |  0.1% |    2259 | jfbauer@comcast.net
>   0.2% |   1 |  0.1% |    2175 | benson.schliesser@savvis.net
>   0.2% |   1 |  0.1% |    1789 | noc@nso.org
> -------+-----+-------+---------+------------------------
> 100.0% | 466 |100.0% | 1684907 | Total
> 




From owner-ietf@ietf.org  Fri May 30 21:07:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04450
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 20:17:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LtlL-0007TP-UG
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 19:58:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LtVM-0006kg-N1
	for ietf@asgard.ietf.org; Fri, 30 May 2003 19:41:48 -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 TAA03546
	for <ietf@ietf.org>; Fri, 30 May 2003 19:41:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LtTi-0002gV-00
	for ietf@ietf.org; Fri, 30 May 2003 19:40:06 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LtTh-0002gR-00
	for ietf@ietf.org; Fri, 30 May 2003 19:40:05 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4UNfgKk053549
	for <ietf@ietf.org>; Sat, 31 May 2003 01:41:42 +0200 (CEST)
Message-ID: <0b1101c32705$05ba6fd0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <012e01c326c8$676edfa0$3500a8c0@tomson.be>
Subject: Re: The utilitiy of IP is at stake here
Date: Sat, 31 May 2003 01:41:41 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric writes:

> First, I sent my mail to the list to make public
> apologies for the public insult made to John on
> this list.

But you claim that Dean was the author of an insult.  How can you apologize
for him?  Are you his legal guardian?

> Second, the objective of this mail was not to discredit
> Dean ...

Yes, it was.  You included many negative comments on Dean that had no place
in your post (in fact, the post overall had no real purpose, since it was
mainly just a personal attack): "troll," "honest and decent contributor"
(implying that Dean was not in this category, "dishonest and undecent"
(adumbrating Dean), and so on.

Why not just stick to the discussion henceforth, and leave character
assassination out of it?





From owner-ietf@ietf.org  Fri May 30 21:12:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06431
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 21:12:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lub7-0004Ra-Co
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 20:51:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LuXY-0004HJ-1i
	for ietf@asgard.ietf.org; Fri, 30 May 2003 20:48:08 -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 UAA05902
	for <ietf@ietf.org>; Fri, 30 May 2003 20:48:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LuVt-0003OM-00
	for ietf@ietf.org; Fri, 30 May 2003 20:46:25 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LuVt-0003OJ-00
	for ietf@ietf.org; Fri, 30 May 2003 20:46:25 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S29B40> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Fri, 30 May 2003 17:48:02 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Anthony Atkielski'" <anthony@atkielski.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Fri, 30 May 2003 17:47:58 -0700
Message-ID: <007601c3270e$481afee0$56144104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <0b3901c32706$ef39b750$0a00000a@atkielski.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA06431

Anthony Atkielski wrote:
> That isn't millions of hours per day.  I get hundreds of spam 
> messages a day, and it only takes me a minute or two each day 
> to delete them; often not even that.  The filters are set up 
> just once.

100M users * 1/30hr = 3.3M hours   ; and that happens every day.

I have to adjust my filters at least once a month to keep the volume
down. If you have a set that only needs to be set up once, please share
them with the list. Maybe all the mail services could put those in place
and we wouldn't need to do anything more.

> 
> I think there is a great tendency to confuse annoyance with 
> real, tangible losses (of time or money).

There is also a tendancy to overlook the effects of real scale. 

> 
> I find television commercials to be a tremendous annoyance, 
> but they don't cause me any losses.  And it's interesting 
> that nobody seems to object to them, even though television 
> programs are interrupted literally every few minutes by them 
> (which, when you think about it, is exceedingly bizarre).

Clearly you have never heard of the devices designed to block
commercials ...





From owner-ietf@ietf.org  Fri May 30 21:13:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06488
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 21:13:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lurg-00057E-0t
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 21:08:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Lufu-0004Z4-QM
	for ietf@asgard.ietf.org; Fri, 30 May 2003 20:56:46 -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 UAA05962
	for <ietf@ietf.org>; Fri, 30 May 2003 20:56:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LueG-0003Pr-00
	for ietf@ietf.org; Fri, 30 May 2003 20:55:04 -0400
Received: from ds20-1.cc.swin.edu.au ([136.186.1.150] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LueF-0003Pn-00
	for ietf@ietf.org; Fri, 30 May 2003 20:55:03 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2/8.9.3) with ESMTP id KAA1773100;
	Sat, 31 May 2003 10:56:41 +1000 (EST)
Message-ID: <3ED7FDC9.AD3FDA0A@swin.edu.au>
Date: Sat, 31 May 2003 10:56:41 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: The utilitiy of ietf@ietf.org is at stake here
References: <51909D9AC2941E4F9D35B264D12CD7C2590D1F@sl6exch3.savvis.ad.savvis.net> <0b2901c32705$ad1dffd0$0a00000a@atkielski.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Anthony Atkielski wrote:
> 
> Delete keys are very handy as a traffic-control device.

You're so right.

*delete*  *delete*  *delete*  *delete*  *delete*  
*delete*  *delete*  *delete*  *delete*  *delete*  *delete*
*delete*  *delete*  [...god my fingers are getting tired! ]
*delete*  *delete*  *delete*  *delete*  *delete* ....

ah, bugger it. maybe i'll just filter out the top two or
three contributors on Rob Austein's recent list....

gja



From owner-ietf@ietf.org  Fri May 30 21:33:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06987
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 21:33:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lusw-0005FX-9J
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 21:10:14 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Luka-0004x3-1f
	for ietf@asgard.ietf.org; Fri, 30 May 2003 21:01:36 -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 VAA06239
	for <ietf@ietf.org>; Fri, 30 May 2003 21:01:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Luiv-0003U0-00
	for ietf@ietf.org; Fri, 30 May 2003 20:59:53 -0400
Received: from champdsl-25-66.mcleodusa.net ([216.43.25.66] helo=episteme-software.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Luiv-0003Tt-00
	for ietf@ietf.org; Fri, 30 May 2003 20:59:53 -0400
Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with
 ESMTP (Eudora Internet Mail Server X 3.2.2b1);
 Fri, 30 May 2003 20:00:58 -0500
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com
Message-Id: <p0600142bbafdab5a7bd4@[216.43.25.67]>
In-Reply-To: <Pine.LNX.4.44.0305301734560.21528-100000@commander.av8.net>
References: <Pine.LNX.4.44.0305301734560.21528-100000@commander.av8.net>
X-Mailer: Eudora [Macintosh version 6.0a15]
Date: Fri, 30 May 2003 20:01:18 -0500
To: Dean Anderson <dean@av8.com>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Answering questions and defamation (was: RE: The utilitiy of
 IP  is at stake here)
Cc: John C Klensin <john-ietf@jck.com>, "'IETF Discussion'" <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

On 5/30/03 at 6:24 PM -0400, Dean Anderson wrote:

>So far, you haven't sent anything (despite a very impressive resume) 
>that seems to be relevant experience in tracking abusers.

For some reason, Dean decided to start Cc'ing  his private mail 
conversation with John to me (I'm not sure exactly why), but because 
of that, I was privy to the e-mail in question and can't let the 
above statement pass.

Dean's above statement is patently false. John did provide (for 
Dean's reference, in message <152050487.1054196854@p3.JCK.COM>) 
absolutely relevant experience in tracking abusers in the mail to 
which he refers.

Given the large number of other false statements and invalid 
arguments in Dean's messages to this list, both on issues of 
substance and with regard to his personal attacks on John, I have 
decided not to engage with Dean publicly, though I have sent him 
private mail pointing out at least one of his invalid arguments. I 
suggest others might also benefit from subjecting Dean's messages to 
careful scrutiny; I have found them lacking in factual information 
and quite misleading.

pr
-- 
Pete Resnick <mailto:presnick@qualcomm.com>
QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102



From owner-ietf@ietf.org  Fri May 30 21:40:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07203
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 21:40:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LvCC-0006UQ-Cc
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 21:30:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LuwY-00061E-Lo
	for ietf@asgard.ietf.org; Fri, 30 May 2003 21:13:58 -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 VAA06615
	for <ietf@ietf.org>; Fri, 30 May 2003 21:13:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Luut-0003a3-00
	for ietf@ietf.org; Fri, 30 May 2003 21:12:15 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Luus-0003ZS-00
	for ietf@ietf.org; Fri, 30 May 2003 21:12:14 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4V1DeKk054768
	for <ietf@ietf.org>; Sat, 31 May 2003 03:13:40 +0200 (CEST)
Message-ID: <0b9001c32711$dee1c090$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <007601c3270e$481afee0$56144104@eagleswings>
Subject: Re: The utilitiy of IP is at stake here
Date: Sat, 31 May 2003 03:13:40 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony writes:

> 100M users * 1/30hr = 3.3M hours   ; and that
> happens every day.

Each day contains 100M x 24 = 2400 M hours.  3.3 M hours is thus 1/8 of 1
percent.

> I have to adjust my filters at least once a month
> to keep the volume down.

I just delete most of it by hand.  It's easy enough to recognize.

> There is also a tendancy to overlook the effects
> of real scale.

I see only speculation and exaggeration with respect to the cost of spam.
It's very annoying, but it's not very expensive.

> Clearly you have never heard of the devices designed
> to block commercials ...

I've heard of them, but they are not widely used.  Nor is anyone complaining
about advertising in magazines or newspapers, although often a large part of
both is taken up by it.




From owner-ietf@ietf.org  Fri May 30 21:48:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07421
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 21:48:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LvCC-0006VW-S8
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 21:30:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Luwn-00061e-J9
	for ietf@asgard.ietf.org; Fri, 30 May 2003 21:14:13 -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 VAA06678
	for <ietf@ietf.org>; Fri, 30 May 2003 21:14:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Luv9-0003b3-00
	for ietf@ietf.org; Fri, 30 May 2003 21:12:31 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Luv8-0003b0-00
	for ietf@ietf.org; Fri, 30 May 2003 21:12:30 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4V1EBKk054771
	for <ietf@ietf.org>; Sat, 31 May 2003 03:14:11 +0200 (CEST)
Message-ID: <0b9501c32711$f148c030$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.44.0305301553050.17819-100000@commander.av8.net> <0b5e01c32708$4f5f67a0$0a00000a@atkielski.com> <Pine.WNT.4.56.0305301746050.1436@TGX200>
Subject: Re: The utilitiy of IP is at stake here
Date: Sat, 31 May 2003 03:14:11 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Terry writes:

> True enough... but "You obviously have no experience..."
> is *real* close to "I think you're stupid".

I did not suggest otherwise.



From owner-ietf@ietf.org  Fri May 30 21:50:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07600
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 21:50:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LvCD-0006X5-Si
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 21:30:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Lv4o-0006E7-QX
	for ietf@asgard.ietf.org; Fri, 30 May 2003 21:22:30 -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 VAA06817
	for <ietf@ietf.org>; Fri, 30 May 2003 21:22:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lv3A-0003dk-00
	for ietf@ietf.org; Fri, 30 May 2003 21:20:48 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lv39-0003db-00
	for ietf@ietf.org; Fri, 30 May 2003 21:20:47 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id VAA02402;
	Fri, 30 May 2003 21:17:49 -0400
Date: Fri, 30 May 2003 21:18:45 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Anthony Atkielski <anthony@atkielski.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <0b5e01c32708$4f5f67a0$0a00000a@atkielski.com>
Message-ID: <Pine.LNX.4.44.0305302111500.21528-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Ok, I take Anthony to fair and neutral observer, and genuine criticism.

I apologize for saying I don't think John has direct operational
experience tracking abusers.  I should have simply explained that my own
experiences tracking abusers were different with respect to costs and
difficulty.

I also apologize for using the word nonsense. I should have explained that
I thought the points were irrelevant. That would have been a less
inflamatory and more information bearing approach.

		--Dean

On Sat, 31 May 2003, Anthony Atkielski wrote:

> > I haven't repeatedly (or at all) defamed anyone.
>
> While I don't recall reading the original posts, you've backquoted text you
> wrote yourself in which you cast aspersions upon others, which is
> defamation.  Speculating that someone lacks experience or that what he has
> written is "nonsense" falls into this category.
>
> > And I also would like to initiate a formal complaint.
>
> Formal complaints of defamation generally must be based on clear evidence of
> damages.  Unless you've lost a job or someone has slashed your tires or
> something because of posts on this list, a "formal complaint" really doesn't
> serve any purpose.
>
> I suggest that everyone here be a lot less sensitive, and try a lot harder
> to stick to the discussion, minus the personal attacks.  It's easy enough to
> say "I don't agree with you" without adding "because I think you're stupid."
>
>
>




From owner-ietf@ietf.org  Fri May 30 21:53:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07739
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 21:53:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LvCE-0006XU-Mb
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 21:30:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Lv7D-0006EI-LW
	for ietf@asgard.ietf.org; Fri, 30 May 2003 21:24:59 -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 VAA06863
	for <ietf@ietf.org>; Fri, 30 May 2003 21:24:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lv5Z-0003eX-00
	for ietf@ietf.org; Fri, 30 May 2003 21:23:17 -0400
Received: from 75.5.33.65.cfl.rr.com ([65.33.5.75] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lv5Y-0003eU-00
	for ietf@ietf.org; Fri, 30 May 2003 21:23:16 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19Lb6L-0007EW-00; Fri, 30 May 2003 00:02:45 -0400
Date: Fri, 30 May 2003 00:02:43 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: william@elan.net
cc: Rob Austein <sra+ietf@hactrn.net>, <ietf@ietf.org>
Subject: Re: Last 7 days on the IETF list
In-Reply-To: <Pine.LNX.4.44.0305301736050.20347-100000@sokol.elan.net>
Message-ID: <Pine.LNX.4.44.0305300000230.27804-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

well, i guess i got shorted on my .02 (insert currency here) then.
where can i collect my other .001 of messages posted, and my .002 of data
transfer?

scott
> >   Messages   |     Bytes       | Who
> > -------+-----+-------+---------+------------------------
> >  11.4% |  53 | 13.9% |  233614 | dean@av8.com
> >  12.2% |  57 | 10.1% |  170963 | anthony@atkielski.com
> >   7.5% |  35 |  7.2% |  121074 | ehall@ehsco.com
> >   3.0% |  14 |  4.8% |   80253 | pdeutsch@earthlink.net
> >   3.9% |  18 |  3.6% |   60755 | valdis.kletnieks@vt.edu
> >   3.4% |  16 |  3.5% |   58293 | alh-ietf@tndh.net
> >   3.6% |  17 |  2.6% |   43278 | michel@arneill-py.sacramento.ca.us
> >   2.8% |  13 |  2.2% |   37288 | moore@cs.utk.edu
> >   2.4% |  11 |  2.3% |   37930 | dwm@xpasc.com
> >   2.1% |  10 |  2.2% |   37479 | vjs@calcite.rhyolite.com
> >   2.1% |  10 |  2.2% |   36561 | iljitsch@muada.com
> >   2.1% |  10 |  1.9% |   31676 | l.wood@eim.surrey.ac.uk
> >   1.9% |   9 |  1.8% |   31053 | shogunx@sleekfreak.ath.cx
> >   1.9% |   9 |  1.8% |   31016 | vixie@vix.com
> >   1.9% |   9 |  1.7% |   27856 | dhc2@dcrocker.net
> >   1.9% |   9 |  1.6% |   27349 | dja2003@hotpop.com
> >   1.9% |   9 |  1.5% |   24511 | sbwoodside@yahoo.com
> >   1.1% |   5 |  2.1% |   34761 | steflist@thor.nma.com
> >   1.7% |   8 |  1.3% |   21321 | jnc@ginger.lcs.mit.edu
> >   1.3% |   6 |  1.7% |   28495 | richard@shockey.us
> >   1.3% |   6 |  1.2% |   19636 | tomson_eric@yahoo.fr
> >   1.3% |   6 |  1.1% |   19259 | jstracke@centive.com
> >   0.9% |   4 |  1.5% |   24586 | john-ietf@jck.com
> >   1.1% |   5 |  1.0% |   16989 | mat@cisco.com
> >   0.9% |   4 |  0.9% |   15992 | avi@bridgewatersystems.com
> >   0.9% |   4 |  0.9% |   14418 | huitema@windows.microsoft.com
> >   0.9% |   4 |  0.8% |   13896 | phoffman@imc.org
> >   0.9% |   4 |  0.7% |   12281 | dee3@torque.pothole.com
> >   0.9% |   4 |  0.7% |   11323 | ietf@soaring.demon.co.uk
> >   0.9% |   4 |  0.7% |   11275 | tjc@ecs.soton.ac.uk
> >   0.6% |   3 |  0.8% |   13511 | darkuncle@darkuncle.net
> >   0.6% |   3 |  0.7% |   12302 | harald@alvestrand.no
> >   0.4% |   2 |  0.9% |   14402 | dws@hunnysoft.com
> >   0.4% |   2 |  0.8% |   14209 | mohta@necom830.hpcl.titech.ac.jp
> >   0.6% |   3 |  0.6% |   10191 | wessorh@ar.com
> >   0.6% |   3 |  0.6% |   10181 | rwelty@averillpark.net
> >   0.6% |   3 |  0.5% |    9109 | lear@cisco.com
> >   0.6% |   3 |  0.5% |    8328 | john.loughney@kolumbus.fi
> >   0.6% |   3 |  0.5% |    7803 | sommerfeld@orchard.arlington.ma.us
> >   0.6% |   3 |  0.5% |    7584 | billc44@citynet.net
> >   0.6% |   3 |  0.4% |    6866 | randy@psg.com
> >   0.2% |   1 |  0.8% |   13680 | soohong.park@samsung.com
> >   0.4% |   2 |  0.5% |    8935 | stephen@sprunk.org
> >   0.4% |   2 |  0.5% |    7722 | tytso@mit.edu
> >   0.4% |   2 |  0.5% |    7620 | rra@stanford.edu
> >   0.4% |   2 |  0.4% |    6916 | jmorris@cdt.org
> >   0.4% |   2 |  0.4% |    6630 | dank@hq.lindsayelec.com
> >   0.4% |   2 |  0.4% |    6470 | dominic.pinto@ieee.org
> >   0.4% |   2 |  0.4% |    6156 | zefram@fysh.org
> >   0.2% |   1 |  0.6% |    9711 | awduche@awduche.com
> >   0.4% |   2 |  0.3% |    5077 | bmanning@isi.edu
> >   0.4% |   2 |  0.3% |    4924 | fritz_saad@hotmail.com
> >   0.4% |   2 |  0.3% |    4618 | ekr@rtfm.com
> >   0.4% |   2 |  0.3% |    4576 | cdel@firsthand.net
> >   0.4% |   2 |  0.3% |    4438 | anewton@ecotroph.net
> >   0.4% |   2 |  0.3% |    4335 | garmitage@swin.edu.au
> >   0.2% |   1 |  0.5% |    7750 | alain.durand@sun.com
> >   0.2% |   1 |  0.4% |    7195 | dws+001@hunnysoft.com
> >   0.2% |   1 |  0.4% |    6953 | bob@wyman.us
> >   0.2% |   1 |  0.4% |    6315 | ggm@apnic.net
> >   0.2% |   1 |  0.4% |    6293 | et7563@sbc.com
> >   0.2% |   1 |  0.4% |    6003 | atul.sabharwal@intel.com
> >   0.2% |   1 |  0.3% |    5766 | hardie@qualcomm.com
> >   0.2% |   1 |  0.3% |    5699 | dhc@dcrocker.net
> >   0.2% |   1 |  0.3% |    5206 | cchaplin@sj.symbol.com
> >   0.2% |   1 |  0.3% |    4923 | peterf@exchange.microsoft.com
> >   0.2% |   1 |  0.3% |    4425 | page@mail.msen.com
> >   0.2% |   1 |  0.3% |    4388 | braendt@hotmail.com
> >   0.2% |   1 |  0.3% |    4306 | gk@ninebynine.org
> >   0.2% |   1 |  0.2% |    4096 | jorge.contreras@haledorr.com
> >   0.2% |   1 |  0.2% |    3465 | inanbe@xs4all.nl
> >   0.2% |   1 |  0.2% |    3310 | hinden@iprg.nokia.com
> >   0.2% |   1 |  0.2% |    3214 | smb@research.att.com
> >   0.2% |   1 |  0.2% |    3194 | gray@washington.edu
> >   0.2% |   1 |  0.2% |    3085 | ole@cisco.com
> >   0.2% |   1 |  0.2% |    3077 | rod.walsh@nokia.com
> >   0.2% |   1 |  0.2% |    2958 | msa@burp.tkv.asdf.org
> >   0.2% |   1 |  0.2% |    2946 | vinton.g.cerf@mci.com
> >   0.2% |   1 |  0.2% |    2782 | swb@employees.org
> >   0.2% |   1 |  0.2% |    2761 | jtk@depaul.edu
> >   0.2% |   1 |  0.2% |    2661 | bob.natale@appliedsnmp.com
> >   0.2% |   1 |  0.2% |    2621 | spencer_dawkins@yahoo.com
> >   0.2% |   1 |  0.1% |    2510 | glc@cisco.com
> >   0.2% |   1 |  0.1% |    2416 | klensin@jck.com
> >   0.2% |   1 |  0.1% |    2323 | braden@isi.edu
> >   0.2% |   1 |  0.1% |    2303 | kent@bbn.com
> >   0.2% |   1 |  0.1% |    2265 | andy.malis@vivacenetworks.com
> >   0.2% |   1 |  0.1% |    2259 | jfbauer@comcast.net
> >   0.2% |   1 |  0.1% |    2175 | benson.schliesser@savvis.net
> >   0.2% |   1 |  0.1% |    1789 | noc@nso.org
> > -------+-----+-------+---------+------------------------
> > 100.0% | 466 |100.0% | 1684907 | Total
> >
>
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81




From owner-ietf@ietf.org  Fri May 30 22:09:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08197
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 22:09:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LvVa-00087M-CH
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 21:50:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LvIz-0006w5-MA
	for ietf@asgard.ietf.org; Fri, 30 May 2003 21:37:09 -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 VAA07130
	for <ietf@ietf.org>; Fri, 30 May 2003 21:37:07 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LvHL-0003jL-00
	for ietf@ietf.org; Fri, 30 May 2003 21:35:27 -0400
Received: from h80ad271f.async.vt.edu ([128.173.39.31] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LvHJ-0003jI-00
	for ietf@ietf.org; Fri, 30 May 2003 21:35:26 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h4V1axn1002226;
	Fri, 30 May 2003 21:36:59 -0400
Message-Id: <200305310136.h4V1axn1002226@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Anthony Atkielski <anthony@atkielski.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here 
In-Reply-To: Your message of "Sat, 31 May 2003 01:55:23 +0200."
             <0b3901c32706$ef39b750$0a00000a@atkielski.com> 
References: <001a01c326d6$9dfe6e60$56144104@eagleswings>
            <0b3901c32706$ef39b750$0a00000a@atkielski.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1696857844P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 30 May 2003 21:36:58 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_1696857844P
Content-Type: text/plain; charset=us-ascii

On Sat, 31 May 2003 01:55:23 +0200, Anthony Atkielski <anthony@atkielski.com>  said:

> That isn't millions of hours per day.  I get hundreds of spam messages a
> day, and it only takes me a minute or two each day to delete them; often not
> even that.

I'm glad that you have such a high-speed connection that you can connect,
download hundreds of messages, and filter/delete them all in a minute or two.

My mother doesn't have that luxury - a 56K modem connection from Earthlink and
Hotmail is as good as it's going to get on Social Security.  And as long as
spam doesn't find her, it's *sufficient*.  But if she has to start worrying
about more than a dozen spams a day, e-mail will become useless for her.

I suggest that you keep in mind that my mother is probably a lot more
representative of the net population at large than you are.

> I find television commercials to be a tremendous annoyance, but they don't
> cause me any losses.  And it's interesting that nobody seems to object to
> them, even though television programs are interrupted literally every few
> minutes by them (which, when you think about it, is exceedingly bizarre).

Unless you're a television critic, there's no real cost to the time commercials
take up.  And it's well understood that commercials are what pays for
free commercial television, and that's the trade off.

There's plenty of examples on the Internet where people have *willingly*
agreed to a certain level of ads in return for free service - the free version
of Eudora, many free e-mail services, etc.  However, there the trade off is
"I accept that the Eudora people will send me an ad for XYZ in return for
the free use of their software" or "the webmail site has a banner add for
QAZ to subsidize my free use" - Eudora has gotten money from XYZ, and the
webmail site has gotten money from QAZ, and in exchange for getting the ad,
the user gets the benefit of free/cheaper service.

But who's getting the benefit from unsolicited spam that neither the user
nor the provider agreed to?


--==_Exmh_1696857844P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+2Ac6cC3lWbTT17ARAuEsAJ4yavVAfbCsuC/tJrw+wxVz7f1qUACfRPiE
bYcYsWZCKJeyCDknPbGFGJM=
=5pOd
-----END PGP SIGNATURE-----

--==_Exmh_1696857844P--



From owner-ietf@ietf.org  Fri May 30 22:19:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08568
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 22:19:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lvpa-0001Kw-Hy
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 22:10:50 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Lvck-0000Wa-Gi
	for ietf@asgard.ietf.org; Fri, 30 May 2003 21:57:34 -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 VAA07963
	for <ietf@ietf.org>; Fri, 30 May 2003 21:57:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lvb6-00040N-00
	for ietf@ietf.org; Fri, 30 May 2003 21:55:52 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lvb5-00040K-00
	for ietf@ietf.org; Fri, 30 May 2003 21:55:51 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4V1vWKk055135
	for <ietf@ietf.org>; Sat, 31 May 2003 03:57:32 +0200 (CEST)
Message-ID: <0bb401c32717$ff823400$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <001a01c326d6$9dfe6e60$56144104@eagleswings>            <0b3901c32706$ef39b750$0a00000a@atkielski.com> <200305310136.h4V1axn1002226@turing-police.cc.vt.edu>
Subject: Re: The utilitiy of IP is at stake here 
Date: Sat, 31 May 2003 03:57:31 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Valdis writes:

> I'm glad that you have such a high-speed connection
> that you can connect, download hundreds of messages,
> and filter/delete them all in a minute or two.

I have a broadband connection, and my perpetually-open Outlook Express
client checks my e-mail every sixty seconds.  So I just delete the junk mail
in my inbox when I come across it.  I'd say that it actually takes 10-15
seconds each time I do it.

> My mother doesn't have that luxury - a 56K modem
> connection from Earthlink and Hotmail is as good as
> it's going to get on Social Security.

In that case, she isn't likely to be posting to USENET, participating in
mailing lists, or putting her e-mail address on Web sites, either, so she
probably won't receive much spam.

> And as long as spam doesn't find her, it's *sufficient*.

Exactly.  See above.

> But if she has to start worrying about more than a
> dozen spams a day, e-mail will become useless for her.

How will the spammer's find her address?

> I suggest that you keep in mind that my mother
> is probably a lot more representative of the net
> population at large than you are.

Yes.  A slow connection, and little or no spam.

> Unless you're a television critic, there's no real
> cost to the time commercials take up.

How can time spent watching television commercials be free, if the same time
spent deleting spam costs money?

> But who's getting the benefit from unsolicited spam
> that neither the user nor the provider agreed to?

The people who reply to the spam, apparently.  The only reason spammers send
it out is that some people reply to it.





From owner-ietf@ietf.org  Fri May 30 22:46:05 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09216
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 22:46:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lw8f-0002OO-1E
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 22:30:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LvrP-0001dE-5b
	for ietf@asgard.ietf.org; Fri, 30 May 2003 22:12:43 -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 WAA08441
	for <ietf@ietf.org>; Fri, 30 May 2003 22:12:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lvpk-00048I-00
	for ietf@ietf.org; Fri, 30 May 2003 22:11:00 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lvpj-00047T-00
	for ietf@ietf.org; Fri, 30 May 2003 22:10:59 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id WAA15572;
	Fri, 30 May 2003 22:07:26 -0400
Date: Fri, 30 May 2003 22:08:23 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Pete Resnick <presnick@qualcomm.com>
cc: John C Klensin <john-ietf@jck.com>, "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: Answering questions and defamation (was: RE: The utilitiy of IP
  is at stake here)
In-Reply-To: <p0600142bbafdab5a7bd4@[216.43.25.67]>
Message-ID: <Pine.LNX.4.44.0305302138510.21528-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Pete sent me private mail on Wednesday first saying wanted to discuss,
and then saying he didn't want to discuss SMTP AUTH. That is why I cc'd
him on my discussion with John.

Today Pete sent me private mail saying one can't trust headers besides
your own. I sent Pete private mail back, pointing out the invalidity of
his assertion. Obviously, you can trust other headers, and you can
identify forged headers.  Pete and John's assertion otherwise is wrong.

Given that John sent me two previous messages, and avoided direct
questions on experience tracking abusers, but included generally his
resume involving standards, I think I have been setup on the issue of his
experience catching abusers. They protest too much.

I note that in the final (of 3) private response where John *finally*
reveals his experiences tracking abusers, he *still* avoids the issue of
cost associated with his experiences. He doesn't indicate when "his ISP
days"  were.  This all could have been avoided if John had substantiated
his experiences in the first place instead sending his resume about
standards body experiences, and other experiences, as I correctly noted,
that were irrelevant.

It all seems to be a diversion from the question of relevance. John still
haven't answered those questions, but has been very upset by being pressed
for details to backup his assertions about the expense and difficulty of
tracking abusers.  My experience has been that once Law Enforcement is
involved, this is a relatively easy and cheap task.  Even if John's
experiences were that it was difficult and expensive at some time in the
past, it doesn't mean that it is today.

		--Dean

On Fri, 30 May 2003, Pete Resnick wrote:

> On 5/30/03 at 6:24 PM -0400, Dean Anderson wrote:
>
> >So far, you haven't sent anything (despite a very impressive resume)
> >that seems to be relevant experience in tracking abusers.
>
> For some reason, Dean decided to start Cc'ing  his private mail
> conversation with John to me (I'm not sure exactly why), but because
> of that, I was privy to the e-mail in question and can't let the
> above statement pass.
>
> Dean's above statement is patently false. John did provide (for
> Dean's reference, in message <152050487.1054196854@p3.JCK.COM>)
> absolutely relevant experience in tracking abusers in the mail to
> which he refers.
>
> Given the large number of other false statements and invalid
> arguments in Dean's messages to this list, both on issues of
> substance and with regard to his personal attacks on John, I have
> decided not to engage with Dean publicly, though I have sent him
> private mail pointing out at least one of his invalid arguments. I
> suggest others might also benefit from subjecting Dean's messages to
> careful scrutiny; I have found them lacking in factual information
> and quite misleading.
>
> pr
> --
> Pete Resnick <mailto:presnick@qualcomm.com>
> QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102
>








From owner-ietf@ietf.org  Fri May 30 22:55:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08196
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 May 2003 22:09:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LvVZ-00085H-Lq
	for ietf-list@asgard.ietf.org; Fri, 30 May 2003 21:50:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LvES-0006Xz-LE
	for ietf@asgard.ietf.org; Fri, 30 May 2003 21:32:28 -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 VAA06967
	for <ietf@ietf.org>; Fri, 30 May 2003 21:32:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LvCo-0003gS-00
	for ietf@ietf.org; Fri, 30 May 2003 21:30:46 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LvCn-0003gM-00
	for ietf@ietf.org; Fri, 30 May 2003 21:30:45 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id VAA19829
	for <ietf@ietf.org>; Fri, 30 May 2003 21:28:30 -0400
Date: Fri, 30 May 2003 21:29:35 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: ietf@ietf.org
Subject: Private message from John Klensin
Message-ID: <Pine.LNX.4.44.0305302120560.21528-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

This is the message to which Pete Resnick refers.

I did not get this until Pete mentioned the message number and I searched
for it.

It is the _last_ private message John sent to me.

In his other previous messages, John did not mention this experience.

		--Dean

---------- Forwarded message ----------
Date: Thu, 29 May 2003 08:27:34 -0400
From: John C Klensin <john-ietf@jck.com>
To: Dean Anderson <dean@av8.com>
Cc: "presnick@qualcomm.com" <presnick@qualcomm.com>
Subject: Re: The utilitiy of IP is at stake here



--On Thursday, 29 May, 2003 00:05 -0400 Dean Anderson
<dean@av8.com> wrote:

>> And I've been involved with SMTP, and its predecessors, for
>> over thirty years now -- standards, protocol design, gateway
>> design and implementation, and operations and deployment in
>> organizations and enterprises ranging from the very small to
>> the very large.
>
> But have you ever tracked down an abuser?

Personally, yes, several times.  And had partial responsibility
for that department for an ISP with millions of customers (both
dialup and dedicated) for a while.  And trained the 20-odd
people in that department how to do it and what to look for when
the abusers were not on our network.   And participated in
writing their terms and conditions.

> Have you ever sold standards based services to customers that
> want standards based services?  Do you really understand why
> customers want standards?

Yes, and I've written standards-based procurement specs too,
including for one of your former employers.

> That's operational experience.
>
> You seem to be unaware that Relays (open or closed) put the IP
> address of the client in the message. This address cannot be
> altered by the client. So it is impossible to send anonymous
> email with an open relay.

I'm aware that they do it.  I'm aware that, while doing it is
beyond the average spammer, IP addresses can be faked.  I'm
aware that some spam software uses a two-hop method and that
only the Received address inserted by _my_ server --or a server
known to my server which I know I can trust -- is reliable.  I'm
aware that spam often contains completely made-up Received
fields (although, obviously, not the locally-inserted one).  And
I'm aware that getting from an IP address to a user
identification can be a very rough process, especially if the
user is coming from an Internet cafe on a cash-only, no-account
basis or using a public terminal in a library or the equivalent
that doesn't require or authenticate sign-ins, or using a dialup
service that makes no attempt to authenticate its users in order
to authorize their use (either, as in the Chinese case and a few
other developing areas, because they
make no attempt to authenticate or because they are operating on
an "internet calling card" basis, with cards that can be
purchased for cash and without identification.

I really have worked these problems, Dean.  In the trenches.

> The property of a users anonymity is not altered by SMTP.

In the sense that positive identification of a user who doesn't
want to be identified --even by species-- is typically hard with
any Internet protocol, that is correct.  And I have _never_ said
otherwise.    That is, however, where SMTP AUTH (and IMAP/POP
AUTH, and some uses of PKI, and maybe RADIUS, and proper use of
TLS/SSL with client certificates, and Kerberos, and...) come in
-- if I am running a server and I care who is using it (or some
resource on it) down to the user level, I need to require that
the users authenticate themselves and make sure they have the
necessary tools and credentials to do so to my satisfaction.

SMTP, and more especially its predecessors --but not SMTP AUTH--
was, incidentally, designed on what I think is exactly the model
you are assuming today.  In that model, the identity of the
machine from which mail was sent could be authenticated (a
technical issue, hasn't changed much, although relays can make
things _much_ more difficult) and the operators of that machine
can be held responsible (administratively and legally) from
anything that originates from their machines.   That
administrative and legal issue caused machine administrators to
either firmly explain AUPs, etc., to their users or to create
accounts and whatever they considered satisfactory authorization
mechanisms.    The introduction of router-based LANs and desktop
machines with IP addresses and SMTP clients weakened that model
considerably, as did public internet "terminals" of several
different sorts.

> SMTP abuse is not the only type of abuse that a user can send.

Of course not.  On a given day, it is far more reasonable to
worry about various security-type attacks.  But they are less
intrusive on the typical user and, typically, easier to defend
against.

>> If you reach different conclusions about something than I do
>> and we disagree, that is fine.  But don't tell me what I
>> don't know or what I was thinking about, or assumed, at a
>> particular time.
>
> Don't mean to tell you what you are thinking. What ever you
> were thinking seems to be questionable, SMTP AUTH serves no
> purpose, and solves no problem.

See "user authentication" above.  You are entitled to believe,
and even to tell your customers, that such authentication is of
no use, but, for those of us who see it as an issue/problem, it
solves it.

> The only problem SMTP AUTH *seems* to solve, judging by the
> people promoting it, is that it is an alternative to
> POP-BEFORE-SMTP.  But of course, that was also a half-baked
> idea, promoted by crusaders who thought (wrongly) that open
> relays somehow (never explained) promoted spam, and somehow
> permitted anonymous email, or enabled (non-existant)
> multiplication. None of these harms ever withstood close
> scrutiny.

Once again, regardless of what I think of Send-after-POP (and I
think it is an obscenity for a number of reasons), it is
legitimate for me to control or monitor (with real
authentication) who gets to use my servers.  I may do that
because I want to be able to track down any user who actually
sends mail from my address range, or because I'm concerned about
allocation of scarce resources (do you know that some servers
are configured to impose different limits on the permitted size
of outgoing mail depending on which user is sending it?), or
because I'm compulsive (or delusional, depending on your
perspective) about property rights in the cycles on the server,
or because I've got some broken notion about attaching security
authorization levels to send different types of mail to the
client-server connection.  The point is that each of the above
is a legitimate reason for wanting to authenticate an
originating user (not just a machine) to the first-hop SMTP
server.  None of them require end-to-end authentication in a
multi-hop environment that doesn't exclusively involve trusted
servers.  And you will note that I made exactly as many claims
that such authentication would solve spam as I did that it would
cure cancer... zero.

Wrt the spam issue, SMTP authentication is useful iff the
_originating_ server can be positively identified _and_ its
operators are cooperative but have no other reliable way of
tracing individual users.  That combination rarely occurs in
today's environment, and I have never claimed (or believed)
otherwise.  Never.

> Real spammers don't abuse open relays.

Absolutely true, if you define "real spammer" as "one who
doesn't abuse open relays".  I've got some evidence to the
contrary, using something close to your definition of a spammer:
back in my ISP days, we tracked down several spammers who were
violating our terms and conditions of service by sending the
stuff and, with the cooperation of law enforcement because of
the nature of the content being advertised, got to examine
software and "interview" them under oath.  They were
deliberately using open relays (rather than, or in addition to,
the SMTP servers we provided) in an attempt to disguise the
origins of their mail, since they knew that sending it violated
the rules to which they had agreed.  And their messages didn't
point to web sites or email addresses for responses -- they
pointed to phone numbers.   Fortunately for us, they were also
stupid.  E.g., if you buys telephone service from the same
entity from which you buy Internet service, it typically takes
that entity even less time to track you down by phone number
than it does to do so by IP address.   The level of
sophistication has clearly gone up in the last several years.

> The vast bulk, and by that I mean millions compared to a
> couple hundred over a seven year period, of open relay abuse
> was conducted by anti-spammer crusaders.

Look. I don't like the "anti-spammer crusaders" either, and I,
and server's I've been responsible for, have been on their hit
list more than once --either because they thought we were
running excessively open relays or because they thought we were
not being diligent enough in stopping/ prosecuting spammers.
I've also been targeted, in campaigns that are almost
indistinguishable, by spammers who were upset by efforts to push
back on them, statements of sympathy for those we caught and put
out of business, or because they didn't like our terms of
service and tended to enforce them.  I've also had spammers
decide to "get" me by using my address in the From: and/or
envelope return path fields of some really nasty high-volume
bulk messages.  These experiences are pretty unpleasant,
especially when they bring servers that support millions of
users to an approximation to a halt (and, yes, we learned to
deal with that, but it cost a lot).  But I very much doubt your
statistics on an overall network basis, although I have no doubt
that they reflect your personal experience.


>> Our goal was to provide an relatively strong authentication
>> mechanism for a number of purposes, including
>> intra-enterprise address authentication (when used in
>> combination with strong internal administrative policies).
>
> And what purpose does this serve?

See above.

> I've worked for organizations large and small, ISPs large and
> small, and have not seen any use for an authentication method
> in SMTP.

See above.

> An authentication method ties SMTP to the user. But SMTP is a
> batch protocol. The user is long gone, in all but a few cases,
> such as dialup. And _USERS_ aren't the only entities sending
> mail.

As indicated above, it is mostly useful as a first-hop
authentication protocol.   In first-hop arrangements the typical
uses of SMTP are not really "batch protocol" and authentication
of the user is meaningful.   Now, some people have had the
notion that SMTP AUTH could be used to establish a chain of
trust among servers in a relay chain.  I've never believed that
to be generally useful -- the authentication mechanism isn't
properly designed for passing along "the user claimed to be X,
and server Y authenticated that, and I trust Y because Z said
so, and I've got appropriate credentials Z and it was
authenticated to me" the information one would really want.  And
it wouldn't scale well either, IMO.   If one really wants
end-to-end authentication of messages or their senders, one
needs... well, end to end methods.  And SMTP AUTH isn't an end
to end method and anyone claiming it is is delusional (or, in
your terms, "doesn't understand how SMTP works").

On the other hand, there is a lot of evidence that most
legitimate, non-bulk, Internet mail these days goes

   local-client -> first-hop SMTP relay -> delivery SMTP

with the intervention of relays that are not under the
presumptive control of either the sender or the receiver.  In
that case, the Received data recorded by the delivery MTA is
extremely useful, and user (or originator) authentication to the
first-hop relay may be quite helpful in identifying the actual
originator (or whomever has the credentials) whether in
conjunction with the address information it records or otherwise.

>> Yes, it helped with one small element of the spam problem, in
>> that it permitted authorized users of particular (not-open)
>> mail relays to authenticate themselves to those relays
>
> How does this affect spam?

Dean, the irony of these exchanges is that you have been so busy
attacking me (and some others) that the possibility that we are
largely in agreement on the important issues has escaped you.  I
am very skeptical, at best, about the possibility of a technical
remedy to spam that doesn't destroy Internet email in the
process.  I think it is mostly a social problem, one that
becomes a legal problem if the social norms are violated.  We
disagree about how to measure costs and impacts but, for better
or worse, the tide seems to be running in my favor.  But, at the
point that it becomes a legal problem, even if only because
someone offers an "opt out" and then redistributes the
supposedly-removed address as a "validated address" to other
spammers, accurate sender identification is very important in
figuring out who to sue or prosecute.

>> But I, at least never expected that would do anything other
>> than to shift the spammers elsewhere and have essentially
>> said so on the list.
>
> How does SMTP AUTH "shift spammers elsewhere"?  Spammers are
> the customers of ISPs. If those ISPs use SMTP AUTH, the
> spammers will have that password.  This changes nothing.

If an ISP sets things up so that it has _any_ reliable
user-identification mechanism (IP addresses work sometimes and
with some setups, and not others, and are problematic if one
wants the relay to be accessible to users coming from other
networks), and that includes per-user (rather than per-server)
credentials (names and "passwords", if you like), then it has a
positive way to identify who has originated a message that turns
out to be problematic.   As outlined above, this is all about
sanctions for prior bad behavior rather than preventing the
behavior (except by the certainty of being caught and
inconvenienced).  And the spammers go elsewhere, to places where
terms of service don't prohibit spamming, or where they are
clearly unenforced or unenforceable, because doing so is
rational.  Why risk prosecution, high special fees, and service
disconnections (the least of the remedies in most cases) when
you can just find a more friendly home?  Of course, if you
_can't_ find a more friendly home, that is where the open relays
and other tactics intended to hide the origins and path of your
mail set in.

regards,
     john

>
> 		--Dean
>











From owner-ietf@ietf.org  Sat May 31 00:26:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10981
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 00:26:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Lxo2-00055O-0Z
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 00:17:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LxjH-0004zX-9W
	for ietf@asgard.ietf.org; Sat, 31 May 2003 00:12:27 -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 AAA10691
	for <ietf@ietf.org>; Sat, 31 May 2003 00:12:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lxhc-0004h7-00
	for ietf@ietf.org; Sat, 31 May 2003 00:10:44 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lxhb-0004h3-00
	for ietf@ietf.org; Sat, 31 May 2003 00:10:43 -0400
Content-class: urn:content-classes:message
Subject: RE: Last 7 days on the IETF list
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Fri, 30 May 2003 21:12:17 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F848@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: Last 7 days on the IETF list
Thread-Index: AcMm4FTkTvP3vII1QmirEHHkiIsVdQASNCKQ
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Rob Austein" <sra+ietf@hactrn.net>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id AAA10981

Rob,

> Rob Austein wrote
> Traffic statistics (as seen from my cave, your mileage
> may vary) for the last seven days on the ietf@ietf.org
> mailing list.

Thanks for posting this. I was about to join another poster in saying
that you should not have posted the bytes; however, on second thought, I
like seeing them in the table. Apparently there is a direct correlation
between the bytes and the number of messages anyway. It is instructive
to see the info.

> Conclusions, if any, are left as an exercise for the reader.

Mmmm let's see. That would be three trolls, somehow fed by four people
including myself (which I regret) which is why I put these three in the
troll box and stopped the troll nourishment 2 days ago.

Michel.



  Messages   |     Bytes       | Who
-------+-----+-------+---------+------------------------
 11.4% |  53 | 13.9% |  233614 | dean@av8.com
 12.2% |  57 | 10.1% |  170963 | anthony@atkielski.com
  7.5% |  35 |  7.2% |  121074 | ehall@ehsco.com
  3.0% |  14 |  4.8% |   80253 | pdeutsch@earthlink.net
  3.9% |  18 |  3.6% |   60755 | valdis.kletnieks@vt.edu
  3.4% |  16 |  3.5% |   58293 | alh-ietf@tndh.net
  3.6% |  17 |  2.6% |   43278 | michel@arneill-py.sacramento.ca.us
  2.8% |  13 |  2.2% |   37288 | moore@cs.utk.edu
  2.4% |  11 |  2.3% |   37930 | dwm@xpasc.com
  2.1% |  10 |  2.2% |   37479 | vjs@calcite.rhyolite.com
  2.1% |  10 |  2.2% |   36561 | iljitsch@muada.com
  2.1% |  10 |  1.9% |   31676 | l.wood@eim.surrey.ac.uk
  1.9% |   9 |  1.8% |   31053 | shogunx@sleekfreak.ath.cx
  1.9% |   9 |  1.8% |   31016 | vixie@vix.com
  1.9% |   9 |  1.7% |   27856 | dhc2@dcrocker.net
  1.9% |   9 |  1.6% |   27349 | dja2003@hotpop.com
  1.9% |   9 |  1.5% |   24511 | sbwoodside@yahoo.com
  1.1% |   5 |  2.1% |   34761 | steflist@thor.nma.com
  1.7% |   8 |  1.3% |   21321 | jnc@ginger.lcs.mit.edu
  1.3% |   6 |  1.7% |   28495 | richard@shockey.us
  1.3% |   6 |  1.2% |   19636 | tomson_eric@yahoo.fr
  1.3% |   6 |  1.1% |   19259 | jstracke@centive.com
  0.9% |   4 |  1.5% |   24586 | john-ietf@jck.com
  1.1% |   5 |  1.0% |   16989 | mat@cisco.com
  0.9% |   4 |  0.9% |   15992 | avi@bridgewatersystems.com
  0.9% |   4 |  0.9% |   14418 | huitema@windows.microsoft.com
  0.9% |   4 |  0.8% |   13896 | phoffman@imc.org
  0.9% |   4 |  0.7% |   12281 | dee3@torque.pothole.com
  0.9% |   4 |  0.7% |   11323 | ietf@soaring.demon.co.uk
  0.9% |   4 |  0.7% |   11275 | tjc@ecs.soton.ac.uk
  0.6% |   3 |  0.8% |   13511 | darkuncle@darkuncle.net
  0.6% |   3 |  0.7% |   12302 | harald@alvestrand.no
  0.4% |   2 |  0.9% |   14402 | dws@hunnysoft.com
  0.4% |   2 |  0.8% |   14209 | mohta@necom830.hpcl.titech.ac.jp
  0.6% |   3 |  0.6% |   10191 | wessorh@ar.com
  0.6% |   3 |  0.6% |   10181 | rwelty@averillpark.net
  0.6% |   3 |  0.5% |    9109 | lear@cisco.com
  0.6% |   3 |  0.5% |    8328 | john.loughney@kolumbus.fi
  0.6% |   3 |  0.5% |    7803 | sommerfeld@orchard.arlington.ma.us
  0.6% |   3 |  0.5% |    7584 | billc44@citynet.net
  0.6% |   3 |  0.4% |    6866 | randy@psg.com
  0.2% |   1 |  0.8% |   13680 | soohong.park@samsung.com
  0.4% |   2 |  0.5% |    8935 | stephen@sprunk.org
  0.4% |   2 |  0.5% |    7722 | tytso@mit.edu
  0.4% |   2 |  0.5% |    7620 | rra@stanford.edu
  0.4% |   2 |  0.4% |    6916 | jmorris@cdt.org
  0.4% |   2 |  0.4% |    6630 | dank@hq.lindsayelec.com
  0.4% |   2 |  0.4% |    6470 | dominic.pinto@ieee.org
  0.4% |   2 |  0.4% |    6156 | zefram@fysh.org
  0.2% |   1 |  0.6% |    9711 | awduche@awduche.com
  0.4% |   2 |  0.3% |    5077 | bmanning@isi.edu
  0.4% |   2 |  0.3% |    4924 | fritz_saad@hotmail.com
  0.4% |   2 |  0.3% |    4618 | ekr@rtfm.com
  0.4% |   2 |  0.3% |    4576 | cdel@firsthand.net
  0.4% |   2 |  0.3% |    4438 | anewton@ecotroph.net
  0.4% |   2 |  0.3% |    4335 | garmitage@swin.edu.au
  0.2% |   1 |  0.5% |    7750 | alain.durand@sun.com
  0.2% |   1 |  0.4% |    7195 | dws+001@hunnysoft.com
  0.2% |   1 |  0.4% |    6953 | bob@wyman.us
  0.2% |   1 |  0.4% |    6315 | ggm@apnic.net
  0.2% |   1 |  0.4% |    6293 | et7563@sbc.com
  0.2% |   1 |  0.4% |    6003 | atul.sabharwal@intel.com
  0.2% |   1 |  0.3% |    5766 | hardie@qualcomm.com
  0.2% |   1 |  0.3% |    5699 | dhc@dcrocker.net
  0.2% |   1 |  0.3% |    5206 | cchaplin@sj.symbol.com
  0.2% |   1 |  0.3% |    4923 | peterf@exchange.microsoft.com
  0.2% |   1 |  0.3% |    4425 | page@mail.msen.com
  0.2% |   1 |  0.3% |    4388 | braendt@hotmail.com
  0.2% |   1 |  0.3% |    4306 | gk@ninebynine.org
  0.2% |   1 |  0.2% |    4096 | jorge.contreras@haledorr.com
  0.2% |   1 |  0.2% |    3465 | inanbe@xs4all.nl
  0.2% |   1 |  0.2% |    3310 | hinden@iprg.nokia.com
  0.2% |   1 |  0.2% |    3214 | smb@research.att.com
  0.2% |   1 |  0.2% |    3194 | gray@washington.edu
  0.2% |   1 |  0.2% |    3085 | ole@cisco.com
  0.2% |   1 |  0.2% |    3077 | rod.walsh@nokia.com
  0.2% |   1 |  0.2% |    2958 | msa@burp.tkv.asdf.org
  0.2% |   1 |  0.2% |    2946 | vinton.g.cerf@mci.com
  0.2% |   1 |  0.2% |    2782 | swb@employees.org
  0.2% |   1 |  0.2% |    2761 | jtk@depaul.edu
  0.2% |   1 |  0.2% |    2661 | bob.natale@appliedsnmp.com
  0.2% |   1 |  0.2% |    2621 | spencer_dawkins@yahoo.com
  0.2% |   1 |  0.1% |    2510 | glc@cisco.com
  0.2% |   1 |  0.1% |    2416 | klensin@jck.com
  0.2% |   1 |  0.1% |    2323 | braden@isi.edu
  0.2% |   1 |  0.1% |    2303 | kent@bbn.com
  0.2% |   1 |  0.1% |    2265 | andy.malis@vivacenetworks.com
  0.2% |   1 |  0.1% |    2259 | jfbauer@comcast.net
  0.2% |   1 |  0.1% |    2175 | benson.schliesser@savvis.net
  0.2% |   1 |  0.1% |    1789 | noc@nso.org
-------+-----+-------+---------+------------------------
100.0% | 466 |100.0% | 1684907 | Total




From owner-ietf@ietf.org  Sat May 31 00:38:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11305
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 00:38:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ly4L-0005jJ-43
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 00:34:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Lxvf-0005HJ-GG
	for ietf@asgard.ietf.org; Sat, 31 May 2003 00:25:15 -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 AAA10964
	for <ietf@ietf.org>; Sat, 31 May 2003 00:25:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lxu0-0004jA-00
	for ietf@ietf.org; Sat, 31 May 2003 00:23:32 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Lxu0-0004j5-00
	for ietf@ietf.org; Sat, 31 May 2003 00:23:32 -0400
Content-class: urn:content-classes:message
Subject: RE: Answering questions and defamation (was: RE: The utilitiy of IP is at stake here)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Fri, 30 May 2003 21:25:06 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F506717F@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: Answering questions and defamation (was: RE: The utilitiy of IP is at stake here)
Thread-Index: AcMm79g9OerVCZeOQliw6p7VBNvPTgAPDxWA
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "John C Klensin" <john-ietf@jck.com>
Cc: "IETF Discussion" <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id AAA11305

John,

With all due respect, I will repeat to you the message I had for Peter
Deutsch two days ago:
- Stop feeding the trolls, it's not good for your blood pressure.
Besides, you do not have to justify who you are or what you did in here.
- Go home, take a deep breath, have a beer, relax.

Michel.




From owner-ietf@ietf.org  Sat May 31 01:19:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12017
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 01:19:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19LyYE-0006to-5n
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 01:05:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LyVC-0006mZ-CU
	for ietf@asgard.ietf.org; Sat, 31 May 2003 01:01:58 -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 BAA11801
	for <ietf@ietf.org>; Sat, 31 May 2003 01:01:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LyTX-0004xx-00
	for ietf@ietf.org; Sat, 31 May 2003 01:00:15 -0400
Received: from ip166.usw12.rb1.bel.nwlink.com ([209.20.253.166] helo=ran.psg.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19LyTX-0004xu-00
	for ietf@ietf.org; Sat, 31 May 2003 01:00:15 -0400
Received: from localhost ([127.0.0.1] helo=ran.psg.com)
	by ran.psg.com with esmtp (Exim 4.20)
	id 19LyV9-000Khr-Uq; Fri, 30 May 2003 22:01:56 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 30 May 2003 22:01:55 -0700
To: John C Klensin <john-ietf@jck.com>
Cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: Answering questions and defamation (was: RE: The
 utilitiy of IP is at stake here)
References: <Pine.LNX.4.44.0305301553050.17819-100000@commander.a
 v8.net>
	<267841966.1054312648@p3.JCK.COM>
Message-Id: <E19LyV9-000Khr-Uq@ran.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> From: John C Klensin <john-ietf@jck.com>
> To: Dean Anderson <dean@av8.com>

john, don't you have a mail filter?

randy




From owner-ietf@ietf.org  Sat May 31 07:58:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29761
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 07:58:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19M4nT-00042g-OF
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 07:45:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19M4l0-0003xt-9e
	for ietf@asgard.ietf.org; Sat, 31 May 2003 07:42:42 -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 HAA29580
	for <ietf@ietf.org>; Sat, 31 May 2003 07:42:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19M4jH-0006jm-00
	for ietf@ietf.org; Sat, 31 May 2003 07:40:56 -0400
Received: from smtp016.mail.yahoo.com ([216.136.174.113])
	by ietf-mx with smtp (Exim 4.12)
	id 19M4jH-0006jj-00
	for ietf@ietf.org; Sat, 31 May 2003 07:40:55 -0400
Received: from 212.68.224.51.brutele.be (HELO isoc) (Tomson?Eric@212.68.224.51 with login)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 31 May 2003 11:42:35 -0000
Reply-To: <Tomson_Eric@Yahoo.fr>
From: "Tomson Eric \(Yahoo.fr\)" <Tomson_Eric@Yahoo.fr>
To: "'Anthony Atkielski'" <anthony@atkielski.com>
Cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Sat, 31 May 2003 13:42:24 +0200
Organization: Internet Society
Message-ID: <000f01c32769$b8d17550$3b00a8c0@tomson.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <0b5e01c32708$4f5f67a0$0a00000a@atkielski.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA29761

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of Anthony
Atkielski
Sent: samedi 31 mai 2003 2:05
To: IETF Discussion
Subject: Re: The utilitiy of IP is at stake here

(...)

I suggest that everyone here be a lot less sensitive, and try a lot harder
to stick to the discussion, minus the personal attacks.  It's easy enough to
say "I don't agree with you" without adding "because I think you're stupid."


---------
Anthony,
Despite our disagreements on other topics, I couldn't agree more with you on
this one.
:)
---------





From owner-ietf@ietf.org  Sat May 31 07:59:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29814
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 07:59:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19M4sF-00047e-Gs
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 07:50:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19M4nT-00042e-IA
	for ietf@asgard.ietf.org; Sat, 31 May 2003 07:45:15 -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 HAA29589
	for <ietf@ietf.org>; Sat, 31 May 2003 07:45:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19M4lo-0006k3-00
	for ietf@ietf.org; Sat, 31 May 2003 07:43:32 -0400
Received: from prue.eim.surrey.ac.uk ([131.227.76.5] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19M4ln-0006k0-00
	for ietf@ietf.org; Sat, 31 May 2003 07:43:31 -0400
Received: from argos.ee.surrey.ac.uk ([131.227.89.15] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 19M4ms-0006aw-00; Sat, 31 May 2003 12:44:38 +0100
Date: Sat, 31 May 2003 12:44:35 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@argos.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Dean Anderson <dean@av8.com>
cc: Pete Resnick <presnick@qualcomm.com>, John C Klensin <john-ietf@jck.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: Answering questions and defamation (was: RE: The utilitiy of IP
  is at stake here)
In-Reply-To: <Pine.LNX.4.44.0305302138510.21528-100000@commander.av8.net>
Message-ID: <Pine.GSO.4.50.0305311212110.11098-100000@argos.ee.surrey.ac.uk>
References: <Pine.LNX.4.44.0305302138510.21528-100000@commander.av8.net>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-105.9 required=5.5
	tests=AWL,BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_PINE,
	      USER_IN_WHITELIST
	autolearn=ham version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
X-Scanner: exiscan *19M4ms-0006aw-00*3cFhTnDSd3g* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 30 May 2003, Dean Anderson wrote:

> Pete sent me private mail on Wednesday
[..]
> Today Pete sent me private mail saying one can't trust headers besides
> your own. I sent Pete private mail back, pointing out the invalidity of
> his assertion. Obviously, you can trust other headers, and you can
> identify forged headers.  Pete and John's assertion otherwise is wrong.

if you have to identify the forged headers first, you can't start by
trusting them. duh.

Some would argue that "trust, but verify" fundamentally isn't trust.

I would argue that this is the sort of grad-school semantics traps
that adults with decent communication skills don't fall into during
discussion.

> It all seems to be a diversion from the question of relevance.

Oh, indeed. One might ask the relevance to this list.

You don't understand the meaning of the word "private", do you?
And you have awfully poor communication skills.

L.

This list is noise. I'm leaving.

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>



From owner-ietf@ietf.org  Sat May 31 08:24:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00396
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 08:24:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19M5GU-0005J6-EZ
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 08:15:14 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19M5Dj-0005CH-RM
	for ietf@asgard.ietf.org; Sat, 31 May 2003 08:12:23 -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 IAA00264
	for <ietf@ietf.org>; Sat, 31 May 2003 08:12:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19M5C4-0006wf-00
	for ietf@ietf.org; Sat, 31 May 2003 08:10:40 -0400
Received: from smtp017.mail.yahoo.com ([216.136.174.114])
	by ietf-mx with smtp (Exim 4.12)
	id 19M5C3-0006wc-00
	for ietf@ietf.org; Sat, 31 May 2003 08:10:40 -0400
Received: from 212.68.224.51.brutele.be (HELO isoc) (Tomson?Eric@212.68.224.51 with login)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 31 May 2003 12:12:20 -0000
Reply-To: <Tomson_Eric@Yahoo.fr>
From: "Tomson Eric \(Yahoo.fr\)" <Tomson_Eric@Yahoo.fr>
To: "'Anthony Atkielski'" <anthony@atkielski.com>
Cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here 
Date: Sat, 31 May 2003 14:12:08 +0200
Organization: Internet Society
Message-ID: <001601c3276d$e0fafed0$3b00a8c0@tomson.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <0bb401c32717$ff823400$0a00000a@atkielski.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id IAA00396

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of Anthony
Atkielski
Sent: samedi 31 mai 2003 3:58
To: IETF Discussion
Subject: Re: The utilitiy of IP is at stake here 

(...)

> But if she has to start worrying about more than a
> dozen spams a day, e-mail will become useless for her.

How will the spammer's find her address?


----------
Anthony,

You suddenly seem a bit naive!

Have you never created e-mail addresses without ever making them public, and
nevertheless note that you get SPAM anyway?

I did. I created more than one e-mail address without ever making them
public, and though I note some of them receive SPAM!

How do the spammers find such addresses? Do they automatically try all
possible combinations of firstname_lastname@some-well-known-domains.com?

Who knows? I personally have no idea! But I must note that spammers succeed
in polluting everyone's mailbox!
----------





From owner-ietf@ietf.org  Sat May 31 10:57:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03825
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 10:57:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19M7bZ-0005bp-UC
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 10:45:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19M7b2-0005XZ-PH
	for ietf@asgard.ietf.org; Sat, 31 May 2003 10:44:36 -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 KAA03696
	for <ietf@ietf.org>; Sat, 31 May 2003 10:44:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19M7ZN-0007bn-00
	for ietf@ietf.org; Sat, 31 May 2003 10:42:53 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19M7ZM-0007bk-00
	for ietf@ietf.org; Sat, 31 May 2003 10:42:52 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4VEiYKk063392
	for <ietf@ietf.org>; Sat, 31 May 2003 16:44:34 +0200 (CEST)
Message-ID: <0c2b01c32783$26d97390$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <001601c3276d$e0fafed0$3b00a8c0@tomson.be>
Subject: Re: The utilitiy of IP is at stake here 
Date: Sat, 31 May 2003 16:44:32 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric writes:

> Have you never created e-mail addresses without
> ever making them public, and nevertheless note
> that you get SPAM anyway?

Not that I can recall.

> I did. I created more than one e-mail address
> without ever making them public, and though I
> note some of them receive SPAM!

Were the addresses along the lines of "postmaster," "info," or "webmaster,"
by chance?

> How do the spammers find such addresses? Do
> they automatically try all possible combinations
> of firstname_lastname@some-well-known-domains.com?

They must either harvest them or guess them.  For non-obvious e-mail
addresses that are never published, they cannot practically do either of
these, and so the addresses will not be spammed.

Most people I know who do not post to USENET or put their addresses on Web
sites or post to mailing lists receive very little spam, whereas I receive
several hundred spams a day on the addresses that I've publicly released
(but none on other addresses).





From owner-ietf@ietf.org  Sat May 31 11:39:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04327
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 11:39:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19M8MH-0006e8-2c
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 11:33:25 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19M8IM-0006Zj-45
	for ietf@asgard.ietf.org; Sat, 31 May 2003 11:29:22 -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 LAA04216
	for <ietf@ietf.org>; Sat, 31 May 2003 11:29:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19M8Gg-0007lJ-00
	for ietf@ietf.org; Sat, 31 May 2003 11:27:38 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19M8Gf-0007lG-00
	for ietf@ietf.org; Sat, 31 May 2003 11:27:37 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4VFTJKk063748
	for <ietf@ietf.org>; Sat, 31 May 2003 17:29:19 +0200 (CEST)
Message-ID: <0c3d01c32789$677f3aa0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <001601c3276d$e0fafed0$3b00a8c0@tomson.be> <0c2b01c32783$26d97390$0a00000a@atkielski.com> <Pine.WNT.4.56.0305310801480.1436@TGX200>
Subject: Re: The utilitiy of IP is at stake here 
Date: Sat, 31 May 2003 17:29:18 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Terry writes:

> At least one of them is a combination of letters
> and numbers that I would have expected to
> resist most dictionary spam attacks.

To whom have you sent e-mail from that address?

If they didn't use a dictionary attack, and they didn't harvest the address,
how did they get it?




From owner-ietf@ietf.org  Sat May 31 11:43:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04503
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 11:43:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19M8Nx-0006ia-Fg
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 11:35:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19M8Ld-0006df-CD
	for ietf@asgard.ietf.org; Sat, 31 May 2003 11:32:45 -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 LAA04261
	for <ietf@ietf.org>; Sat, 31 May 2003 11:32:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19M8Jx-0007m8-00
	for ietf@ietf.org; Sat, 31 May 2003 11:31:02 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 19M8Jx-0007m5-00
	for ietf@ietf.org; Sat, 31 May 2003 11:31:01 -0400
Received: from [63.202.92.152] (adsl-63-202-92-152.dsl.snfc21.pacbell.net [63.202.92.152])
	(authenticated bits=0)
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h4VFWfAG031225
	for <ietf@ietf.org>; Sat, 31 May 2003 08:32:41 -0700 (PDT)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05210619bafe7907c0f8@[63.202.92.152]>
In-Reply-To: <13622120747.20030530161224@brandenburg.com>
References: <00e901c3261b$a3dbcf50$56144104@eagleswings>
 <127103972754.20030529132930@brandenburg.com> 
 <3ED699EB.8090005@ehsco.com>
 <115140380105.20030529233617@brandenburg.com>
 <p05210603bafd388cbb49@[63.202.92.152]> <3ED79782.195F1A20@earthlink.net>
 <p05210607bafd52b3d9b3@[63.202.92.152]>
 <13622120747.20030530161224@brandenburg.com>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Sat, 31 May 2003 08:32:04 -0700
To: ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: The utilitiy of IP is at stake here
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 4:12 PM -0700 5/30/03, Dave Crocker wrote:
>Perhaps you could synthesize the numbers in a way that the carriers will
>agree to?   That it, sanitize out the competitive information, to
>produce something relevant only to spam control in the aggregate.

The numbers are a few years old, anecdotal (although at least they 
came from people inside the companies!), and not computed in the saw 
way. For instance, BigISP1 counted the time spent on customer service 
on spam-related topics plus sysop time plus connectivity costs, while 
BigISP2 only counted the latter two.

But, to be more relevant, let me say that all of the numbers were in 
millions of dollars.

To bludgeon the point a bit:

- Big ISPs and other mail service providers know how much spam is costing them.

- For some ISPs, the amount is in the millions of dollars.

- Even an expensive team of consultants could devise a trust-based or 
work-based protocol and shepherd it through the IETF for less than 
one tenth the annual cost for a single ISP.

Given the above, the reason that the people who are most financially 
hurt by the spam problem have not done anything about it from a 
protocol level is either that they are financially stupid or that 
their research into the solutions didn't result in a solution that 
would cost them more. I believe it is the latter. People outside 
those companies might have different opinions, but to say "if we 
invent a protocol that we think will work, they will use it" is 
nonsense.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Sat May 31 13:02:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05741
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 13:02:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19M9ZU-0000A6-KF
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 12:51:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19M9UQ-00005M-Q7
	for ietf@asgard.ietf.org; Sat, 31 May 2003 12:45:54 -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 MAA05471
	for <ietf@ietf.org>; Sat, 31 May 2003 12:45:52 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19M9Sl-0000Ld-00
	for ietf@ietf.org; Sat, 31 May 2003 12:44:11 -0400
Received: from h80ad268a.async.vt.edu ([128.173.38.138] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19M9Sj-0000La-00
	for ietf@ietf.org; Sat, 31 May 2003 12:44:10 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h4VGjcn1014458;
	Sat, 31 May 2003 12:45:38 -0400
Message-Id: <200305311645.h4VGjcn1014458@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Anthony Atkielski <anthony@atkielski.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here 
In-Reply-To: Your message of "Sat, 31 May 2003 16:44:32 +0200."
             <0c2b01c32783$26d97390$0a00000a@atkielski.com> 
References: <001601c3276d$e0fafed0$3b00a8c0@tomson.be>
            <0c2b01c32783$26d97390$0a00000a@atkielski.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-993142416P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sat, 31 May 2003 12:45:36 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-993142416P
Content-Type: text/plain; charset=us-ascii

On Sat, 31 May 2003 16:44:32 +0200, Anthony Atkielski <anthony@atkielski.com>  said:

> They must either harvest them or guess them.  For non-obvious e-mail
> addresses that are never published, they cannot practically do either of
> these, and so the addresses will not be spammed.

"that are never published".

That's one *TALL* order for a useful e-mail address.

That means that you can't join a mailing list for (say) cancer survivors,
or for people with persian cats, or for your church, or for other immigrants
from the same country as you... because then your address might be published.

Sort of limits the usefulness of e-mail.

That means that you can't use the Internet to buy things at a site that wants
an e-mail address to send you things like shipping confirmations.

Sort of limits the usefulness of e-mail even more.

For that matter, even if you're NOT on a mailing list, and don't purchase
things online, you have to worry that *NONE* of your correspondents use a
certain worm-prone MUA - if *they* get hit by a worm that finds your e-mail
address and a lists' e-mail address, suddenly your address has been used as the
faked source and published on a list you've never heard of.  Note that there's
a synergy here with the list issue above, if you ever post to a list....

And then the trawlers come through, and the spamming begins.

Sort of limits the usefulness of e-mail to a ridiculous level.

So it's not safe to join a mailing list, it's not safe to use it for any
e-commerce, and it's not safe to use it to communicate with the 85% of the
people who use the problem MUA.

Now what were you saying about useful?

--==_Exmh_-993142416P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+2NwwcC3lWbTT17ARAgSDAJsEXn/iFLEFH2BIl3u8iba9Tyr7FwCfWm8Z
Wb1EFVhfuNT4+jpdSfpmr0s=
=9Lmq
-----END PGP SIGNATURE-----

--==_Exmh_-993142416P--



From owner-ietf@ietf.org  Sat May 31 16:18:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08828
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 16:18:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MCHr-0002Jv-Rz
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 15:45:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MCGP-0002GI-5L
	for ietf@asgard.ietf.org; Sat, 31 May 2003 15:43:37 -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 PAA08519
	for <ietf@ietf.org>; Sat, 31 May 2003 15:43:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MCEj-0000wT-00
	for ietf@ietf.org; Sat, 31 May 2003 15:41:53 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MCEi-0000wP-00
	for ietf@ietf.org; Sat, 31 May 2003 15:41:52 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 7AB8B1396C; Sat, 31 May 2003 19:43:04 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Spam
References: <g37k88th1e.fsf@sa.vix.com> <3ED7AE4A.3080703@centive.com>
From: Paul Vixie <vixie@vix.com>
Date: 31 May 2003 19:43:04 +0000
In-Reply-To: <3ED7AE4A.3080703@centive.com>
Message-ID: <g3y90msy0n.fsf@sa.vix.com>
Lines: 37
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

> >if we could make spamganging so illegal that they were eventually not
> >replaced, then their traffic would be replaced by bulk e-mail from every
> >customer of every CRM (customer relationship management) company in the
> >world.
>
> I'm not sure why this follows.  Wiping out the fraudulent spammers would 
> take a War On Spam, with massive levels of propaganda to stir up public 
> opinion enough to justify the money it would cost.  In that kind of 
> environment, even in the aftermath, no white hat would dare spam; their 
> customers would immediately turn against them.

i apologize for sounding too much like a futurist in the above-quoted text.
i did not mean to sound speculative.

i've met with these people.  not just a few, but with dozens.  i know what
they want to do and i know why they aren't doing it and i know how much money
they think they can make/save/both if they could only send unsolicited bulk
e-mail.  the mere fact that "if everybody did it then no e-mail would ever
again be read" does not sway them at all.  the mere fact that the pond was
once poisoned by evil-intending bad actors is completely irrelevant to them.

what i don't understand about the internet engineering mindset is that y'all
think you can build a universal "distributed system" for end to end 
communications and that somehow it won't be used to its full potential.  you
think other people will "leave money on the table".  they just won't, ever!

once thinking that smtp would be the right answer for a global population,
or now thinking that smtp can be saved if we can just make abuse expensive,
is indicative of designers who think that the only consumers are Just Like
Them And Their Friends.  they were but aren't, and they won't ever be again!

get a grip!  the full spectrum of humanity is impossibly broad and is not
subject to the kinds of politeness rules that you think are implicit in the
act of taking every breath or step in a life.  and an interpersonal batch
communication system addressing such broadness Won't look much like smtp.
-- 
Paul Vixie



From owner-ietf@ietf.org  Sat May 31 17:13:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09727
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 17:13:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MDSP-0003iK-Sx
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 17:00:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MDNv-0003ea-RV
	for ietf@asgard.ietf.org; Sat, 31 May 2003 16:55:27 -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 QAA09287
	for <ietf@ietf.org>; Sat, 31 May 2003 16:55:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MDMF-00019b-00
	for ietf@ietf.org; Sat, 31 May 2003 16:53:44 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MDMF-00019Y-00
	for ietf@ietf.org; Sat, 31 May 2003 16:53:43 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4VKtPKk066314
	for <ietf@ietf.org>; Sat, 31 May 2003 22:55:25 +0200 (CEST)
Message-ID: <0c8301c327b6$f563b7b0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <001601c3276d$e0fafed0$3b00a8c0@tomson.be>            <0c2b01c32783$26d97390$0a00000a@atkielski.com> <200305311645.h4VGjcn1014458@turing-police.cc.vt.edu>
Subject: Re: The utilitiy of IP is at stake here 
Date: Sat, 31 May 2003 22:55:24 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Valdis writes:

> That's one *TALL* order for a useful e-mail address.

Not really.  A great many people never use e-mail for anything except
exchanging messages with friends and relatives.

> That means that you can't join a mailing list for
> (say) cancer survivors, or for people with persian
> cats, or for your church, or for other immigrants
> from the same country as you... because then your
> address might be published.

Perhaps ... but most people never join mailing lists, so this is not a
problem for the bulk of the Internet community.

> Sort of limits the usefulness of e-mail.

Hardly.  Most people don't use mailing lists.

> That means that you can't use the Internet
> to buy things at a site that wants an e-mail
> address to send you things like shipping confirmations.

Why not?  Many companies will not publish or share your address.

> For that matter, even if you're NOT on a mailing
> list, and don't purchase things online, you have
> to worry that *NONE* of your correspondents use a
> certain worm-prone MUA ...

Spare me the angry-young-male syndrome.

The vast majority of people using Outlook Express (I assume that's the MUA
you're reluctant to name) are not infected by worms.

> ... if *they* get hit by a worm that finds your e-mail
> address ...

_If_ they get hit by a worm.  But they generally do not get hit by worms.

> Sort of limits the usefulness of e-mail to a
> ridiculous level.

Most people seem to get a lot out of e-mail despite spam.  Most people don't
receive that much spam, unless their addresses are widely disseminated
and/or published.

> So it's not safe to join a mailing list, it's not
> safe to use it for any e-commerce, and it's not safe
> to use it to communicate with the 85% of the
> people who use the problem MUA.

Only the first point is valid, and even that depends on the mailing list.
E-commerce is not generally a problem, with reputable merchants, and the
"problem MUA" is not a problem for the vast majority of its users.

Your hyperbole is unwarranted and casts doubt upon your credibility for
those who know better.





From owner-ietf@ietf.org  Sat May 31 17:39:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10205
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 17:39:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MDwL-0004St-KM
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 17:31:01 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MDv9-0004P3-Em
	for ietf@asgard.ietf.org; Sat, 31 May 2003 17:29:47 -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 RAA10086
	for <ietf@ietf.org>; Sat, 31 May 2003 17:29:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MDtT-0001NF-00
	for ietf@ietf.org; Sat, 31 May 2003 17:28:03 -0400
Received: from [208.184.79.11] (helo=clint.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MDtS-0001NA-00
	for ietf@ietf.org; Sat, 31 May 2003 17:28:02 -0400
Received: from bbprime (208.184.79.253.songbird.com [208.184.79.253] (may be forged))
	by clint.songbird.com (8.11.6/8.11.6) with ESMTP id h4VLVpx31460;
	Sat, 31 May 2003 14:31:51 -0700
Date: Sat, 31 May 2003 14:28:59 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <020304736.20030531142859@brandenburg.com>
To: Paul Vixie <vixie@vix.com>
CC: ietf@ietf.org
Subject: Re: Spam
In-Reply-To: <g3y90msy0n.fsf@sa.vix.com>
References: <g37k88th1e.fsf@sa.vix.com> <3ED7AE4A.3080703@centive.com>
 <g3y90msy0n.fsf@sa.vix.com>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Paul,

PV> once thinking that smtp would be the right answer for a global population,
PV> or now thinking that smtp can be saved if we can just make abuse expensive,
PV> is indicative of designers who think that the only consumers are Just Like
PV> Them And Their Friends.  they were but aren't, and they won't ever be again!


Unfortunately, casting the issue in terms of saving or discarding SMTP
is also unhelpful. It makes sure that we debate lots of protocol
details, without having any basic agreement on the more import usage and
protection details that will drive the mundane technical choices.

On the other hand, a relevant point about current operations, versus
future operations, is how we move 100 million users.  But again, that is
best discussed in terms of the users and their usage, rather than the
protocol details.

So:  What is this better service supposed to look like?  How do we
transition a very large installed base to it.

Extra credit:  The transition question has more to do with user
motivation and choice than with technical engineering.

d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Sat May 31 18:03:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10627
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 18:03:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MEJd-00059U-Py
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 17:55:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MEDZ-00050H-J2
	for ietf@asgard.ietf.org; Sat, 31 May 2003 17:48:49 -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 RAA10388
	for <ietf@ietf.org>; Sat, 31 May 2003 17:48:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MEBt-0001Ro-00
	for ietf@ietf.org; Sat, 31 May 2003 17:47:05 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MEBs-0001Rl-00
	for ietf@ietf.org; Sat, 31 May 2003 17:47:04 -0400
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49])
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h4VLfUS16781
	for <ietf@ietf.org>; Sat, 31 May 2003 14:41:30 -0700
Date: Sat, 31 May 2003 14:41:29 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here 
In-Reply-To: <001601c3276d$e0fafed0$3b00a8c0@tomson.be>
Message-ID: <Pine.LNX.4.33.0305311426550.16737-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Sat, 31 May 2003, Tomson Eric (Yahoo.fr) wrote:

> How will the spammer's find her address?

Guessing and trying?

Online directory provided by her email provider?

Not understanding risks, she joins a seniors mail list?

Someone she corresponds with blasts an email to a bunch of
folks leaving all addresses exposed, and one of the
addressees does some action which exposes the email to a
spammer's harvesting process?

Or more explicitly, someone she knows copies her in a post to
a mailing list which is being harvested.

More I'm sure. The AOL address my wife uses was never used for
anything but family oriented email and never part of a list which
was posted to from that address. Yet she receives an inordinate amount of
filthy and body alteration spam. Since this is a very old AOL address and
was simply based on name and initials, I suspect one of the first two
approaches I listed above.

The point being that it isn't difficult to end up in the spammer's email
address lists.

Dave Morris






From owner-ietf@ietf.org  Sat May 31 18:20:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11935
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 18:20:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MEWl-00016n-5j
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 18:08:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MEPk-0006A0-4d
	for ietf@asgard.ietf.org; Sat, 31 May 2003 18:01:24 -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 SAA10497
	for <ietf@ietf.org>; Sat, 31 May 2003 18:01:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MEO4-0001TM-00
	for ietf@ietf.org; Sat, 31 May 2003 17:59:40 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MEO3-0001TJ-00
	for ietf@ietf.org; Sat, 31 May 2003 17:59:39 -0400
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49])
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h4VLs5S16801
	for <ietf@ietf.org>; Sat, 31 May 2003 14:54:05 -0700
Date: Sat, 31 May 2003 14:54:04 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <p05210619bafe7907c0f8@[63.202.92.152]>
Message-ID: <Pine.LNX.4.33.0305311448390.16737-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Sat, 31 May 2003, Paul Hoffman / IMC wrote:

> Given the above, the reason that the people who are most financially
> hurt by the spam problem have not done anything about it from a
> protocol level is either that they are financially stupid or that

I find your position curious for a couple of reasons:
  a.  You have now explicitly noted that your data is several
      years old
  b.  Three big mail providers (AOL and as I recall, MSN and Yahoo)
      recently announced a joint inititiative to deal with the spam
      problem.

Perhaps their costs have now changed to the point where a solution might
cost less than the cost of dealing with spam. Or they decided they
couldn't wait any longer for the IETF to take the problem seriously.

Dave Morris





From owner-ietf@ietf.org  Sat May 31 18:22:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12093
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 18:22:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MEd9-00038l-JT
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 18:15:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MEUL-0000SM-Nm
	for ietf@asgard.ietf.org; Sat, 31 May 2003 18:06:09 -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 SAA10950
	for <ietf@ietf.org>; Sat, 31 May 2003 18:06:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MESf-0001WO-00
	for ietf@ietf.org; Sat, 31 May 2003 18:04:25 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MESe-0001VG-00
	for ietf@ietf.org; Sat, 31 May 2003 18:04:24 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 1E3D613969
	for <ietf@ietf.org>; Sat, 31 May 2003 22:05:37 +0000 (GMT)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ietf@ietf.org
Subject: Re: Spam 
In-Reply-To: Message from Dave Crocker <dhc2@dcrocker.net> 
	of "Sat, 31 May 2003 14:28:59 MST."
	<020304736.20030531142859@brandenburg.com> 
X-Mailer: MH-E 7.3; nmh 1.0.4; GNU Emacs 21.3.1
Date: Sat, 31 May 2003 22:05:37 +0000
Message-Id: <20030531220537.1E3D613969@sa.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

(keith, this message is also meant to serve as an answer to your private mail)

> Unfortunately, casting the issue in terms of saving or discarding SMTP
> is also unhelpful. It makes sure that we debate lots of protocol
> details, without having any basic agreement on the more import usage
> and protection details that will drive the mundane technical choices.

well, but, so, the debate about protocol details was raging before i
started saying "stop trying to save smtp" so these items are at best
unrelated.

> On the other hand, a relevant point about current operations, versus
> future operations, is how we move 100 million users.  But again, that is
> best discussed in terms of the users and their usage, rather than the
> protocol details.
> 
> So:  What is this better service supposed to look like?

see further below, which was written in response to private mail from
keith before i saw dave's message (to which this is a direct reply.)

> How do we transition a very large installed base to it.

the whole installed base is in incredible pain right now and there will
be a lot of sites like mine who will switch over early, turning off
their tcp/25 service, as soon as we think there are reasonable
alternatives for reaching us.  (this contrasts with the ipv6 transition,
where the existing ipv4 installed base is not wholly in incredible pain;
only a few mega-networks are feeling incredible ipv4 pain, and the vast
majority of non-mega-networks is feeling no ipv4 pain at all.)

> Extra credit:  The transition question has more to do with user
> motivation and choice than with technical engineering.

how well i know that!  like i said, the motivation is overwhelming.  an
alternative only needs to barely work before it will be seen as compelling.

that means i'll be cutting off tcp/25 while most of the world has only that
way, or fax and phones, to reach me.  thousands, no, tens of thousands of
other sites will do likewise.  the mega-exporters of batched interpersonal
communications traffic will be the last to change over, since their costs
are the highest, but they (hotmail, aol, etc) will be forced to endure these
costs when the "reachability base" dwindles.

in other words, by waiting until the barn is on fire and the horses are
dying, the quality and stability of our alternative, and the costs of getting
moved to it, have become almost irrelevant.  i guess we can all pat ourselves
on the back now, for letting things get this bad, before we acted.  (NOT.)

i am damned close to turning off tcp/25 even if the only alternative is
telco and fax and netnews and web.  THAT is how the pain:gain ratio is now.
SO, telling me that moving 100M users is hard, won't make me believe it.

--------

now as to the question keith and dave both asked: "why does smtp have to die?"

i guess it could be done on top of esmtp but we'll have to be able to
put sig(heloname,ipsrc,privatekey) in the HELO, sig(fromaddr,privatekey)
in the MAIL, and crypt(rcptaddr,publickey) in the RCPT.  the receiving
relay should be able to determine, at esmtp session time, whether the
owner of the heloname'd server knows what ip address it is using and
that it knows it is sending this mail and that there is transitive
trust from it to you.  similar restrictions on the MAIL fromaddr.
we'd want to sign the recipient name using its public key to indicate
that the sender has a way of learning/reaching this key.  and so on.

but at smtp session time, the smtp speaker must be able to determine a
shared value system between sender and recipient, which means the
recipient's values must be known to the smtp speaker.  things such as
"i only accept e-mail that is promised to be solicited or non-bulk"
have to be able to be matched up with promises of the form "i promise
that this mail is solicited" or "i promise that this mail is not bulk".
the combination of authentic promises and transitive trust is enough
to ensure that all communications is consensual, which is an explicit
goal now that the internet community no longer has this as an implicit
assumption (due to its originally small size and closed nature.)

so, whether we use esmtp as a bearer channel is indeed irrelevant, so
long as we'd be willing to stop trying to maintain a distinction between
an MTA and MUA, and perform recipient-specified functions at session time,
and so long as we can add attributes to all the existing protocol elements.
but those are HUGE elements of the (e)smtp model, and the resulting protocol
can in my opinion be called "new" even if it looks superficially like what
we do now.  there's absolutely no reason to use the same port number, for
example.  there's no fallback.  if newproto doesn't work because the firewall
or nat or whatever only allows tcp/25 sessions, then give up and use the
telephone or fax machine.

transitive trust and mailbox/server/relay certificates and chains of same
are the much harder issues, technically.  pgp and x.509 are both HARD for
the majority of mailbox owners (think of your parents of grandparents) to
use.  to make a new global-scale system, we have to make it marketable.

--------

now as to my own motives:

my reason for harping on the "stop trying to save smtp" issue in recent
days here is just my disbelief that baynesian or other filters, or lists
of who's been naughty and who's been nice, or anything like that, can be
bolted on "usefully".  that stuff is all crutches and bandaids while what's
needed is a whole new monster.

my reason for making "all communications must be consensual" as the key
design criteria for a new interpersonal batch communication system is that
it's what i've always believed, from the earliest days of the first RBL which
later became MAPS, and it's the single thing that's most failed in the (e)smtp
model as we've exploded the endpoint population to the hundreds of millions.



From owner-ietf@ietf.org  Sat May 31 18:27:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12251
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 18:27:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MEf8-0003aV-4o
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 18:17:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MEXG-0001MR-LI
	for ietf@asgard.ietf.org; Sat, 31 May 2003 18:09: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 SAA11289
	for <ietf@ietf.org>; Sat, 31 May 2003 18:09:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MEVa-0001XP-00
	for ietf@ietf.org; Sat, 31 May 2003 18:07:26 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MEVZ-0001XM-00
	for ietf@ietf.org; Sat, 31 May 2003 18:07:26 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4VM98Kk066889
	for <ietf@ietf.org>; Sun, 1 Jun 2003 00:09:08 +0200 (CEST)
Message-ID: <0cbc01c327c1$41b61810$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <g37k88th1e.fsf@sa.vix.com> <3ED7AE4A.3080703@centive.com> <g3y90msy0n.fsf@sa.vix.com> <020304736.20030531142859@brandenburg.com>
Subject: Re: Spam
Date: Sun, 1 Jun 2003 00:09:07 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I think it is totally impractical to talk about moving 100 million users to
anything.  These are not the pioneer days of computing; there are hundreds
of millions of people using computers today, and you aren't going to move
them all to anything.  It's rather like suggesting that North American
switch from 120 VAC to 480 VDC for home electrical power.  It's not going to
happen.  Look at QWERTY keyboards and NTSC if you believe otherwise.

----- Original Message -----
From: "Dave Crocker" <dhc2@dcrocker.net>
To: "Paul Vixie" <vixie@vix.com>
Cc: <ietf@ietf.org>
Sent: Saturday, May 31, 2003 23:28
Subject: Re: Spam


> Paul,
>
> PV> once thinking that smtp would be the right answer for a global
population,
> PV> or now thinking that smtp can be saved if we can just make abuse
expensive,
> PV> is indicative of designers who think that the only consumers are Just
Like
> PV> Them And Their Friends.  they were but aren't, and they won't ever be
again!
>
>
> Unfortunately, casting the issue in terms of saving or discarding SMTP
> is also unhelpful. It makes sure that we debate lots of protocol
> details, without having any basic agreement on the more import usage and
> protection details that will drive the mundane technical choices.
>
> On the other hand, a relevant point about current operations, versus
> future operations, is how we move 100 million users.  But again, that is
> best discussed in terms of the users and their usage, rather than the
> protocol details.
>
> So:  What is this better service supposed to look like?  How do we
> transition a very large installed base to it.
>
> Extra credit:  The transition question has more to do with user
> motivation and choice than with technical engineering.
>
> d/
> --
>  Dave Crocker <mailto:dcrocker@brandenburg.com>
>  Brandenburg InternetWorking <http://www.brandenburg.com>
>  Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>
>
>
>




From owner-ietf@ietf.org  Sat May 31 18:37:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12450
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 18:37:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MEhp-0003ef-Na
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 18:20:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MEZp-00029a-D6
	for ietf@asgard.ietf.org; Sat, 31 May 2003 18:11:49 -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 SAA11503
	for <ietf@ietf.org>; Sat, 31 May 2003 18:11:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MEY9-0001Xi-00
	for ietf@ietf.org; Sat, 31 May 2003 18:10:05 -0400
Received: from gull.mail.pas.earthlink.net ([207.217.120.84])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MEY8-0001Xf-00
	for ietf@ietf.org; Sat, 31 May 2003 18:10:04 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by gull.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19MEZV-0003sP-00; Sat, 31 May 2003 15:11:29 -0700
Date: Sat, 31 May 2003 18:09:44 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: moore@cs.utk.edu, dhc2@dcrocker.net, vixie@vix.com, ietf@ietf.org
Subject: Re: Spam
Message-Id: <20030531180944.053e0074.moore@cs.utk.edu>
In-Reply-To: <020304736.20030531142859@brandenburg.com>
References: <g37k88th1e.fsf@sa.vix.com>
	<3ED7AE4A.3080703@centive.com>
	<g3y90msy0n.fsf@sa.vix.com>
	<020304736.20030531142859@brandenburg.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> PV> once thinking that smtp would be the right answer for a global
> PV> population, or now thinking that smtp can be saved if we can just make
> PV> abuse expensive, is indicative of designers who think that the only
> PV> consumers are Just Like Them And Their Friends.  they were but aren't,
> PV> and they won't ever be again!
> 
> 
> Unfortunately, casting the issue in terms of saving or discarding SMTP
> is also unhelpful. 

as is casting the issue in terms of "those who are stuck in old-fashioned 
thinking" vs. those that aren't.

perhaps if Paul were to talk about the technical features that the system
needs to have, it would be obvious whether or not it's more feasible to
shoehorn this into SMTP or to transition to another system.   or at least,
we'd be able to evaluate his assertion.   but trying to discuss this in the
current mode is pointless.




From owner-ietf@ietf.org  Sat May 31 18:40:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12633
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 18:40:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MEmw-0004Ow-Tu
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 18:25:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MEeX-0003Zg-0k
	for ietf@asgard.ietf.org; Sat, 31 May 2003 18:16:41 -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 SAA11897
	for <ietf@ietf.org>; Sat, 31 May 2003 18:16:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MEcq-0001Yr-00
	for ietf@ietf.org; Sat, 31 May 2003 18:14:56 -0400
Received: from mrburns.nildram.co.uk ([195.112.4.54])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MEcq-0001Yo-00
	for ietf@ietf.org; Sat, 31 May 2003 18:14:56 -0400
Received: from hourglass (unknown [81.6.214.202])
	by mrburns.nildram.co.uk (Postfix) with ESMTP
	id CCA0D1D6DDE; Sat, 31 May 2003 23:16:33 +0100 (BST)
From: "Christian de Larrinaga" <cdel@firsthand.net>
To: "Dave Crocker" <dcrocker@brandenburg.com>, "Paul Vixie" <vixie@vix.com>
Cc: <ietf@ietf.org>
Subject: RE: Spam
Date: Sat, 31 May 2003 23:16:49 +0100
Message-ID: <MABBIEBOAFJNELEGFHCKAECIIEAA.cdel@firsthand.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <020304736.20030531142859@brandenburg.com>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dave

>
> Extra credit:  The transition question has more to do with user
> motivation and choice than with technical engineering.

I'm curious. Why not just have users send their mail directly if they wish?


Christian




From owner-ietf@ietf.org  Sat May 31 19:10:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13174
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 19:10:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MFFo-0006RP-6F
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 18:55:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MF6V-0006Cf-UZ
	for ietf@asgard.ietf.org; Sat, 31 May 2003 18:45:35 -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 SAA12959
	for <ietf@ietf.org>; Sat, 31 May 2003 18:45:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MF4p-0001qt-00
	for ietf@ietf.org; Sat, 31 May 2003 18:43:51 -0400
Received: from scaup.mail.pas.earthlink.net ([207.217.120.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MF4p-0001qq-00
	for ietf@ietf.org; Sat, 31 May 2003 18:43:51 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by scaup.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19MF6F-0007He-00; Sat, 31 May 2003 15:45:19 -0700
Date: Sat, 31 May 2003 18:43:35 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Paul Vixie <paul@vix.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: Spam
Message-Id: <20030531184335.72e2ef97.moore@cs.utk.edu>
In-Reply-To: <20030531220537.1E3D613969@sa.vix.com>
References: <020304736.20030531142859@brandenburg.com>
	<20030531220537.1E3D613969@sa.vix.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> so, whether we use esmtp as a bearer channel is indeed irrelevant, 

okay, that's what I was thinking too.

but I also don't see any particular utility in authenticating either the
source IP address or the mail from address, and a fair amount of disadvantage
to both; I think we need a different token to authenticate the sender.
a lot of the problems with some of the existing proposals is that they try
to overload the existing from or mail from addresses too much.  even RFC 822
recognized that Sender is different than From is different than Return-Path.

> but those are HUGE elements of the (e)smtp model, and the resulting protocol
> can in my opinion be called "new" even if it looks superficially like what
> we do now.  there's absolutely no reason to use the same port number, for
> example.  there's no fallback.

I don't share your opinion that everyone will want to switch completely.
significant numbers of users will need fallback, at least for a transition 
period.  I would far prefer a solution that lets mail recievers turn a knob
that pessimizes handling of unauthenticated messages more and more (as more
and more legitimate senders start authenticating messages) than one which
forces receivers to maintain separate servers. (I'd also rather avoid the "how
do we design a new mail protocol" pandora's box - the amount of second-system
effect would be huge, and it would take years to sort it out)

even if we had to retro-fit something very different onto port 25,  it would
probably be more attractive to negotiate the new protocol within ESMTP than to
have a different protocol on a different port.



From owner-ietf@ietf.org  Sat May 31 19:13:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13356
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 19:13:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MFFo-0006SC-J5
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 18:55:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MFDu-0006Mk-71
	for ietf@asgard.ietf.org; Sat, 31 May 2003 18:53:14 -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 SAA13051
	for <ietf@ietf.org>; Sat, 31 May 2003 18:53:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MFCE-0001sY-00
	for ietf@ietf.org; Sat, 31 May 2003 18:51:30 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MFCD-0001sV-00
	for ietf@ietf.org; Sat, 31 May 2003 18:51:29 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4VMrBKk067278
	for <ietf@ietf.org>; Sun, 1 Jun 2003 00:53:11 +0200 (CEST)
Message-ID: <0cdf01c327c7$698bca50$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <20030531220537.1E3D613969@sa.vix.com>
Subject: Re: Spam 
Date: Sun, 1 Jun 2003 00:53:11 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Paul writes:

> the whole installed base is in incredible pain
> right now ...

Oooh ... let's not jump off the deep end here.  Spam is a nuisance for most
Internet users, not an "incredible pain."  It's very important to
distinguish between something that does real damage and something that
merely annoys.

> ... and there will be a lot of sites like mine who will
> switch over early, turning off their tcp/25 service, as
> soon as we think there are reasonable alternatives for
> reaching us.

Don't hold your breath.

> ... and the vast majority of non-mega-networks is feeling
> no ipv4 pain at all.

The same is true for spam.

> like i said, the motivation is overwhelming.

I don't think so.  Apart from a minority of power users, most people aren't
exactly fuming over spam.  It's a nuisance, like postal junk mail, but it's
not a preoccupation.

> i am damned close to turning off tcp/25 even if the
> only alternative is telco and fax and netnews and web.

Then perhaps you should do so.  It sounds like you're on the verge of a
heart attack right now.

> SO, telling me that moving 100M users is hard, won't
> make me believe it.

And not believing it won't make it any less true.  Think IMAP, encryption
and digital signatures (built in to OE for years now, never used by anyone),
PNG (around since forever, but still practically ignored), and so on.

> if newproto doesn't work because the firewall or nat
> or whatever only allows tcp/25 sessions, then give up
> and use the telephone or fax machine.

Wow!  You must have an unusual user community.  In some organizations, you'd
be fired for having an attitude like that.

> that stuff is all crutches and bandaids while what's
> needed is a whole new monster.

Nothing that depends on automation will work, because no automated system
can distinguish between spam and legitimate e-mail.  Any system will require
human intervention.  And human intervention is likely to be an obstacle to
implementation and compliance if human users see it as more trouble than it
is worth.  And human users who are not drowning in spam (and most aren't)
will be disinclined to favor any kind of human intervention at all.

> my reason for making "all communications must be
> consensual" as the key design criteria for a new
> interpersonal batch communication system is that
> it's what i've always believed ...

That's equivalent to having a screening device on your telephone that only
rings the phone if callers dial a certain number code.  This works for a
handful of telephone subscribers, but for most others, it is simply not
practical.  In most situations, you must be able to accepted unsolicited
communications, without requiring any kind of prior consent.





From owner-ietf@ietf.org  Sat May 31 19:27:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12635
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 18:40:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MEhp-0003el-Vf
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 18:20:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MEaO-0002Iu-3M
	for ietf@asgard.ietf.org; Sat, 31 May 2003 18:12:24 -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 SAA11563
	for <ietf@ietf.org>; Sat, 31 May 2003 18:12:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MEYi-0001Y2-00
	for ietf@ietf.org; Sat, 31 May 2003 18:10:40 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MEYh-0001Xz-00
	for ietf@ietf.org; Sat, 31 May 2003 18:10:39 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h4VMCLKk066920
	for <ietf@ietf.org>; Sun, 1 Jun 2003 00:12:21 +0200 (CEST)
Message-ID: <0cc201c327c1$b518d220$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.33.0305311426550.16737-100000@egate.xpasc.com>
Subject: Re: The utilitiy of IP is at stake here 
Date: Sun, 1 Jun 2003 00:12:21 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

David writes:

> Guessing and trying?

That would require tens of thousands or even millions of bounces for every
successful mailing attempt.  I don't think anyone is doing it that way.

> Online directory provided by her email provider?

Which e-mail providers are providing online directories?  And how many of
these directories allow you to extract addresses without specifying any
search parameters (such as a name)?

> Not understanding risks, she joins a seniors mail list?

Possible, but not likely.

> Someone she corresponds with blasts an email to
> a bunch of folks leaving all addresses exposed,
> and one of the addressees does some action which
> exposes the email to a spammer's harvesting process?

This is getting more and more farfetched.

> Or more explicitly, someone she knows copies her
> in a post to a mailing list which is being harvested.

A list to which she doesn't belong?  Again, this seems unlikely.

> The point being that it isn't difficult to end up
> in the spammer's email address lists.

I have quite a few addresses that remain untouched.  Only the ones for which
an obvious harvesting path exists have received spam.




From owner-ietf@ietf.org  Sat May 31 19:43:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13829
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 19:43:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MFo1-0007mc-Dc
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 19:30:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MFfK-0007dK-Sb
	for ietf@asgard.ietf.org; Sat, 31 May 2003 19:21:34 -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 TAA13575
	for <ietf@ietf.org>; Sat, 31 May 2003 19:21:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MFde-00021Q-00
	for ietf@ietf.org; Sat, 31 May 2003 19:19:50 -0400
Received: from windlord.stanford.edu ([171.64.19.147])
	by ietf-mx with smtp (Exim 4.12)
	id 19MFdd-00021N-00
	for ietf@ietf.org; Sat, 31 May 2003 19:19:49 -0400
Received: (qmail 1734 invoked by uid 50); 31 May 2003 23:21:25 -0000
To: "IETF Discussion" <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
References: <Pine.LNX.4.33.0305311426550.16737-100000@egate.xpasc.com>
	<0cc201c327c1$b518d220$0a00000a@atkielski.com>
In-Reply-To: <0cc201c327c1$b518d220$0a00000a@atkielski.com> ("Anthony
 Atkielski"'s message of "Sun, 1 Jun 2003 00:12:21 +0200")
From: Russ Allbery <rra@stanford.edu>
Organization: The Eyrie
Date: Sat, 31 May 2003 16:21:25 -0700
Message-ID: <ylvfvq8zyi.fsf@windlord.stanford.edu>
Lines: 15
User-Agent: Gnus/5.090008 (Oort Gnus v0.08) XEmacs/21.4 (Portable Code,
 sparc-sun-solaris2.6)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Anthony Atkielski <anthony@atkielski.com> writes:
> David writes:

>> Guessing and trying?

> That would require tens of thousands or even millions of bounces for
> every successful mailing attempt.  I don't think anyone is doing it that
> way.

Objective evidence indicates that your belief is incorrect.  Dictionary
spam is, in fact, quite common.  It is, predictably, mostly targetted at
large ISPs where the hit rate is better than with personal domains.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>



From owner-ietf@ietf.org  Sat May 31 21:11:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15007
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 21:11:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MH3v-00019g-Ra
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 20:51:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MH2f-00014T-OS
	for ietf@asgard.ietf.org; Sat, 31 May 2003 20:49:45 -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 UAA14787
	for <ietf@ietf.org>; Sat, 31 May 2003 20:49:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MH0y-0002Lp-00
	for ietf@ietf.org; Sat, 31 May 2003 20:48:00 -0400
Received: from mail16.speakeasy.net ([216.254.0.216] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MH0x-0002Lm-00
	for ietf@ietf.org; Sat, 31 May 2003 20:47:59 -0400
Received: (qmail 3014 invoked from network); 1 Jun 2003 00:49:40 -0000
Received: from unknown (HELO 192.168.254.124) ([66.92.168.196])
          (envelope-sender <dja2003@hotpop.com>)
          by mail16.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <vjs@calcite.rhyolite.com>; 1 Jun 2003 00:49:40 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: The utilitiy of IP is at stake here
Date: Sat, 31 May 2003 20:52:03 -0400
User-Agent: KMail/1.5
References: <3ED7A03C.1040603@ehsco.com> <200305302153.h4ULrATA019693@calcite.rhyolite.com>
In-Reply-To: <200305302153.h4ULrATA019693@calcite.rhyolite.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305312052.04011.dja2003@hotpop.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Vernon Schryver <vjs@calcite.rhyolite.com> wrote:

 > Do a sanity check and think about how you would
 > spend $0.5B on filtering spam.

Hmmmm, that oughta buy a lot of hit-man contracts....  B-)

-- 
David J. Aronson, Unemployed Software Engineer near Washington DC
See http://destined.to/program/ for online resume, and other info




From owner-ietf@ietf.org  Sat May 31 21:21:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15300
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 21:21:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MHHf-0001Np-C9
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 21:05:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MH69-00019k-96
	for ietf@asgard.ietf.org; Sat, 31 May 2003 20:53:21 -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 UAA14817
	for <ietf@ietf.org>; Sat, 31 May 2003 20:53:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MH4S-0002Mc-00
	for ietf@ietf.org; Sat, 31 May 2003 20:51:36 -0400
Received: from out001pub.verizon.net ([206.46.170.140] helo=out001.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MH4Q-0002MY-00
	for ietf@ietf.org; Sat, 31 May 2003 20:51:34 -0400
Received: from earthlink.net ([4.65.81.67]) by out001.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030601005201.RUFN12592.out001.verizon.net@earthlink.net>;
          Sat, 31 May 2003 19:52:01 -0500
Message-ID: <3ED94D1C.C94BDA21@earthlink.net>
Date: Sat, 31 May 2003 17:47:24 -0700
From: Peter Deutsch <pdeutsch@earthlink.net>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Anthony Atkielski <anthony@atkielski.com>
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
References: <Pine.LNX.4.33.0305311426550.16737-100000@egate.xpasc.com> <0cc201c327c1$b518d220$0a00000a@atkielski.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [4.65.81.67] at Sat, 31 May 2003 19:52:01 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

g'day,


Anthony Atkielski wrote:
...
> > Someone she corresponds with blasts an email to
> > a bunch of folks leaving all addresses exposed,
> > and one of the addressees does some action which
> > exposes the email to a spammer's harvesting process?
> 
> This is getting more and more farfetched.

Oh, really now...

Anthony, please don't take this the wrong way, but it's really starting
to look either like you don't know enough to extrapolate out from your
own experience, or you're just trolling.

Consider the following randomly chosen message from Dave Farber's IP
list from earlier today:


----------8<----------8<----------8<----------8<----------8<----------
      cut here    cut here    cut here    cut here    cut here


Subject:         [IP] more on Stopping spam isn't as easy as you might
hope
   Date:         Sat, 31 May 2003 13:07:01 -0400
   From:         Dave Farber <dave@farber.net>
     To:         ip@v2.listbox.com



>Date: Sat, 31 May 2003 12:49:42 -0400
>From: Meng Weng Wong <mengwong@dumbo.xxxxx.com>
>Subject: Re: [IP] Stopping spam isn't as easy as you might hope
>To: johnl@xxxx.com
>Cc: Dave Farber <dave@farber.net>
>
> >Date: Sat, 31 May 2003 04:01:08 -0400
> >From: John R Levine <johnl@xxxx.com>
> >
> >The social problem with designated sender is that there are plenty of
> >perfectly legitimate reasons for mail from a domain to originate someplace
> >other than its home network.  Lots of people maintain accounts at Yahoo or
> >other free mail providers, but send mail with their Yahoo address from
> >their home ISP using the ISP's mail server.
>
>MUAs should add a configuration field to distinguish header "From:"
>vs. envelope from.  That solves this problem.  If they choose not to
>do this, they should send mail through Yahoo's web interface.  That's
>a fair constraint.  Yahoo gives them free email; in return, they're
>supposed to give Yahoo their eyeballs.
...

----------8<----------8<----------8<----------8<----------8<----------
      cut here    cut here    cut here    cut here    cut here

Observe that this message contained not one, but two additional email
addresses besides Dave's and the list address Note also, that the folks
over there are pounding on this problem, as well (nd for those few
who've been out of the galaxy, Dave's list is a distilled collection of
posts, most of which are forwarded to him, so almost every posting Dave
sends on has at least one email address in it. Some, including this
randomly chosen example, have more.)


Note, there's nothing special about the IP list in this case, I just
used it because Dave's list is the next one in my mailbox after the IETF
list, so I didn't have to go far to find a refutation of your claim.
Most Usenet groups would probably turn up an example or two, if you
bothered to go look. Note also that as a curtesy, I've blanked the
domain names in this example, but this is a formality, since this list
is available in a public archive, so you don't even need to subscribe to
harvest it...


> > Or more explicitly, someone she knows copies her
> > in a post to a mailing list which is being harvested.
> 
> A list to which she doesn't belong?  Again, this seems unlikely.

see above...

> > The point being that it isn't difficult to end up
> > in the spammer's email address lists.
> 
> I have quite a few addresses that remain untouched.  Only the ones for which
> an obvious harvesting path exists have received spam.

Please stop thinking the entire world is just like you. It's not, so
behaving like it is can be quite counterproductive (not to mention
downright harmful if engineering decisions actually get made based upon
your ignorance).

Put another way, I'm happy for you that spam is not yet a major problem
for you. It's a major problem for lots of people on this list. More
importantly, it's perceived to be a growing problem for the rest of the
Internet, for which a solution will be needed in the not too distant
future, so people on this list are discussing the near future, not
*your* particular present reality. Your "but it's not a problem for me"
reaction is more than distracting, it's downright counter-productive in
this context.



				- peterd



-- 
---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software

    "There are more things in heaven and earth, Horatio, Than are
     dreamt of in your philosophy." 

                        - Hamlet, Act I, Scene V
 
---------------------------------------------------------------------



From owner-ietf@ietf.org  Sat May 31 21:23:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15445
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 21:23:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MHHf-0001Nv-MR
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 21:05:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MH8S-0001E4-Fg
	for ietf@asgard.ietf.org; Sat, 31 May 2003 20:55:44 -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 UAA14824
	for <ietf@ietf.org>; Sat, 31 May 2003 20:55:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MH6m-0002Mq-00
	for ietf@ietf.org; Sat, 31 May 2003 20:54:00 -0400
Received: from mail16.speakeasy.net ([216.254.0.216] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MH6k-0002Mn-00
	for ietf@ietf.org; Sat, 31 May 2003 20:53:58 -0400
Received: (qmail 10687 invoked from network); 1 Jun 2003 00:55:40 -0000
Received: from unknown (HELO 192.168.254.124) ([66.92.168.196])
          (envelope-sender <dja2003@hotpop.com>)
          by mail16.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <william@elan.net>; 1 Jun 2003 00:55:40 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: william@elan.net
Subject: Re: Last 7 days on the IETF list
Date: Sat, 31 May 2003 20:58:04 -0400
User-Agent: KMail/1.5
Cc: ietf@ietf.org
References: <Pine.LNX.4.44.0305301736050.20347-100000@sokol.elan.net>
In-Reply-To: <Pine.LNX.4.44.0305301736050.20347-100000@sokol.elan.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305312058.04540.dja2003@hotpop.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

william@elan.net wrote:

 > I don't think posting message size is quite appropriate as part of
 > your statistics and even more particularly as a criteria to order the
 > list. Unless I'm mistaken you're calculating bytes for entire message
 > but often > 75% comes from another message being replied to

That has its own implications, which IMHO should definitely be taken into 
account.  'Nuff said?

-- 
David J. Aronson, Unemployed Software Engineer near Washington DC
See http://destined.to/program/ for online resume, and other info




From owner-ietf@ietf.org  Sat May 31 21:34:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15762
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 21:34:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MHav-0002il-Ce
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 21:25:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MHON-0001lc-2M
	for ietf@asgard.ietf.org; Sat, 31 May 2003 21:12:11 -0400
Received: from carmen.ipv6.tilab.com (carmen.ipv6.tilab.com [163.162.170.198] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15082
	for <ietf@ietf.org>; Sat, 31 May 2003 21:12:08 -0400 (EDT)
Received: from carmen.ipv6.tilab.com (localhost [IPv6:::1])
	by carmen.ipv6.tilab.com (8.12.9/8.12.3) with ESMTP id h51131mV026372
	for <ietf@ietf.org>; Sun, 1 Jun 2003 03:03:01 +0200 (MEST)
Received: (from root@localhost)
	by carmen.ipv6.tilab.com (8.12.9/8.12.3/Submit) id h511313O026371
	for ietf@ietf.org; Sun, 1 Jun 2003 03:03:01 +0200 (MEST)
Date: Sun, 1 Jun 2003 03:03:01 +0200 (MEST)
From: Super-User <root@carmen.ipv6.tilab.com>
Message-Id: <200306010103.h511313O026371@carmen.ipv6.tilab.com>
To: ietf@ietf.org
Subject: The IETF_Censored mailing list
Sender: owner-ietf@ietf.org
Precedence: bulk


                        The IETF_Censored mailing list
                                       
   At times, the IETF list is subject to debates that have little to do
   with the purposes for which the IETF list was created. Some people
   would appreciate a "quieter" forum for the relevant debates that take
   place, but the IETF's policy of openness has so far prevented the IETF
   from imposing any censorship policy on the IETF@ietf.org list.
   
   To give people an alternative, there is a list called
   "ietf_censored@carmen.ipv6.cselt.it".
   
   This list is a sublist (that is, it gets the same messages as) the
   open IETF discussion list. However, this list will not forward all
   messages; in particular, the filters have been set so that persons and
   discussions that are, in the view of Raffaele D'Albenzio, irrelevant
   to the IETF list are not forwarded.
   
   Because this filter is automated, the criteria include:
     * Well known troublemakers
     * Well known crosspostings
     * Subjects that have led to recent non-conclusive exchanges
     * Some ways to say "unsubscribe"
     * Some "out-of-office-reply" messages
       
   To join the list, send the word "subscribe" in the BODY of a message
   to ietf_censored-request@carmen.ipv6.cselt.it (the URL here is an RFC
   2368 mailto URL that does the Right Thing).
   
   To unsubscribe, send the word "unsubscribe" in the BODY of a message
   to ietf_censored-request@carmen.ipv6.cselt.it. Do not send to the list
   - your message will be filtered!
   (members of the main IETF list itself must follow instructions for
   that list, of course. You are only a member of ietf_censored if there
   is a comment on the bottom of your IETF list mail saying that the
   message has been sent through the ietf_censored list.)
   
   For fun, there is a special list for the rejected messages:
   ietf_censored-rejects@carmen.ipv6.cselt.it - subscribe in the same
   fashion, by mail to ietf_censored-rejects-request@carmen.ipv6.cselt.it
   
   By public request, the current set of filters are listed at
   http://vesuvio.ipv6.tilab.com/cgi-bin/ietf_censored-filters
   
   This page is http://carmen.ipv6.cselt.it/ietf_censored.html, and is
   posted monthly in text form to ietf@ietf.org
     _________________________________________________________________
   
   Raffaele D'Albenzio < root@carmen.ipv6.cselt.it>



From owner-ietf@ietf.org  Sat May 31 22:24:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA16516
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 22:24:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MIIO-00042Q-Lt
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 22:10:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MIHh-0003wv-2Q
	for ietf@asgard.ietf.org; Sat, 31 May 2003 22:09:21 -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 WAA16350
	for <ietf@ietf.org>; Sat, 31 May 2003 22:09:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MIG0-0002oG-00
	for ietf@ietf.org; Sat, 31 May 2003 22:07:36 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MIFz-0002o9-00
	for ietf@ietf.org; Sat, 31 May 2003 22:07:35 -0400
Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1])
	by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id DAA27570
	for <ietf@ietf.org>; Sun, 1 Jun 2003 03:09:16 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by pigeon.ecs.soton.ac.uk (8.9.3p2/8.9.3) with ESMTP id DAA18856
	for <ietf@ietf.org>; Sun, 1 Jun 2003 03:09:15 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id h5129FL29220
	for ietf@ietf.org; Sun, 1 Jun 2003 03:09:15 +0100
Date: Sun, 1 Jun 2003 03:09:15 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: Answering questions and defamation (was: RE: The utilitiy of IP is at stake here)
Message-ID: <20030601020915.GE7127@login.ecs.soton.ac.uk>
References: <Pine.LNX.4.44.0305301553050.17819-100000@commander.av8.net> <267841966.1054312648@p3.JCK.COM> <E19LyV9-000Khr-Uq@ran.psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E19LyV9-000Khr-Uq@ran.psg.com>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, May 30, 2003 at 10:01:55PM -0700, Randy Bush wrote:
> > From: John C Klensin <john-ietf@jck.com>
> > To: Dean Anderson <dean@av8.com>
> 
> john, don't you have a mail filter?

Trouble is even after kill-filing the trolls the good folk still rise to
the bait so I'm just cutting 50% of the posts (well, less if you look at
the stats that were posted after I filtered the chart-toppers :)

Tim



From owner-ietf@ietf.org  Sat May 31 22:28:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA16723
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 22:28:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MIS7-0004Da-ME
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 22:20:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MILg-00042i-2h
	for ietf@asgard.ietf.org; Sat, 31 May 2003 22:13:28 -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 WAA16436
	for <ietf@ietf.org>; Sat, 31 May 2003 22:13:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MIJz-0002q5-00
	for ietf@ietf.org; Sat, 31 May 2003 22:11:43 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MIJy-0002q2-00
	for ietf@ietf.org; Sat, 31 May 2003 22:11:42 -0400
Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1])
	by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id DAA27636
	for <ietf@ietf.org>; Sun, 1 Jun 2003 03:13:24 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by pigeon.ecs.soton.ac.uk (8.9.3p2/8.9.3) with ESMTP id DAA18962
	for <ietf@ietf.org>; Sun, 1 Jun 2003 03:13:24 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id h512DOG29242
	for ietf@ietf.org; Sun, 1 Jun 2003 03:13:24 +0100
Date: Sun, 1 Jun 2003 03:13:24 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Re: The IETF_Censored mailing list
Message-ID: <20030601021324.GG7127@login.ecs.soton.ac.uk>
References: <200306010103.h511313O026371@carmen.ipv6.tilab.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200306010103.h511313O026371@carmen.ipv6.tilab.com>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

How timely...

On Sun, Jun 01, 2003 at 03:03:01AM +0200, Super-User wrote:
> 
>                         The IETF_Censored mailing list
>                                        
>    At times, the IETF list is subject to debates that have little to do
>    with the purposes for which the IETF list was created. Some people
>    would appreciate a "quieter" forum for the relevant debates that take
>    place, but the IETF's policy of openness has so far prevented the IETF
>    from imposing any censorship policy on the IETF@ietf.org list.
>    
>    To give people an alternative, there is a list called
>    "ietf_censored@carmen.ipv6.cselt.it".
>    
>    This list is a sublist (that is, it gets the same messages as) the
>    open IETF discussion list. However, this list will not forward all
>    messages; in particular, the filters have been set so that persons and
>    discussions that are, in the view of Raffaele D'Albenzio, irrelevant
>    to the IETF list are not forwarded.
>    
>    Because this filter is automated, the criteria include:
>      * Well known troublemakers
>      * Well known crosspostings
>      * Subjects that have led to recent non-conclusive exchanges
>      * Some ways to say "unsubscribe"
>      * Some "out-of-office-reply" messages
>        
>    To join the list, send the word "subscribe" in the BODY of a message
>    to ietf_censored-request@carmen.ipv6.cselt.it (the URL here is an RFC
>    2368 mailto URL that does the Right Thing).
>    
>    To unsubscribe, send the word "unsubscribe" in the BODY of a message
>    to ietf_censored-request@carmen.ipv6.cselt.it. Do not send to the list
>    - your message will be filtered!
>    (members of the main IETF list itself must follow instructions for
>    that list, of course. You are only a member of ietf_censored if there
>    is a comment on the bottom of your IETF list mail saying that the
>    message has been sent through the ietf_censored list.)
>    
>    For fun, there is a special list for the rejected messages:
>    ietf_censored-rejects@carmen.ipv6.cselt.it - subscribe in the same
>    fashion, by mail to ietf_censored-rejects-request@carmen.ipv6.cselt.it
>    
>    By public request, the current set of filters are listed at
>    http://vesuvio.ipv6.tilab.com/cgi-bin/ietf_censored-filters
>    
>    This page is http://carmen.ipv6.cselt.it/ietf_censored.html, and is
>    posted monthly in text form to ietf@ietf.org
>      _________________________________________________________________
>    
>    Raffaele D'Albenzio < root@carmen.ipv6.cselt.it>



From owner-ietf@ietf.org  Sat May 31 22:34:16 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA16946
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 22:34:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MIS8-0004Dh-1b
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 22:20:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MIMq-00042k-RL
	for ietf@asgard.ietf.org; Sat, 31 May 2003 22:14:40 -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 WAA16442
	for <ietf@ietf.org>; Sat, 31 May 2003 22:14:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MILA-0002qB-00
	for ietf@ietf.org; Sat, 31 May 2003 22:12:56 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MIL9-0002q8-00
	for ietf@ietf.org; Sat, 31 May 2003 22:12:55 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 2531713948
	for <ietf@ietf.org>; Sun,  1 Jun 2003 02:14:07 +0000 (GMT)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ietf@ietf.org
Subject: Re: Spam 
In-Reply-To: Message from Keith Moore <moore@cs.utk.edu> 
	of "Sat, 31 May 2003 18:43:35 -0400."
	<20030531184335.72e2ef97.moore@cs.utk.edu> 
X-Mailer: MH-E 7.3; nmh 1.0.4; GNU Emacs 21.3.1
Date: Sun, 01 Jun 2003 02:14:07 +0000
Message-Id: <20030601021407.2531713948@sa.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> ... I also don't see any particular utility in authenticating either
> the source IP address or the mail from address, and a fair amount of
> disadvantage to both; I think we need a different token to
> authenticate the sender.

knowing the intent of the owner of the host is important.  we can't
tolerate any more hosts which become open proxies or open relays by
virtue of having swallowed an ms-outlook script-cookie pif-file.  if
a host hasn't made its intent to send e-mail known through a trusted
framework, then there's no reason for me to accept a tcp session from
it.  (credit goes to margie arbon of maps for proving this to me.)

> a lot of the problems with some of the existing proposals is that they
> try to overload the existing from or mail from addresses too much.
> even RFC 822 recognized that Sender is different than From is
> different than Return-Path.

the fact that any of the requirements which fall out of the new design
are incompatible with or inconvenient when viewed from an rfc821 or
rfc822 context should probably be viewed as neutral, or a feature.

using (e)smtp as a bearer channel for ibcs(*) might be expedient.  or not.

> I don't share your opinion that everyone will want to switch completely.

i know.  however, it doesn't matter.  you and a lot of people are free to
remain with the current system.  noone will stop you.  perhaps if you
become a small enough eyeball market, the spammers would leave you alone.

> significant numbers of users will need fallback, at least for a
> transition period.  I would far prefer a solution that lets mail
> recievers turn a knob that pessimizes handling of unauthenticated
> messages more and more (as more and more legitimate senders start
> authenticating messages) than one which forces receivers to maintain
> separate servers. (I'd also rather avoid the "how do we design a new
> mail protocol" pandora's box - the amount of second-system effect
> would be huge, and it would take years to sort it out)

i can imagine a fair number of mta authors deciding with you that they
ought to try ibcs first and then fall back to smtp if there is no _ibcs._tcp
SRV RR for the destination.  however, i expect that most remaining smtp
servers will be rejecting so damned much e-mail by that time that the
actual value of such fallback will be indistinguishable from nil.  (ymmv.)

> even if we had to retro-fit something very different onto port 25, it
> would probably be more attractive to negotiate the new protocol within
> ESMTP than to have a different protocol on a different port.

there's some small possibility of negotiating this on top of tcp/465,
but not tcp/25.  there's too much i need to know before i'll accept a
command, even a helo command, from an initiator.

---
(*) ibcs = interpersonnal batch communication system

--
Paul Vixie



From owner-ietf@ietf.org  Sat May 31 23:14:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17507
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 23:14:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MJ56-00068C-V0
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 23:00:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MIzN-0005wi-Gx
	for ietf@asgard.ietf.org; Sat, 31 May 2003 22:54:29 -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 WAA17286
	for <ietf@ietf.org>; Sat, 31 May 2003 22:54:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MIxh-00035Y-00
	for ietf@ietf.org; Sat, 31 May 2003 22:52:45 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MIxf-00035V-00
	for ietf@ietf.org; Sat, 31 May 2003 22:52:43 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 208862; Sat, 31 May 2003 21:53:50 -0500
Message-ID: <3ED96AD9.7050003@ehsco.com>
Date: Sat, 31 May 2003 21:54:17 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Paul Vixie <paul@vix.com>, ietf@ietf.org
Subject: Re: Spam
References: <020304736.20030531142859@brandenburg.com>	<20030531220537.1E3D613969@sa.vix.com> <20030531184335.72e2ef97.moore@cs.utk.edu>
In-Reply-To: <20030531184335.72e2ef97.moore@cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/31/2003 5:43 PM Keith Moore wrote:

> but I also don't see any particular utility in authenticating either
> the source IP address or the mail from address,

One of the potential benefits of binding IP address to the host identity
would be enforcement. A spammer may be able to crank millions of
identities into thousands of domains, but they will only ever have a
handful of servers and that smaller subset would be significantly easier
to enforce against, at least until they move.

The principle benefit of binding sender identity is forgery prevention
while preserving mobility. Folks can argue that the optional mechanisms
for doing this today are adequate towards this, but as long as they are
optional they will be limited. There are also benefits for binding the
"return-path" identity at the transfer level, specifically for features
like header encryption, as well as for control messages (transfer headers
without message headers or a message body).

> disadvantage to both; I think we need a different token to authenticate
> the sender. a lot of the problems with some of the existing proposals
> is that they try to overload the existing from or mail from addresses
> too much.  even RFC 822 recognized that Sender is different than From
> is different than Return-Path.

Just as a point, the 822 separation between Sender and From has become
largely irrelevant in modern usage, and a modernized equivalent would
likely need to use a different metaphor (not that I want to argue over
what that metaphor should be right now, just pointing out that the 822
model isn't particular relevant anymore). I agree that there needs to be a
distinction between the ~entity who authored the message and the ~entity
who is responsible for the message being transferred. I also think they
need separate identitifiers when they are different.

> I don't share your opinion that everyone will want to switch
> completely. significant numbers of users will need fallback, at least
> for a transition period.

There will certainly be a need for SMTP for a long time to come. Lots of
sites won't be able to switch for some time to come, for whatever reasons,
and this will be especially true the further you get from the G8 world.
However, that doesn't mean that everybody will need to run SMTPng
gateways. There is also the ability to run SMTPng and SMTP as separate
transfer networks, with gateways in between them at critical points (such
as at ISPs).

For example, Hotmail and AOL exchange mail directly already, and they
could use SMTPng for these exchanges and immediately start to take
advantage of the available features, regardless of what they use to talk
to the rest of the world. Meanwhile, these same benefits would motivate
the telco ISPs to setup an SMTPng gateway that talked to those sites, and
these same features could motivate corporates and governments, and so
forth. As this spread outwards, the primary communication for the majority
of the site-to-site exchanges would move to the SMTPng network. Once the
smaller sites decided they wanted to participate in direct transfers, they
could just switch over with no loss in connectivity (except to places on
export-control lists, perhaps).

At some point it might even be possible to route legacy messages through
the SMTPng network somehow, for those remaining sites who haven't
upgraded. As a radical approach, ISPs could do this by making all DNS
lookups for MX RRs answer with their SMTP-SMTPng gateway address.

Anyway, my personal thinking is that we can probably reach a tipping point
with just a few thousand servers, if they are the right ones anyway, and
after that the upgrades can spread outwards independently. My guess is
that the 80/20 rule probably applies to email, in that 80% of the messages
are probably routed through 20% of the mail servers, and getting a sizable
portion of that 20% would likely be enough to capture most of the
messaging network.

BTW, this is the same reason why we don't need to worry about ~100 million
users. We only have to worry about the site-to-site external servers. We
don't have to worry about their internal servers.

> I would far prefer a solution that lets mail
> recievers turn a knob that pessimizes handling of unauthenticated
> messages more and more (as more and more legitimate senders start
> authenticating messages) than one which forces receivers to maintain
> separate servers.

There are two reasons I have for not trying it. First of all, each change
request would be measured by the cost of that change in comparison to the
cost of modifying existing codebases. Several elements might be declared
as necessary but would still be rejected as unjustifiable. Some of the big
changes -- like splitting the transfer and message headers, which would
require new mailstore services for most systems -- would get tremendous
pushback, and might not even make the cut.

Secondarily, antyhing that did get through would be the proverbial square
peg, which would have to be encapsulated, converted, and bit-stuffed into
the proverbial round hole. All of this would make implementation much more
difficult, and would in turn make SMTP/821 more fragile.

My feeling is that the whole effort would be much more likely to succeed
if it were a from-scratch design. In fact, trying to do this inside SMTP
seems like a pretty good strategy for making sure that it either doesn't
happen at all, or that whatever gets through would be watered down and not
have been worth the effort.

> (I'd also rather avoid the "how do we design a new
> mail protocol" pandora's box - the amount of second-system effect would
> be huge, and it would take years to sort it out)

I competely agree with this sentiment, but that can be dealt with by
turning feature requests into architecture requests, and keeping the
features themselves out of the core specs. As an example, I want a
"recall" feature that lets me rescind an unread message from a recipient's
mailstore. That kind of feature has certain requirements (end-to-end
option encapsulation and verifiable identities), but that particular
feature should definitly not be in the spec. I can think of about 10-20
core architectural elements, but after that everything else probably
should be part of another spec.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Sat May 31 23:57:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18330
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 May 2003 23:57:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MJmI-0007Lr-Pr
	for ietf-list@asgard.ietf.org; Sat, 31 May 2003 23:45:02 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MJk8-0007Fa-Id
	for ietf@asgard.ietf.org; Sat, 31 May 2003 23:42:48 -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 XAA17977
	for <ietf@ietf.org>; Sat, 31 May 2003 23:42:46 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MJiS-0003FM-00
	for ietf@ietf.org; Sat, 31 May 2003 23:41:04 -0400
Received: from h80ad2513.async.vt.edu ([128.173.37.19] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MJiQ-0003FJ-00
	for ietf@ietf.org; Sat, 31 May 2003 23:41:03 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h513gXn1025595;
	Sat, 31 May 2003 23:42:34 -0400
Message-Id: <200306010342.h513gXn1025595@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: "Eric A. Hall" <ehall@ehsco.com>
Cc: ietf@ietf.org
Subject: Re: Spam 
In-Reply-To: Your message of "Sat, 31 May 2003 21:54:17 CDT."
             <3ED96AD9.7050003@ehsco.com> 
References: <020304736.20030531142859@brandenburg.com> <20030531220537.1E3D613969@sa.vix.com> <20030531184335.72e2ef97.moore@cs.utk.edu>
            <3ED96AD9.7050003@ehsco.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-799858064P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sat, 31 May 2003 23:42:32 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-799858064P
Content-Type: text/plain; charset=us-ascii

On Sat, 31 May 2003 21:54:17 CDT, "Eric A. Hall" said:

> One of the potential benefits of binding IP address to the host identity
> would be enforcement. A spammer may be able to crank millions of
> identities into thousands of domains, but they will only ever have a
> handful of servers and that smaller subset would be significantly easier
> to enforce against, at least until they move.

We're starting to see the rise of zombie networks of trojaned machines to
send spam, similar to the DDoS networks.  Which makes Paul Vixie's comments
even more important:

On Sun, 01 Jun 2003 02:14:07 +0000, Paul Vixie said:
> knowing the intent of the owner of the host is important.  we can't
> tolerate any more hosts which become open proxies or open relays by
> virtue of having swallowed an ms-outlook script-cookie pif-file.  if
> a host hasn't made its intent to send e-mail known through a trusted
> framework, then there's no reason for me to accept a tcp session from
> it.  (credit goes to margie arbon of maps for proving this to me.)



--==_Exmh_-799858064P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+2XYocC3lWbTT17ARAtL+AKDLr78SAgw+K0bazuwFYRF+6aqVNACfQ78S
9X8vxCM+hy0Q8aP7IXmyWo8=
=m8US
-----END PGP SIGNATURE-----

--==_Exmh_-799858064P--



